Re: RfC: pre-LC version of Screen Orientation; deadline August 18

On August 14, 2014 at 3:23:23 AM, Dominique Hazael-Massieux (d...@w3.org) wrote: > > HTH, It does! thank you. I've filed a bug for each on GH.  https://github.com/w3c/screen-orientation/issues/ Hope to fix 'em up soon! 

[Bug 26587] New: Element removal order is undefined in "fully exit fullscreen"

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26587 Bug ID: 26587 Summary: Element removal order is undefined in "fully exit fullscreen" Product: WebAppsWG Version: unspecified Hardware: PC OS: All

[Bug 26580] Not enough "element" in "for an element"

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26580 Anne changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 26583] New: [Custom]: Add the possibility to extend the custom element

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26583 Bug ID: 26583 Summary: [Custom]: Add the possibility to extend the custom element Product: WebAppsWG Version: unspecified Hardware: PC OS: Windows NT

Re: [Streams API] Add load-using-streams functionality to XHR or only to Fetch API?

On Thu, Aug 14, 2014 at 9:39 AM, Takeshi Yoshino wrote: > I guess you don't want to do (a). (b) is fine. Then, readers of > http://fetch.spec.whatwg.org/ can easily know that discussions about fetch() > are happening at the ServiceWorker issue tracker even if he/she is not > familiar with ServiceW

[Bug 26580] New: Not enough "element" in "for an element"

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26580 Bug ID: 26580 Summary: Not enough "element" in "for an element" Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: nor

Re: [Streams API] Add load-using-streams functionality to XHR or only to Fetch API?

On Thu, Aug 14, 2014 at 4:29 PM, Anne van Kesteren wrote: > On Thu, Aug 14, 2014 at 9:19 AM, Takeshi Yoshino > wrote: > > We'd like to continue prototyping in Blink anyway to provide feedback to > the > > spec as browser developer's point of view, but if we're sure that we > won't > > add it to

Re: [Streams API] Add load-using-streams functionality to XHR or only to Fetch API?

On Thu, Aug 14, 2014 at 9:19 AM, Takeshi Yoshino wrote: > We'd like to continue prototyping in Blink anyway to provide feedback to the > spec as browser developer's point of view, but if we're sure that we won't > add it to XHR, we want to stop the work on XHR (both spec and impl) at some > early

Re: RfC: pre-LC version of Screen Orientation; deadline August 18

Le lundi 04 août 2014 à 08:19 -0400, Arthur Barstow a écrit : > Marcos and Mounir, the Editors of WebApps' Screen Orientation API, > consider their spec feature complete with only a few minor [Bugs] open. > As such, we seek wide review on their "pre-LC" version: > >

Re: [Streams API] Add load-using-streams functionality to XHR or only to Fetch API?

Streams API itself still has many issues, right. We'd like to continue prototyping in Blink anyway to provide feedback to the spec as browser developer's point of view, but if we're sure that we won't add it to XHR, we want to stop the work on XHR (both spec and impl) at some early stage after fig

Re: [Streams API] Add load-using-streams functionality to XHR or only to Fetch API?

On Thu, Aug 14, 2014 at 6:20 AM, Takeshi Yoshino wrote: > We're implementing Streams API and integration of it and XHR > experimentally in Blink. I think the question is not so much how far along XMLHttpRequest and fetch() are, but how far along streams is. E.g. a chat I had yesterday http://krij