https://www.w3.org/Bugs/Public/show_bug.cgi?id=24573
Bug ID: 24573
Summary: Clarify non-null Blob
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24573
Simon Pieters sim...@opera.com changed:
What|Removed |Added
Status|NEW |RESOLVED
On Fri, Feb 7, 2014 at 5:31 AM, Feras Moussa feras.mou...@hotmail.com wrote:
In addition to the base Stream spec, the remaining platform-specific pieces
which do not fit into the shared-base spec will live in an independent spec.
This includes things such as support in other APIs (XHR,
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24576
Bug ID: 24576
Summary: Calling URL.createObjectURL() on a closed Blob
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24577
Bug ID: 24577
Summary: [Custom]: Need adopted callback
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24578
Bug ID: 24578
Summary: [Custom]: define registry primitive
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24579
Bug ID: 24579
Summary: [Custom]: make callbacks more explicit
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24557
Hayato Ito hay...@chromium.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15417
Anne ann...@annevk.nl changed:
What|Removed |Added
Status|NEW |RESOLVED
Hi all,
I wonder what people think of if we started to rather aggressively deprecate
the horrible API
main-thread sync XHR?
Currently its usage is still way too high (up to 2% based on telemetry data),
but
if all the browsers warned about use of deprecated feature, we might be able to
get
From: Olli Pettay olli.pet...@helsinki.fi
And at least we'd improve responsiveness of those websites which stop using
sync XHR because of the warning.
I think this is a great point that makes such an effort worthwhile even if it
ends up not leading to euthanizing sync XHR.
On 2/7/14 5:56 PM, Domenic Denicola wrote:
I think this is a great point that makes such an effort worthwhile even if it
ends up not leading to euthanizing sync XHR.
I am all for it.
Cheers,
David
--
David Rajchenbach-Teller, PhD
Performance Team, Mozilla
On Fri, Feb 7, 2014 at 6:18 PM, Jonas Sicking jo...@sicking.cc wrote:
Agreed. I think for this to be effective we need to get multiple browser
vendors being willing to add such a warning. We would also need to add text
to the various versions of the spec (whatwg and w3c).
For what it's worth,
What about developers who are sending requests as the page is unloading? My
understanding is that sync requests are required. Is this not the case?
On Friday, February 7, 2014, Anne van Kesteren ann...@annevk.nl wrote:
On Fri, Feb 7, 2014 at 6:18 PM, Jonas Sicking jo...@sicking.cc wrote:
As I understand it, that is one of the scenarios covered by the recently
proposed Beacon API:
http://www.w3.org/TR/beacon/
Sent from my Windows Phone
From: Scott González
Sent: 2/7/2014 9:33 AM
To: Anne van Kesteren
Cc: Jonas Sicking; Domenic Denicola;
On 2/7/14 12:32 PM, Scott González wrote:
What about developers who are sending requests as the page is unloading?
Does Beacon address their use cases? If not, what are the use cases?
-Boris
On 02/07/2014 07:32 PM, Scott González wrote:
What about developers who are sending requests as the page is unloading? My
understanding is that sync requests are required. Is this not the case?
We need sendBeacon asap, and browsers could start warn first when sync XHR is
used outside unload
On 1/31/14 10:21 AM, ext Arthur Barstow wrote:
* Do we want to continue both efforts (and thus reflect this in the
charter update)?
Given the feedback on this thread, I don't think there is consensus to
only focus on one API so I added the Mozilla FileSystem API spec to the
set of File
As a side-note, it may be interesting to warn also that synchronous XHR
has different semantics between browsers so is not a good choice anyway.
Cheers,
David
On 2/7/14 6:18 PM, Jonas Sicking wrote:
Agreed. I think for this to be effective we need to get multiple browser
vendors being willing
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24583
Bug ID: 24583
Summary: [imports]: failed fetch should result null document in
import list
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Linux
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21650
Anne ann...@annevk.nl changed:
What|Removed |Added
Status|NEW |RESOLVED
On Feb 7, 2014 8:57 AM, Domenic Denicola dome...@domenicdenicola.com
wrote:
From: Olli Pettay olli.pet...@helsinki.fi
And at least we'd improve responsiveness of those websites which stop
using sync XHR because of the warning.
I think this is a great point that makes such an effort
On Feb 7, 2014, at 9:32 AM, Scott González scott.gonza...@gmail.com wrote:
What about developers who are sending requests as the page is unloading? My
understanding is that sync requests are required. Is this not the case?
Besides the proposed Beacon API, if you don't need to do a POST then
On Feb 7, 2014, at 9:18 AM, Jonas Sicking jo...@sicking.cc wrote:
On Feb 7, 2014 8:57 AM, Domenic Denicola dome...@domenicdenicola.com
wrote:
From: Olli Pettay olli.pet...@helsinki.fi
And at least we'd improve responsiveness of those websites which stop
using sync XHR because of
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24586
Bug ID: 24586
Summary: Remove FileList
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
There are certain situations where sync XHRs are, in fact, required...
unless we make other accommodations. For example, in the Clipboard API,
developers are allowed to inject into the clipboard as a semi-trusted event
during the event handling phase of certain user-initiated events (e.g.
On 02/08/2014 03:19 AM, James Greene wrote:
There are certain situations where sync XHRs are, in fact, required... unless
we make other accommodations. For example, in the Clipboard API,
developers are allowed to inject into the clipboard as a semi-trusted event
during the event handling phase
27 matches
Mail list logo
