On a general note, if window.stop() is invoked is not appropriate
language. window.stop() could set some flag for XMLHttpRequest to look
at, or have some other kind of connection, but implicit connections
are bad. We should remove those when we encounter them.
On Sat, Aug 17, 2013 at 1:48 AM,
On Thu, Aug 1, 2013 at 6:13 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jul 30, 2013 at 10:25 AM, Takeshi Yoshino tyosh...@google.com wrote:
Change on 2010/09/13
http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest-2/Overview.src.html.diff?r1=1.138;r2=1.139;f=h
reversed the order of
If you are going to Shenzhen in November for TPAC, please note there is
a Test the Web Forward event on Saturday November 9:
[[
http://lists.w3.org/Archives/Public/public-testtwf/2013Aug/.html
Now that we've wrapped up the Shanghai event, we've kicked off the
planning for our next event.
On 2013-08-28 17:48, Dominique Hazael-Massieux wrote:
Hi WebApps WG,
The Media Capture Task Force (responsible for specs that deal with
MediaStream objects [1]) has been considering whether one should be able
to assign a MediaStream to video and audio elements via an URL
obtained via
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23102
Bug ID: 23102
Summary: Reset response entity bodies
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
On Aug 30, 2013 4:05 AM, Anne van Kesteren ann...@annevk.nl wrote:
On a general note, if window.stop() is invoked is not appropriate
language. window.stop() could set some flag for XMLHttpRequest to look
at, or have some other kind of connection, but implicit connections
are bad. We should
On Fri, Aug 30, 2013 at 7:45 PM, Jonas Sicking jo...@sicking.cc wrote:
Why? I agree that it can be hard to define order of externally visible
effects, such as events, if there are any. However from a readability point
of view indirection through state flags just makes the spec harder to read.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23106
Bug ID: 23106
Summary: Spec should treat content type as an opaque string
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Sorry for the delay!
We've had an opportunity to discuss your suggestions and comments with our
internal teams and agree with your approach. The main original concerns we had
were:
* Creating a dependency between the screen and device orientation specs. Based
on your comments this doesn't
