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

=JeffH

• Re: [heycam/webidl] get-buffer-source-{reference,copy} ought to point to the algorithm (#229) (Monday, 7 November)
• Re: [heycam/webidl] #es-to-dictionary and #dictionary-to-es do not have reader-discernable titles (#228) (Monday, 7 November)
• [heycam/webidl] get-buffer-source-{reference,copy} ought to point to the algorithm (#229) (Monday, 7 November)
• [heycam/webidl] #es-to-dictionary and #dictionary-to-es do not have reader-discernable titles (#228) (Monday, 7 November)

Aaron Shafovaloff

• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 23 November)

achristensen07

• Re: [whatwg/url] IDNA / UTS #46 "should" requirements (#110) (Saturday, 19 November)
• Re: [whatwg/url] Change host parser for non-special schemes (#148) (Tuesday, 8 November)
• Re: [whatwg/url] Change host parser for non-special schemes (#148) (Tuesday, 1 November)

Adam Rice

• Re: [whatwg/streams] us.abort() is not called if us.write() fails (#620) (Tuesday, 29 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Tuesday, 29 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Monday, 28 November)
• Re: [whatwg/streams] Do not assert() when writer is detached during close() (#621) (Monday, 28 November)
• Re: [whatwg/streams] us.abort() is not called if us.write() fails (#620) (Monday, 28 November)
• [whatwg/streams] Do not assert() when writer is detached during close() (#621) (Friday, 25 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Friday, 25 November)
• Re: [whatwg/streams] us.abort() is not called if us.write() fails (#620) (Friday, 25 November)
• [whatwg/streams] us.abort() is not called if us.write() fails (#620) (Friday, 25 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 24 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Thursday, 24 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Thursday, 24 November)
• Re: [whatwg/streams] TransformStream byte streams (#616) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Tuesday, 22 November)
• [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Tuesday, 22 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Tuesday, 22 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Tuesday, 22 November)
• Re: [whatwg/streams] TransformStream byte streams (#616) (Tuesday, 22 November)
• Re: [whatwg/streams] Make the remaining failing tests pass (d673b08) (Monday, 21 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Monday, 21 November)
• [whatwg/streams] "Wait until any ongoing write finishes (i.e. the..." (#618) (Monday, 21 November)
• [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Monday, 21 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Monday, 21 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Monday, 21 November)
• Re: [whatwg/streams] TransformStream byte streams (#616) (Monday, 21 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Monday, 21 November)
• [whatwg/streams] TransformStream byte streams (#616) (Monday, 21 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Friday, 18 November)
• Re: [whatwg/streams] Cloning (not teeing) a readable stream, via controller tricks (#599) (Thursday, 17 November)
• Re: [whatwg/encoding] Inform readers about the structure of the sparsity of index-euc-kr (#78) (Thursday, 17 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Thursday, 17 November)
• Re: [whatwg/encoding] Add Streams support (#72) (Thursday, 17 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Thursday, 17 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Wednesday, 16 November)
• Re: [whatwg/streams] Invoking methods should not call .apply() (#613) (Wednesday, 16 November)
• Re: [whatwg/streams] Invoking methods should not call .apply() (#613) (Wednesday, 16 November)
• Re: [whatwg/streams] Invoking methods should not call .apply() (#613) (Wednesday, 16 November)
• Re: [whatwg/streams] Invoking methods should not call .apply() (#613) (Wednesday, 16 November)
• Re: [whatwg/streams] Invoking methods should not call .apply() (#613) (Wednesday, 16 November)
• [whatwg/streams] Invoking methods should not call .apply() (#613) (Wednesday, 16 November)
• Re: [whatwg/streams] Editorial: consistently use minimal returns (#612) (Tuesday, 15 November)
• Re: [whatwg/streams] Editorial: consistently use minimal returns (#612) (Tuesday, 15 November)
• Re: [whatwg/streams] Editorial: consistently use minimal returns (#612) (Tuesday, 15 November)
• Re: [whatwg/streams] Mark promise rejections for "state promises" as handled (#607) (Tuesday, 15 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Tuesday, 15 November)
• Re: [whatwg/streams] Editorial: consistently use minimal returns (#612) (Tuesday, 15 November)
• [whatwg/streams] Minor fixes to writable-stream tests (#610) (Monday, 14 November)
• Re: [whatwg/streams] Remove trivial non-zero delays in wpts (#605) (Friday, 11 November)
• Re: [whatwg/streams] rework recording-streams helper (#609) (Friday, 11 November)
• Re: [whatwg/streams] skip WPT dir if not present (#608) (Friday, 11 November)
• Re: [whatwg/streams] Mark promise rejections for "state promises" as handled (#607) (Thursday, 10 November)
• Re: [whatwg/streams] Remove trivial non-zero delays in wpts (#605) (Thursday, 10 November)
• Re: [whatwg/streams] Remove trivial non-zero delays in wpts (#605) (Thursday, 10 November)
• Re: [whatwg/streams] port piping tests to WPT (#603) (Thursday, 10 November)
• Re: [whatwg/streams] port piping tests to WPT (#603) (Thursday, 10 November)
• Re: [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Thursday, 10 November)
• Re: [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Thursday, 10 November)
• Re: [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Thursday, 10 November)
• Re: [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Wednesday, 9 November)
• [whatwg/streams] Remove trivial non-zero delays in wpts (#605) (Wednesday, 9 November)
• Re: [whatwg/streams] port piping tests to WPT (#603) (Wednesday, 9 November)
• Re: [whatwg/streams] Marking promise rejections as handled (#547) (Tuesday, 8 November)
• Re: [whatwg/streams] Marking promise rejections as handled (#547) (Tuesday, 8 November)
• Re: [whatwg/streams] move TransformStream strategies to second argument (#600) (Monday, 7 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Saturday, 5 November)
• Re: [whatwg/streams] delete dead code (#602) (Saturday, 5 November)
• Re: [whatwg/streams] delete dead code (#602) (Saturday, 5 November)
• Re: [whatwg/streams] WPT-ify some tests (#597) (Saturday, 5 November)
• Re: [whatwg/streams] WPT-ify some tests (#597) (Saturday, 5 November)
• Re: [whatwg/streams] WPT-ify some tests (#597) (Saturday, 5 November)
• Re: [whatwg/streams] WPT-ify some tests (#597) (Saturday, 5 November)
• Re: [whatwg/streams] use abstract ops in TransformStream implementation (#598) (Friday, 4 November)
• Re: [whatwg/streams] use abstract ops in TransformStream implementation (#598) (Friday, 4 November)
• Re: [whatwg/streams] use abstract ops in TransformStream implementation (#598) (Friday, 4 November)
• Re: [whatwg/streams] WPT-ify some tests (#597) (Friday, 4 November)
• Re: [whatwg/streams] Marking promise rejections as handled (#547) (Friday, 4 November)
• Re: [whatwg/streams] test non-function strategy.size (#594) (Thursday, 3 November)
• Re: [whatwg/streams] test non-function strategy.size (#594) (Thursday, 3 November)
• Re: [whatwg/streams] test non-function strategy.size (#594) (Thursday, 3 November)
• Re: [whatwg/streams] test non-function strategy.size (#594) (Thursday, 3 November)
• Re: [whatwg/streams] remove dead code (#593) (Thursday, 3 November)
• Re: [whatwg/streams] remove dead code (#593) (Thursday, 3 November)
• Re: [whatwg/streams] Add code coverage reporting the reference implementation/tests (#590) (Thursday, 3 November)
• Re: [whatwg/streams] Why are [[writeRequests]] and [[queue]] separate? (#589) (Thursday, 3 November)
• [whatwg/streams] WritableStream: Test no-op releaseLock (#588) (Wednesday, 2 November)
• Re: [whatwg/streams] Should ReadableStreamDefaultReader be exposed? (#586) (Wednesday, 2 November)
• [whatwg/streams] Editorial: "return undefined." vs. "return" (#587) (Wednesday, 2 November)
• [whatwg/streams] "non-negative" (#585) (Wednesday, 2 November)
• Re: [whatwg/streams] assert invariants in InvokeOrNoop and friends (#584) (Tuesday, 1 November)
• Re: [whatwg/streams] "Set totalSize to totalSize + pair.[[size]]." (#582) (Tuesday, 1 November)

Aleksey Shvayka

• Re: [w3c/webcomponents] Add [SameObject] to import IDL attribute (#600) (Wednesday, 2 November)
• [w3c/webcomponents] Add [SameObject] to import IDL attribute (#600) (Wednesday, 2 November)

Alex Russell

• Re: [w3ctag/spec-reviews] Review OffscreenCanvas (#144) (Tuesday, 15 November)
• Re: [w3ctag/spec-reviews] WebVR (#106) (Tuesday, 15 November)
• Re: [w3ctag/spec-reviews] Review Web Authentication spec (#97) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] Review Web Authentication spec (#97) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] MediaStream Recorder (#131) (Tuesday, 1 November)

Alexei Czeskis

• Re: [w3ctag/spec-reviews] Review Web Authentication spec (#97) (Wednesday, 2 November)

Andrea Giammarchi

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 21 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 20 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 20 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 20 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 19 November)
• Re: [w3c/webcomponents] Constructor arguments in custom elements (#605) (Friday, 11 November)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Thursday, 10 November)
• Re: [w3c/webcomponents] "is" attribute for autonomous custom elements (#603) (Thursday, 10 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 3 November)

Andreas Plesch

• Re: [whatwg/dom] add changed value to mutation record (#376) (Saturday, 19 November)
• Re: [whatwg/dom] add changed value to mutation record (#376) (Saturday, 19 November)
• Re: [whatwg/dom] add changed value to mutation record (#376) (Saturday, 19 November)
• [whatwg/dom] add changed value to mutation record (#376) (Friday, 18 November)

Andrew Betts

• Re: [w3ctag/spec-reviews] Review request for Scroll Anchoring (#142) (Tuesday, 1 November)

Andrew Sutherland

• Re: [w3c/ServiceWorker] The promises returned by skipWaiting() should have more consistent activation-waiting behavior and not call Activate() multiple times (#1015) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] The promises returned by skipWaiting() should have more consistent activation-waiting behavior and not call Activate() multiple times (#1015) (Monday, 28 November)
• [w3c/ServiceWorker] The promises returned by skipWaiting() should have more consistent activation-waiting behavior and not call Activate() multiple times (#1015) (Sunday, 27 November)
• Re: [w3c/ServiceWorker] serviceworker for iframes with srcdoc (#765) (Wednesday, 16 November)

Anne van Kesteren

• [whatwg/dom] Meta: run output through the HTML checker (#381) (Wednesday, 30 November)
• [whatwg/dom] Copy the origin pointer when cloning a document (#380) (Wednesday, 30 November)
• Re: [whatwg/storage] Error handling in estimate() (#38) (Wednesday, 30 November)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Wednesday, 30 November)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Wednesday, 30 November)
• Re: [whatwg/fetch] Simplify HeadersInit (#418) (Wednesday, 30 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 29 November)
• Re: [whatwg/storage] Error handling in estimate() (#38) (Tuesday, 29 November)
• Re: [whatwg/fullscreen] Decide on wanted behavior for request+exit or exit+request together (#63) (Tuesday, 29 November)
• Re: [heycam/webidl] Meta: remove sequence<T> as Bikeshed definition (#245) (Tuesday, 29 November)
• [heycam/webidl] Meta: remove sequence<T> as Bikeshed definition (#245) (Tuesday, 29 November)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Tuesday, 29 November)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Tuesday, 29 November)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Tuesday, 29 November)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Tuesday, 29 November)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 29 November)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 29 November)
• Re: [whatwg/dom] 1 (#379) (Tuesday, 29 November)
• Re: [whatwg/fetch] Meta: run HTML checker on generated HTML (#426) (Monday, 28 November)
• Re: [whatwg/fetch] Meta: run HTML checker on generated HTML (#426) (Monday, 28 November)
• Re: [whatwg/fetch] Meta: run HTML checker on generated HTML (#426) (Monday, 28 November)
• Re: [whatwg/fetch] Meta: run HTML checker on generated HTML (#426) (Monday, 28 November)
• Re: [whatwg/fetch] Meta: run HTML checker on generated HTML (#426) (Monday, 28 November)
• [whatwg/fetch] Meta: run HTML checker on generated HTML (#426) (Monday, 28 November)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Monday, 28 November)
• Re: [w3c/webcomponents] [Shadow]: Declarative Shadow DOM (bugzilla: 28441) (#71) (Monday, 28 November)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Monday, 28 November)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Monday, 28 November)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 28 November)
• Re: [whatwg/fetch] FormData content-type doesn't match form submission behavior in browsers (#422) (Monday, 28 November)
• Re: [whatwg/fetch] FormData content-type doesn't match form submission behavior in browsers (#422) (Monday, 28 November)
• Re: [whatwg/fetch] Add a space before multipart/form-data's boundary parameter (#423) (Monday, 28 November)
• Re: [w3c/webcomponents] [shadow-dom] [spec-bug] in asignedNodes description. (#612) (Monday, 28 November)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Monday, 28 November)
• Re: [whatwg/fetch] FormData content-type doesn't match form submission behavior in browsers (#422) (Monday, 28 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [whatwg/fetch] Clarification of Body package data algorithm with bytes, FormData and multipart/form-data MIME type (#392) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [whatwg/xhr] Wordpress.org issue (#103) (Friday, 25 November)
• Re: [whatwg/xhr] Wordpress.org issue (#103) (Friday, 25 November)
• [whatwg/fetch] Add a space before multipart/form-data's boundary parameter (#423) (Friday, 25 November)
• Re: [whatwg/fetch] Export various things for service worker (#420) (Thursday, 24 November)
• Re: [whatwg/fetch] Export all <dfn>s that Service Worker uses (#403) (Thursday, 24 November)
• Re: [whatwg/fetch] Export various things for service worker (#420) (Thursday, 24 November)
• Re: [whatwg/fetch] Emptying a readable stream should be for readablestream (#421) (Thursday, 24 November)
• Re: [whatwg/dom] Meta: fix markup errors (#377) (Thursday, 24 November)
• Re: [whatwg/dom] Meta: fix markup errors (#377) (Thursday, 24 November)
• Re: [whatwg/dom] Meta: fix markup errors (#377) (Thursday, 24 November)
• Re: [whatwg/fetch] Export response's associated response (#420) (Thursday, 24 November)
• Re: [whatwg/dom] Meta: fix markup errors (#377) (Thursday, 24 November)
• Re: [whatwg/xhr] Should setting an invalid value to responseType on an XHR in LOADING/DONE state throw? (#102) (Thursday, 24 November)
• Re: [whatwg/xhr] Should setting an invalid value to responseType on an XHR in LOADING/DONE state throw? (#102) (Thursday, 24 November)
• Re: [w3c/FileAPI] Whatdoes it mean to invoke the Blob constructor with zero parameters? (#54) (Thursday, 24 November)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Thursday, 24 November)
• Re: [whatwg/fetch] Simplify HeadersInit (#418) (Thursday, 24 November)
• Re: [whatwg/fetch] Simplify HeadersInit (#418) (Thursday, 24 November)
• Re: [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Thursday, 24 November)
• Re: [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Thursday, 24 November)
• Re: [whatwg/fetch] Simplify HeadersInit (#418) (Wednesday, 23 November)
• Re: [whatwg/fetch] Simplify HeadersInit (#418) (Wednesday, 23 November)
• Re: [whatwg/fetch] nosniff and images (#395) (Wednesday, 23 November)
• Re: [heycam/webidl] Editorial: markup legacy caller correctly (#244) (Wednesday, 23 November)
• Re: [heycam/webidl] Editorial: markup legacy caller correctly (#244) (Wednesday, 23 November)
• [heycam/webidl] Editorial: markup legacy caller correctly (#244) (Wednesday, 23 November)
• Re: [whatwg/fetch] Simplify HeadersInit (#418) (Wednesday, 23 November)
• Re: [whatwg/fetch] nosniff and images (#395) (Wednesday, 23 November)
• Re: [whatwg/fetch] Simplify HeadersInit (#418) (Wednesday, 23 November)
• [whatwg/fetch] Simplify HeadersInit (#418) (Wednesday, 23 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Wednesday, 23 November)
• Re: [whatwg/fetch] OpenEndedDictionary clarification (#164) (Wednesday, 23 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Wednesday, 23 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Wednesday, 23 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Wednesday, 23 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Wednesday, 23 November)
• Re: [w3ctag/spec-reviews] IFrame support in web payments (#147) (Wednesday, 23 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Tuesday, 22 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Tuesday, 22 November)
• Re: [whatwg/dom] setAttributeNS needs special-casing for the xlink namespace (#343) (Tuesday, 22 November)
• Re: [whatwg/dom] setAttributeNS needs special-casing for the xlink namespace (#343) (Tuesday, 22 November)
• Re: [whatwg/dom] Consider adding document.parseURL(url) (#356) (Tuesday, 22 November)
• Re: [whatwg/dom] Sort out isTrusted (#338) (Tuesday, 22 November)
• Re: [whatwg/dom] Sort out isTrusted (#338) (Tuesday, 22 November)
• Re: [whatwg/dom] Validating a qualified name does not match browsers in a corner case (#319) (Tuesday, 22 November)
• Re: [whatwg/dom] Give "create an event" a target argument (#358) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [heycam/webidl] Meta: export record and sequence (#243) (Tuesday, 22 November)
• Re: [heycam/webidl] Meta: export record and sequence (#243) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• [heycam/webidl] Meta: export record and sequence (#243) (Tuesday, 22 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Tuesday, 22 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• [w3c/ServiceWorker] Meta: move the specification to the top-level directory (#1009) (Monday, 21 November)
• Re: [whatwg/fetch] Sharing cookies from one subdomain to the other (#417) (Monday, 21 November)
• Re: [whatwg/fetch] Sharing cookies from one subdomain to the other (#417) (Monday, 21 November)
• Re: [w3c/ServiceWorker] Lots of bikeshed usage issues (#965) (Monday, 21 November)
• Re: [w3c/ServiceWorker] Lots of bikeshed usage issues (#965) (Monday, 21 November)
• [w3c/ServiceWorker] Editorial: export Handle Functional Event (#1008) (Monday, 21 November)
• Re: [whatwg/fullscreen] Editorial: use the Infra Standard (#62) (Monday, 21 November)
• Re: [whatwg/fullscreen] Editorial: use the Infra Standard (#62) (Monday, 21 November)
• Re: [whatwg/fullscreen] Editorial: use the Infra Standard (#62) (Monday, 21 November)
• Re: [whatwg/url] Editorial: start using Infra Standard (#165) (Monday, 21 November)
• Re: [whatwg/url] Editorial: start using Infra Standard (#165) (Monday, 21 November)
• Re: [whatwg/dom] Editorial: make use of the Infra Standard (#375) (Monday, 21 November)
• Re: [whatwg/url] IDNA (#53) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Sunday, 20 November)
• Re: [whatwg/dom] add changed value to mutation record (#376) (Saturday, 19 November)
• Re: [whatwg/dom] add changed value to mutation record (#376) (Saturday, 19 November)
• Re: [whatwg/dom] add changed value to mutation record (#376) (Saturday, 19 November)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Friday, 18 November)
• Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Friday, 18 November)
• Re: [whatwg/dom] Editorial: make use of the Infra Standard (#375) (Friday, 18 November)
• [whatwg/dom] Editorial: make use of the Infra Standard (#375) (Friday, 18 November)
• [whatwg/fullscreen] Editorial: use the Infra Standard (#62) (Friday, 18 November)
• Re: [whatwg/url] Editorial: start using Infra Standard (#165) (Friday, 18 November)
• Re: [whatwg/url] Editorial: start using Infra Standard (#165) (Friday, 18 November)
• Re: [whatwg/url] Editorial: start using Infra Standard (#165) (Friday, 18 November)
• Re: [whatwg/url] Editorial: start using Infra Standard (#165) (Friday, 18 November)
• [whatwg/url] Editorial: start using Infra Standard (#165) (Friday, 18 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Friday, 18 November)
• Re: [heycam/webidl] Describing overloaded methods (#241) (Friday, 18 November)
• Re: [heycam/webidl] Describing overloaded methods (#241) (Thursday, 17 November)
• Re: [whatwg/dom] Clarify isTrusted (#374) (Thursday, 17 November)
• [whatwg/dom] Clarify isTrusted (#374) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] consider exposing a type attribute on Client (#1005) (Thursday, 17 November)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Thursday, 17 November)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Thursday, 17 November)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Thursday, 17 November)
• Re: [whatwg/streams] Cloning (not teeing) a readable stream, via controller tricks (#599) (Thursday, 17 November)
• [heycam/webidl] Describing overloaded methods (#241) (Thursday, 17 November)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Thursday, 17 November)
• Re: [whatwg/encoding] Inform readers about the structure of the sparsity of index-euc-kr (#78) (Thursday, 17 November)
• Re: [whatwg/encoding] Note >8835 pointers in index jis0208 cannot be reached (#83) (Wednesday, 16 November)
• Re: [whatwg/encoding] GBK encoding/decoding support (#56) (Wednesday, 16 November)
• Re: [whatwg/encoding] Add Streams support (#72) (Wednesday, 16 November)
• Re: [whatwg/encoding] Inform readers about the structure of the sparsity of index-euc-kr (#78) (Wednesday, 16 November)
• Re: [whatwg/encoding] Document an implementation buffer trick (#84) (Wednesday, 16 November)
• Re: [whatwg/encoding] Document an implementation buffer trick (#84) (Wednesday, 16 November)
• [whatwg/encoding] Document an implementation buffer trick (#84) (Wednesday, 16 November)
• Re: [whatwg/encoding] index-jis0208.txt should be JIS X 0208 and add another index file (#47) (Wednesday, 16 November)
• [whatwg/encoding] Note >8835 pointers in index jis0208 cannot be reached (#83) (Wednesday, 16 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Wednesday, 16 November)
• Re: [whatwg/encoding] Commit snapshots (#80) (Wednesday, 16 November)
• Re: [whatwg/encoding] Commit snapshots (#80) (Wednesday, 16 November)
• [whatwg/streams] Change directory listing order (#614) (Wednesday, 16 November)
• Re: [whatwg/encoding] Meta: enable commit/branch snapshots (#82) (Wednesday, 16 November)
• [whatwg/encoding] Meta: enable commit/branch snapshots (#82) (Wednesday, 16 November)
• Re: [whatwg/encoding] GBK encoding/decoding support (#56) (Wednesday, 16 November)
• Re: [whatwg/encoding] Confusion between Big5 and Big5-HKSCS encodings (#75) (Wednesday, 16 November)
• Re: [whatwg/encoding] Confusion between Big5 and Big5-HKSCS encodings (#75) (Wednesday, 16 November)
• Re: [whatwg/encoding] Confusion between KOI8-U and KOI8-RU encodings (#74) (Wednesday, 16 November)
• Re: [whatwg/encoding] Confusion between KOI8-U and KOI8-RU encodings (#74) (Wednesday, 16 November)
• Re: [whatwg/encoding] Consider adding "replacement" as a label for the replacement encoding (#70) (Wednesday, 16 November)
• Re: [w3c/webcomponents] createElement step 5 is inconsistent with parser-created customized built-in elements (#608) (Wednesday, 16 November)
• Re: [whatwg/dom] Remove incorrect customized built-in element checks (#373) (Wednesday, 16 November)
• Re: [w3c/FileAPI] Remove Jonas Sicking from Editor list (#53) (Tuesday, 15 November)
• Re: [whatwg/fetch] Does terminating a fetch before headers come back reject the promise? (#416) (Tuesday, 15 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Tuesday, 15 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Tuesday, 15 November)
• [heycam/webidl] No seemingly consistent Shepherd story (#240) (Tuesday, 15 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Tuesday, 15 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Tuesday, 15 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Tuesday, 15 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Tuesday, 15 November)
• Re: [whatwg/encoding] Editorial style nits (#76) (Tuesday, 15 November)
• Re: [whatwg/encoding] Editorial style nits (#76) (Tuesday, 15 November)
• Re: [whatwg/encoding] Editorial: cross-reference more IDL terms (#81) (Tuesday, 15 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Tuesday, 15 November)
• Re: [w3c/webcomponents] createElement step 5 is inconsistent with parser-created customized built-in elements (#608) (Tuesday, 15 November)
• Re: [whatwg/encoding] Fix #17: gb18030 cannot encode U+E5E5 (#25) (Tuesday, 15 November)
• Re: [whatwg/fetch] Sharing cookies from one subdomain to the other (#417) (Tuesday, 15 November)
• Re: [whatwg/fetch] Does terminating a fetch before headers come back reject the promise? (#416) (Tuesday, 15 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Monday, 14 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Monday, 14 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Monday, 14 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Monday, 14 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Monday, 14 November)
• Re: [whatwg/xhr] Rq (#100) (Monday, 14 November)
• [heycam/webidl] Meta: export record mappings (#239) (Monday, 14 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Monday, 14 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Saturday, 12 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Saturday, 12 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Saturday, 12 November)
• [whatwg/xhr] Clean up "fire an event" and derivatives (#99) (Saturday, 12 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Saturday, 12 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Saturday, 12 November)
• Re: [whatwg/xhr] Entry settings object usage is probably wrong (#98) (Saturday, 12 November)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Saturday, 12 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Saturday, 12 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Saturday, 12 November)
• Re: [whatwg/xhr] Entry settings object usage is probably wrong (#98) (Friday, 11 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Friday, 11 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Friday, 11 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Friday, 11 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Friday, 11 November)
• [heycam/webidl] ByteString still seems off (#236) (Friday, 11 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Friday, 11 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Friday, 11 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Friday, 11 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Friday, 11 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Friday, 11 November)
• Re: [w3c/ServiceWorker] ServiceWorkerMessageEvent isn't consistent with MessageEvent (#989) (Friday, 11 November)
• Re: [w3c/ServiceWorker] Use Extended MessageEvent (6c68bd8) (Friday, 11 November)
• Re: [w3c/ServiceWorker] ServiceWorkerMessageEvent isn't consistent with MessageEvent (#989) (Friday, 11 November)
• Re: [w3c/ServiceWorker] Use Extended MessageEvent (6c68bd8) (Friday, 11 November)
• Re: [w3c/ServiceWorker] Use Extended MessageEvent (6c68bd8) (Friday, 11 November)
• Re: [whatwg/encoding] Serializing internal TextDecoder state? (#7) (Friday, 11 November)
• Re: [whatwg/encoding] Serializing internal TextDecoder state? (#7) (Friday, 11 November)
• Re: [whatwg/encoding] Confusion between Big5 and Big5-HKSCS encodings (#75) (Friday, 11 November)
• Re: [whatwg/encoding] Editorial style nits (#76) (Friday, 11 November)
• Re: [whatwg/encoding] Editorial style nits (#76) (Friday, 11 November)
• Re: [whatwg/encoding] Editorial: cross-reference more IDL terms (#81) (Friday, 11 November)
• [whatwg/encoding] Editorial: cross-reference more IDL terms (#81) (Friday, 11 November)
• Re: [whatwg/encoding] Editorial style nits (#76) (Friday, 11 November)
• [whatwg/encoding] Commit snapshots (#80) (Friday, 11 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Friday, 11 November)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Friday, 11 November)
• Re: [whatwg/fetch] Update fetch.bs: bar.com should be bar.invalid (#415) (Thursday, 10 November)
• Re: [whatwg/fetch] Update fetch.bs: bar.com should be bar.invalid (#415) (Thursday, 10 November)
• Re: [whatwg/encoding] Convert to bikeshed. (#48) (Thursday, 10 November)
• Re: [whatwg/encoding] Convert to bikeshed. (#48) (Thursday, 10 November)
• Re: [whatwg/encoding] Bikeshed conversion (#79) (Thursday, 10 November)
• Re: [whatwg/encoding] Bikeshed conversion (#79) (Thursday, 10 November)
• Re: [whatwg/fetch] Update fetch.bs: bar.com should be bar.invalid (#415) (Thursday, 10 November)
• Re: [whatwg/encoding] Bikeshed conversion (#79) (Thursday, 10 November)
• Re: [whatwg/encoding] Bikeshed conversion (#79) (Thursday, 10 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 10 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 10 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 10 November)
• Re: [whatwg/fetch] "bar.com" in the example (#414) (Thursday, 10 November)
• Re: [whatwg/encoding] Bikeshed conversion (#79) (Thursday, 10 November)
• [whatwg/encoding] Bikeshed conversion (#79) (Thursday, 10 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Thursday, 10 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Thursday, 10 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Thursday, 10 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Thursday, 10 November)
• [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Thursday, 10 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Thursday, 10 November)
• Re: [w3c/webcomponents] Constructor arguments in custom elements (#605) (Thursday, 10 November)
• Re: [w3c/ServiceWorker] Behavior of the onfetch setter regarding no-fetch service workers (#1004) (Thursday, 10 November)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Thursday, 10 November)
• Re: [whatwg/dom] Remove SVGZoomEvent? (#283) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• Re: [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• Re: [heycam/webidl] Make [SameObject] beneficial (#212) (Wednesday, 9 November)
• Re: [whatwg/fetch] Export 'keepalive flag', and tie it to 'request'. (#413) (Wednesday, 9 November)
• Re: [whatwg/fetch] Export 'keepalive flag', and tie it to 'request'. (#413) (Wednesday, 9 November)
• Re: [whatwg/fetch] Export 'keepalive flag', and tie it to 'request'. (#413) (Wednesday, 9 November)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Wednesday, 9 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Tuesday, 8 November)
• Re: [whatwg/fetch] Export 'keepalive flag', and tie it to 'request'. (#413) (Tuesday, 8 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Tuesday, 8 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Tuesday, 8 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Tuesday, 8 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Tuesday, 8 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Tuesday, 8 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Tuesday, 8 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Tuesday, 8 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Tuesday, 8 November)
• [whatwg/xhr] Convert XHR to bikeshed (#97) (Tuesday, 8 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Tuesday, 8 November)
• Re: [heycam/webidl] Globals can define a named property setter (#231) (Tuesday, 8 November)
• Re: [heycam/webidl] Globals can define a named property setter (#231) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Globals can define a named property setter (#231) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• [heycam/webidl] Globals can define a named property setter (#231) (Tuesday, 8 November)
• Re: [whatwg/url] Change host parser for non-special schemes (#148) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [whatwg/url] Change host parser for non-special schemes (#148) (Tuesday, 8 November)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Tuesday, 8 November)
• Re: [heycam/webidl] #es-to-dictionary and #dictionary-to-es do not have reader-discernable titles (#228) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] get-buffer-source-{reference,copy} ought to point to the algorithm (#229) (Tuesday, 8 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Tuesday, 8 November)
• Re: [whatwg/dom] "The assignedSlot attribute’s getter must return..." (#369) (Tuesday, 8 November)
• Re: [whatwg/dom] "The assignedSlot attribute’s getter must return..." (#369) (Tuesday, 8 November)
• Re: [w3c/screen-orientation] Event firing needs fixes (#93) (Monday, 7 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Monday, 7 November)
• Re: [whatwg/dom] "The adoptNode(node) method, when invoked, must ..." (#368) (Monday, 7 November)
• Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Monday, 7 November)
• Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Monday, 7 November)
• Re: [w3c/ServiceWorker] Editorial: more link-defaults and anchors cleanup (#1002) (Monday, 7 November)
• Re: [heycam/webidl] enum local to interface (#227) (Monday, 7 November)
• Re: [heycam/webidl] add a type to represent the undefined value (#60) (Monday, 7 November)
• Re: [heycam/webidl] add a type to represent the undefined value (#60) (Monday, 7 November)
• [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Monday, 7 November)
• Re: [w3c/webcomponents] Add an assignedElements() method (#602) (Monday, 7 November)
• Re: [whatwg/url] Semi-colon (;) should be illegal in URL hostname parsing (#159) (Monday, 7 November)
• Re: [heycam/webidl] Add instructions on when & where to file issues (#225) (Monday, 7 November)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Monday, 7 November)
• Re: [whatwg/url] percent-encoding rules don't match browsers? (#162) (Monday, 7 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Monday, 7 November)
• Re: [whatwg/fetch] Streams and fetches that outlive the environment settings object (#411) (Monday, 7 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Monday, 7 November)
• Re: [whatwg/dom] Upstream `delegatesFocus` property of ShadowRootInit from W3C spec. (#367) (Monday, 7 November)
• Re: [heycam/webidl] Fix internal methods that only target platform objects w/ indexed/named props (#202) (Monday, 7 November)
• Re: [w3c/webcomponents] Add an assignedElements() method (#602) (Monday, 7 November)
• Re: [w3c/ServiceWorker] Editorial: more link-defaults and anchors cleanup (#1002) (Monday, 7 November)
• Re: [heycam/webidl] Fix internal methods that only target platform objects w/ indexed/named props (#202) (Sunday, 6 November)
• Re: [heycam/webidl] Fix internal methods that only target platform objects w/ indexed/named props (#202) (Sunday, 6 November)
• Re: [whatwg/fetch] Use auto-linking for CSP3. (#410) (Friday, 4 November)
• Re: [whatwg/fetch] Use auto-linking for CSP3. (#410) (Friday, 4 November)
• Re: [whatwg/fullscreen] wip (#61) (Friday, 4 November)
• Re: [whatwg/fullscreen] wip (#61) (Friday, 4 November)
• Re: [whatwg/fullscreen] wip (#61) (Friday, 4 November)
• Re: [whatwg/fetch] Editorial: remove direct w3c.github.io links (#409) (Friday, 4 November)
• Re: [whatwg/fetch] Editorial: remove direct w3c.github.io links (#409) (Friday, 4 November)
• Re: [whatwg/fetch] Editorial: remove direct w3c.github.io links (#409) (Friday, 4 November)
• [whatwg/fetch] Editorial: remove direct w3c.github.io links (#409) (Friday, 4 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Remove all references to RegExp. (#220) (Thursday, 3 November)
• Re: [whatwg/fetch] Meta: set up the architecture for commit/branch snapshots (#408) (Thursday, 3 November)
• [whatwg/fetch] Meta: set up the architecture for commit/branch snapshots (#408) (Thursday, 3 November)
• Re: [whatwg/fetch] Editorial: "stream of data" reference (#406) (Thursday, 3 November)
• Re: [whatwg/url] Meta: set up the architecture for commit/branch snapshots (#160) (Thursday, 3 November)
• [whatwg/url] Meta: set up the architecture for commit/branch snapshots (#160) (Thursday, 3 November)
• Re: [whatwg/dom] Meta: commit snapshot cleanup (#363) (Thursday, 3 November)
• Re: [whatwg/dom] Meta: commit snapshot cleanup (#363) (Thursday, 3 November)
• Re: [w3c/ServiceWorker] Define client.reserved (d88e979) (Thursday, 3 November)
• [whatwg/dom] Add a section on defining a new event (#364) (Thursday, 3 November)
• [whatwg/dom] Meta: commit snapshot cleanup (#363) (Wednesday, 2 November)
• Re: [whatwg/dom] Set up the architecture for commit/branch snapshots (#350) (Wednesday, 2 November)
• Re: [whatwg/dom] Set up the architecture for commit/branch snapshots (#350) (Wednesday, 2 November)
• Re: [whatwg/dom] Consider adding document.parseURL(url) (#356) (Wednesday, 2 November)
• Re: [w3c/webcomponents] When to PUBLIC? (#599) (Wednesday, 2 November)
• Re: [w3c/ServiceWorker] Export dfn for HTML and DOM (66a4fd9) (Wednesday, 2 November)
• Re: [w3c/ServiceWorker] Editorial: export terms for Fetch (#999) (Wednesday, 2 November)
• Re: [w3c/ServiceWorker] Export dfn for HTML and DOM (66a4fd9) (Wednesday, 2 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Wednesday, 2 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Wednesday, 2 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Wednesday, 2 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• Re: [whatwg/url] Change host parser for non-special schemes (#148) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove support for [Unforgeable]-annotated interfaces (#215) (Tuesday, 1 November)
• [heycam/webidl] Remove support for [Unforgeable]-annotated interfaces (#215) (Tuesday, 1 November)
• Re: [w3c/ServiceWorker] Editorial: export terms for Fetch (#999) (Tuesday, 1 November)
• Re: [whatwg/fullscreen] wip (#61) (Tuesday, 1 November)
• [whatwg/fullscreen] wip (#61) (Tuesday, 1 November)
• Re: [whatwg/fetch] Annevk/conversion cleanup (#407) (Tuesday, 1 November)
• [whatwg/fetch] Annevk/conversion cleanup (#407) (Tuesday, 1 November)
• Re: [whatwg/fetch] CORS protocol and HTTP caches (#402) (Tuesday, 1 November)
• Re: [whatwg/dom] Set up the architecture for commit/branch snapshots (#350) (Tuesday, 1 November)
• Re: [whatwg/dom] Set up the architecture for commit/branch snapshots (#350) (Tuesday, 1 November)
• Re: [whatwg/url] Percent-decode more stuff? (#87) (Tuesday, 1 November)
• Re: [whatwg/dom] Set up the architecture for commit/branch snapshots (#350) (Tuesday, 1 November)
• Re: [whatwg/fetch] CORS protocol and HTTP caches (#402) (Tuesday, 1 November)
• Re: [whatwg/dom] Editorial: resolve all novel bikeshed "link errors" (#361) (Tuesday, 1 November)
• Re: [whatwg/dom] Editorial: resolve all novel bikeshed "link errors" (#361) (Tuesday, 1 November)
• Re: [whatwg/url] Change host parser for non-special schemes (#148) (Tuesday, 1 November)

Anthony Ramine

• Re: [w3c/DOM-Parsing] Fix 2 issues in createContextualFragment (#23) (Monday, 14 November)
• [w3c/DOM-Parsing] Fix 2 issues in createContextualFragment (#23) (Tuesday, 8 November)

Aryeh Gregor

• Re: [whatwg/dom] Remove SVGZoomEvent? (#283) (Monday, 7 November)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Monday, 7 November)
• Re: [w3c/uievents] Require support or non-support for legacy init*Event (#112) (Tuesday, 1 November)
• Re: [whatwg/dom] document.createEvent() supports lots of events that most UAs do not support initializers for (#362) (Tuesday, 1 November)
• [whatwg/dom] document.createEvent() supports lots of events that most UAs do not support initializers for (#362) (Tuesday, 1 November)
• Re: [w3c/uievents] Require support or non-support for legacy init*Event (#112) (Tuesday, 1 November)

Axel Nennker

• Re: [heycam/webidl] enum local to interface (#227) (Monday, 7 November)
• Re: [heycam/webidl] enum local to interface (#227) (Monday, 7 November)
• [heycam/webidl] enum local to interface (#227) (Monday, 7 November)

beidson

• Re: [w3c/IndexedDB] Problem with test IndexedDB/idbobjectstore-rename-store.html (#113) (Friday, 11 November)
• Re: [w3c/IndexedDB] Problem with test IndexedDB/idbobjectstore-rename-store.html (#113) (Friday, 11 November)
• [w3c/IndexedDB] Problem with test IndexedDB/idbobjectstore-rename-store.html (#113) (Friday, 11 November)
• Re: [w3c/IndexedDB] Clear object store handle's index set when deleted. Resolves #109 (#111) (Saturday, 5 November)
• Re: [w3c/IndexedDB] Behavior tested by transaction-abort-multiple-metadata-revert.html is not obviously specified anywhere (#109) (Friday, 4 November)
• Re: [w3c/IndexedDB] Behavior tested by transaction-abort-multiple-metadata-revert.html is not obviously specified anywhere (#109) (Friday, 4 November)
• [w3c/IndexedDB] Behavior tested by transaction-abort-multiple-metadata-revert.html is not obviously specified anywhere (#109) (Friday, 4 November)

Ben Bangert

• Re: [w3c/push-api] Add a messageHandlingError event (#214) (Wednesday, 2 November)
• [w3c/push-api] Add a messageHandlingError event (#214) (Wednesday, 2 November)

Ben Kelly

• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Wednesday, 23 November)
• Re: [whatwg/fetch] Simplify HeadersInit (#418) (Wednesday, 23 November)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Monday, 21 November)
• Re: [w3c/ServiceWorker] Allow waitUntil to be called multiple times, async (#771) (Monday, 21 November)
• Re: [w3c/ServiceWorker] consider exposing a type attribute on Client (#1005) (Friday, 18 November)
• Re: [w3c/ServiceWorker] consider exposing a type attribute on Client (#1005) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] consider exposing self.clients on window and other worker globals (#955) (Wednesday, 16 November)
• [w3c/ServiceWorker] consider exposing a type attribute on Client (#1005) (Wednesday, 16 November)
• Re: [w3c/ServiceWorker] serviceworker for iframes with srcdoc (#765) (Wednesday, 16 November)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Monday, 14 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Thursday, 10 November)
• Re: [w3c/ServiceWorker] Service worker Failed to load resource: net::ERR_UNSAFE_REDIRECT (#1001) (Friday, 4 November)
• Re: [w3c/ServiceWorker] Service worker Failed to load resource: net::ERR_UNSAFE_REDIRECT (#1001) (Friday, 4 November)
• Re: [w3c/ServiceWorker] Service worker Failed to load resource: net::ERR_UNSAFE_REDIRECT (#1001) (Wednesday, 2 November)
• Re: [w3c/ServiceWorker] Service worker Failed to load resource: net::ERR_UNSAFE_REDIRECT (#1001) (Wednesday, 2 November)

Boris Zbarsky

• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 29 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 29 November)
• Re: [whatwg/fetch] FormData content-type doesn't match form submission behavior in browsers (#422) (Monday, 28 November)
• Re: [whatwg/fetch] FormData content-type doesn't match form submission behavior in browsers (#422) (Friday, 25 November)
• [whatwg/fetch] FormData content-type doesn't match form submission behavior in browsers (#422) (Thursday, 24 November)
• [w3c/FileAPI] Whatdoes it mean to invoke the Blob constructor with zero parameters? (#54) (Thursday, 24 November)
• Re: [heycam/webidl] Remove the RegExp type (#148) (Thursday, 24 November)
• Re: [whatwg/fetch] Simplify HeadersInit (#418) (Wednesday, 23 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Tuesday, 22 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Tuesday, 22 November)
• Re: [heycam/webidl] Describing overloaded methods (#241) (Thursday, 17 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Thursday, 17 November)
• Re: [whatwg/xhr] Entry settings object usage is probably wrong (#98) (Monday, 14 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Monday, 14 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Monday, 14 November)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Friday, 11 November)
• Re: [heycam/webidl] [Clamp] and [EnforceRange] reduce the max value long long supports (#237) (Friday, 11 November)
• Re: [heycam/webidl] [Clamp] and [EnforceRange] reduce the max value long long supports (#237) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] [Clamp] and [EnforceRange] reduce the max value long long supports (#237) (Friday, 11 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Friday, 11 November)
• Re: [heycam/webidl] Modernize and clean up dictionary type conversions (#234) (Thursday, 10 November)
• Re: [heycam/webidl] Modernize and clean up dictionary type conversions (#234) (Thursday, 10 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Thursday, 10 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Thursday, 10 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Thursday, 10 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Wednesday, 9 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Wednesday, 9 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Wednesday, 9 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Wednesday, 9 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Wednesday, 9 November)
• [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Wednesday, 9 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Wednesday, 9 November)
• Re: [heycam/webidl] Minor fixups to creating an operation Function (#232) (Wednesday, 9 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Tuesday, 8 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Tuesday, 8 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Tuesday, 8 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Tuesday, 8 November)
• Re: [heycam/webidl] Investigate banning nullable enums (#213) (Tuesday, 8 November)
• Re: [heycam/webidl] Investigate banning nullable enums (#213) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Globals can define a named property setter (#231) (Tuesday, 8 November)
• Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Tuesday, 8 November)
• Re: [heycam/webidl] #es-to-dictionary and #dictionary-to-es do not have reader-discernable titles (#228) (Tuesday, 8 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Monday, 7 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Monday, 7 November)
• Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Monday, 7 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Monday, 7 November)
• Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Monday, 7 November)
• Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Monday, 7 November)
• Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Monday, 7 November)
• Re: [heycam/webidl] enum local to interface (#227) (Monday, 7 November)
• Re: [heycam/webidl] Fix typo in sequence type conversion example (#223) (Saturday, 5 November)
• Re: [heycam/webidl] Fix typo in sequence type conversion example (#223) (Saturday, 5 November)
• Re: [heycam/webidl] Prevent [[SetPrototypeOf]] on all globals (#209) (Thursday, 3 November)
• Re: [heycam/webidl] Prevent [[SetPrototypeOf]] on all globals (#209) (Thursday, 3 November)
• Re: [heycam/webidl] Remove all references to RegExp. (#220) (Thursday, 3 November)
• Re: [heycam/webidl] Remove all references to RegExp. (#220) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Union types with colliding enum values (#219) (Thursday, 3 November)
• Re: [whatwg/dom] document.createEvent() supports lots of events that most UAs do not support initializers for (#362) (Tuesday, 1 November)
• Re: [w3c/uievents] Require support or non-support for legacy init*Event (#112) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)

Brad Hill

• Re: [w3ctag/spec-reviews] Unblocking the HTTPS Transitions (#74) (Tuesday, 1 November)

Brian Terlson

• Re: [whatwg/streams] "non-negative" or "nonnegative" ? (#585) (Wednesday, 2 November)
• Re: [whatwg/streams] "non-negative" or "nonnegative" ? (#585) (Wednesday, 2 November)

Cameron Steele

• Re: [whatwg/url] fix typo in IPv4 number parser algorithm (#166) (Sunday, 27 November)
• Re: [whatwg/url] fix typo in IPv4 number parser algorithm (#166) (Sunday, 27 November)
• Re: [whatwg/url] fix typo in IPv4 number parser algorithm (#166) (Sunday, 27 November)
• Re: [whatwg/url] fix typo in IPv4 number parser algorithm (#166) (Saturday, 26 November)
• [whatwg/url] fix typo in IPv4 number parser algorithm (#166) (Saturday, 26 November)

chaals

• Re: [w3c/manifest] Update references to W3C if available (#526) (Friday, 11 November)
• Re: [w3c/IndexedDB] Horizontal review… (#112) (Thursday, 10 November)
• [w3c/IndexedDB] Horizontal review… (#112) (Thursday, 10 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 9 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 9 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)

Chris Rebert

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Monday, 28 November)

chris van wiemeersch

• Re: [w3c/gamepad] UA applied mapping cannot be escaped (#1) (Wednesday, 16 November)
• Re: [w3c/gamepad] Need to spec better support for control mapping (#7) (Wednesday, 16 November)
• Re: [w3c/gamepad] UA applied mapping cannot be escaped (#1) (Wednesday, 16 November)

cynthia

• Re: [w3c/DOM-Parsing] Fix 2 issues in createContextualFragment (#23) (Monday, 14 November)
• Re: [w3c/DOM-Parsing] Step 4 of createContextualFragment is not enough (#15) (Monday, 14 November)
• Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) (Monday, 14 November)
• Re: [w3c/DOM-Parsing] Fix 2 issues in createContextualFragment (#23) (Tuesday, 8 November)

Cyrille Tuzi

• Re: [w3c/webcomponents] Add an assignedElements() method (#602) (Monday, 7 November)
• Re: [w3c/webcomponents] Add an assignedElements() method (#602) (Sunday, 6 November)
• [w3c/webcomponents] Add an assignedElements() method (#602) (Saturday, 5 November)

Cătălin Badea

• [w3c/ServiceWorker] .ready promise should be resolved after updating registration.state properties (#1011) (Tuesday, 22 November)
• [w3c/ServiceWorker] Behavior of the onfetch setter regarding no-fetch service workers (#1004) (Wednesday, 9 November)

Daniel Appelquist

• Re: [w3ctag/spec-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Wednesday, 23 November)
• Re: [w3ctag/spec-reviews] Privacy Mode (#101) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] privacy of sensor & other exotic APIs (#129) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] privacy of sensor & other exotic APIs (#129) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] privacy of sensor & other exotic APIs (#129) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Tuesday, 1 November)

Daniel Olano

• Re: [w3c/webcomponents] "is" attribute for autonomous custom elements (#603) (Friday, 11 November)
• Re: [w3c/webcomponents] Constructor arguments in custom elements (#605) (Friday, 11 November)
• [w3c/webcomponents] Constructor arguments in custom elements (#605) (Thursday, 10 November)
• [w3c/webcomponents] "is" attribute for autonomous custom elements (#603) (Wednesday, 9 November)

Dave Tapuska

• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Wednesday, 9 November)
• [w3c/touch-events] Add a default passive algorithm definition for Window, Document and HTMLElement. (#75) (Wednesday, 9 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Monday, 7 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Friday, 4 November)
• [whatwg/dom] Add the ability for an EventTarget to provide an algorithm to override (#366) (Friday, 4 November)
• [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Friday, 4 November)
• Re: [w3c/uievents] Require support or non-support for legacy init*Event (#112) (Tuesday, 1 November)

David Frank

• Re: [whatwg/fetch] 204 and json (#113) (Monday, 7 November)

Dennis Kugelmann

• Re: [w3c/webcomponents] [Shadow]: Declarative Shadow DOM (bugzilla: 28441) (#71) (Monday, 28 November)

Derek Gray

• Re: [whatwg/dom] "The assignedSlot attribute’s getter must return..." (#369) (Friday, 11 November)
• Re: [whatwg/dom] "The assignedSlot attribute’s getter must return..." (#369) (Tuesday, 8 November)
• Re: [whatwg/dom] "The assignedSlot attribute’s getter must return..." (#369) (Tuesday, 8 November)
• [whatwg/dom] "The assignedSlot attribute’s getter must return..." (#369) (Monday, 7 November)
• Re: [whatwg/dom] "The adoptNode(node) method, when invoked, must ..." (#368) (Monday, 7 November)
• Re: [whatwg/dom] "The adoptNode(node) method, when invoked, must ..." (#368) (Monday, 7 November)
• [whatwg/dom] "The adoptNode(node) method, when invoked, must ..." (#368) (Monday, 7 November)
• Re: [w3c/webcomponents] [Imports]: Consider changing component location to component identifier (bugzilla: 21253) (#235) (Friday, 4 November)

Domenic Denicola

• Re: [whatwg/streams] Convert writable stream tests to web platform tests format (#492) (Tuesday, 29 November)
• Re: [whatwg/streams] us.abort() is not called if us.write() fails (#620) (Tuesday, 29 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Tuesday, 29 November)
• Re: [w3ctag/spec-reviews] IFrame support in web payments (#147) (Tuesday, 29 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Monday, 28 November)
• Re: [whatwg/streams] Do not assert() when writer is detached during close() (#621) (Saturday, 26 November)
• Re: [whatwg/streams] us.abort() is not called if us.write() fails (#620) (Saturday, 26 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Saturday, 26 November)
• Re: [w3c/ServiceWorker] Fix arguments to "fetch a classic worker script" (#1012) (Wednesday, 23 November)
• Re: [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Wednesday, 23 November)
• Re: [whatwg/fetch] Simplify HeadersInit (#418) (Wednesday, 23 November)
• Re: [w3ctag/spec-reviews] IFrame support in web payments (#147) (Wednesday, 23 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Tuesday, 22 November)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Tuesday, 22 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Tuesday, 22 November)
• Re: [whatwg/streams] TransformStream byte streams (#616) (Tuesday, 22 November)
• [w3c/ServiceWorker] Fix arguments to "fetch a classic worker script" (#1012) (Tuesday, 22 November)
• Re: [whatwg/streams] "Wait until any ongoing write finishes (i.e. the..." (#618) (Tuesday, 22 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Tuesday, 22 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Sunday, 20 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Sunday, 20 November)
• Re: [w3c/webcomponents] Copying global `<style>` textContent into ShadowDOM roots is not ideal. (#609) (Saturday, 19 November)
• Re: [w3c/webcomponents] Copying global `<style>` textContent into ShadowDOM roots is not ideal. (#609) (Saturday, 19 November)
• Re: [w3c/webcomponents] Copying global `<style>` textContent into ShadowDOM roots is not ideal. (#609) (Saturday, 19 November)
• Re: [w3c/webcomponents] Best way to distribute global styles into shadow root? (#609) (Saturday, 19 November)
• Re: [w3c/webcomponents] Best way to distribute global styles into shadow root? (#609) (Saturday, 19 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Saturday, 19 November)
• Re: [whatwg/streams] Create Geranebb21 (#615) (Friday, 18 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Friday, 18 November)
• Re: [heycam/webidl] Should we x-link base concepts to the Infra Standard? (#242) (Thursday, 17 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Thursday, 17 November)
• Re: [whatwg/dom] Clarify isTrusted (#374) (Thursday, 17 November)
• Re: [whatwg/streams] Cloning (not teeing) a readable stream, via controller tricks (#599) (Thursday, 17 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Thursday, 17 November)
• Re: [whatwg/streams] Cloning (not teeing) a readable stream, via controller tricks (#599) (Wednesday, 16 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Wednesday, 16 November)
• Re: [whatwg/streams] Change directory listing order (#614) (Wednesday, 16 November)
• Re: [whatwg/streams] Change directory listing order (#614) (Wednesday, 16 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Wednesday, 16 November)
• Re: [whatwg/encoding] Add Streams support (#72) (Wednesday, 16 November)
• Re: [whatwg/streams] Invoking methods should not call .apply() (#613) (Wednesday, 16 November)
• [whatwg/dom] Remove incorrect customized built-in element checks (#373) (Tuesday, 15 November)
• Re: [w3c/webcomponents] createElement step 5 is inconsistent with parser-created customized built-in elements (#608) (Tuesday, 15 November)
• Re: [whatwg/fetch] Does terminating a fetch before headers come back reject the promise? (#416) (Tuesday, 15 November)
• Re: [whatwg/streams] Editorial: "return undefined." vs. "return" (#587) (Tuesday, 15 November)
• Re: [whatwg/streams] Editorial: consistently use minimal returns (#612) (Tuesday, 15 November)
• Re: [whatwg/streams] Editorial: consistently use minimal returns (#612) (Tuesday, 15 November)
• Re: [whatwg/streams] Editorial: consistently use minimal returns (#612) (Tuesday, 15 November)
• Re: [whatwg/streams] Editorial: consistently use minimal returns (#612) (Tuesday, 15 November)
• Re: [whatwg/streams] Mark promise rejections for "state promises" as handled (#607) (Tuesday, 15 November)
• Re: [whatwg/streams] Marking promise rejections as handled (#547) (Tuesday, 15 November)
• [whatwg/streams] Editorial: consistently use minimal returns (#612) (Monday, 14 November)
• Re: [whatwg/streams] "non-negative" or "nonnegative" ? (#585) (Monday, 14 November)
• Re: [whatwg/streams] "non-negative" or "nonnegative" ? (#585) (Monday, 14 November)
• Re: [whatwg/streams] Mark promise rejections for "state promises" as handled (#607) (Monday, 14 November)
• Re: [whatwg/streams] Mark promise rejections for "state promises" as handled (#607) (Monday, 14 November)
• [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Monday, 14 November)
• [whatwg/fetch] Does terminating a fetch before headers come back reject the promise? (#416) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [whatwg/streams] Minor fixes to writable-stream tests (#610) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [w3c/webcomponents] Constructing a custom element synchronously drops prefix from its name (#607) (Sunday, 13 November)
• Re: [w3c/webcomponents] Constructing a custom element synchronously drops prefix from its name (#607) (Sunday, 13 November)
• Re: [w3c/webcomponents] Constructing a custom element synchronously drops prefix from its name (#607) (Sunday, 13 November)
• Re: [w3c/webcomponents] Constructing a custom element synchronously drops prefix from its name (#607) (Sunday, 13 November)
• Re: [whatwg/xhr] Entry settings object usage is probably wrong (#98) (Saturday, 12 November)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Saturday, 12 November)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Friday, 11 November)
• Re: [heycam/webidl] [Clamp] and [EnforceRange] reduce the max value long long supports (#237) (Friday, 11 November)
• Re: [heycam/webidl] [Clamp] and [EnforceRange] reduce the max value long long supports (#237) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [whatwg/xhr] Entry settings object usage is probably wrong (#98) (Friday, 11 November)
• Re: [whatwg/xhr] Entry settings object usage is probably wrong (#98) (Friday, 11 November)
• [whatwg/xhr] Entry settings object usage is probably wrong (#98) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [whatwg/encoding] Commit snapshots (#80) (Friday, 11 November)
• [heycam/webidl] Modernize and clean up dictionary type conversions (#234) (Thursday, 10 November)
• Re: [whatwg/streams] rework recording-streams helper (#609) (Thursday, 10 November)
• Re: [whatwg/streams] skip WPT dir if not present (#608) (Thursday, 10 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Thursday, 10 November)
• Re: [w3c/webcomponents] Constructor arguments in custom elements (#605) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Thursday, 10 November)
• Re: [whatwg/streams] skip WPT dir if not present (#608) (Thursday, 10 November)
• Re: [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• Re: [whatwg/dom] Add a section on defining a new event (#364) (Thursday, 10 November)
• Re: [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• Re: [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• [whatwg/streams] Mark promise rejections for "state promises" as handled (#607) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Wednesday, 9 November)
• Re: [whatwg/streams] Closing the controller with a pipe (#606) (Wednesday, 9 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Wednesday, 9 November)
• Re: [heycam/webidl] #es-to-dictionary and #dictionary-to-es do not have reader-discernable titles (#228) (Wednesday, 9 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Wednesday, 9 November)
• Re: [whatwg/streams] Closing the controller with a pipe (#606) (Wednesday, 9 November)
• Re: [whatwg/streams] Closing the controller with a pipe (#606) (Wednesday, 9 November)
• Re: [whatwg/fetch] Streams and fetches that outlive the environment settings object (#411) (Tuesday, 8 November)
• Re: [whatwg/streams] Marking promise rejections as handled (#547) (Tuesday, 8 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Tuesday, 8 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Tuesday, 8 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Tuesday, 8 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Tuesday, 8 November)
• [heycam/webidl] Minor fixups to creating an operation Function (#232) (Tuesday, 8 November)
• Re: [heycam/webidl] get-buffer-source-{reference,copy} ought to point to the algorithm (#229) (Monday, 7 November)
• Re: [heycam/webidl] get-buffer-source-{reference,copy} ought to point to the algorithm (#229) (Monday, 7 November)
• Re: [heycam/webidl] #es-to-dictionary and #dictionary-to-es do not have reader-discernable titles (#228) (Monday, 7 November)
• Re: [whatwg/streams] port piping tests to WPT (#603) (Monday, 7 November)
• Re: [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Monday, 7 November)
• Re: [whatwg/streams] Marking promise rejections as handled (#547) (Monday, 7 November)
• Re: [heycam/webidl] #es-to-dictionary and #dictionary-to-es do not have reader-discernable titles (#228) (Monday, 7 November)
• Re: [w3c/screen-orientation] Event firing needs fixes (#93) (Monday, 7 November)
• Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Monday, 7 November)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Monday, 7 November)
• Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Monday, 7 November)
• [w3c/screen-orientation] Confusiong between "_pending-promise_" and "doc's pending promise" (#94) (Monday, 7 November)
• [w3c/screen-orientation] Event firing needs fixes (#93) (Monday, 7 November)
• Re: [heycam/webidl] Fix internal methods that only target platform objects w/ indexed/named props (#202) (Sunday, 6 November)
• Re: [heycam/webidl] Add missing index increment and use index variable (#224) (Sunday, 6 November)
• Re: [heycam/webidl] Add missing index increment and use index variable (#224) (Sunday, 6 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Saturday, 5 November)
• Re: [whatwg/streams] test non-function strategy.size (#594) (Friday, 4 November)
• [whatwg/streams] Cloning (not teeing) a readable stream, via controller tricks (#599) (Friday, 4 November)
• [whatwg/fetch] Streams and fetches that outlive the environment settings object (#411) (Friday, 4 November)
• Re: [whatwg/url] percent-encoding rules don't match browsers? (#162) (Friday, 4 November)
• Re: [whatwg/url] percent-encoding rules don't match browsers? (#162) (Friday, 4 November)
• Re: [whatwg/url] path /. (#161) (Friday, 4 November)
• Re: [whatwg/streams] fix error description (#596) (Friday, 4 November)
• Re: [whatwg/streams] test non-function strategy.size (#594) (Friday, 4 November)
• [w3c/ServiceWorker] Editorial: more link-defaults and anchors cleanup (#1002) (Thursday, 3 November)
• Re: [whatwg/streams] sync spec and implementation of autoAllocateChunkSize (#592) (Thursday, 3 November)
• Re: [whatwg/streams] sync spec and implementation of autoAllocateChunkSize (#592) (Thursday, 3 November)
• Re: [whatwg/streams] test non-function sink.abort (#591) (Thursday, 3 November)
• Re: [whatwg/streams] update travis config (#595) (Thursday, 3 November)
• [heycam/webidl] Set up auto-deploy to GitHub pages from master (#221) (Thursday, 3 November)
• Re: [whatwg/streams] update travis config (#595) (Thursday, 3 November)
• Re: [whatwg/streams] update travis config (#595) (Thursday, 3 November)
• Re: [whatwg/streams] Run ReadableStream tests against ReadableByteStream (#217) (Thursday, 3 November)
• Re: [heycam/webidl] Prevent [[SetPrototypeOf]] on all globals (#209) (Thursday, 3 November)
• Re: [heycam/webidl] Remove all references to RegExp. (#220) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Prevent [[SetPrototypeOf]] on all globals (#209) (Thursday, 3 November)
• Re: [heycam/webidl] Remove all references to RegExp. (#220) (Thursday, 3 November)
• Re: [heycam/webidl] Remove all references to RegExp. (#220) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [whatwg/streams] Add code coverage reporting to the reference implementation/tests (6ee11ff) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [whatwg/streams] Add code coverage to reference implementation (#208) (Thursday, 3 November)
• Re: [whatwg/streams] Add code coverage reporting the reference implementation/tests (#590) (Thursday, 3 November)
• Re: [heycam/webidl] Union types with colliding enum values (#219) (Thursday, 3 November)
• Re: [heycam/webidl] Union types with colliding enum values (#219) (Thursday, 3 November)
• [heycam/webidl] Union types with colliding enum values (#219) (Wednesday, 2 November)
• Re: [whatwg/streams] Add code coverage reporting the reference implementation/tests (#590) (Wednesday, 2 November)
• Re: [whatwg/streams] test non-function sink.abort (#591) (Wednesday, 2 November)
• Re: [whatwg/streams] test non-function sink.abort (#591) (Wednesday, 2 November)
• Re: [whatwg/streams] Add code coverage reporting the reference implementation/tests (#590) (Wednesday, 2 November)
• Re: [whatwg/streams] Add code coverage reporting the reference implementation/tests (#590) (Wednesday, 2 November)
• [whatwg/streams] Add code coverage reporting the reference implementation/tests (#590) (Wednesday, 2 November)
• Re: [whatwg/dom] Meta: commit snapshot cleanup (#363) (Wednesday, 2 November)
• Re: [whatwg/streams] explicity operate on underlying source and sink instead of public methods (#321) (Wednesday, 2 November)
• Re: [whatwg/streams] explicity operate on underlying source and sink instead of public methods (#321) (Wednesday, 2 November)
• Re: [whatwg/streams] Implementation of net.Socket (#305) (Wednesday, 2 November)
• Re: [whatwg/streams] should ReadableStreamClose() resolve BYOB reader readIntoRequests? (#455) (Wednesday, 2 November)
• Re: [whatwg/streams] Should ReadableStreamDefaultReader be exposed? (#586) (Wednesday, 2 November)
• Re: [whatwg/streams] eslint fixes and standardize exports style (#579) (Wednesday, 2 November)
• Re: [whatwg/streams] assert invariants in InvokeOrNoop and friends (#584) (Wednesday, 2 November)
• Re: [whatwg/streams] WritableStream: Test no-op releaseLock (#588) (Wednesday, 2 November)
• Re: [whatwg/streams] Editorial: "return undefined." vs. "return" (#587) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] Review Web Authentication spec (#97) (Wednesday, 2 November)
• Re: [whatwg/dom] Set up the architecture for commit/branch snapshots (#350) (Wednesday, 2 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Wednesday, 2 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Wednesday, 2 November)
• Re: [heycam/webidl] Remove support for [Unforgeable]-annotated interfaces (#215) (Tuesday, 1 November)
• [heycam/webidl] Update attribute setter/getters in various ways (#217) (Tuesday, 1 November)
• Re: [whatwg/dom] document.createEvent() supports lots of events that most UAs do not support initializers for (#362) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] MediaStream Recorder (#131) (Tuesday, 1 November)

Dominic Cooney

• [w3c/webcomponents] createElement step 5 is inconsistent with parser-created customized built-in elements (#608) (Tuesday, 15 November)

Dominick Ng

• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Tuesday, 15 November)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Thursday, 3 November)

Dominique Hazael-Massieux

• Re: [w3c/webcomponents] Add implementation links (#588) (Tuesday, 22 November)
• Re: [w3ctag/spec-reviews] Audio Output Device APIs (#132) (Wednesday, 2 November)

EduardoRFS

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)

Eero Häkkinen

• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 25 November)
• Re: [whatwg/fetch] Clarification of Body package data algorithm with bytes, FormData and multipart/form-data MIME type (#392) (Friday, 25 November)
• Re: [whatwg/fetch] Clarification of Body package data algorithm with bytes, FormData and multipart/form-data MIME type (#392) (Friday, 25 November)
• [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 25 November)

Emmanuel Chappat

• [whatwg/fetch] Sharing cookies from one subdomain to the other (#417) (Tuesday, 15 November)

Eric Bidelman

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 5 November)

Eric Elliott

• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Thursday, 17 November)

Fatenbazzi

• [whatwg/xhr] Wordpress.org issue (#103) (Thursday, 24 November)

Francois Marier

• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Wednesday, 30 November)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Tuesday, 29 November)

François Daoust

• [w3c/gamepad] Spec broken because of use of "old school" WebIDL mode (#47) (Wednesday, 30 November)
• [w3ctag/spec-reviews] Remote Playback API (#145) (Wednesday, 9 November)

Gary Kacmarcik

• [w3c/uievents] Example 33 cleanup (#113) (Thursday, 3 November)

geranebaker

• [whatwg/streams] Create Geranebb21 (#615) (Friday, 18 November)

Gijs

• [whatwg/url] Semi-colon (;) should be illegal in URL hostname parsing (#159) (Wednesday, 2 November)

Glenn Adams

• Re: [w3ctag/spec-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Wednesday, 23 November)
• Re: [w3ctag/spec-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Saturday, 19 November)

Gustavo Villa

• [w3c/manifest] Fix typographical error (#525) (Wednesday, 9 November)

Hadley Beeman

• Re: [w3ctag/spec-reviews] Review Web Bluetooth (#139) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] Review Web Bluetooth (#139) (Tuesday, 1 November)

Hayato Ito

• Re: [w3c/webcomponents] [shadow-dom] [spec-bug] in asignedNodes description. (#612) (Monday, 28 November)
• Re: [w3c/webcomponents] [shadow-dom] [spec-bug] in asignedNodes description. (#612) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Add implementation links (#588) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [whatwg/dom] "The assignedSlot attribute’s getter must return..." (#369) (Tuesday, 8 November)
• Re: [w3c/webcomponents] Add an assignedElements() method (#602) (Monday, 7 November)
• Re: [w3c/webcomponents] When to PUBLIC? (#599) (Wednesday, 2 November)

Henri Sivonen

• Re: [whatwg/encoding] Document an implementation buffer trick (#84) (Monday, 28 November)
• Re: [whatwg/encoding] Inform readers about the structure of the sparsity of index-euc-kr (#78) (Thursday, 17 November)
• Re: [whatwg/encoding] Inform readers about the structure of the sparsity of index-euc-kr (#78) (Thursday, 17 November)

Hux 黄玄

• Re: [w3c/ServiceWorker] Service worker Failed to load resource: net::ERR_UNSAFE_REDIRECT (#1001) (Friday, 4 November)

Ian Kilpatrick

• Re: [w3ctag/spec-reviews] Custom Paint API to CR (#140) (Tuesday, 1 November)

Ilya Grigorik

• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Wednesday, 30 November)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Tuesday, 29 November)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Monday, 28 November)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Monday, 28 November)
• [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Wednesday, 23 November)

isonmad

• [whatwg/streams] rework recording-streams helper (#609) (Thursday, 10 November)
• Re: [whatwg/streams] skip WPT dir if not present (#608) (Thursday, 10 November)
• [whatwg/streams] skip WPT dir if not present (#608) (Thursday, 10 November)
• Re: [whatwg/streams] port piping tests to WPT (#603) (Thursday, 10 November)
• Re: [whatwg/streams] port piping tests to WPT (#603) (Thursday, 10 November)
• Re: [whatwg/streams] port piping tests to WPT (#603) (Thursday, 10 November)
• Re: [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Thursday, 10 November)
• Re: [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Thursday, 10 November)
• Re: [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Monday, 7 November)
• Re: [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Monday, 7 November)
• Re: [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Monday, 7 November)
• Re: [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Monday, 7 November)
• [whatwg/streams] WPT-ify most of the remaining tape tests (#604) (Sunday, 6 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Saturday, 5 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Saturday, 5 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Saturday, 5 November)
• [whatwg/streams] port piping tests to WPT (#603) (Saturday, 5 November)
• [whatwg/streams] delete dead code (#602) (Saturday, 5 November)
• [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Saturday, 5 November)
• [whatwg/streams] move TransformStream strategies to second argument (#600) (Saturday, 5 November)
• Re: [whatwg/streams] WPT-ify some tests (#597) (Saturday, 5 November)
• Re: [whatwg/streams] WPT-ify some tests (#597) (Friday, 4 November)
• Re: [whatwg/streams] WPT-ify some tests (#597) (Friday, 4 November)
• Re: [whatwg/streams] WPT-ify some tests (#597) (Friday, 4 November)
• Re: [whatwg/streams] WPT-ify some tests (#597) (Friday, 4 November)
• Re: [whatwg/streams] use abstract ops in TransformStream implementation (#598) (Friday, 4 November)
• [whatwg/streams] use abstract ops in TransformStream implementation (#598) (Friday, 4 November)
• [whatwg/streams] WPT-ify some tests (#597) (Friday, 4 November)
• [whatwg/streams] fix error description (#596) (Friday, 4 November)
• Re: [whatwg/streams] test non-function strategy.size (#594) (Friday, 4 November)
• Re: [whatwg/streams] test non-function strategy.size (#594) (Friday, 4 November)
• Re: [whatwg/streams] update travis config (#595) (Thursday, 3 November)
• [whatwg/streams] update travis config (#595) (Thursday, 3 November)
• Re: [whatwg/streams] Run ReadableStream tests against ReadableByteStream (#217) (Thursday, 3 November)
• Re: [whatwg/streams] Add code coverage reporting to the reference implementation/tests (6ee11ff) (Thursday, 3 November)
• Re: [whatwg/streams] test non-function strategy.size (#594) (Thursday, 3 November)
• Re: [whatwg/streams] test non-function strategy.size (#594) (Thursday, 3 November)
• Re: [whatwg/streams] test non-function strategy.size (#594) (Thursday, 3 November)
• [whatwg/streams] test non-function strategy.size (#594) (Thursday, 3 November)
• [whatwg/streams] remove dead code (#593) (Thursday, 3 November)
• [whatwg/streams] sync spec and implementation of autoAllocateChunkSize (#592) (Thursday, 3 November)
• Re: [whatwg/streams] test non-function sink.abort (#591) (Thursday, 3 November)
• Re: [whatwg/streams] test non-function sink.abort (#591) (Wednesday, 2 November)
• [whatwg/streams] test non-function sink.abort (#591) (Wednesday, 2 November)
• Re: [whatwg/streams] Add code coverage reporting the reference implementation/tests (#590) (Wednesday, 2 November)
• Re: [whatwg/streams] Add code coverage reporting the reference implementation/tests (#590) (Wednesday, 2 November)
• [whatwg/streams] Why are [[writeRequests]] and [[queue]] separate? (#589) (Wednesday, 2 November)
• Re: [whatwg/streams] eslint fixes and standardize exports style (#579) (Wednesday, 2 November)
• Re: [whatwg/streams] eslint fixes and standardize exports style (#579) (Wednesday, 2 November)
• Re: [whatwg/streams] eslint fixes and standardize exports style (#579) (Tuesday, 1 November)
• Re: [whatwg/streams] eslint fixes and standardize exports style (#579) (Tuesday, 1 November)
• Re: [whatwg/streams] assert invariants in InvokeOrNoop and friends (#584) (Tuesday, 1 November)

Ivan Herman

• Re: [whatwg/fetch] "bar.com" in the example (#414) (Thursday, 10 November)
• Re: [whatwg/fetch] Update fetch.bs: bar.com should be bar.invalid (#415) (Thursday, 10 November)
• Re: [whatwg/fetch] "bar.com" in the example (#414) (Thursday, 10 November)
• [whatwg/fetch] Update fetch.bs (#415) (Thursday, 10 November)
• [whatwg/fetch] "rom bar.com" (#414) (Thursday, 10 November)

Jake Archibald

• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Tuesday, 29 November)
• [w3c/ServiceWorker] serviceworker.skipWaiting (#1016) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] The promises returned by skipWaiting() should have more consistent activation-waiting behavior and not call Activate() multiple times (#1015) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Thursday, 24 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Thursday, 24 November)
• Re: [whatwg/fetch] Export various things for service worker (#420) (Thursday, 24 November)
• Re: [whatwg/fetch] Emptying a readable stream should be for readablestream (#421) (Thursday, 24 November)
• Re: [whatwg/fetch] Emptying a readable stream should be for readablestream (#421) (Thursday, 24 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Thursday, 24 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Thursday, 24 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Thursday, 24 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Thursday, 24 November)
• [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Thursday, 24 November)
• Re: [whatwg/fetch] Export various things for service worker (#420) (Thursday, 24 November)
• [whatwg/fetch] Emptying a readable stream should be for readablestream (#421) (Thursday, 24 November)
• Re: [whatwg/fetch] Export response's associated response (#420) (Thursday, 24 November)
• Re: [whatwg/fetch] Export response's associated response (#420) (Thursday, 24 November)
• [whatwg/fetch] Export response's associated response (#420) (Thursday, 24 November)
• Re: [w3c/ServiceWorker] ServiceWorker lifetime and respondWith() with a user-constructed ReadableStream (#882) (Thursday, 24 November)
• Re: [w3c/ServiceWorker] Lots of bikeshed usage issues (#965) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Lots of bikeshed usage issues (#965) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Monday, 21 November)
• Re: [w3c/push-api] event.waitUntil(registration.subscribe()) would cause a deadlock (#221) (Friday, 18 November)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Friday, 18 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] Add more Soft Update on functional events (#1006) (Thursday, 17 November)
• Re: [heycam/webidl] add a type to represent the undefined value (#60) (Monday, 7 November)
• Re: [whatwg/streams] Should ReadableStreamDefaultReader be exposed? (#586) (Wednesday, 2 November)
• [whatwg/streams] Should ReadableStreamDefaultReader be exposed? (#586) (Wednesday, 2 November)

James Dalessio

• Re: [w3c/ServiceWorker] Edge case for use of client.frameType (#1007) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Edge case for use of client.frameType (#1007) (Tuesday, 22 November)
• [w3c/ServiceWorker] Edge case for use of client.frameType (#1007) (Saturday, 19 November)

Jeff Burtoft

• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Thursday, 17 November)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Thursday, 3 November)

Jimmy Karl Roland Wärting

• Re: [w3c/FileAPI] Remove FileList (Migrate to | typedef FileList FrozenArray<File>; | (#19) (Wednesday, 16 November)

jmuransky

• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Tuesday, 8 November)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Monday, 7 November)

Johannes Wilm

• Re: [w3c/editing] contentEditable: clarification of selection and typing behavior (#156) (Wednesday, 30 November)
• Re: [w3c/editing] contentEditable: clarification of selection and typing behavior (#156) (Wednesday, 30 November)
• Re: [w3c/editing] contentEditable: clarification of selection and typing behavior (#156) (Wednesday, 30 November)
• Re: [w3c/editing] contentEditable: clarification of selection and typing behavior (#156) (Wednesday, 30 November)
• Re: [w3c/editing] execCommand: Fix HTML spec URLs (#155) (Monday, 28 November)
• Re: [w3c/editing] Broken link in execCommand (#154) (Monday, 28 November)
• Re: [w3c/editing] <div> in <dl> (#153) (Wednesday, 2 November)
• Re: [w3c/editing] <div> in <dl> (#153) (Wednesday, 2 November)
• Re: [w3c/editing] <div> in <dl> (#153) (Wednesday, 2 November)
• Re: [w3c/editing] <div> in <dl> (#153) (Wednesday, 2 November)

John Mellor

• Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Monday, 28 November)

John Reilly

• Re: [w3c/ServiceWorker] service-worker.d.ts.... (#576) (Tuesday, 15 November)

Joseph Orbegoso Pea

• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Wednesday, 30 November)
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Tuesday, 29 November)
• [w3c/webcomponents] [spec-bug] Jarbled text. (#612) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 28 November)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Monday, 28 November)
• [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Sunday, 27 November)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Sunday, 27 November)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Friday, 25 November)
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Friday, 25 November)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Friday, 25 November)
• Re: [w3c/webcomponents] Define the timing when distribution happens (#73) (Friday, 25 November)
• Re: [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Wednesday, 23 November)
• Re: [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Wednesday, 23 November)
• [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Wednesday, 23 November)
• Re: [w3c/webcomponents] customElements.define should throw on registration of definitions that shadow built-in properties / methods. (#583) (Wednesday, 23 November)
• Re: [w3c/webcomponents] Copying global `<style>` textContent into ShadowDOM roots is not ideal. (#609) (Saturday, 19 November)
• Re: [w3c/webcomponents] Best way to distribute global styles into shadow root? (#609) (Saturday, 19 November)
• Re: [w3c/webcomponents] Best way to distribute global styles into shadow root? (#609) (Saturday, 19 November)
• [w3c/webcomponents] Best way to distribute global styles into shadow root? (#609) (Saturday, 19 November)
• Re: [w3c/webcomponents] [idea] Not having <slot> element get in the way of structure. (#589) (Monday, 14 November)
• Re: [w3c/webcomponents] [idea] Not having <slot> element get in the way of structure. (#589) (Sunday, 13 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 9 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 5 November)
• Re: [w3c/webcomponents] [BUG?] Setting visibility:hidden on a Custom Element causes attachedCallback not to be executed. (#601) (Thursday, 3 November)
• Re: [w3c/webcomponents] [BUG?] Setting visibility:hidden on a Custom Element causes attachedCallback not to be executed. (#601) (Thursday, 3 November)
• [w3c/webcomponents] [BUG?] Setting visibility:hidden on a Custom Element causes callbacks not to be executed (not upgraded?). (#601) (Thursday, 3 November)

Josh

• [w3c/IndexedDB] Add support for URL as one of the basic types like Date (#108) (Wednesday, 2 November)
• Re: [w3c/IndexedDB] Feature Request: Allow batch adding records (from an Array) (#69) (Wednesday, 2 November)
• Re: [w3c/IndexedDB] Feature Request: Allow batch adding records (from an Array) (#69) (Wednesday, 2 November)

Joshua Bell

• Re: [whatwg/storage] Error handling in estimate() (#38) (Wednesday, 30 November)
• Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Friday, 18 November)
• Re: [w3c/IndexedDB] Allow delete() on index (#68) (Friday, 18 November)
• Re: [w3c/IndexedDB] Can the indexedDB attribute have [SameObject] (#116) (Thursday, 17 November)
• Re: [w3c/IndexedDB] Add [SameObject] annotation to global indexedDB (#117) (Thursday, 17 November)
• [w3c/IndexedDB] DOMStringList should have [Exposed=(Window,Worker)] (#118) (Thursday, 17 November)
• Re: [w3c/IndexedDB] Add [SameObject] annotation to global indexedDB (#117) (Thursday, 17 November)
• Re: [w3c/IndexedDB] Add [SameObject] annotation to global indexedDB (#117) (Thursday, 17 November)
• Re: [w3c/IndexedDB] Can the indexedDB attribute have [SameObject] (#116) (Thursday, 17 November)
• [w3c/IndexedDB] Add [SameObject] annotation to global indexedDB (#117) (Thursday, 17 November)
• Re: [whatwg/encoding] Inform readers about the structure of the sparsity of index-euc-kr (#78) (Thursday, 17 November)
• Re: [w3c/IndexedDB] Tiny grammar fix (#114) (Wednesday, 16 November)
• Re: [w3c/IndexedDB] Tiny grammar fix (#114) (Wednesday, 16 November)
• Re: [whatwg/encoding] Consider adding "replacement" as a label for the replacement encoding (#70) (Wednesday, 16 November)
• Re: [whatwg/encoding] Note >8835 pointers in index jis0208 cannot be reached (#83) (Wednesday, 16 November)
• Re: [w3c/IndexedDB] Problem with test IndexedDB/idbobjectstore-rename-store.html (#113) (Friday, 11 November)
• Re: [whatwg/encoding] Bikeshed conversion (#79) (Thursday, 10 November)
• Re: [whatwg/encoding] Bikeshed conversion (#79) (Thursday, 10 November)
• Re: [w3c/IndexedDB] Clear object store handle's index set when deleted. Resolves #109 (#111) (Saturday, 5 November)
• Re: [w3c/IndexedDB] Behavior tested by transaction-abort-multiple-metadata-revert.html is not obviously specified anywhere (#109) (Saturday, 5 November)
• Re: [w3c/IndexedDB] Clear object store handle's index set when deleted. Resolves #109 (#111) (Friday, 4 November)
• [w3c/IndexedDB] Clear object store handle's index set when deleted. Resolves #109 (#111) (Friday, 4 November)
• [w3c/IndexedDB] Add non-normative docs for APIs (#110) (Friday, 4 November)
• Re: [w3c/IndexedDB] Behavior tested by transaction-abort-multiple-metadata-revert.html is not obviously specified anywhere (#109) (Friday, 4 November)
• Re: [w3c/IndexedDB] Behavior tested by transaction-abort-multiple-metadata-revert.html is not obviously specified anywhere (#109) (Friday, 4 November)
• Re: [w3c/IndexedDB] Feature Request: Allow batch adding records (from an Array) (#69) (Wednesday, 2 November)
• Re: [w3c/IndexedDB] Feature Request: Allow batch adding records (from an Array) (#69) (Wednesday, 2 November)

JR Conlin

• Re: [w3c/push-api] Add a messageHandlingError event (#214) (Saturday, 5 November)

Jungkee Song

• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] The promises returned by skipWaiting() should have more consistent activation-waiting behavior and not call Activate() multiple times (#1015) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] The promises returned by skipWaiting() should have more consistent activation-waiting behavior and not call Activate() multiple times (#1015) (Tuesday, 29 November)
• Re: [w3c/ServiceWorker] The promises returned by skipWaiting() should have more consistent activation-waiting behavior and not call Activate() multiple times (#1015) (Monday, 28 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Friday, 25 November)
• Re: [w3c/ServiceWorker] ServiceWorker lifetime and respondWith() with a user-constructed ReadableStream (#882) (Friday, 25 November)
• Re: [w3c/ServiceWorker] Fix arguments to "fetch a classic worker script" (#1012) (Thursday, 24 November)
• Re: [w3c/ServiceWorker] Fix arguments to "fetch a classic worker script" (#1012) (Thursday, 24 November)
• [w3c/ServiceWorker] Sort out settings object for service worker module scripts (#1013) (Thursday, 24 November)
• Re: [w3c/ServiceWorker] Fix arguments to "fetch a classic worker script" (#1012) (Thursday, 24 November)
• Re: [w3c/ServiceWorker] Does accessing ExtendableEvent's extend lifetime promises race? (#931) (Wednesday, 23 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Wednesday, 23 November)
• Re: [w3c/ServiceWorker] Fix arguments to "fetch a classic worker script" (#1012) (Wednesday, 23 November)
• Re: [w3c/ServiceWorker] Fix arguments to "fetch a classic worker script" (#1012) (Wednesday, 23 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Wednesday, 23 November)
• Re: [w3c/ServiceWorker] .ready promise should be resolved after updating registration.state properties (#1011) (Wednesday, 23 November)
• Re: [w3c/ServiceWorker] Lots of bikeshed usage issues (#965) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• [w3c/ServiceWorker] Introduce Extend Service Worker Lifetime algorithm (#1010) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Editorial: export Handle Functional Event (#1008) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] consider exposing a type attribute on Client (#1005) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Edge case for use of client.frameType (#1007) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] consider exposing a type attribute on Client (#1005) (Friday, 18 November)
• Re: [w3c/ServiceWorker] Add more Soft Update on functional events (#1006) (Friday, 18 November)
• Re: [w3c/ServiceWorker] Add more Soft Update on functional events (#1006) (Friday, 18 November)
• Re: [w3c/ServiceWorker] should UA check for updates on navigate when there is no fetch event? (#905) (Friday, 18 November)
• [w3c/ServiceWorker] Add more Soft Update on functional events (#1006) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] Property on fetchEvent to indicate the target client (#874) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] Property on fetchEvent to indicate the target client (#874) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] serviceworker for iframes with srcdoc (#765) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] serviceworker for iframes with srcdoc (#765) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] serviceworker for iframes with srcdoc (#765) (Wednesday, 16 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Friday, 11 November)
• Re: [w3c/ServiceWorker] ServiceWorkerMessageEvent isn't consistent with MessageEvent (#989) (Friday, 11 November)
• Re: [w3c/ServiceWorker] Use Extended MessageEvent (6c68bd8) (Friday, 11 November)
• Re: [w3c/ServiceWorker] Use Extended MessageEvent (6c68bd8) (Friday, 11 November)
• Re: [w3c/ServiceWorker] Use Extended MessageEvent (6c68bd8) (Friday, 11 November)
• Re: [w3c/ServiceWorker] ServiceWorkerMessageEvent isn't consistent with MessageEvent (#989) (Friday, 11 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Friday, 11 November)
• Re: [w3c/ServiceWorker] Use Extended MessageEvent (6c68bd8) (Friday, 11 November)
• Re: [w3c/ServiceWorker] Use Extended MessageEvent (6c68bd8) (Friday, 11 November)
• Re: [w3c/ServiceWorker] ServiceWorkerMessageEvent isn't consistent with MessageEvent (#989) (Friday, 11 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Friday, 11 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Friday, 11 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Thursday, 10 November)
• Re: [w3c/ServiceWorker] Behavior of the onfetch setter regarding no-fetch service workers (#1004) (Thursday, 10 November)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Thursday, 10 November)
• Re: [w3c/ServiceWorker] Spec client.reserved (#1003) (Wednesday, 9 November)
• [w3c/ServiceWorker] Spec client.reserved (#1003) (Wednesday, 9 November)
• Re: [w3c/ServiceWorker] Editorial: more link-defaults and anchors cleanup (#1002) (Monday, 7 November)
• Re: [w3c/ServiceWorker] spec exactly how to order non-window Client objects (#887) (Monday, 7 November)
• Re: [w3c/ServiceWorker] Editorial: more link-defaults and anchors cleanup (#1002) (Monday, 7 November)
• Re: [w3c/ServiceWorker] Editorial: more link-defaults and anchors cleanup (#1002) (Monday, 7 November)
• Re: [w3c/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Friday, 4 November)
• Re: [w3c/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Friday, 4 November)
• Re: [w3c/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Friday, 4 November)
• Re: [w3c/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Friday, 4 November)
• Re: [w3c/ServiceWorker] Should the active worker move to environment settings object? (#811) (Friday, 4 November)
• Re: [w3c/ServiceWorker] Should the active worker move to environment settings object? (#811) (Friday, 4 November)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Friday, 4 November)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Friday, 4 November)
• Re: [w3c/ServiceWorker] Define client.reserved (d88e979) (Thursday, 3 November)
• Re: [w3c/ServiceWorker] Export dfn for HTML and DOM (66a4fd9) (Wednesday, 2 November)
• Re: [w3c/ServiceWorker] Export dfn for HTML and DOM (66a4fd9) (Wednesday, 2 November)
• Re: [w3c/ServiceWorker] Editorial: export terms for Fetch (#999) (Wednesday, 2 November)
• Re: [w3c/ServiceWorker] Editorial: export terms for Fetch (#999) (Tuesday, 1 November)
• Re: [w3c/ServiceWorker] Editorial: export terms for Fetch (#999) (Tuesday, 1 November)

Justin Fagnani

• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Thursday, 10 November)

Justin Novosad

• Re: [w3ctag/spec-reviews] ImageBitmapRenderingContext (part of offscreen canvas) (#141) (Monday, 14 November)

Katelyn Gadd

• Re: [w3c/gamepad] UA applied mapping cannot be escaped (#1) (Wednesday, 16 November)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Monday, 28 November)
• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Friday, 18 November)
• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Friday, 18 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#524) (Tuesday, 8 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#524) (Tuesday, 8 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#524) (Tuesday, 8 November)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 2 November)

Kit Cambridge

• Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Monday, 28 November)
• Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Monday, 28 November)
• Re: [w3c/push-api] event.waitUntil(registration.subscribe()) would cause a deadlock (#221) (Monday, 14 November)

Kyle Huey

• Re: [whatwg/dom] document.createEvent() supports lots of events that most UAs do not support initializers for (#362) (Tuesday, 1 November)

L. David Baron

• Re: [w3ctag/spec-reviews] PaymentRequest.canMakeActivePayment() (#146) (Wednesday, 23 November)
• Re: [w3ctag/spec-reviews] IFrame support in web payments (#147) (Tuesday, 22 November)
• Re: [w3ctag/spec-reviews] PaymentRequest.canMakeActivePayment() (#146) (Friday, 18 November)
• Re: [w3ctag/spec-reviews] PaymentRequest.canMakeActivePayment() (#146) (Friday, 18 November)
• Re: [whatwg/dom] Add a section on defining a new event (#364) (Thursday, 10 November)
• Re: [w3ctag/spec-reviews] ImageBitmapRenderingContext (part of offscreen canvas) (#141) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] TV-Specific Web Subsetting (#105) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] Review Web Authentication spec (#97) (Wednesday, 2 November)

littledan

• Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Tuesday, 8 November)
• Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226) (Monday, 7 November)
• Re: [heycam/webidl] Prevent [[SetPrototypeOf]] on all globals (#209) (Tuesday, 1 November)

Lukasz Olejnik

• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Tuesday, 1 November)

Léonie Watson

• Re: [w3c/WebPlatformWG] Update some links (#81) (Wednesday, 30 November)
• Re: [w3c/WebPlatformWG] Update some links (#81) (Wednesday, 30 November)
• Re: [w3c/pointerlock] CFC: Publish FPWD of Pointer Lock 2.0 (closes 14th Nov 2016) (#12) (Wednesday, 16 November)
• [w3c/pointerlock] CFC: Publish FPWD of Pointer Lock 2.0 (closes 14th Nov 2016) (#12) (Monday, 7 November)
• Re: [w3c/pointerlock] CFC: Publish FPWD of Pointer Lock 2.0 (closes 14th Nov 2016) (#11) (Monday, 7 November)
• Re: [w3c/pointerlock] CFC: Publish FPWD of Pointer Lock 2.0 (closes 14th Nov 2016) (#11) (Monday, 7 November)
• Re: [w3c/pointerlock] CFC: Publish FPWD of Pointer Lock 2.0 (closes 15th Nov 2016) (#11) (Tuesday, 1 November)
• Re: [w3c/pointerlock] CFC: Publish FPWD of Pointer Lock 2.0 (closes 15th Nov 2016) (#11) (Tuesday, 1 November)
• [w3c/pointerlock] CFC: Publish FPWD of Pointer Lock 2.0 (closes 15th Nov 2016) (#11) (Tuesday, 1 November)

Marcos Cáceres

• Re: [w3c/manifest] feat: add more complete explainer (#528) (Wednesday, 30 November)
• Re: [w3c/manifest] feat: add more complete explainer (#528) (Wednesday, 30 November)
• [w3c/screen-orientation] Test suite (#95) (Tuesday, 29 November)
• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Monday, 28 November)
• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Monday, 28 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Wednesday, 23 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Wednesday, 23 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Tuesday, 22 November)
• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Monday, 21 November)
• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Monday, 21 November)
• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Friday, 18 November)
• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Friday, 18 November)
• [w3c/manifest] feat: Add splashscreens member + purpose (closes #501) (#530) (Friday, 18 November)
• Re: [w3c/manifest] feat: add more complete explainer (#528) (Thursday, 17 November)
• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Thursday, 17 November)
• Re: [w3c/manifest] Add info push notifications to extensions registry (#529) (Wednesday, 16 November)
• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Tuesday, 15 November)
• Re: [w3c/manifest] Proposal: Add Optional Member for IARC Rating (#523) (Tuesday, 15 November)
• Re: [w3c/manifest] Update references to W3C if available (#526) (Monday, 14 November)
• Re: [w3c/manifest] feat: add more complete explainer (#528) (Monday, 14 November)
• [w3c/manifest] feat: add more complete explainer (#528) (Monday, 14 November)
• Re: [w3c/manifest] [Explainer] Add simple example with name and icon (#527) (Monday, 14 November)
• Re: [w3c/manifest] [Explainer] Add simple example with name and icon (#527) (Monday, 14 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Friday, 11 November)
• Re: [w3c/manifest] Update references to W3C if available (#526) (Friday, 11 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Thursday, 10 November)
• Re: [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• Re: [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Thursday, 10 November)
• Re: [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• Re: [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• Re: [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• Re: [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• [whatwg/dom] Clarification on construction and creation of events (#372) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Thursday, 10 November)
• Re: [w3c/manifest] Fix typographical error (#525) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] feat: add AppBannerPromptOutcome enum (#519) (Tuesday, 8 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 8 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 8 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 8 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 8 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 8 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 8 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#524) (Tuesday, 8 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 8 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 8 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#524) (Tuesday, 8 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#524) (Tuesday, 8 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#524) (Tuesday, 8 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#524) (Tuesday, 8 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#524) (Tuesday, 8 November)
• [w3c/manifest] feat(installation): define when/how to fire BIP (#524) (Tuesday, 8 November)
• Re: [w3c/screen-orientation] Event firing needs fixes (#93) (Tuesday, 8 November)
• Re: [w3c/manifest] feat: add AppBannerPromptOutcome enum (#519) (Tuesday, 8 November)
• Re: [w3c/manifest] Proposal: Add Optional Member for IARC Rating (#523) (Tuesday, 8 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#522) (Tuesday, 8 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#522) (Tuesday, 8 November)
• Re: [w3c/manifest] fix (index): fix 'covert' typos (#521) (Tuesday, 8 November)
• Re: [w3c/manifest] fix (index): fix 'covert' typos (#521) (Tuesday, 8 November)
• [w3c/manifest] feat(installation): define when/how to fire BIP (#522) (Tuesday, 8 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Monday, 7 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Monday, 7 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Monday, 7 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Monday, 7 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Monday, 7 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Monday, 7 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Monday, 7 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Monday, 7 November)
• [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Monday, 7 November)
• Re: [w3c/manifest] feat: add AppBannerPromptOutcome enum (#519) (Monday, 7 November)
• Re: [w3c/manifest] feat: add AppBannerPromptOutcome enum (#519) (Monday, 7 November)
• Re: [w3c/manifest] feat: define application life-cycle task source (#518) (Monday, 7 November)
• Re: [w3c/manifest] feat: define application life-cycle task source (#518) (Monday, 7 November)
• Re: [w3c/manifest] feat(window): add window.onbeforeinstallprompt (#517) (Monday, 7 November)
• Re: [w3c/manifest] feat(window): add window.onbeforeinstallprompt (#517) (Monday, 7 November)
• [w3c/manifest] feat: add AppBannerPromptOutcome enum (#519) (Monday, 7 November)
• [w3c/manifest] feat: define application life-cycle task source (#518) (Monday, 7 November)
• [w3c/manifest] feat(window): add window.onbeforeinstallprompt (#517) (Monday, 7 November)
• Re: [w3c/manifest] WIP: beforeinstallprompt (#506) (Monday, 7 November)
• Re: [w3c/manifest] WIP: beforeinstallprompt (#506) (Monday, 7 November)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Friday, 4 November)
• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Thursday, 3 November)
• Re: [w3c/manifest] When purpose is invalid, return set with "any" instead of undefined. (#515) (Thursday, 3 November)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Thursday, 3 November)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 3 November)
• Re: [w3c/manifest] Bikeshedding: should 'purpose' be named 'kind'? (#509) (Thursday, 3 November)
• Re: [w3c/manifest] Parsing image's purpose is missing (#511) (Thursday, 3 November)
• Re: [w3c/manifest] Processing the purpose member should return the same value in both error conditions (#513) (Thursday, 3 November)
• Re: [w3c/manifest] Parsing image purpose. (#516) (Thursday, 3 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Wednesday, 2 November)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Wednesday, 2 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Wednesday, 2 November)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Wednesday, 2 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Wednesday, 2 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Wednesday, 2 November)

Marijn Kruisselbrink

• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Tuesday, 29 November)
• Re: [w3c/FileAPI] Fix typo and remove some extraneous whitespace (#52) (Wednesday, 23 November)
• Re: [w3c/ServiceWorker] consider exposing a type attribute on Client (#1005) (Friday, 18 November)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] Add more Soft Update on functional events (#1006) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] serviceworker for iframes with srcdoc (#765) (Wednesday, 16 November)
• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Tuesday, 8 November)
• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Tuesday, 8 November)

Mark Nottingham

• Re: [whatwg/fetch] Does terminating a fetch before headers come back reject the promise? (#416) (Monday, 21 November)

Martin Thomson

• Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Tuesday, 29 November)
• Re: [w3c/push-api] Switching to contiguous webidl (#229) (Tuesday, 29 November)
• [w3c/push-api] Switching to contiguous webidl (#229) (Tuesday, 29 November)
• Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Sunday, 27 November)
• Re: [w3c/push-api] Allow passing a base64url-encoded value to `applicationServerKey` (#227) (Sunday, 27 November)
• Re: [w3c/push-api] Allow passing a base64url-encoded value to `applicationServerKey` (#227) (Sunday, 27 November)
• [w3c/push-api] Ergonomics of VAPID key (#226) (Thursday, 24 November)
• [w3c/push-api] Edit the summary on the repo (#225) (Thursday, 24 November)
• Re: [w3c/push-api] Clarify encryption key lifetime and intention (#224) (Friday, 18 November)
• Re: [w3c/push-api] Clarify encryption key lifetime and intention (#224) (Friday, 18 November)
• Re: [w3c/push-api] Some things about the PushEncryptionKeys p256dh and auth are not clear enough (#212) (Friday, 18 November)
• Re: [w3c/push-api] Remove references to the soft update algorithm (#223) (Wednesday, 16 November)
• Re: [w3c/push-api] Remove references to Soft Update (#215) (Wednesday, 16 November)
• Re: [w3c/push-api] Remove references to the soft update algorithm (#223) (Wednesday, 16 November)
• [w3c/push-api] Update editors (#219) (Monday, 7 November)
• Re: [w3c/push-api] Rewrite introduction to clarify applicability and use cases (#218) (Monday, 7 November)
• Re: [w3c/push-api] Add applicability statement (#179) (Monday, 7 November)
• Re: [w3c/push-api] Rewrite introduction to clarify applicability and use cases (#218) (Monday, 7 November)
• Re: [w3c/push-api] Push API should be allowed without dependency on service worker (#84) (Friday, 4 November)
• Re: [w3c/push-api] Push API should be allowed without dependency on service worker (#84) (Friday, 4 November)
• [w3c/push-api] Rewrite introduction to clarify applicability and use cases (#218) (Thursday, 3 November)
• [w3c/push-api] Update reference to DSS spec (#217) (Thursday, 3 November)
• [w3c/push-api] Please use Contiguous IDL instead (#216) (Thursday, 3 November)
• Re: [w3c/push-api] Add inline notes / todos for large unresolved issues (#62) (Thursday, 3 November)
• Re: [w3c/push-api] Add inline notes / todos for large unresolved issues (#62) (Thursday, 3 November)
• Re: [w3c/push-api] The term webapp seems odd (#77) (Thursday, 3 November)
• Re: [w3c/push-api] Link to definition of secure origin instead of mentioning https only (#79) (Thursday, 3 November)
• Re: [w3c/push-api] Link to definition of secure origin instead of mentioning https only (#79) (Thursday, 3 November)
• Re: [w3c/push-api] Push API should be allowed without dependency on service worker (#84) (Thursday, 3 November)
• Re: [w3c/push-api] Strings or binary or both (#83) (Thursday, 3 November)
• Re: [w3c/push-api] Strings or binary or both (#83) (Thursday, 3 November)
• Re: [w3c/push-api] Discovering relevant service timers (#111) (Thursday, 3 November)
• Re: [w3c/push-api] Discovering relevant service timers (#111) (Thursday, 3 November)
• [w3c/push-api] Remove references to Soft Update (#215) (Thursday, 3 November)
• Re: [w3c/push-api] Push events should Soft Update service worker (#115) (Thursday, 3 November)
• Re: [w3c/push-api] Push events should Soft Update service worker (#115) (Thursday, 3 November)
• Re: [w3c/push-api] Allow UAs to unsubscribe offline "successfully" (#122) (Thursday, 3 November)
• Re: [w3c/push-api] Should receipt_endpoint be expose in PushSubscription of webpush api (#144) (Thursday, 3 November)
• Re: [w3c/push-api] Should receipt_endpoint be expose in PushSubscription of webpush api (#144) (Thursday, 3 November)
• Re: [w3c/push-api] Push event shouldn't be dispatched to an activating worker (#147) (Thursday, 3 November)
• Re: [w3c/push-api] Push event shouldn't be dispatched to an activating worker (#147) (Thursday, 3 November)
• Re: [w3c/push-api] Service worker events (#146) (Thursday, 3 November)
• Re: [w3c/push-api] Service worker events (#146) (Thursday, 3 November)
• Re: [w3c/push-api] Multiple consecutive messages (#168) (Thursday, 3 November)
• Re: [w3c/push-api] Multiple consecutive messages (#168) (Thursday, 3 November)
• Re: [w3c/push-api] Add a messageHandlingError event (#214) (Thursday, 3 November)
• Re: [w3c/push-api] Add a messageHandlingError event (#214) (Thursday, 3 November)
• Re: [w3c/push-api] Add a messageHandlingError event (#214) (Wednesday, 2 November)

maryammjd

• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Tuesday, 1 November)

Masayuki Nakano

• [w3c/uievents-key] Maybe odd mapping "KanaMode" to KEYCODE_KANA of Android (#30) (Monday, 21 November)
• Re: [w3c/uievents] WheelEvent.intDelta(X|Y|Z) might be useful for some web apps which cannot scroll its contents smoothly (#114) (Sunday, 13 November)
• [w3c/uievents] WheelEvent.intDelta(X|Y|Z) might be useful for some web apps which cannot scroll its contents smoothly (#114) (Sunday, 13 November)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Tuesday, 22 November)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Sunday, 20 November)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Thursday, 10 November)
• [w3c/push-api] event.waitUntil(registration.subscribe()) would cause a deadlock (#221) (Thursday, 10 November)
• [w3c/ServiceWorker] NavigationPreloadManager.setHeaderValue should reject invalid HTTP header field values (#1000) (Tuesday, 1 November)

Matt Gaunt

• Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Monday, 28 November)

Matt Giuca

• Re: [w3c/manifest] Add installation prompt control flow (#417) (Wednesday, 23 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Wednesday, 23 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Tuesday, 22 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Thursday, 10 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Wednesday, 9 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 8 November)
• Re: [w3c/manifest] feat(installation): define when/how to fire BIP (#524) (Tuesday, 8 November)
• Re: [w3c/manifest] feat: add AppBannerPromptOutcome enum (#519) (Tuesday, 8 November)
• Re: [w3c/manifest] feat: add AppBannerPromptOutcome enum (#519) (Monday, 7 November)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Thursday, 3 November)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Thursday, 3 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Wednesday, 2 November)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Wednesday, 2 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Wednesday, 2 November)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Wednesday, 2 November)
• [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Wednesday, 2 November)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Tuesday, 1 November)

Matthew Phillips

• Re: [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Wednesday, 23 November)
• Re: [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Wednesday, 23 November)
• Re: [w3c/webcomponents] [idea] Not having <slot> element get in the way of structure. (#589) (Sunday, 13 November)
• Re: [w3c/webcomponents] [BUG?] Setting visibility:hidden on a Custom Element causes attachedCallback not to be executed. (#601) (Thursday, 3 November)
• Re: [w3c/webcomponents] When to PUBLIC? (#599) (Wednesday, 2 November)

Melvyn Sopacua

• Re: [whatwg/dom] Consider adding document.parseURL(url) (#356) (Wednesday, 2 November)
• Re: [whatwg/dom] Consider adding document.parseURL(url) (#356) (Wednesday, 2 November)

Michael van Ouwerkerk

• Re: [w3c/push-api] Update editors (#219) (Tuesday, 8 November)
• Re: [w3c/push-api] Add Peter Beverloo as an editor, retire Michael (#220) (Tuesday, 8 November)
• Re: [w3c/push-api] Add Peter Beverloo as an editor, retire Michael (#220) (Tuesday, 8 November)
• Re: [w3c/push-api] Update editors (#219) (Tuesday, 8 November)

Michael[tm] Smith

• Re: [w3ctag/spec-reviews] PaymentRequest.canMakeActivePayment() (#146) (Saturday, 12 November)

Mike West

• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Monday, 28 November)
• Re: [whatwg/fetch] nosniff and images (#395) (Wednesday, 23 November)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Monday, 14 November)
• Re: [whatwg/fetch] Export 'keepalive flag', and tie it to 'request'. (#413) (Wednesday, 9 November)
• Re: [whatwg/fetch] Export 'keepalive flag', and tie it to 'request'. (#413) (Wednesday, 9 November)
• Re: [whatwg/fetch] Export 'keepalive flag', and tie it to 'request'. (#413) (Wednesday, 9 November)
• [whatwg/fetch] Export 'keepalive flag', and tie it to 'request'. (#413) (Tuesday, 8 November)
• Re: [whatwg/fetch] Use auto-linking for CSP3. (#410) (Friday, 4 November)
• [whatwg/fetch] Use auto-linking for CSP3. (#410) (Friday, 4 November)
• Re: [whatwg/fetch] Editorial: remove direct w3c.github.io links (#409) (Friday, 4 November)
• Re: [whatwg/fetch] Editorial: remove direct w3c.github.io links (#409) (Friday, 4 November)

Mounir Lamouri

• Re: [w3c/manifest] Proposal: Add Optional Member for IARC Rating (#523) (Friday, 11 November)
• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Friday, 11 November)
• [w3c/manifest] Parsing image purpose. (#516) (Wednesday, 2 November)
• [w3c/manifest] When purpose is invalid, return set with "any" instead of undefined. (#515) (Wednesday, 2 November)

Ms2ger

• [w3c/DOM-Parsing] Define the origin of the documents returned from DOMParser (#24) (Monday, 28 November)
• [whatwg/dom] cloneNode should probably define the new Document's origin (#378) (Monday, 28 November)
• Re: [heycam/webidl] Remove all references to RegExp. (#220) (Thursday, 3 November)
• Re: [w3c/uievents] Require support or non-support for legacy init*Event (#112) (Tuesday, 1 November)

Nathan Schloss

• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Thursday, 17 November)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Monday, 7 November)

Nicolas Le Gall

• Re: [whatwg/streams] Closing the controller with a pipe (#606) (Wednesday, 9 November)
• Re: [whatwg/streams] Closing the controller with a pipe (#606) (Wednesday, 9 November)
• Re: [whatwg/streams] Closing the controller with a pipe (#606) (Wednesday, 9 November)
• [whatwg/streams] Closing the controller with a pipe (#606) (Wednesday, 9 November)

Nigel Megitt

• Re: [w3ctag/spec-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Saturday, 19 November)
• Re: [w3ctag/spec-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Wednesday, 2 November)

Noah Levitt

• [whatwg/url] handling invalid octal ip address (#164) (Monday, 7 November)
• Re: [whatwg/url] percent-encoding rules don't match browsers? (#162) (Friday, 4 November)
• [whatwg/url] percent-encoding rules don't match browsers? (#162) (Friday, 4 November)
• Re: [whatwg/url] path /. (#161) (Friday, 4 November)
• [whatwg/url] path /. (#161) (Friday, 4 November)

noopole

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)

Nour-Eddine ECH-CHEBABY

• Re: [w3c/ServiceWorker] Service worker Failed to load resource: net::ERR_UNSAFE_REDIRECT (#1001) (Sunday, 6 November)
• Re: [w3c/ServiceWorker] Service worker Failed to load resource: net::ERR_UNSAFE_REDIRECT (#1001) (Sunday, 6 November)
• Re: [w3c/ServiceWorker] Service worker Failed to load resource: net::ERR_UNSAFE_REDIRECT (#1001) (Friday, 4 November)
• Re: [w3c/ServiceWorker] Service worker Failed to load resource: net::ERR_UNSAFE_REDIRECT (#1001) (Friday, 4 November)
• Re: [w3c/ServiceWorker] Service worker Failed to load resource: net::ERR_UNSAFE_REDIRECT (#1001) (Friday, 4 November)
• [w3c/ServiceWorker] Service worker Failed to load resource: net::ERR_UNSAFE_REDIRECT (#1001) (Wednesday, 2 November)

Ole Ersoy

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 21 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 21 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 20 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 20 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 20 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 9 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 9 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 9 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 9 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 6 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 5 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 5 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 4 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 4 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 3 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 2 November)

Ole Martin Handeland

• Re: [w3c/ServiceWorker] service-worker.d.ts.... (#576) (Monday, 14 November)

Pascal Reintjens

• Re: [w3c/push-api] Clarify encryption key lifetime and intention (#224) (Thursday, 24 November)
• Re: [w3c/push-api] Some things about the PushEncryptionKeys p256dh and auth are not clear enough (#212) (Tuesday, 1 November)

Patrick H. Lauke

• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Friday, 18 November)

patrick kettner

• Re: [w3c/manifest] Add info push notifications to extensions registry (#529) (Tuesday, 15 November)

Pete Otaqui

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)

Peter Beverloo

• Re: [w3c/push-api] Switching to contiguous webidl (#229) (Tuesday, 29 November)
• Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Monday, 28 November)
• [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Friday, 25 November)
• Re: [w3c/push-api] Allow passing a base64url-encoded value to `applicationServerKey` (#227) (Friday, 25 November)
• [w3c/push-api] Allow passing a base64url-encoded value to `applicationServerKey` (#227) (Friday, 25 November)
• Re: [w3c/push-api] Ergonomics of VAPID key (#226) (Thursday, 24 November)
• Re: [w3c/push-api] Clarify encryption key lifetime and intention (#224) (Friday, 18 November)
• [w3c/push-api] Clarify encryption key lifetime and intention (#224) (Friday, 18 November)
• [w3c/push-api] Remove references to the soft update algorithm (#223) (Wednesday, 16 November)
• Re: [w3c/push-api] event.waitUntil(registration.subscribe()) would cause a deadlock (#221) (Tuesday, 15 November)
• Re: [w3c/push-api] event.waitUntil(registration.subscribe()) would cause a deadlock (#221) (Monday, 14 November)
• [w3c/push-api] Add Peter Beverloo as an editor, retire Michael (#220) (Tuesday, 8 November)
• Re: [w3c/push-api] Update editors (#219) (Monday, 7 November)
• Re: [w3c/push-api] Rewrite introduction to clarify applicability and use cases (#218) (Friday, 4 November)
• Re: [w3c/push-api] Update reference to DSS spec (#217) (Thursday, 3 November)
• Re: [w3c/push-api] Update reference to DSS spec (#217) (Thursday, 3 November)
• Re: [w3c/push-api] update reference to FIPS-186-4 (#210) (Thursday, 3 November)
• Re: [w3c/push-api] Link to a definition of "start up a service worker if it is not running" (#63) (Thursday, 3 November)
• Re: [w3c/push-api] Link to a definition of "start up a service worker if it is not running" (#63) (Thursday, 3 November)

Peter Linss

• Re: [w3ctag/spec-reviews] Review Web Bluetooth (#139) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] Motion path spec (#66) (Tuesday, 1 November)

Peter Occil

• Re: [whatwg/encoding] Fix #17: gb18030 cannot encode U+E5E5 (#25) (Monday, 14 November)

Peter Rushforth

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 30 November)

Philip Jägenstedt

• Re: [whatwg/fullscreen] Decide on wanted behavior for request+exit or exit+request together (#63) (Tuesday, 29 November)
• Re: [whatwg/fullscreen] Decide on wanted behavior for request+exit or exit+request together (#63) (Tuesday, 29 November)
• Re: [whatwg/fullscreen] Decide on wanted behavior for request+exit or exit+request together (#63) (Monday, 28 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Saturday, 26 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] What should happen if an element is moved to another document right after requestFullscreen (#33) (Tuesday, 22 November)
• Re: [whatwg/fullscreen] Decide on wanted behavior for request+exit or exit+request together (#63) (Tuesday, 22 November)
• [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Tuesday, 22 November)
• Re: [whatwg/fullscreen] Decide on wanted behavior for request+exit or exit+request together (#63) (Monday, 21 November)
• Re: [whatwg/fullscreen] Decide on wanted behavior for request+exit or exit+request together (#63) (Monday, 21 November)
• [whatwg/fullscreen] Decide on wanted behavior for request+exit or exit+request together (#63) (Monday, 21 November)
• Re: [whatwg/fullscreen] Editorial: use the Infra Standard (#62) (Monday, 21 November)
• Re: [whatwg/fullscreen] Editorial: use the Infra Standard (#62) (Monday, 21 November)
• Re: [w3c/IndexedDB] Add [SameObject] annotation to global indexedDB (#117) (Thursday, 17 November)
• Re: [w3c/IndexedDB] Add [SameObject] annotation to global indexedDB (#117) (Thursday, 17 November)
• [w3c/IndexedDB] Can the indexedDB attribute have [SameObject] (#116) (Thursday, 17 November)
• Re: [whatwg/dom] document.createEvent() supports lots of events that most UAs do not support initializers for (#362) (Thursday, 17 November)
• [w3c/uievents] Update link to ED to point directly to the spec (#115) (Wednesday, 16 November)
• Re: [w3c/uievents] Update link to ED to point directly to the spec (#115) (Wednesday, 16 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 10 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 10 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 10 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Wednesday, 9 November)
• Re: [whatwg/dom] document.createEvent() supports lots of events that most UAs do not support initializers for (#362) (Wednesday, 9 November)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Wednesday, 9 November)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Wednesday, 9 November)
• Re: [heycam/webidl] Investigate banning nullable enums (#213) (Tuesday, 8 November)
• Re: [heycam/webidl] Investigate banning nullable enums (#213) (Tuesday, 8 November)
• Re: [heycam/webidl] Investigate banning nullable enums (#213) (Tuesday, 8 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Monday, 7 November)
• Re: [w3c/uievents] Require support or non-support for legacy init*Event (#112) (Wednesday, 2 November)
• Re: [w3c/uievents] Require support or non-support for legacy init*Event (#112) (Tuesday, 1 November)

Philippe Le Hegaret

• [w3c/charter-html] Drop High Level User Events (#137) (Monday, 7 November)

Piotrek Koszuliński

• Re: [w3c/editing] contentEditable: clarification of selection and typing behavior (#156) (Wednesday, 30 November)
• Re: [w3c/editing] contentEditable: clarification of selection and typing behavior (#156) (Wednesday, 30 November)
• Re: [w3c/editing] contentEditable: clarification of selection and typing behavior (#156) (Wednesday, 30 November)
• Re: [w3c/editing] contentEditable: clarification of selection and typing behavior (#156) (Wednesday, 30 November)

r12a

• Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Friday, 18 November)
• Re: [whatwg/encoding] Inform readers about the structure of the sparsity of index-euc-kr (#78) (Thursday, 17 November)
• Re: [whatwg/encoding] GBK encoding/decoding support (#56) (Wednesday, 16 November)

Raphael Kubo da Costa

• Re: [w3c/editing] contentEditable: clarification of selection and typing behavior (#156) (Wednesday, 30 November)
• [w3c/editing] contentEditable: clarification of selection and typing behavior (#156) (Monday, 28 November)
• [w3c/editing] execCommand: Fix HTML spec URLs (#155) (Monday, 28 November)

rektide

• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Wednesday, 23 November)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Wednesday, 23 November)
• Re: [w3c/ServiceWorker] Interacting with HTTP/2 push (#215) (Thursday, 3 November)

Rick Byers

• Re: [w3c/touch-events] Adding the fling intervention behavior to TouchEvent's spec (#76) (Wednesday, 30 November)
• [w3c/touch-events] Add defacto (#77) (Wednesday, 30 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 10 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Wednesday, 9 November)
• Re: [w3c/touch-events] Add a default passive algorithm definition for Window, Document and HTMLElement. (#75) (Wednesday, 9 November)
• Re: [w3c/uievents] Require support or non-support for legacy init*Event (#112) (Tuesday, 1 November)

Ricky Miller

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 5 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 4 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 3 November)

Rob Dolin (MSFT)

• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Thursday, 17 November)
• [w3c/manifest] Add info push notifications to extensions registry (#529) (Tuesday, 15 November)
• Re: [w3c/manifest] [Explainer] Add simple example with name and icon (#527) (Monday, 14 November)
• [w3c/manifest] [Explainer] Add simple example with name and icon (#527) (Friday, 11 November)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Thursday, 10 November)
• [w3c/manifest] Update references to W3C if available (#526) (Thursday, 10 November)
• Re: [w3c/manifest] Fix typographical error (#525) (Wednesday, 9 November)
• [w3c/manifest] Proposal: Add Optional Member for IARC Rating (#523) (Tuesday, 8 November)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Thursday, 3 November)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 2 November)
• Re: [w3c/manifest] Bikeshedding: should 'purpose' be named 'kind'? (#509) (Wednesday, 2 November)

Rouslan Solomakhin

• [w3ctag/spec-reviews] IFrame support in web payments (#147) (Tuesday, 22 November)
• Re: [w3ctag/spec-reviews] PaymentRequest.canMakeActivePayment() (#146) (Friday, 18 November)
• Re: [w3ctag/spec-reviews] PaymentRequest.canMakeActivePayment() (#146) (Saturday, 12 November)
• [w3ctag/spec-reviews] PaymentRequest.canMakeActivePayment() (#146) (Friday, 11 November)

Russell Bicknell

• [whatwg/dom] Upstream `delegatesFocus` property of ShadowRootInit from W3C spec. (#367) (Friday, 4 November)

Ryosuke Niwa

• Re: [w3c/webcomponents] Constructing a custom element synchronously drops prefix from its name (#607) (Sunday, 13 November)
• Re: [w3c/webcomponents] Constructing a custom element synchronously drops prefix from its name (#607) (Sunday, 13 November)
• Re: [w3c/webcomponents] Constructing a custom element synchronously drops prefix from its name (#607) (Sunday, 13 November)
• Re: [w3c/webcomponents] Constructing a custom element synchronously drops prefix from its name (#607) (Sunday, 13 November)
• Re: [w3c/webcomponents] Constructing a custom element synchronously drops prefix from its name (#607) (Sunday, 13 November)
• Re: [w3c/webcomponents] Constructing a custom element synchronously drops prefix from its name (#607) (Sunday, 13 November)
• [w3c/webcomponents] Constructing a custom element synchronously drops prefix from its name (#607) (Sunday, 13 November)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Saturday, 12 November)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Friday, 11 November)
• Re: [w3c/webcomponents] Constructor arguments in custom elements (#605) (Friday, 11 November)
• Re: [w3c/webcomponents] Constructor arguments in custom elements (#605) (Friday, 11 November)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Friday, 11 November)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Friday, 11 November)
• Re: [w3c/webcomponents] Constructor arguments in custom elements (#605) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [w3c/selection-api] setBaseAndExtent should clear selection when baseNode or extentNode is null (#72) (Monday, 7 November)
• Re: [w3c/webcomponents] Add an assignedElements() method (#602) (Monday, 7 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 5 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 5 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 4 November)
• Re: [w3c/webcomponents] [BUG?] Setting visibility:hidden on a Custom Element causes attachedCallback not to be executed. (#601) (Thursday, 3 November)

Santiago Ferreira

• [w3c/manifest] fix (index): fix 'covert' typos (#521) (Monday, 7 November)

Scott Graham

• Re: [w3c/gamepad] Arbitrary buffering of API calls is causing issues (#46) (Wednesday, 2 November)

Sean King

• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Tuesday, 22 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 5 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 5 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 5 November)

Sebastian Mayr

• Re: [whatwg/url] IDNA (#53) (Sunday, 20 November)

Sergei Č.

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

Shawn Huang

• Re: [whatwg/storage] Error handling in estimate() (#38) (Wednesday, 30 November)
• [whatwg/storage] Error handling in estimate() (#38) (Tuesday, 29 November)

ShijunS

• Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Tuesday, 29 November)
• Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Tuesday, 29 November)
• Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Monday, 28 November)
• Re: [w3c/push-api] Push API should be allowed without dependency on service worker (#84) (Thursday, 3 November)

Simon Pieters

• Re: [whatwg/dom] Meta: fix markup errors (#377) (Thursday, 24 November)
• Re: [whatwg/dom] Meta: fix markup errors (#377) (Thursday, 24 November)
• [whatwg/dom] Meta: fix markup errors (#377) (Thursday, 24 November)
• Re: [whatwg/fetch] nosniff and images (#395) (Wednesday, 23 November)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Wednesday, 9 November)
• Re: [w3c/editing] <div> in <dl> (#153) (Wednesday, 2 November)
• Re: [w3c/editing] <div> in <dl> (#153) (Wednesday, 2 November)
• Re: [w3c/editing] <div> in <dl> (#153) (Wednesday, 2 November)
• Re: [w3c/editing] <div> in <dl> (#153) (Wednesday, 2 November)
• [w3c/editing] <div> in <dl> (#153) (Tuesday, 1 November)
• Re: [w3c/uievents] Require support or non-support for legacy init*Event (#112) (Tuesday, 1 November)
• Re: [whatwg/url] Stop decoding all %2e's in paths (#156) (Tuesday, 1 November)
• [w3c/uievents] Require support or non-support for legacy init*Event (#112) (Tuesday, 1 November)

sleevi

• Re: [whatwg/url] Change host parser for non-special schemes (#148) (Monday, 7 November)
• Re: [whatwg/url] percent-encoding rules don't match browsers? (#162) (Friday, 4 November)
• Re: [whatwg/url] percent-encoding rules don't match browsers? (#162) (Friday, 4 November)

smaug----

• Re: [w3c/uievents] WheelEvent.intDelta(X|Y|Z) might be useful for some web apps which cannot scroll its contents smoothly (#114) (Sunday, 13 November)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Saturday, 12 November)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 10 November)
• Re: [w3c/uievents] Require support or non-support for legacy init*Event (#112) (Wednesday, 2 November)

sof

• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Monday, 21 November)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Friday, 18 November)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Thursday, 17 November)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Thursday, 17 November)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Thursday, 17 November)
• [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Wednesday, 16 November)

Steve Kobes

• Re: [w3ctag/spec-reviews] Review request for Scroll Anchoring (#142) (Tuesday, 1 November)

Steve Orvell

• [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Friday, 11 November)

stevefaulkner

• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Friday, 18 November)

Steven Vachon

• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Monday, 7 November)
• [whatwg/url] size (or length) for URLSearchParams (#163) (Monday, 7 November)

SummerLW

• Re: [w3c/touch-events] Adding the fling intervention behavior to TouchEvent's spec (#76) (Wednesday, 30 November)
• [w3c/touch-events] Adding the fling intervention behavior to TouchEvent's spec (#76) (Wednesday, 30 November)

T.V.VIGNESH

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 19 November)

Tab Atkins Jr.

• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Wednesday, 30 November)
• Re: [w3c/ServiceWorker] Lots of bikeshed usage issues (#965) (Tuesday, 29 November)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Tuesday, 22 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Monday, 21 November)
• Re: [heycam/webidl] Describing overloaded methods (#241) (Saturday, 19 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Saturday, 19 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Thursday, 17 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Tuesday, 15 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Friday, 11 November)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Friday, 11 November)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Thursday, 10 November)
• Re: [whatwg/encoding] Bikeshed conversion (#79) (Thursday, 10 November)
• Re: [whatwg/encoding] Bikeshed conversion (#79) (Thursday, 10 November)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Wednesday, 9 November)
• Re: [heycam/webidl] #es-to-dictionary and #dictionary-to-es do not have reader-discernable titles (#228) (Wednesday, 9 November)
• Re: [whatwg/xhr] Convert XHR to bikeshed (#97) (Tuesday, 8 November)
• Re: [heycam/webidl] #es-to-dictionary and #dictionary-to-es do not have reader-discernable titles (#228) (Monday, 7 November)
• Re: [heycam/webidl] #es-to-dictionary and #dictionary-to-es do not have reader-discernable titles (#228) (Monday, 7 November)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Monday, 7 November)
• Re: [whatwg/fetch] Use auto-linking for CSP3. (#410) (Friday, 4 November)

Takeshi Yoshino

• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Wednesday, 30 November)
• Re: [whatwg/streams] us.abort() is not called if us.write() fails (#620) (Tuesday, 29 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Tuesday, 29 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Monday, 28 November)
• Re: [whatwg/xhr] Should setting an invalid value to responseType on an XHR in LOADING/DONE state throw? (#102) (Thursday, 24 November)
• Re: [whatwg/xhr] Should setting an invalid value to responseType on an XHR in LOADING/DONE state throw? (#102) (Thursday, 24 November)
• [whatwg/xhr] Should setting an invalid value to responseType on an XHR in LOADING/DONE state throw? (#102) (Thursday, 24 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Thursday, 24 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Thursday, 24 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Thursday, 24 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Thursday, 24 November)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Tuesday, 22 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Tuesday, 22 November)
• Re: [whatwg/streams] TransformStream byte streams (#616) (Tuesday, 22 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Tuesday, 22 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Monday, 21 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Monday, 21 November)
• Re: [whatwg/streams] Aborting a writable stream should not abort writes in progress (#611) (Friday, 18 November)
• Re: [whatwg/streams] Invoking methods should not call .apply() (#613) (Wednesday, 16 November)
• Re: [whatwg/streams] Invoking methods should not call .apply() (#613) (Wednesday, 16 November)
• Re: [whatwg/streams] Invoking methods should not call .apply() (#613) (Wednesday, 16 November)
• Re: [whatwg/streams] Remove trivial non-zero delays in wpts (#605) (Friday, 11 November)
• Re: [whatwg/streams] Remove trivial non-zero delays in wpts (#605) (Wednesday, 9 November)
• Re: [whatwg/streams] Marking promise rejections as handled (#547) (Wednesday, 9 November)
• Re: [whatwg/streams] add "bytes" readableType to TransformStream transformer (#601) (Monday, 7 November)
• Re: [whatwg/streams] Marking promise rejections as handled (#547) (Monday, 7 November)
• Re: [whatwg/streams] Explain why you can release a writer lock while writes are pending (#578) (Friday, 4 November)
• Re: [whatwg/streams] Document difference of lock between writable and readable (#516) (Friday, 4 November)
• Re: [whatwg/streams] Explain why you can release a writer lock while writes are pending (#578) (Friday, 4 November)
• Re: [whatwg/streams] Marking promise rejections as handled (#547) (Friday, 4 November)
• Re: [whatwg/streams] pipeTo(): Rationale for propagating an error happened during error propagation to pipePromise (#558) (Friday, 4 November)
• Re: [whatwg/streams] pipeTo(): Rationale for propagating an error happened during error propagation to pipePromise (#558) (Friday, 4 November)
• Re: [whatwg/streams] Why are [[writeRequests]] and [[queue]] separate? (#589) (Friday, 4 November)
• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) (Wednesday, 2 November)
• Re: [whatwg/streams] "Set totalSize to totalSize + pair.[[size]]." (#582) (Tuesday, 1 November)

Ted Mielczarek

• Re: [w3c/gamepad] Arbitrary buffering of API calls is causing issues (#46) (Thursday, 3 November)

terry10

• Re: [whatwg/xhr] Rq (#100) (Sunday, 13 November)
• Re: [whatwg/xhr] Rq (#100) (Sunday, 13 November)
• [whatwg/xhr] Rq (#100) (Sunday, 13 November)

Timothy Gu

• Re: [w3c/FileAPI] Fix typo and remove some extraneous whitespace (#52) (Wednesday, 23 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Wednesday, 23 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Monday, 14 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Monday, 7 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Monday, 7 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Monday, 7 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Monday, 7 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Monday, 7 November)
• Re: [w3c/FileAPI] Fix typo and remove some extraneous whitespace (#52) (Sunday, 6 November)
• Re: [w3c/FileAPI] Fix typo and remove some extraneous whitespace (#52) (Sunday, 6 November)
• Re: [heycam/webidl] Add missing index increment and use index variable (#224) (Sunday, 6 November)
• Re: [heycam/webidl] Add missing index increment and use index variable (#224) (Sunday, 6 November)
• [heycam/webidl] Add missing index increment and use index variable (#224) (Sunday, 6 November)
• [w3c/FileAPI] Fix typo and remove some extraneous whitespace (#52) (Saturday, 5 November)
• [whatwg/fetch] Use Web IDL's new record type (#412) (Saturday, 5 November)
• [heycam/webidl] Fix typo in sequence type conversion example (#223) (Saturday, 5 November)

tkodw

• Re: [w3c/gamepad] Arbitrary buffering of API calls is causing issues (#46) (Friday, 4 November)
• [w3c/gamepad] Arbitrary buffering of API calls is causing issues (#46) (Wednesday, 2 November)

Tobie Langel

• Re: [heycam/webidl] Meta: export record and sequence (#243) (Tuesday, 22 November)
• Re: [heycam/webidl] Meta: export record and sequence (#243) (Tuesday, 22 November)
• Re: [heycam/webidl] Meta: export record and sequence (#243) (Tuesday, 22 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Monday, 21 November)
• Re: [heycam/webidl] Update attribute setter/getters in various ways (#217) (Saturday, 19 November)
• Re: [heycam/webidl] Editorial: use <var ignore> instead of Ignored Vars. (#238) (Saturday, 19 November)
• Re: [heycam/webidl] Refactor "determine value of length property of named constructors" algorithm (#204) (Saturday, 19 November)
• Re: [heycam/webidl] Should we x-link base concepts to the Infra Standard? (#242) (Thursday, 17 November)
• [heycam/webidl] Should we x-link base concepts to the Infra Standard? (#242) (Thursday, 17 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Wednesday, 16 November)
• Re: [heycam/webidl] No seemingly consistent Shepherd story (#240) (Tuesday, 15 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Fix internal methods that only target platform objects w/ indexed/named props (#202) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Monday, 14 November)
• Re: [whatwg/fetch] Use Web IDL's new record type (#412) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Monday, 14 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Monday, 14 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Monday, 14 November)
• Re: [heycam/webidl] Meta: export record mappings (#239) (Monday, 14 November)
• [heycam/webidl] Editorial: use <var ignore> instead of Ignored Vars. (#238) (Sunday, 13 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Saturday, 12 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Saturday, 12 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Saturday, 12 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Saturday, 12 November)
• Re: [heycam/webidl] [Clamp] and [EnforceRange] reduce the max value long long supports (#237) (Saturday, 12 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Saturday, 12 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] [Clamp] and [EnforceRange] reduce the max value long long supports (#237) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] [Clamp] and [EnforceRange] reduce the max value long long supports (#237) (Friday, 11 November)
• [heycam/webidl] [Clamp] and [EnforceRange] reduce the max value long long supports (#237) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• [heycam/webidl] Refactor integer conversion in ES bindings. (#235) (Friday, 11 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Thursday, 10 November)
• Re: [heycam/webidl] Shepherd: difference between "record" and "record type" (#233) (Thursday, 10 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Wednesday, 9 November)
• Re: [heycam/webidl] #es-to-dictionary and #dictionary-to-es do not have reader-discernable titles (#228) (Wednesday, 9 November)
• Re: [heycam/webidl] Minor fixups to creating an operation Function (#232) (Wednesday, 9 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Tuesday, 8 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Tuesday, 8 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Tuesday, 8 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add instructions on when & where to file issues (#225) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• Re: [heycam/webidl] Add legacy platform objects. (#230) (Tuesday, 8 November)
• [heycam/webidl] Add legacy platform objects. (#230) (Monday, 7 November)
• Re: [heycam/webidl] get-buffer-source-{reference,copy} ought to point to the algorithm (#229) (Monday, 7 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Monday, 7 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Monday, 7 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Monday, 7 November)
• Re: [heycam/webidl] Extend the dfn of object types. (#211) (Monday, 7 November)
• Re: [heycam/webidl] Add missing index increment and use index variable (#224) (Monday, 7 November)
• Re: [heycam/webidl] Add missing index increment and use index variable (#224) (Monday, 7 November)
• Re: [heycam/webidl] Add instructions on when & where to file issues (#225) (Monday, 7 November)
• Re: [heycam/webidl] Add instructions on when & where to file issues (#225) (Monday, 7 November)
• [heycam/webidl] Add instructions on when & where to file issues (#225) (Monday, 7 November)
• Re: [heycam/webidl] Fix internal methods that only target platform objects w/ indexed/named props (#202) (Monday, 7 November)
• Re: [heycam/webidl] Fix internal methods that only target platform objects w/ indexed/named props (#202) (Sunday, 6 November)
• Re: [heycam/webidl] Fix internal methods that only target platform objects w/ indexed/named props (#202) (Sunday, 6 November)
• Re: [heycam/webidl] Fix internal methods that only target platform objects w/ indexed/named props (#202) (Sunday, 6 November)
• Re: [heycam/webidl] Remove all references to RegExp. (#220) (Friday, 4 November)
• Re: [heycam/webidl] Remove all references to RegExp. (#220) (Thursday, 3 November)
• Re: [heycam/webidl] Conversion to sequence<T> need not throw on a RegExp object (#145) (Thursday, 3 November)
• Re: [heycam/webidl] Remove the RegExp type (#148) (Thursday, 3 November)
• [heycam/webidl] Use Type(V) is object instead of if |V| is any kind of object (#222) (Thursday, 3 November)
• Re: [heycam/webidl] does [Constructor] invocation require 'new' or not (generally)? (#62) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Remove all references to RegExp. (#220) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Refactor "determine value of length property of named constructors" algorithm (#204) (Thursday, 3 November)
• [heycam/webidl] Remove all references to RegExp. (#220) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Throw when not calling interfaces as constructors (#205) (Thursday, 3 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Wednesday, 2 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Wednesday, 2 November)
• Re: [heycam/webidl] Remove support for [Unforgeable]-annotated interfaces (#215) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove support for [Unforgeable]-annotated interfaces (#215) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• Re: [heycam/webidl] Bikeshed cleanup. (#218) (Tuesday, 1 November)
• Re: [heycam/webidl] Bikeshed cleanup. (#218) (Tuesday, 1 November)
• [heycam/webidl] Bikeshed cleanup. (#218) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• Re: [heycam/webidl] Remove realm argument of "perform a security check" (#216) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Tuesday, 1 November)

Tomek Wytrębowicz

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 2 November)

Travis Leithead

• Re: [w3ctag/spec-reviews] Privacy Mode (#101) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] Privacy Mode (#101) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] privacy of sensor & other exotic APIs (#129) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] TV Control Feedback (#111) (Wednesday, 2 November)
• Re: [w3ctag/spec-reviews] TV Control Feedback (#111) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] Review Web Bluetooth (#139) (Tuesday, 1 November)
• [w3ctag/spec-reviews] Review OffscreenCanvas (#144) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] WebVR (#106) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] Review request for Scroll Anchoring (#142) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] MediaStream Recorder (#131) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] Audio Output Device APIs (#132) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] Audio Output Device APIs (#132) (Tuesday, 1 November)

Trey Shugart

• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [w3c/webcomponents] Constructor arguments in custom elements (#605) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• [w3c/webcomponents] CustomElementRegistry.prototype.get() and case sensitivity (#604) (Thursday, 10 November)
• Re: [w3c/webcomponents] Add an assignedElements() method (#602) (Sunday, 6 November)
• Re: [w3c/webcomponents] Add an assignedElements() method (#602) (Sunday, 6 November)

Tsuyoshi Horo

• Re: [whatwg/fetch] Add a bit to Opaque Responses to distinguish redirects (#79) (Tuesday, 29 November)

Ukaza Perdana

• Re: [w3c/webcomponents] [imports]: Use cases for HTML Imports (#573) (Tuesday, 22 November)

ukiyocariniaval

• [whatwg/dom] 1 (#379) (Tuesday, 29 November)

Valentin Gosu

• Re: [whatwg/url] Semi-colon (;) should be illegal in URL hostname parsing (#159) (Monday, 7 November)

Victor Costan

• [w3c/IndexedDB] Repository website (#115) (Wednesday, 16 November)
• Re: [w3c/IndexedDB] Tiny grammar fix (#114) (Monday, 14 November)
• [w3c/IndexedDB] Tiny grammar fix (#114) (Monday, 14 November)

Vincent Scheib

• Re: [w3c/pointerlock] CFC: Publish FPWD of Pointer Lock 2.0 (closes 14th Nov 2016) (#12) (Friday, 18 November)
• Re: [w3c/pointerlock] CFC: Publish FPWD of Pointer Lock 2.0 (closes 14th Nov 2016) (#12) (Friday, 18 November)
• Re: [w3ctag/spec-reviews] Review Web Bluetooth (#139) (Tuesday, 1 November)
• Re: [w3ctag/spec-reviews] Review Web Bluetooth (#139) (Tuesday, 1 November)

Vsevolod Shmyroff

• Re: [w3c/FileAPI] Update editors info (#50) (Tuesday, 22 November)
• Re: [w3c/FileAPI] Update editors info (#50) (Tuesday, 22 November)
• Re: [w3c/FileAPI] Remove Jonas Sicking from Editor list (#53) (Tuesday, 22 November)
• Re: [w3c/FileAPI] Remove Jonas Sicking from Editor list (#53) (Wednesday, 16 November)
• [w3c/FileAPI] Remove Jonas Sicking from Editor list (#53) (Tuesday, 15 November)
• Re: [w3c/FileAPI] Update editors info (#50) (Tuesday, 15 November)

wisniewskit

• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Friday, 18 November)

Xiaoqian Wu

• Re: [w3c/editing] execCommand: Fix HTML spec URLs (#155) (Monday, 28 November)
• Re: [w3c/manifest] Fix typographical error (#525) (Thursday, 10 November)

Xidorn Quan

• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Saturday, 26 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Friday, 25 November)
• Re: [whatwg/fullscreen] Decide on wanted behavior for request+exit or exit+request together (#63) (Monday, 21 November)

Xue Fuqiao

• Re: [w3c/WebPlatformWG] Update some links (#81) (Wednesday, 30 November)
• [w3c/WebPlatformWG] Some minor issues in index.html (#82) (Tuesday, 29 November)
• [w3c/WebPlatformWG] Update some links (#81) (Tuesday, 29 November)
• [w3c/editing] Broken link in execCommand (#154) (Wednesday, 23 November)

Yoichi Osato

• Re: [w3c/selection-api] setBaseAndExtent should clear selection when baseNode or extentNode is null (#72) (Monday, 7 November)

youennf

• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Tuesday, 29 November)
• Re: [whatwg/fetch] FormData content-type doesn't match form submission behavior in browsers (#422) (Monday, 28 November)
• Re: [whatwg/fetch] FormData content-type doesn't match form submission behavior in browsers (#422) (Monday, 28 November)
• Re: [whatwg/fetch] FormData content-type doesn't match form submission behavior in browsers (#422) (Friday, 25 November)
• Re: [whatwg/streams] Cloning (not teeing) a readable stream, via controller tricks (#599) (Thursday, 24 November)
• Re: [whatwg/streams] Cloning (not teeing) a readable stream, via controller tricks (#599) (Sunday, 13 November)

Yutaka Hirano

• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 29 November)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 29 November)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 29 November)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 29 November)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 29 November)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 29 November)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 29 November)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 29 November)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Tuesday, 29 November)
• [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 28 November)
• Re: [whatwg/fetch] Streams and fetches that outlive the environment settings object (#411) (Thursday, 10 November)
• Re: [whatwg/fetch] CORS protocol and HTTP caches (#402) (Thursday, 10 November)
• Re: [whatwg/fetch] CORS protocol and HTTP caches (#402) (Thursday, 10 November)
• Re: [whatwg/fetch] Streams and fetches that outlive the environment settings object (#411) (Tuesday, 8 November)
• Re: [whatwg/fetch] CORS protocol and HTTP caches (#402) (Tuesday, 1 November)

Yves Lafon

• Re: [w3c/push-api] Edit the summary on the repo (#225) (Friday, 25 November)
• Re: [w3c/push-api] Edit the summary on the repo (#225) (Friday, 25 November)
• Re: [w3c/ServiceWorker] Editorial: export Handle Functional Event (#1008) (Monday, 21 November)
• Re: [w3c/ServiceWorker] Editorial: export terms for Fetch (#999) (Tuesday, 1 November)

Zach Lym

• Re: [w3c/ServiceWorker] Disable SW's when cookies are disabled? (#209) (Monday, 28 November)

Zambonifofex

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 19 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 8 November)

行云流水

• [w3c/webcomponents] When to PUBLIC? (#599) (Wednesday, 2 November)

Last message date: Wednesday, 30 November 2016 22:50:16 UTC