public-webapps-github@w3.org from August 2016 by author

Adam Klein

• Re: [heycam/webidl] Named properties visibility algorithm leads to ES invariant violation (#152) (Friday, 26 August)

Adam Rice

• [w3c/ServiceWorker] Replace e.g. with i.e. (#970) (Wednesday, 31 August)
• Re: [whatwg/streams] First draft at a pipeTo "algorithm" (#512) (Wednesday, 31 August)
• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) (Monday, 22 August)
• [whatwg/streams] Requirements.md: Change example of push stream from TCP to UDP (#508) (Monday, 22 August)
• [whatwg/streams] Minor comment nitpicks (#507) (Friday, 19 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Tuesday, 16 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Monday, 15 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Friday, 12 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Friday, 5 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Friday, 5 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Friday, 5 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Friday, 5 August)
• Re: [whatwg/encoding] "In equations, all numbers are integers, additio..." (#66) (Thursday, 4 August)
• Re: [whatwg/streams] Editorial changes to the socket example (#486) (Monday, 1 August)
• Re: [whatwg/streams] Editorial changes to the socket example (#486) (Monday, 1 August)
• Re: [whatwg/encoding] "In equations, all numbers are integers, additio..." (#66) (Monday, 1 August)

adamvy

• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)

Addy Osmani

• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)

Alex Danilo

• Re: [w3c/WebPlatformWG] CFC to publish WebIDL-1 as a Proposed Recommendation (#61) (Tuesday, 16 August)

Alex Russell

• Re: [w3c/permissions] Drop .request() (#83) (Saturday, 27 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 26 August)
• Re: [w3c/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Move service worker spec into w3c (#881) (Monday, 22 August)
• Re: [w3c/ServiceWorker] Move service worker spec into w3c (#881) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Declarative url filters in `fetch` event (#949) (Friday, 19 August)

aliams

• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 24 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [w3c/IndexedDB] transaction should either take DOMStringList or DOMStringList needs to be iterable (#85) (Monday, 22 August)
• [slightlyoff/ServiceWorker] Add option to ignore case for cache querying (#956) (Tuesday, 16 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Move service worker spec into w3c (#881) (Wednesday, 3 August)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Tuesday, 2 August)

Alice

• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Tuesday, 30 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Tuesday, 30 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Monday, 29 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 25 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Wednesday, 24 August)

Ambar Choudhury

• Re: [whatwg/fetch] Fetch Streaming Intermediate Emissions (#349) (Wednesday, 3 August)
• [whatwg/fetch] Fetch Streaming Intermediate Emissions (#349) (Wednesday, 3 August)

Anders Riutta

• Re: [whatwg/streams] light weight transformations (#461) (Tuesday, 23 August)
• Re: [whatwg/streams] light weight transformations (#461) (Thursday, 11 August)
• Re: [whatwg/streams] light weight transformations (#461) (Wednesday, 3 August)
• Re: [whatwg/streams] light weight transformations (#461) (Tuesday, 2 August)

Andrea Giammarchi

• Re: [w3c/webcomponents] HTML element constructors need to Get(newTarget, "Prototype") (#560) (Wednesday, 31 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 26 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 25 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 25 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 25 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 25 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 25 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 25 August)
• Re: [w3c/webcomponents] Rename interface CustomElementsRegistry to CustomElementRegistry (#548) (Thursday, 25 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Tuesday, 23 August)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Tuesday, 23 August)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Monday, 22 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Monday, 22 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Monday, 22 August)
• Re: [w3c/webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Monday, 22 August)
• Re: [whatwg/fetch] Aborting a fetch (#27) (Thursday, 18 August)
• Re: [whatwg/fetch] Aborting a fetch (#27) (Thursday, 18 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)

Andreas Kuckartz

• Re: [w3c/IndexedDB] CFC: Publish FPWD of IndexedDB 2.0 (#84) (Wednesday, 3 August)

Andres Rios

• Re: [whatwg/xhr] Consider adding toJSON to FormData (#84) (Wednesday, 17 August)
• Re: [whatwg/xhr] Consider adding toJSON to FormData (#84) (Wednesday, 17 August)
• Re: [whatwg/xhr] Consider adding toJSON to FormData (#84) (Wednesday, 17 August)
• Re: [whatwg/xhr] Consider adding toJSON to FormData (#84) (Wednesday, 17 August)
• Re: [whatwg/xhr] Consider adding toJSON to FormData (#84) (Wednesday, 17 August)
• Re: [whatwg/xhr] Consider adding toJSON to FormData (#84) (Wednesday, 17 August)

Andrew Betts

• Re: [w3ctag/spec-reviews] Notifications API (#94) (Tuesday, 2 August)
• Re: [w3ctag/spec-reviews] Notifications API (#94) (Tuesday, 2 August)

Andrew Sutherland

• Re: [slightlyoff/ServiceWorker] Handling race conditions - API for accessing pending requests? (#959) (Friday, 19 August)
• Re: [slightlyoff/ServiceWorker] Handling race conditions - API for accessing pending requests? (#959) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] Add option to ignore case for cache querying (#956) (Tuesday, 16 August)
• Re: [slightlyoff/ServiceWorker] consider firing a "clientcontrolled" event on ServiceWorkerGlobalScope (#886) (Thursday, 4 August)

Andy Earnshaw

• Re: [w3c/webcomponents] Should I write new components backwards compatible with v0 API? (#549) (Saturday, 20 August)
• Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) (Monday, 8 August)

Anne van Kesteren

• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Wednesday, 31 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Wednesday, 31 August)
• Re: [whatwg/dom] Mark ATTRIBUTE_NODE and SHOW_ATTRIBUTE as no longer historical (#321) (Wednesday, 31 August)
• Re: [whatwg/dom] Mark ATTRIBUTE_NODE and SHOW_ATTRIBUTE as no longer historical (#321) (Wednesday, 31 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Wednesday, 31 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Wednesday, 31 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Wednesday, 31 August)
• Re: [whatwg/fetch] Block text/csv for requests whose type is "script"? (#337) (Wednesday, 31 August)
• Re: [whatwg/fetch] Block text/csv for requests whose type is "script"? (#337) (Wednesday, 31 August)
• Re: [whatwg/fetch] Block additional script MIMETypes (audio, video, csv) (#379) (Wednesday, 31 August)
• Re: [whatwg/fetch] Block additional script MIMETypes (audio, video, csv) (#379) (Wednesday, 31 August)
• Re: [whatwg/dom] Drop "invoking" from "invoking retargeting" (#318) (Wednesday, 31 August)
• Re: [whatwg/dom] Drop "invoking" from "invoking retargeting" (#318) (Wednesday, 31 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Tuesday, 30 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/xhr] spec.whatwg (#86) (Tuesday, 30 August)
• Re: [whatwg/fetch] Block additional script MIMETypes (audio, video, csv) (#379) (Tuesday, 30 August)
• Re: [whatwg/dom] Validating a qualified name does not match browsers in a corner case (#319) (Tuesday, 30 August)
• Re: [whatwg/dom] Validating a qualified name does not match browsers in a corner case (#319) (Tuesday, 30 August)
• Re: [whatwg/dom] Validating a qualified name does not match browsers in a corner case (#319) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 30 August)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 30 August)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 30 August)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 30 August)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 30 August)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 30 August)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 30 August)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 30 August)
• Re: [whatwg/dom] Drop "invoking" from "invoking retargeting" (#318) (Tuesday, 30 August)
• Re: [whatwg/fetch] Request should allow WritableStream as body (#378) (Monday, 29 August)
• Re: [whatwg/fetch] Request should allow WritableStream as body (#378) (Monday, 29 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Monday, 29 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Monday, 29 August)
• Re: [heycam/webidl] Callback interface prototype should be Function.prototype, not Object… (#156) (Monday, 29 August)
• Re: [w3c/ServiceWorker] Add option to ignore case for cache querying (#956) (Monday, 29 August)
• [heycam/webidl] Remove final TYPEDARRAYS reference (#157) (Monday, 29 August)
• Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Monday, 29 August)
• Re: [w3c/ServiceWorker] Add URL to GitHub repo (#967) (Monday, 29 August)
• [w3c/ServiceWorker] Add URL (#967) (Monday, 29 August)
• [w3c/ServiceWorker] Lots of bikeshed usage issues (#965) (Monday, 29 August)
• [w3c/ServiceWorker] CacheStorage has an associated global object? (#964) (Monday, 29 August)
• Re: [whatwg/dom] Callback functions/interfaces need to be invoked with WebIDL concepts (#303) (Monday, 29 August)
• Re: [whatwg/dom] Editorial: integrate more explicitly with IDL for callbacks (#315) (Monday, 29 August)
• Re: [whatwg/dom] MutationObserver.observe()'s dictionary argument must be optional per WebIDL (#316) (Monday, 29 August)
• Re: [whatwg/dom] Editorial: add missing comma (#317) (Monday, 29 August)
• Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Monday, 29 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Sunday, 28 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Saturday, 27 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Saturday, 27 August)
• Re: [whatwg/dom] Editorial: integrate more explicitly with IDL for callbacks (#315) (Friday, 26 August)
• Re: [whatwg/dom] Editorial: integrate more explicitly with IDL for callbacks (#315) (Friday, 26 August)
• Re: [whatwg/fetch] Add From-Origin? (#365) (Friday, 26 August)
• Re: [whatwg/fetch] Add From-Origin? (#365) (Friday, 26 August)
• [whatwg/fetch] Make Request constructor more forgiving (#377) (Friday, 26 August)
• Re: [whatwg/fetch] Remove response's cache state concept (8d343bb) (Friday, 26 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Friday, 26 August)
• Re: [whatwg/dom] wip to fix #303 (#315) (Friday, 26 August)
• Re: [whatwg/fetch] Remove response's cache state concept (8d343bb) (Friday, 26 August)
• [whatwg/dom] wip to fix #303 (#315) (Friday, 26 August)
• Re: [whatwg/fetch] Remove response's cache state concept (8d343bb) (Friday, 26 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Friday, 26 August)
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Friday, 26 August)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 26 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Friday, 26 August)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Friday, 26 August)
• Re: [heycam/webidl] Named properties visibility algorithm leads to ES invariant violation (#152) (Friday, 26 August)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Thursday, 25 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Thursday, 25 August)
• Re: [whatwg/dom] DOMTokenList.value could be a stringifier attribute (#314) (Thursday, 25 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Thursday, 25 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Thursday, 25 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Thursday, 25 August)
• Re: [whatwg/url] Update origin links now that HTML defines it with for=''. (#146) (Thursday, 25 August)
• Re: [whatwg/url] Update origin links now that HTML defines it with for=''. (#146) (Thursday, 25 August)
• Re: [whatwg/fetch] Fix ReadableStream abstract operations markup (#361) (Thursday, 25 August)
• [whatwg/xhr] Fix ReadableStream abstract operations markup (#85) (Thursday, 25 August)
• Re: [whatwg/fetch] Fix ReadableStream operations (#374) (Thursday, 25 August)
• Re: [whatwg/fetch] Fix ReadableStream abstract operations markup (#361) (Thursday, 25 August)
• Re: [whatwg/fetch] Fix ReadableStream operations (#374) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] Change the rest of the links to the new repo (#961) (Thursday, 25 August)
• Re: [whatwg/dom] DOMTokenList.value could be a stringifier attribute (#314) (Thursday, 25 August)
• Re: [whatwg/dom] Should EventInit contain 'timestamp'? (#76) (Thursday, 25 August)
• Re: [whatwg/storage] Exposing cross-origin resource size (#31) (Wednesday, 24 August)
• Re: [whatwg/encoding] Consider adding "replacement" as a label for the replacement encoding (#70) (Wednesday, 24 August)
• Re: [whatwg/fetch] Preventing some CRLF header injection attacks (#375) (Wednesday, 24 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 24 August)
• [whatwg/fetch] Preventing some CRLF header injection attacks (#375) (Wednesday, 24 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 24 August)
• Re: [heycam/webidl] "get a copy of the bytes held by the buffer source" should not fail for detached buffers (#151) (Wednesday, 24 August)
• Re: [heycam/webidl] "get a copy of the bytes held by the buffer source" should not fail for detached buffers (#151) (Wednesday, 24 August)
• Re: [whatwg/storage] Exposing cross-origin resource size (#31) (Wednesday, 24 August)
• Re: [w3c/FileAPI] Blob.close() has several problems (#10) (Wednesday, 24 August)
• [heycam/webidl] "get a copy of the bytes held by the buffer source" should not fail for detached buffers (#151) (Wednesday, 24 August)
• Re: [w3c/FileAPI] Blob.close() has several problems (#10) (Wednesday, 24 August)
• Re: [whatwg/fetch] Fix ReadableStream operations (#374) (Wednesday, 24 August)
• Re: [whatwg/fetch] Fix ReadableStream operations (#374) (Wednesday, 24 August)
• Re: [whatwg/fetch] Clarification on step 4 of Headers `delete` method (#372) (Wednesday, 24 August)
• Re: [whatwg/fetch] Clarification on step 4 of Headers `delete` method (#372) (Wednesday, 24 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Wednesday, 24 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Wednesday, 24 August)
• Re: [whatwg/url] Update origin links now that HTML defines it with for=''. (#146) (Wednesday, 24 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Wednesday, 24 August)
• Re: [whatwg/fetch] Go deeper into HTTP caching (#373) (Wednesday, 24 August)
• Re: [w3c/webcomponents] Rename interface CustomElementsRegistry to CustomElementRegistry (#548) (Wednesday, 24 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Wednesday, 24 August)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Wednesday, 24 August)
• Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41) (Wednesday, 24 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Wednesday, 24 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Wednesday, 24 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [whatwg/url] Update origin links now that HTML defines it with for=''. (#146) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41) (Tuesday, 23 August)
• Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41) (Tuesday, 23 August)
• Re: [whatwg/fetch] Fix ReadableStream abstract operations markup (#361) (Tuesday, 23 August)
• Re: [whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339) (Tuesday, 23 August)
• Re: [whatwg/fetch] Clarification on step 4 of Headers `delete` method (#372) (Tuesday, 23 August)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Tuesday, 23 August)
• Re: [whatwg/fetch] Explicitly ignore 1xx responses (#366) (Tuesday, 23 August)
• Re: [whatwg/fetch] Explicitly ignore 1xx responses (#366) (Tuesday, 23 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Tuesday, 23 August)
• [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 23 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Tuesday, 23 August)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Tuesday, 23 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Tuesday, 23 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Tuesday, 23 August)
• [whatwg/dom] Expose namespace constants? (#311) (Tuesday, 23 August)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Tuesday, 23 August)
• Re: [whatwg/fetch] Clarification on step 4 of Headers `delete` method (#372) (Tuesday, 23 August)
• Re: [whatwg/fetch] Clarification on step 4 of Headers `delete` method (#372) (Tuesday, 23 August)
• Re: [w3c/webcomponents] Move the check for HTMLElement and its subclass from customElements.define to construction timing (#541) (Tuesday, 23 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Monday, 22 August)
• [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Monday, 22 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Monday, 22 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Monday, 22 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Monday, 22 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Monday, 22 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Monday, 22 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Monday, 22 August)
• Re: [whatwg/url] Doesn't describe how to process url as 'http:///google.com' (#145) (Monday, 22 August)
• Re: [whatwg/url] Doesn't describe how to process url as 'http:///google.com' (#145) (Monday, 22 August)
• Re: [w3c/webcomponents] Forbid reentrance to `customElements.define` (#545) (Saturday, 20 August)
• Re: [slightlyoff/ServiceWorker] Handle Fetch "shift+reload" (#952) (Saturday, 20 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Friday, 19 August)
• Re: [whatwg/dom] Editorial: make text around "locate a namespace" more similar (#304) (Friday, 19 August)
• Re: [whatwg/dom] Editorial: wrap contains() in <code> (#307) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr a Node again (#102) (Friday, 19 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Friday, 19 August)
• Re: [whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Friday, 19 August)
• [whatwg/dom] Editorial: wrap contains() in <code> (#307) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [slightlyoff/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Thursday, 18 August)
• Re: [whatwg/dom] Shadow: Rename "unclosed node" (#306) (Thursday, 18 August)
• Re: [whatwg/dom] "unclosed node of node" reads confusingly (#285) (Thursday, 18 August)
• Re: [whatwg/dom] Shadow: Rename "unclosed node" (#306) (Thursday, 18 August)
• Re: [whatwg/dom] Shadow: Rename "unclosed node" (#306) (Thursday, 18 August)
• Re: [whatwg/dom] Shadow: Rename "unclosed node" (#306) (Thursday, 18 August)
• Re: [whatwg/dom] Shadow: Rename "unclosed node" (#306) (Thursday, 18 August)
• Re: [slightlyoff/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Thursday, 18 August)
• [whatwg/dom] Define mutation events (#305) (Thursday, 18 August)
• Re: [whatwg/dom] Callback functions/interfaces need to be invoked with WebIDL concepts (#303) (Thursday, 18 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Thursday, 18 August)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Thursday, 18 August)
• Re: [whatwg/dom] "unclosed node of node" reads confusingly (#285) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• [whatwg/dom] Editorial: make text around "locate a namespace" more similar (#304) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Thursday, 18 August)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Wednesday, 17 August)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Wednesday, 17 August)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Make it clearer that cache mode "default" follows normal logic (#340) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• Re: [whatwg/dom] CDATASection misses (#300) (Wednesday, 17 August)
• Re: [whatwg/dom] "unclosed node of node" reads confusingly (#285) (Wednesday, 17 August)
• Re: [whatwg/dom] Future for unique tokens in DOMTokenList (#201) (Wednesday, 17 August)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Wednesday, 17 August)
• Re: [whatwg/dom] Exclude style="" by default from mutation observers (#153) (Wednesday, 17 August)
• Re: [whatwg/dom] Exclude style="" by default from mutation observers (#153) (Wednesday, 17 August)
• Re: [whatwg/dom] Define nodeName as "#cdata-section" for CDATASection nodes (#302) (Wednesday, 17 August)
• Re: [whatwg/dom] Define nodeName as "#cdata-section" for CDATASection nodes (#302) (Wednesday, 17 August)
• Re: [whatwg/dom] Define nodeName as "#cdata-section" for CDATASection nodes (#302) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/url] Convenience method to return an Object (#143) (Wednesday, 17 August)
• Re: [whatwg/fetch] Fix ReadableStream abstract operations markup (#361) (Wednesday, 17 August)
• Re: [whatwg/url] Convenience method to return an Object (#143) (Wednesday, 17 August)
• Re: [whatwg/dom] Made more formal for object global (#206) (Wednesday, 17 August)
• Re: [whatwg/dom] Specify global object references in more detail (#296) (Wednesday, 17 August)
• Re: [whatwg/dom] Made more formal for object global (#206) (Wednesday, 17 August)
• Re: [whatwg/dom] Specify global object references in more detail (#296) (Wednesday, 17 August)
• Re: [whatwg/xhr] Consider adding toJSON to FormData (#84) (Wednesday, 17 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Wednesday, 17 August)
• Re: [whatwg/xhr] Consider adding toJSON to FormData (#84) (Wednesday, 17 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/xhr] Consider adding toJSON to FormData (#84) (Wednesday, 17 August)
• Re: [whatwg/xhr] Consider adding toJSON to FormData (#84) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/xhr] Consider adding toJSON to FormData (#84) (Wednesday, 17 August)
• Re: [whatwg/fetch] Vary HTTP cache on credentials mode (#307) (Wednesday, 17 August)
• Re: [whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339) (Wednesday, 17 August)
• Re: [w3c/webcomponents] Let's make document.write()/open() throw during parser invocations of custom element constructors (#537) (Wednesday, 17 August)
• Re: [whatwg/dom] CDATASection misses (#300) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• Re: [whatwg/dom] CDATASection misses (#300) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Wednesday, 17 August)
• Re: [whatwg/dom] get rid of NonElementParentNode? (#298) (Wednesday, 17 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Tuesday, 16 August)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Tuesday, 16 August)
• Re: [whatwg/fetch] Allowed header in CORS with Access-Control-Expose-Headers (#369) (Tuesday, 16 August)
• Re: [whatwg/fetch] Allowed header in CORS with Access-Control-Expose-Headers (#369) (Tuesday, 16 August)
• Re: [whatwg/dom] get rid of NonElementParentNode? (#298) (Tuesday, 16 August)
• Re: [whatwg/dom] get rid of NonElementParentNode? (#298) (Tuesday, 16 August)
• Re: [whatwg/dom] get rid of NonElementParentNode? (#298) (Tuesday, 16 August)
• Re: [whatwg/dom] get rid of NonElementParentNode? (#298) (Tuesday, 16 August)
• Re: [whatwg/dom] get rid of NonElementParentNode? (#298) (Tuesday, 16 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Tuesday, 16 August)
• Re: [whatwg/dom] Make Attr a Node again (#102) (Tuesday, 16 August)
• Re: [whatwg/dom] get rid of NonElementParentNode? (#298) (Tuesday, 16 August)
• [whatwg/dom] Make Attr inherit from Node again (#299) (Tuesday, 16 August)
• [whatwg/xhr] Consider adding toJSON to FormData (#84) (Tuesday, 16 August)
• [whatwg/dom] Stop defining nodeName in terms of tagName (#297) (Tuesday, 16 August)
• Re: [whatwg/dom] Reinstate CDATASection (#295) (Tuesday, 16 August)
• Re: [whatwg/dom] List subclasses explicitly or not (#190) (Tuesday, 16 August)
• Re: [whatwg/dom] Reinstate CDATASection (#295) (Tuesday, 16 August)
• Re: [whatwg/dom] Reinstate CDATASection (#295) (Tuesday, 16 August)
• Re: [whatwg/dom] Pass the old and new document to adoptedCallback (#293) (Tuesday, 16 August)
• Re: [whatwg/dom] Specify global object references in more detail (#296) (Tuesday, 16 August)
• [whatwg/dom] Specify global object references in more detail (#296) (Tuesday, 16 August)
• Re: [whatwg/dom] Document.defaultCharset (#58) (Tuesday, 16 August)
• Re: [whatwg/dom] Document.defaultCharset (#58) (Tuesday, 16 August)
• Re: [whatwg/dom] Should EventInit contain 'timestamp'? (#76) (Tuesday, 16 August)
• Re: [whatwg/dom] Resize events needed? (#149) (Tuesday, 16 August)
• Re: [whatwg/dom] [CEReactions] for insertAdjacentText (#294) (Tuesday, 16 August)
• Re: [whatwg/dom] Default value for node document or always set it explicitly (#212) (Tuesday, 16 August)
• Re: [whatwg/dom] Resize events needed? (#149) (Tuesday, 16 August)
• Re: [whatwg/dom] Default value for node document or always set it explicitly (#212) (Tuesday, 16 August)
• [whatwg/dom] Reinstate CDATASection (#295) (Tuesday, 16 August)
• Re: [whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339) (Tuesday, 16 August)
• Re: [whatwg/dom] Pass the old and new document to adoptedCallback (#293) (Tuesday, 16 August)
• Re: [whatwg/dom] Pass the old and new document to adoptedCallback (#293) (Tuesday, 16 August)
• Re: [whatwg/dom] The adopted callback should be passed the old and new document (#292) (Tuesday, 16 August)
• Re: [whatwg/dom] Pass the old and new document to adoptedCallback (#293) (Tuesday, 16 August)
• Re: [whatwg/dom] Pass the old and new document to adoptedCallback (#293) (Tuesday, 16 August)
• Re: [whatwg/url] Bot.exe (#144) (Tuesday, 16 August)
• Re: [whatwg/fetch] Allowed header in CORS with Access-Control-Expose-Headers (#369) (Tuesday, 16 August)
• [w3c/FileAPI] Define WebKit's underlying file changes behavior (#47) (Monday, 15 August)
• Re: [whatwg/dom] Consider making dispatchEvent() unset stop (immediate) propagation flags (#219) (Monday, 15 August)
• Re: [w3c/webcomponents] Should :defined match <x-foo> in browsing-context-less documents? (#540) (Monday, 15 August)
• Re: [whatwg/dom] Mark more elements in browsing-context-less documents as "undefined" (#291) (Monday, 15 August)
• Re: [whatwg/dom] Mark more elements in browsing-context-less documents as "undefined" (#291) (Monday, 15 August)
• Re: [whatwg/dom] Consider making dispatchEvent() unset stop (immediate) propagation flags (#219) (Monday, 15 August)
• Re: [whatwg/dom] Consider making dispatchEvent() unset stop (immediate) propagation flags (#219) (Monday, 15 August)
• Re: [whatwg/url] Convenience method to return an `Object` (#143) (Monday, 15 August)
• Re: [whatwg/dom] The adopted callback should be passed the old and new document (#292) (Monday, 15 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Sunday, 14 August)
• Re: [whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339) (Saturday, 13 August)
• Re: [slightlyoff/ServiceWorker] Match Service Worker Registration has broken matching algorithm (#954) (Saturday, 13 August)
• Re: [slightlyoff/ServiceWorker] Match Service Worker Registration has broken matching algorithm (#954) (Saturday, 13 August)
• Re: [whatwg/url] easy initialization: `new URLSearchParams({ using: "a nice API" })` (#141) (Friday, 12 August)
• Re: [whatwg/fetch] OpenEndedDictionary clarification (#164) (Friday, 12 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 12 August)
• [slightlyoff/ServiceWorker] Match Service Worker Registration has broken matching algorithm (#954) (Friday, 12 August)
• [slightlyoff/ServiceWorker] "or its equivalent" (#953) (Friday, 12 August)
• [slightlyoff/ServiceWorker] Handle Fetch "shift+reload" (#952) (Friday, 12 August)
• [slightlyoff/ServiceWorker] Handle Fetch creates JavaScript objects too early (and other feedback) (#951) (Friday, 12 August)
• Re: [w3c/webcomponents] Ignore title attributes on <link rel=stylesheet> in shadow trees (#535) (Friday, 12 August)
• Re: [whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339) (Friday, 12 August)
• Re: [whatwg/fetch] Vary HTTP cache on credentials mode (#307) (Friday, 12 August)
• Re: [whatwg/fetch] Consider adding HTML's 401 verbiage (#311) (Friday, 12 August)
• Re: [whatwg/fetch] Consider adding HTML's 401 verbiage (#311) (Friday, 12 August)
• Re: [whatwg/fetch] Mark Accept-* request headers as simple / safe (#326) (Friday, 12 August)
• Re: [whatwg/fetch] Mark Accept-* request headers as simple / safe (#326) (Friday, 12 August)
• Re: [whatwg/fetch] Should "set response's CSP list" be in Main fetch? (#364) (Friday, 12 August)
• Re: [whatwg/fetch] The empty string is rejected as header values (#115) (Friday, 12 August)
• Re: [whatwg/fetch] The empty string is rejected as header values (#115) (Friday, 12 August)
• Re: [whatwg/fetch] "A value is a byte sequence that matches the field-content token production." (#213) (Friday, 12 August)
• Re: [whatwg/fetch] "A value is a byte sequence that matches the field-content token production." (#213) (Friday, 12 August)
• Re: [whatwg/fullscreen] Use new "allowed to use" algorithm once introduced (#41) (Friday, 12 August)
• Re: [whatwg/fullscreen] Use HTML's new "allowed to use" algorithm (#46) (Friday, 12 August)
• Re: [whatwg/fullscreen] Use new "allowed to use" algorithm once introduced (#41) (Friday, 12 August)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Friday, 12 August)
• Re: [whatwg/fetch] Remove Headers (#368) (Friday, 12 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Friday, 12 August)
• [whatwg/url] Replace pop with shorten (#140) (Thursday, 11 August)
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Thursday, 11 August)
• Re: [whatwg/fetch] Stop using entry settings object (#367) (Thursday, 11 August)
• Re: [whatwg/fetch] Stop using entry settings object (#367) (Thursday, 11 August)
• Re: [whatwg/fetch] Stop using entry settings object (#367) (Thursday, 11 August)
• Re: [whatwg/fetch] Stop using entry settings object (#367) (Thursday, 11 August)
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Thursday, 11 August)
• [whatwg/fetch] Stop using environment settings object (#367) (Thursday, 11 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)
• Re: [whatwg/xhr] Remove any headers (#83) (Thursday, 11 August)
• Re: [whatwg/xhr] Remove any headers (#83) (Thursday, 11 August)
• Re: [whatwg/xhr] Remove any headers (#83) (Thursday, 11 August)
• [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)
• Re: [whatwg/xhr] Remove any headers (#83) (Thursday, 11 August)
• Re: [w3c/webcomponents] Steps in element definition that throw an exception should abort (#543) (Thursday, 11 August)
• Re: [w3c/webcomponents] Should :defined match <x-foo> in browsing-context-less documents? (#540) (Thursday, 11 August)
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Thursday, 11 August)
• [slightlyoff/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Wednesday, 10 August)
• Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41) (Wednesday, 10 August)
• [whatwg/fetch] Explicitly ignore 1xx responses (#366) (Wednesday, 10 August)
• Re: [whatwg/fetch] Possible typo in header value definition (#332) (Wednesday, 10 August)
• Re: [whatwg/url] empty username? (#139) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899) (Wednesday, 10 August)
• [whatwg/xhr] overrideMimeType cannot throw for invalid MIME types (#82) (Wednesday, 10 August)
• Re: [whatwg/xhr] overrideMimeType cannot throw for invalid MIME types (#82) (Wednesday, 10 August)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Wednesday, 10 August)
• Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Wednesday, 10 August)
• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Wednesday, 10 August)
• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Wednesday, 10 August)
• Re: [whatwg/url] empty username? (#139) (Wednesday, 10 August)
• Re: [whatwg/fetch] Mark Accept-* request headers as simple / safe (#326) (Wednesday, 10 August)
• [whatwg/fetch] Add From-Origin? (#365) (Wednesday, 10 August)
• [whatwg/fetch] Should "set response's CSP list" be in Main fetch? (#364) (Wednesday, 10 August)
• Re: [whatwg/fetch] Dispatch to foreign fetch for redirects (#362) (Wednesday, 10 August)
• Re: [whatwg/fetch] Move 401/407 to HTTP-network-or-cache fetch (#363) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Wednesday, 10 August)
• Re: [whatwg/fetch] Move 401/407 to HTTP-network-or-cache fetch (#363) (Wednesday, 10 August)
• [whatwg/fetch] Move 401/407 to HTTP-network-or-cache fetch (#363) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Wednesday, 10 August)
• [whatwg/fetch] Dispatch to foreign fetch for redirects (#362) (Wednesday, 10 August)
• Re: [whatwg/fetch] A cross-origin to same-origin redirect should not result in an opaque response (#357) (Wednesday, 10 August)
• Re: [whatwg/fetch] A cross-origin to same-origin redirect should not result in an opaque response (#357) (Wednesday, 10 August)
• Re: [whatwg/fetch] Sentence fragment when making CORS preflight request (#328) (Wednesday, 10 August)
• Re: [whatwg/fetch] Sentence fragment when making CORS preflight request (#328) (Wednesday, 10 August)
• Re: [whatwg/fetch] fetch filter the symbols (#331) (Wednesday, 10 August)
• Re: [whatwg/fetch] fetch filter the symbols (#331) (Wednesday, 10 August)
• Re: [whatwg/fetch] Add a bit to Opaque Responses to distinguish redirects (#79) (Wednesday, 10 August)
• Re: [whatwg/fetch] Add a bit to Opaque Responses to distinguish redirects (#79) (Wednesday, 10 August)
• Re: [whatwg/fetch] Use `,` rather than `, ` for combine operation (#207) (Wednesday, 10 August)
• Re: [whatwg/fetch] Why does the Header fill algorithm require copying the header list? (#360) (Wednesday, 10 August)
• Re: [whatwg/fetch] Why does the Header fill algorithm require copying the header list? (#360) (Wednesday, 10 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Wednesday, 10 August)
• Re: [whatwg/fetch] Non-null response body check is a no-op (#343) (Wednesday, 10 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Wednesday, 10 August)
• Re: [whatwg/fetch] Access to the HTTP trailer (#34) (Wednesday, 10 August)
• Re: [whatwg/fetch] Referrer policies: add the missing policies (fixes #342) (#346) (Wednesday, 10 August)
• Re: [whatwg/fetch] Referrer policies: add the missing policies (fixes #342) (#346) (Wednesday, 10 August)
• Re: [whatwg/fetch] Support same-origin, strict-origin, strict-origin-when-cross-origin in request' referrer policy (#342) (Wednesday, 10 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Wednesday, 10 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Wednesday, 10 August)
• Re: [whatwg/fetch] Add ReadableStreamOperations for ServiceWorker (#350) (Wednesday, 10 August)
• Re: [whatwg/url] empty username? (#139) (Wednesday, 10 August)
• Re: [whatwg/url] // in path (#138) (Wednesday, 10 August)
• Re: [whatwg/url] // in path (#138) (Wednesday, 10 August)
• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Tuesday, 9 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Tuesday, 9 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Tuesday, 9 August)
• Re: [whatwg/fetch] Request's current url is undefined for a new request (#351) (Tuesday, 9 August)
• Re: [whatwg/fetch] A request needs to be created with a URL (#359) (Tuesday, 9 August)
• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Tuesday, 9 August)
• Re: [whatwg/fetch] A request needs to be created with a URL (#359) (Tuesday, 9 August)
• Re: [whatwg/fetch] A request needs to be created with a URL (#359) (Tuesday, 9 August)
• [whatwg/fetch] A request needs to be created with a URL (#359) (Tuesday, 9 August)
• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Tuesday, 9 August)
• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Tuesday, 9 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Tuesday, 9 August)
• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Tuesday, 9 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Tuesday, 9 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Tuesday, 9 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Tuesday, 9 August)
• Re: [whatwg/fetch] Add ReadableStreamOperations for ServiceWorker (#350) (Tuesday, 9 August)
• Re: [whatwg/fetch] Add ReadableStreamOperations for ServiceWorker (#350) (Tuesday, 9 August)
• Re: [whatwg/fetch] Add ReadableStreamOperations for ServiceWorker (#350) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Tuesday, 9 August)
• Re: [whatwg/dom] "unclosed node of node" reads confusingly (#285) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Tuesday, 9 August)
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Tuesday, 9 August)
• Re: [whatwg/dom] "unclosed node of node" reads confusingly (#285) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 9 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Tuesday, 9 August)
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Monday, 8 August)
• Re: [whatwg/fetch] Delay opaque responses until response body is in (#355) (Monday, 8 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Monday, 8 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Monday, 8 August)
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Monday, 8 August)
• Re: [whatwg/fetch] Delay opaque responses until response body is in (#355) (Monday, 8 August)
• Re: [whatwg/fetch] Support for CSRF? (#256) (Monday, 8 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Monday, 8 August)
• Re: [whatwg/url] relative URLs (#136) (Sunday, 7 August)
• Re: [whatwg/url] relative URLs (#136) (Sunday, 7 August)
• Re: [whatwg/fetch] Body's total bytes for HEAD requests (#284) (Saturday, 6 August)
• Re: [whatwg/fetch] Body's total bytes for HEAD requests (#284) (Saturday, 6 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Saturday, 6 August)
• Re: [whatwg/fetch] Add a bit to Opaque Responses to distinguish redirects (#79) (Friday, 5 August)
• Re: [whatwg/fetch] Add a bit to Opaque Responses to distinguish redirects (#79) (Friday, 5 August)
• Re: [whatwg/fetch] Make it clearer that cache mode "default" follows normal logic (#340) (Friday, 5 August)
• Re: [whatwg/fetch] Delay opaque responses until response body is in (#355) (Friday, 5 August)
• [whatwg/fetch] A cross-origin to same-origin redirect should not result in an opaque response (#357) (Friday, 5 August)
• Re: [whatwg/fetch] Adding bikeshed metadata to Methods, Headers, Statuses, and Bodies. (#356) (Friday, 5 August)
• Re: [whatwg/fetch] Adding bikeshed metadata to Methods, Headers, Statuses, and Bodies. (#356) (Friday, 5 August)
• Re: [whatwg/fetch] Adding bikeshed metadata to Methods, Headers, Statuses, and Bodies. (#356) (Friday, 5 August)
• [whatwg/fetch] Delay opaque responses until response body is in (#355) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache? (#941) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache? (#941) (Friday, 5 August)
• Re: [whatwg/fetch] Adding bikeshed metadata to Methods, Headers, Statuses, and Bodies. (#356) (Friday, 5 August)
• Re: [whatwg/fetch] Delay opaque responses until response body is in (#355) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Thursday, 4 August)
• Re: [whatwg/fetch] Make it clearer that cache mode "default" follows normal logic (#340) (Friday, 5 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] consider firing a "clientcontrolled" event on ServiceWorkerGlobalScope (#886) (Friday, 5 August)
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 5 August)
• Re: [whatwg/fetch] OCSP fetches bypass service worker (#347) (Friday, 5 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 5 August)
• Re: [w3c/permissions] feat(algorithms): allow calling with a PermissionName (#115) (Friday, 5 August)
• Re: [whatwg/fetch] The comma-delimited combined value definition does not support Set-Cookie headers (#345) (Thursday, 4 August)
• Re: [whatwg/fetch] The comma-delimited combined value definition does not support Set-Cookie headers (#345) (Thursday, 4 August)
• Re: [whatwg/fetch] OCSP fetches bypass service worker (#347) (Thursday, 4 August)
• Re: [whatwg/fetch] OCSP fetches bypass service worker (#347) (Thursday, 4 August)
• Re: [whatwg/encoding] Editorial: make gb18030 math more clear (#65) (Thursday, 4 August)
• Re: [whatwg/dom] "unclosed node of node" reads confusingly (#285) (Thursday, 4 August)
• Re: [whatwg/fetch] The comma-delimited combined value definition does not support Set-Cookie headers (#345) (Thursday, 4 August)
• Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) (Thursday, 4 August)
• Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) (Thursday, 4 August)
• Re: [w3c/permissions] feat(algorithms): allow calling with a PermissionName (#115) (Thursday, 4 August)
• Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204) (Thursday, 4 August)
• Re: [whatwg/fetch] Request's current url is undefined for a new request (#351) (Thursday, 4 August)
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Thursday, 4 August)
• Re: [whatwg/storage] Exposing cross-origin resource size (#31) (Thursday, 4 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Thursday, 4 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Thursday, 4 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Thursday, 4 August)
• Re: [whatwg/encoding] Editorial: make gb18030 math more clear (#65) (Thursday, 4 August)
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Thursday, 4 August)
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Thursday, 4 August)
• Re: [whatwg/encoding] Editorial: Clean up gb18030 math (#63) (Thursday, 4 August)
• Re: [whatwg/fetch] Add hooks for foreign fetch (#223) (Thursday, 4 August)
• Re: [whatwg/fetch] Does the spec suggest Fetch can only handle UTF-8 content? (#353) (Thursday, 4 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [whatwg/fetch] OCSP fetches bypass service worker (#347) (Thursday, 4 August)
• Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204) (Thursday, 4 August)
• Re: [whatwg/dom] Shadow: Add "retargeting steps" to the dispatch algorithm (#288) (Thursday, 4 August)
• Re: [whatwg/fetch] Only append Authorization if none is set (#198) (Thursday, 4 August)
• Re: [whatwg/dom] Shadow: Add "retargeting steps" to the dispatch algorithm (#288) (Thursday, 4 August)
• Re: [whatwg/fetch] Passthrough original error response unless there's a security issue in doing so (#352) (Thursday, 4 August)
• Re: [whatwg/dom] Upstream Touch Events retargeting (#286) (Thursday, 4 August)
• Re: [whatwg/dom] Shadow: Add "retargeting steps" to the dispatch algorithm (#288) (Thursday, 4 August)
• Re: [whatwg/fetch] Does the spec suggest Fetch can only handle UTF-8 content? (#353) (Thursday, 4 August)
• Re: [whatwg/fetch] Default value for ByteString in ResponseInit should be removed (#348) (Thursday, 4 August)
• Re: [whatwg/fetch] Default value for ByteString in ResponseInit should be removed (#348) (Thursday, 4 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Thursday, 4 August)
• Re: [whatwg/fetch] Request's current url is undefined for a new request (#351) (Thursday, 4 August)
• Re: [whatwg/fetch] Passthrough original error response unless there's a security issue in doing so (#352) (Thursday, 4 August)
• Re: [whatwg/fetch] Add ReadableStreamOperations for ServiceWorker (#350) (Thursday, 4 August)
• Re: [whatwg/fetch] Default value for ByteString in ResponseInit should be removed (#348) (Thursday, 4 August)
• Re: [whatwg/fetch] Default value for ByteString in ResponseInit should be removed (#348) (Thursday, 4 August)
• Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204) (Thursday, 4 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Thursday, 4 August)
• Re: [whatwg/fetch] Referrer policies: add the missing policies (fixes #342) (#346) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] consider firing a "clientcontrolled" event on ServiceWorkerGlobalScope (#886) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Thursday, 4 August)
• [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [whatwg/encoding] "In equations, all numbers are integers, additio..." (#66) (Thursday, 4 August)
• Re: [whatwg/dom] Shadow: Add a hook for retargeting other attributes (#288) (Thursday, 4 August)
• Re: [whatwg/fetch] Does the spec suggest Fetch can only handle UTF-8 content? (#353) (Thursday, 4 August)
• Re: [whatwg/dom] Shadow: Add a hook for retargeting other attributes (#288) (Thursday, 4 August)
• Re: [whatwg/dom] Is document.createEvent("progressevent") really useful? (#289) (Thursday, 4 August)
• Re: [whatwg/encoding] "In equations, all numbers are integers, additio..." (#66) (Thursday, 4 August)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Thursday, 4 August)
• Re: [whatwg/streams] Separate out exported abstract ops from internal ones (#372) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Tuesday, 2 August)

Anssi Kostiainen

• Re: [w3c/ServiceWorker] Change the rest of the links to the new repo (#961) (Thursday, 25 August)
• [w3c/ServiceWorker] Change the rest of the links to the new repo (#961) (Wednesday, 24 August)

ArkadiuszMichalski

• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Tuesday, 30 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Thursday, 25 August)
• Re: [whatwg/dom] Future for unique tokens in DOMTokenList (#201) (Saturday, 20 August)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Saturday, 20 August)

Arron Eicholz

• Re: [heycam/webidl] Check if NodeFilter.length is defined correctly. (#83) (Tuesday, 23 August)

Arthur Stolyar

• Re: [w3c/ServiceWorker] consider exposing self.clients on window and other worker globals (#955) (Monday, 29 August)
• Re: [w3c/ServiceWorker] consider exposing self.clients on window and other worker globals (#955) (Friday, 26 August)
• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Friday, 26 August)
• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920) (Wednesday, 24 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Tuesday, 23 August)
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Saturday, 20 August)
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Friday, 19 August)
• Re: [slightlyoff/ServiceWorker] Declarative url filters in `fetch` event (#949) (Friday, 19 August)
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Friday, 19 August)
• Re: [slightlyoff/ServiceWorker] Handle Fetch "shift+reload" (#952) (Friday, 19 August)
• Re: [slightlyoff/ServiceWorker] Handling race conditions - API for accessing pending requests? (#959) (Friday, 19 August)
• Re: [slightlyoff/ServiceWorker] Handling race conditions - API for accessing pending requests? (#959) (Thursday, 18 August)
• Re: [slightlyoff/ServiceWorker] Handling race conditions - API for accessing pending requests? (#959) (Thursday, 18 August)
• Re: [slightlyoff/ServiceWorker] Handling race conditions - API for accessing pending requests? (#959) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 16 August)
• Re: [slightlyoff/ServiceWorker] Declarative url filters in `fetch` event (#949) (Friday, 12 August)
• Re: [slightlyoff/ServiceWorker] Declarative url filters in `fetch` event (#949) (Friday, 12 August)
• [slightlyoff/ServiceWorker] Declarative `fetch` event (#949) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] Firefox buggy (#948) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] Firefox buggy (#948) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)

Aryeh Gregor

• Re: [whatwg/dom] Validating a qualified name does not match browsers in a corner case (#319) (Tuesday, 30 August)
• Re: [whatwg/dom] Validating a qualified name does not match browsers in a corner case (#319) (Tuesday, 30 August)
• Re: [whatwg/dom] Validating a qualified name does not match browsers in a corner case (#319) (Tuesday, 30 August)
• Re: [whatwg/dom] Validating a qualified name does not match browsers in a corner case (#319) (Tuesday, 30 August)
• [whatwg/dom] Validating a qualified name does not match browsers in a corner case (#319) (Tuesday, 30 August)
• Re: [heycam/webidl] Callback interface prototype should be Function.prototype, not Object… (#156) (Monday, 29 August)
• Re: [heycam/webidl] Callback interface prototype should be Function.prototype, not Object… (#156) (Monday, 29 August)
• Re: [heycam/webidl] Callback interface prototype should be Function.prototype, not Object… (#156) (Monday, 29 August)
• [heycam/webidl] Callback interface prototype should be Function.prototype, not Object… (#156) (Monday, 29 August)
• Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Monday, 29 August)
• Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Monday, 29 August)
• Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Sunday, 28 August)
• [whatwg/dom] MutationObserver.observe()'s dictionary argument must be optional per WebIDL (#316) (Sunday, 28 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Sunday, 28 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Sunday, 28 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Thursday, 25 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 24 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Wednesday, 24 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Wednesday, 24 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Wednesday, 24 August)
• [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Wednesday, 24 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 24 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Tuesday, 23 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 17 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Tuesday, 16 August)
• Re: [whatwg/dom] Consider banning insertNode() of the Range's start node (#63) (Tuesday, 16 August)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Monday, 15 August)
• Re: [whatwg/dom] surroundContents() with CharacterData node as newParent argument (#250) (Monday, 15 August)

beidson

• Re: [w3c/gamepad] Snapshot API as "Version 1" CR (#31) (Wednesday, 24 August)
• Re: [w3c/gamepad] Handedness of controllers (#30) (Friday, 5 August)
• Re: [w3c/IndexedDB] Naming for "v2" ? (#82) (Monday, 1 August)

Ben

• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Wednesday, 17 August)
• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Thursday, 4 August)

Ben Francis

• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Wednesday, 3 August)
• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Wednesday, 3 August)

Ben Kelly

• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Monday, 29 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Monday, 29 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Monday, 29 August)
• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Monday, 29 August)
• Re: [w3c/ServiceWorker] Handle Fetch "shift+reload" (#952) (Monday, 29 August)
• Re: [w3c/ServiceWorker] consider exposing self.clients on window and other worker globals (#955) (Monday, 29 August)
• Re: [w3c/ServiceWorker] Add option to ignore case for cache querying (#956) (Monday, 29 August)
• Re: [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308) (Monday, 29 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Monday, 29 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 26 August)
• [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 24 August)
• Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813) (Wednesday, 24 August)
• Re: [whatwg/streams] Backpressure from tee-ing and slow/pending consumer (#506) (Wednesday, 24 August)
• Re: [whatwg/streams] Backpressure from tee-ing and slow/pending consumer (#506) (Wednesday, 24 August)
• Re: [w3c/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Tuesday, 23 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Friday, 19 August)
• Re: [slightlyoff/ServiceWorker] Reliable way to detect if a fetch is for a new page (#958) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] Reliable way to detect if a fetch is for a new page (#958) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] notification of cancelled download? (#957) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] Add option to ignore case for cache querying (#956) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Tuesday, 16 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 12 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 12 August)
• Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Friday, 12 August)
• [slightlyoff/ServiceWorker] consider exposing self.clients on window and other worker globals (#955) (Friday, 12 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Thursday, 11 August)
• Re: [slightlyoff/ServiceWorker] Firefox buggy (#948) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] Firefox buggy (#948) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] Firefox buggy (#948) (Wednesday, 10 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] Service worker updation doesn't work as expected (#946) (Wednesday, 10 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Tuesday, 9 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Tuesday, 9 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Tuesday, 9 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Monday, 8 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 8 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 8 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 8 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Monday, 8 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Send correct Accept header with fetch() request (#945) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Send correct Accept header with fetch() request (#945) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)
• Re: [whatwg/fetch] Add a bit to Opaque Responses to distinguish redirects (#79) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)
• Re: [whatwg/fetch] Make it clearer that cache mode "default" follows normal logic (#340) (Friday, 5 August)
• [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Thursday, 4 August)
• Re: [whatwg/fetch] OCSP fetches bypass service worker (#347) (Thursday, 4 August)
• Re: [whatwg/fetch] OCSP fetches bypass service worker (#347) (Thursday, 4 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Thursday, 4 August)
• Re: [whatwg/fetch] OCSP fetches bypass service worker (#347) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] consider firing a "clientcontrolled" event on ServiceWorkerGlobalScope (#886) (Thursday, 4 August)
• Re: [whatwg/streams] should ReadableStreamClose() resolve BYOB reader readIntoRequests? (#455) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Block 206s entering the cache (via put & addAll) (#937) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] potential http cache issues with importScripts() (#894) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Monday, 1 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] consider firing a "clientcontrolled" event on ServiceWorkerGlobalScope (#886) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Monday, 1 August)

Benjamin C. Wiley Sittler

• Re: [slightlyoff/ServiceWorker] Add cookie accessor/setter methods? (#707) (Friday, 12 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)

Bevis Tseng

• Re: [w3c/IndexedDB] Gather developer feedback on new spec additions (#65) (Tuesday, 30 August)
• Re: [w3c/IndexedDB] Integrate with window.onerror (#49) (Wednesday, 3 August)

bmaurer

• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 1 August)

bokand

• Re: [w3ctag/spec-reviews] Review window.visualViewport API (#128) (Wednesday, 31 August)
• Re: [w3ctag/spec-reviews] Review window.visualViewport API (#128) (Thursday, 11 August)
• [w3ctag/spec-reviews] Review window.visualViewport API (#128) (Friday, 5 August)

Boris Zbarsky

• Re: [heycam/webidl] Update method creation for operations (#155) (Tuesday, 30 August)
• Re: [heycam/webidl] Update method creation for operations (#155) (Tuesday, 30 August)
• Re: [heycam/webidl] Update method creation for operations (#155) (Tuesday, 30 August)
• Re: [heycam/webidl] Update method creation for operations (#155) (Tuesday, 30 August)
• Re: [heycam/webidl] Update method creation for operations (#155) (Tuesday, 30 August)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Monday, 29 August)
• Re: [heycam/webidl] Callback interface prototype should be Function.prototype, not Object… (#156) (Monday, 29 August)
• Re: [heycam/webidl] Callback interface prototype should be Function.prototype, not Object… (#156) (Monday, 29 August)
• Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Monday, 29 August)
• Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Monday, 29 August)
• Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Monday, 29 August)
• Re: [heycam/webidl] Named properties visibility algorithm leads to ES invariant violation (#152) (Friday, 26 August)
• Re: [heycam/webidl] Named properties visibility algorithm leads to ES invariant violation (#152) (Friday, 26 August)
• Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) (Thursday, 25 August)
• Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) (Thursday, 25 August)
• Re: [heycam/webidl] Add some IDs to callback-invoking definitions (#146) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] [Exposed] doesn't seem to work well with partial interfaces (#154) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• [heycam/webidl] Named properties visibility algorithm leads to ES invariant violation (#152) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 24 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 24 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 24 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 24 August)
• Re: [heycam/webidl] "get a copy of the bytes held by the buffer source" should not fail for detached buffers (#151) (Wednesday, 24 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Wednesday, 24 August)
• Re: [heycam/webidl] Add missing 'return's. (#150) (Tuesday, 23 August)
• Re: [heycam/webidl] Platform object [[Delete]] method is missing some "return" statements (#149) (Tuesday, 23 August)
• [heycam/webidl] Platform object [[Delete]] method is missing some "return" statements (#149) (Tuesday, 23 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Tuesday, 23 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Monday, 22 August)
• Re: [heycam/webidl] Conversion to sequence<T> need not throw on a RegExp object (#145) (Monday, 22 August)
• Re: [heycam/webidl] Remove the RegExp type (#148) (Monday, 22 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Monday, 22 August)
• Re: [whatwg/dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143) (Friday, 12 August)
• Re: [heycam/webidl] Provide a concise syntax to create IDL dictionaries from prose (#142) (Friday, 5 August)
• Re: [heycam/webidl] Defining a ByteString default value using a string literal with no explanation of how it's done makes no sense (#141) (Thursday, 4 August)
• Re: [heycam/webidl] Defining a ByteString default value using a string literal with no explanation of how it's done makes no sense (#141) (Thursday, 4 August)
• [heycam/webidl] Defining a ByteString default value using a string literal with no explanation of how it's done makes no sense (#141) (Thursday, 4 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Thursday, 4 August)
• Re: [heycam/webidl] is Step 5.5.1. of effective overload set construction really needed? (#140) (Tuesday, 2 August)
• Re: [heycam/webidl] Step 5.8 of effective overload set construction is a no-op? (#139) (Monday, 1 August)
• Re: [heycam/webidl] Overload resolution algorithm: Steps 11.5. and 11.6. are identical (#138) (Monday, 1 August)
• Re: [heycam/webidl] Overload resolution algorithm: Steps 11.5. and 11.6. are identical (#138) (Monday, 1 August)
• Re: [w3c/gamepad] IDL array[]s no longer exist (#28) (Monday, 1 August)

Brandon Jones

• [w3c/gamepad] Snapshot API as "Version 1" CR (#31) (Tuesday, 23 August)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Tuesday, 9 August)
• [w3c/gamepad] Handedness of controllers (#30) (Friday, 5 August)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Thursday, 4 August)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Tuesday, 2 August)
• Re: [w3c/gamepad] Added GamepadPose (#25) (Monday, 1 August)

Brent Kimmel

• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Sunday, 7 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Sunday, 7 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)

Brian Terlson

• Re: [heycam/webidl] "get a copy of the bytes held by the buffer source" should not fail for detached buffers (#151) (Wednesday, 24 August)

Cameron McCormack

• Re: [heycam/webidl] Bikeshed Conversion (#147) (Friday, 19 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Friday, 19 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Friday, 19 August)
• Re: [heycam/webidl] Step 5.8 of effective overload set construction is a no-op? (#139) (Thursday, 18 August)
• Re: [whatwg/fetch] Default value for ByteString in ResponseInit should be removed (#348) (Thursday, 4 August)
• Re: [whatwg/fetch] Default value for ByteString in ResponseInit should be removed (#348) (Thursday, 4 August)
• Re: [whatwg/fetch] Default value for ByteString in ResponseInit should be removed (#348) (Thursday, 4 August)
• Re: [heycam/webidl] Step 5.8 of effective overload set construction is a no-op? (#139) (Wednesday, 3 August)
• Re: [heycam/webidl] is Step 5.5.1. of effective overload set construction really needed? (#140) (Wednesday, 3 August)
• Re: [heycam/webidl] is Step 5.5.1. of effective overload set construction really needed? (#140) (Wednesday, 3 August)

chaals

• [w3c/manifest] Status section has misleading info on filing bugs (#489) (Wednesday, 24 August)
• [w3c/manifest] Redundant reference to RFC3166? (#488) (Wednesday, 24 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Wednesday, 24 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Tuesday, 23 August)
• Re: [w3c/charter-html] Improved ARIA WG description (#132) (Thursday, 4 August)

Chad Killingsworth

• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Monday, 29 August)

Chong Zhang

• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] [beforeinput] InputType for MacOS Transpose (ctrl-t) (#148) (Wednesday, 24 August)
• Re: [w3c/editing] [beforeinput] InputType for MacOS Transpose (ctrl-t) (#148) (Wednesday, 24 August)
• Re: [w3c/editing] [beforeinput] InputType for MacOS Transpose (ctrl-t) (#148) (Wednesday, 24 August)
• Re: [w3c/editing] [beforeinput] Rename drag&drop to deleteByDrag&insertFromDrop (#147) (Wednesday, 24 August)
• [w3c/editing] [beforeinput] InputType for MacOS Transpose (ctrl-t) (#148) (Wednesday, 24 August)
• [w3c/editing] [beforeinput] Rename drag&drop to deleteByDrag&insertFromDrop (#147) (Wednesday, 24 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Wednesday, 17 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Wednesday, 17 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Wednesday, 17 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Tuesday, 16 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Tuesday, 16 August)
• [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Tuesday, 16 August)

Chris Dumez

• Re: [heycam/webidl] Callback interface prototype should be Function.prototype, not Object… (#156) (Monday, 29 August)
• Re: [heycam/webidl] Callback interface prototype should be Function.prototype, not Object… (#156) (Monday, 29 August)
• Re: [heycam/webidl] Callback interface prototype should be Function.prototype, not Object… (#156) (Monday, 29 August)
• Re: [whatwg/dom] DOMTokenList.value could be a stringifier attribute (#314) (Thursday, 25 August)
• Re: [whatwg/dom] DOMTokenList.value could be a stringifier attribute (#314) (Thursday, 25 August)
• [whatwg/dom] DOMTokenList.value could be a stringifier attribute (#314) (Thursday, 25 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 24 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 24 August)
• Re: [whatwg/encoding] Consider adding "replacement" as a label for the replacement encoding (#70) (Wednesday, 24 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Wednesday, 24 August)
• Re: [whatwg/encoding] Consider adding "replacement" as a label for the replacement encoding (#70) (Wednesday, 24 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Tuesday, 23 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Tuesday, 23 August)
• Re: [whatwg/encoding] Consider adding "replacement" as a label for the replacement encoding (#70) (Monday, 22 August)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Saturday, 20 August)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Saturday, 20 August)
• Re: [whatwg/dom] Remove feature detection from add() and add supports() (#123) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Wednesday, 17 August)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Tuesday, 16 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Tuesday, 16 August)
• Re: [whatwg/dom] Consider making dispatchEvent() unset stop (immediate) propagation flags (#219) (Tuesday, 16 August)
• Re: [whatwg/dom] Consider making dispatchEvent() unset stop (immediate) propagation flags (#219) (Tuesday, 16 August)
• Re: [whatwg/dom] Consider making dispatchEvent() unset stop (immediate) propagation flags (#219) (Monday, 15 August)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Saturday, 13 August)
• Re: [whatwg/dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143) (Saturday, 13 August)
• Re: [whatwg/dom] Consider making dispatchEvent() unset stop (immediate) propagation flags (#219) (Friday, 12 August)
• Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) (Friday, 12 August)
• Re: [whatwg/dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143) (Friday, 12 August)
• Re: [whatwg/dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143) (Thursday, 11 August)
• Re: [whatwg/dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143) (Thursday, 11 August)
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Thursday, 11 August)
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Thursday, 11 August)
• Re: [whatwg/dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143) (Wednesday, 10 August)
• Re: [whatwg/dom] Is document.createEvent("progressevent") really useful? (#289) (Thursday, 4 August)
• [whatwg/dom] Is document.createEvent("progressevent") really useful? (#289) (Thursday, 4 August)
• Re: [heycam/webidl] Step 5.8 of effective overload set construction is a no-op? (#139) (Wednesday, 3 August)
• Re: [heycam/webidl] is Step 5.5.1. of effective overload set construction really needed? (#140) (Wednesday, 3 August)
• [heycam/webidl] is Step 5.5.1. of effective overload set construction really needed? (#140) (Monday, 1 August)
• [heycam/webidl] Step 5.8 of effective overload set construction is a no-op? (#139) (Monday, 1 August)
• [heycam/webidl] Overload resolution algorithm: Steps 11.5. and 11.6. are identical (#138) (Monday, 1 August)

Chris Morgan

• [w3c/webcomponents] Better custom event support for custom elements would be great (#546) (Saturday, 13 August)

Chris Rebert

• Re: [whatwg/dom] cancelBubble legacy property (#211) (Tuesday, 16 August)
• Re: [w3c/uievents] 3.4 and 3.5 duplicate HTML spec (#95) (Thursday, 11 August)

chris van wiemeersch

• Re: [w3c/gamepad] Consider changing API to match SDL2's (#24) (Thursday, 4 August)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Thursday, 4 August)
• Re: [w3c/gamepad] Consider changing API to match SDL2's (#24) (Thursday, 4 August)
• Re: [w3c/gamepad] Add a Project Description and Project URL (#29) (Tuesday, 2 August)

cyns

• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Tuesday, 30 August)

Cyril Auburtin

• Re: [whatwg/dom] Proposal to improve the DOM creation api (#150) (Friday, 12 August)
• Re: [whatwg/dom] Removing event listeners through an identifier (#208) (Thursday, 11 August)
• Re: [whatwg/dom] Proposal to improve the DOM creation api (#150) (Thursday, 11 August)
• Re: [whatwg/dom] Proposal to improve the DOM creation api (#150) (Thursday, 11 August)
• Re: [whatwg/dom] Consider adding more utils to Elements (#145) (Thursday, 11 August)
• Re: [whatwg/dom] new Element(tagName)? (#287) (Wednesday, 3 August)
• Re: [whatwg/dom] new Element(tagName)? (#287) (Wednesday, 3 August)
• [whatwg/dom] new Element(tagName)? (#287) (Tuesday, 2 August)

Dan Dascalescu

• [slightlyoff/ServiceWorker] Typo fixes (#944) (Friday, 5 August)

Daniel Appelquist

• Re: [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) (Wednesday, 31 August)
• Re: [w3ctag/spec-reviews] Extensibility of Accessibility (#63) (Wednesday, 31 August)
• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Wednesday, 31 August)
• Re: [w3ctag/spec-reviews] WebVR (#106) (Wednesday, 31 August)
• Re: [w3ctag/spec-reviews] privacy of sensor other exotic APIs (#129) (Wednesday, 10 August)
• Re: [w3ctag/spec-reviews] Review window.visualViewport API (#128) (Wednesday, 10 August)
• Re: [w3ctag/spec-reviews] Review window.visualViewport API (#128) (Wednesday, 10 August)
• [w3ctag/spec-reviews] privacy of sensor other exotic APIs (#129) (Wednesday, 10 August)

Daniel Freedman

• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Friday, 5 August)

Dave Cramer

• [w3c/manifest] Discoverability of metadata in web application manifest (#486) (Friday, 12 August)

Dave Tapuska

• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)

David Baron

• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Wednesday, 31 August)
• Re: [w3ctag/spec-reviews] Review window.visualViewport API (#128) (Tuesday, 30 August)
• Re: [w3ctag/spec-reviews] Filters in Canvas 2D (#116) (Wednesday, 17 August)
• Re: [w3ctag/spec-reviews] Filters in Canvas 2D (#116) (Wednesday, 17 August)
• Re: [w3ctag/spec-reviews] Review window.visualViewport API (#128) (Tuesday, 16 August)
• Re: [w3ctag/spec-reviews] Filters in Canvas 2D (#116) (Tuesday, 16 August)

David Frank

• Re: [whatwg/streams] Backpressure from tee-ing and slow/pending consumer (#506) (Friday, 19 August)
• Re: [whatwg/streams] Backpressure from tee-ing and slow/pending consumer (#506) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• [whatwg/streams] Backpressure from tee-ing and slow/pending consumer (#506) (Thursday, 18 August)
• Re: [whatwg/fetch] Does the spec suggest Fetch can only handle UTF-8 content? (#353) (Thursday, 4 August)
• [whatwg/fetch] Does the spec suggest Fetch can only handle UTF-8 content? (#353) (Thursday, 4 August)

Dennis Decoene

• Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Wednesday, 10 August)

Dexter Miguel

• Re: [whatwg/fetch] Aborting a fetch (#27) (Friday, 12 August)

Dimitri Glazkov

• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Monday, 22 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Monday, 22 August)

Domenic Denicola

• Re: [heycam/webidl] Update method creation for operations (#155) (Wednesday, 31 August)
• Re: [heycam/webidl] Update method creation for operations (#155) (Wednesday, 31 August)
• Re: [heycam/webidl] Update method creation for operations (#155) (Wednesday, 31 August)
• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Wednesday, 31 August)
• Re: [whatwg/streams] Factor out WritableStreamDefaultWriterRelease (#513) (Wednesday, 31 August)
• Re: [w3c/webcomponents] HTML element constructors need to Get(newTarget, "Prototype") (#560) (Wednesday, 31 August)
• [whatwg/dom] " public-scrip-coord@w3.org" (#322) (Wednesday, 31 August)
• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Tuesday, 30 August)
• Re: [whatwg/streams] Convert writable stream tests to web platform tests format (#492) (Tuesday, 30 August)
• Re: [whatwg/streams] Convert some general tests for ws into wpt (#510) (Tuesday, 30 August)
• [whatwg/streams] Factor out WritableStreamDefaultWriterRelease (#513) (Tuesday, 30 August)
• [whatwg/streams] First draft at a pipeTo "algorithm" (#512) (Tuesday, 30 August)
• Re: [whatwg/streams] Convert some general tests for ws into wpt (#510) (Tuesday, 30 August)
• Re: [whatwg/streams] Convert some general tests for ws into wpt (#510) (Tuesday, 30 August)
• Re: [whatwg/streams] Convert some general tests for ws into wpt (#510) (Tuesday, 30 August)
• Re: [whatwg/streams] Convert some general tests for ws into wpt (#510) (Tuesday, 30 August)
• Re: [whatwg/dom] Drop "invoking" from "invoking retargeting" (#318) (Tuesday, 30 August)
• Re: [heycam/webidl] Update method creation for operations (#155) (Tuesday, 30 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Monday, 29 August)
• Re: [w3c/webcomponents] "The problematic position" when Custom Elements throw errors? (#547) (Monday, 29 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Monday, 29 August)
• Re: [whatwg/fetch] Request should allow WritableStream as body (#378) (Monday, 29 August)
• Re: [heycam/webidl] Callback interface prototype should be Function.prototype, not Object… (#156) (Monday, 29 August)
• Re: [w3c/webcomponents] What's the expected behavior of a class with observedAttributes but no attributeChangedCallback? (#555) (Friday, 26 August)
• Re: [w3c/webcomponents] What's the expected behavior of a class with observedAttributes but no attributeChangedCallback? (#555) (Friday, 26 August)
• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) (Friday, 26 August)
• Re: [whatwg/dom] Editorial: integrate more explicitly with IDL for callbacks (#315) (Friday, 26 August)
• Re: [whatwg/dom] Editorial: integrate more explicitly with IDL for callbacks (#315) (Friday, 26 August)
• Re: [whatwg/dom] Editorial: integrate more explicitly with IDL for callbacks (#315) (Friday, 26 August)
• [w3c/ServiceWorker] Parse URLs relative to the relevant settings object, not entry (#963) (Friday, 26 August)
• Re: [whatwg/dom] Editorial: integrate more explicitly with IDL for callbacks (#315) (Friday, 26 August)
• Re: [whatwg/dom] Editorial: integrate more explicitly with IDL for callbacks (#315) (Friday, 26 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 25 August)
• Re: [whatwg/streams] piping issue (#509) (Thursday, 25 August)
• Re: [whatwg/streams] Convert writable stream tests to web platform tests format (#492) (Thursday, 25 August)
• Re: [heycam/webidl] Update method creation for operations (#155) (Thursday, 25 August)
• [heycam/webidl] Update method creation for operations (#155) (Thursday, 25 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 25 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 25 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 25 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 25 August)
• Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) (Thursday, 25 August)
• Re: [heycam/webidl] Add some IDs to callback-invoking definitions (#146) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• [heycam/webidl] [Exposed] doesn't seem to work well with partial interfaces (#154) (Thursday, 25 August)
• [heycam/webidl] [SecureContext] restrictions on interface vs. interface member are confusing (#153) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [heycam/webidl] Add namespaces (#121) (Thursday, 25 August)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Thursday, 25 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Thursday, 25 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Wednesday, 24 August)
• Re: [heycam/webidl] Add namespaces (#121) (Wednesday, 24 August)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Wednesday, 24 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Wednesday, 24 August)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Wednesday, 24 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Tuesday, 23 August)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] Rename interface CustomElementsRegistry to CustomElementRegistry (#548) (Tuesday, 23 August)
• Re: [w3c/webcomponents] Rename interface CustomElementsRegistry to CustomElementRegistry (#548) (Monday, 22 August)
• Re: [whatwg/encoding] Consider adding "replacement" as a label for the replacement encoding (#70) (Monday, 22 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Monday, 22 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream() to drain all the available data (#489) (Monday, 22 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Monday, 22 August)
• Re: [whatwg/streams] Requirements.md: Change example of push stream from TCP to UDP (#508) (Monday, 22 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Monday, 22 August)
• Re: [w3c/webcomponents] "The problematic position" when Custom Elements throw errors? (#547) (Monday, 22 August)
• [heycam/webidl] Remove the RegExp type (#148) (Saturday, 20 August)
• Re: [w3c/webcomponents] Should I write new components backwards compatible with v0 API? (#549) (Saturday, 20 August)
• Re: [w3c/webcomponents] Should I write new components backwards compatible with v0 API? (#549) (Saturday, 20 August)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Saturday, 20 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Friday, 19 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Friday, 19 August)
• Re: [whatwg/streams] Backpressure from tee-ing and slow/pending consumer (#506) (Friday, 19 August)
• Re: [whatwg/streams] Backpressure from tee-ing and slow/pending consumer (#506) (Friday, 19 August)
• Re: [whatwg/streams] Backpressure from tee-ing and slow/pending consumer (#506) (Friday, 19 August)
• Re: [whatwg/streams] Minor comment nitpicks (#507) (Friday, 19 August)
• Re: [w3c/webcomponents] "The problematic position" when Custom Elements throw errors? (#547) (Friday, 19 August)
• Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• [heycam/webidl] Add some IDs to callback-invoking definitions (#146) (Wednesday, 17 August)
• Re: [whatwg/url] Convenience method to return an Object (#143) (Wednesday, 17 August)
• Re: [whatwg/url] Convenience method to return an Object (#143) (Wednesday, 17 August)
• Re: [whatwg/url] Convenience method to return an Object (#143) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] notification of cancelled download? (#957) (Wednesday, 17 August)
• Re: [whatwg/dom] get rid of NonElementParentNode? (#298) (Tuesday, 16 August)
• Re: [whatwg/url] Convenience method to return an Object (#143) (Tuesday, 16 August)
• Re: [whatwg/dom] Pass the old and new document to adoptedCallback (#293) (Tuesday, 16 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Monday, 15 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Monday, 15 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Monday, 15 August)
• Re: [w3c/webcomponents] Step 13.3-4 in element definition should clarify the ordering (#542) (Monday, 15 August)
• [whatwg/dom] Pass the old and new document to adoptedCallback (#293) (Monday, 15 August)
• Re: [heycam/webidl] Conversion to sequence<T> need not throw on a RegExp object (#145) (Monday, 15 August)
• Re: [whatwg/url] Convenience method to return an `Object` (#143) (Monday, 15 August)
• Re: [w3c/webcomponents] Move the check for HTMLElement and its subclass from customElements.define to construction timing (#541) (Monday, 15 August)
• Re: [w3c/webcomponents] Better custom event support for custom elements would be great (#546) (Saturday, 13 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Friday, 12 August)
• Re: [w3c/webcomponents] Move the check for HTMLElement and its subclass from customElements.define to construction timing (#541) (Friday, 12 August)
• Re: [w3c/webcomponents] Forbid reentrance to `customElements.define` (#545) (Friday, 12 August)
• [whatwg/dom] Mark more elements in browsing-context-less documents as "undefined" (#291) (Friday, 12 August)
• Re: [whatwg/streams] light weight transformations (#461) (Thursday, 11 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)
• Re: [whatwg/fetch] Stop using entry settings object (#367) (Thursday, 11 August)
• Re: [whatwg/fetch] Stop using entry settings object (#367) (Thursday, 11 August)
• Re: [whatwg/fetch] Stop using entry settings object (#367) (Thursday, 11 August)
• Re: [slightlyoff/ServiceWorker] Tidy up global object usage (#950) (Thursday, 11 August)
• Re: [whatwg/dom] Proposal to improve the DOM creation api (#150) (Thursday, 11 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)
• Re: [w3c/webcomponents] Steps in element definition that throw an exception should abort (#543) (Thursday, 11 August)
• Re: [w3c/webcomponents] Should :defined match <x-foo> in browsing-context-less documents? (#540) (Thursday, 11 August)
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Thursday, 11 August)
• Re: [w3c/webcomponents] Step 13.3-4 in element definition should clarify the ordering (#542) (Thursday, 11 August)
• [slightlyoff/ServiceWorker] Tidy up global object usage (#950) (Wednesday, 10 August)
• Re: [w3c/webcomponents] Let's make document.write()/open() throw during parser invocations of custom element constructors (#537) (Wednesday, 10 August)
• Re: [whatwg/streams] light weight transformations (#461) (Wednesday, 10 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Wednesday, 10 August)
• [w3c/webcomponents] Should :defined match <x-foo> in browsing-context-less documents? (#540) (Wednesday, 10 August)
• Re: [whatwg/url] // in path (#138) (Wednesday, 10 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 9 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Monday, 8 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Monday, 8 August)
• Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Friday, 5 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Friday, 5 August)
• Re: [whatwg/streams] light weight transformations (#461) (Friday, 5 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Friday, 5 August)
• Re: [whatwg/streams] Factor out some logic into helper functions (#505) (Friday, 5 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Friday, 5 August)
• Re: [whatwg/streams] Make writer.desiredSize return 0 for closed writable streams (#501) (Friday, 5 August)
• Re: [whatwg/streams] Make writer.desiredSize return 0 for closed streams (#503) (Friday, 5 August)
• Re: [w3c/webcomponents] Other named properties in shadow DOM (#536) (Friday, 5 August)
• [w3c/webcomponents] Let's make document.write()/open() throw during parser invocations of custom element constructors (#537) (Friday, 5 August)
• Re: [whatwg/streams] should ReadableStreamClose() resolve BYOB reader readIntoRequests? (#455) (Thursday, 4 August)
• Re: [whatwg/dom] Is document.createEvent("progressevent") really useful? (#289) (Thursday, 4 August)
• Re: [whatwg/streams] Add lint for coding style, etc. (#494) (Thursday, 4 August)
• Re: [whatwg/streams] Byte streams: write up design rationales and vision for how they are used/what they enable (#177) (Thursday, 4 August)
• Re: [whatwg/streams] Can we not have "four interfaces" (#102) (Thursday, 4 August)
• Re: [whatwg/streams] Byte streams: write up design rationales and vision for how they are used/what they enable (#177) (Thursday, 4 August)
• Re: [whatwg/streams] Update spec to use ReadableStreamDefaultControllerErrorIfNeeded (#500) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [whatwg/streams] Remove unchecked expectation from readable byte stream test (#502) (Thursday, 4 August)
• Re: [whatwg/streams] Remove unchecked expectation from readable byte stream test (#502) (Thursday, 4 August)
• Re: [whatwg/streams] "Web sockets do not provide any way to tell when..." (#485) (Thursday, 4 August)
• Re: [whatwg/streams] Add an example of using desiredSize and ready with writable streams (#496) (Thursday, 4 August)
• [whatwg/streams] Make writer.desiredSize return 0 for closed writable streams (#501) (Thursday, 4 August)
• [whatwg/streams] Decide whether writer.ready should become writer.waitForDesiredSize() (#493) (Thursday, 4 August)
• Re: [whatwg/streams] Rename headings ID atrributes (#497) (Thursday, 4 August)
• Re: [whatwg/streams] Add an example of using desiredSize and ready with writable streams (#496) (Thursday, 4 August)
• Re: [whatwg/streams] Update spec to use ReadableStreamDefaultControllerErrorIfNeeded (#500) (Thursday, 4 August)
• Re: [whatwg/streams] Rename headings ID atrributes (#497) (Thursday, 4 August)
• Re: [whatwg/streams] Factor out state checking and ReadableStreamDefaultControllerError() call into a new abstract op (28c20b1) (Thursday, 4 August)
• Re: [whatwg/streams] Add an example of using desiredSize and ready with writable streams (#496) (Thursday, 4 August)
• Re: [whatwg/streams] Add an example of using desiredSize and ready with writable streams (#496) (Thursday, 4 August)
• [whatwg/streams] Add an example of using desiredSize and ready with writable streams (#496) (Thursday, 4 August)
• Re: [whatwg/streams] Synchronous (or asynchronous) state probing on WritableStream (#463) (Thursday, 4 August)
• [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) (Thursday, 4 August)
• Re: [whatwg/streams] Synchronous queue draining for WritableStream (#465) (Thursday, 4 August)
• Re: [whatwg/streams] Synchronous queue draining for WritableStream (#465) (Thursday, 4 August)
• Re: [whatwg/streams] Synchronous (or asynchronous) state probing on WritableStream (#463) (Thursday, 4 August)
• Re: [whatwg/streams] Implement flow-control in TransformStream fixes #330 maybe (#429) (Thursday, 4 August)
• Re: [whatwg/streams] Implement flow-control in TransformStream fixes #330 maybe (#429) (Thursday, 4 August)
• Re: [whatwg/streams] Separate out exported abstract ops from internal ones (#372) (Thursday, 4 August)
• Re: [whatwg/streams] Consider adding type assertions for all abstract operations (#453) (Thursday, 4 August)
• Re: [whatwg/streams] Consider adding type assertions for all abstract operations (#453) (Thursday, 4 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Thursday, 4 August)
• [whatwg/streams] Convert writable stream tests to web platform tests format (#492) (Thursday, 4 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Thursday, 4 August)
• Re: [whatwg/streams] Add totalSize caching to queue-with-size library (#491) (Thursday, 4 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Thursday, 4 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Thursday, 4 August)
• Re: [whatwg/streams] Performance improvements (#490) (Thursday, 4 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Wednesday, 3 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Wednesday, 3 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Wednesday, 3 August)
• Re: [whatwg/streams] Performance improvements (#490) (Wednesday, 3 August)
• Re: [whatwg/streams] Performance improvements (#490) (Wednesday, 3 August)
• Re: [whatwg/streams] Performance improvements (#490) (Wednesday, 3 August)
• Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Wednesday, 3 August)
• [w3c/webcomponents] Other named properties in shadow DOM (#536) (Wednesday, 3 August)
• Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Wednesday, 3 August)
• Re: [whatwg/dom] new Element(tagName)? (#287) (Wednesday, 3 August)
• Re: [whatwg/streams] Add totalSize caching to queue-with-size library (7215774) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] light weight transformations (#461) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Tuesday, 2 August)
• Re: [w3c/webcomponents] Ignore title attributes on <link rel=stylesheet> in shadow trees (#535) (Tuesday, 2 August)
• Re: [w3c/gamepad] Added GamepadPose (#25) (Monday, 1 August)
• Re: [w3c/webcomponents] Scripts in HTML Imports should be scoped to the import (treat imports as script modules) (bugzilla: 27836) (#157) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Add URL.createObjectURL(stream) support (#480) (Monday, 1 August)
• Re: [whatwg/streams] Repo/package confusion (#487) (Monday, 1 August)
• Re: [whatwg/streams] Repo/package confusion (#487) (Monday, 1 August)
• Re: [whatwg/streams] "ws.onend" (#482) (Monday, 1 August)
• Re: [whatwg/streams] Editorial changes to the socket example (#486) (Monday, 1 August)
• Re: [whatwg/streams] Editorial changes to the socket example (#486) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream() to drain all the available data (#489) (Monday, 1 August)
• Re: [w3c/gamepad] Added GamepadPose (#25) (Monday, 1 August)
• Re: [whatwg/encoding] "In equations, all numbers are integers, additio..." (#66) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Monday, 1 August)

Dominic Cooney

• [w3c/WebPlatformWG] Add Dominic Cooney to TPAC 2016 Mon, Fri attendees (#63) (Friday, 26 August)
• Re: [w3c/webcomponents] Move the check for HTMLElement and its subclass from customElements.define to construction timing (#541) (Tuesday, 16 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Tuesday, 16 August)
• Re: [w3c/webcomponents] Forbid reentrance to `customElements.define` (#545) (Tuesday, 16 August)
• Re: [whatwg/dom] The adopted callback should be passed the old and new document (#292) (Monday, 15 August)
• [whatwg/dom] The adopted callback should be passed the old and new document (#292) (Monday, 15 August)

Dominic Tarr

• Re: [whatwg/streams] light weight transformations (#461) (Tuesday, 23 August)
• Re: [whatwg/streams] light weight transformations (#461) (Tuesday, 23 August)
• Re: [whatwg/streams] light weight transformations (#461) (Thursday, 4 August)
• Re: [whatwg/streams] light weight transformations (#461) (Tuesday, 2 August)

Dominique Hazael-Massieux

• [w3ctag/spec-reviews] MediaStream Image Capture (#133) (Wednesday, 31 August)
• [w3ctag/spec-reviews] Audio Output Device APIs (#132) (Wednesday, 31 August)
• [w3ctag/spec-reviews] MediaStream Recorder (#131) (Wednesday, 31 August)
• [w3ctag/spec-reviews] Media Capture From DOM Element (#130) (Wednesday, 31 August)
• Re: [w3c/FileAPI] Improve readability of Blob-related statements (#42) (Thursday, 18 August)
• [w3c/selection-api] Fix normative references (#71) (Monday, 1 August)
• Re: [w3c/selection-api] Normative references (#69) (Monday, 1 August)

Doug

• Re: [w3c/webcomponents] [imports]: Respect the crossOrigin attribute (bugzilla: 25568) (#216) (Wednesday, 17 August)

dwoldrich

• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Monday, 22 August)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Wednesday, 10 August)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Wednesday, 10 August)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Tuesday, 9 August)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Tuesday, 2 August)

Ehsan Akhgari

• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Friday, 12 August)
• Re: [whatwg/dom] Consider banning insertNode() of the Range's start node (#63) (Monday, 8 August)

Eric Bidelman

• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Tuesday, 30 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Wednesday, 24 August)
• [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Wednesday, 24 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 9 August)

Erik Dahlström

• Re: [whatwg/dom] Remove SVGZoomEvent? (#283) (Monday, 8 August)

Ersagun Kuruca

• Re: [whatwg/url] Convenience method to return an Object (#143) (Wednesday, 17 August)

Florian Rivoal

• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)

Francisco Euzébio da Cruz

• [whatwg/xhr] spec.whatwg (#86) (Tuesday, 30 August)

Francisco Jordano

• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)

Francois Marier

• Re: [whatwg/fetch] Referrer policies: add the missing policies (fixes #342) (#346) (Wednesday, 10 August)

Gabriel Wicke

• Re: [whatwg/streams] light weight transformations (#461) (Friday, 5 August)
• Re: [whatwg/streams] Performance improvements (#490) (Wednesday, 3 August)
• [whatwg/streams] Performance improvements (#490) (Wednesday, 3 August)
• Re: [whatwg/streams] Performance improvements (#490) (Wednesday, 3 August)
• Re: [whatwg/streams] light weight transformations (#461) (Wednesday, 3 August)
• Re: [whatwg/streams] light weight transformations (#461) (Tuesday, 2 August)
• Re: [whatwg/streams] light weight transformations (#461) (Tuesday, 2 August)

Gary Kacmarcik

• Re: [w3c/editing] July 29th F2F Agenda Item - static ranges (#138) (Tuesday, 30 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Friday, 19 August)
• Re: [w3c/uievents] Fix #89. Make some of legacy UIEvents composed events (#93) (Wednesday, 3 August)
• Re: [w3c/uievents] Fix #89. Make some of legacy UIEvents composed events (#93) (Wednesday, 3 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Data and dataTransfer attributes (#139) (Monday, 1 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - static ranges (#138) (Monday, 1 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Dragging and dropping (#134) (Monday, 1 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Non-cancelable event 1of 2 (#137) (Monday, 1 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - History handling (undo/redo) (#136) (Monday, 1 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Clipboard events (#135) (Monday, 1 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Dragging and dropping (#134) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)

gked

• Re: [w3c/editing] Sections on contenteditable and designmode have insufficient discussion of keyboard accessibility (#127) (Tuesday, 23 August)
• Re: [w3c/editing] New API: Selection#makeVisible() (#129) (Thursday, 18 August)
• [w3c/selection-api] New API: Selection#makeVisible() (#73) (Thursday, 18 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Wednesday, 17 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Data and dataTransfer attributes (#139) (Monday, 15 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Dragging and dropping (#134) (Tuesday, 2 August)

Hadley Beeman

• Re: [w3ctag/spec-reviews] Data on the Web Best Practices (#135) (Wednesday, 31 August)
• [w3ctag/spec-reviews] Data on the Web Best Practices (#135) (Wednesday, 31 August)

Hakuno

• Re: [slightlyoff/ServiceWorker] Firefox buggy (#948) (Thursday, 11 August)
• Re: [slightlyoff/ServiceWorker] Firefox buggy (#948) (Wednesday, 10 August)
• [slightlyoff/ServiceWorker] Firefox buggy (#948) (Wednesday, 10 August)

Harald Alvestrand

• Re: [w3c/permissions] Remove object-based permissions (#42) (Tuesday, 30 August)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 26 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• [w3c/permissions] Resolve "issue-media-granted" (#119) (Wednesday, 10 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Wednesday, 10 August)

Hayato Ito

• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Wednesday, 31 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Tuesday, 30 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Tuesday, 30 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Tuesday, 30 August)
• Re: [w3c/webcomponents] Fix #556, make focus navigation work when shadow host's tabindex is -1 (#557) (Tuesday, 30 August)
• Re: [w3c/webcomponents] Fix #556, make focus navigation work when shadow host's tabindex is -1 (#557) (Tuesday, 30 August)
• Re: [w3c/webcomponents] Fix #556, make focus navigation work when shadow host's tabindex is -1 (#557) (Tuesday, 30 August)
• Re: [w3c/webcomponents] Fix #556, make focus navigation work when shadow host's tabindex is -1 (#557) (Tuesday, 30 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Tuesday, 30 August)
• Re: [w3c/touch-events] Add TouchEvent's retargeting steps (#73) (Monday, 29 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Monday, 29 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/touch-events] Add TouchEvent's retargeting steps (#73) (Thursday, 25 August)
• Re: [w3c/touch-events] Add TouchEvent's retargeting steps (#73) (Thursday, 25 August)
• [w3c/touch-events] Add TouchEvent's retargeting steps (#73) (Thursday, 25 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 25 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Wednesday, 24 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Wednesday, 24 August)
• Re: [w3c/webcomponents] DocumentOrShadowRoot.deepActiveElement (#104) (Tuesday, 23 August)
• Re: [w3c/webcomponents] Should I write new components backwards compatible with v0 API? (#549) (Tuesday, 23 August)
• Re: [whatwg/dom] Shadow: Rename "unclosed node" (#306) (Thursday, 18 August)
• Re: [whatwg/dom] Shadow: Rename "unclosed node" (#306) (Thursday, 18 August)
• [whatwg/dom] Shadow: Rename "unclosed node" (#306) (Thursday, 18 August)
• Re: [whatwg/dom] "unclosed node of node" reads confusingly (#285) (Thursday, 18 August)
• Re: [w3c/webcomponents] Ignore title attributes on <link rel=stylesheet> in shadow trees (#535) (Monday, 15 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Monday, 15 August)
• Re: [w3c/webcomponents] Change Bob's coffee drink from "green eye" to "red eye" (#539) (Wednesday, 10 August)
• Re: [whatwg/dom] "unclosed node of node" reads confusingly (#285) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 9 August)
• Re: [whatwg/dom] "unclosed node of node" reads confusingly (#285) (Tuesday, 9 August)
• Re: [whatwg/dom] Shadow: Add a hook for retargeting other attributes (#288) (Thursday, 4 August)
• Re: [whatwg/dom] Shadow: Add a hook for retargeting other attributes (#288) (Thursday, 4 August)
• Re: [whatwg/dom] Shadow: Add a hook for retargeting other attributes (#288) (Wednesday, 3 August)
• [whatwg/dom] Shadow: Add a hook for retargeting other attributes (#288) (Wednesday, 3 August)
• Re: [w3c/uievents] Fix #89. Make some of legacy UIEvents composed events (#93) (Wednesday, 3 August)
• Re: [whatwg/dom] Upstream Touch Events retargeting (#286) (Tuesday, 2 August)
• Re: [whatwg/dom] "unclosed node of node" reads confusingly (#285) (Monday, 1 August)
• [w3c/webcomponents] Ignore title attributes on <link ref=stylesheet> in shadow trees (#535) (Monday, 1 August)
• [whatwg/dom] Upstream Touch Events retargeting (#286) (Monday, 1 August)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Monday, 1 August)
• Re: [w3c/uievents] Fix #89. Make some of legacy UIEvents composed events (#93) (Monday, 1 August)
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Monday, 1 August)

Henri Sivonen

• Re: [whatwg/encoding] Consider adding "replacement" as a label for the replacement encoding (#70) (Wednesday, 24 August)
• Re: [whatwg/encoding] Consider adding "replacement" as a label for the replacement encoding (#70) (Wednesday, 24 August)
• [whatwg/encoding] Consider adding "replacement" as a label for the replacement encoding (#70) (Monday, 22 August)
• Re: [whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) (Thursday, 11 August)
• Re: [whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) (Thursday, 4 August)
• Re: [whatwg/encoding] Editorial: Clean up gb18030 math (#63) (Thursday, 4 August)
• Re: [whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) (Thursday, 4 August)
• Re: [whatwg/encoding] "In equations, all numbers are integers, additio..." (#66) (Thursday, 4 August)

Ian Pouncey

• [w3c/WebPlatformWG] Added myself as attendee (#64) (Friday, 26 August)

Ilya Grigorik

• Re: [whatwg/fetch] Delay opaque responses until response body is in (#355) (Friday, 5 August)
• Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 5 August)

Inian

• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Saturday, 27 August)

iTROJACK

• [whatwg/url] Bot.exe (#144) (Tuesday, 16 August)

Jake Archibald

• Re: [w3c/ServiceWorker] SW for multilingual website (#968) (Tuesday, 30 August)
• Re: [w3c/ServiceWorker] SW for multilingual website (#968) (Tuesday, 30 August)
• Re: [w3c/ServiceWorker] SW for multilingual website (#968) (Tuesday, 30 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Monday, 29 August)
• [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Monday, 29 August)
• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Friday, 26 August)
• Re: [w3c/ServiceWorker] Handle Fetch "shift+reload" (#952) (Friday, 26 August)
• Re: [w3c/ServiceWorker] consider exposing self.clients on window and other worker globals (#955) (Friday, 26 August)
• Re: [w3c/ServiceWorker] Add option to ignore case for cache querying (#956) (Friday, 26 August)
• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Friday, 26 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Friday, 26 August)
• Re: [w3c/ServiceWorker] Declarative url filters in `fetch` event (#949) (Friday, 26 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 26 August)
• Re: [w3c/ServiceWorker] notification of cancelled download? (#957) (Friday, 26 August)
• Re: [w3c/ServiceWorker] notification of cancelled download? (#957) (Friday, 26 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 22 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Thursday, 18 August)
• Re: [slightlyoff/ServiceWorker] Handling race conditions - API for accessing pending requests? (#959) (Thursday, 18 August)
• Re: [slightlyoff/ServiceWorker] Handling race conditions - API for accessing pending requests? (#959) (Thursday, 18 August)
• Re: [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Tuesday, 16 August)
• Re: [slightlyoff/ServiceWorker] Allow respondWith() to be called asynchronously or allow some way to cancel the response. (#836) (Sunday, 14 August)
• Re: [slightlyoff/ServiceWorker] Declarative url filters in `fetch` event (#949) (Friday, 12 August)
• Re: [whatwg/fetch] Aborting a fetch (#27) (Friday, 12 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Wednesday, 10 August)
• Re: [whatwg/fetch] Add From-Origin? (#365) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] Move service worker spec into w3c (#881) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Monday, 8 August)
• Re: [whatwg/fetch] Support for CSRF? (#256) (Monday, 8 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] Send correct Accept header with fetch() request (#945) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Send correct Accept header with fetch() request (#945) (Friday, 5 August)
• Re: [whatwg/fetch] Delay opaque responses until response body is in (#355) (Friday, 5 August)
• Re: [whatwg/fetch] Delay opaque responses until response body is in (#355) (Friday, 5 August)
• Re: [whatwg/fetch] Delay opaque responses until response body is in (#355) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache? (#941) (Friday, 5 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Thursday, 4 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Thursday, 4 August)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Thursday, 4 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Thursday, 4 August)
• Re: [whatwg/fetch] Passthrough original error response unless there's a security issue in doing so (#352) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Thursday, 4 August)
• Re: [whatwg/fetch] Does the spec suggest Fetch can only handle UTF-8 content? (#353) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Introduce `Service-Worker-Max-Age` header (#721) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Introduce `Service-Worker-Max-Age` header (#721) (Wednesday, 3 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Wednesday, 3 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Wednesday, 3 August)
• [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Wednesday, 3 August)
• [whatwg/fetch] Passthrough original error response unless there's a security issue in doing so (#352) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Wednesday, 3 August)
• Re: [whatwg/fetch] Fetch Streaming Intermediate Emissions (#349) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] How are unloaded tabs represented? (#626) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 3 August)
• Re: [whatwg/fetch] Fetch Streaming Intermediate Emissions (#349) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] Take control over the very first page (#938) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Take control over the very first page (#938) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 1 August)

James Craig

• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Tuesday, 30 August)
• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Tuesday, 30 August)
• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Tuesday, 30 August)

James Dalessio

• Re: [slightlyoff/ServiceWorker] Allow respondWith() to be called asynchronously or allow some way to cancel the response. (#836) (Sunday, 14 August)
• Re: [slightlyoff/ServiceWorker] Allow respondWith() to be called asynchronously or allow some way to cancel the response. (#836) (Sunday, 14 August)

James M Snell

• Re: [whatwg/url] Convenience method to return an Object (#143) (Wednesday, 17 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Tuesday, 9 August)
• Re: [whatwg/url] relative URLs (#136) (Saturday, 6 August)
• Re: [whatwg/url] relative URLs (#136) (Friday, 5 August)

Jan Miksovsky

• Re: [w3c/webcomponents] What's the expected behavior of a class with observedAttributes but no attributeChangedCallback? (#555) (Friday, 26 August)
• [w3c/webcomponents] What's the expected behavior of a class with observedAttributes but no attributeChangedCallback? (#555) (Friday, 26 August)

jan-ivar

• Re: [w3c/permissions] Passing base dictionary wont work. (#59) (Tuesday, 30 August)
• Re: [w3c/permissions] Passing base dictionary wont work. (#59) (Tuesday, 30 August)
• Re: [w3c/permissions] Passing base dictionary wont work. (#59) (Tuesday, 30 August)
• Re: [w3c/permissions] questions on query() (#124) (Tuesday, 30 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Monday, 29 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Saturday, 27 August)
• Re: [w3c/permissions] Drop .request() (#83) (Saturday, 27 August)
• Re: [w3c/permissions] Drop .request() (#83) (Saturday, 27 August)
• Re: [w3c/permissions] Drop .request() (#83) (Saturday, 27 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Saturday, 27 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Saturday, 27 August)
• Re: [w3c/permissions] Drop .request() (#83) (Saturday, 27 August)
• Re: [w3c/permissions] Drop .request() (#83) (Saturday, 27 August)
• Re: [w3c/permissions] Drop .request() (#83) (Saturday, 27 August)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 26 August)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 26 August)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 26 August)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 26 August)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 26 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Friday, 26 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Tuesday, 16 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Monday, 15 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Friday, 12 August)

Jason Kiss

• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Friday, 12 August)

Jeena Lee

• Re: [whatwg/fetch] Clarification on step 4 of Headers `delete` method (#372) (Tuesday, 23 August)
• Re: [whatwg/fetch] Clarification on step 4 of Headers `delete` method (#372) (Tuesday, 23 August)
• [whatwg/fetch] Clarification on step 4 of Headers `delete` method (#372) (Monday, 22 August)

Jeff Barczewski

• Re: [whatwg/fetch] Aborting a fetch (#27) (Thursday, 18 August)
• Re: [whatwg/fetch] Aborting a fetch (#27) (Thursday, 18 August)
• Re: [whatwg/fetch] Aborting a fetch (#27) (Thursday, 18 August)

Jeffrey Yasskin

• Re: [w3c/permissions] Passing base dictionary wont work. (#59) (Tuesday, 30 August)
• Re: [w3c/permissions] Passing base dictionary wont work. (#59) (Tuesday, 30 August)
• Re: [w3c/permissions] questions on query() (#124) (Tuesday, 30 August)
• Re: [w3c/permissions] Passing base dictionary wont work. (#59) (Tuesday, 30 August)
• [w3c/permissions] Pass objects instead of PermissionDescriptors to the Permissions interface. (#125) (Tuesday, 30 August)
• Re: [w3c/permissions] questions on query() (#124) (Tuesday, 30 August)
• Re: [w3c/permissions] questions on query() (#124) (Tuesday, 30 August)
• Re: [w3c/permissions] Drop .request() (#83) (Tuesday, 30 August)
• Re: [w3c/permissions] Drop .request() (#83) (Tuesday, 30 August)
• [w3c/permissions] deploy.sh doesn't fail for patches with bikeshed errors (#123) (Tuesday, 30 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Monday, 29 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Monday, 29 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Monday, 29 August)
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Monday, 29 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Monday, 29 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Monday, 29 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Monday, 29 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Monday, 29 August)
• Re: [w3c/permissions] Drop .request() (#83) (Sunday, 28 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Saturday, 27 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Saturday, 27 August)
• Re: [w3c/permissions] Drop .request() (#83) (Saturday, 27 August)
• Re: [w3c/permissions] Drop .request() (#83) (Saturday, 27 August)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 26 August)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 26 August)
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Friday, 26 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Friday, 26 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Friday, 26 August)
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Friday, 26 August)
• [w3c/permissions] refactor(media devices): use "allowed to use" (#122) (Friday, 26 August)
• Re: [w3c/permissions] Drop .request() (#83) (Thursday, 25 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Thursday, 25 August)
• Re: [whatwg/url] Update origin links now that HTML defines it with for=''. (#146) (Wednesday, 24 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Wednesday, 24 August)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Tuesday, 23 August)
• Re: [whatwg/url] Update origin links now that HTML defines it with for=''. (#146) (Tuesday, 23 August)
• [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Tuesday, 23 August)
• [whatwg/url] Update origin links now that HTML defines it with for=''. (#146) (Tuesday, 23 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Monday, 15 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Friday, 12 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Friday, 12 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• Re: [w3c/permissions] Resolve TODOs on media type permissions (#120) (Wednesday, 10 August)
• Re: [w3c/permissions] Resolve "issue-media-granted" (#119) (Wednesday, 10 August)
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Monday, 8 August)
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 5 August)
• Re: [w3c/permissions] Move the Permissions registry (#103) (Friday, 5 August)
• Re: [w3c/permissions] refactor: move permissions registry (closes #103) (#118) (Friday, 5 August)
• Re: [heycam/webidl] Provide a concise syntax to create IDL dictionaries from prose (#142) (Friday, 5 August)
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 5 August)
• Re: [w3c/permissions] feat(algorithms): allow calling with a PermissionName (#115) (Friday, 5 August)
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Thursday, 4 August)
• Re: [w3c/permissions] feat(algorithms): allow calling with a PermissionName (#115) (Thursday, 4 August)
• [heycam/webidl] Provide a concise syntax to create IDL dictionaries from prose (#142) (Thursday, 4 August)
• Re: [w3ctag/packaging-on-the-web] Why not the non-zip formats? (#31) (Wednesday, 3 August)
• [w3ctag/packaging-on-the-web] Turn on HTTPS (#32) (Tuesday, 2 August)
• [w3ctag/packaging-on-the-web] Why not the non-zip formats? (#31) (Tuesday, 2 August)
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Tuesday, 2 August)
• [w3c/permissions] feat(state): delegate to features for constraints (#117) (Tuesday, 2 August)

jfw7

• [w3c/webcomponents] Change Bob's coffee drink from "green eye" to "red eye" (#539) (Tuesday, 9 August)
• [w3c/webcomponents] Broken wikipedia link for "Green Eye" (#538) (Tuesday, 9 August)

Jimmy Karl Roland Wärting

• [whatwg/fetch] Request should allow WritableStream as body (#378) (Monday, 29 August)
• Re: [whatwg/streams] piping issue (#509) (Thursday, 25 August)
• [whatwg/streams] piping issue (#509) (Thursday, 25 August)
• Re: [whatwg/streams] can streams be transferred via postMessage()? (#276) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)
• Re: [whatwg/fetch] Fetch would silently ignore the input body if it's not an existing data type? (#371) (Friday, 19 August)

Johannes Wilm

• Re: [w3c/editing] July 29th F2F Agenda Item - static ranges (#138) (Tuesday, 30 August)
• Re: [w3c/editing] Should contenteditable have break-word behavior by default? (#145) (Tuesday, 30 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)
• Re: [w3c/editing] RESOLUTION: have a relatedEvent to point to the UI event that caused a DI event to be fired (#82) (Thursday, 25 August)
• Re: [w3c/editing] RESOLUTION: have a relatedEvent to point to the UI event that caused a DI event to be fired (#82) (Thursday, 25 August)
• Re: [w3c/editing] [beforeinput] Should we allow canceling the committed text from IME? (#128) (Thursday, 25 August)
• Re: [w3c/editing] [beforeinput] Should we allow canceling the committed text from IME? (#128) (Thursday, 25 August)
• Re: [w3c/editing] How to combine data and transferData attributes? (#131) (Thursday, 25 August)
• Re: [w3c/editing] How to combine data and transferData attributes? (#131) (Thursday, 25 August)
• Re: [w3c/editing] beforeInput/input events should be fired for any element with contentEditable enabled, input and textArea elements where input element and textArea will have targetRanges set to null. (#96) (Thursday, 25 August)
• Re: [w3c/editing] beforeInput/input events should be fired for any element with contentEditable enabled, input and textArea elements where input element and textArea will have targetRanges set to null. (#96) (Thursday, 25 August)
• Re: [w3c/editing] Add a mechanism to opt-in/opt-out editing features (#93) (Thursday, 25 August)
• Re: [w3c/editing] Add a mechanism to opt-in/opt-out editing features (#93) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Opt-in/opt-out of editing features and menus (#141) (Thursday, 25 August)
• Re: [w3c/editing] Determine what kind of object is exposed on beforeInput/input events (#92) (Thursday, 25 August)
• Re: [w3c/editing] Determine what kind of object is exposed on beforeInput/input events (#92) (Thursday, 25 August)
• Re: [w3c/editing] RESOLUTION: We will ask the accessibility people to look at IMEs and the problems we should have considered here but didn’t. (#83) (Thursday, 25 August)
• Re: [w3c/editing] RESOLUTION: We will ask the accessibility people to look at IMEs and the problems we should have considered here but didn’t. (#83) (Thursday, 25 August)
• Re: [w3c/editing] Cancelable attribute should be removed from the spec because it already referenced in Event.idl (#100) (Thursday, 25 August)
• Re: [w3c/editing] Cancelable attribute should be removed from the spec because it already referenced in Event.idl (#100) (Thursday, 25 August)
• Re: [w3c/editing] inputType should be tied to the command names and having that tied to a way of declaring what you support (#110) (Thursday, 25 August)
• Re: [w3c/editing] inputType should be tied to the command names and having that tied to a way of declaring what you support (#110) (Thursday, 25 August)
• Re: [w3c/editing] inputType for Menu Bar>Edit>Delete (no obvious direction) (#130) (Thursday, 25 August)
• Re: [w3c/editing] inputType for Menu Bar>Edit>Delete (no obvious direction) (#130) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Dragging and dropping (#134) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Clipboard events (#135) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Dragging and dropping (#134) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Non-cancelable event 1of 2 (#137) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Non-cancelable event 1of 2 (#137) (Thursday, 25 August)
• Re: [w3c/editing] [beforeinput] Rename drag&drop to deleteByDrag&insertFromDrop (#147) (Thursday, 25 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Thursday, 25 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Thursday, 25 August)
• Re: [w3c/editing] [beforeinput] Rename drag&drop to deleteByDrag&insertFromDrop (#147) (Thursday, 25 August)
• Re: [w3c/editing] [beforeinput] Add InputType 'deleteByKill', 'insertFromYank' and 'transpose' (#148) (Thursday, 25 August)
• Re: [w3c/editing] [beforeinput] Add InputType 'deleteByKill', 'insertFromYank' and 'transpose' (#148) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Non-cancelable event 2 of 2 (#140) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Data and dataTransfer attributes (#139) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Non-cancelable event 2 of 2 (#140) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Data and dataTransfer attributes (#139) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - History handling (undo/redo) (#136) (Thursday, 25 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - History handling (undo/redo) (#136) (Thursday, 25 August)
• Re: [w3c/editing] Do we need to spec device specific events? (#62) (Thursday, 25 August)
• Re: [w3c/editing] Do we need to spec device specific events? (#62) (Thursday, 25 August)
• Re: [w3c/editing] Should Device-Specific Edit Events say what Device-Independent Edit Event they will cause? (#25) (Thursday, 25 August)
• Re: [w3c/editing] Should Device-Specific Edit Events say what Device-Independent Edit Event they will cause? (#25) (Thursday, 25 August)
• Re: [w3c/editing] Track the source of Intentions (#19) (Thursday, 25 August)
• Re: [w3c/editing] Track the source of Intentions (#19) (Thursday, 25 August)
• Re: [w3c/editing] [beforeinput] InputType for MacOS Transpose (ctrl-t) (#148) (Wednesday, 24 August)
• Re: [w3c/editing] [beforeinput] InputType for MacOS Transpose (ctrl-t) (#148) (Wednesday, 24 August)
• Re: [w3c/editing] [beforeinput] InputType for MacOS Transpose (ctrl-t) (#148) (Wednesday, 24 August)
• Re: [w3c/editing] [beforeinput] InputType for MacOS Transpose (ctrl-t) (#148) (Wednesday, 24 August)
• Re: [w3c/editing] [beforeinput] Rename drag&drop to deleteByDrag&insertFromDrop (#147) (Wednesday, 24 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Wednesday, 24 August)
• Re: [w3c/editing] [beforeinput] Rename drag&drop to deleteByDrag&insertFromDrop (#147) (Wednesday, 24 August)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Wednesday, 24 August)
• Re: [w3c/WebPlatformWG] Add Johannes Wilm to attendees (#62) (Tuesday, 23 August)
• [w3c/WebPlatformWG] Add Johannes Wilm to attendees (#62) (Tuesday, 23 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Friday, 19 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Friday, 19 August)
• Re: [w3c/editing] New API: Selection#makeVisible() (#129) (Thursday, 18 August)
• Re: [w3c/editing] New API: Selection#makeVisible() (#129) (Thursday, 18 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Thursday, 18 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Thursday, 18 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Wednesday, 17 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Wednesday, 17 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Wednesday, 17 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Tuesday, 16 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Tuesday, 16 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Tuesday, 16 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Tuesday, 16 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Tuesday, 16 August)
• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Tuesday, 16 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Data and dataTransfer attributes (#139) (Monday, 15 August)
• [w3c/uievents] definition for "dispatch" shouldn't be in the UI events spec (#106) (Monday, 15 August)
• [w3c/uievents] When beforeinput/input events are fired seems "strange" (#105) (Monday, 15 August)
• Re: [w3c/uievents] Events do not have "default action"s (#104) (Monday, 15 August)
• Re: [w3c/uievents] Events do not have "default action"s (#104) (Monday, 15 August)
• [w3c/uievents] Events do not have "default action"s (#104) (Monday, 15 August)
• Re: [w3c/uievents] Events do not have "default action"s (#104) (Monday, 15 August)
• Re: [w3c/uievents] Events do not have "default action"s (#104) (Monday, 15 August)
• Re: [w3c/uievents] Events do not have "default action"s (#104) (Monday, 15 August)
• Re: [w3c/uievents] Events do not have "default action"s (#104) (Monday, 15 August)
• Re: [w3c/uievents] Events do not have "default action"s (#104) (Monday, 15 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Sunday, 14 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Sunday, 14 August)
• Re: [w3c/editing] July 29th F2F Agenda Item - Data and dataTransfer attributes (#139) (Saturday, 13 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] deleteContentForward/Backward doesn't specify behavior for deletion of non-collapsed selection (#143) (Monday, 1 August)
• [w3c/editing] deleteContentForward/Backward doesn't specify behavior for deletion of non-collapsed selection (#143) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)

John-David Dalton

• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Friday, 26 August)
• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Friday, 26 August)
• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Friday, 26 August)
• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Friday, 26 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)

Jon Walsh

• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 27 August)

Jonas Sicking

• Re: [w3c/IndexedDB] Integrate with window.onerror (#49) (Wednesday, 3 August)
• Re: [w3c/IndexedDB] Integrate with window.onerror (#49) (Monday, 1 August)

Joseph Orbegoso Pea

• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Wednesday, 31 August)
• Re: [w3c/webcomponents] [idea] slottedCallback for Custom Elements (#527) (Wednesday, 31 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Wednesday, 31 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Tuesday, 30 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Monday, 29 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Monday, 29 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Monday, 29 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Monday, 29 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade. (#559) (Monday, 29 August)
• Re: [w3c/webcomponents] How to wait for will-be custom elements to be upgraded? (#558) (Monday, 29 August)
• [w3c/webcomponents] [IDEA] Asynchronous upgrade. (#559) (Monday, 29 August)
• [w3c/webcomponents] How to wait for will-be custom elements to be upgraded? (#558) (Monday, 29 August)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Wednesday, 24 August)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Wednesday, 24 August)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Wednesday, 24 August)
• [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Monday, 22 August)
• Re: [w3c/webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Sunday, 21 August)
• Re: [w3c/webcomponents] Should I write new components backwards compatible with v0 API? (#549) (Saturday, 20 August)
• Re: [w3c/webcomponents] Should I write new components backwards compatible with v0 API? (#549) (Saturday, 20 August)
• [w3c/webcomponents] Should I write new components backwards compatible with v0 API? (#549) (Saturday, 20 August)
• Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) (Saturday, 6 August)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 2 August)

Josh Matthews

• Re: [slightlyoff/ServiceWorker] Firefox buggy (#948) (Wednesday, 10 August)
• [whatwg/fetch] Why does the Header fill algorithm require copying the header list? (#360) (Tuesday, 9 August)
• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Tuesday, 9 August)
• Re: [whatwg/fetch] A request needs to be created with a URL (#359) (Tuesday, 9 August)
• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Tuesday, 9 August)
• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Tuesday, 9 August)
• Re: [whatwg/fetch] Request's current url is undefined for a new request (#351) (Thursday, 4 August)
• [whatwg/fetch] Request's current url is undefined for a new request (#351) (Wednesday, 3 August)

Joshua Bell

• [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Tuesday, 30 August)
• Re: [w3c/IndexedDB] Gather developer feedback on new spec additions (#65) (Monday, 29 August)
• [w3c/IndexedDB] Error events from open/deleteDatabase requests - cancelable? bubbles? (#86) (Monday, 29 August)
• Re: [w3c/FileAPI] Race condition in Introduction example (#48) (Wednesday, 24 August)
• Re: [w3c/IndexedDB] transaction should either take DOMStringList or DOMStringList needs to be iterable (#85) (Sunday, 21 August)
• Re: [w3c/IndexedDB] transaction should either take DOMStringList or DOMStringList needs to be iterable (#85) (Sunday, 21 August)
• Re: [w3c/IndexedDB] transaction should either take DOMStringList or DOMStringList needs to be iterable (#85) (Saturday, 20 August)
• Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Friday, 19 August)
• Re: [w3c/IndexedDB] DOMStringList has been removed from DOM (#28) (Friday, 5 August)
• Re: [w3c/IndexedDB] DOMStringList has been removed from DOM (#28) (Thursday, 4 August)
• [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache? (#942) (Thursday, 4 August)
• [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache (#941) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache? (#941) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] (duplicate) (#942) (Thursday, 4 August)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Thursday, 4 August)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Thursday, 4 August)
• Re: [w3c/IndexedDB] Integrate with window.onerror (#49) (Wednesday, 3 August)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Tuesday, 2 August)
• [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Monday, 1 August)
• Re: [slightlyoff/ServiceWorker] Block 206s entering the cache (via put & addAll) (#937) (Monday, 1 August)
• Re: [w3c/IndexedDB] Integrate with window.onerror (#49) (Monday, 1 August)
• Re: [w3c/IndexedDB] Naming for "v2" ? (#82) (Monday, 1 August)
• Re: [w3c/IndexedDB] Naming for "v2" ? (#82) (Monday, 1 August)

ju-lien

• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Wednesday, 24 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)

Julian Reschke

• Re: [whatwg/fetch] Possible typo in header value definition (#332) (Wednesday, 10 August)

Jungkee Song

• Re: [whatwg/fetch] Remove response's cache state concept (8d343bb) (Friday, 26 August)
• [whatwg/fetch] Use of response's cache state (#376) (Friday, 26 August)
• Re: [whatwg/fetch] Remove response's cache state concept (8d343bb) (Friday, 26 August)
• Re: [whatwg/fetch] Remove response's cache state concept (8d343bb) (Friday, 26 August)
• Re: [whatwg/fetch] Remove response's cache state concept (8d343bb) (Friday, 26 August)
• Re: [w3c/ServiceWorker] Change the rest of the links to the new repo (#961) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] Change the rest of the links to the new repo (#961) (Wednesday, 24 August)
• Re: [w3c/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 23 August)
• Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Monday, 22 August)
• Re: [slightlyoff/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Thursday, 18 August)
• Re: [slightlyoff/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Thursday, 18 August)
• Re: [slightlyoff/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Thursday, 18 August)
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 16 August)
• Re: [slightlyoff/ServiceWorker] "or its equivalent" (#953) (Tuesday, 16 August)
• Re: [slightlyoff/ServiceWorker] "or its equivalent" (#953) (Tuesday, 16 August)
• Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Friday, 12 August)
• Re: [slightlyoff/ServiceWorker] Tidy up global object usage (#950) (Thursday, 11 August)
• Re: [slightlyoff/ServiceWorker] Tidy up global object usage (#950) (Thursday, 11 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Thursday, 11 August)
• Re: [slightlyoff/ServiceWorker] Should waitUntil() fast fail if a single extension promise rejects? (#936) (Thursday, 11 August)
• Re: [whatwg/fetch] Move 401/407 to HTTP-network-or-cache fetch (#363) (Wednesday, 10 August)
• Re: [whatwg/fetch] Move 401/407 to HTTP-network-or-cache fetch (#363) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] clarify that Clients.matchAll() only returns Window Client objects with active documents (#888) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] Unregister algorithm step 6.1 is no longer necessary (#855) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Tuesday, 9 August)
• Re: [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache? (#941) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache? (#941) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache? (#941) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache? (#941) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Wednesday, 3 August)
• Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) (Tuesday, 2 August)
• [whatwg/fetch] OCSP fetches bypass service worker (#347) (Tuesday, 2 August)

Justin Fagnani

• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 25 August)

Katelyn Gadd

• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Tuesday, 23 August)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Monday, 22 August)

Kearwood Gilbert

• Re: [w3c/gamepad] Added GamepadPose (#25) (Tuesday, 2 August)
• Re: [w3c/gamepad] Added GamepadPose (#25) (Tuesday, 2 August)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] fix(display modes): refine standalone (closes #495) (#496) (Friday, 26 August)
• Re: [w3c/manifest] doc(extensibility): e.g., of site verificaton (closes #476) (#497) (Friday, 26 August)
• Re: [w3c/manifest] WIP: purpose (#493) (Thursday, 25 August)
• Re: [w3c/manifest] WIP: purpose (#493) (Thursday, 25 August)
• Re: [w3c/manifest] WIP: purpose (#493) (Thursday, 25 August)
• Re: [w3c/manifest] WIP: purpose (#493) (Thursday, 25 August)
• Re: [w3c/manifest] WIP: purpose (#493) (Thursday, 25 August)
• Re: [w3c/manifest] WIP: purpose (#493) (Thursday, 25 August)
• Re: [w3c/manifest] feat(screenshots): Add screenshots member (closes #477) (#490) (Thursday, 25 August)
• Re: [w3c/manifest] Add screenshots object (#477) (Thursday, 25 August)
• Re: [w3c/manifest] feat(screenshots): Add screenshots member (closes #477) (#490) (Thursday, 25 August)
• Re: [w3c/manifest] feat(platform): allow platform on image obj (closes #361) (#491) (Thursday, 25 August)
• Re: [w3c/manifest] feat(platform): allow platform on image obj (closes #361) (#491) (Thursday, 25 August)
• Re: [w3c/manifest] feat(platform): allow platform on image obj (closes #361) (#491) (Thursday, 25 August)
• Re: [w3c/manifest] [Example] Make Racer 2k example from future (#487) (Friday, 12 August)
• Re: [w3c/manifest] [Example] Make Racer 2k example from future (#487) (Friday, 12 August)
• Re: [w3c/manifest] refactor: install steps (#485) (Tuesday, 9 August)
• Re: [w3c/manifest] refactor: install steps (#485) (Tuesday, 9 August)
• Re: [w3c/manifest] fix: transition URLs to TLS (#482) (Wednesday, 3 August)
• Re: [w3c/manifest] fix: transition URLs to TLS (#482) (Wednesday, 3 August)

Koji Ishii

• Re: [w3c/webcomponents] How to wait for will-be custom elements to be upgraded? (#558) (Tuesday, 30 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] "The problematic position" when Custom Elements throw errors? (#547) (Tuesday, 23 August)
• Re: [w3c/webcomponents] Rename interface CustomElementsRegistry to CustomElementRegistry (#548) (Tuesday, 23 August)
• Re: [w3c/webcomponents] "The problematic position" when Custom Elements throw errors? (#547) (Monday, 22 August)
• Re: [w3c/webcomponents] "The problematic position" when Custom Elements throw errors? (#547) (Monday, 22 August)
• [w3c/webcomponents] "The problematic position" when Custom Elements throw errors? (#547) (Friday, 19 August)
• Re: [w3c/webcomponents] Move the check for HTMLElement and its subclass from customElements.define to construction timing (#541) (Monday, 15 August)
• Re: [w3c/selection-api] Selection events for text controls (#53) (Saturday, 13 August)
• Re: [w3c/webcomponents] Steps in element definition that throw an exception should abort (#543) (Thursday, 11 August)
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Monday, 1 August)

leolux

• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Wednesday, 3 August)
• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Wednesday, 3 August)
• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Wednesday, 3 August)

Lewis Phạm

• [slightlyoff/ServiceWorker] Take control over the very first page (#938) (Monday, 1 August)

littledan

• Re: [heycam/webidl] "get a copy of the bytes held by the buffer source" should not fail for detached buffers (#151) (Wednesday, 24 August)

Lukasz Olejnik

• Re: [w3ctag/spec-reviews] privacy of sensor other exotic APIs (#129) (Thursday, 11 August)

Léonie Watson

• [w3c/FileAPI] Update editors info (#50) (Sunday, 28 August)
• [w3c/FileAPI] Update feedback info (#49) (Sunday, 28 August)
• Re: [w3c/WebPlatformWG] Added myself as attendee (#64) (Friday, 26 August)
• Re: [w3c/WebPlatformWG] Add Dominic Cooney to TPAC 2016 Mon, Fri attendees (#63) (Friday, 26 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Wednesday, 24 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Wednesday, 24 August)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Wednesday, 24 August)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Wednesday, 24 August)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Wednesday, 24 August)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Wednesday, 24 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Wednesday, 24 August)
• Re: [w3c/gamepad] Snapshot API as "Version 1" CR (#31) (Tuesday, 23 August)
• Re: [w3c/WebPlatformWG] CFC to publish WebIDL-1 as a Proposed Recommendation (#61) (Tuesday, 23 August)
• Re: [w3c/WebPlatformWG] CFC to publish WebIDL-1 as a Proposed Recommendation (#61) (Tuesday, 23 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Sunday, 21 August)
• [w3c/WebPlatformWG] CFC to publish WebIDL-1 as a Proposed Recommendation (#61) (Tuesday, 16 August)
• [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Friday, 12 August)
• Re: [w3c/IndexedDB] CFC: Publish FPWD of IndexedDB 2.0 (#84) (Thursday, 11 August)
• Re: [w3c/IndexedDB] CFC: Publish FPWD of IndexedDB 2.0 (#84) (Thursday, 11 August)
• [w3c/IndexedDB] CFC: Publish FPWD of IndexedDB 2.0 (#84) (Wednesday, 3 August)

Maciej Hirsz

• [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Friday, 19 August)

Madara Uchiha

• Re: [whatwg/dom] get rid of NonElementParentNode? (#298) (Tuesday, 16 August)

Malisa

• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Tuesday, 9 August)
• Re: [whatwg/fetch] Unclear intent in steps 29, 34.3, and 36 of the Request constructor (#358) (Tuesday, 9 August)
• [whatwg/fetch] Unclear intent in steps 29 and 34.3 of the Request constructor (#358) (Monday, 8 August)
• Re: [whatwg/fetch] The comma-delimited combined value definition does not support Set-Cookie headers (#345) (Thursday, 4 August)
• Re: [whatwg/fetch] The comma-delimited combined value definition does not support Set-Cookie headers (#345) (Thursday, 4 August)
• [whatwg/fetch] Default value for ByteString in ResponseInit should be removed (#348) (Tuesday, 2 August)

Marc Larue

• Re: [whatwg/fetch] Remove Headers (#368) (Friday, 12 August)
• [whatwg/fetch] Remove Headers (#368) (Thursday, 11 August)
• Re: [whatwg/xhr] Remove any headers (#83) (Thursday, 11 August)
• [whatwg/xhr] Remove any headers (#83) (Thursday, 11 August)

Marcos Cáceres

• Re: [w3c/manifest] fix(display modes): refine standalone (closes #495) (#496) (Friday, 26 August)
• Re: [w3c/manifest] fix(display modes): refine standalone (closes #495) (#496) (Friday, 26 August)
• [w3c/manifest] doc(extensibility): e.g., of site verificaton (closes #476) (#497) (Friday, 26 August)
• Re: [w3c/manifest] deprecate gh-pages in favor of echidna (#494) (Friday, 26 August)
• Re: [w3c/manifest] fix(display modes): refine standalone (closes #495) (#496) (Friday, 26 August)
• [w3c/manifest] fix(display modes): refine standalone (closes #495) (#496) (Friday, 26 August)
• Re: [w3c/manifest] Standalone description not accurate (#495) (Friday, 26 August)
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Thursday, 25 August)
• [w3c/manifest] WIP: purpose (#493) (Thursday, 25 August)
• Re: [w3c/manifest] feat(screenshots): Add screenshots member (closes #477) (#490) (Thursday, 25 August)
• Re: [w3c/manifest] feat(platform): allow platform on image obj (closes #361) (#491) (Thursday, 25 August)
• Re: [w3c/manifest] feat(platform): allow platform on image obj (closes #361) (#491) (Thursday, 25 August)
• Re: [w3c/manifest] feat(platform): allow platform on image obj (closes #361) (#491) (Thursday, 25 August)
• Re: [w3c/manifest] feat(platform): allow platform on image obj (closes #361) (#491) (Thursday, 25 August)
• Re: [w3c/manifest] Ability to define platform-specific icon/splash style (#361) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] Change the rest of the links to the new repo (#961) (Thursday, 25 August)
• Re: [w3c/ServiceWorker] Change the rest of the links to the new repo (#961) (Thursday, 25 August)
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Thursday, 25 August)
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Thursday, 25 August)
• Re: [w3c/manifest] Drop gh-pages branch (#492) (Thursday, 25 August)
• Re: [w3c/manifest] Drop gh-pages branch (#492) (Thursday, 25 August)
• Re: [w3c/manifest] Drop gh-pages branch (#492) (Thursday, 25 August)
• [w3c/manifest] Drop gh-pages branch (#492) (Thursday, 25 August)
• Re: [w3c/manifest] feat(platform): allow platform on image obj (closes #361) (#491) (Thursday, 25 August)
• [w3c/manifest] feat(platform): allow platform on image obj (closes #361) (#491) (Thursday, 25 August)
• Re: [w3c/manifest] Ability to define platform-specific icon/splash style (#361) (Thursday, 25 August)
• Re: [w3c/manifest] feat(screenshots): Add screenshots member (closes #477) (#490) (Thursday, 25 August)
• Re: [w3c/manifest] feat(screenshots): Add screenshots member (closes #477) (#490) (Thursday, 25 August)
• Re: [w3c/manifest] feat(screenshots): Add screenshots member (closes #477) (#490) (Thursday, 25 August)
• [w3c/manifest] feat(screenshots): Add screenshots member (closes #477) (#490) (Thursday, 25 August)
• Re: [w3c/manifest] Add screenshots object (#477) (Thursday, 25 August)
• Re: [w3c/manifest] Status section has misleading info on filing bugs (#489) (Thursday, 25 August)
• Re: [w3c/manifest] Redundant reference to ISO 3166? (#488) (Thursday, 25 August)
• Re: [w3c/manifest] Redundant reference to ISO 3166? (#488) (Thursday, 25 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Wednesday, 24 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Wednesday, 24 August)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Friday, 19 August)
• Re: [w3c/manifest] Add screenshots object (#477) (Wednesday, 17 August)
• Re: [w3c/manifest] Add screenshots object (#477) (Wednesday, 17 August)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Wednesday, 17 August)
• Re: [w3c/manifest] Add screenshots object (#477) (Wednesday, 17 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Tuesday, 16 August)
• Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Monday, 15 August)
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Monday, 15 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Monday, 15 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Monday, 15 August)
• Re: [w3c/manifest] Discoverability of metadata in web application manifest (#486) (Monday, 15 August)
• Re: [w3c/manifest] Discoverability of metadata in web application manifest (#486) (Monday, 15 August)
• Re: [w3c/manifest] Discoverability of metadata in web application manifest (#486) (Monday, 15 August)
• Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Monday, 15 August)
• [heycam/webidl] Remove mention of OMG IDL (#144) (Friday, 12 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Friday, 12 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Friday, 12 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Thursday, 11 August)
• Re: [w3c/manifest] refactor: install steps (#485) (Tuesday, 9 August)
• Re: [w3c/manifest] Installation doesnt define task source (#484) (Tuesday, 9 August)
• Re: [w3c/manifest] refactor: install steps (#485) (Tuesday, 9 August)
• Re: [w3c/manifest] refactor: install steps (#485) (Tuesday, 9 August)
• [w3c/manifest] refactor: install steps (#485) (Tuesday, 9 August)
• [w3c/manifest] Installation doesnt define task source (#484) (Tuesday, 9 August)
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Tuesday, 9 August)
• [heycam/webidl] docs(README): contributing section (closes #136) (#143) (Monday, 8 August)
• Re: [w3c/permissions] Flesh out request("geolocation") (#112) (Monday, 8 August)
• Re: [w3c/permissions] Flesh out request("geolocation") (#112) (Monday, 8 August)
• Re: [w3c/manifest] Fix: fetch things properly (closes #481 #465) (#483) (Friday, 5 August)
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Friday, 5 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Friday, 5 August)
• Re: [w3c/manifest] Fix: fetch things properly (closes #481 #465) (#483) (Friday, 5 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [w3c/manifest] Fix: fetch things properly (closes #481 #465) (#483) (Thursday, 4 August)
• [w3c/manifest] Fix: fetch things properly (closes #481 #465) (#483) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)
• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Thursday, 4 August)
• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Thursday, 4 August)
• Re: [w3c/permissions] refactor: move permissions registry (closes #103) (#118) (Wednesday, 3 August)
• [w3c/permissions] refactor: move permissions registry (closes #103) (#118) (Wednesday, 3 August)
• Re: [w3c/permissions] Remove object-based permissions (#42) (Wednesday, 3 August)
• Re: [w3c/permissions] feat(algorithms): allow calling with a PermissionName (#115) (Wednesday, 3 August)
• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Wednesday, 3 August)
• Re: [w3ctag/spec-reviews] Notifications API (#94) (Wednesday, 3 August)
• Re: [w3c/manifest] fix: transition URLs to TLS (#482) (Wednesday, 3 August)
• Re: [w3c/manifest] fix: transition URLs to TLS (#482) (Wednesday, 3 August)
• Re: [w3c/manifest] fix: transition URLs to TLS (#482) (Wednesday, 3 August)
• [w3c/manifest] fix: transition URLs to TLS (#482) (Wednesday, 3 August)

Marijn Kruisselbrink

• Re: [w3c/ServiceWorker] Replace e.g. with i.e. (#970) (Wednesday, 31 August)
• Re: [w3c/ServiceWorker] Lots of bikeshed usage issues (#965) (Monday, 29 August)
• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Friday, 26 August)
• Re: [w3c/FileAPI] Race condition in Introduction example (#48) (Tuesday, 23 August)
• Re: [slightlyoff/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18) (Monday, 22 August)
• Re: [whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339) (Monday, 22 August)
• Re: [w3c/FileAPI] Improve readability of Blob-related statements (#42) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] cache.match should create partial responses if given a range request (#913) (Wednesday, 17 August)
• Re: [w3c/FileAPI] Improve readability of Blob-related statements (#42) (Wednesday, 17 August)
• Re: [w3c/FileAPI] Improve readability of Blob-related statements (#42) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] Match Service Worker Registration has broken matching algorithm (#954) (Friday, 12 August)
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Tuesday, 9 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 8 August)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 8 August)
• Re: [slightlyoff/ServiceWorker] Send correct Accept header with fetch() request (#945) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Send correct Accept header with fetch() request (#945) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache (#941) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Thursday, 4 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 3 August)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Tuesday, 2 August)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Tuesday, 2 August)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Tuesday, 2 August)
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Tuesday, 2 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 2 August)

Mark Nottingham

• [whatwg/fetch] Go deeper into HTTP caching (#373) (Wednesday, 24 August)
• Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41) (Wednesday, 24 August)
• Re: [whatwg/fetch] Vary HTTP cache on credentials mode (#307) (Wednesday, 17 August)
• Re: [whatwg/fetch] Add From-Origin? (#365) (Thursday, 11 August)
• Re: [whatwg/fetch] Status code to use in a response indicating rejection of a cross-origin access (#172) (Tuesday, 2 August)

Martin Thomson

• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Monday, 15 August)
• Re: [w3c/permissions] Flesh out request("geolocation") (#112) (Monday, 8 August)

Mathias Bynens

• Re: [whatwg/storage] Exposing cross-origin resource size (#31) (Tuesday, 2 August)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Wednesday, 31 August)

Matthew Phillips

• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 25 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Wednesday, 24 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 2 August)
• Re: [w3c/webcomponents] Scripts in HTML Imports should be scoped to the import (treat imports as script modules) (bugzilla: 27836) (#157) (Monday, 1 August)

Megan Lindsay

• Re: [w3ctag/spec-reviews] WebVR (#106) (Wednesday, 10 August)

Michael van Ouwerkerk

• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 8 August)

michael-n-cooper

• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Tuesday, 30 August)

Michael[tm] Smith

• Re: [w3c/ServiceWorker] Add URL to GitHub repo (#967) (Monday, 29 August)
• Re: [w3c/ServiceWorker] Add URL to GitHub repo (#967) (Monday, 29 August)

Michiel Bijl

• Re: [w3ctag/spec-reviews] ARIA (#107) (Friday, 19 August)

Mike Taylor

• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Wednesday, 17 August)

Mike West

• Re: [whatwg/fetch] Block additional script MIMETypes (audio, video, csv) (#379) (Tuesday, 30 August)
• Re: [whatwg/fetch] Block additional script MIMETypes (audio, video, csv) (#379) (Tuesday, 30 August)
• Re: [whatwg/fetch] Block additional script MIMETypes (audio, video, csv) (#379) (Tuesday, 30 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• [whatwg/fetch] Editorial: Add Bikeshed metadata for 'request' (#370) (Wednesday, 17 August)
• Re: [whatwg/fetch] Adding bikeshed metadata to Methods, Headers, Statuses, and Bodies. (#356) (Friday, 5 August)
• Re: [whatwg/fetch] Adding bikeshed metadata to Methods, Headers, Statuses, and Bodies. (#356) (Friday, 5 August)
• Re: [whatwg/fetch] Adding bikeshed metadata to Methods, Headers, Statuses, and Bodies. (#356) (Friday, 5 August)
• [whatwg/fetch] Adding bikeshed metadata to Methods, Headers, Statuses, and Bodies. (#356) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache? (#941) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Why does CacheStorage have [SecureContext] but not Cache? (#941) (Friday, 5 August)

Mikhail Losev

• Re: [whatwg/url] Doesn't describe how to process url as 'http:///google.com' (#145) (Monday, 22 August)
• Re: [whatwg/url] Doesn't describe how to process url as 'http:///google.com' (#145) (Monday, 22 August)
• Re: [whatwg/url] Doesn't describe how to process url as 'http:///google.com' (#145) (Monday, 22 August)
• [whatwg/url] Doesn't describe how to process url as 'http:///google.com' (#145) (Monday, 22 August)

Mounir Lamouri

• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Thursday, 4 August)

Ms2ger

• [heycam/webidl] Add missing 'return's. (#150) (Tuesday, 23 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Tuesday, 16 August)
• Re: [w3c/FileAPI] Stop using DOMError (#11) (Thursday, 11 August)
• Re: [w3c/FileAPI] Don't use [EnsureUTF16] (gone from Web IDL) (#9) (Monday, 1 August)

Nathan Schloss

• Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920) (Wednesday, 24 August)
• Re: [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Tuesday, 16 August)
• Re: [slightlyoff/ServiceWorker] Recovering from fetch failures (#939) (Tuesday, 16 August)
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 16 August)
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 16 August)

Nick Doty

• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Friday, 26 August)

ojan

• Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144) (Thursday, 18 August)

Owen Campbell-Moore

• [w3c/manifest] Standalone description not accurate (#495) (Thursday, 25 August)

Pasindu Perera

• Re: [whatwg/fetch] Allowed header in CORS with Access-Control-Expose-Headers (#369) (Tuesday, 16 August)
• Re: [whatwg/fetch] Allowed header in CORS with Access-Control-Expose-Headers (#369) (Tuesday, 16 August)
• Re: [whatwg/fetch] Allowed header in CORS with Access-Control-Expose-Headers (#369) (Tuesday, 16 August)
• [whatwg/fetch] Allowed header in CORS with Access-Control-Expose-Headers (#369) (Tuesday, 16 August)

Patrick H. Lauke

• Re: [w3c/pointerlock] Expanded/clarified introduction (#6) (Friday, 5 August)
• [w3c/pointerlock] Expanded/clarified introduction (#6) (Friday, 5 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] Add informative note about not doing naive "touch OR mouse etc" event handling (#71) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)

patrick kettner

• Re: [w3c/manifest] deprecate gh-pages in favor of echidna (#494) (Friday, 26 August)
• [w3c/manifest] deprecate gh-pages in favor of echidna (#494) (Thursday, 25 August)
• Re: [w3c/manifest] Drop gh-pages branch (#492) (Thursday, 25 August)
• Re: [w3c/manifest] Drop gh-pages branch (#492) (Thursday, 25 August)
• Re: [w3c/manifest] Drop gh-pages branch (#492) (Thursday, 25 August)
• Re: [w3c/manifest] Ability to define platform-specific icon/splash style (#361) (Thursday, 25 August)
• Re: [w3c/manifest] feat(screenshots): Add screenshots member (closes #477) (#490) (Thursday, 25 August)
• Re: [w3c/manifest] feat(screenshots): Add screenshots member (closes #477) (#490) (Thursday, 25 August)
• Re: [w3c/manifest] Add screenshots object (#477) (Wednesday, 24 August)
• Re: [w3c/manifest] Add screenshots object (#477) (Wednesday, 17 August)
• Re: [w3c/manifest] Add screenshots object (#477) (Wednesday, 17 August)
• Re: [w3c/manifest] Discoverability of metadata in web application manifest (#486) (Friday, 12 August)

Pedram Emrouznejad

• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Sunday, 14 August)

Peleg Rosenthal

• Re: [whatwg/streams] Backpressure from tee-ing and slow/pending consumer (#506) (Sunday, 21 August)

Peter Beverloo

• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Thursday, 4 August)
• Re: [w3ctag/spec-reviews] Notifications API (#94) (Monday, 1 August)

Peter Linss

• Re: [w3ctag/packaging-on-the-web] Turn on HTTPS (#32) (Tuesday, 2 August)
• Re: [w3ctag/packaging-on-the-web] Turn on HTTPS (#32) (Tuesday, 2 August)

Peter Rushforth

• Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Disallow attachShadow(...) for some elements. (#110) (Tuesday, 9 August)

Philip Jägenstedt

• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Wednesday, 31 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Wednesday, 31 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Wednesday, 31 August)
• Re: [w3c/permissions] refactor(media devices): use "allowed to use" (#122) (Wednesday, 31 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Wednesday, 31 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Wednesday, 31 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Wednesday, 31 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Wednesday, 31 August)
• Re: [whatwg/dom] Mark ATTRIBUTE_NODE and SHOW_ATTRIBUTE as no longer historical (#321) (Wednesday, 31 August)
• [whatwg/dom] Mark ATTRIBUTE_NODE and SHOW_ATTRIBUTE as no longer historical (#321) (Wednesday, 31 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Tuesday, 30 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Tuesday, 30 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Tuesday, 30 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Tuesday, 30 August)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Sunday, 28 August)
• [whatwg/dom] Editorial: add missing comma (#317) (Sunday, 28 August)
• Re: [whatwg/dom] Callback functions/interfaces need to be invoked with WebIDL concepts (#303) (Thursday, 25 August)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Thursday, 25 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Wednesday, 24 August)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Tuesday, 23 August)
• Re: [whatwg/dom] Define mutation events (#305) (Tuesday, 23 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Tuesday, 23 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Tuesday, 23 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Tuesday, 23 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Tuesday, 23 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Tuesday, 23 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Monday, 22 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Monday, 22 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Monday, 22 August)
• Re: [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Monday, 22 August)
• [whatwg/dom] compareDocumentPosition with Attr nodes still not quite right (#309) (Monday, 22 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Thursday, 18 August)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Thursday, 18 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Wednesday, 17 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Wednesday, 17 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Wednesday, 17 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• [whatwg/dom] Callback functions/interfaces need to be invoked with WebIDL concepts (#303) (Wednesday, 17 August)
• Re: [whatwg/dom] CDATASection misses (#300) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• [whatwg/dom] Define nodeName as "#cdata-section" for CDATASection nodes (#302) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• Re: [whatwg/dom] CDATASection misses (#300) (Wednesday, 17 August)
• Re: [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• [whatwg/dom] Fix and clarify more around CDATASection (#301) (Wednesday, 17 August)
• Re: [whatwg/dom] CDATASection misses (#300) (Wednesday, 17 August)
• Re: [whatwg/dom] CDATASection misses (#300) (Wednesday, 17 August)
• Re: [whatwg/dom] CDATASection misses (#300) (Wednesday, 17 August)
• [whatwg/dom] CDATASection misses (#300) (Wednesday, 17 August)
• Re: [whatwg/dom] Reinstate CDATASection (#295) (Tuesday, 16 August)
• Re: [whatwg/dom] Document.defaultCharset (#58) (Tuesday, 16 August)
• Re: [whatwg/dom] Reinstate CDATASection (#295) (Tuesday, 16 August)
• Re: [whatwg/dom] Reinstate CDATASection (#295) (Tuesday, 16 August)
• Re: [whatwg/dom] Reinstate CDATASection (#295) (Tuesday, 16 August)
• Re: [whatwg/dom] Reinstate CDATASection (#295) (Tuesday, 16 August)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Monday, 15 August)
• Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Monday, 15 August)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Friday, 12 August)
• Re: [w3c/selection-api] Selection events for text controls (#53) (Friday, 12 August)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Friday, 12 August)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Friday, 12 August)
• Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) (Friday, 12 August)
• Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Friday, 12 August)
• Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) (Friday, 12 August)
• [whatwg/fullscreen] Use HTML's new "allowed to use" algorithm (#46) (Friday, 12 August)
• [w3c/permissions] Use HTML's new "allowed to use" algorithm (#121) (Friday, 12 August)
• Re: [whatwg/fullscreen] Use new "allowed to use" algorithm once introduced (#41) (Friday, 12 August)
• Re: [whatwg/dom] Is document.createEvent("progressevent") really useful? (#289) (Thursday, 4 August)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Wednesday, 3 August)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Monday, 1 August)
• Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) (Monday, 1 August)
• Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) (Monday, 1 August)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Monday, 1 August)

Philipp Legner

• Re: [slightlyoff/ServiceWorker] Send correct Accept header with fetch() request (#945) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Send correct Accept header with fetch() request (#945) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Send correct Accept header with fetch() request (#945) (Friday, 5 August)
• [slightlyoff/ServiceWorker] Send correct Accept header with fetch() request (#945) (Friday, 5 August)

Philippe Le Hegaret

• Re: [w3c/charter-html] update pointer lock and input events information (#136) (Monday, 29 August)
• Re: [w3c/charter-html] update pointer lock and input events information (#136) (Monday, 29 August)
• Re: [w3c/charter-html] Adjust FTEs (#134) (Monday, 29 August)
• Re: [w3c/charter-html] Removed CORS maintenance (#135) (Monday, 29 August)
• [w3c/charter-html] Removed CORS maintenance (#135) (Monday, 29 August)
• [w3c/charter-html] Adjust FTEs (#134) (Monday, 29 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Wednesday, 24 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Wednesday, 24 August)
• [w3c/charter-html] Improved ARIA WG description (#132) (Thursday, 4 August)

PhistucK

• Re: [whatwg/dom] Remove feature detection from add() and add supports() (#123) (Friday, 19 August)

piersh

• Re: [slightlyoff/ServiceWorker] notification of cancelled download? (#957) (Wednesday, 17 August)
• [slightlyoff/ServiceWorker] notification of cancelled download? (#957) (Wednesday, 17 August)

Piotrek Koszuliński

• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 25 August)

r12a

• Re: [whatwg/encoding] "In equations, all numbers are integers, additio..." (#66) (Tuesday, 2 August)

Ramón Isijara

• Re: [whatwg/fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179) (Tuesday, 16 August)

Rhys Evans

• Re: [slightlyoff/ServiceWorker] Handling race conditions - API for accessing pending requests? (#959) (Thursday, 18 August)
• Re: [slightlyoff/ServiceWorker] Reliable way to detect if a fetch is for a new page (#958) (Wednesday, 17 August)
• [slightlyoff/ServiceWorker] Handling race conditions - API for accessing pending requests? (#959) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] Reliable way to detect if a fetch is for a new page (#958) (Wednesday, 17 August)
• [slightlyoff/ServiceWorker] Reliable way to detect if a fetch is for a new page (#958) (Wednesday, 17 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Monday, 8 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Saturday, 6 August)
• Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 5 August)
• Re: [slightlyoff/ServiceWorker] Reporting URL for SW update failures (#877) (Tuesday, 2 August)

Richard Schwerdtfeger

• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Wednesday, 31 August)
• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Tuesday, 30 August)
• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Tuesday, 30 August)
• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Monday, 29 August)
• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Thursday, 25 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Wednesday, 24 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Wednesday, 24 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Wednesday, 24 August)
• [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Tuesday, 23 August)
• [w3c/webcomponents] Should ARIA 2.0 have a role corresonding to each HTML element? (#552) (Tuesday, 23 August)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Tuesday, 23 August)

Rick Byers

• Re: [w3c/editing] Should contenteditable have break-word behavior by default? (#145) (Tuesday, 30 August)
• Re: [w3c/touch-events] Add TouchEvent's retargeting steps (#73) (Tuesday, 30 August)
• Re: [whatwg/dom] Should EventInit contain 'timestamp'? (#76) (Thursday, 25 August)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Tuesday, 23 August)
• [w3c/editing] Should contenteditable have break-word behavior by default? (#145) (Monday, 22 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Wednesday, 3 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)
• Re: [w3c/uievents] Fix #89. Make some of legacy UIEvents composed events (#93) (Monday, 1 August)
• Re: [w3c/touch-events] Add informative note about not doing naive "touch OR mouse etc" event handling (#71) (Monday, 1 August)

Rob Brackett

• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 26 August)
• Re: [w3c/webcomponents] Move the check for HTMLElement and its subclass from customElements.define to construction timing (#541) (Friday, 12 August)

Rob Dodson

• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Wednesday, 24 August)
• Re: [w3c/webcomponents] DocumentOrShadowRoot.deepActiveElement (#104) (Tuesday, 23 August)

Rob Dolin (MSFT)

• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Tuesday, 16 August)
• Re: [w3c/manifest] Add screenshots object (#477) (Tuesday, 16 August)
• Re: [w3c/manifest] Ability to claim web app (#476) (Tuesday, 16 August)
• Re: [w3c/manifest] Allow unique start_url for subdomains (#470) (Friday, 12 August)
• Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Friday, 12 August)
• [w3c/manifest] [Example] Make Racer 2k example from future (#487) (Friday, 12 August)

RobertPlamondon

• Re: [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308) (Monday, 29 August)
• Re: [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308) (Friday, 26 August)

Rohit Sharma

• Re: [slightlyoff/ServiceWorker] Service worker updation doesn't work as expected (#946) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] Service worker updation doesn't work as expected (#946) (Wednesday, 10 August)
• Re: [slightlyoff/ServiceWorker] Service worker updation doesn't work as expected (#946) (Wednesday, 10 August)
• [slightlyoff/ServiceWorker] Service worker updation doesn't work as expected (#946) (Wednesday, 10 August)

Roland Firmont

• Re: [w3c/FileAPI] Race condition in Introduction example (#48) (Wednesday, 24 August)
• [w3c/FileAPI] Race condition in Introduction example (#48) (Tuesday, 23 August)

Ruben Verborgh

• Re: [whatwg/fetch] Mark Accept-* request headers as simple / safe (#326) (Friday, 12 August)
• Re: [whatwg/fetch] Mark Accept-* request headers as simple / safe (#326) (Wednesday, 10 August)

Russell Bicknell

• [whatwg/dom] `compareDocumentPosition` should allow comparison of elements in the same shadow-including root (#320) (Tuesday, 30 August)

Ryosuke Niwa

• Re: [w3c/webcomponents] HTML element constructors need to Get(newTarget, "Prototype") (#560) (Wednesday, 31 August)
• Re: [w3c/webcomponents] HTML element constructors need to Get(newTarget, "Prototype") (#560) (Wednesday, 31 August)
• [w3c/webcomponents] HTML element constructors need to Get(newTarget, "Prototype") (#560) (Wednesday, 31 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Wednesday, 31 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Monday, 29 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Monday, 29 August)
• Re: [w3c/webcomponents] How to wait for will-be custom elements to be upgraded? (#558) (Monday, 29 August)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Monday, 29 August)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Wednesday, 24 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 23 August)
• Re: [w3c/webcomponents] Rename interface CustomElementsRegistry to CustomElementRegistry (#548) (Tuesday, 23 August)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Monday, 22 August)
• Re: [w3c/webcomponents] Rename interface CustomElementsRegistry to CustomElementRegistry (#548) (Monday, 22 August)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Monday, 22 August)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Monday, 22 August)
• Re: [w3c/webcomponents] Should I write new components backwards compatible with v0 API? (#549) (Sunday, 21 August)
• Re: [w3c/webcomponents] Rename interface CustomElementsRegistry to CustomElementRegistry (#548) (Saturday, 20 August)
• [w3c/webcomponents] Rename interface CustomElementsRegistry to CustomElementRegistry (#548) (Saturday, 20 August)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Saturday, 20 August)
• [w3c/IndexedDB] transaction should either take DOMStringList or DOMStringList needs to be iterable (#85) (Saturday, 20 August)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Friday, 19 August)
• [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Friday, 19 August)
• Re: [w3c/webcomponents] Observe ShadowRoot attachment (#204) (Wednesday, 17 August)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Monday, 15 August)
• Re: [w3c/webcomponents] Move the check for HTMLElement and its subclass from customElements.define to construction timing (#541) (Monday, 15 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Monday, 15 August)
• Re: [w3c/webcomponents] Move the check for HTMLElement and its subclass from customElements.define to construction timing (#541) (Sunday, 14 August)
• Re: [w3c/webcomponents] Move the check for HTMLElement and its subclass from customElements.define to construction timing (#541) (Sunday, 14 August)
• [heycam/webidl] Conversion to sequence<T> need not throw on a RegExp object (#145) (Saturday, 13 August)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Friday, 12 August)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Friday, 12 August)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Friday, 12 August)
• Re: [w3c/selection-api] Selection events for text controls (#53) (Friday, 12 August)
• Re: [w3c/webcomponents] Forbid reentrance to `customElements.define` (#545) (Friday, 12 August)
• [w3c/webcomponents] Forbid reentrance to `customElements.define` (#545) (Friday, 12 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 11 August)
• Re: [w3c/webcomponents] Should :defined match <x-foo> in browsing-context-less documents? (#540) (Thursday, 11 August)
• Re: [w3c/webcomponents] Steps in element definition that throw an exception should abort (#543) (Thursday, 11 August)
• Re: [w3c/webcomponents] Steps in element definition that throw an exception should abort (#543) (Thursday, 11 August)
• Re: [w3c/webcomponents] Steps in element definition that throw an exception should abort (#543) (Thursday, 11 August)
• Re: [w3c/webcomponents] Steps in element definition that throw an exception should abort (#543) (Thursday, 11 August)
• [w3c/webcomponents] Steps in element definition that throw an exception should abort (#543) (Thursday, 11 August)
• Re: [w3c/webcomponents] Step 13.3-4 in element definition should clarify the ordering (#542) (Thursday, 11 August)
• Re: [w3c/webcomponents] Step 13.3-4 in element definition should clarify the ordering (#542) (Thursday, 11 August)
• [w3c/webcomponents] Step 13.3-4 in element definition should clarify the ordering (#542) (Thursday, 11 August)
• Re: [w3c/webcomponents] Move the check for HTMLElement and its subclass from customElements.define to construction timing (#541) (Thursday, 11 August)
• [w3c/webcomponents] Move the check for HTMLElement and its subclass from customElements.define to construction timing (#541) (Thursday, 11 August)
• Re: [w3c/webcomponents] Let's make document.write()/open() throw during parser invocations of custom element constructors (#537) (Wednesday, 10 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Wednesday, 10 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 9 August)
• [w3c/selection-api] setBaseAndExtent should clear selection when baseNode or extentNode is null (#72) (Monday, 8 August)
• Re: [w3c/selection-api] setBaseAndExtent() and setPositon() should be marked as "deprecated" (#67) (Monday, 8 August)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Sunday, 7 August)
• Re: [w3c/webcomponents] Other named properties in shadow DOM (#536) (Wednesday, 3 August)
• Re: [w3c/webcomponents] Ignore title attributes on <link rel=stylesheet> in shadow trees (#535) (Tuesday, 2 August)
• Re: [w3c/selection-api] Fix normative references (#71) (Monday, 1 August)
• Re: [w3c/selection-api] Normative references (#69) (Monday, 1 August)

Salvador de la Puente González

• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Monday, 29 August)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Monday, 29 August)
• Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813) (Wednesday, 24 August)
• Re: [w3c/ServiceWorker] Handling race conditions - API for accessing pending requests? (#959) (Wednesday, 24 August)
• Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920) (Wednesday, 24 August)
• Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 23 August)
• Re: [w3c/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Tuesday, 23 August)

Sam Ruby

• Re: [slightlyoff/ServiceWorker] should ServiceWorkerContainer.getRegistrations() check the uninstalling flag (#943) (Wednesday, 10 August)

Samer Masterson

• Re: [slightlyoff/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Thursday, 4 August)
• [slightlyoff/ServiceWorker] Is it possible to serve service worker from CDN/remote origin? (#940) (Thursday, 4 August)

Scott González

• Re: [w3c/touch-events] note about avoiding conditional "touch OR mouse/keyboard" event handling (#72) (Tuesday, 2 August)

Sebastian Kippe

• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Friday, 5 August)

Sebastian Mayr

• Re: [whatwg/url] toJSON() serialization (#137) (Monday, 8 August)

Shiino Yuki

• Re: [heycam/webidl] Named properties visibility algorithm leads to ES invariant violation (#152) (Monday, 29 August)

ShijunS

• [w3c/permissions] questions on query() (#124) (Tuesday, 30 August)
• Re: [w3c/permissions] questions on query() (#124) (Tuesday, 30 August)
• Re: [w3c/permissions] Drop .request() (#83) (Tuesday, 30 August)
• Re: [w3c/permissions] Drop .request() (#83) (Tuesday, 30 August)
• Re: [w3c/permissions] Drop .request() (#83) (Sunday, 28 August)
• Re: [w3c/permissions] Drop .request() (#83) (Sunday, 28 August)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Saturday, 27 August)
• [w3c/push-api] update reference to FIPS-186-4 (#210) (Thursday, 25 August)

shlatchz

• [w3c/ServiceWorker] Chrome API unavailable in ServiceWorker (#969) (Tuesday, 30 August)

Simon Pieters

• Re: [heycam/webidl] Add namespaces (#121) (Friday, 26 August)
• Re: [whatwg/dom] Define mutation events (#305) (Wednesday, 24 August)
• Re: [whatwg/dom] Define mutation events (#305) (Wednesday, 24 August)
• Re: [whatwg/dom] [CEReactions] for insertAdjacentText (#294) (Wednesday, 17 August)
• Re: [whatwg/dom] [CEReactions] for insertAdjacentText (#294) (Wednesday, 17 August)
• [whatwg/dom] [CEReactions] for insertAdjacentText (#294) (Tuesday, 16 August)
• Re: [w3c/webcomponents] Ignore title attributes on <link rel=stylesheet> in shadow trees (#535) (Tuesday, 16 August)
• Re: [w3c/webcomponents] Ignore title attributes on <link rel=stylesheet> in shadow trees (#535) (Friday, 12 August)

sleevi

• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Thursday, 18 August)

smaug----

• Re: [whatwg/dom] Define mutation events (#305) (Tuesday, 23 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Monday, 22 August)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Monday, 22 August)
• Re: [whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339) (Friday, 19 August)
• Re: [whatwg/dom] Make Attr inherit from Node again (#299) (Wednesday, 17 August)
• Re: [whatwg/dom] Consider making dispatchEvent() unset stop (immediate) propagation flags (#219) (Monday, 15 August)
• Re: [whatwg/dom] Consider making dispatchEvent() unset stop (immediate) propagation flags (#219) (Monday, 15 August)
• Re: [whatwg/dom] Consider banning insertNode() of the Range's start node (#63) (Monday, 8 August)
• Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Wednesday, 3 August)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Tuesday, 2 August)
• Re: [w3c/webcomponents] Ignore title attributes on <link rel=stylesheet> in shadow trees (#535) (Tuesday, 2 August)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Monday, 1 August)

Spongman

• Re: [slightlyoff/ServiceWorker] notification of cancelled download? (#957) (Wednesday, 17 August)

stevefaulkner

• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Friday, 12 August)

Steven Lambert

• Re: [whatwg/dom] Proposal to improve the DOM creation api (#150) (Thursday, 11 August)

Steven Vachon

• Re: [whatwg/url] empty username? (#139) (Wednesday, 10 August)
• Re: [whatwg/url] empty username? (#139) (Wednesday, 10 August)
• Re: [whatwg/url] empty username? (#139) (Wednesday, 10 August)
• Re: [whatwg/url] empty username? (#139) (Wednesday, 10 August)
• [whatwg/url] empty username? (#139) (Wednesday, 10 August)
• Re: [whatwg/url] // in path (#138) (Wednesday, 10 August)
• [whatwg/url] // in path (#138) (Wednesday, 10 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Tuesday, 9 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Monday, 8 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Monday, 8 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Monday, 8 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Monday, 8 August)
• Re: [whatwg/url] toJSON() serialization (#137) (Monday, 8 August)
• [whatwg/url] toJSON() serialization (#137) (Monday, 8 August)
• Re: [whatwg/url] relative URLs (#136) (Sunday, 7 August)
• Re: [whatwg/url] relative URLs (#136) (Saturday, 6 August)
• Re: [whatwg/url] relative URLs (#136) (Saturday, 6 August)
• Re: [whatwg/url] relative URLs (#136) (Friday, 5 August)
• [whatwg/url] relative URLs (#136) (Friday, 5 August)

Tab Atkins Jr.

• Re: [w3c/ServiceWorker] Chrome API unavailable in ServiceWorker (#969) (Tuesday, 30 August)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Tuesday, 30 August)
• Re: [w3c/ServiceWorker] Chrome API unavailable in ServiceWorker (#969) (Tuesday, 30 August)
• Re: [whatwg/url] Update origin links now that HTML defines it with for=''. (#146) (Tuesday, 23 August)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Wednesday, 17 August)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Wednesday, 17 August)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Wednesday, 17 August)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Wednesday, 17 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Tuesday, 9 August)
• Re: [whatwg/dom] "unclosed node of node" reads confusingly (#285) (Tuesday, 2 August)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Monday, 1 August)

Takayoshi Kochi

• Re: [w3c/webcomponents] Fix #556, make focus navigation work when shadow host's tabindex is -1 (#557) (Wednesday, 31 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Wednesday, 31 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Wednesday, 31 August)
• Re: [whatwg/dom] Drop "invoking" from "invoking retargeting" (#318) (Wednesday, 31 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Tuesday, 30 August)
• [whatwg/dom] Drop "invoking" from "invoking retargeting" (#318) (Tuesday, 30 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Tuesday, 30 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Tuesday, 30 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Tuesday, 30 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Tuesday, 30 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Tuesday, 30 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Tuesday, 30 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Tuesday, 30 August)
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Monday, 29 August)
• [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Monday, 29 August)
• Re: [w3c/pointerlock] Use the new "retargeting algorighm" in the DOM spec. (#8) (Monday, 29 August)
• [w3c/webcomponents] Fix #556, make focus navigation work when shadow host's tabindex is -1 (#557) (Monday, 29 August)
• [w3c/webcomponents] Shadow host with its .tabindex property -1 would be skipped for focus navigation (#556) (Monday, 29 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Monday, 29 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 26 August)
• Re: [w3c/webcomponents] Rename interface CustomElementsRegistry to CustomElementRegistry (#548) (Thursday, 25 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 25 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 25 August)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 25 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Wednesday, 10 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Tuesday, 9 August)
• Re: [w3c/webcomponents] Scripts in HTML Imports should be scoped to the import (treat imports as script modules) (bugzilla: 27836) (#157) (Monday, 1 August)
• Re: [w3c/webcomponents] [imports]: ES6 module loader should be aware modules in HTML Imports (bugzilla: 24848) (#223) (Monday, 1 August)
• Re: [w3c/webcomponents] [imports]: ES6 module loader should be aware modules in HTML Imports (bugzilla: 24848) (#223) (Monday, 1 August)
• Re: [w3c/webcomponents] [imports]: Typo: "overnride" (bugzilla: 26233) (#205) (Monday, 1 August)
• Re: [w3c/webcomponents] [imports]: Typo: "overnride" (bugzilla: 26233) (#205) (Monday, 1 August)
• Re: [w3c/webcomponents] [imports]: Things to Consider in the Future (bugzilla: 23278) (#220) (Monday, 1 August)
• Re: [w3c/webcomponents] [Imports]: Write HTML Imports spec (bugzilla: 20683) (#149) (Monday, 1 August)
• Re: [w3c/webcomponents] [Imports]: Write HTML Imports spec (bugzilla: 20683) (#149) (Monday, 1 August)
• Re: [w3c/webcomponents] [imports]: Things to Consider in the Future (bugzilla: 23278) (#220) (Monday, 1 August)

Takeshi Yoshino

• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Wednesday, 31 August)
• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Wednesday, 31 August)
• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Wednesday, 31 August)
• Re: [whatwg/streams] Convert writable stream tests to web platform tests format (#492) (Wednesday, 31 August)
• [whatwg/streams] lint glob should exclude Emacs backup files (#514) (Wednesday, 31 August)
• Re: [whatwg/streams] Convert some general tests for ws into wpt (#510) (Wednesday, 31 August)
• Re: [whatwg/streams] Convert some general tests for ws into wpt (#510) (Wednesday, 31 August)
• Re: [whatwg/streams] Convert some general tests for ws into wpt (#510) (Wednesday, 31 August)
• Re: [whatwg/streams] More concrete examples of "optimization" of pipeTo (#359) (Tuesday, 30 August)
• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Tuesday, 30 August)
• [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Tuesday, 30 August)
• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) (Monday, 29 August)
• Re: [whatwg/streams] Convert writable stream tests to web platform tests format (#492) (Monday, 29 August)
• [whatwg/streams] Convert some general tests for ws into wpt (#510) (Monday, 29 August)
• Re: [whatwg/streams] Convert writable stream tests to web platform tests format (#492) (Monday, 29 August)
• Re: [whatwg/streams] Convert writable stream tests to web platform tests format (#492) (Monday, 29 August)
• Re: [whatwg/streams] Convert writable stream tests to web platform tests format (#492) (Thursday, 25 August)
• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) (Thursday, 25 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Monday, 22 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Monday, 22 August)
• Re: [whatwg/streams] Requirements.md: Change example of push stream from TCP to UDP (#508) (Monday, 22 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Tuesday, 16 August)
• [whatwg/streams] Factor out some logic into helper functions (#505) (Thursday, 4 August)
• Re: [whatwg/streams] Make writer.desiredSize return 0 for closed streams (#503) (Thursday, 4 August)
• [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Thursday, 4 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream to drain all data (#504) (Thursday, 4 August)
• [whatwg/streams] Make writer.desiredSize return 0 for closed streams (#503) (Thursday, 4 August)
• Re: [whatwg/streams] Update spec to use ReadableStreamDefaultControllerErrorIfNeeded (#500) (Thursday, 4 August)
• [whatwg/streams] Remove unchecked expectation from readable byte stream test (#502) (Thursday, 4 August)
• Re: [whatwg/streams] Add a lint step for the reference implementation (62f9269) (Thursday, 4 August)
• Re: [whatwg/streams] Update spec to use ReadableStreamDefaultControllerErrorIfNeeded (#500) (Thursday, 4 August)
• Re: [whatwg/streams] Add an example of using desiredSize and ready with writable streams (#496) (Thursday, 4 August)
• Re: [whatwg/streams] Add an example of using desiredSize and ready with writable streams (#496) (Thursday, 4 August)
• [whatwg/streams] Update spec to use ReadableStreamDefaultControllerErrorIfNeeded (#500) (Thursday, 4 August)
• [whatwg/streams] Use some logging framework (#499) (Thursday, 4 August)
• [whatwg/streams] Argument order of transform() function (or attempt to remove done) (#498) (Thursday, 4 August)
• Re: [whatwg/streams] Rename headings ID atrributes (#497) (Thursday, 4 August)
• [whatwg/streams] Rename headings ID atrributes (#497) (Thursday, 4 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Thursday, 4 August)
• [whatwg/streams] Add lint for coding style, etc. (#494) (Thursday, 4 August)
• Re: [whatwg/streams] Synchronous (or asynchronous) state probing on WritableStream (#463) (Thursday, 4 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Thursday, 4 August)
• Re: [whatwg/streams] Synchronous queue draining for WritableStream (#465) (Thursday, 4 August)
• Re: [whatwg/streams] Port locking infrastructure to writable streams (#319) (Thursday, 4 August)
• Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Thursday, 4 August)
• Re: [whatwg/streams] Port locking infrastructure to writable streams (#319) (Thursday, 4 August)
• Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Thursday, 4 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Thursday, 4 August)
• Re: [whatwg/streams] Port precise flow control to writable streams (#318) (Thursday, 4 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Thursday, 4 August)
• Re: [whatwg/streams] Port precise flow control to writable streams (#318) (Thursday, 4 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Wednesday, 3 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Wednesday, 3 August)
• [whatwg/streams] Add totalSize caching to queue-with-size library (#491) (Wednesday, 3 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Wednesday, 3 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Add totalSize caching to queue-with-size library (7215774) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Tuesday, 2 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] [WritableStream] Locking semantics (#474) (Monday, 1 August)
• Re: [whatwg/streams] [WritableStream] Locking semantics (#474) (Monday, 1 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream() to drain all the available data (#489) (Monday, 1 August)
• Re: [whatwg/streams] Fix makeReadableBackpressureByteSocketStream() to drain all the available data (#489) (Monday, 1 August)
• Re: [whatwg/streams] "socket.setTCPWindowSize" (#483) (Monday, 1 August)
• [whatwg/streams] Fix makeReadableBackpressureByteSocketStream() to drain all the available data (#489) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Monday, 1 August)
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)
• [whatwg/streams] Align WritableStream structure with ReadableStream structure (#488) (Monday, 1 August)