Tuesday, 31 May 2016
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#257)
- Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78)
- Re: [whatwg/dom] Un-customify adopted elements (#260)
- Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78)
- [whatwg/dom] Un-customify adopted elements (#260)
- Re: [whatwg/dom] Don't set custom element state redundantly (#253)
- Re: [w3c/IndexedDB] Return number of records deleted (#32)
- Re: [whatwg/dom] Don't set custom element state redundantly (#253)
- Re: [whatwg/dom] Don't set custom element state redundantly (#253)
- Re: [whatwg/streams] light weight transformations (#461)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509)
- Re: [whatwg/fetch] Grammar change: "that is check" to that checks" (#310)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258)
- [w3c/webcomponents] Why must the is="" attribute exist? (#509)
- Re: [w3c/webcomponents] What happens in these slot/content scenarios? (#508)
- [whatwg/dom] Why can't Node's nodeValue use [TreatNullAs=EmptyString]? (#259)
- [w3c/webcomponents] What happens in these slot/content scenarios? (#508)
- Re: [w3c/webcomponents] How to detect when an element is transcluded into a shadow tree? (#504)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258)
- Re: [w3c/IndexedDB] Integrate with window.onerror (#49)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258)
- Re: [whatwg/fetch] Grammar change: "that is check" to that checks" (#310)
- Re: [slightlyoff/ServiceWorker] should UA check for updates on navigate when there is no fetch event? (#905)
- [whatwg/fetch] Grammar change: "that is check" to that checks" (#310)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258)
- [whatwg/dom] Use HTML's 'document base URL' concept. (#258)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462)
- [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462)
- [whatwg/streams] Synchronous (or asynchronous) state probing on WritableStream (#463)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486)
- Re: [slightlyoff/ServiceWorker] what is the best way to save Request while offline ? (#904)
- Re: [slightlyoff/ServiceWorker] what is the best way to save Request while offline ? (#904)
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#257)
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#257)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#257)
- [whatwg/storage] Classify 'Application Cache' as site storage (#30)
- [whatwg/dom] Shadow: Update the definition of an unclosed node (#257)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207)
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#256)
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#256)
- [whatwg/dom] Shadow: Update the definition of an unclosed node (#256)
- [slightlyoff/ServiceWorker] need AsyncLocalStorage (was #904) (#906)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- Re: [w3ctag/spec-reviews] File URI Scheme (#59)
- Re: [whatwg/streams] Port locking infrastructure to writable streams (#319)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462)
- [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- Re: [whatwg/dom] I don't think Element.insertAdjacentText can cause CEReactions (#255)
- Re: [whatwg/dom] I don't think Element.insertAdjacentText can cause CEReactions (#255)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207)
- Re: [w3ctag/spec-reviews] File URI Scheme (#59)
- Re: [w3ctag/spec-reviews] File URI Scheme (#59)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278)
- Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78)
- Re: [w3ctag/spec-reviews] File URI Scheme (#59)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- Re: [w3c/IndexedDB] Integrate with window.onerror (#49)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207)
- [whatwg/streams] light weight transformations (#461)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207)
- Re: [w3c/manifest] Ability to detect if the current document is part of an "installed" web app (#454)
- Re: [w3c/manifest] Ability to detect if the current document is part of an "installed" web app (#454)
- Re: [w3ctag/spec-reviews] File URI Scheme (#59)
- Re: [w3ctag/spec-reviews] First Party Cookies (#114)
- [whatwg/dom] I don't think Element.insertAdjacentText can cause CEReactions (#255)
Monday, 30 May 2016
- Re: [w3c/manifest] Add support for disabling default overscroll actions (#398)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207)
- Re: [whatwg/fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255)
- Re: [whatwg/fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255)
- Re: [whatwg/fetch] Body's total bytes for HEAD requests (#284)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278)
- Re: [whatwg/fetch] Set the HTTPS state to 'modern' for more things (#290)
- Re: [whatwg/fetch] Set the HTTPS state to 'modern' for more things (#290)
- Re: [whatwg/fetch] Block redirects to non-HTTP schemes (#309)
- Re: [whatwg/fetch] Block redirects to non-HTTP schemes (#309)
- Re: [w3c/WebPlatformWG] Add myself to attendance member for Sep. 19, WebComponents. (#37)
- Re: [w3c/WebPlatformWG] Add myself to attendance member for Sep. 19, WebComponents. (#37)
- [whatwg/fetch] Block redirects to non-HTTP schemes (#309)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56)
- Re: [whatwg/dom] Markup "synthetic events" term as a proper <dfn> (#254)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56)
- [w3c/WebPlatformWG] Add myself to attendance member for Sep. 19, WebComponents. (#37)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56)
- Re: [slightlyoff/ServiceWorker] what is the best way to save Request while offline ? (#904)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56)
- Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41)
- [whatwg/dom] Markup "synthetic events" term as a proper <dfn> (#254)
Sunday, 29 May 2016
- Re: [slightlyoff/ServiceWorker] Service workers registration lifetime (#903)
- Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902)
- Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902)
- Re: [whatwg/storage] Expose persist() to workers (#29)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902)
- Re: [slightlyoff/ServiceWorker] Service workers registration lifetime (#903)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/storage] Expose persist() to workers (#29)
Saturday, 28 May 2016
- [slightlyoff/ServiceWorker] should UA check for updates on navigate when there is no fetch event? (#905)
- Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78)
- Re: [whatwg/storage] Expose persist() to workers (#29)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77)
- Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41)
- Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
Friday, 27 May 2016
- Re: [w3c/screen-orientation] Move the HTML specification monkey patching to the HTML specification (#69)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41)
- Re: [whatwg/streams] Consider adding type assertions for all abstract operations (#453)
- Re: [whatwg/streams] ReadableStreamCancel() should assert IsReadableStream(stream) (#452)
- Re: [whatwg/streams] ReadableStreamCancel() should assert IsReadableStream(stream) (#452)
- Re: [whatwg/streams] Add an assert on stream's state in ReadableStreamAddReadRequest() (#458)
- Re: [whatwg/streams] ReadableStreamAddReadRequest() should assert state is readable (#454)
- Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41)
- Re: [whatwg/streams] Move assertion on stream from ReadableStreamCancel() to its callers (#459)
- Re: [whatwg/streams] Update wpt-runner dependency to require 1.0.1 or later (#456)
- Re: [whatwg/streams] Update wpt-runner dependency to require 1.0.1 or later (#456)
- Re: [whatwg/streams] PromiseInvokeOrNoop is not autolinking (#450)
- Re: [w3c/WebPlatformWG] Add Microsoft attendees (#36)
- Re: [whatwg/streams] Fix PromiseInvokeOrNoop autolinking (#460)
- Re: [whatwg/streams] Fix PromiseInvokeOrNoop autolinking (#460)
- Re: [whatwg/streams] Typo fix (#457)
- Re: [w3c/WebPlatformWG] Add Microsoft attendees (#36)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- [w3c/WebPlatformWG] Add Microsoft attendees (#36)
- Re: [whatwg/storage] Expose persist() to workers (#29)
- Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41)
- [whatwg/storage] Expose persist() to workers (#29)
- Re: [w3c/FileAPI] Re-add FileReader.readAsBinaryString() ? (#39)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [slightlyoff/ServiceWorker] Service workers registration lifetime (#903)
- Re: [slightlyoff/ServiceWorker] what is the best way to save Request while offline ? (#904)
- Re: [whatwg/xhr] abort() handling of state is busted (#54)
- Re: [whatwg/url] Consider always escaping U+0020 (#125)
- Re: [whatwg/url] Consider always escaping U+0020 (#125)
- [whatwg/url] Consider always escaping U+0020 (#125)
- Re: [whatwg/streams] PromiseInvokeOrNoop is not autolinking (#450)
- [whatwg/streams] Fix PromiseInvokeOrNoop autolinking (#460)
- Re: [whatwg/streams] ReadableStreamCancel() should assert IsReadableStream(stream) (#452)
- [whatwg/streams] Move assertion on stream from ReadableStreamCancel() to its callers (#459)
- Re: [w3c/WebPlatformWG] Create page for July 28-29 service worker meeting. (#35)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- [whatwg/encoding] Group constants together in half-width math (#49)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193)
- Re: [slightlyoff/ServiceWorker] Service workers registration lifetime (#903)
- Re: [slightlyoff/ServiceWorker] Service workers registration lifetime (#903)
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193)
- Re: [whatwg/xhr] abort() handling of state is busted (#54)
- Re: [whatwg/xhr] abort() handling of state is busted (#54)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- [slightlyoff/ServiceWorker] what is the best way to save Request while offline ? (#904)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193)
- Re: [whatwg/fetch] Only-if-cached (#159)
- Re: [w3c/push-api] Fire pushsubscriptionchange when user revokes permission (#116)
- [slightlyoff/ServiceWorker] Service workers registration lifetime (#903)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145)
- Re: [whatwg/fetch] Only-if-cached (#159)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145)
Thursday, 26 May 2016
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [whatwg/fetch] Only-if-cached (#159)
- Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88)
- [w3c/WebPlatformWG] Create page for July 28-29 service worker meeting. (#35)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88)
- Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145)
- Re: [whatwg/xhr] abort() handling of state is busted (#54)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [whatwg/url] javascript: URL should not be able to be base URLs (#124)
- Re: [whatwg/fetch] Only-if-cached (#159)
- Re: [whatwg/fetch] Only-if-cached (#159)
- [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486)
- Re: [whatwg/streams] ReadableStreamAddReadRequest() should assert state is readable (#454)
- [whatwg/streams] Add an assert on stream's state in ReadableStreamAddReadRequest() (#458)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- [whatwg/url] javascript: URL should not be able to be base URLs (#124)
- Re: [whatwg/streams] should ReadableStreamClose() resolve BYOB reader readIntoRequests? (#455)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] idea: clash-free auto-generated class naming. (#492)
- Re: [w3c/webcomponents] idea: clash-free auto-generated class naming. (#492)
- [whatwg/streams] Typo fix (#457)
- [whatwg/streams] Update wpt-runner dependency to require 1.0.1 or later (#456)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- Re: [whatwg/fetch] Only-if-cached (#159)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/webcomponents] How to detect when an element is transcluded into a shadow tree? (#504)
- Re: [w3c/webcomponents] How to detect when an element is transcluded into a shadow tree? (#504)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486)
- Re: [w3c/webcomponents] How to detect when an element is transcluded into a shadow tree? (#504)
Wednesday, 25 May 2016
- Re: [w3c/webcomponents] customElements.define not working (#506)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [w3ctag/spec-reviews] ARIA (#107)
- Re: [w3ctag/spec-reviews] ARIA (#107)
- [w3c/uievents-key] [DomKey] Suggest using DomKey "LaunchApplication1" instead of "LaunchMyComputer" for APPCOMMAND_LAUNCH_APP1 (#27)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453)
- Re: [whatwg/xhr] abort() handling of state is busted (#54)
- [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97)
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193)
- [whatwg/streams] should ReadableStreamClose() resolve BYOB reader readIntoRequests? (#455)
- Re: [w3c/push-api] Fire pushsubscriptionchange when user revokes permission (#116)
- [whatwg/streams] ReadableStreamAddReadRequest() should assert state is readable (#454)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453)
- [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453)
- Re: [whatwg/xhr] abort() handling of state is busted (#54)
- [whatwg/streams] ReadableStreamCancel() should assert IsReadableStream(stream) (#452)
- Re: [whatwg/streams] PromiseInvokeOrNoop is not linked (#451)
- Re: [whatwg/streams] PromiseInvokeOrNoop is not linked (#451)
- [whatwg/streams] PromiseInvokeOrNoop is not linked (#451)
- [whatwg/streams] PromiseInvokeOrNoop is not autolinking (#450)
- Re: [w3c/webcomponents] customElements.define not working (#506)
- Re: [w3c/webcomponents] customElements.define not working (#506)
- Re: [w3c/webcomponents] customElements.define not working (#506)
- [w3c/webcomponents] customElements.define not working (#506)
- Re: [w3c/push-api] Fire pushsubscriptionchange when user revokes permission (#116)
- Re: [w3c/WebPlatformWG] Add self to attendees list (#34)
- Re: [w3c/WebPlatformWG] Add self to attendees list (#34)
- [w3c/WebPlatformWG] Add self to attendees list (#34)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- Re: [w3c/push-api] Fire pushsubscriptionchange when user revokes permission (#116)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- [whatwg/url] Clarify the informative nature of referenced RFCs (#123)
- Re: [whatwg/url] Section 3 (Hosts) should be non-normative (#122)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [slightlyoff/ServiceWorker] Secure Client-Subscribed 1:M Broadcast message delivery (#901)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486)
- Re: [slightlyoff/ServiceWorker] Additional PositionOptions required for ServiceWorker background GeoLocation (#898)
- Re: [slightlyoff/ServiceWorker] Additional PositionOptions required for ServiceWorker background GeoLocation (#898)
- Re: [w3ctag/spec-reviews] Privacy Mode (#101)
- Re: [slightlyoff/ServiceWorker] Additional PositionOptions required for ServiceWorker background GeoLocation (#898)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [w3c/manifest] Allow for multiple scopes (#449)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [w3c/manifest] Integration with service workers (#161)
- Re: [heycam/webidl] Missing destruction sequence for ice agent. (#127)
- Re: [heycam/webidl] Missing destruction sequence for ice agent. (#127)
- Re: [heycam/webidl] Missing destruction sequence for ice agent. (#127)
Tuesday, 24 May 2016
- Re: [w3c/IndexedDB] boolean should be a valid key (#76)
- [w3c/IndexedDB] Enforce transaction commit ordering more strictly (#77)
- [heycam/webidl] Missing destruction sequence for ice agent. (#127)
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193)
- [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193)
- Re: [w3c/push-api] Fire pushsubscriptionchange when user revokes permission (#116)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [w3c/FileAPI] Update Typed Array spec URL (#34)
- Re: [w3c/FileAPI] Update Typed Array spec URL (#34)
- Re: [w3c/FileAPI] Update Typed Array spec URL (#34)
- Re: [w3c/FileAPI] Update Typed Array spec URL (#34)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252)
- Re: [whatwg/fetch] Allow * for Access-Control-Allow-Headers and Access-Control-Allow-Methods (#251)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/streams] ReadableStreamTee returns undefined `branch1` and `branch2` (#449)
- Re: [whatwg/streams] ReadableStreamTee returns undefined `branch1` and `branch2` (#449)
- [whatwg/dom] Don't set custom element state redundantly (#253)
- Re: [w3c/push-api] Fire pushsubscriptionchange when user revokes permission (#116)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)
Monday, 23 May 2016
- [whatwg/streams] ReadableStreamTee returns undefined `branch1` and `branch2` (#449)
- Re: [w3c/manifest] Integration with service workers (#161)
- Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902)
- Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902)
- Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902)
- Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902)
- [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902)
- Re: [w3c/webcomponents] add a script for auto-publication (#498)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)
- [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)
- Re: [heycam/webidl] "Restricted" Float32Array (#126)
- Re: [heycam/webidl] "Restricted" Float32Array (#126)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [heycam/webidl] "Restricted" Float32Array (#126)
- Re: [heycam/webidl] "Restricted" Float32Array (#126)
- Re: [heycam/webidl] "Restricted" Float32Array (#126)
- [heycam/webidl] "Restricted" Float32Array (#126)
- Re: [w3c/editing] Should beforeFocus be another Edit Event? (#27)
- Re: [w3c/editing] Should beforeFocus be another Edit Event? (#27)
- Re: [w3c/editing] RESOLUTION: We think we want strict subsets - events is a subset of caret is a subset of typing which is a subset of true. (#86)
- Re: [w3c/editing] RESOLUTION: We think we want strict subsets - events is a subset of caret is a subset of typing which is a subset of true. (#86)
- Re: [w3c/editing] We could have "data" property that returns the text/plain version and a dataTransfer field for richer things. (#105)
- Re: [w3c/editing] We could have "data" property that returns the text/plain version and a dataTransfer field for richer things. (#105)
- Re: [w3c/editing] [Input Events] Word deletion (#125)
- Re: [w3c/editing] [Input Events] Word deletion (#125)
- Re: [w3c/editing] [Input Events] Rename "replaceContent" with "insertContent" or "insertNonText" (#126)
- Re: [w3c/editing] New API: Selection#makeVisible() (#129)
- Re: [w3c/editing] New API: Selection#makeVisible() (#129)
- [w3c/editing] New API: Selection#makeVisible() (#129)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)
- Re: [w3c/webcomponents] How to detect when an element is transcluded into a shadow tree? (#504)
Sunday, 22 May 2016
- [w3c/pointerlock] pointerlockchange and the accessibility tree (#1)
- Re: [whatwg/url] The href setter needs to reset the query object (#117)
- Re: [w3c/webcomponents] attachedCallback in light tree, but when transcluded into shadow tree? (#504)
- Re: [w3c/webcomponents] attachedCallback in light tree, but when transcluded into shadow tree? (#504)
- Re: [w3c/webcomponents] attachedCallback in light tree, but what about in shadow tree? (#504)
- [w3c/webcomponents] attachedCallback in light tree, but what about in shadow tree? (#504)
- Re: [w3c/webcomponents] Voting for/against proposals (#503)
- Re: [w3c/webcomponents] Voting for/against proposals (#503)
- Re: [w3c/webcomponents] Voting for/against proposals (#503)
- Re: [w3c/webcomponents] Voting for/against proposals (#503)
- [w3c/uievents] Figure out what to do with focusin/focusout (#88)
- [w3c/webcomponents] Voting for/against proposals (#503)
Saturday, 21 May 2016
- Re: [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308)
- Re: [w3c/webcomponents] add a script for auto-publication (#498)
- Re: [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308)
- [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125)
Friday, 20 May 2016
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125)
- [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/dom] cancelBubble legacy property (#211)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [w3c/editing] beforeinput: Should we fire `replaceContent` during IME composition? (#122)
- Re: [w3c/editing] beforeinput: Should we fire `replaceContent` during IME composition? (#122)
- Re: [w3c/editing] [Input Events] Word deletion (#125)
- [whatwg/fetch] Vary HTTP cache on credentials mode (#307)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Clarify whether a dictionary member set to `undefined` is "present" (#124)
- Re: [heycam/webidl] Clarify whether a dictionary member set to `undefined` is "present" (#124)
- [whatwg/url] Section 3 (Hosts) should be non-normative (#122)
- Re: [whatwg/dom] Use USVString for URLs and origins in IDL (#252)
- Re: [whatwg/dom] Use USVString for URLs and origins in IDL (#252)
- Re: [w3c/editing] [Input Events] Word deletion (#125)
- [whatwg/dom] Use USVString for URLs and origins in IDL (#252)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [w3c/clipboard-apis] Create an easier to use API (#12)
- [w3c/uievents-key] It's odd KEYCODE_MEDIA_CLOSE of Android is mapped to "Close" (#26)
- [slightlyoff/ServiceWorker] Secure Client-Subscribed 1:M Broadcast message delivery (#901)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] add a script for auto-publication (#498)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)
- Re: [heycam/webidl] Clarify whether a dictionary member set to `undefined` is "present" (#124)
- Re: [w3c/DOM-Parsing] Remove styles made obsolete by new W3C stylesheets (#8)
- [w3c/DOM-Parsing] Remove styles made obsolete by new W3C stylesheets (#8)
- [heycam/webidl] Clarify whether a dictionary member set to `undefined` is "present" (#124)
Thursday, 19 May 2016
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [w3c/webcomponents] add a script for auto-publication (#498)
- Re: [w3c/IndexedDB] Support N-dimensional queries on indexes (#40)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123)
- [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123)
- [heycam/webidl] "File a bug" header goes to bugzilla not github (#122)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)
Wednesday, 18 May 2016
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295)
- Re: [whatwg/fetch] update reference to referrer policy spec (#305)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295)
- Re: [whatwg/fetch] update reference to referrer policy spec (#305)
- Re: [whatwg/fetch] Only-if-cached (#159)
- Re: [whatwg/xhr] what is the problem (#70)
- Re: [whatwg/xhr] what is the problem (#70)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [whatwg/xhr] what is the problem (#70)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468)
- [whatwg/xhr] what is the problem (#70)
- Re: [whatwg/url] incorrect definition of ASCII hex digits (#121)
- Re: [slightlyoff/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [slightlyoff/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [whatwg/url] incorrect definition of ASCII hex digits (#121)
- Re: [whatwg/url] incorrect definition of ASCII hex digits (#121)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899)
- Re: [w3ctag/spec-reviews] CSP (#42)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468)
- [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467)
- Re: [whatwg/url] incorrect definition of ASCII hex digits (#121)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
Tuesday, 17 May 2016
- Re: [w3c/webcomponents] Move respec-complement.css to custom and shadow (#502)
- Re: [w3c/webcomponents] Move respec-complement.css to custom and shadow (#502)
- [w3c/webcomponents] Move respec-complement.css to custom and shadow (#502)
- Re: [w3c/webcomponents] add a script for auto-publication (#498)
- Re: [w3c/webcomponents] add a script for auto-publication (#498)
- [whatwg/url] incorrect definition of ASCII hex digits (#121)
- Re: [w3c/webcomponents] add a script for auto-publication (#498)
- Re: [w3c/webcomponents] add a script for auto-publication (#498)
- Re: [w3c/webcomponents] add a script for auto-publication (#498)
- [whatwg/fetch] Add referrer policy to blob-generated responses (#306)
- Re: [whatwg/fetch] Blob URLs should grab HTTPS state from Blob objects (#270)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899)
- [whatwg/fetch] update reference to referrer policy spec (#305)
- Re: [whatwg/storage] Fix typo to 'conservative' (#28)
- Re: [whatwg/storage] Fix typo to 'conservative' (#28)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- [whatwg/storage] Fix typo to 'conservative' (#28)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [w3c/webcomponents] What does the construct stylesheets proposal mean for web developers? (#501)
- Re: [w3c/webcomponents] What does the construct stylesheets proposal mean for web developers? (#501)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
Monday, 16 May 2016
- Re: [w3c/webcomponents] add a script for auto-publication (#498)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and opaque origins (#900)
- Re: [w3c/webcomponents] Update attachedCallback to connectedCallback. (#491)
- [w3c/webcomponents] What does the construct stylesheets proposal mean for web developers? (#501)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899)
- Re: [whatwg/streams] Should consumers of readers/streams be notified why a stream was canceled? (#448)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and opaque origins (#900)
- Re: [whatwg/encoding] Creating test suites for each encoding. (#30)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272)
- [slightlyoff/ServiceWorker] Foreign fetch and opaque origins (#900)
- [slightlyoff/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [w3c/uievents-key] No differences between "AudioBassDown", "AudioBassUp" and "AudioBassBoostDown", "AudioBassBoostUp"? (#25)
- [w3c/uievents-key] No differences between "AudioBassDown", "AudioBassUp" and "AudioBassBoostDown", "AudioBassBoostUp"? (#25)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272)
- Re: [whatwg/xhr] Consider setting omit-Origin-header-flag for same origin requests (#31)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Body's total bytes for HEAD requests (#284)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/fetch] Body's total bytes for HEAD requests (#284)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [w3c/manifest] Include Minimal Store/Catalog MetaData in Manifest (#448)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897)
- Re: [slightlyoff/ServiceWorker] "// close() method inherited from WorkerGlobalScope should not be accessible." (#865)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
Sunday, 15 May 2016
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [whatwg/dom] toggleEventListener (#251)
- Re: [whatwg/dom] toggleEventListener (#251)
- Re: [whatwg/dom] toggleEventListener (#251)
- Re: [whatwg/dom] toggleEventListener (#251)
- Re: [whatwg/dom] toggleEventListener (#251)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- [whatwg/dom] toggleEventListener (#251)
- Re: [whatwg/fetch] Body's total bytes for HEAD requests (#284)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- [whatwg/fetch] Optional disable setting headers keys in lowercase (#304)
- Re: [slightlyoff/ServiceWorker] Correct scope documentation in explainer.md (#797)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
Saturday, 14 May 2016
- [whatwg/streams] Should consumers of readers/streams be notified why a stream was canceled? (#448)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
Friday, 13 May 2016
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [whatwg/streams] new ReadableStream() header specifies default highWaterMark=1 (#447)
- [whatwg/streams] new ReadableStream() header specifies default highWaterMark=1 (#447)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [w3c/webcomponents] Expose ShadowRoot object's encapsulation mode (#275)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [slightlyoff/ServiceWorker] Move service worker spec into w3c (#881)
- Re: [w3c/webcomponents] [Shadow] How should various document internal references work when SVG is being used in shadow DOM (bugzilla: 27380) (#179)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)
- Re: [whatwg/url] Percent-encode 0x0D and 0x0A to "%0D%0A" in the application/x-www-form-urlencoded byte serializer? (#120)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897)
- Re: [WICG/directory-upload] HTMLInputElement.directory should be a Directory attribute and not a boolean (#31)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [WICG/directory-upload] Consider to remove HTMLInputElement.getFilesAndDirectories andHTMLInputElement.getFiles (#33)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [slightlyoff/ServiceWorker] Move service worker spec into w3c (#881)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249)
- Re: [whatwg/url] Percent-encode 0x0D and 0x0A to "%0D%0A" in the application/x-www-form-urlencoded byte serializer? (#120)
- [slightlyoff/ServiceWorker] Additional PositionOptions required for ServiceWorker background GeoLocation (#898)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- [w3ctag/spec-reviews] ReadableStreams (specs: Streams, Fetch) (#121)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [heycam/webidl] Add namespaces (#121)
Thursday, 12 May 2016
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295)
- Re: [whatwg/fetch] TypeError new Headers(obj) (#300)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/uievents] Gamepad-specific DOM keys / location? (#79)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Update attachedCallback to connectedCallback. (#491)
- Re: [whatwg/url] IDNA (#53)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/fetch] Only-if-cached (#159)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [WICG/directory-upload] Easier way to get files without complicated asynchronous traversal code (#26)
- Re: [WICG/directory-upload] Easier way to get files without complicated asynchronous traversal code (#26)
- Re: [w3c/uievents] Gamepad-specific DOM keys / location? (#79)
- Re: [w3c/uievents] Gamepad-specific DOM keys / location? (#79)
- Re: [WICG/directory-upload] Leading slash in FormData filename field (#36)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249)
- Re: [whatwg/dom] surroundContents() with CharacterData node as newParent argument (#250)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [whatwg/dom] surroundContents() with CharacterData node as newParent argument (#250)
- Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303)
- Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303)
- [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/dom] surroundContents() with CharacterData node as newParent argument (#250)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [w3c/webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/dom] Shadow: define composedPath() (#247)
- Re: [w3c/push-api] Use NotAllowedError instead of defining a new PermissionDeniedError. … (#192)
- Re: [w3c/push-api] Refer to reusable definition of PermissionDeniedError once that becomes available (#107)
- Re: [w3c/push-api] Use NotAllowedError instead of defining a new PermissionDeniedError. … (#192)
- Re: [w3c/push-api] Note that the subscription shares fate with the registration (#191)
- Re: [w3c/push-api] Clarify when to unsubscribe if the service worker is unregistered (#190)
- Re: [w3c/push-api] Note that the subscription shares fate with the registration (#191)
- Re: [whatwg/url] Percent-encode 0x0D and 0x0A to "%0D%0A" in the application/x-www-form-urlencoded byte serializer? (#120)
- Re: [whatwg/url] Percent-encode 0x0D and 0x0A to "%0D%0A" in the application/x-www-form-urlencoded byte serializer? (#120)
- [whatwg/url] Percent-encode 0x0D and 0x0A to "%0D%0A" in the application/x-www-form-urlencoded byte serializer? (#120)
- Re: [whatwg/url] Investigate aligning application/x-www-form-urlencoded with URL's query (#18)
- Re: [whatwg/url] Investigate aligning application/x-www-form-urlencoded with URL's query (#18)
- Re: [w3c/webcomponents] Update attachedCallback to connectedCallback. (#491)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/url] Investigate aligning application/x-www-form-urlencoded with URL's query (#18)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [w3c/IndexedDB] Define flush-to-disk guarantees and control (#50)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)
- Re: [w3c/uievents] Gamepad-specific DOM keys / location? (#79)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)
- Re: [whatwg/dom] Shadow: define composedPath() (#247)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/dom] Shadow: define composedPath() (#247)
- Re: [whatwg/dom] Rename rootNode to getRootNode() and add composed argument (#248)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [w3c/push-api] Note that the subscription shares fate with the registration (#191)
- [w3c/push-api] Use NotAllowedError instead of defining a new PermissionDeniedError. … (#192)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745)
- [w3ctag/spec-reviews] Performance API's, Security and Privacy (#120)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
Wednesday, 11 May 2016
- [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- [heycam/webidl] Add namespaces (#121)
- Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119)
- Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [w3ctag/spec-reviews] URNbis documents (#117)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/manifest] Accessible Platform Architectures WG review (#419)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)
- Re: [w3c/push-api] Refer to reusable definition of PermissionDeniedError once that becomes available (#107)
- Re: [w3c/push-api] Note that the subscription shares fate with the registration (#191)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [whatwg/dom] Shadow: define composedPath() (#247)
- Re: [whatwg/dom] Shadow: define composedPath() (#247)
- Re: [whatwg/dom] Rename rootNode to getRootNode() and add composed argument (#248)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)
- Re: [whatwg/fetch] Fetch should handle 'X-Frame-Options' (#302)
- Re: [heycam/webidl] Use CreateDataProperty where possible. (#117)
- [whatwg/dom] surroundContents() with CharacterData node as newParent argument (#250)
- Re: [whatwg/dom] Shadow: define composedPath() (#247)
- [heycam/webidl] Update to the ES2017 signature of [[DefineOwnProperty]]. (#120)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [w3ctag/spec-reviews] TAG Review of HTML 5.1 (#119)
- Re: [whatwg/fetch] Fetch should handle 'X-Frame-Options' (#302)
- Re: [whatwg/fetch] Fetch should handle 'X-Frame-Options' (#302)
- Re: [whatwg/fetch] Fetch should handle 'X-Frame-Options' (#302)
- [whatwg/fetch] Fetch should handle 'X-Frame-Options' (#302)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [heycam/webidl] Need an error for "User refused permission" (#95)
- Re: [heycam/webidl] Document that NotAllowedError should be used for denied permissions. (#116)
- Re: [heycam/webidl] Use CreateDataProperty where possible. (#117)
- Re: [whatwg/dom] Shadow: define composedPath() (#247)
- Re: [whatwg/dom] Shadow: define composedPath() (#247)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/dom] Shadow: define composedPath() (#247)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/dom] Unify behavior for error handling in supports() and contains() methods (#202)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
Tuesday, 10 May 2016
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119)
- [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119)
- [whatwg/dom] Provide greater visibility of `implements` relationships? (#249)
- [w3ctag/spec-reviews] TAG Review of HTML 5.1 (#119)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896)
- Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896)
- Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896)
- [heycam/webidl] What is the expected interaction of [SecureContext] with mixins? (#118)
- [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897)
- Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896)
- [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896)
- Re: [w3c/DOM-Parsing] Sort out what's happening with innerHTML on <script> and <style> in XML documents (#6)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [w3c/DOM-Parsing] Sort out what's happening with innerHTML on <script> and <style> in XML documents (#6)
- Re: [w3ctag/spec-reviews] relative URLs are not updated pushState() (#118)
- Re: [w3c/DOM-Parsing] Sort out what's happening with innerHTML on <script> and <style> in XML documents (#6)
- Re: [w3c/DOM-Parsing] Sort out what's happening with innerHTML on <script> and <style> in XML documents (#6)
- Re: [w3c/DOM-Parsing] Sort out what's happening with innerHTML on <script> and <style> in XML documents (#6)
- Re: [w3c/DOM-Parsing] Sort out what's happening with innerHTML on <script> and <style> in XML documents (#6)
- Re: [slightlyoff/ServiceWorker] Fix Typo: "necessary" (#895)
- Re: [slightlyoff/ServiceWorker] Fix Typo: "necessary" (#895)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/dom] input.toggle for checkbox, radios (#246)
- [slightlyoff/ServiceWorker] Fix Typo: "necessary" (#895)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- [whatwg/dom] Rename rootNode to getRootNode() and add composed argument (#248)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/dom] input.toggle for checkbox, radios (#246)
- [whatwg/dom] Shadow: define composedPath() (#247)
- [whatwg/dom] input.toggle for checkbox, radios (#246)
- Re: [w3c/webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432)
- Re: [w3c/webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [whatwg/dom] "event . cancelable Returns true or false depend..." (#226)
- Re: [whatwg/dom] Rename scoped to composed and invert its meaning (#244)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [whatwg/dom] Rename scoped to composed and invert its meaning (#244)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3ctag/spec-reviews] relative URLs are not updated pushState() (#118)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/manifest] Chore(extensions): add link to registry (closes #452) (#458)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] add a script for auto-publication (#498)
- [w3c/webcomponents] add a script for auto-publication (#498)
Monday, 9 May 2016
- Re: [w3ctag/spec-reviews] relative URLs are not updated pushState() (#118)
- [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893)
- [w3ctag/spec-reviews] relative URLs are not updated pushState() (#118)
- [slightlyoff/ServiceWorker] potential http cache issues with importScripts() (#894)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444)
- Re: [w3c/manifest] Chore(extensions): add link to registry (closes #452) (#458)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444)
- Re: [whatwg/dom] Better way to maintain this reference on event listener functions (#245)
- Re: [whatwg/dom] Better way to maintain this reference on event listener functions (#245)
- Re: [whatwg/fetch] Use integrity hash as cache identifier (#301)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891)
- Re: [whatwg/fetch] Use integrity hash as cache identifier (#301)
- Re: [whatwg/dom] Better way to maintain this reference on event listener functions (#245)
- Re: [whatwg/streams] Update reference implementation for Node v6 (#445)
- [whatwg/fetch] Use integrity hash as cache identifier (#301)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/editing] [Input Events] Word deletion (#125)
- Re: [w3c/editing] [Input Events] Rename "replaceContent" with "insertContent" or "insertNonText" (#126)
- Re: [w3c/editing] [beforeinput] Should we allow canceling the committed text from IME? (#128)
- Re: [whatwg/dom] Owned weak event listener to prevent memory leak (using EventListenerOptions) (#243)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/dom] Owned weak event listener to prevent memory leak (using EventListenerOptions) (#243)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- [whatwg/url] Make it clearer that just about anything is parseable, probably via some examples (#119)
- [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/dom] Better way to maintain this reference on event listener functions (#245)
- Re: [whatwg/dom] Removing event listeners through an identifier (#208)
- Re: [whatwg/dom] Owned weak event listener to prevent memory leak (using EventListenerOptions) (#243)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Better way to maintain this reference on event listener functions (#245)
- Re: [whatwg/dom] Better way to maintain this reference on event listener functions (#245)
- Re: [whatwg/dom] Better way to maintain this reference on event listener functions (#245)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- [whatwg/dom] Better way to maintain this reference on event listener functions (#245)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Removing event listeners through an identifier (#208)
- [whatwg/dom] Rename scoped to composed and invert its meaning (#244)
- Re: [whatwg/dom] Removing event listeners through an identifier (#208)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Owned weak event listener to prevent memory leak (using EventListenerOptions) (#243)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465)
- [whatwg/dom] Owned weak event listener to prevent memory leak (using EventListenerOptions) (#243)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444)
Sunday, 8 May 2016
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497)
- [w3c/DOM-Parsing] Scripting flag and behaviour for noscript (#7)
- Re: [whatwg/streams] pipeTo should return a cancelable promise (#446)
- Re: [whatwg/streams] pipeTo should return a cancelable promise (#446)
- [whatwg/streams] pipeTo should return a cancelable promise (#446)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497)
Saturday, 7 May 2016
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [whatwg/fetch] TypeError new Headers(obj) (#300)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [whatwg/fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [whatwg/fetch] Add timeout option (#20)
- [slightlyoff/ServiceWorker] Never fail for navigation requests (#892)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891)
- Re: [w3c/manifest] Chore(extensions): add link to registry (closes #452) (#458)
- Re: [w3c/gamepad] Should spec a buffering/refresh interval model of gamepad data? (#22)
- Re: [whatwg/fetch] TypeError new Headers(obj) (#300)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497)
- Re: [whatwg/fetch] TypeError new Headers(obj) (#300)
- Re: [whatwg/fetch] TypeError new Headers(obj) (#300)
- [whatwg/fetch] TypeError new Headers(obj) (#300)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497)
- [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497)
Friday, 6 May 2016
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466)
- Re: [w3c/manifest] Chore(extensions): add link to registry (closes #452) (#458)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/encoding] Convert to bikeshed. (#48)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- [whatwg/encoding] Convert to bikeshed. (#48)
- Re: [whatwg/encoding] Convert to bikeshed. (#48)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- [heycam/webidl] Use CreateDataProperty where possible. (#117)
- Re: [heycam/webidl] Update links to ES2017. (#114)
- Re: [heycam/webidl] Update links to ES2017. (#114)
- Re: [heycam/webidl] Update links to ES2017. (#114)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] Provide more information in the spec on how withCredentials and Access-Control-Allow-Credentials interact (#264)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496)
- [WICG/directory-upload] Security issue of directory upload: pretend to download when actaully to upload a directory (#38)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496)
- [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496)
Thursday, 5 May 2016
- [heycam/webidl] Document that NotAllowedError should be used for denied permissions. (#116)
- Re: [w3c/IndexedDB] boolean should be a valid key (#76)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- [heycam/webidl] FrozenArray<dictionary>? (#115)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466)
- Re: [w3c/IndexedDB] Consider introducing "unbounded range" API (#13)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [w3c/IndexedDB] boolean should be a valid key (#76)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [w3c/IndexedDB] Consider introducing "unbounded range" API (#13)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/dom] Event delegation via EventListenerOptions (#215)
- Re: [whatwg/dom] Event delegation via EventListenerOptions (#215)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] Add more CORS protocol examples (#296)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [w3c/gamepad] Should spec a buffering/refresh interval model of gamepad data? (#22)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] Add CORS protocol examples (#297)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [w3c/webcomponents] document.currentScript from a script in a shadow tree. (#477)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/fetch] Add CORS protocol examples (#297)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- [w3c/manifest] short_name to fall back to name & vice versa (#466)
- Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299)
- Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299)
- Re: [whatwg/fetch] OpenEndedDictionary clarification (#164)
- Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299)
- [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- [whatwg/fetch] More wildcards in CORS when used without credentials (#298)
- Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [w3c/webcomponents] Shadow DOM Cascade Order (#316)
- [whatwg/fetch] Add CORS protocol examples (#297)
- Re: [whatwg/fetch] Add CORS protocol examples (#297)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [whatwg/fetch] Provide more information in the spec on how withCredentials and Access-Control-Allow-Credentials interact (#264)
- Re: [w3ctag/spec-reviews] Cross-spec device identification & association (#64)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- [whatwg/fetch] Add more CORS protocol examples (#296)
- Re: [w3ctag/spec-reviews] Cross-spec device identification & association (#64)
- Re: [w3c/webcomponents] Umbrella bugs for shadow DOM related issues in other specifications for v1 API (#495)
- [w3c/filesystem-api] Provide a API to monitor file/directory change (#7)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/fetch] OpenEndedDictionary clarification (#164)
- Re: [whatwg/fetch] Tight coupling between JS engine and browser engine (#263)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/fetch] OpenEndedDictionary clarification (#164)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/fetch] Tight coupling between JS engine and browser engine (#263)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [w3c/gamepad] Should spec a buffering/refresh interval model of gamepad data? (#22)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [w3c/webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80)
- [w3c/webcomponents] Umbrella bugs for shadow DOM related issues in other specifications for v1 API (#495)
- Re: [w3c/webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80)
- Re: [w3c/webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80)
- Re: [w3c/webcomponents] "::slotted" pseudo elements (#331)
- Re: [w3c/webcomponents] Shadow DOM Cascade Order (#316)
- Re: [w3c/webcomponents] "::slotted" pseudo elements (#331)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [w3c/webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80)
- Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252)
- Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252)
- Re: [whatwg/fetch] Add new Access-Control-Suppress-Headers CORS response header (#253)
Wednesday, 4 May 2016
- Re: [w3ctag/spec-reviews] Cross-spec device identification & association (#64)
- Re: [w3ctag/spec-reviews] Cross-spec device identification & association (#64)
- Re: [w3ctag/spec-reviews] requestIdleCallback (#70)
- Re: [w3ctag/spec-reviews] Cross-spec device identification & association (#64)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242)
- Re: [whatwg/fetch] Merge HTML5 and Fetch definitions of 'HTTPS state' (#241)
- Re: [w3c/webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80)
- Re: [w3c/webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [w3c/DOM-Parsing] insertAdjacentHTML is broken (#4)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891)
- Re: [w3c/DOM-Parsing] insertAdjacentHTML is broken (#4)
- [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891)
- Re: [heycam/webidl] Update links to ES2017. (#114)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891)
- Re: [w3c/DOM-Parsing] insertAdjacentHTML is broken (#4)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27)
- Re: [w3c/charter-html] Deliverables (55977a8)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278)
- [w3c/push-api] Note that the subscription shares fate with the registration (#191)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278)
- Re: [w3c/push-api] Clarify when to unsubscribe if the service worker is unregistered (#190)
- Re: [heycam/webidl] Update links to ES2017. (#114)
- Re: [w3c/permissions] Requesting permissions needs to be able to ask for multiple things (#92)
- [whatwg/fetch] Add "only-if-cached" cache mode back (#295)
- Re: [whatwg/fetch] Editorial: make an HTTPS state value its own thing (#294)
- Re: [whatwg/fetch] Editorial: make an HTTPS state value its own thing (#294)
- Re: [whatwg/fetch] Editorial: make an HTTPS state value its own thing (#294)
- [whatwg/fetch] Editorial: make an HTTPS state value its own thing (#294)
- Re: [whatwg/fetch] OpenEndedDictionary clarification (#164)
- Re: [whatwg/fetch] Add a way to copy Requests with a different URL (#191)
- Re: [whatwg/fetch] Only-if-cached (#159)
- Re: [w3c/permissions] Requesting permissions needs to be able to ask for multiple things (#92)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854)
- Re: [whatwg/fetch] Preserve fragment in Request/Response URLs (#214)
- Re: [whatwg/fetch] Give user entered data: URI documents the HTTPS state 'modern' (#243)
- Re: [whatwg/fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245)
- Re: [w3c/permissions] Requesting permissions needs to be able to ask for multiple things (#92)
- Re: [whatwg/fetch] Tight coupling between JS engine and browser engine (#263)
- Re: [w3c/permissions] Requesting permissions needs to be able to ask for multiple things (#92)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278)
- Re: [whatwg/fetch] need setHeaderFunction( request => newHeaders ) function called before request sent (#156)
- Re: [whatwg/fetch] Allow operation to outlive the document unloading (beacon) (#124)
- Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204)
- Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204)
- Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204)
- Re: [heycam/webidl] Modernize invoking user code (#113)
- Re: [w3c/permissions] Define an algorithm to update the permission storage. (#91)
- Re: [heycam/webidl] Update links to ES2017. (#114)
- [heycam/webidl] Update links to ES2017. (#114)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27)
- Re: [whatwg/fetch] "There is a cache match for request if origin is..." (#281)
- Re: [whatwg/fetch] Editorial: clarify cache match conditions (#291)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [whatwg/fetch] Clarify why request's url field exists (#292)
- Re: [whatwg/fetch] How does request url differ from url list and current url? (#275)
- Re: [whatwg/fetch] Clarify why request's url field exists (#292)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [w3c/push-api] Clarify when to unsubscribe if the service worker is unregistered (#190)
- Re: [w3c/push-api] Expose PushSubscriptionOptions value on PushSubscription (#184)
- Re: [w3c/push-api] Expose PushSubscriptionOptions value on PushSubscription (#184)
- Re: [w3c/push-api] Can you change the value of PushSubscriptionOptions (#183)
- Re: [w3c/push-api] Can you change the value of PushSubscriptionOptions (#183)
- Re: [w3c/push-api] Provide support for subscription association (#182)
- Re: [slightlyoff/ServiceWorker] "javascript global environment" and related terms were removed from HTML (#832)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851)
- Re: [whatwg/fetch] Editorial: clarify cache match conditions (#291)
- [w3c/push-api] Clarify when to unsubscribe if the service worker is unregistered (#190)
Tuesday, 3 May 2016
- [heycam/webidl] Modernize invoking user code (#113)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (3c18527)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- [whatwg/fetch] Explain CORS protocol and credentials interaction (#293)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/fetch] Allow setting `cookie` header in credential-less CORS requests (#268)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- [w3c/editing] [beforeinput] Should we allow canceling the committed text from IME? (#128)
- Re: [w3c/permissions] Requesting permissions needs to be able to ask for multiple things (#92)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/fetch] Clarify why request's url field exists (#292)
- Re: [whatwg/fetch] Clarify why request's url field exists (#292)
- Re: [whatwg/fetch] Allow setting `cookie` header in credential-less CORS requests (#268)
- Re: [whatwg/fetch] Clarify why request's url field exists (#292)
- [whatwg/fetch] Clarify why request's url field exists (#292)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/fetch] Add examples for PATCH and PatcH (or some such) (#260)
- Re: [whatwg/fetch] Add examples for PATCH and PatcH (or some such) (#260)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- [whatwg/fetch] Editorial: clarify cache match conditions (#291)
- Re: [whatwg/fetch] Editorial: clarify cache match conditions (#291)
- Re: [whatwg/fetch] Set the HTTPS state to 'modern' for more things (#290)
- Re: [w3ctag/spec-reviews] Payments Drafts Review (#109)
- Re: [w3ctag/spec-reviews] Payments Drafts Review (#109)
- Re: [whatwg/fullscreen] Consider adding Document.fullscreen property (#38)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242)
- [w3c/gamepad] `navigator.getGamepads()` should return a `Promise` (#23)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242)
- Re: [whatwg/storage] Feedback on the persist() algorithm. (#26)
Monday, 2 May 2016
- Re: [whatwg/encoding] index-jis0208.txt should be JIS X 0208 and add another index file (#47)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [w3c/permissions] Allow UAs to maintain zero or multiple permission stores. (#95)
- [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242)
- Re: [whatwg/encoding] index-jis0208.txt should be JIS X 0208 and add another index file (#47)
- [whatwg/encoding] index-jis0208.txt should be JIS X 0208 and add another index file (#47)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242)
- Re: [w3c/webcomponents] Update attachedCallback to connectedCallback. (#491)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486)
- [w3c/gamepad] Should spec a buffering/refresh interval model of gamepad data? (#22)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [heycam/webidl] Remove dictionary constructors (#109)
- Re: [heycam/webidl] Remove support for [Constructor] on dictionaries (fixes #109). (#111)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2)
- Re: [w3c/permissions] Allow UAs to maintain zero or multiple permission stores. (#95)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242)
- [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242)
- [w3c/IndexedDB] boolean should be a valid key (#76)
Sunday, 1 May 2016
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- [w3c/webcomponents] idea: clash-free auto-generated class naming. (#492)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Why allow shadow root style to access :host? (#490)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/dom] Comment out query/queryAll/Elements for now (10b6cf1)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [w3c/editing] [Input Events] Rename "replaceContent" with "insertContent" or "insertNonText" (#126)
- Re: [w3c/editing] [Input Events] Word deletion (#125)
- Re: [whatwg/dom] Comment out query/queryAll/Elements for now (10b6cf1)
- Re: [whatwg/dom] Comment out query/queryAll/Elements for now (10b6cf1)
- Re: [whatwg/storage] Feedback on the persist() algorithm. (#26)
- Re: [whatwg/fullscreen] Consider adding Document.fullscreen property (#38)
- [w3c/uievents] It is unclear whether beforeinput should be dispatched when input event is triggered because of mouse click (#87)
- Re: [whatwg/fullscreen] Consider adding Document.fullscreen property (#38)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)
- [whatwg/fullscreen] Consider adding Document.fullscreen property (#38)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)