=JeffH
Akash Goel
Alex Russell
alexelias
aliams
Andrea Giammarchi
Andrew Betts
Andrew Sutherland
Andrés
Andy Earnshaw
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Friday, 27 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Friday, 27 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Friday, 27 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Friday, 27 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Friday, 27 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Thursday, 26 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Thursday, 26 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Thursday, 26 May)
- [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Thursday, 26 May)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505) (Wednesday, 25 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
Anne van Kesteren
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258) (Tuesday, 31 May)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258) (Tuesday, 31 May)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258) (Tuesday, 31 May)
- Re: [whatwg/fetch] Grammar change: "that is check" to that checks" (#310) (Tuesday, 31 May)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258) (Tuesday, 31 May)
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#257) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Tuesday, 31 May)
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#257) (Tuesday, 31 May)
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#257) (Tuesday, 31 May)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Tuesday, 31 May)
- Re: [whatwg/dom] I don't think Element.insertAdjacentText can cause CEReactions (#255) (Tuesday, 31 May)
- Re: [whatwg/dom] I don't think Element.insertAdjacentText can cause CEReactions (#255) (Tuesday, 31 May)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207) (Tuesday, 31 May)
- Re: [w3ctag/spec-reviews] File URI Scheme (#59) (Tuesday, 31 May)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278) (Tuesday, 31 May)
- Re: [w3ctag/spec-reviews] File URI Scheme (#59) (Tuesday, 31 May)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207) (Monday, 30 May)
- Re: [whatwg/fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Monday, 30 May)
- Re: [whatwg/fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Monday, 30 May)
- Re: [whatwg/fetch] Body's total bytes for HEAD requests (#284) (Monday, 30 May)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278) (Monday, 30 May)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278) (Monday, 30 May)
- Re: [whatwg/fetch] Set the HTTPS state to 'modern' for more things (#290) (Monday, 30 May)
- Re: [whatwg/fetch] Set the HTTPS state to 'modern' for more things (#290) (Monday, 30 May)
- Re: [whatwg/fetch] Block redirects to non-HTTP schemes (#309) (Monday, 30 May)
- Re: [whatwg/fetch] Block redirects to non-HTTP schemes (#309) (Monday, 30 May)
- [whatwg/fetch] Block redirects to non-HTTP schemes (#309) (Monday, 30 May)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56) (Monday, 30 May)
- Re: [whatwg/dom] Markup "synthetic events" term as a proper <dfn> (#254) (Monday, 30 May)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56) (Monday, 30 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Sunday, 29 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Sunday, 29 May)
- Re: [whatwg/storage] Expose persist() to workers (#29) (Sunday, 29 May)
- Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41) (Saturday, 28 May)
- Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41) (Friday, 27 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 27 May)
- Re: [whatwg/storage] Expose persist() to workers (#29) (Friday, 27 May)
- Re: [whatwg/url] Consider always escaping U+0020 (#125) (Friday, 27 May)
- Re: [slightlyoff/ServiceWorker] Service workers registration lifetime (#903) (Friday, 27 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Friday, 27 May)
- Re: [whatwg/fetch] Only-if-cached (#159) (Friday, 27 May)
- Re: [whatwg/fetch] Only-if-cached (#159) (Friday, 27 May)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Friday, 27 May)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Friday, 27 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Thursday, 26 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Thursday, 26 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 26 May)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486) (Thursday, 26 May)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Thursday, 26 May)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Thursday, 26 May)
- Re: [whatwg/url] javascript: URL should not be able to be base URLs (#124) (Thursday, 26 May)
- Re: [whatwg/fetch] Only-if-cached (#159) (Thursday, 26 May)
- Re: [whatwg/fetch] Only-if-cached (#159) (Thursday, 26 May)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505) (Wednesday, 25 May)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- Re: [whatwg/url] Section 3 (Hosts) should be non-normative (#122) (Wednesday, 25 May)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505) (Wednesday, 25 May)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505) (Wednesday, 25 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Tuesday, 24 May)
- Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252) (Tuesday, 24 May)
- Re: [whatwg/fetch] Allow * for Access-Control-Allow-Headers and Access-Control-Allow-Methods (#251) (Tuesday, 24 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Tuesday, 24 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Tuesday, 24 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Tuesday, 24 May)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505) (Tuesday, 24 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 24 May)
- [whatwg/fetch] Vary HTTP cache on credentials mode (#307) (Friday, 20 May)
- Re: [whatwg/dom] Use USVString for URLs and origins in IDL (#252) (Friday, 20 May)
- Re: [whatwg/dom] Use USVString for URLs and origins in IDL (#252) (Friday, 20 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 19 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 19 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 19 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 19 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Thursday, 19 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 19 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Thursday, 19 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Thursday, 19 May)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123) (Thursday, 19 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Thursday, 19 May)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123) (Thursday, 19 May)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123) (Thursday, 19 May)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295) (Wednesday, 18 May)
- Re: [whatwg/fetch] update reference to referrer policy spec (#305) (Wednesday, 18 May)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295) (Wednesday, 18 May)
- Re: [whatwg/fetch] update reference to referrer policy spec (#305) (Wednesday, 18 May)
- Re: [whatwg/fetch] Only-if-cached (#159) (Wednesday, 18 May)
- Re: [whatwg/xhr] what is the problem (#70) (Wednesday, 18 May)
- Re: [whatwg/xhr] what is the problem (#70) (Wednesday, 18 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Wednesday, 18 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Wednesday, 18 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Wednesday, 18 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Wednesday, 18 May)
- Re: [whatwg/url] incorrect definition of ASCII hex digits (#121) (Wednesday, 18 May)
- Re: [whatwg/url] incorrect definition of ASCII hex digits (#121) (Wednesday, 18 May)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899) (Wednesday, 18 May)
- Re: [whatwg/storage] Fix typo to 'conservative' (#28) (Tuesday, 17 May)
- Re: [whatwg/storage] Fix typo to 'conservative' (#28) (Tuesday, 17 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Tuesday, 17 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Tuesday, 17 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Tuesday, 17 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Tuesday, 17 May)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899) (Tuesday, 17 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 16 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Monday, 16 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 16 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 16 May)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272) (Monday, 16 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Monday, 16 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Monday, 16 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Monday, 16 May)
- Re: [whatwg/fetch] Body's total bytes for HEAD requests (#284) (Monday, 16 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Monday, 16 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Monday, 16 May)
- Re: [whatwg/dom] toggleEventListener (#251) (Sunday, 15 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Sunday, 15 May)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96) (Friday, 13 May)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897) (Friday, 13 May)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897) (Friday, 13 May)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295) (Friday, 13 May)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295) (Friday, 13 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Friday, 13 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 13 May)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249) (Friday, 13 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 13 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 13 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Friday, 13 May)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96) (Friday, 13 May)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249) (Friday, 13 May)
- Re: [whatwg/url] Percent-encode 0x0D and 0x0A to "%0D%0A" in the application/x-www-form-urlencoded byte serializer? (#120) (Friday, 13 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 13 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Friday, 13 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Friday, 13 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Friday, 13 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Thursday, 12 May)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249) (Thursday, 12 May)
- Re: [whatwg/dom] surroundContents() with CharacterData node as newParent argument (#250) (Thursday, 12 May)
- Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Thursday, 12 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
- Re: [whatwg/dom] surroundContents() with CharacterData node as newParent argument (#250) (Thursday, 12 May)
- Re: [w3c/webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Thursday, 12 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 12 May)
- Re: [whatwg/dom] Shadow: define composedPath() (#247) (Thursday, 12 May)
- Re: [whatwg/url] Investigate aligning application/x-www-form-urlencoded with URL's query (#18) (Thursday, 12 May)
- Re: [whatwg/url] Investigate aligning application/x-www-form-urlencoded with URL's query (#18) (Thursday, 12 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 12 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Wednesday, 11 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Wednesday, 11 May)
- Re: [whatwg/dom] Shadow: define composedPath() (#247) (Wednesday, 11 May)
- Re: [whatwg/dom] Shadow: define composedPath() (#247) (Wednesday, 11 May)
- Re: [whatwg/dom] Rename rootNode to getRootNode() and add composed argument (#248) (Wednesday, 11 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Wednesday, 11 May)
- Re: [whatwg/fetch] Fetch should handle 'X-Frame-Options' (#302) (Wednesday, 11 May)
- Re: [whatwg/dom] Shadow: define composedPath() (#247) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [w3ctag/spec-reviews] TAG Review of HTML 5.1 (#119) (Wednesday, 11 May)
- Re: [whatwg/fetch] Fetch should handle 'X-Frame-Options' (#302) (Wednesday, 11 May)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249) (Wednesday, 11 May)
- Re: [whatwg/dom] Shadow: define composedPath() (#247) (Wednesday, 11 May)
- Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 10 May)
- Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 10 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Tuesday, 10 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Tuesday, 10 May)
- [whatwg/dom] Rename rootNode to getRootNode() and add composed argument (#248) (Tuesday, 10 May)
- Re: [whatwg/dom] input.toggle for checkbox, radios (#246) (Tuesday, 10 May)
- [whatwg/dom] Shadow: define composedPath() (#247) (Tuesday, 10 May)
- Re: [w3c/webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Tuesday, 10 May)
- Re: [w3c/webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Tuesday, 10 May)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465) (Tuesday, 10 May)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465) (Tuesday, 10 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 10 May)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465) (Tuesday, 10 May)
- Re: [whatwg/dom] "event . cancelable Returns true or false depend..." (#226) (Tuesday, 10 May)
- Re: [whatwg/dom] Rename scoped to composed and invert its meaning (#244) (Tuesday, 10 May)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465) (Tuesday, 10 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 10 May)
- Re: [w3ctag/spec-reviews] relative URLs are not updated pushState() (#118) (Tuesday, 10 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Tuesday, 10 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Tuesday, 10 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Monday, 9 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Monday, 9 May)
- Re: [whatwg/fetch] Use integrity hash as cache identifier (#301) (Monday, 9 May)
- Re: [whatwg/fetch] Use integrity hash as cache identifier (#301) (Monday, 9 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Monday, 9 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Monday, 9 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Monday, 9 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Monday, 9 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Monday, 9 May)
- Re: [whatwg/dom] Better way to maintain this reference on event listener functions (#245) (Monday, 9 May)
- Re: [whatwg/dom] Better way to maintain this reference on event listener functions (#245) (Monday, 9 May)
- Re: [whatwg/dom] Better way to maintain this reference on event listener functions (#245) (Monday, 9 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 9 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 9 May)
- Re: [whatwg/dom] Removing event listeners through an identifier (#208) (Monday, 9 May)
- [whatwg/dom] Rename scoped to composed and invert its meaning (#244) (Monday, 9 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 9 May)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465) (Monday, 9 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Friday, 6 May)
- Re: [whatwg/fetch] Add more CORS protocol examples (#296) (Thursday, 5 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Thursday, 5 May)
- Re: [whatwg/fetch] Add CORS protocol examples (#297) (Thursday, 5 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299) (Thursday, 5 May)
- Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299) (Thursday, 5 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Thursday, 5 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Thursday, 5 May)
- [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Thursday, 5 May)
- Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252) (Thursday, 5 May)
- [whatwg/fetch] Add CORS protocol examples (#297) (Thursday, 5 May)
- Re: [whatwg/fetch] Add CORS protocol examples (#297) (Thursday, 5 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Thursday, 5 May)
- Re: [whatwg/fetch] Provide more information in the spec on how withCredentials and Access-Control-Allow-Credentials interact (#264) (Thursday, 5 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Thursday, 5 May)
- [whatwg/fetch] Add more CORS protocol examples (#296) (Thursday, 5 May)
- Re: [w3c/webcomponents] Umbrella bugs for shadow DOM related issues in other specifications for v1 API (#495) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/fetch] OpenEndedDictionary clarification (#164) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27) (Wednesday, 4 May)
- Re: [w3c/DOM-Parsing] insertAdjacentHTML is broken (#4) (Wednesday, 4 May)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27) (Wednesday, 4 May)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 4 May)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278) (Wednesday, 4 May)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295) (Wednesday, 4 May)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 4 May)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278) (Wednesday, 4 May)
- [whatwg/fetch] Add "only-if-cached" cache mode back (#295) (Wednesday, 4 May)
- Re: [whatwg/fetch] Editorial: make an HTTPS state value its own thing (#294) (Wednesday, 4 May)
- Re: [whatwg/fetch] Editorial: make an HTTPS state value its own thing (#294) (Wednesday, 4 May)
- [whatwg/fetch] Editorial: make an HTTPS state value its own thing (#294) (Wednesday, 4 May)
- Re: [whatwg/fetch] OpenEndedDictionary clarification (#164) (Wednesday, 4 May)
- Re: [whatwg/fetch] Add a way to copy Requests with a different URL (#191) (Wednesday, 4 May)
- Re: [whatwg/fetch] Only-if-cached (#159) (Wednesday, 4 May)
- Re: [w3c/permissions] Requesting permissions needs to be able to ask for multiple things (#92) (Wednesday, 4 May)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 4 May)
- Re: [whatwg/fetch] Preserve fragment in Request/Response URLs (#214) (Wednesday, 4 May)
- Re: [whatwg/fetch] Give user entered data: URI documents the HTTPS state 'modern' (#243) (Wednesday, 4 May)
- Re: [whatwg/fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Wednesday, 4 May)
- Re: [whatwg/fetch] Tight coupling between JS engine and browser engine (#263) (Wednesday, 4 May)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278) (Wednesday, 4 May)
- Re: [whatwg/fetch] need setHeaderFunction( request => newHeaders ) function called before request sent (#156) (Wednesday, 4 May)
- Re: [whatwg/fetch] Allow operation to outlive the document unloading (beacon) (#124) (Wednesday, 4 May)
- Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204) (Wednesday, 4 May)
- Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204) (Wednesday, 4 May)
- Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204) (Wednesday, 4 May)
- Re: [heycam/webidl] Update links to ES2017. (#114) (Wednesday, 4 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Wednesday, 4 May)
- Re: [whatwg/fetch] "There is a cache match for request if origin is..." (#281) (Wednesday, 4 May)
- Re: [whatwg/fetch] Editorial: clarify cache match conditions (#291) (Wednesday, 4 May)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27) (Wednesday, 4 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Wednesday, 4 May)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27) (Wednesday, 4 May)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Wednesday, 4 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Wednesday, 4 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Wednesday, 4 May)
- Re: [whatwg/fetch] Clarify why request's url field exists (#292) (Wednesday, 4 May)
- Re: [whatwg/fetch] How does request url differ from url list and current url? (#275) (Wednesday, 4 May)
- Re: [whatwg/fetch] Clarify why request's url field exists (#292) (Wednesday, 4 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Wednesday, 4 May)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27) (Wednesday, 4 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Tuesday, 3 May)
- [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Tuesday, 3 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Tuesday, 3 May)
- Re: [whatwg/fetch] Allow setting `cookie` header in credential-less CORS requests (#268) (Tuesday, 3 May)
- Re: [whatwg/fetch] Clarify why request's url field exists (#292) (Tuesday, 3 May)
- [whatwg/fetch] Clarify why request's url field exists (#292) (Tuesday, 3 May)
- Re: [whatwg/fetch] Add examples for PATCH and PatcH (or some such) (#260) (Tuesday, 3 May)
- Re: [whatwg/fetch] Add examples for PATCH and PatcH (or some such) (#260) (Tuesday, 3 May)
- [whatwg/fetch] Editorial: clarify cache match conditions (#291) (Tuesday, 3 May)
- Re: [whatwg/fetch] Editorial: clarify cache match conditions (#291) (Tuesday, 3 May)
- Re: [whatwg/fullscreen] Consider adding Document.fullscreen property (#38) (Tuesday, 3 May)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2) (Tuesday, 3 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242) (Tuesday, 3 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242) (Tuesday, 3 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242) (Tuesday, 3 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Monday, 2 May)
- Re: [whatwg/encoding] index-jis0208.txt should be JIS X 0208 and add another index file (#47) (Monday, 2 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242) (Monday, 2 May)
- Re: [w3c/webcomponents] Update attachedCallback to connectedCallback. (#491) (Monday, 2 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Monday, 2 May)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486) (Monday, 2 May)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2) (Monday, 2 May)
- Re: [w3c/permissions] Allow UAs to maintain zero or multiple permission stores. (#95) (Monday, 2 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242) (Monday, 2 May)
- Re: [whatwg/dom] Comment out query/queryAll/Elements for now (10b6cf1) (Sunday, 1 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Sunday, 1 May)
- Re: [whatwg/storage] Feedback on the persist() algorithm. (#26) (Sunday, 1 May)
- Re: [whatwg/fullscreen] Consider adding Document.fullscreen property (#38) (Sunday, 1 May)
Anthony Ramine
ArkadiuszMichalski
Arthur Stolyar
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Sunday, 29 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 9 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 9 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891) (Saturday, 7 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Tuesday, 3 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Tuesday, 3 May)
Aryeh Gregor
Balazs Kelemen
bashi
beidson
Ben Francis
Ben Kelly
- Re: [slightlyoff/ServiceWorker] Service workers registration lifetime (#903) (Sunday, 29 May)
- [slightlyoff/ServiceWorker] should UA check for updates on navigate when there is no fetch event? (#905) (Saturday, 28 May)
- Re: [slightlyoff/ServiceWorker] Service workers registration lifetime (#903) (Friday, 27 May)
- Re: [slightlyoff/ServiceWorker] what is the best way to save Request while offline ? (#904) (Friday, 27 May)
- [w3c/WebPlatformWG] Create page for July 28-29 service worker meeting. (#35) (Thursday, 26 May)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453) (Thursday, 26 May)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453) (Wednesday, 25 May)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453) (Wednesday, 25 May)
- [whatwg/streams] should ReadableStreamClose() resolve BYOB reader readIntoRequests? (#455) (Wednesday, 25 May)
- [whatwg/streams] ReadableStreamAddReadRequest() should assert state is readable (#454) (Wednesday, 25 May)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453) (Wednesday, 25 May)
- [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453) (Wednesday, 25 May)
- [whatwg/streams] ReadableStreamCancel() should assert IsReadableStream(stream) (#452) (Wednesday, 25 May)
- [whatwg/streams] PromiseInvokeOrNoop is not linked (#451) (Wednesday, 25 May)
- [whatwg/streams] ReadableStreamTee returns undefined `branch1` and `branch2` (#449) (Monday, 23 May)
- Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902) (Monday, 23 May)
- Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902) (Monday, 23 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Monday, 23 May)
- Re: [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308) (Saturday, 21 May)
- [whatwg/url] Section 3 (Hosts) should be non-normative (#122) (Friday, 20 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 19 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Tuesday, 17 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 16 May)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272) (Monday, 16 May)
- Re: [whatwg/xhr] Consider setting omit-Origin-header-flag for same origin requests (#31) (Monday, 16 May)
- [whatwg/streams] new ReadableStream() header specifies default highWaterMark=1 (#447) (Friday, 13 May)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272) (Thursday, 12 May)
- Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 10 May)
- Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 10 May)
- [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 10 May)
- [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Monday, 9 May)
- [slightlyoff/ServiceWorker] potential http cache issues with importScripts() (#894) (Monday, 9 May)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [whatwg/fetch] TypeError new Headers(obj) (#300) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891) (Wednesday, 4 May)
- [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891) (Wednesday, 4 May)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 4 May)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278) (Wednesday, 4 May)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 4 May)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278) (Wednesday, 4 May)
- Re: [w3c/push-api] Clarify when to unsubscribe if the service worker is unregistered (#190) (Wednesday, 4 May)
- Re: [whatwg/fetch] Clarify why request's url field exists (#292) (Tuesday, 3 May)
- Re: [whatwg/fetch] Clarify why request's url field exists (#292) (Tuesday, 3 May)
Ben Page
Ben Tian
Bevis Tseng
Boris Zbarsky
- Re: [whatwg/xhr] abort() handling of state is busted (#54) (Friday, 27 May)
- Re: [whatwg/xhr] abort() handling of state is busted (#54) (Wednesday, 25 May)
- Re: [heycam/webidl] "Restricted" Float32Array (#126) (Monday, 23 May)
- Re: [heycam/webidl] "Restricted" Float32Array (#126) (Monday, 23 May)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125) (Saturday, 21 May)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125) (Friday, 20 May)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125) (Friday, 20 May)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125) (Friday, 20 May)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125) (Friday, 20 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 20 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 20 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 20 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 20 May)
- Re: [heycam/webidl] Clarify whether a dictionary member set to `undefined` is "present" (#124) (Friday, 20 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 19 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Thursday, 19 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 19 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 19 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Thursday, 19 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Thursday, 19 May)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123) (Thursday, 19 May)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123) (Thursday, 19 May)
- Re: [heycam/webidl] Conversion for (SomeDictionary or sequence<T>) seems incorrect (#123) (Thursday, 19 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Thursday, 19 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 18 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 18 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 18 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 18 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 18 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Wednesday, 18 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Wednesday, 18 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Wednesday, 18 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Tuesday, 10 May)
- [heycam/webidl] What is the expected interaction of [SecureContext] with mixins? (#118) (Tuesday, 10 May)
- Re: [w3c/DOM-Parsing] Sort out what's happening with innerHTML on <script> and <style> in XML documents (#6) (Tuesday, 10 May)
- Re: [w3c/DOM-Parsing] Sort out what's happening with innerHTML on <script> and <style> in XML documents (#6) (Tuesday, 10 May)
- Re: [w3c/DOM-Parsing] Sort out what's happening with innerHTML on <script> and <style> in XML documents (#6) (Tuesday, 10 May)
- Re: [whatwg/fetch] OpenEndedDictionary clarification (#164) (Thursday, 5 May)
BronislavKlucka
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505) (Wednesday, 25 May)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505) (Wednesday, 25 May)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505) (Wednesday, 25 May)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) (Monday, 23 May)
- [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505) (Monday, 23 May)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) (Monday, 23 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Saturday, 14 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
Burak Tamtürk
Cameron McCormack
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249) (Friday, 13 May)
- Re: [heycam/webidl] Use CreateDataProperty where possible. (#117) (Wednesday, 11 May)
- Re: [heycam/webidl] Need an error for "User refused permission" (#95) (Wednesday, 11 May)
- Re: [heycam/webidl] Document that NotAllowedError should be used for denied permissions. (#116) (Wednesday, 11 May)
- Re: [heycam/webidl] Use CreateDataProperty where possible. (#117) (Wednesday, 11 May)
- Re: [heycam/webidl] Update links to ES2017. (#114) (Friday, 6 May)
- Re: [heycam/webidl] Update links to ES2017. (#114) (Friday, 6 May)
- Re: [whatwg/fetch] OpenEndedDictionary clarification (#164) (Thursday, 5 May)
- Re: [heycam/webidl] Remove dictionary constructors (#109) (Monday, 2 May)
- Re: [heycam/webidl] Remove support for [Constructor] on dictionaries (fixes #109). (#111) (Monday, 2 May)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2) (Monday, 2 May)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2) (Monday, 2 May)
- Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2) (Monday, 2 May)
chaals
Chong Zhang
Chris Rebert
chris van wiemeersch
Cory Benfield
cyns
Cyril Auburtin
Dale Harvey
Daniel Appelquist
Daniel Stenberg
Daniel Veditz
Dave Methvin
Dave Tapuska
David Fahlander
David Håsäther
ddorwin
Denis Ah-Kang
Dexter
Dimitri Glazkov
Domenic Denicola
- [whatwg/dom] Un-customify adopted elements (#260) (Tuesday, 31 May)
- Re: [whatwg/dom] Don't set custom element state redundantly (#253) (Tuesday, 31 May)
- Re: [whatwg/dom] Don't set custom element state redundantly (#253) (Tuesday, 31 May)
- Re: [whatwg/streams] light weight transformations (#461) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 31 May)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258) (Tuesday, 31 May)
- [whatwg/dom] Why can't Node's nodeValue use [TreatNullAs=EmptyString]? (#259) (Tuesday, 31 May)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258) (Tuesday, 31 May)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258) (Tuesday, 31 May)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258) (Tuesday, 31 May)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56) (Monday, 30 May)
- Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56) (Monday, 30 May)
- Re: [w3c/screen-orientation] Move the HTML specification monkey patching to the HTML specification (#69) (Friday, 27 May)
- Re: [whatwg/streams] Consider adding type assertions for all abstract operations (#453) (Friday, 27 May)
- Re: [whatwg/streams] ReadableStreamCancel() should assert IsReadableStream(stream) (#452) (Friday, 27 May)
- Re: [whatwg/streams] ReadableStreamCancel() should assert IsReadableStream(stream) (#452) (Friday, 27 May)
- Re: [whatwg/streams] Add an assert on stream's state in ReadableStreamAddReadRequest() (#458) (Friday, 27 May)
- Re: [whatwg/streams] ReadableStreamAddReadRequest() should assert state is readable (#454) (Friday, 27 May)
- Re: [whatwg/streams] Move assertion on stream from ReadableStreamCancel() to its callers (#459) (Friday, 27 May)
- Re: [whatwg/streams] Update wpt-runner dependency to require 1.0.1 or later (#456) (Friday, 27 May)
- Re: [whatwg/streams] Update wpt-runner dependency to require 1.0.1 or later (#456) (Friday, 27 May)
- Re: [whatwg/streams] PromiseInvokeOrNoop is not autolinking (#450) (Friday, 27 May)
- Re: [whatwg/streams] Fix PromiseInvokeOrNoop autolinking (#460) (Friday, 27 May)
- Re: [whatwg/streams] Fix PromiseInvokeOrNoop autolinking (#460) (Friday, 27 May)
- Re: [whatwg/streams] Typo fix (#457) (Friday, 27 May)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453) (Wednesday, 25 May)
- Re: [whatwg/streams] ReadableStreamClose() should assert IsReadableStream(stream) (#453) (Wednesday, 25 May)
- Re: [whatwg/streams] PromiseInvokeOrNoop is not linked (#451) (Wednesday, 25 May)
- Re: [whatwg/streams] PromiseInvokeOrNoop is not linked (#451) (Wednesday, 25 May)
- [whatwg/streams] PromiseInvokeOrNoop is not autolinking (#450) (Wednesday, 25 May)
- Re: [w3c/webcomponents] customElements.define not working (#506) (Wednesday, 25 May)
- Re: [w3c/webcomponents] customElements.define not working (#506) (Wednesday, 25 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Wednesday, 25 May)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- Re: [whatwg/url] Clarify the informative nature of referenced RFCs (#123) (Wednesday, 25 May)
- Re: [w3c/FileAPI] Update Typed Array spec URL (#34) (Tuesday, 24 May)
- Re: [w3c/FileAPI] Update Typed Array spec URL (#34) (Tuesday, 24 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 24 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 24 May)
- Re: [whatwg/streams] ReadableStreamTee returns undefined `branch1` and `branch2` (#449) (Tuesday, 24 May)
- Re: [whatwg/streams] ReadableStreamTee returns undefined `branch1` and `branch2` (#449) (Tuesday, 24 May)
- [whatwg/dom] Don't set custom element state redundantly (#253) (Tuesday, 24 May)
- Re: [heycam/webidl] "Restricted" Float32Array (#126) (Monday, 23 May)
- Re: [w3c/webcomponents] Voting for/against proposals (#503) (Sunday, 22 May)
- Re: [w3c/webcomponents] Voting for/against proposals (#503) (Sunday, 22 May)
- Re: [w3c/webcomponents] Voting for/against proposals (#503) (Sunday, 22 May)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125) (Friday, 20 May)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125) (Friday, 20 May)
- [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125) (Friday, 20 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 20 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 20 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 20 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 20 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 19 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Thursday, 19 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 19 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 19 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Thursday, 19 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 19 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 19 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 19 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Thursday, 19 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Thursday, 19 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Thursday, 19 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Wednesday, 18 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Wednesday, 18 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Wednesday, 18 May)
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Wednesday, 18 May)
- Re: [w3c/webcomponents] Move respec-complement.css to custom and shadow (#502) (Tuesday, 17 May)
- Re: [w3c/webcomponents] add a script for auto-publication (#498) (Tuesday, 17 May)
- Re: [w3c/webcomponents] add a script for auto-publication (#498) (Tuesday, 17 May)
- [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Tuesday, 17 May)
- Re: [whatwg/fetch] Blob URLs should grab HTTPS state from Blob objects (#270) (Tuesday, 17 May)
- Re: [w3c/webcomponents] add a script for auto-publication (#498) (Monday, 16 May)
- Re: [w3c/webcomponents] Update attachedCallback to connectedCallback. (#491) (Monday, 16 May)
- Re: [whatwg/streams] Should consumers of readers/streams be notified why a stream was canceled? (#448) (Monday, 16 May)
- Re: [whatwg/dom] toggleEventListener (#251) (Sunday, 15 May)
- Re: [whatwg/streams] new ReadableStream() header specifies default highWaterMark=1 (#447) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [whatwg/dom] Provide greater visibility of `implements` relationships? (#249) (Friday, 13 May)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Friday, 13 May)
- Re: [heycam/webidl] Add namespaces (#121) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [w3c/webcomponents] Update attachedCallback to connectedCallback. (#491) (Thursday, 12 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Thursday, 12 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- [heycam/webidl] Add namespaces (#121) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Tuesday, 10 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Tuesday, 10 May)
- [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897) (Tuesday, 10 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Tuesday, 10 May)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444) (Monday, 9 May)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444) (Monday, 9 May)
- Re: [whatwg/dom] Better way to maintain this reference on event listener functions (#245) (Monday, 9 May)
- Re: [whatwg/streams] Update reference implementation for Node v6 (#445) (Monday, 9 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Monday, 9 May)
- [whatwg/url] Make it clearer that just about anything is parseable, probably via some examples (#119) (Monday, 9 May)
- [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Monday, 9 May)
- Re: [whatwg/streams] pipeTo should return a cancelable promise (#446) (Sunday, 8 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 6 May)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444) (Friday, 6 May)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444) (Friday, 6 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/fetch] Merge HTML5 and Fetch definitions of 'HTTPS state' (#241) (Wednesday, 4 May)
- Re: [heycam/webidl] Update links to ES2017. (#114) (Wednesday, 4 May)
- Re: [w3c/permissions] Requesting permissions needs to be able to ask for multiple things (#92) (Wednesday, 4 May)
- [heycam/webidl] Modernize invoking user code (#113) (Tuesday, 3 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Tuesday, 3 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Tuesday, 3 May)
- Re: [w3c/permissions] Requesting permissions needs to be able to ask for multiple things (#92) (Tuesday, 3 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Tuesday, 3 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 2 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 2 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242) (Monday, 2 May)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Sunday, 1 May)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Sunday, 1 May)
Dominic Cooney
Dominic Tarr
Duan Yao
Dylan Barrell
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Monday, 16 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Monday, 16 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Sunday, 15 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Saturday, 14 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [w3c/webcomponents] Expose ShadowRoot object's encapsulation mode (#275) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Thursday, 12 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Thursday, 5 May)
Ehsan Akhgari
Elliott Sprehn
Erik Isaksen
Erik Wilde
Fagner Brack
fvsch
Gary Kacmarcik
Geoffrey Sneddon
Gregory Wild-Smith
Hallvord R. M. Steen
Harald Alvestrand
Hasan Yousef
Hayato Ito
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#257) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486) (Tuesday, 31 May)
- [whatwg/dom] Shadow: Update the definition of an unclosed node (#257) (Tuesday, 31 May)
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#256) (Tuesday, 31 May)
- Re: [whatwg/dom] Shadow: Update the definition of an unclosed node (#256) (Tuesday, 31 May)
- [whatwg/dom] Shadow: Update the definition of an unclosed node (#256) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Friday, 27 May)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486) (Thursday, 26 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Thursday, 26 May)
- Re: [w3c/webcomponents] idea: clash-free auto-generated class naming. (#492) (Thursday, 26 May)
- Re: [w3c/webcomponents] idea: clash-free auto-generated class naming. (#492) (Thursday, 26 May)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Thursday, 26 May)
- Re: [w3c/webcomponents] How to detect when an element is transcluded into a shadow tree? (#504) (Thursday, 26 May)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486) (Thursday, 26 May)
- Re: [w3c/webcomponents] How to detect when an element is transcluded into a shadow tree? (#504) (Thursday, 26 May)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486) (Wednesday, 25 May)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505) (Wednesday, 25 May)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) (Friday, 20 May)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) (Thursday, 19 May)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) (Thursday, 19 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Wednesday, 18 May)
- Re: [whatwg/dom] Shadow: define composedPath() (#247) (Thursday, 12 May)
- Re: [whatwg/dom] Shadow: define composedPath() (#247) (Thursday, 12 May)
- Re: [whatwg/dom] Rename rootNode to getRootNode() and add composed argument (#248) (Thursday, 12 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Tuesday, 10 May)
- Re: [whatwg/dom] Rename scoped to composed and invert its meaning (#244) (Tuesday, 10 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Tuesday, 10 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Monday, 9 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Monday, 9 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Monday, 9 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 9 May)
Henri Sivonen
Hiroki Nakagawa
Honza Bambas
Ilya Grigorik
Ivan Nikulin
Jake Archibald
- Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902) (Sunday, 29 May)
- Re: [slightlyoff/ServiceWorker] Additional PositionOptions required for ServiceWorker background GeoLocation (#898) (Wednesday, 25 May)
- Re: [slightlyoff/ServiceWorker] Additional PositionOptions required for ServiceWorker background GeoLocation (#898) (Wednesday, 25 May)
- Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902) (Monday, 23 May)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468) (Wednesday, 18 May)
- Re: [slightlyoff/ServiceWorker] Fix Typo: "necessary" (#895) (Tuesday, 10 May)
- Re: [slightlyoff/ServiceWorker] Fix Typo: "necessary" (#895) (Tuesday, 10 May)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465) (Tuesday, 10 May)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465) (Tuesday, 10 May)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465) (Tuesday, 10 May)
- Re: [whatwg/streams] pipeTo should return a cancelable promise (#446) (Sunday, 8 May)
- [whatwg/streams] pipeTo should return a cancelable promise (#446) (Sunday, 8 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Saturday, 7 May)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466) (Friday, 6 May)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466) (Thursday, 5 May)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466) (Thursday, 5 May)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465) (Thursday, 5 May)
- [w3c/manifest] short_name to fall back to name & vice versa (#466) (Thursday, 5 May)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891) (Wednesday, 4 May)
jan-ivar
Janne Koschinski
Jasper St. Pierre
Jeff Burtoft
Jeffrey Yasskin
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Saturday, 28 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Wednesday, 25 May)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96) (Friday, 13 May)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96) (Thursday, 12 May)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96) (Thursday, 12 May)
- [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96) (Wednesday, 11 May)
- Re: [w3c/push-api] Refer to reusable definition of PermissionDeniedError once that becomes available (#107) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Tuesday, 10 May)
- [heycam/webidl] Document that NotAllowedError should be used for denied permissions. (#116) (Thursday, 5 May)
- [heycam/webidl] FrozenArray<dictionary>? (#115) (Thursday, 5 May)
- Re: [w3ctag/spec-reviews] Cross-spec device identification & association (#64) (Wednesday, 4 May)
Jesse McCarthy
jgraham
Joey Smith
Johannes Wilm
- Re: [w3c/editing] Should beforeFocus be another Edit Event? (#27) (Monday, 23 May)
- Re: [w3c/editing] Should beforeFocus be another Edit Event? (#27) (Monday, 23 May)
- 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) (Monday, 23 May)
- 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) (Monday, 23 May)
- Re: [w3c/editing] We could have "data" property that returns the text/plain version and a dataTransfer field for richer things. (#105) (Monday, 23 May)
- Re: [w3c/editing] We could have "data" property that returns the text/plain version and a dataTransfer field for richer things. (#105) (Monday, 23 May)
- Re: [w3c/editing] [Input Events] Word deletion (#125) (Monday, 23 May)
- Re: [w3c/editing] [Input Events] Word deletion (#125) (Monday, 23 May)
- Re: [w3c/editing] [Input Events] Rename "replaceContent" with "insertContent" or "insertNonText" (#126) (Monday, 23 May)
- Re: [w3c/editing] beforeinput: Should we fire `replaceContent` during IME composition? (#122) (Friday, 20 May)
- Re: [w3c/editing] beforeinput: Should we fire `replaceContent` during IME composition? (#122) (Friday, 20 May)
- Re: [w3c/editing] [Input Events] Word deletion (#125) (Friday, 20 May)
- Re: [w3c/editing] [Input Events] Word deletion (#125) (Friday, 20 May)
- Re: [w3c/editing] [Input Events] Word deletion (#125) (Monday, 9 May)
- Re: [w3c/editing] [Input Events] Rename "replaceContent" with "insertContent" or "insertNonText" (#126) (Monday, 9 May)
- Re: [w3c/editing] [beforeinput] Should we allow canceling the committed text from IME? (#128) (Monday, 9 May)
John M. Harris, Jr.
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Sunday, 15 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Sunday, 15 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Sunday, 15 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Sunday, 15 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Sunday, 15 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 12 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 12 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 11 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Tuesday, 10 May)
- Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Tuesday, 10 May)
Jonas Sicking
Jonathan Watt
- Re: [w3c/webcomponents] [Shadow] How should various document internal references work when SVG is being used in shadow DOM (bugzilla: 27380) (#179) (Friday, 13 May)
- Re: [WICG/directory-upload] HTMLInputElement.directory should be a Directory attribute and not a boolean (#31) (Friday, 13 May)
- Re: [WICG/directory-upload] Consider to remove HTMLInputElement.getFilesAndDirectories andHTMLInputElement.getFiles (#33) (Friday, 13 May)
- Re: [WICG/directory-upload] Easier way to get files without complicated asynchronous traversal code (#26) (Thursday, 12 May)
- Re: [WICG/directory-upload] Easier way to get files without complicated asynchronous traversal code (#26) (Thursday, 12 May)
- Re: [WICG/directory-upload] Leading slash in FormData filename field (#36) (Thursday, 12 May)
- Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Wednesday, 11 May)
- Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Wednesday, 11 May)
- [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Tuesday, 10 May)
- Re: [whatwg/fetch] Editorial: make an HTTPS state value its own thing (#294) (Wednesday, 4 May)
Joseph Orbegoso Pea
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 31 May)
- [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 31 May)
- [w3c/webcomponents] What happens in these slot/content scenarios? (#508) (Tuesday, 31 May)
- Re: [w3c/webcomponents] How to detect when an element is transcluded into a shadow tree? (#504) (Tuesday, 31 May)
- Re: [w3c/webcomponents] attachedCallback in light tree, but when transcluded into shadow tree? (#504) (Sunday, 22 May)
- Re: [w3c/webcomponents] attachedCallback in light tree, but when transcluded into shadow tree? (#504) (Sunday, 22 May)
- Re: [w3c/webcomponents] attachedCallback in light tree, but what about in shadow tree? (#504) (Sunday, 22 May)
- [w3c/webcomponents] attachedCallback in light tree, but what about in shadow tree? (#504) (Sunday, 22 May)
- [w3c/webcomponents] Voting for/against proposals (#503) (Sunday, 22 May)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Sunday, 1 May)
- [w3c/webcomponents] idea: clash-free auto-generated class naming. (#492) (Sunday, 1 May)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Sunday, 1 May)
- Re: [w3c/webcomponents] Why allow shadow root style to access :host? (#490) (Sunday, 1 May)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Sunday, 1 May)
Josh Matthews
Joshua Bell
- Re: [w3c/IndexedDB] Integrate with window.onerror (#49) (Tuesday, 31 May)
- [w3c/WebPlatformWG] Add self to attendees list (#34) (Wednesday, 25 May)
- [w3c/IndexedDB] Enforce transaction commit ordering more strictly (#77) (Tuesday, 24 May)
- Re: [w3c/IndexedDB] Support N-dimensional queries on indexes (#40) (Thursday, 19 May)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891) (Monday, 9 May)
- Re: [whatwg/encoding] Convert to bikeshed. (#48) (Friday, 6 May)
- Re: [w3c/IndexedDB] Consider introducing "unbounded range" API (#13) (Thursday, 5 May)
- Re: [w3c/IndexedDB] boolean should be a valid key (#76) (Thursday, 5 May)
- Re: [w3c/IndexedDB] Consider introducing "unbounded range" API (#13) (Thursday, 5 May)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891) (Wednesday, 4 May)
- Re: [whatwg/storage] Should navigator.storage.estimate() be available on insecure contexts? (#27) (Wednesday, 4 May)
Joshua Nelson
jplaisted
juj
Jungkee Song
- Re: [slightlyoff/ServiceWorker] Service workers registration lifetime (#903) (Friday, 27 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Friday, 27 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Friday, 27 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 26 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Wednesday, 25 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 24 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 24 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 24 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 24 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 24 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Friday, 20 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 19 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 19 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 19 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 19 May)
- Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 19 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Monday, 16 May)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897) (Monday, 16 May)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897) (Monday, 16 May)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897) (Friday, 13 May)
- Re: [slightlyoff/ServiceWorker] Why are so many things [Unforgeable]? (#897) (Friday, 13 May)
- Re: [slightlyoff/ServiceWorker] Move service worker spec into w3c (#881) (Friday, 13 May)
- Re: [slightlyoff/ServiceWorker] caches.match() rejection on missing name is a footgun (#891) (Saturday, 7 May)
- Re: [slightlyoff/ServiceWorker] "javascript global environment" and related terms were removed from HTML (#832) (Wednesday, 4 May)
- Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Wednesday, 4 May)
Jxck
Keith Yeung
Kenji Baheux
Kit Cambridge
Koji Ishii
Kyaw Tun
Lewis Phạm
Liam
Luis Canales
Léonie Watson
Maciej Stachowiak
Majid Valipour
Marco Colli
Marcos Cáceres
- Re: [w3c/manifest] Ability to detect if the current document is part of an "installed" web app (#454) (Tuesday, 31 May)
- Re: [w3c/manifest] Ability to detect if the current document is part of an "installed" web app (#454) (Tuesday, 31 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Thursday, 26 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Thursday, 19 May)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465) (Thursday, 19 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Thursday, 19 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Wednesday, 18 May)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466) (Wednesday, 18 May)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468) (Wednesday, 18 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Wednesday, 18 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Wednesday, 18 May)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468) (Wednesday, 18 May)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468) (Wednesday, 18 May)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468) (Wednesday, 18 May)
- Re: [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468) (Wednesday, 18 May)
- [w3c/manifest] Feat(application's name): how to get the app's name (closes #466) (#468) (Wednesday, 18 May)
- Re: [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Wednesday, 18 May)
- [w3c/manifest] Feat(image object): set client to Document (closes #465) (#467) (Wednesday, 18 May)
- Re: [w3c/manifest] Include Minimal Store/Catalog MetaData in Manifest (#448) (Monday, 16 May)
- Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147) (Monday, 16 May)
- Re: [w3c/manifest] Chore(extensions): add link to registry (closes #452) (#458) (Tuesday, 10 May)
- Re: [w3c/manifest] Chore(extensions): add link to registry (closes #452) (#458) (Saturday, 7 May)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466) (Friday, 6 May)
- Re: [w3c/manifest] short_name to fall back to name & vice versa (#466) (Thursday, 5 May)
Marijn Kruisselbrink
- Re: [whatwg/fetch] Add referrer policy to blob-generated responses (#306) (Thursday, 19 May)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899) (Tuesday, 17 May)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and opaque origins (#900) (Monday, 16 May)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899) (Monday, 16 May)
- Re: [slightlyoff/ServiceWorker] Foreign fetch and opaque origins (#900) (Monday, 16 May)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272) (Monday, 16 May)
- [slightlyoff/ServiceWorker] Foreign fetch and opaque origins (#900) (Monday, 16 May)
- [slightlyoff/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899) (Monday, 16 May)
- Re: [slightlyoff/ServiceWorker] Move service worker spec into w3c (#881) (Friday, 13 May)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272) (Thursday, 12 May)
- Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272) (Thursday, 12 May)
Mark Kennedy
Mark Nottingham
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207) (Tuesday, 31 May)
- Re: [w3ctag/spec-reviews] File URI Scheme (#59) (Tuesday, 31 May)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207) (Tuesday, 31 May)
- Re: [w3ctag/spec-reviews] File URI Scheme (#59) (Tuesday, 31 May)
- Re: [whatwg/fetch] should fetch() allow no-cors cross-origin HEAD request? (#278) (Tuesday, 31 May)
- Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207) (Tuesday, 31 May)
- Re: [w3ctag/spec-reviews] File URI Scheme (#59) (Tuesday, 31 May)
- Re: [w3ctag/spec-reviews] First Party Cookies (#114) (Tuesday, 31 May)
- Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41) (Monday, 30 May)
- Re: [w3ctag/spec-reviews] Privacy Mode (#101) (Wednesday, 25 May)
- Re: [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308) (Saturday, 21 May)
- Re: [w3ctag/spec-reviews] CSP (#42) (Wednesday, 18 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Tuesday, 17 May)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295) (Tuesday, 17 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Tuesday, 17 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Tuesday, 17 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 16 May)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295) (Thursday, 12 May)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295) (Thursday, 12 May)
- Re: [whatwg/fetch] Add "only-if-cached" cache mode back (#295) (Thursday, 12 May)
- [w3ctag/spec-reviews] Performance API's, Security and Privacy (#120) (Thursday, 12 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Wednesday, 4 May)
- Re: [whatwg/fetch] Editorial: clarify cache match conditions (#291) (Wednesday, 4 May)
Mark Otaris
Martin Thomson
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Saturday, 28 May)
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Friday, 27 May)
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Tuesday, 24 May)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96) (Friday, 13 May)
- Re: [w3c/push-api] Note that the subscription shares fate with the registration (#191) (Thursday, 12 May)
- [w3c/push-api] Use NotAllowedError instead of defining a new PermissionDeniedError. … (#192) (Thursday, 12 May)
- [w3c/push-api] Note that the subscription shares fate with the registration (#191) (Wednesday, 4 May)
- Re: [w3c/push-api] Clarify when to unsubscribe if the service worker is unregistered (#190) (Wednesday, 4 May)
- Re: [w3c/push-api] Expose PushSubscriptionOptions value on PushSubscription (#184) (Wednesday, 4 May)
- Re: [w3c/push-api] Expose PushSubscriptionOptions value on PushSubscription (#184) (Wednesday, 4 May)
- Re: [w3c/push-api] Can you change the value of PushSubscriptionOptions (#183) (Wednesday, 4 May)
- Re: [w3c/push-api] Can you change the value of PushSubscriptionOptions (#183) (Wednesday, 4 May)
- Re: [w3c/push-api] Provide support for subscription association (#182) (Wednesday, 4 May)
Masayoshi Takahashi
Masayuki Nakano
Matt Falkenhagen
Matthew Ryan
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Monday, 16 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Monday, 16 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Monday, 16 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Saturday, 14 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Friday, 13 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Friday, 13 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Thursday, 12 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Wednesday, 11 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Wednesday, 11 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Wednesday, 11 May)
- [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Wednesday, 11 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Wednesday, 11 May)
Max Barrett
Max Klenk
Michael Kohler
Michael van Ouwerkerk
michael-nordman
Mike Taylor
Mike West
Mounir Lamouri
Ms2ger
- [whatwg/dom] Use HTML's 'document base URL' concept. (#258) (Tuesday, 31 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 13 May)
- [heycam/webidl] Update to the ES2017 signature of [[DefineOwnProperty]]. (#120) (Wednesday, 11 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 11 May)
- [whatwg/encoding] Convert to bikeshed. (#48) (Friday, 6 May)
- Re: [whatwg/encoding] Convert to bikeshed. (#48) (Friday, 6 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Friday, 6 May)
- [heycam/webidl] Use CreateDataProperty where possible. (#117) (Friday, 6 May)
- Re: [heycam/webidl] Update links to ES2017. (#114) (Friday, 6 May)
- Re: [heycam/webidl] Update links to ES2017. (#114) (Wednesday, 4 May)
- Re: [heycam/webidl] Modernize invoking user code (#113) (Wednesday, 4 May)
- [heycam/webidl] Update links to ES2017. (#114) (Wednesday, 4 May)
ockxdd
Paul Adenot
Pedram Emrouznejad
Peter Beverloo
Peter Linss
Peter Müller
Philippe Le Hegaret
publicocean0
r12a
Rajendra Singh Rathore
Richard Maher
Rick Byers
Rob Dolin (MSFT)
Robert Grant
roryhewitt
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Tuesday, 24 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Friday, 13 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Friday, 13 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Thursday, 5 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Thursday, 5 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Thursday, 5 May)
- Re: [whatwg/fetch] Add CORS protocol examples (#297) (Thursday, 5 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Wednesday, 4 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Wednesday, 4 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (3c18527) (Tuesday, 3 May)
- Re: [whatwg/fetch] Explain CORS protocol and credentials interaction (#293) (Tuesday, 3 May)
Ryosuke Niwa
- Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Tuesday, 31 May)
- Re: [w3c/webcomponents] What happens in these slot/content scenarios? (#508) (Tuesday, 31 May)
- Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Tuesday, 31 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Sunday, 29 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Saturday, 28 May)
- Re: [w3c/webcomponents] customElements.define not working (#506) (Wednesday, 25 May)
- Re: [w3c/webcomponents] A proposal to help with testing/SEO/accessibility of closed ShadowDOM (#505) (Tuesday, 24 May)
- Re: [w3c/editing] New API: Selection#makeVisible() (#129) (Monday, 23 May)
- Re: [w3c/editing] New API: Selection#makeVisible() (#129) (Monday, 23 May)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) (Thursday, 19 May)
- Re: [w3c/webcomponents] What does the construct stylesheets proposal mean for web developers? (#501) (Tuesday, 17 May)
- Re: [w3c/webcomponents] What does the construct stylesheets proposal mean for web developers? (#501) (Tuesday, 17 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Monday, 16 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Friday, 13 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Friday, 13 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Friday, 13 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Thursday, 12 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Thursday, 12 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 12 May)
- Re: [whatwg/dom] Shadow: define composedPath() (#247) (Wednesday, 11 May)
- Re: [whatwg/dom] Shadow: define composedPath() (#247) (Wednesday, 11 May)
- Re: [w3c/webcomponents] add a script for auto-publication (#498) (Tuesday, 10 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Monday, 9 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Monday, 9 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Monday, 9 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Monday, 9 May)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497) (Sunday, 8 May)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497) (Saturday, 7 May)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497) (Saturday, 7 May)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497) (Saturday, 7 May)
- [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497) (Saturday, 7 May)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Friday, 6 May)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Friday, 6 May)
- [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Friday, 6 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [w3c/webcomponents] document.currentScript from a script in a shadow tree. (#477) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Thursday, 5 May)
- Re: [w3c/webcomponents] Shadow DOM Cascade Order (#316) (Thursday, 5 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- [w3c/webcomponents] Umbrella bugs for shadow DOM related issues in other specifications for v1 API (#495) (Thursday, 5 May)
- Re: [w3c/webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80) (Thursday, 5 May)
- Re: [w3c/webcomponents] "::slotted" pseudo elements (#331) (Thursday, 5 May)
- Re: [w3c/webcomponents] Shadow DOM Cascade Order (#316) (Thursday, 5 May)
- Re: [w3c/webcomponents] "::slotted" pseudo elements (#331) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Wednesday, 4 May)
- Re: [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Wednesday, 4 May)
- [w3c/webcomponents] Retargeting algorithm shouldn't set relatedTarget to null even when target and relatedNode are in two distinct disconnected trees (#494) (Wednesday, 4 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242) (Tuesday, 3 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Monday, 2 May)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Monday, 2 May)
- [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Monday, 2 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 2 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 2 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242) (Monday, 2 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 2 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242) (Monday, 2 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242) (Monday, 2 May)
- [whatwg/dom] Event.prototype.deepPath as an attribute breaks WordPress.com (#242) (Monday, 2 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Sunday, 1 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Sunday, 1 May)
Sam Ruby
Sean Hunt
Shahar Mor
Shawn Huang
Simon Pieters
sleevi
smaug----
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Friday, 27 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Friday, 27 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Friday, 27 May)
- Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Thursday, 26 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Thursday, 26 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Thursday, 26 May)
- Re: [w3c/webcomponents] Does relatedTargetScoped need changes (#486) (Thursday, 26 May)
- [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Sunday, 22 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Thursday, 19 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 17 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Wednesday, 11 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 10 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/dom] Event.prototype.deepPath as an attribute breaks TinyMCE 4.3.10 (#242) (Thursday, 5 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 5 May)
- [w3c/uievents] It is unclear whether beforeinput should be dispatched when input event is triggered because of mouse click (#87) (Sunday, 1 May)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Sunday, 1 May)
stefan hakansson
Steven
Steven Lambert
Steven R. Loomis
Tab Atkins Jr.
Takayoshi Kochi
- [w3c/WebPlatformWG] Add myself to attendance member for Sep. 19, WebComponents. (#37) (Monday, 30 May)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Friday, 27 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Friday, 27 May)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Friday, 27 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Thursday, 26 May)
- Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507) (Thursday, 26 May)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Thursday, 26 May)
- Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Thursday, 26 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Thursday, 26 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Friday, 20 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Thursday, 19 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Wednesday, 18 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Wednesday, 18 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Wednesday, 18 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Wednesday, 18 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 17 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 17 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 10 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 10 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 10 May)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Friday, 6 May)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Friday, 6 May)
Takeshi Yoshino
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Tuesday, 31 May)
- [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Tuesday, 31 May)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Tuesday, 31 May)
- [whatwg/streams] Synchronous (or asynchronous) state probing on WritableStream (#463) (Tuesday, 31 May)
- Re: [whatwg/streams] Port locking infrastructure to writable streams (#319) (Tuesday, 31 May)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Tuesday, 31 May)
- [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Tuesday, 31 May)
- Re: [whatwg/streams] PromiseInvokeOrNoop is not autolinking (#450) (Friday, 27 May)
- [whatwg/streams] Fix PromiseInvokeOrNoop autolinking (#460) (Friday, 27 May)
- Re: [whatwg/streams] ReadableStreamCancel() should assert IsReadableStream(stream) (#452) (Friday, 27 May)
- [whatwg/streams] Move assertion on stream from ReadableStreamCancel() to its callers (#459) (Friday, 27 May)
- Re: [whatwg/streams] ReadableStreamAddReadRequest() should assert state is readable (#454) (Thursday, 26 May)
- [whatwg/streams] Add an assert on stream's state in ReadableStreamAddReadRequest() (#458) (Thursday, 26 May)
- Re: [whatwg/streams] should ReadableStreamClose() resolve BYOB reader readIntoRequests? (#455) (Thursday, 26 May)
- [whatwg/streams] Typo fix (#457) (Thursday, 26 May)
- [whatwg/streams] Update wpt-runner dependency to require 1.0.1 or later (#456) (Thursday, 26 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Tuesday, 24 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Tuesday, 24 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Tuesday, 24 May)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 16 May)
- Re: [whatwg/fetch] Body's total bytes for HEAD requests (#284) (Monday, 16 May)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444) (Monday, 9 May)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444) (Monday, 9 May)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444) (Friday, 6 May)
- Re: [whatwg/streams] Mostly-editorial tweaks to align with newer ES algorithm styles (#444) (Friday, 6 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Friday, 6 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Friday, 6 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Friday, 6 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Friday, 6 May)
- Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Friday, 6 May)
- Re: [whatwg/fetch] Provide more information in the spec on how withCredentials and Access-Control-Allow-Credentials interact (#264) (Friday, 6 May)
TanviHacks
Taylor Hurt
Thiez
Tobie Langel
Travis Leithead
Trey Shugart
triple-underscore
Vignesh Shanmugam
vyv03354
Xiaoqian Wu
Xidorn Quan
yosin
youennf
Yutaka Hirano
Zachary Forrest y Salazar
ziyunfei
Zoltan Kis
⭐caitp⭐
Иван К
Last message date: Tuesday, 31 May 2016 23:43:35 UTC