On 09/09/2012 06:33 PM, Mike Wilson wrote:
Is it defined how the browser should behave wrt calling
unrelated event handlers in user code during synchronous
XHR requests? (with "unrelated" I refer to events that are
not related to the ongoing synchronous request itself)
I didn't find statements d
On 9/9/12 12:13 PM, Glenn Maynard wrote:
In particular, a Blob represents immutable binary data. That means
that it has to copy the input anyway. Given that, it doesn't make
sense to pass the input by reference if the caller _does_ happen to
have an WebIDL array object.
That do
Is it defined how the browser should behave wrt calling
unrelated event handlers in user code during synchronous
XHR requests? (with "unrelated" I refer to events that are
not related to the ongoing synchronous request itself)
I didn't find statements directly addressing this in
http://www.w3.org
On Sun, Sep 9, 2012 at 9:34 AM, Boris Zbarsky wrote:
> In particular, a Blob represents immutable binary data. That means that
> it has to copy the input anyway. Given that, it doesn't make sense to pass
> the input by reference if the caller _does_ happen to have an WebIDL array
> object.
>
T
In particular, a Blob represents immutable binary data. That means that
it has to copy the input anyway. Given that, it doesn't make sense to
pass the input by reference if the caller _does_ happen to have an
WebIDL array object.
But worse yet, actual real-life callers call this with JS arra
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18809
Summary: Some examples in the index section (3.3.4) have errors
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: trivial
