The clipboard spec tests are now on their way to the web-platform-tests
repository:
https://github.com/w3c/web-platform-tests/pull/1097
..pending the review:
https://critic.hoppipolla.co.uk/r/1983
If you want to help, that review tool is very good at enabling collaboration
and various people
On Wed, Jul 16, 2014 at 10:58 PM, Hajime Morrita morr...@google.com wrote:
https://github.com/w3c/webcomponents/commit/90da4809a207916486bc7af83a568f3762e780a0
Does this really make sense though?
We want to include credentials for same-origin fetches, but not
cross-origin? Why not always
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26366
Bug ID: 26366
Summary: It's possible to go fullscreen with an element not in
the document
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Linux
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26368
Bug ID: 26368
Summary: Typo: Queue a task to run these subsubsteps
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity:
On Jul 14, 2014, at 3:47 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Jul 10, 2014 at 7:05 PM, Arun Ranganathan a...@mozilla.com wrote:
On Jul 3, 2014, at 10:50 AM, Anne van Kesteren ann...@annevk.nl wrote:
That would mean you would get different results between using
FileReaderSync
Aymeric,
On Jul 16, 2014, at 8:20 AM, Aymeric Vitte vitteayme...@gmail.com wrote:
Example:
var myfile=new Blob();
//chunks are coming in
myfile=new Blob([myfile,chunk],...)
//mylink A tag
mylink.href=URL.createObjectURL(myfile)
click on mylink -- does not work
Expected behavior:
On Jun 30, 2014, at 7:13 PM, Glenn Maynard gl...@zewt.org wrote:
Why would the identifier not just be the blob URL itself?
Done.
Also, both Chrome and Firefox treat the entire URL as case-sensitive, eg.
Blob:... won't revoke the URL, or uppercasing the hostname portion in
Chrome.
Arun,
Streams will solve this, assuming they are implemented by all related
APIs (this is not obvious, most of WGs seem not to care at all now that
they have implemented their own so-called streams)
Quoting your other answer:
Well, the bug that removed them
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26379
Bug ID: 26379
Summary: exitFullscreen() should pop from the stack, resize and
fire fullscreenchange events together
Product: WebAppsWG
Version: unspecified
Hardware: PC
