public-webapps-github@w3.org from February 2017 by author

100の人

• Re: [whatwg/url] Define URL's toJSON() (#229) (Friday, 3 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Friday, 3 February)

achristensen07

• Re: [whatwg/url] Large ports of non special urls (#257) (Thursday, 23 February)
• [whatwg/url] Large ports of non special urls (#257) (Thursday, 23 February)
• Re: [whatwg/url] Change host parser for non-special schemes (#148) (Wednesday, 22 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)

Adam Rice

• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 28 February)
• Re: [whatwg/streams] strategy.size() can reenter WritableStream logic before its caller finishes all the work (#675) (Friday, 17 February)
• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Friday, 17 February)
• Re: [whatwg/streams] Chunking with Streams (#171) (Friday, 17 February)
• Re: [whatwg/streams] strategy.size() can reenter WritableStream logic before its caller finishes all the work (#675) (Friday, 17 February)
• Re: [whatwg/streams] Should write() always error the stream when it rejects the promise it returned? (#476) (Friday, 17 February)
• [whatwg/streams] Correct bad variable in PromiseInvokeOrNoop (#685) (Wednesday, 15 February)
• Re: [whatwg/streams] sink.abort() can be called during sink.start() (#683) (Wednesday, 15 February)
• [whatwg/streams] Are abstract operations supposed to be in alphabetical order? (#684) (Wednesday, 15 February)
• Re: [whatwg/streams] sink.abort() can be called during sink.start() (#683) (Wednesday, 15 February)
• Re: [whatwg/streams] sink.abort() can be called during sink.start() (#683) (Wednesday, 15 February)
• [whatwg/streams] sink.abort() can be called during sink.start() (#683) (Wednesday, 15 February)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Wednesday, 15 February)
• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Tuesday, 14 February)
• [whatwg/streams] "If returnValue is an abrupt completion, return ..." (#682) (Tuesday, 14 February)
• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Tuesday, 14 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Tuesday, 14 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Tuesday, 14 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Tuesday, 14 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Tuesday, 14 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Tuesday, 14 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Tuesday, 14 February)
• Re: [whatwg/streams] Writable stream spec fixes (#681) (Monday, 13 February)
• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Monday, 13 February)
• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Monday, 13 February)
• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Monday, 13 February)
• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Monday, 13 February)
• Re: [whatwg/streams] Writable stream spec fixes (#681) (Monday, 13 February)
• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Friday, 10 February)
• Re: [whatwg/streams] strategy.size() can reenter WritableStream logic before its caller finishes all the work (#675) (Friday, 10 February)
• [whatwg/streams] Execute strategySize first in write() (#680) (Friday, 10 February)
• Re: [whatwg/streams] define semantics of {source,sink}.finally() (#636) (Friday, 10 February)
• Re: [whatwg/streams] strategy.size() can reenter WritableStream logic before its caller finishes all the work (#675) (Friday, 10 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Friday, 10 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Thursday, 9 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Thursday, 9 February)
• Re: [whatwg/encoding] " push a copy of input " (#92) (Thursday, 9 February)
• Re: [whatwg/encoding] " push a copy of input " (#92) (Thursday, 9 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Thursday, 9 February)
• [whatwg/encoding] " push a copy of input " (#92) (Thursday, 9 February)
• Re: [whatwg/streams] WebIDL syntax for parameterized streams? (#678) (Monday, 6 February)
• Re: [whatwg/streams] WebIDL syntax for parameterized streams? (#678) (Monday, 6 February)
• Re: [whatwg/streams] Export the "error the stream" concept? (#679) (Monday, 6 February)
• [whatwg/streams] Export the "error the stream" concept? (#679) (Monday, 6 February)
• [whatwg/streams] WebIDL syntax for parameterized streams? (#678) (Monday, 6 February)
• [whatwg/encoding] "decoder = TextDecoder(encoding)" (#90) (Monday, 6 February)

albertsylvester

• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 7 February)

Alex Russell

• Re: [w3ctag/spec-reviews] IndexedDB 2.0 features review (#153) (Wednesday, 22 February)
• Re: [w3ctag/spec-reviews] WebUSB (#108) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] WebUSB (#108) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] WebUSB (#108) (Thursday, 9 February)
• [w3ctag/spec-reviews] WASM JS API review (#151) (Tuesday, 7 February)

aliams

• Re: [w3c/IndexedDB] simplify algorithm names (#160) (Saturday, 25 February)
• Re: [w3c/IndexedDB] open/deleteDatabase should throw on opaque origin (#150) (Wednesday, 15 February)
• Re: [w3c/IndexedDB] Key generator behavior with explicit keys above 2^53 (#147) (Monday, 13 February)
• Re: [w3c/IndexedDB] Fix markdown indentation to repair algorithm. Resolves #142 (#143) (Monday, 6 February)

alvaropratama

• [whatwg/xhr] mobile legends hack dong (#110) (Tuesday, 7 February)

Andrea Giammarchi

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

Andres Rios

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Tuesday, 21 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)

Andrew Betts

• Re: [w3ctag/spec-reviews] Notifications API (#94) (Friday, 17 February)
• Re: [w3ctag/spec-reviews] Notifications API (#94) (Friday, 17 February)
• Re: [w3ctag/spec-reviews] PaymentRequest.canMakeActivePayment() (#146) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] IFrame support in web payments (#147) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] IFrame support in web payments (#147) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Review origin policy. (#127) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Review request for Scroll Anchoring (#142) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Review request for Scroll Anchoring (#142) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Review Accessibility Object Model (#134) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) (Wednesday, 8 February)

Andrew Sutherland

• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Friday, 3 February)

Andrey Logvinov

• Re: [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) (Thursday, 9 February)

anlex N

• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 28 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 28 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 28 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 21 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 21 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 21 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 21 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Saturday, 18 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Saturday, 18 February)
• [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Friday, 17 February)

Anne van Kesteren

• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Tuesday, 28 February)
• Re: [whatwg/fetch] Vary HTTP cache on credentials mode (#307) (Tuesday, 28 February)
• Re: [whatwg/fetch] Vary HTTP cache on credentials mode (#307) (Tuesday, 28 February)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 27 February)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 27 February)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 27 February)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 27 February)
• Re: [whatwg/dom] EventTarget.addEventListener lacks a proper definition on how to handle invalid callback (#405) (Monday, 27 February)
• Re: [whatwg/dom] Consider adding localNameFilter to MutationObserver (#398) (Monday, 27 February)
• Re: [whatwg/fetch] Go deeper into HTTP caching (#373) (Monday, 27 February)
• Re: [whatwg/url] Use empty host for file URL's (#260) (Monday, 27 February)
• Re: [whatwg/url] username/password/port should be removed when "file" is added as scheme (#259) (Monday, 27 February)
• Re: [whatwg/url] Use empty host for file URL's (#260) (Monday, 27 February)
• Re: [whatwg/dom] High resolution timing for events (#23) (Monday, 27 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Monday, 27 February)
• Re: [whatwg/url] username/password/port should be removed when "file" is added as scheme (#259) (Saturday, 25 February)
• Re: [whatwg/url] username/password/port should be removed when "file" is added as scheme (#259) (Saturday, 25 February)
• Re: [whatwg/url] username/password/port should be removed when "file" is added as scheme (#259) (Saturday, 25 February)
• Re: [whatwg/xhr] "To handle response end-of-body for response, ru..." (#116) (Saturday, 25 February)
• Re: [whatwg/xhr] Use a single slot for the response object (#124) (Saturday, 25 February)
• Re: [whatwg/xhr] Editorial: use a single response object (#126) (Saturday, 25 February)
• Re: [whatwg/xhr] Regression fix: need transmitted/length defined before progress event dispatch (#121) (Saturday, 25 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Saturday, 25 February)
• Re: [whatwg/url] username/password/port should be removed when "file" is added as scheme (#259) (Saturday, 25 February)
• Re: [whatwg/url] Use empty host for file URL's (#260) (Saturday, 25 February)
• Re: [heycam/webidl] short-svg (#322) (Saturday, 25 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Saturday, 25 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Saturday, 25 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Saturday, 25 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Saturday, 25 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Saturday, 25 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Saturday, 25 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Saturday, 25 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Friday, 24 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Friday, 24 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Friday, 24 February)
• Re: [whatwg/xhr] "Every millisecond, as long as the stop timeout flag is unset, queue a microtask to run these subsubsubsteps" looks wrong. (#112) (Friday, 24 February)
• Re: [whatwg/url] Use empty host for file URL's (#260) (Friday, 24 February)
• Re: [whatwg/xhr] overrideMimeType does not throw for invalid input (#125) (Friday, 24 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Friday, 24 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Friday, 24 February)
• Re: [whatwg/url] username/password/port should be removed when "file" is added as scheme (#259) (Friday, 24 February)
• Re: [w3c/webcomponents] Shadow dom innerhtml and CSP unsafe-inline (#627) (Friday, 24 February)
• Re: [whatwg/url] Empty or null host when scheme is "file:"? (#258) (Friday, 24 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Friday, 24 February)
• Re: [whatwg/xhr] Ensure progress events fired from "process response" always have a valid loaded value (#118) (Friday, 24 February)
• Re: [whatwg/xhr] Clarify when subsubsubsteps run in "process response" (#122) (Friday, 24 February)
• Re: [whatwg/url] Large ports of non special urls (#257) (Thursday, 23 February)
• Re: [whatwg/storage] API exposure/behavior for unique origins? (#41) (Thursday, 23 February)
• Re: [whatwg/storage] Disable the API in opaque origins (#43) (Thursday, 23 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Thursday, 23 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Thursday, 23 February)
• Re: [whatwg/url] Empty or null host when scheme is "file:"? (#258) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• Re: [whatwg/url] Empty or null host when scheme is "file:"? (#258) (Thursday, 23 February)
• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Thursday, 23 February)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Thursday, 23 February)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Thursday, 23 February)
• Re: [whatwg/xhr] Early return step needed for cancelled send()? (#101) (Thursday, 23 February)
• [whatwg/xhr] Editorial: use a single response object (#126) (Thursday, 23 February)
• [whatwg/xhr] overrideMimeType does not throw for invalid input (#125) (Thursday, 23 February)
• [whatwg/xhr] Use a single slot for the response object (#124) (Thursday, 23 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Thursday, 23 February)
• Re: [whatwg/xhr] Remove assertion/test annotation system (#119) (Thursday, 23 February)
• Re: [whatwg/xhr] Meta: remove annotation system and update deploy infrastructure (#123) (Thursday, 23 February)
• [whatwg/xhr] Meta: remove annotation system and update deploy infrastructure (#123) (Thursday, 23 February)
• Re: [whatwg/url] Large ports of non special urls (#257) (Thursday, 23 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 23 February)
• [whatwg/xhr] Clarify when subsubsubsteps run in "process response" (#122) (Thursday, 23 February)
• [whatwg/storage] Disable the API in opaque origins (#43) (Thursday, 23 February)
• Re: [whatwg/storage] Meta: enable PR preview (#42) (Thursday, 23 February)
• Re: [whatwg/storage] Meta: enable PR preview (#42) (Thursday, 23 February)
• Re: [whatwg/xhr] Ensure progress events fired from "process response" always have a valid loaded value (#118) (Thursday, 23 February)
• [heycam/webidl] Constant sequence value (#318) (Thursday, 23 February)
• Re: [whatwg/url] Change host parser for non-special schemes (#148) (Thursday, 23 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Thursday, 23 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [whatwg/xhr] Meta: enable PR preview (#117) (Wednesday, 22 February)
• Re: [whatwg/fetch] "parse a header value" should be more careful with types (#474) (Wednesday, 22 February)
• Re: [whatwg/fetch] Breaking: redo value parsing as value extraction (#494) (Wednesday, 22 February)
• Re: [whatwg/xhr] Ensure progress events fired from "process response" always have a valid loaded value (#118) (Wednesday, 22 February)
• [whatwg/fetch] "process request body" is gone (#495) (Wednesday, 22 February)
• [whatwg/xhr] Regression fix: need transmitted/length defined before progress event dispatch (#121) (Wednesday, 22 February)
• Re: [whatwg/xhr] Clean up "fire an event" and derivatives (#99) (Wednesday, 22 February)
• Re: [whatwg/xhr] Meta: enable PR preview (#117) (Wednesday, 22 February)
• Re: [whatwg/xhr] overrideMimeType cannot throw for invalid MIME types (#82) (Wednesday, 22 February)
• Re: [whatwg/xhr] setRequestHeader behavior doesn't seem to match implementations (#108) (Wednesday, 22 February)
• Re: [whatwg/xhr] overrideMimeType cannot throw for invalid MIME types (#82) (Wednesday, 22 February)
• Re: [whatwg/xhr] FormData.prototype.get should return `undefined` for not-present entries, instead of `null` (#27) (Wednesday, 22 February)
• Re: [whatwg/fetch] Breaking: redo value parsing as value extraction (#494) (Wednesday, 22 February)
• [whatwg/fetch] Breaking: redo value parsing as value extraction (#494) (Wednesday, 22 February)
• Re: [whatwg/xhr] overrideMimeType cannot throw for invalid MIME types (#82) (Wednesday, 22 February)
• Re: [whatwg/xhr] Should we be pinning Blob URIs on fetches? (#79) (Wednesday, 22 February)
• Re: [whatwg/xhr] Should we be pinning Blob URIs on fetches? (#79) (Wednesday, 22 February)
• Re: [whatwg/encoding] Meta: enable PR preview (#93) (Wednesday, 22 February)
• Re: [whatwg/encoding] Meta: enable PR preview (#93) (Wednesday, 22 February)
• Re: [whatwg/fetch] Meta: enable PR review (#493) (Wednesday, 22 February)
• Re: [whatwg/fetch] Meta: enable PR review (#493) (Wednesday, 22 February)
• Re: [whatwg/fetch] Response's trailer cannot use [SameObject] (#488) (Wednesday, 22 February)
• Re: [whatwg/fetch] Clarify the ABNF flavor in use (#490) (Wednesday, 22 February)
• Re: [whatwg/fetch] ABNF Notation Reference (#489) (Wednesday, 22 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Wednesday, 22 February)
• Re: [whatwg/fetch] Headers.get/getAll/has do not byte-lowercase the name (#203) (Wednesday, 22 February)
• Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Wednesday, 22 February)
• Re: [whatwg/xhr] overrideMimeType cannot throw for invalid MIME types (#82) (Wednesday, 22 February)
• Re: [whatwg/xhr] Should we be pinning Blob URIs on fetches? (#79) (Wednesday, 22 February)
• [w3c/FileAPI] Describe internal slots of Blob and File objects better (#71) (Wednesday, 22 February)
• Re: [whatwg/xhr] FormData.prototype.get should return `undefined` for not-present entries, instead of `null` (#27) (Wednesday, 22 February)
• Re: [whatwg/url] new URLSearchParams(entries) (#256) (Wednesday, 22 February)
• Re: [whatwg/url] new URLSearchParams(entries) (#256) (Wednesday, 22 February)
• Re: [whatwg/url] Remove javascript URL special case from the API (#254) (Wednesday, 22 February)
• Re: [whatwg/url] Remove special-casing of javascript URLs in the API (#253) (Wednesday, 22 February)
• Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Tuesday, 21 February)
• Re: [whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339) (Tuesday, 21 February)
• Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Tuesday, 21 February)
• Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Tuesday, 21 February)
• Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Tuesday, 21 February)
• Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Tuesday, 21 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Tuesday, 21 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 21 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Tuesday, 21 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 21 February)
• [whatwg/xhr] Document that cannot be serialized does not throw (#120) (Tuesday, 21 February)
• Re: [whatwg/fullscreen] Meta: enable PR preview (#77) (Tuesday, 21 February)
• Re: [whatwg/fetch] Make Request constructor more forgiving (#377) (Tuesday, 21 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 21 February)
• Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Tuesday, 21 February)
• Re: [whatwg/fetch] Streams based uploading with Content-Length (not chunked encoding) (#95) (Tuesday, 21 February)
• [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Monday, 20 February)
• [whatwg/xhr] Remove assertion/test annotation system (#119) (Monday, 20 February)
• Re: [whatwg/xhr] Ensure progress events fired from "process response" always have a valid loaded value (#118) (Monday, 20 February)
• Re: [whatwg/fetch] Streams based uploading with Content-Length (not chunked encoding) (#95) (Monday, 20 February)
• Re: [whatwg/url] Define a host's "public suffix" and "registrable domain" (#72) (Monday, 20 February)
• Re: [whatwg/url] Define a host's "public suffix" and "registrable domain" (#72) (Monday, 20 February)
• Re: [whatwg/fetch] Allow setting `cookie` header in credential-less CORS requests (#268) (Monday, 20 February)
• Re: [whatwg/fetch] Allow setting `cookie` header in credential-less CORS requests (#268) (Monday, 20 February)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Monday, 20 February)
• Re: [whatwg/url] Use Nontransitional_Processing for IDNA ToASCII (#240) (Monday, 20 February)
• Re: [whatwg/url] IDNA Nontransitional_Processing (#239) (Monday, 20 February)
• Re: [whatwg/url] IDNA Nontransitional_Processing (#239) (Monday, 20 February)
• Re: [whatwg/url] Remove javascript URL special case from the API (#254) (Monday, 20 February)
• [whatwg/storage] Meta: enable PR preview (#42) (Monday, 20 February)
• Re: [whatwg/encoding] Meta: enable PR preview (#93) (Monday, 20 February)
• [whatwg/xhr] Meta: enable PR preview (#117) (Monday, 20 February)
• Re: [heycam/webidl] Code-points, code-units, characters, oh my! (#312) (Monday, 20 February)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Monday, 20 February)
• Re: [heycam/webidl] Code-points, code-units, characters, oh my! (#312) (Monday, 20 February)
• [whatwg/fullscreen] Meta: enable PR preview (#77) (Saturday, 18 February)
• [whatwg/encoding] Meta: enable PR preview (#93) (Saturday, 18 February)
• [whatwg/dom] Meta: enable PR preview (#413) (Saturday, 18 February)
• [whatwg/fetch] Meta: enable PR review (#493) (Saturday, 18 February)
• Re: [whatwg/fetch] Expose PerformanceResourceTiming in Response Objects (#491) (Saturday, 18 February)
• Re: [whatwg/fetch] Allow service-workers mode to be set in fetch options (#492) (Saturday, 18 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Saturday, 18 February)
• Re: [whatwg/xhr] what's this mean ? fetch will be replace xmlhttprequest ? (#115) (Saturday, 18 February)
• Re: [whatwg/xhr] what's this mean ? fetch will be replace xmlhttprequest ? (#115) (Saturday, 18 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/url] Editorial: Minor formatting tweak (#255) (Friday, 17 February)
• Re: [whatwg/url] Editorial: Minor formatting tweak (#255) (Friday, 17 February)
• Re: [whatwg/url] Editorial: Minor formatting tweak (#255) (Friday, 17 February)
• Re: [whatwg/url] Editorial: Minor formatting tweak (#255) (Friday, 17 February)
• Re: [whatwg/url] Editorial: Minor formatting tweak (#255) (Friday, 17 February)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Friday, 17 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Friday, 17 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Friday, 17 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Friday, 17 February)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Friday, 17 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/url] A file URL cannot have credentials (#252) (Thursday, 16 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 16 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 16 February)
• Re: [whatwg/url] Remove special-casing of javascript URLs in the API (#253) (Thursday, 16 February)
• Re: [whatwg/url] Remove javascript URL special case from the API (#254) (Thursday, 16 February)
• [whatwg/url] Remove javascript URL special case from the API (#254) (Thursday, 16 February)
• [whatwg/url] Remove special-casing of javascript URLs in the API (#253) (Thursday, 16 February)
• [whatwg/url] A file URL cannot have credentials (#252) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Use DOMStringList for ancestorOrigins (#1052) (Thursday, 16 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Thursday, 16 February)
• Re: [w3c/FileAPI] Update feedback info (#69) (Thursday, 16 February)
• Re: [w3c/FileAPI] Update feedback info (#69) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Add Client type for ServiceWorkerGlobalScope environments (#1074) (Thursday, 16 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Thursday, 16 February)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 16 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Use DOMStringList for ancestorOrigins (#1052) (Thursday, 16 February)
• Re: [whatwg/url] Meta: make .pr-preview.json valid json (#251) (Wednesday, 15 February)
• Re: [whatwg/url] Meta: make .pr-preview.json valid json (#251) (Wednesday, 15 February)
• Re: [whatwg/url] Meta: update .pr-preview.json config file (#250) (Wednesday, 15 February)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Wednesday, 15 February)
• Re: [whatwg/url] Meta: update .pr-preview.json config file (#250) (Wednesday, 15 February)
• Re: [whatwg/dom] Meta: link to web-platform-tests in header (#411) (Wednesday, 15 February)
• Re: [whatwg/dom] Meta: link to web-platform-tests in header (#411) (Wednesday, 15 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Wednesday, 15 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Wednesday, 15 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Wednesday, 15 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Wednesday, 15 February)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Wednesday, 15 February)
• Re: [whatwg/storage] API exposure/behavior for unique origins? (#41) (Wednesday, 15 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Wednesday, 15 February)
• Re: [w3c/IndexedDB] Implement transaction cleanup hook for [HTML] (#145) (Wednesday, 15 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Wednesday, 15 February)
• Re: [whatwg/dom] Add legacyOutputDidListenersThrowFlag to event dispatch for IDB (#409) (Tuesday, 14 February)
• Re: [whatwg/dom] Add legacyOutputDidListenersThrowFlag to event dispatch for IDB (#409) (Tuesday, 14 February)
• [whatwg/fetch] Clarify the ABNF flavor in use (#490) (Tuesday, 14 February)
• Re: [whatwg/fetch] Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 14 February)
• Re: [whatwg/fetch] Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 14 February)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Tuesday, 14 February)
• Re: [whatwg/fetch] Dispatch to foreign fetch for redirects (#362) (Tuesday, 14 February)
• Re: [whatwg/fetch] Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 14 February)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Tuesday, 14 February)
• Re: [whatwg/fetch] Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 14 February)
• Re: [whatwg/fetch] ABNF Notation Reference (#489) (Tuesday, 14 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Tuesday, 14 February)
• Re: [heycam/webidl] Set up auto-deploy to GitHub pages from master (#221) (Tuesday, 14 February)
• Re: [w3c/IndexedDB] "If an exception was propagated out from any event handler" is not a thing (#140) (Tuesday, 14 February)
• [whatwg/dom] Add legacyOutputDidListenersThrowFlag to event dispatch for IDB (#409) (Tuesday, 14 February)
• Re: [w3c/IndexedDB] Implement transaction cleanup hook for [HTML] (#145) (Tuesday, 14 February)
• Re: [heycam/webidl] Set up auto-deploy to GitHub pages from master (#221) (Tuesday, 14 February)
• Re: [whatwg/url] Use Nontransitional_Processing for IDNA ToASCII (#240) (Tuesday, 14 February)
• Re: [whatwg/xhr] Editorial: add an IDL index (#113) (Tuesday, 14 February)
• Re: [whatwg/url] Editorial: remove one more instance of "simply" (#249) (Tuesday, 14 February)
• Re: [whatwg/url] Editorial: remove one more instance of "simply" (#249) (Tuesday, 14 February)
• Re: [whatwg/url] Avoid using "simply" (#201) (Tuesday, 14 February)
• Re: [whatwg/url] Editorial: use specific names for encode sets (#243) (Tuesday, 14 February)
• Re: [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Tuesday, 14 February)
• Re: [whatwg/fetch] Access to the HTTP trailer (#34) (Monday, 13 February)
• Re: [heycam/webidl] Add an informative section on overloads vs. unions/optional (#307) (Monday, 13 February)
• Re: [heycam/webidl] Add an informative section on overloads vs. unions/optional (#307) (Monday, 13 February)
• Re: [w3c/webcomponents] Support renaming, aliasing, or namespacing imported elements (#344) (Monday, 13 February)
• Re: [whatwg/fetch] Cannot use [SameObject] for trailers (#473) (Monday, 13 February)
• [whatwg/fetch] Response's trailer cannot use [SameObject] (#488) (Monday, 13 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Monday, 13 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Monday, 13 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Monday, 13 February)
• Re: [whatwg/xhr] Editorial: add an IDL index (#113) (Monday, 13 February)
• Re: [whatwg/xhr] Editorial: add an IDL index (#113) (Monday, 13 February)
• Re: [whatwg/xhr] Editorial: add an IDL index (#113) (Monday, 13 February)
• Re: [whatwg/url] Explicitly list non-goals (#233) (Monday, 13 February)
• Re: [w3c/webcomponents] Support renaming, aliasing, or namespacing imported elements (#344) (Monday, 13 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Monday, 13 February)
• Re: [heycam/webidl] Investigate banning nullable enums (#213) (Monday, 13 February)
• Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Monday, 13 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Monday, 13 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Monday, 13 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Monday, 13 February)
• Re: [w3c/webcomponents] Support renaming, aliasing, or namespacing imported elements (#344) (Monday, 13 February)
• Re: [whatwg/url] IDNA Nontransitional_Processing (#239) (Monday, 13 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Monday, 13 February)
• Re: [whatwg/url] Explicitly list non-goals (#233) (Monday, 13 February)
• Re: [whatwg/url] IDNA (#53) (Monday, 13 February)
• Re: [whatwg/fetch] Error-prone: "Response with null body status cannot have body" (#487) (Monday, 13 February)
• Re: [whatwg/xhr] Editorial: add an IDL index (#113) (Monday, 13 February)
• Re: [heycam/webidl] Add an informative section on overloads vs. unions/optional (#307) (Monday, 13 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Monday, 13 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Monday, 13 February)
• Re: [whatwg/url] Provide means to "strip query" (#247) (Monday, 13 February)
• Re: [whatwg/url] Typo in file state (#246) (Sunday, 12 February)
• Re: [whatwg/url] Editorial: use specific names for encode sets (#243) (Sunday, 12 February)
• Re: [whatwg/fullscreen] https://content.jwplatform.com/libraries/LJpSz0C8.js (#76) (Saturday, 11 February)
• Re: [whatwg/url] Editorial: use specific names for encode sets (#243) (Saturday, 11 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Saturday, 11 February)
• Re: [whatwg/url] Editorial: use specific names for encode sets (#243) (Saturday, 11 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Saturday, 11 February)
• Re: [whatwg/url] Editorial: use specific names for encode sets (#243) (Saturday, 11 February)
• Re: [whatwg/url] Editorial: use specific names for encode sets (#243) (Saturday, 11 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (c9e0a6c) (Saturday, 11 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/url] Make IPv6 addresses in special URLs valid (#238) (Friday, 10 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/url] Setting path to base's path seems wrong (#231) (Friday, 10 February)
• Re: [whatwg/url] Paths need to be copied from base URLs (#244) (Friday, 10 February)
• Re: [whatwg/url] Paths need to be copied from base URLs (#244) (Friday, 10 February)
• Re: [whatwg/url] Paths need to be copied from base URLs (#244) (Friday, 10 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• [whatwg/url] IDNA: avoid defining valid domain string in terms of the parser (#245) (Friday, 10 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Friday, 10 February)
• Re: [whatwg/url] Define which URLs are valid in the parser examples (#242) (Friday, 10 February)
• Re: [whatwg/url] Is file:///C|/foo/bar meant to be a syntax violation? (#209) (Friday, 10 February)
• Re: [whatwg/url] Define which URLs are valid in the parser examples (#242) (Friday, 10 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Friday, 10 February)
• Re: [whatwg/url] Define which URLs are valid in the parser examples (#242) (Friday, 10 February)
• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• Re: [whatwg/url] Define which URLs are valid in the parser examples (#242) (Friday, 10 February)
• Re: [whatwg/url] Define which URLs are valid in the parser examples (#242) (Friday, 10 February)
• Re: [whatwg/url] Use Nontransitional_Processing for IDNA ToASCII (#240) (Friday, 10 February)
• Re: [whatwg/url] Use Nontransitional_Processing for IDNA ToASCII (#240) (Friday, 10 February)
• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• [whatwg/url] Paths need to be copied from base URLs (#244) (Friday, 10 February)
• [whatwg/url] Editorial: use specific names for encode sets (#243) (Friday, 10 February)
• Re: [whatwg/url] Define which URLs are valid in the parser examples (#242) (Friday, 10 February)
• Re: [whatwg/url] Define which URLs are valid in the parser examples (#242) (Friday, 10 February)
• Re: [whatwg/url] Is file:///C|/foo/bar meant to be a syntax violation? (#209) (Friday, 10 February)
• [whatwg/url] Define which URLs are valid in the parser examples (#242) (Friday, 10 February)
• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• Re: [whatwg/url] Consider always escaping U+0020 (#125) (Friday, 10 February)
• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Friday, 10 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Friday, 10 February)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 10 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Friday, 10 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Friday, 10 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Friday, 10 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 9 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 9 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 9 February)
• Re: [whatwg/url] Editorial: use the Infra Standard for URL's path (#237) (Thursday, 9 February)
• Re: [whatwg/url] Use Infra more (#235) (Thursday, 9 February)
• Re: [whatwg/url] Editorial: use the Infra Standard for URL's path (#237) (Thursday, 9 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Thursday, 9 February)
• Re: [whatwg/url] IDNA Nontransitional_Processing (#239) (Thursday, 9 February)
• [whatwg/url] Use Nontransitional_Processing for IDNA ToASCII (#240) (Thursday, 9 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 9 February)
• Re: [whatwg/url] Editorial: use the Infra Standard for URL's path (#237) (Thursday, 9 February)
• Re: [whatwg/url] Editorial: use the Infra Standard for URL's path (#237) (Thursday, 9 February)
• Re: [whatwg/url] Editorial: use the Infra Standard for URL's path (#237) (Thursday, 9 February)
• [whatwg/url] IDNA Nontransitional_Processing (#239) (Thursday, 9 February)
• Re: [whatwg/url] Consider always escaping U+0020 (#125) (Thursday, 9 February)
• [whatwg/url] Make IPv6 addresses in special URLs valid (#238) (Thursday, 9 February)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Thursday, 9 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 9 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 9 February)
• [whatwg/url] Editorial: use the Infra Standard for URL's path (#237) (Thursday, 9 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Thursday, 9 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Thursday, 9 February)
• Re: [whatwg/url] Document, possibly standardize, "plus" scheme convention (#230) (Thursday, 9 February)
• Re: [whatwg/dom] Add event.srcElement as a legacy alias to event.target (#407) (Thursday, 9 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Thursday, 9 February)
• Re: [whatwg/url] Meta: enable preview and diffs for all pull requests (#236) (Thursday, 9 February)
• Re: [whatwg/encoding] " push a copy of input " (#92) (Thursday, 9 February)
• Re: [whatwg/url] Meta: enable preview and diffs for all pull requests (#236) (Thursday, 9 February)
• Re: [whatwg/url] Meta: enable preview and diffs for all pull requests (#236) (Thursday, 9 February)
• [whatwg/url] Meta: enable preview and diffs for all pull requests (#236) (Thursday, 9 February)
• Re: [whatwg/encoding] " push a copy of input " (#92) (Thursday, 9 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Thursday, 9 February)
• Re: [whatwg/xhr] indexing my site with my naanmani.wordpress.com in various places. (#111) (Thursday, 9 February)
• Re: [whatwg/xhr] indexing my site with my naanmani.wordpress.com in various places. (#111) (Thursday, 9 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Thursday, 9 February)
• Re: [whatwg/encoding] " push a copy of input " (#92) (Thursday, 9 February)
• Re: [whatwg/encoding] " push a copy of input " (#92) (Thursday, 9 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 8 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 8 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 8 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Wednesday, 8 February)
• Re: [whatwg/url] file: URL with a port number through the host setter (#97) (Wednesday, 8 February)
• [whatwg/url] Use Infra more (#235) (Wednesday, 8 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Wednesday, 8 February)
• Re: [whatwg/fetch] Regression: make Request constructor account for changes to fill (#484) (Wednesday, 8 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Wednesday, 8 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Wednesday, 8 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Wednesday, 8 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Wednesday, 8 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Wednesday, 8 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Wednesday, 8 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Wednesday, 8 February)
• Re: [whatwg/url] Meta: state idempotence clearly as a goal (#226) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Wednesday, 8 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [whatwg/url] Add more restrictions to the host parser (#159) (Wednesday, 8 February)
• Re: [whatwg/url] Add more restrictions to the host parser (#159) (Wednesday, 8 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Wednesday, 8 February)
• Re: [whatwg/fetch] Constructing a Headers from another Headers is lossy (#481) (Wednesday, 8 February)
• Re: [whatwg/fetch] Type confusion in Request constructor leading to underdefined behavior (#483) (Wednesday, 8 February)
• [whatwg/fetch] Regression: make Request constructor account for changes to fill (#484) (Wednesday, 8 February)
• Re: [whatwg/fetch] Type confusion in Request constructor leading to underdefined behavior (#483) (Wednesday, 8 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Wednesday, 8 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Wednesday, 8 February)
• [heycam/webidl] Allow records to be omitted (#304) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Wednesday, 8 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 8 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 8 February)
• Re: [whatwg/url] Repeated slashes should be arranged in file scheme (#234) (Wednesday, 8 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Wednesday, 8 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Wednesday, 8 February)
• Re: [whatwg/url] toJSON() serialization (#137) (Wednesday, 8 February)
• Re: [whatwg/url] toJSON() serialization (#137) (Wednesday, 8 February)
• Re: [whatwg/url] toJSON() serialization (#137) (Wednesday, 8 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Wednesday, 8 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Wednesday, 8 February)
• Re: [whatwg/dom] initEvent should not require three parameters (#387) (Wednesday, 8 February)
• Re: [whatwg/dom] initEvent should not require three parameters (#387) (Wednesday, 8 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Wednesday, 8 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Wednesday, 8 February)
• Re: [whatwg/dom] Fallback to legacy type only when event is trusted (#406) (Wednesday, 8 February)
• Re: [whatwg/dom] Fallback to legacy type only when event is trusted (#406) (Wednesday, 8 February)
• Re: [w3c/FileAPI] Rename Blob URL to Object URL (#65) (Wednesday, 8 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Tuesday, 7 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Tuesday, 7 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Tuesday, 7 February)
• Re: [whatwg/url] Meta: state idempotence clearly as a goal (#226) (Tuesday, 7 February)
• Re: [whatwg/url] Meta: state idempotence clearly as a goal (#226) (Tuesday, 7 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [whatwg/url] Editorial: move Windows drive letter to a more logical location (#227) (Tuesday, 7 February)
• Re: [whatwg/url] Meta: state idempotence clearly as a goal (#226) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Tuesday, 7 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Tuesday, 7 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)
• Re: [heycam/webidl] Allow extended attributes to apply to types (#286) (Tuesday, 7 February)
• Re: [whatwg/fetch] Constructing a Headers from another Headers is lossy (#481) (Tuesday, 7 February)
• Re: [whatwg/fetch] Add several ports to the "bad ports" list. (#482) (Tuesday, 7 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [whatwg/encoding] "decoder = TextDecoder(encoding)" (#90) (Tuesday, 7 February)
• Re: [whatwg/encoding] Editorial: fix formatting of code and add new to constructor (#91) (Tuesday, 7 February)
• Re: [w3c/FileAPI] What should the ProgressEvent attributes be in the case of an error/abort? (#14) (Tuesday, 7 February)
• Re: [w3c/FileAPI] Rename Blob URL to Object URL (#65) (Tuesday, 7 February)
• Re: [whatwg/encoding] Editorial: fix formatting of code and add new to constructor (#91) (Tuesday, 7 February)
• Re: [whatwg/encoding] "decoder = TextDecoder(encoding)" (#90) (Tuesday, 7 February)
• [whatwg/encoding] Editorial: fix formatting of code and add new to constructor (#91) (Tuesday, 7 February)
• Re: [whatwg/fetch] Meta: update spec deploy and editing infrastructure (#478) (Tuesday, 7 February)
• Re: [whatwg/fetch] Meta: update spec deploy and editing infrastructure (#478) (Tuesday, 7 February)
• Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Tuesday, 7 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)
• Re: [whatwg/url] File state did not correctly deal with lack of base URL (#225) (Tuesday, 7 February)
• Re: [whatwg/url] file state needs clarification (#217) (Tuesday, 7 February)
• Re: [whatwg/url] File state did not correctly deal with lack of base URL (#225) (Tuesday, 7 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Tuesday, 7 February)
• Re: [whatwg/url] Document, possibly standardize, "plus" scheme convention (#230) (Tuesday, 7 February)
• Re: [whatwg/url] Setting path to base's path seems wrong (#231) (Tuesday, 7 February)
• Re: [whatwg/url] Setting path to base's path seems wrong (#231) (Tuesday, 7 February)
• Re: [whatwg/xhr] mobile legends hack dong (#110) (Tuesday, 7 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Tuesday, 7 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Tuesday, 7 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Tuesday, 7 February)
• Re: [whatwg/url] Explicitly list non-goals (#233) (Tuesday, 7 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Thursday, 2 February)
• Re: [whatwg/url] Meta: state idempotence clearly as a goal (#226) (Thursday, 2 February)
• Re: [whatwg/url] Meta: state idempotence clearly as a goal (#226) (Thursday, 2 February)
• Re: [whatwg/url] toJSON() serialization (#137) (Thursday, 2 February)
• [whatwg/url] Define URL's toJSON() (#229) (Thursday, 2 February)
• Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Thursday, 2 February)
• [heycam/webidl] Drop toJSON as reserved identifier (#293) (Thursday, 2 February)
• Re: [heycam/webidl] Editorial: markup legacy caller correctly (#244) (Thursday, 2 February)
• Re: [heycam/webidl] Editorial: markup legacy caller correctly (#244) (Thursday, 2 February)
• Re: [whatwg/url] Should 'C%3A' or 'C%7C' be interpreted as 'C:' and 'C|'? (#210) (Thursday, 2 February)
• Re: [whatwg/url] Maybe ensure there is a path item after the Windows drive letter path item (#193) (Thursday, 2 February)
• Re: [whatwg/url] Maybe ensure there is a path item after the Windows drive letter path item (#193) (Thursday, 2 February)
• Re: [whatwg/url] Is file:///C|/foo/bar meant to be a syntax violation? (#209) (Thursday, 2 February)
• [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 2 February)
• [whatwg/url] Editorial: move Windows drive letter to a more logical location (#227) (Thursday, 2 February)
• Re: [whatwg/url] Should 'C%3A' or 'C%7C' be interpreted as 'C:' and 'C|'? (#210) (Thursday, 2 February)
• Re: [whatwg/dom] Meta: use SSH securely (#397) (Thursday, 2 February)
• Re: [whatwg/dom] Meta: use SSH securely (#397) (Thursday, 2 February)
• Re: [whatwg/url] IDNA2008 (#223) (Thursday, 2 February)
• [whatwg/fetch] Meta: update spec deploy and editing infrastructure (#478) (Thursday, 2 February)
• Re: [whatwg/fetch] Meta: update spec deploy and editing infrastructure (#478) (Thursday, 2 February)
• Re: [whatwg/url] IDNA2008 (#223) (Thursday, 2 February)
• Re: [whatwg/url] URLSearchParams constructor test has a bug (#220) (Thursday, 2 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Thursday, 2 February)
• Re: [whatwg/url] IDNA2008 (#223) (Thursday, 2 February)
• Re: [whatwg/url] IDNA2008 (#223) (Thursday, 2 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Thursday, 2 February)
• Re: [whatwg/url] File state did not correctly deal with lack of base URL (#225) (Thursday, 2 February)
• [whatwg/url] Meta: state idempotence clearly as a goal (#226) (Thursday, 2 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Thursday, 2 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Thursday, 2 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Thursday, 2 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Wednesday, 1 February)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 1 February)
• [whatwg/url] File state did not correctly deal with lack of base URL (#225) (Wednesday, 1 February)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 1 February)
• [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 1 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Wednesday, 1 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 1 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 1 February)
• Re: [whatwg/url] file: URL with a port number through the host setter (#97) (Wednesday, 1 February)
• [whatwg/url] Cleanup API for file and non-special URLs (#224) (Wednesday, 1 February)
• Re: [whatwg/fetch] Fix typo particpating->participating (#477) (Wednesday, 1 February)
• Re: [whatwg/fetch] Fix typo particpating->participating (#477) (Wednesday, 1 February)
• Re: [whatwg/dom] EventTarget.addEventListener lacks a proper definition on how to handle invalid callback (#405) (Wednesday, 1 February)
• Re: [w3c/FileAPI] Remove createFor() (#57) (Wednesday, 1 February)
• Re: [w3c/FileAPI] Remove the URL.createFor method. (#62) (Wednesday, 1 February)

anonymous

• Re: [whatwg/xhr] what's this mean ? fetch will be replace xmlhttprequest ? (#115) (Saturday, 18 February)
• [whatwg/xhr] what's this mean ? fetch will be repalce xmlhttprequest ? (#115) (Friday, 17 February)

Anssi Kostiainen

• Re: [w3c/manifest] Simple Example and Complex Example (#553) (Friday, 10 February)

Aron Nyborg Allen

• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 14 February)
• [w3c/IndexedDB] Security and Web Worker access for IndexedDB (#141) (Thursday, 2 February)

Ben Kelly

• Re: [w3c/ServiceWorker] clarify Clients.matchAll() focus order for nested frames (#1080) (Tuesday, 28 February)
• Re: [w3c/ServiceWorker] clarify Clients.matchAll() focus order for nested frames (#1080) (Tuesday, 28 February)
• [w3c/ServiceWorker] SW spec associates Client objects with browsing context in a couple places (#1083) (Tuesday, 28 February)
• Re: [w3c/ServiceWorker] clarify Clients.matchAll() focus order for nested frames (#1080) (Tuesday, 28 February)
• Re: [w3c/ServiceWorker] clarify that Client "creation order" means when reserved Client created (#1078) (Monday, 27 February)
• Re: [w3c/ServiceWorker] clarify that Client "creation order" means when reserved Client created (#1078) (Monday, 27 February)
• Re: [w3c/ServiceWorker] clarify Clients.matchAll() focus order for nested frames (#1080) (Friday, 24 February)
• Re: [w3c/ServiceWorker] clarify that Client "creation order" means when reserved Client created (#1078) (Friday, 24 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• [w3c/ServiceWorker] clarify Clients.matchAll() focus order for nested frames (#1080) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• [w3c/ServiceWorker] clarify that Client "creation order" means when reserved Client created (#1078) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Service worker ID - remove? (#1076) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Service worker ID - remove? (#1076) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Service worker ID - remove? (#1076) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Service worker ID - remove? (#1076) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Track ancestorOrigins privacy issues (#1075) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] `Clients.matchAll()` should exclude the current environment (#1037) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Support returning ServiceWorker Client environments from `Clients.matchAll()` (#1036) (Thursday, 16 February)
• [w3c/ServiceWorker] Add Client type for ServiceWorkerGlobalScope environments (#1074) (Wednesday, 15 February)
• Re: [w3c/ServiceWorker] Support returning ServiceWorker Client environments from `Clients.matchAll()` (#1036) (Wednesday, 15 February)
• Re: [w3c/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Wednesday, 15 February)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Tuesday, 14 February)
• Re: [whatwg/fetch] should CSP be checked on each redirect? (#485) (Thursday, 9 February)
• Re: [whatwg/fetch] should CSP be checked on each redirect? (#485) (Thursday, 9 February)
• Re: [whatwg/fetch] should CSP be checked on each redirect? (#485) (Thursday, 9 February)
• [whatwg/fetch] should CSP be checked on each redirect? (#485) (Thursday, 9 February)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Thursday, 9 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Tuesday, 7 February)
• Re: [w3c/ServiceWorker] Pagination in cache.keys() (#1066) (Friday, 3 February)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Thursday, 2 February)

Ben Lesh

• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Monday, 20 February)

Boris Zbarsky

• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 28 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 28 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 28 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 28 February)
• Re: [heycam/webidl] Why can't an inherited dictionary override something as required? (#321) (Thursday, 23 February)
• Re: [heycam/webidl] Make the situation with [] default values a bit clearer. (#319) (Thursday, 23 February)
• [heycam/webidl] Make the situation with [] default values a bit clearer. (#319) (Thursday, 23 February)
• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Wednesday, 15 February)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Wednesday, 15 February)
• Re: [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Tuesday, 14 February)
• Re: [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Tuesday, 14 February)
• [heycam/webidl] Distinguishability categories are a bit confused about types vs non-types (#309) (Monday, 13 February)
• Re: [heycam/webidl] Allow records to be nullable in all cases and omitted as optional operation arguments. (#305) (Monday, 13 February)
• Re: [heycam/webidl] Allow records to be nullable in all cases and omitted as optional operation arguments. (#305) (Monday, 13 February)
• Re: [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Monday, 13 February)
• Re: [heycam/webidl] Add an informative section on overloads vs. unions/optional (#307) (Monday, 13 February)
• Re: [heycam/webidl] Add an informative section on overloads vs. unions/optional (#307) (Monday, 13 February)
• Re: [heycam/webidl] Add an informative section on overloads vs. unions/optional (#307) (Monday, 13 February)
• Re: [heycam/webidl] Add an informative section on overloads vs. unions/optional (#307) (Monday, 13 February)
• [heycam/webidl] No obvious way to link to the effective overload set construction algorithm (#308) (Monday, 13 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Saturday, 11 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Saturday, 11 February)
• Re: [heycam/webidl] Allow records to be nullable in all cases and omitted as optional operation arguments. (#305) (Saturday, 11 February)
• [heycam/webidl] Allow records to be nullable in all cases and omitted as optional operation arguments. (#305) (Saturday, 11 February)
• Re: [whatwg/fetch] should CSP be checked on each redirect? (#485) (Thursday, 9 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Wednesday, 8 February)
• Re: [whatwg/fetch] Regression: make Request constructor account for changes to fill (#484) (Wednesday, 8 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Wednesday, 8 February)
• Re: [heycam/webidl] Disambiguate / explain maplike vs record (#303) (Wednesday, 8 February)
• Re: [heycam/webidl] Disambiguate / explain maplike vs record (#303) (Wednesday, 8 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [heycam/webidl] Allow extended attributes to apply to types (#286) (Tuesday, 7 February)
• [whatwg/fetch] Type confusion in Request constructor leading to underdefined behavior (#483) (Tuesday, 7 February)
• Re: [whatwg/fetch] Constructing a Headers from another Headers is lossy (#481) (Tuesday, 7 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [whatwg/fetch] Add several ports to the "bad ports" list. (#482) (Tuesday, 7 February)
• Re: [heycam/webidl] Fix an example of serialization behavior (#302) (Tuesday, 7 February)
• Re: [heycam/webidl] Fix an example of serialization behavior (#302) (Tuesday, 7 February)
• Re: [heycam/webidl] Clarify that exceptions are always thrown in the current Realm (#300) (Tuesday, 7 February)
• Re: [heycam/webidl] Environment stuff for exception throwing is nonsense (#292) (Tuesday, 7 February)
• Re: [heycam/webidl] Clarify that exceptions are always thrown in the current Realm (#300) (Tuesday, 7 February)
• Re: [heycam/webidl] `any` type conversion does not take into account of symbols (#301) (Tuesday, 7 February)
• Re: [heycam/webidl] `any` type conversion does not take into account of symbols (#301) (Tuesday, 7 February)
• Re: [heycam/webidl] Allow extended attributes to apply to types (#286) (Friday, 3 February)
• [whatwg/fetch] Constructing a Headers from another Headers is lossy (#481) (Friday, 3 February)
• Re: [heycam/webidl] Environment stuff for exception throwing is nonsense (#292) (Friday, 3 February)
• Re: [heycam/webidl] Fix #296: ban dictionary recursion through records. (#298) (Friday, 3 February)
• Re: [heycam/webidl] Fix #296: ban dictionary recursion through records. (#298) (Friday, 3 February)
• Re: [heycam/webidl] Dictionary inclusion rules need to take record<> into account (#296) (Friday, 3 February)
• Re: [heycam/webidl] Ban nullable records in dictionary members and operation arguments. (#299) (Friday, 3 February)
• Re: [heycam/webidl] Where does it say that a nullable record<> cannot be the type of a dictionary member? (#295) (Friday, 3 February)
• Re: [heycam/webidl] Where does it say that a nullable record<> cannot be the type of an operation argument? (#297) (Friday, 3 February)
• Re: [heycam/webidl] Ban nullable records in dictionary members and operation arguments. (#299) (Friday, 3 February)
• Re: [heycam/webidl] Where does it say that a nullable record<> cannot be the type of a dictionary member? (#295) (Friday, 3 February)
• Re: [heycam/webidl] Where does it say that a nullable record<> cannot be the type of a dictionary member? (#295) (Friday, 3 February)
• Re: [heycam/webidl] Sort out when dictionaries and records should have default values (#76) (Friday, 3 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Friday, 3 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Friday, 3 February)
• [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Friday, 3 February)
• [heycam/webidl] Where does it say that a nullable record<> cannot be the type of an operation argument? (#297) (Friday, 3 February)
• Re: [heycam/webidl] Dictionary inclusion rules need to take record<> into account (#296) (Friday, 3 February)
• [heycam/webidl] Dictionary inclusion rules need to take record<> into account (#296) (Friday, 3 February)
• [heycam/webidl] Where does it say that a nullable record cannot be the type of a dictionary member? (#295) (Friday, 3 February)
• Re: [heycam/webidl] Do records purposefully throw on any object with an enumerable Symbol-named property? (#294) (Friday, 3 February)
• [heycam/webidl] Do records purposefully throw on any object with an enumerable Symbol-named property? (#294) (Friday, 3 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Thursday, 2 February)
• Re: [heycam/webidl] Drop toJSON as reserved identifier (#293) (Thursday, 2 February)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 1 February)
• [heycam/webidl] Environment stuff for exception throwing is nonsense (#292) (Wednesday, 1 February)

Brad Nelson

• Re: [w3c/IndexedDB] Security: Add note about UAs needing to handle version skew (#139) (Wednesday, 1 February)

Brett Zamir

• Re: [w3c/IndexedDB] Grant access to other origins (#60) (Friday, 24 February)
• Re: [w3c/IndexedDB] Grant access to other origins (#60) (Thursday, 23 February)
• Re: [w3c/IndexedDB] Key generator behavior with explicit keys above 2^53 (#147) (Thursday, 23 February)
• Re: [w3c/IndexedDB] Rework key generator algorithm (#153) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] Rework key generator algorithm (#153) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] Fixes for 'steps for storing' (#146) (Saturday, 18 February)
• Re: [w3c/IndexedDB] Fixes for 'steps for storing' (#146) (Thursday, 16 February)
• Re: [w3c/IndexedDB] Fixes for 'steps for storing' (#146) (Wednesday, 15 February)
• Re: [w3c/IndexedDB] Key generator behavior with explicit keys above 2^53 (#147) (Tuesday, 14 February)
• Re: [w3c/IndexedDB] Fixes for 'steps for storing' (#146) (Tuesday, 14 February)
• Re: [w3c/IndexedDB] Fixes for 'steps for storing' (#146) (Tuesday, 14 February)
• Re: [w3c/IndexedDB] Simplify "steps for storing a record into an object store"? (#144) (Sunday, 12 February)
• Re: [w3c/IndexedDB] Simplify "steps for storing a record into an object store"? (#144) (Sunday, 12 February)
• Re: [w3c/IndexedDB] Simplify "steps for storing a record into an object store"? (#144) (Sunday, 12 February)
• Re: [w3c/IndexedDB] Simplify "steps for storing a record into an object store"? (#144) (Sunday, 12 February)
• [w3c/IndexedDB] Simplify "steps for storing a record into an object store"? (#144) (Sunday, 12 February)

Bryan Bess

• [w3c/webcomponents] Fix a few typos (#625) (Saturday, 11 February)

Cameron McCormack

• Re: [heycam/webidl] Set up auto-deploy to GitHub pages from master (#221) (Tuesday, 14 February)
• Re: [heycam/webidl] Set up auto-deploy to GitHub pages from master (#221) (Tuesday, 14 February)

cardner

• Re: [w3c/webcomponents] Shadow dom innerhtml and CSP unsafe-inline (#627) (Saturday, 18 February)
• Re: [w3c/webcomponents] Shadow dom innerhtml and CSP unsafe-inline (#627) (Saturday, 18 February)
• [w3c/webcomponents] Shadow dom innerhtml and CSP unsafe-inline (#627) (Saturday, 18 February)

Chris Dumez

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 24 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 24 February)
• Re: [whatwg/dom] initEvent should not require three parameters (#387) (Friday, 24 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 24 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 21 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 21 February)
• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Wednesday, 15 February)
• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Wednesday, 15 February)
• Re: [whatwg/dom] initEvent should not require three parameters (#387) (Wednesday, 8 February)

Chris Peterson

• Re: [whatwg/dom] High resolution timing for events (#23) (Sunday, 26 February)

Chris Rebert

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Saturday, 11 February)

Claudio Gomboli

• Re: [w3c/manifest] Icon shapes and masking (#555) (Thursday, 16 February)

Conrad Irwin

• Re: [whatwg/fetch] Error-prone: "Response with null body status cannot have body" (#487) (Monday, 13 February)
• Re: [whatwg/fetch] Error-prone: "Response with null body status cannot have body" (#487) (Monday, 13 February)
• [whatwg/fetch] Error-prone: "Response with null body status cannot have body" (#487) (Monday, 13 February)
• Re: [w3c/ServiceWorker] Pagination in cache.keys() (#1066) (Friday, 3 February)
• [w3c/ServiceWorker] Pagination in cache.keys() (#1066) (Friday, 3 February)

cynthia

• Re: [w3c/IndexedDB] Clarify purpose and lifetime of upgrade transactions (#155) (Friday, 24 February)
• Re: [w3c/IndexedDB] Clarify purpose and lifetime of upgrade transactions (#155) (Friday, 24 February)
• Re: [w3c/IndexedDB] Clarify purpose and lifetime of upgrade transactions (#155) (Friday, 24 February)
• [w3c/IndexedDB] Non-normative note about what an upgrade transaction is normally used for (#154) (Wednesday, 22 February)
• Re: [w3ctag/spec-reviews] IndexedDB 2.0 features review (#153) (Wednesday, 22 February)
• Re: [w3ctag/spec-reviews] IndexedDB 2.0 features review (#153) (Wednesday, 22 February)
• Re: [w3ctag/spec-reviews] TV Control API (#111) (Tuesday, 21 February)
• Re: [w3ctag/spec-reviews] IndexedDB 2.0 features review (#153) (Tuesday, 21 February)

Cyril Auburtin

• Re: [whatwg/url] new URLSearchParams(entries) (#256) (Wednesday, 22 February)
• [whatwg/url] new URLSearchParams(entries) (#256) (Tuesday, 21 February)

Daijirō Wachi

• Re: [whatwg/url] username/password/port should be removed when "file" is added as scheme (#259) (Saturday, 25 February)
• Re: [whatwg/url] username/password/port should be removed when "file" is added as scheme (#259) (Saturday, 25 February)
• Re: [whatwg/url] username/password/port should be removed when "file" is added as scheme (#259) (Saturday, 25 February)
• Re: [whatwg/url] username/password/port should be removed when "file" is added as scheme (#259) (Saturday, 25 February)
• [whatwg/url] username/password/port should be removed when "file" is added as scheme (#259) (Thursday, 23 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Friday, 17 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Thursday, 9 February)
• Re: [whatwg/url] Repeated slashes should be ignored in file scheme (#234) (Wednesday, 8 February)
• Re: [whatwg/url] Repeated slashes should be ignored in file scheme (#234) (Wednesday, 8 February)
• [whatwg/url] Repeated slashes should be arranged in file scheme (#234) (Tuesday, 7 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Tuesday, 7 February)
• [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Sunday, 5 February)

Daniel Appelquist

• Re: [w3ctag/spec-reviews] Media Capture From DOM Element (#130) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Media Capture From DOM Element (#130) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] TV Control API (#111) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Custom Paint API to CR (#140) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] WebRTC Stats review (#148) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Long Task API (#150) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Geofencing FPWD (#89) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Geofencing FPWD (#89) (Wednesday, 8 February)

Daniel Buchner

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

Daniel Stenberg

• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• [whatwg/url] All the other network schemes (#241) (Friday, 10 February)
• Re: [whatwg/url] IDNA2008 (#223) (Thursday, 2 February)
• Re: [whatwg/url] IDNA2008 (#223) (Thursday, 2 February)
• Re: [whatwg/url] IDNA2008 (#223) (Thursday, 2 February)
• Re: [whatwg/url] IDNA2008 (#223) (Thursday, 2 February)
• Re: [whatwg/url] IDNA2008 (#223) (Thursday, 2 February)

Daosheng Mu

• [w3c/gamepad] GamepadHapticActuator pulse should be annotated [Throws, NewObject] (#59) (Monday, 20 February)
• [w3c/gamepad] GamepadHapticActuator needs to define the situation of loss focus (#58) (Friday, 17 February)

Dave Herman

• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 23 February)

Dave Tapuska

• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Thursday, 23 February)
• [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Thursday, 23 February)
• [w3c/uievents] Clearly specify initUIEvent (#133) (Tuesday, 21 February)

Dennis Schubert

• Re: [whatwg/dom] EventTarget.addEventListener lacks a proper definition on how to handle invalid callback (#405) (Monday, 27 February)
• Re: [whatwg/dom] EventTarget.addEventListener lacks a proper definition on how to handle invalid callback (#405) (Monday, 27 February)
• Re: [whatwg/dom] EventTarget.addEventListener lacks a proper definition on how to handle invalid callback (#405) (Monday, 27 February)

dhalapathy

• Re: [whatwg/xhr] indexing my site with my naanmani.wordpress.com in various places. (#111) (Thursday, 9 February)
• [whatwg/xhr] indexing my site with my naanmani.wordpress.com in various places. (#111) (Thursday, 9 February)

Domenic Denicola

• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Saturday, 25 February)
• Re: [whatwg/streams] Access to reader.readIntoRequests withtout checking reader type (#686) (Friday, 24 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 24 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 24 February)
• Re: [heycam/webidl] Cleanup DOMException. (#320) (Thursday, 23 February)
• Re: [heycam/webidl] Why can't an inherited dictionary override something as required? (#321) (Thursday, 23 February)
• Re: [heycam/webidl] Why can't an inherited dictionary override something as required? (#321) (Thursday, 23 February)
• [heycam/webidl] Why can't an inherited dictionary override something as required? (#321) (Thursday, 23 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Thursday, 23 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 23 February)
• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• [w3ctag/spec-reviews] allow-top-navigation-by-user-activation (#154) (Thursday, 23 February)
• Re: [heycam/webidl] Base sequences, dictionaries, and records on Infra types (#317) (Wednesday, 22 February)
• Re: [heycam/webidl] Base sequences, dictionaries, and records on Infra types (#317) (Wednesday, 22 February)
• Re: [heycam/webidl] Base sequences, dictionaries, and records on Infra types (#317) (Wednesday, 22 February)
• Re: [heycam/webidl] Base sequences, dictionaries, and records on Infra types (#317) (Wednesday, 22 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Wednesday, 22 February)
• [heycam/webidl] Base sequences, dictionaries, and records on Infra types (#317) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Wednesday, 22 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [heycam/webidl] Carry out math operations on real numbers, not IEEE 754. (#316) (Wednesday, 22 February)
• Re: [heycam/webidl] Carry out math operations on real numbers, not IEEE 754. (#316) (Wednesday, 22 February)
• Re: [heycam/webidl] Carry out math operations on real numbers, not IEEE 754. (#316) (Wednesday, 22 February)
• Re: [heycam/webidl] Carry out math operations on real numbers, not IEEE 754. (#316) (Wednesday, 22 February)
• Re: [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Wednesday, 22 February)
• Re: [whatwg/xhr] FormData.prototype.get should return `undefined` for not-present entries, instead of `null` (#27) (Wednesday, 22 February)
• Re: [whatwg/url] Remove javascript URL special case from the API (#254) (Tuesday, 21 February)
• Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Tuesday, 21 February)
• Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Tuesday, 21 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 21 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 21 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 21 February)
• Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Tuesday, 21 February)
• Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Tuesday, 21 February)
• [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Monday, 20 February)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Friday, 17 February)
• Re: [w3c/IndexedDB] Implement transaction cleanup hook for [HTML] (#145) (Friday, 17 February)
• Re: [whatwg/streams] Should write() always error the stream when it rejects the promise it returned? (#476) (Friday, 17 February)
• Re: [whatwg/streams] Should write() always error the stream when it rejects the promise it returned? (#476) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Thursday, 16 February)
• Re: [whatwg/url] A file URL cannot have credentials (#252) (Thursday, 16 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 16 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 16 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 16 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 16 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Wednesday, 15 February)
• [w3c/ServiceWorker] Update to reference HTML for link rel=serviceworker (#1073) (Wednesday, 15 February)
• Re: [w3c/ServiceWorker] Use DOMStringList for ancestorOrigins (#1052) (Wednesday, 15 February)
• Re: [whatwg/streams] Correct bad variable in PromiseInvokeOrNoop (#685) (Wednesday, 15 February)
• Re: [whatwg/streams] "If returnValue is an abrupt completion, return ..." (#682) (Wednesday, 15 February)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Wednesday, 15 February)
• Re: [whatwg/streams] Are abstract operations supposed to be in alphabetical order? (#684) (Wednesday, 15 February)
• Re: [w3c/IndexedDB] Implement transaction cleanup hook for [HTML] (#145) (Wednesday, 15 February)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Tuesday, 14 February)
• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Tuesday, 14 February)
• Re: [whatwg/streams] "Set totalSize to totalSize + pair.[[size]]." (#582) (Tuesday, 14 February)
• Re: [whatwg/streams] precision issues with very large chunks and desiredSize (#657) (Tuesday, 14 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Tuesday, 14 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Tuesday, 14 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Tuesday, 14 February)
• Re: [whatwg/dom] Add legacyOutputDidListenersThrowFlag to event dispatch for IDB (#409) (Tuesday, 14 February)
• Re: [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Tuesday, 14 February)
• Re: [whatwg/dom] Add legacyOutputDidListenersThrowFlag to event dispatch for IDB (#409) (Tuesday, 14 February)
• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Monday, 13 February)
• Re: [heycam/webidl] Allow extended attributes to apply to types (#286) (Monday, 13 February)
• Re: [heycam/webidl] Allow records to be nullable in all cases and omitted as optional operation arguments. (#305) (Monday, 13 February)
• Re: [whatwg/url] Editorial: use specific names for encode sets (#243) (Monday, 13 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Monday, 13 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Monday, 13 February)
• Re: [whatwg/dom] "If options is a dictionary, then set capture to..." (#408) (Monday, 13 February)
• Re: [whatwg/streams] Writable stream spec fixes (#681) (Monday, 13 February)
• Re: [whatwg/xhr] Editorial: add an IDL index (#113) (Monday, 13 February)
• Re: [whatwg/url] Use Nontransitional_Processing for IDNA ToASCII (#240) (Monday, 13 February)
• Re: [whatwg/url] Consider always escaping U+0020 (#125) (Monday, 13 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Monday, 13 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Monday, 13 February)
• Re: [whatwg/xhr] Editorial: add an IDL index (#113) (Monday, 13 February)
• Re: [whatwg/xhr] Editorial: add an IDL index (#113) (Monday, 13 February)
• [w3c/ServiceWorker] useCache attribute design seems very very wrong (#1069) (Monday, 13 February)
• [heycam/webidl] Add an informative section on overloads vs. unions/optional (#307) (Sunday, 12 February)
• [whatwg/xhr] Editorial: add an IDL index (#113) (Sunday, 12 February)
• Re: [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Saturday, 11 February)
• [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Saturday, 11 February)
• Re: [whatwg/url] Editorial: use specific names for encode sets (#243) (Saturday, 11 February)
• Re: [whatwg/url] Editorial: use specific names for encode sets (#243) (Saturday, 11 February)
• Re: [whatwg/url] Editorial: use specific names for encode sets (#243) (Saturday, 11 February)
• Re: [whatwg/streams] "Set totalSize to totalSize + pair.[[size]]." (#582) (Friday, 10 February)
• Re: [whatwg/streams] factor out pipeTo into abstract op ReadableStreamPipeTo (#676) (Friday, 10 February)
• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Friday, 10 February)
• Re: [whatwg/url] Editorial: use specific names for encode sets (#243) (Friday, 10 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 10 February)
• Re: [whatwg/url] Make IPv6 addresses in special URLs valid (#238) (Friday, 10 February)
• Re: [whatwg/url] Paths need to be copied from base URLs (#244) (Friday, 10 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/url] Paths need to be copied from base URLs (#244) (Friday, 10 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Friday, 10 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 9 February)
• [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 9 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Thursday, 9 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 9 February)
• Re: [w3c/FileAPI] Stop using incumbent settings object (#67) (Thursday, 9 February)
• Re: [w3c/FileAPI] Stop using incumbent settings object (#67) (Thursday, 9 February)
• Re: [w3c/FileAPI] Stop using incumbent settings object (#67) (Thursday, 9 February)
• [w3c/FileAPI] Stop using incumbent settings object (#67) (Thursday, 9 February)
• Re: [whatwg/url] Editorial: use the Infra Standard for URL's path (#237) (Thursday, 9 February)
• Re: [whatwg/url] Editorial: use the Infra Standard for URL's path (#237) (Thursday, 9 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 9 February)
• Re: [whatwg/url] Repeated slashes should be ignored in file scheme (#234) (Wednesday, 8 February)
• Re: [whatwg/url] Repeated slashes should be ignored in file scheme (#234) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] IFrame support in web payments (#147) (Wednesday, 8 February)
• Re: [whatwg/url] Repeated slashes should be ignored in file scheme (#234) (Wednesday, 8 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 8 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Wednesday, 8 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Wednesday, 8 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Wednesday, 8 February)
• Re: [whatwg/url] Meta: state idempotence clearly as a goal (#226) (Wednesday, 8 February)
• Re: [heycam/webidl] Disambiguate / explain maplike vs record (#303) (Wednesday, 8 February)
• Re: [heycam/webidl] Disambiguate / explain maplike vs record (#303) (Wednesday, 8 February)
• Re: [heycam/webidl] Disambiguate / explain maplike vs record (#303) (Wednesday, 8 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Tuesday, 7 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Tuesday, 7 February)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 7 February)
• Re: [w3c/FileAPI] Stop using the "incumbent settings object" (#60) (Tuesday, 7 February)
• Re: [w3c/FileAPI] Stop using the "incumbent settings object" (#60) (Tuesday, 7 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Tuesday, 7 February)
• Re: [whatwg/url] Meta: state idempotence clearly as a goal (#226) (Tuesday, 7 February)
• Re: [whatwg/url] Editorial: move Windows drive letter to a more logical location (#227) (Tuesday, 7 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Tuesday, 7 February)
• [heycam/webidl] Clarify that exceptions are always thrown in the current Realm (#300) (Monday, 6 February)
• Re: [whatwg/streams] Export the "error the stream" concept? (#679) (Monday, 6 February)
• Re: [whatwg/streams] WebIDL syntax for parameterized streams? (#678) (Monday, 6 February)
• Re: [w3c/FileAPI] Stop using the "incumbent settings object" (#60) (Saturday, 4 February)
• [w3c/FileAPI] "origin of a blob URL" is redundant/confusing (#63) (Friday, 3 February)
• Re: [heycam/webidl] Allow extended attributes to apply to types (#286) (Friday, 3 February)
• Re: [heycam/webidl] Allow extended attributes to apply to types (#286) (Friday, 3 February)
• Re: [heycam/webidl] Environment stuff for exception throwing is nonsense (#292) (Friday, 3 February)
• Re: [heycam/webidl] Allow extended attributes to apply to types (#286) (Friday, 3 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Friday, 3 February)
• Re: [heycam/webidl] Environment stuff for exception throwing is nonsense (#292) (Friday, 3 February)
• Re: [whatwg/url] File state did not correctly deal with lack of base URL (#225) (Friday, 3 February)
• [whatwg/url] Setting path to base's path seems wrong (#231) (Friday, 3 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Friday, 3 February)
• Re: [heycam/webidl] Revamp interface bindings (#283) (Friday, 3 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Friday, 3 February)
• Re: [whatwg/fetch] Meta: update spec deploy and editing infrastructure (#478) (Thursday, 2 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Thursday, 2 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 2 February)
• Re: [heycam/webidl] Clarify [[Call]] + [[Construct]] for named (and possibly non-named) constructors (#278) (Thursday, 2 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Thursday, 2 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Thursday, 2 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Wednesday, 1 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Wednesday, 1 February)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 1 February)

Dominic Cooney

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Tuesday, 21 February)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 16 February)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Thursday, 16 February)

Dominique Hazael-Massieux

• Re: [w3ctag/spec-reviews] Media Capture From DOM Element (#130) (Friday, 10 February)

Eli Sadoff

• [whatwg/dom] "If options is a dictionary, then set capture to..." (#408) (Monday, 13 February)

François REMY

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)

Fuqiao Xue

• [heycam/webidl] Fix an example of serialization behavior (#302) (Tuesday, 7 February)

Gary Kacmarcik

• Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Tuesday, 21 February)
• Re: [w3c/clipboard-apis] Clarify the algorithm for setting target of a clipboard event in 7.2 Processing model for event dispatch (#29) (Friday, 17 February)
• Re: [w3c/clipboard-apis] Clarify the algorithm for setting target of a clipboard event in 7.2 Processing model for event dispatch (#29) (Friday, 17 February)
• Re: [w3c/clipboard-apis] Clarify the algorithm for setting target of a clipboard event in 7.2 Processing model for event dispatch (#29) (Friday, 17 February)
• Re: [w3c/clipboard-apis] How should focus be managed? (#26) (Friday, 17 February)
• Re: [w3c/editing] Behavior of queryCommandEnabled (#161) (Thursday, 16 February)
• Re: [w3c/editing] Behavior of queryCommandEnabled (#161) (Thursday, 16 February)
• Re: [w3c/editing] Behavior of queryCommandEnabled (#161) (Thursday, 16 February)
• Re: [w3c/clipboard-apis] Behavior of queryCommandEnabled (#7) (Thursday, 16 February)
• Re: [w3c/clipboard-apis] Behavior of queryCommandEnabled (#7) (Thursday, 16 February)
• [w3c/editing] Behavior of queryCommandEnabled (#161) (Thursday, 16 February)
• Re: [w3c/clipboard-apis] The ClipboardEvent constructor is strange (#10) (Thursday, 16 February)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Wednesday, 15 February)
• Re: [w3c/uievents-code] 'Key value' terminology is ambiguous and confusing (#14) (Thursday, 2 February)
• Re: [w3c/uievents-code] 'Key value' terminology is ambiguous and confusing (#14) (Thursday, 2 February)
• Re: [w3c/uievents-code] Printable control characters needs refinement (#15) (Wednesday, 1 February)
• Re: [w3c/uievents-code] Printable control characters needs refinement (#15) (Wednesday, 1 February)
• Re: [w3c/uievents-key] Example 33 cleanup (#41) (Wednesday, 1 February)
• Re: [w3c/uievents-key] Example 33 cleanup (#41) (Wednesday, 1 February)
• Re: [w3c/uievents-key] Are Shift or AltGr fallbacks sufficient? (#40) (Wednesday, 1 February)
• Re: [w3c/uievents-key] Request example for DomKey when Ctrl and CapsLock are both down (#39) (Wednesday, 1 February)

Geoffrey Sneddon

• Re: [whatwg/url] Explicitly list non-goals (#233) (Monday, 13 February)
• [whatwg/url] Explicitly list non-goals (#233) (Monday, 6 February)

gked

• [w3c/clipboard-apis] Add ipr functionality to the spec (#39) (Friday, 17 February)
• Re: [w3c/clipboard-apis] How do we address cross-origin selection/focus changes? (#38) (Thursday, 16 February)

guest271314

• Re: [whatwg/fetch] Reading FormData from Request(); setting correct MIME type (#480) (Saturday, 4 February)
• [whatwg/fetch] Reading `FormData` from `Request()`; setting correct `MIME` type (#480) (Friday, 3 February)

Hadley Beeman

• Re: [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Data on the Web Best Practices (#135) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Data on the Web Best Practices (#135) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] WebRTC Stats review (#148) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] TV-Specific Web Subsetting (#105) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] WASM JS API review (#151) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Security Questionnaire (#77) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Security Questionnaire (#77) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Privacy Mode (#101) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Performance API's, Security and Privacy (#120) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Review origin policy. (#127) (Wednesday, 8 February)

Hayato Ito

• Re: [w3c/webcomponents] Shadow dom innerhtml and CSP unsafe-inline (#627) (Friday, 24 February)
• Re: [w3c/webcomponents] Shadow DOM Example 1 without slot attribute applied, select by class (#626) (Wednesday, 22 February)
• Re: [w3c/webcomponents] Shadow DOM Example 1 without slot attribute applied, select by class (#626) (Wednesday, 22 February)
• Re: [w3c/webcomponents] Shadow DOM Example 1 without slot attribute applied, select by class (#626) (Friday, 17 February)
• Re: [w3c/webcomponents] Fix a few typos (#625) (Monday, 13 February)

Hemant Singh

• Re: [whatwg/dom] Consider adding localNameFilter to MutationObserver (#398) (Saturday, 25 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Saturday, 25 February)

Ian Hickson

• Re: [whatwg/url] All the other network schemes (#241) (Friday, 10 February)

Ian Kilpatrick

• Re: [w3ctag/spec-reviews] Custom Paint API to CR (#140) (Wednesday, 22 February)

ianbjacobs

• [w3ctag/spec-reviews] Web Payments Working Group Specifications (#152) (Wednesday, 15 February)

Ilya Grigorik

• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Monday, 27 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Saturday, 25 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Saturday, 25 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Friday, 24 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Friday, 24 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Friday, 24 February)
• Re: [w3ctag/spec-reviews] Performance API's, Security and Privacy (#120) (Saturday, 11 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Saturday, 11 February)
• Re: [w3ctag/spec-reviews] Performance API's, Security and Privacy (#120) (Wednesday, 8 February)

Isiah Meadows

• Re: [whatwg/dom] Consider adding Promise-based API for listerning event (#333) (Thursday, 2 February)
• Re: [whatwg/dom] Consider adding Promise-based API for listerning event (#333) (Wednesday, 1 February)
• Re: [whatwg/dom] Consider adding Promise-based API for listerning event (#333) (Wednesday, 1 February)

Islam Sharabash

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)

Jake Archibald

• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Saturday, 25 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Friday, 24 February)
• Re: [w3c/ServiceWorker] Introduce Try Clear Registration; Delay activation (#1079) (Friday, 24 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Friday, 24 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Wednesday, 22 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Tuesday, 21 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Tuesday, 21 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Service worker ID - remove? (#1076) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Sunday, 19 February)
• [w3c/ServiceWorker] Service worker ID - remove? (#1076) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Thursday, 16 February)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Tuesday, 14 February)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Tuesday, 14 February)
• Re: [whatwg/fetch] Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 14 February)
• Re: [whatwg/fetch] Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 14 February)
• Re: [whatwg/fetch] Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 14 February)
• Re: [whatwg/fetch] Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 14 February)
• Re: [whatwg/fetch] Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 14 February)
• Re: [whatwg/fetch] Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 14 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Tuesday, 14 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Tuesday, 14 February)
• Re: [w3c/ServiceWorker] useCache attribute design seems very very wrong (#1069) (Monday, 13 February)
• Re: [w3c/ServiceWorker] Correcting usecache attribute. Fixes #1069 (#1070) (Monday, 13 February)
• Re: [w3c/ServiceWorker] Correcting usecache attribute. Fixes #1069 (#1070) (Monday, 13 February)
• Re: [w3c/ServiceWorker] useCache attribute design seems very very wrong (#1069) (Monday, 13 February)
• [w3c/ServiceWorker] Correcting usecache attribute. Fixes #1069 (#1070) (Monday, 13 February)
• Re: [w3c/ServiceWorker] useCache attribute design seems very very wrong (#1069) (Monday, 13 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Friday, 10 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Friday, 10 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Friday, 10 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Thursday, 9 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Thursday, 9 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Support returning ServiceWorker Client environments from `Clients.matchAll()` (#1036) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Tuesday, 7 February)
• Re: [w3c/ServiceWorker] Pagination in cache.keys() (#1066) (Friday, 3 February)

James M Snell

• Re: [whatwg/url] Use Nontransitional_Processing for IDNA ToASCII (#240) (Thursday, 9 February)
• Re: [whatwg/url] IDNA Nontransitional_Processing (#239) (Thursday, 9 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 2 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Thursday, 2 February)
• Re: [whatwg/url] Meta: state idempotence clearly as a goal (#226) (Thursday, 2 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Wednesday, 1 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Wednesday, 1 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 1 February)
• Re: [whatwg/url] Cleanup API for file and non-special URLs (#224) (Wednesday, 1 February)

Jan Potoms

• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Tuesday, 14 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Monday, 13 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Wednesday, 1 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Wednesday, 1 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Wednesday, 1 February)

jan-ivar

• Re: [w3c/permissions] Define restrictions on "device-info" permission (from TPAC). (#131) (Tuesday, 14 February)

Jeffrey Posnick

• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)

Jeffrey Yasskin

• Re: [heycam/webidl] Base sequences, dictionaries, and records on Infra types (#317) (Wednesday, 22 February)
• Re: [heycam/webidl] Base sequences, dictionaries, and records on Infra types (#317) (Wednesday, 22 February)
• Re: [w3c/permissions] May reorder the permission state read steps (#137) (Wednesday, 8 February)
• [heycam/webidl] Ban nullable records in dictionary members and operation arguments. (#299) (Friday, 3 February)
• [heycam/webidl] Fix #296: ban dictionary recursion through records. (#298) (Friday, 3 February)
• Re: [heycam/webidl] Where does it say that a nullable record<> cannot be the type of a dictionary member? (#295) (Friday, 3 February)
• Re: [heycam/webidl] Where does it say that a nullable record<> cannot be the type of a dictionary member? (#295) (Friday, 3 February)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Friday, 3 February)

jeisinger

• [w3c/IndexedDB] specify what should happen if the origin of execution context is opaque (#148) (Tuesday, 14 February)

jgraham

• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Monday, 6 February)

Jimmy Karl Roland Wärting

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

Jordan Harband

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)

Josef Jezek

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

Joseph Orbegoso Pea

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

Joseph Pecoraro

• [whatwg/fetch] ABNF Notation Reference (#489) (Tuesday, 14 February)

Joshua Bell

• Re: [w3c/IndexedDB] simplify algorithm names (#160) (Tuesday, 28 February)
• Re: [w3c/IndexedDB] Indicate 2.0 feature support in Chrome/Firefox/Safari (#157) (Tuesday, 28 February)
• Re: [w3c/IndexedDB] Make algorithm names more succinct and consistent (#158) (Tuesday, 28 February)
• [w3c/IndexedDB] simplify algorithm names (#160) (Saturday, 25 February)
• [w3c/IndexedDB] Add caniuse panels (#159) (Friday, 24 February)
• [w3c/IndexedDB] Make algorithm names more succinct and consistent (#158) (Friday, 24 February)
• Re: [w3c/IndexedDB] Security: Add note about UAs needing to handle version skew (#139) (Friday, 24 February)
• [w3c/IndexedDB] Indicate 2.0 feature support in Chrome/Firefox/Safari (#157) (Friday, 24 February)
• [w3c/IndexedDB] Add Security note about persistence/version skew (#156) (Friday, 24 February)
• Re: [w3c/IndexedDB] Non-normative note about what an upgrade transaction is normally used for (#154) (Friday, 24 February)
• Re: [w3c/IndexedDB] Clarify purpose and lifetime of upgrade transactions (#155) (Friday, 24 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Thursday, 23 February)
• Re: [whatwg/storage] Disable the API in opaque origins (#43) (Thursday, 23 February)
• Re: [w3c/IndexedDB] Key generator behavior with explicit keys above 2^53 (#147) (Thursday, 23 February)
• [w3c/IndexedDB] Clarify purpose and lifetime of upgrade transactions (#155) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] Non-normative note about what an upgrade transaction is normally used for (#154) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] Rework key generator algorithm (#153) (Wednesday, 22 February)
• Re: [whatwg/storage] API exposure/behavior for unique origins? (#41) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] Rework key generator algorithm (#153) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] Rework key generator algorithm (#153) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] Implement transaction cleanup hook for [HTML] (#145) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] Implement transaction cleanup hook for [HTML] (#145) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] Key generator behavior with explicit keys above 2^53 (#147) (Wednesday, 22 February)
• Re: [w3c/IndexedDB] Rework key generator algorithm (#153) (Wednesday, 22 February)
• [w3c/IndexedDB] Rework key generator algorithm (#153) (Wednesday, 22 February)
• Re: [w3ctag/spec-reviews] IndexedDB 2.0 features review (#153) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Sunday, 19 February)
• Re: [w3c/IndexedDB] Fixes for 'steps for storing' (#146) (Friday, 17 February)
• Re: [w3c/IndexedDB] Implement transaction cleanup hook for [HTML] (#145) (Friday, 17 February)
• Re: [w3c/IndexedDB] specify what should happen if the origin of execution context is opaque (#148) (Friday, 17 February)
• Re: [whatwg/storage] API exposure/behavior for unique origins? (#41) (Friday, 17 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Friday, 17 February)
• Re: [w3c/IndexedDB] open/deleteDatabase should throw on opaque origin (#150) (Friday, 17 February)
• Re: [w3c/IndexedDB] open/deleteDatabase should throw on opaque origin (#150) (Friday, 17 February)
• Re: [w3c/IndexedDB] open/deleteDatabase should throw on opaque origin (#150) (Friday, 17 February)
• Re: [whatwg/storage] API exposure/behavior for unique origins? (#41) (Wednesday, 15 February)
• Re: [w3c/IndexedDB] Editorial: remove repeated word (#151) (Wednesday, 15 February)
• Re: [w3c/IndexedDB] Editorial: remove repeated word (#151) (Wednesday, 15 February)
• Re: [w3c/IndexedDB] Fixes for 'steps for storing' (#146) (Wednesday, 15 February)
• Re: [w3c/IndexedDB] Fixes for 'steps for storing' (#146) (Wednesday, 15 February)
• Re: [w3c/IndexedDB] open/deleteDatabase should throw on opaque origin (#150) (Wednesday, 15 February)
• Re: [w3c/IndexedDB] open/deleteDatabase should throw on opaque origin (#150) (Tuesday, 14 February)
• [w3c/IndexedDB] open/deleteDatabase should throw on opaque origin (#150) (Tuesday, 14 February)
• Re: [w3c/IndexedDB] specify what should happen if the origin of execution context is opaque (#148) (Tuesday, 14 February)
• Re: [whatwg/dom] Add legacyOutputDidListenersThrowFlag to event dispatch for IDB (#409) (Tuesday, 14 February)
• [w3c/IndexedDB] Use proposed DOM hook for exceptions thrown during dispatch (#149) (Tuesday, 14 February)
• Re: [w3c/IndexedDB] Implement transaction cleanup hook for [HTML] (#145) (Tuesday, 14 February)
• [whatwg/storage] API exposure/behavior for unique origins? (#41) (Tuesday, 14 February)
• Re: [whatwg/dom] Add legacyOutputDidListenersThrowFlag to event dispatch for IDB (#409) (Tuesday, 14 February)
• Re: [w3c/IndexedDB] Implement transaction cleanup hook for [HTML] (#145) (Tuesday, 14 February)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Tuesday, 14 February)
• Re: [w3c/IndexedDB] Fixes for 'steps for storing' (#146) (Tuesday, 14 February)
• Re: [w3c/IndexedDB] "If an exception was propagated out from any event handler" is not a thing (#140) (Monday, 13 February)
• [w3c/IndexedDB] Key generator behavior with explicit keys above 2^53 (#147) (Monday, 13 February)
• [w3c/IndexedDB] Fixes for 'steps for storing' (#146) (Monday, 13 February)
• Re: [w3c/IndexedDB] Simplify "steps for storing a record into an object store"? (#144) (Monday, 13 February)
• [w3c/IndexedDB] Implement transaction cleanup hook for [HTML] (#145) (Monday, 13 February)
• Re: [w3c/IndexedDB] Simplify "steps for storing a record into an object store"? (#144) (Monday, 13 February)
• Re: [w3c/IndexedDB] Security: Add note about UAs needing to handle version skew (#139) (Thursday, 9 February)
• Re: [whatwg/encoding] " push a copy of input " (#92) (Thursday, 9 February)
• Re: [whatwg/encoding] " push a copy of input " (#92) (Thursday, 9 February)
• Re: [w3c/IndexedDB] Security and Web Worker access for IndexedDB (#141) (Tuesday, 7 February)
• Re: [w3c/IndexedDB] Step for multientry key conversion are mis-indented (#142) (Monday, 6 February)
• Re: [w3c/IndexedDB] Fix markdown indentation to repair algorithm. Resolves #142 (#143) (Monday, 6 February)
• Re: [w3c/IndexedDB] Fix markdown indentation to repair algorithm. Resolves #142 (#143) (Monday, 6 February)
• [w3c/IndexedDB] Fix markdown indentation to repair algorithm. Resolves #142 (#143) (Monday, 6 February)
• [w3c/IndexedDB] Step for multientry key conversion are mis-indented (#142) (Monday, 6 February)
• Re: [whatwg/encoding] "decoder = TextDecoder(encoding)" (#90) (Monday, 6 February)
• Re: [w3c/FileAPI] Please set the repository's URL to https://w3c.github.io/FileAPI/ (#64) (Sunday, 5 February)

Joyee Cheung

• Re: [whatwg/url] Should URL constructors prepend ? when initializing query objects? (#248) (Tuesday, 14 February)
• Re: [whatwg/url] Should URL constructors prepend ? when initializing query objects? (#248) (Tuesday, 14 February)
• [whatwg/url] Should URL constructors prepend ? when initializing query objects? (#248) (Tuesday, 14 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Wednesday, 8 February)

JP Sugarbroad

• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)

Jungkee Song

• Re: [w3c/ServiceWorker] Update to reference HTML for link rel=serviceworker (#1073) (Monday, 27 February)
• Re: [w3c/ServiceWorker] Introduce Try Clear Registration; Delay activation (#1079) (Saturday, 25 February)
• Re: [w3c/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Saturday, 25 February)
• Re: [w3c/ServiceWorker] Introduce Try Clear Registration; Delay activation (#1079) (Saturday, 25 February)
• Re: [w3c/ServiceWorker] Introduce Try Clear Registration; Delay activation (#1079) (Saturday, 25 February)
• Re: [w3c/ServiceWorker] Introduce Try Clear Registration; Delay activation (#1079) (Saturday, 25 February)
• Re: [w3c/ServiceWorker] clarify that Client "creation order" means when reserved Client created (#1078) (Saturday, 25 February)
• Re: [w3c/ServiceWorker] clarify that Client "creation order" means when reserved Client created (#1078) (Friday, 24 February)
• Re: [w3c/ServiceWorker] Introduce Try Clear Registration; Delay activation (#1079) (Thursday, 23 February)
• Re: [w3c/ServiceWorker] Introduce Try Clear Registration; Delay activation (#1079) (Thursday, 23 February)
• [w3c/ServiceWorker] Introduce Try Clear Registration; Delay activation (#1079) (Thursday, 23 February)
• Re: [w3c/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Use DOMStringList for ancestorOrigins (#1052) (Thursday, 16 February)
• [w3c/ServiceWorker] Track ancestorOrigins privacy issues (#1075) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Use DOMStringList for ancestorOrigins (#1052) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] "ancestor origins array" is going away (#1051) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Use DOMStringList for ancestorOrigins (#1052) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Use DOMStringList for ancestorOrigins (#1052) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Add Client type for ServiceWorkerGlobalScope environments (#1074) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Add Client type for ServiceWorkerGlobalScope environments (#1074) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Add Client type for ServiceWorkerGlobalScope environments (#1074) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Add Client type for ServiceWorkerGlobalScope environments (#1074) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Add Client type for ServiceWorkerGlobalScope environments (#1074) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Add Client type for ServiceWorkerGlobalScope environments (#1074) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Add Client type for ServiceWorkerGlobalScope environments (#1074) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Add Client type for ServiceWorkerGlobalScope environments (#1074) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] `Clients.matchAll()` should exclude the current environment (#1037) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Support returning ServiceWorker Client environments from `Clients.matchAll()` (#1036) (Thursday, 16 February)
• Re: [w3c/ServiceWorker] Handling duplicate importScripts() (#1041) (Wednesday, 15 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Wednesday, 15 February)
• Re: [w3c/ServiceWorker] Add specific Processing headings + minor editorial (#1071) (Tuesday, 14 February)
• Re: [w3c/ServiceWorker] Add specific Processing headings + minor editorial (#1071) (Tuesday, 14 February)
• Re: [w3c/ServiceWorker] Add specific Processing headings + minor editorial (#1071) (Tuesday, 14 February)
• Re: [w3c/ServiceWorker] useCache attribute design seems very very wrong (#1069) (Monday, 13 February)
• Re: [w3c/ServiceWorker] Correcting usecache attribute. Fixes #1069 (#1070) (Monday, 13 February)
• Re: [w3c/ServiceWorker] Correcting usecache attribute. Fixes #1069 (#1070) (Monday, 13 February)
• Re: [w3c/ServiceWorker] Add check for CORS-safelisted methods and headers to foreign fetch. (#1067) (Monday, 13 February)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Friday, 10 February)
• Re: [w3c/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Thursday, 9 February)
• Re: [w3c/ServiceWorker] Drop isReload (#873) (Thursday, 9 February)
• Re: [w3c/ServiceWorker] Drop isReload (#873) (Thursday, 9 February)
• Re: [w3c/ServiceWorker] Drop isReload (#873) (Thursday, 9 February)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Thursday, 9 February)
• Re: [whatwg/fetch] Add 'target browsing context' to requests. (#466) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Wednesday, 8 February)
• Re: [whatwg/fetch] Add 'target browsing context' to requests. (#466) (Tuesday, 7 February)
• Re: [w3c/ServiceWorker] Content-Type requirement of service worker importScripts() (#1032) (Monday, 6 February)
• Re: [w3c/ServiceWorker] Content-Type requirement of service worker importScripts() (#1032) (Monday, 6 February)
• Re: [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Friday, 3 February)
• [w3c/ServiceWorker] Improve Activate with Try Activate (#1065) (Friday, 3 February)

Justin

• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Friday, 3 February)

Justin Fagnani

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

jvanbec

• Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Sunday, 19 February)
• Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Sunday, 19 February)
• Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Sunday, 19 February)

Jxck

• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 14 February)

K3N

• Re: [w3c/FileAPI] Rename Blob URL to Object URL (#65) (Wednesday, 8 February)
• Re: [w3c/FileAPI] Rename Blob URL to Object URL (#65) (Wednesday, 8 February)
• [w3c/FileAPI] Rename Blob URL to Object URL (#65) (Monday, 6 February)

Keith Yeung

• Re: [whatwg/xhr] Clarify when subsubsubsteps run in "process response" (#122) (Friday, 24 February)
• Re: [whatwg/xhr] Ensure progress events fired from "process response" always have a valid loaded value (#118) (Wednesday, 22 February)
• Re: [whatwg/xhr] Ensure progress events fired from "process response" always have a valid loaded value (#118) (Tuesday, 21 February)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Monday, 20 February)
• [whatwg/xhr] Ensure progress events fired from "process response" always have a valid loaded value (#118) (Monday, 20 February)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Saturday, 18 February)
• [whatwg/xhr] "To handle response end-of-body for response, ru..." (#116) (Saturday, 18 February)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] Icon shapes and masking (#555) (Thursday, 16 February)
• Re: [w3c/manifest] Icon shapes and masking (#555) (Thursday, 16 February)
• Re: [w3c/manifest] Icon shapes and masking (#555) (Thursday, 16 February)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Monday, 13 February)
• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Thursday, 9 February)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Thursday, 9 February)
• Re: [w3c/manifest] scope="../" should be invalid (#551) (Thursday, 9 February)
• Re: [w3c/manifest] style: less resistance (737c006) (Wednesday, 8 February)
• Re: [w3c/manifest] style: less resistance (737c006) (Wednesday, 8 February)
• Re: [w3c/manifest] scope="../" should be invalid (#551) (Wednesday, 8 February)
• Re: [w3c/manifest] scope="../" should be invalid (#551) (Wednesday, 8 February)
• [w3c/manifest] Make start_url relative to scope and not manifest location (#552) (Wednesday, 8 February)
• Re: [w3c/manifest] scope="../" should be invalid (#551) (Wednesday, 8 February)
• Re: [w3c/manifest] scope="../" should be invalid (#551) (Wednesday, 8 February)
• Re: [w3c/manifest] scope="../" should be invalid (#551) (Monday, 6 February)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Monday, 6 February)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Monday, 6 February)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Monday, 6 February)
• [w3c/manifest] Make unbounded navigation scope less broad (#550) (Monday, 6 February)
• [w3c/manifest] unbounded check in navigation should check origin (#549) (Monday, 6 February)

Kinuko Yasuda

• Re: [w3c/ServiceWorker] Create F2F agenda - 3-4 April 2017 (#1053) (Friday, 10 February)

Kit Cambridge

• Re: [w3c/push-api] push-register (pushregistrationlost / pushsubscriptionchange) behavior when clearing browser cache (#61) (Wednesday, 22 February)

L. David Baron

• Re: [w3ctag/spec-reviews] MediaStream Recorder (#131) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] ImageBitmapRenderingContext (part of offscreen canvas) (#141) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Review OffscreenCanvas (#144) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Review OffscreenCanvas (#144) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Review request for Scroll Anchoring (#142) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Review OffscreenCanvas (#144) (Wednesday, 8 February)

Larry Masinter

• Re: [whatwg/url] Goal: Getting a fixed document release (#222) (Sunday, 12 February)

lcchueri

• Re: [w3c/webcomponents] Shadow DOM Example 1 without slot attribute applied, select by class (#626) (Friday, 17 February)
• [w3c/webcomponents] Shadow DOM Example 1 whithout slot attribute applied, select by class (#626) (Tuesday, 14 February)

Lea Verou

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Thursday, 16 February)
• [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Thursday, 16 February)

Lukasz Olejnik

• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Wednesday, 22 February)

Luna Lu

• Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34) (Thursday, 16 February)
• Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34) (Wednesday, 15 February)
• Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34) (Wednesday, 15 February)

Léonie Watson

• Re: [w3c/IndexedDB] Horizontal review… (#112) (Monday, 13 February)
• Re: [w3c/IndexedDB] Horizontal review… (#112) (Monday, 13 February)

Maciej Stachowiak

• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Saturday, 11 February)

Mahmoud Hashemi

• Re: [whatwg/url] Document, possibly standardize, "plus" scheme convention (#230) (Thursday, 9 February)
• Re: [whatwg/url] Document, possibly standardize, "plus" scheme convention (#230) (Thursday, 9 February)
• Re: [whatwg/url] Document, possibly standardize, "plus" scheme convention (#230) (Friday, 3 February)
• Re: [whatwg/url] Document, possibly standardize, "plus" scheme convention (#230) (Friday, 3 February)
• Re: [whatwg/url] Document, possibly standardize, "plus" scheme convention (#230) (Friday, 3 February)
• [whatwg/url] Document, possibly standardize, "plus" scheme convention (#230) (Friday, 3 February)

Majid Valipour

• Re: [whatwg/dom] High resolution timing for events (#23) (Tuesday, 28 February)

Marcos Cáceres

• Re: [heycam/webidl] Scroll script causes jank (#314) (Tuesday, 21 February)
• Re: [heycam/webidl] Scroll script causes jank (#314) (Tuesday, 21 February)
• Re: [heycam/webidl] Code-points, code-units, characters, oh my! (#312) (Tuesday, 21 February)
• Re: [heycam/webidl] Code-points, code-units, characters, oh my! (#312) (Monday, 20 February)
• [heycam/webidl] Code-points, code-units, characters, oh my! (#312) (Monday, 20 February)
• Re: [w3c/manifest] Icon shapes and masking (#555) (Thursday, 16 February)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Monday, 13 February)
• Re: [w3c/manifest] Should the scope terminate by "/"? (#554) (Monday, 13 February)
• [whatwg/url] Provide means to "strip query" (#247) (Monday, 13 February)
• Re: [w3c/manifest] Simple Example and Complex Example (#553) (Friday, 10 February)
• Re: [w3ctag/spec-reviews] Review Accessibility Object Model (#134) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Wednesday, 8 February)

Marijn Kruisselbrink

• Re: [w3c/FileAPI] Update feedback info (#49) (Thursday, 16 February)
• Re: [w3c/FileAPI] Update feedback info (#69) (Thursday, 16 February)
• Re: [whatwg/storage] API exposure/behavior for unique origins? (#41) (Tuesday, 14 February)
• Re: [w3c/ServiceWorker] Add specific Processing headings + minor editorial (#1071) (Tuesday, 14 February)
• Re: [w3c/ServiceWorker] Add check for CORS-safelisted methods and headers to foreign fetch. (#1067) (Monday, 13 February)
• Re: [w3c/ServiceWorker] Add check for CORS-safelisted methods and headers to foreign fetch. (#1067) (Monday, 13 February)
• Re: [w3c/FileAPI] Constructing a new blob from a closed blob (#17) (Friday, 10 February)
• Re: [w3c/FileAPI] Cloning a Blob and then close the original one, does it change the state of the cloned one? (#18) (Friday, 10 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Friday, 10 February)
• Re: [w3c/FileAPI] Blob.close() has several problems (#10) (Friday, 10 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Thursday, 9 February)
• [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Thursday, 9 February)
• Re: [w3c/FileAPI] Stop using incumbent settings object (#67) (Thursday, 9 February)
• Re: [w3c/FileAPI] Stop using incumbent settings object (#67) (Thursday, 9 February)
• Re: [w3c/FileAPI] Stop using the "incumbent settings object" (#60) (Thursday, 9 February)
• Re: [w3c/FileAPI] Stop using incumbent settings object (#67) (Thursday, 9 February)
• Re: [w3c/FileAPI] Stop using incumbent settings object (#67) (Thursday, 9 February)
• Re: [w3c/FileAPI] Stop using incumbent settings object (#67) (Thursday, 9 February)
• Re: [w3c/FileAPI] Rename Blob URL to Object URL (#65) (Tuesday, 7 February)
• Re: [w3c/FileAPI] What should the ProgressEvent attributes be in the case of an error/abort? (#14) (Tuesday, 7 February)
• [w3c/FileAPI] Set FileReader.error to an AbortError when abort() is called. (#66) (Monday, 6 February)
• Re: [w3c/FileAPI] Stop using the "incumbent settings object" (#60) (Monday, 6 February)
• Re: [w3c/FileAPI] Use Encoding's "UTF-8 encode" hook (#37) (Saturday, 4 February)
• Re: [w3c/FileAPI] "origin of a blob URL" is redundant/confusing (#63) (Friday, 3 February)
• Re: [w3c/FileAPI] Not expose FileReaderSync to service worker (#16) (Friday, 3 February)
• Re: [w3c/FileAPI] What should the ProgressEvent attributes be in the case of an error/abort? (#14) (Friday, 3 February)
• Re: [w3c/FileAPI] Don't use [EnsureUTF16] (gone from Web IDL) (#9) (Friday, 3 February)
• Re: [w3c/FileAPI] "Unicode Serialization of a Blob URL" algorithm makes no sense (#59) (Friday, 3 February)
• Re: [w3c/FileAPI] Use ASCII origin in blob URLs (#7) (Friday, 3 February)
• Re: [w3c/FileAPI] Fix several issues with the "Serialization of a Blob URL" algorithm. (#61) (Friday, 3 February)
• Re: [w3c/FileAPI] Use HTML's definition of "Unicode serialization of an origin" (#58) (Friday, 3 February)
• Re: [w3c/ServiceWorker] Add check for CORS-safelisted methods and headers to foreign fetch. (#1067) (Friday, 3 February)
• [w3c/ServiceWorker] Add check for CORS-safelisted methods and headers to foreign fetch. (#1067) (Friday, 3 February)
• Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Friday, 3 February)
• Re: [w3c/FileAPI] Blob.close() has several problems (#10) (Wednesday, 1 February)
• Re: [w3c/FileAPI] Remove createFor() (#57) (Wednesday, 1 February)
• Re: [w3c/FileAPI] Remove the URL.createFor method. (#62) (Wednesday, 1 February)
• Re: [w3c/FileAPI] Remove the URL.createFor method. (#62) (Wednesday, 1 February)

maritza1979

• Re: [heycam/webidl] Allow extended attributes to apply to types (#286) (Tuesday, 7 February)

Mark Nottingham

• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Tuesday, 28 February)
• Re: [whatwg/fetch] Vary HTTP cache on credentials mode (#307) (Tuesday, 28 February)
• Re: [whatwg/fetch] Vary HTTP cache on credentials mode (#307) (Tuesday, 28 February)
• Re: [whatwg/fetch] Vary HTTP cache on credentials mode (#307) (Tuesday, 28 February)
• Re: [whatwg/fetch] Vary HTTP cache on credentials mode (#307) (Tuesday, 28 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Monday, 27 February)
• Re: [whatwg/fetch] Go deeper into HTTP caching (#373) (Monday, 27 February)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Monday, 27 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Monday, 27 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Monday, 27 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Friday, 24 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Friday, 24 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Friday, 24 February)
• Re: [whatwg/fetch] Streams based uploading with Content-Length (not chunked encoding) (#95) (Tuesday, 21 February)
• Re: [w3ctag/spec-reviews] Review origin policy. (#127) (Monday, 13 February)
• Re: [whatwg/url] Document, possibly standardize, "plus" scheme convention (#230) (Friday, 3 February)

Mark Roberts

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)

Martin Thomson

• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Monday, 27 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Monday, 27 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Monday, 27 February)
• Re: [w3c/push-api] Restructure the `push` event (#237) (Tuesday, 21 February)
• Re: [w3c/push-api] Restructure the `push` event (#237) (Tuesday, 21 February)
• Re: [w3c/push-api] Connectivity is not required to unsubscribe a subscription (#238) (Monday, 20 February)
• Re: [w3c/push-api] Connectivity is not required to unsubscribe a subscription (#238) (Monday, 20 February)
• Re: [w3c/push-api] Propose enabling background sync from `pushsubscriptionchange` events (#240) (Friday, 17 February)
• Re: [w3c/push-api] Interaction with SOP (#211) (Friday, 17 February)
• Re: [w3c/push-api] Clarify that push messages can come from anywhere (#239) (Friday, 17 February)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] Handling duplicate importScripts() (#1041) (Wednesday, 15 February)
• Re: [w3c/ServiceWorker] Drop isReload (#873) (Thursday, 9 February)

Matthew Krebs

• Re: [w3c/ServiceWorker] Introduce Try Clear Registration; Delay activation (#1079) (Tuesday, 28 February)

Matthew Phillips

• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Monday, 13 February)
• Re: [w3c/webcomponents] Support renaming, aliasing, or namespacing imported elements (#344) (Monday, 13 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Friday, 10 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Friday, 10 February)

Matthew Robb

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

Michael[tm] Smith

• Re: [w3c/ServiceWorker] Update to reference HTML for link rel=serviceworker (#1073) (Monday, 27 February)
• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Monday, 27 February)
• [whatwg/url] Editorial: Minor formatting tweak (#255) (Friday, 17 February)
• Re: [w3c/ServiceWorker] A header-based SW installation (#685) (Tuesday, 14 February)
• Re: [w3c/ServiceWorker] Add specific Processing headings + minor editorial (#1071) (Tuesday, 14 February)
• [w3c/ServiceWorker] Add specific Processing headings + minor editorial (#1071) (Tuesday, 14 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Thursday, 9 February)
• [whatwg/fetch] Fix typo particpating->participating (#477) (Wednesday, 1 February)

Mike Taylor

• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Monday, 27 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Saturday, 25 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Saturday, 25 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 24 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 24 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 24 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 21 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 21 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 21 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Monday, 13 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 10 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 10 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 10 February)
• Re: [whatwg/dom] Add event.srcElement as a legacy alias to event.target (#407) (Thursday, 9 February)
• [whatwg/dom] Add event.srcElement as a legacy alias to event.target (#407) (Thursday, 9 February)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Thursday, 9 February)

Mike West

• Re: [whatwg/fetch] Breaking: redo value parsing as value extraction (#494) (Wednesday, 22 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Friday, 17 February)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Friday, 17 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Friday, 17 February)
• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Wednesday, 15 February)
• [whatwg/dom] Consider removing `document.origin` (#410) (Wednesday, 15 February)
• Re: [whatwg/fetch] should CSP be checked on each redirect? (#485) (Thursday, 9 February)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Thursday, 9 February)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Review origin policy. (#127) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Wednesday, 8 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Wednesday, 8 February)
• Re: [whatwg/fetch] Add 'target browsing context' to requests. (#466) (Wednesday, 8 February)
• Re: [whatwg/fetch] Add 'target browsing context' to requests. (#466) (Wednesday, 8 February)
• Re: [whatwg/fetch] Add several ports to the "bad ports" list. (#482) (Tuesday, 7 February)
• Re: [whatwg/fetch] Add several ports to the "bad ports" list. (#482) (Tuesday, 7 February)
• Re: [whatwg/fetch] Add 'target browsing context' to requests. (#466) (Tuesday, 7 February)
• Re: [whatwg/fetch] Add several ports to the "bad ports" list. (#482) (Tuesday, 7 February)
• [whatwg/fetch] Add several ports to the "bad ports" list. (#482) (Tuesday, 7 February)
• Re: [w3c/ServiceWorker] Content-Type requirement of service worker importScripts() (#1032) (Monday, 6 February)

Mircea Trofin

• Re: [w3c/IndexedDB] Security: Add note about UAs needing to handle version skew (#139) (Wednesday, 1 February)

Ms2ger

• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 1 February)
• Re: [w3c/FileAPI] Stop using the "incumbent settings object" (#60) (Wednesday, 1 February)
• Re: [w3c/FileAPI] Remove createFor() (#57) (Wednesday, 1 February)

Nathan Schloss

• Re: [whatwg/fetch] Expose PerformanceResourceTiming in Response Objects (#491) (Tuesday, 21 February)
• Re: [whatwg/fetch] Expose PerformanceResourceTiming in Response Objects (#491) (Tuesday, 21 February)
• Re: [whatwg/fetch] Allow service-workers mode to be set in fetch options (#492) (Tuesday, 21 February)
• [w3c/ServiceWorker] Find a way for service workers to get their current state (#1077) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Service worker ID - remove? (#1076) (Tuesday, 21 February)
• [whatwg/fetch] Allow service-workers mode to be set in fetch options (#492) (Friday, 17 February)
• [whatwg/fetch] Expose PerformanceResourceTiming in Response Objects (#491) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Service worker ID - remove? (#1076) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Service worker ID - remove? (#1076) (Friday, 17 February)

nazizajka

• [whatwg/fullscreen] https://content.jwplatform.com/libraries/LJpSz0C8.js (#76) (Saturday, 11 February)

Nigel Megitt

• Re: [w3ctag/spec-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Thursday, 9 February)

nilssolanki

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Friday, 17 February)

Nora Lorinda Nattress

• Re: [whatwg/url] Merge pull request #1 from whatwg/master (#211) (Wednesday, 1 February)

Ole Ersoy

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 23 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 23 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 23 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 22 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 20 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 20 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 20 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 20 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 20 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 20 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 19 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 19 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 19 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 19 February)

OvermindDL1

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

Owen Campbell-Moore

• [w3c/manifest] Icon shapes and masking (#555) (Wednesday, 15 February)

Patrick Dark

• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• Re: [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)
• [whatwg/dom] Event Listener Execution Order for Same Event Is Undefined (#415) (Thursday, 23 February)

patrick kettner

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 21 February)

Patrick McManus

• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Tuesday, 7 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Tuesday, 7 February)

Paul Kinlan

• Re: [w3c/manifest] scope="../" should be invalid (#551) (Wednesday, 8 February)

PauloLeca

• [heycam/webidl] short-svg (#322) (Saturday, 25 February)
• Re: [heycam/webidl] short-svg (#322) (Saturday, 25 February)

Pete Otaqui

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

Peter Beverloo

• Re: [w3c/push-api] Connectivity is not required to unsubscribe a subscription (#238) (Friday, 24 February)
• [w3c/push-api] Enable auto publishing of Push API drafts (#241) (Friday, 17 February)
• Re: [w3c/push-api] PushSubscription should have an attribute for ExpirationTime (#86) (Friday, 17 February)
• Re: [w3c/push-api] Describe process for subscription updates (#132) (Friday, 17 February)
• Re: [w3c/push-api] Describe process for subscription updates (#132) (Friday, 17 February)
• [w3c/push-api] Propose enabling background sync from `pushsubscriptionchange` events (#240) (Friday, 17 February)
• [w3c/push-api] Clarify that push messages can come from anywhere (#239) (Friday, 17 February)
• Re: [w3c/push-api] Fire pushsubscriptionchange when user revokes permission (#116) (Friday, 17 February)
• Re: [w3c/push-api] Fire pushsubscriptionchange when user revokes permission (#116) (Friday, 17 February)
• Re: [w3c/push-api] push-register (pushregistrationlost / pushsubscriptionchange) behavior when clearing browser cache (#61) (Friday, 17 February)
• Re: [w3c/push-api] push-register (pushregistrationlost / pushsubscriptionchange) behavior when clearing browser cache (#61) (Friday, 17 February)
• Re: [w3c/push-api] pushsubscriptionchange - Initial feedback (#120) (Friday, 17 February)
• Re: [w3c/push-api] pushsubscriptionchange - Initial feedback (#120) (Friday, 17 February)
• Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Friday, 17 February)
• Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Friday, 17 February)
• [w3c/push-api] Connectivity is not required to unsubscribe a subscription (#238) (Friday, 17 February)
• Re: [w3c/push-api] event.waitUntil(registration.subscribe()) would cause a deadlock (#221) (Friday, 17 February)
• Re: [w3c/push-api] event.waitUntil(registration.subscribe()) would cause a deadlock (#221) (Friday, 17 February)
• Re: [w3c/push-api] Restructure the `push` event (#237) (Friday, 17 February)
• Re: [w3c/push-api] Restructure the `push` event (#237) (Friday, 17 February)
• [w3c/push-api] Restructure the `push` event (#237) (Friday, 17 February)
• Re: [w3c/push-api] Properly define the pushsubscriptionchange event (#234) (Friday, 17 February)
• Re: [w3c/push-api] Properly defining `pushsubscriptionchange` (#228) (Friday, 17 February)
• [w3c/push-api] Firing `pushsubscriptionchange` when permission is regranted (#236) (Friday, 17 February)
• Re: [w3c/push-api] Properly define the pushsubscriptionchange event (#234) (Friday, 17 February)
• Re: [w3c/push-api] Properly define the pushsubscriptionchange event (#234) (Friday, 17 February)
• [w3c/push-api] Separate out an algorithm for creating a push subscription (#235) (Friday, 17 February)

Peter Rushforth

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

Philip Jägenstedt

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Monday, 27 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Friday, 24 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Friday, 24 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Friday, 24 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Friday, 24 February)
• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Thursday, 23 February)
• [w3c/uievents] Specify the arguments of initMouseEvent() (#136) (Thursday, 23 February)
• Re: [w3c/uievents] Specify the arguments of initCompositionEvent() (#134) (Thursday, 23 February)
• [w3c/uievents] Specify the arguments of initCompositionEvent() (#134) (Thursday, 23 February)
• Re: [w3c/uievents] Clearly specify initUIEvent (#133) (Thursday, 23 February)
• Re: [w3c/uievents] Clearly specify initUIEvent (#133) (Tuesday, 21 February)
• Re: [w3c/uievents] Clearly specify initUIEvent (#133) (Tuesday, 21 February)
• Re: [whatwg/fullscreen] Meta: enable PR preview (#77) (Tuesday, 21 February)
• Re: [w3c/IndexedDB] open/deleteDatabase should throw on opaque origin (#150) (Friday, 17 February)
• Re: [w3c/IndexedDB] open/deleteDatabase should throw on opaque origin (#150) (Thursday, 16 February)
• Re: [w3c/clipboard-apis] The ClipboardEvent constructor is strange (#10) (Thursday, 16 February)
• Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34) (Thursday, 16 February)
• [whatwg/dom] Meta: link to web-platform-tests in header (#411) (Wednesday, 15 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Wednesday, 15 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Wednesday, 15 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Wednesday, 15 February)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Wednesday, 15 February)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Wednesday, 15 February)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Tuesday, 14 February)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Tuesday, 14 February)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Tuesday, 14 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Tuesday, 14 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Tuesday, 14 February)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Tuesday, 14 February)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Tuesday, 14 February)
• Re: [heycam/webidl] Investigate banning nullable enums (#213) (Monday, 13 February)
• Re: [heycam/webidl] Investigate banning nullable enums (#213) (Monday, 13 February)
• Re: [whatwg/dom] initEvent should not require three parameters (#387) (Wednesday, 8 February)
• Re: [whatwg/dom] initEvent should not require three parameters (#387) (Wednesday, 8 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Wednesday, 8 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Monday, 6 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Monday, 6 February)
• Re: [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Monday, 6 February)
• [whatwg/fullscreen] Link to web-platform-tests in header (#75) (Monday, 6 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Friday, 3 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Friday, 3 February)

PhistucK

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Tuesday, 21 February)

pkotwicz

• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Saturday, 11 February)
• Re: [w3c/manifest] scope="../" should be invalid (#551) (Wednesday, 8 February)
• [w3c/manifest] scope="../" should be invalid (#551) (Monday, 6 February)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Monday, 6 February)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Monday, 6 February)

Prayag Verma

• Re: [w3c/IndexedDB] Editorial: remove repeated word (#151) (Wednesday, 15 February)
• [w3c/IndexedDB] Editorial: remove repeated word (#151) (Wednesday, 15 February)

publicocean0

• Re: [w3c/ServiceWorker] Find a way for service workers to get their current state (#1077) (Sunday, 26 February)
• [w3c/ServiceWorker] No event for knowing when service worker is not available (#1082) (Sunday, 26 February)
• Re: [w3c/ServiceWorker] requestIdleCallback (equivalent) for ServiceWorkerGlobalScope (#790) (Sunday, 26 February)
• [w3c/ServiceWorker] no way for using a websocket inside a service worker (#1072) (Tuesday, 14 February)

rektide

• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Friday, 24 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Friday, 24 February)

Rhy (Rachael L) Moore

• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Thursday, 9 February)

Rimas

• Re: [whatwg/url] Use empty host for file URL's (#260) (Monday, 27 February)
• Re: [whatwg/url] Use empty host for file URL's (#260) (Monday, 27 February)
• Re: [whatwg/url] Use empty host for file URL's (#260) (Saturday, 25 February)
• Re: [whatwg/url] Use empty host for file URL's (#260) (Saturday, 25 February)
• Re: [whatwg/url] Use empty host for file URL's (#260) (Friday, 24 February)
• [whatwg/url] Use empty host for file URL's (#260) (Friday, 24 February)
• Re: [whatwg/url] Empty or null host when scheme is "file:"? (#258) (Friday, 24 February)
• Re: [whatwg/url] Empty or null host when scheme is "file:"? (#258) (Thursday, 23 February)
• [whatwg/url] Empty or null host when scheme is "file:"? (#258) (Thursday, 23 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Tuesday, 21 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Wednesday, 8 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 8 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 8 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 8 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Tuesday, 7 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Friday, 3 February)
• Re: [whatwg/url] Fix: allow percent encoded code points in the non-special URLs host (#218) (Wednesday, 1 February)

Rob Dolin (MSFT)

• Re: [w3c/manifest] Simple Example and Complex Example (#553) (Friday, 10 February)
• [w3c/manifest] Simple Example and Complex Example (#553) (Thursday, 9 February)
• Re: [w3c/manifest] scope="../" should be invalid (#551) (Wednesday, 8 February)

rolivo

• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (c9e0a6c) (Friday, 10 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (c9e0a6c) (Friday, 10 February)

Romain

• [whatwg/streams] Access to reader.readIntoRequests withtout checking reader type (#686) (Thursday, 23 February)

Russell Bicknell

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

Ryosuke Niwa

• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Monday, 27 February)
• Re: [w3c/selection-api] Let addRange not update existing range (#80) (Monday, 27 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 23 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 22 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 22 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 22 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 22 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 20 February)
• Re: [w3c/selection-api] Bahavior without browsing context (#82) (Monday, 20 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 20 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 20 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 20 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 19 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 19 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 19 February)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Sunday, 19 February)
• Re: [w3c/webcomponents] Shadow dom innerhtml and CSP unsafe-inline (#627) (Saturday, 18 February)
• Re: [w3c/webcomponents] Shadow dom innerhtml and CSP unsafe-inline (#627) (Saturday, 18 February)
• Re: [w3c/webcomponents] Shadow dom innerhtml and CSP unsafe-inline (#627) (Saturday, 18 February)
• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Friday, 17 February)
• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Friday, 17 February)
• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Thursday, 16 February)
• Re: [w3c/selection-api] Let addRange not update existing range (#80) (Thursday, 16 February)
• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Thursday, 16 February)
• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Thursday, 16 February)
• Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34) (Wednesday, 15 February)
• Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34) (Wednesday, 15 February)
• Re: [w3c/selection-api] Let addRange not update existing range (#80) (Wednesday, 15 February)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Tuesday, 14 February)
• Re: [w3c/selection-api] Let addRange not update existing range (#80) (Tuesday, 14 February)
• Re: [w3c/selection-api] Let addRange not update existing range (#80) (Tuesday, 14 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Monday, 13 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Monday, 13 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Monday, 13 February)
• Re: [w3c/selection-api] Selection should detach associated Range when Range move to another root. (#79) (Monday, 13 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Tuesday, 7 February)

Salvador de la Puente González

• Re: [w3c/push-api] push-register (pushregistrationlost / pushsubscriptionchange) behavior when clearing browser cache (#61) (Saturday, 25 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Saturday, 25 February)
• Re: [w3c/push-api] push-register (pushregistrationlost / pushsubscriptionchange) behavior when clearing browser cache (#61) (Wednesday, 22 February)

sayandevd

• Re: [whatwg/xhr] t (#114) (Thursday, 16 February)
• [whatwg/xhr] t (#114) (Thursday, 16 February)

Sean King

• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Saturday, 11 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Thursday, 9 February)

Sebastian Zartner

• Re: [whatwg/dom] High resolution timing for events (#23) (Saturday, 25 February)

Simon Pieters

• Re: [whatwg/url] Is failure ever not a syntax violation? (#219) (Monday, 13 February)
• Re: [whatwg/url] Define which URLs are valid in the parser examples (#242) (Friday, 10 February)
• Re: [whatwg/url] Define which URLs are valid in the parser examples (#242) (Friday, 10 February)
• Re: [whatwg/url] Define which URLs are valid in the parser examples (#242) (Friday, 10 February)
• Re: [whatwg/url] Consider always escaping U+0020 (#125) (Friday, 10 February)
• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Friday, 3 February)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 1 February)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 1 February)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 1 February)

Simon Sapin

• Re: [whatwg/url] Large ports of non special urls (#257) (Thursday, 23 February)

sleevi

• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 27 February)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 27 February)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 27 February)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 27 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Monday, 27 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Monday, 27 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Monday, 27 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Friday, 24 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Tuesday, 21 February)
• Re: [whatwg/url] IDNA Nontransitional_Processing (#239) (Thursday, 16 February)
• Re: [whatwg/url] Use Nontransitional_Processing for IDNA ToASCII (#240) (Tuesday, 14 February)

smaug----

• Re: [w3c/ServiceWorker] clarify Clients.matchAll() focus order for nested frames (#1080) (Tuesday, 28 February)
• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Thursday, 23 February)
• Re: [w3c/uievents] Specify the arguments of initCompositionEvent() (#134) (Thursday, 23 February)
• Re: [w3c/uievents] Clearly specify initUIEvent (#133) (Wednesday, 22 February)
• Re: [w3c/selection-api] Let addRange not update existing range (#80) (Wednesday, 15 February)
• Re: [whatwg/dom] Add legacyOutputDidListenersThrowFlag to event dispatch for IDB (#409) (Tuesday, 14 February)
• [whatwg/xhr] "Every millisecond, as long as the stop timeout flag is unset, queue a microtask to run these subsubsubsteps" looks wrong. (#112) (Friday, 10 February)

spanicker

• Re: [whatwg/fetch] Expose PerformanceResourceTiming in Response Objects (#491) (Friday, 17 February)
• [w3ctag/spec-reviews] Long Task API (#150) (Friday, 3 February)

STD4453

• Re: [whatwg/url] Typo in file state (#246) (Sunday, 12 February)
• [whatwg/url] Typo in file state (#246) (Sunday, 12 February)

stefan hakansson

• Re: [w3c/permissions] Define restrictions on "device-info" permission (from TPAC). (#131) (Monday, 27 February)
• Re: [w3c/permissions] Define restrictions on "device-info" permission (from TPAC). (#131) (Wednesday, 22 February)

Steven

• Re: [whatwg/url] toJSON() serialization (#137) (Thursday, 2 February)

Stuart P. Bentley

• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Friday, 24 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Friday, 24 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Thursday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 22 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 1 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 1 February)

Surma

• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• Re: [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)
• [w3c/ServiceWorker] Consider throwing when non-promise is passed to `waitUntil`. (#1068) (Wednesday, 8 February)

Tab Atkins Jr.

• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Wednesday, 15 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Monday, 13 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Friday, 10 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Friday, 10 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Friday, 10 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Friday, 10 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Monday, 6 February)

Takayoshi Kochi

• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Friday, 17 February)
• Re: [w3c/webcomponents] [imports]: <link rel=import> shouldn't be active when added by innerHTML (bugzilla: 26898) (#193) (Monday, 13 February)
• Re: [w3c/webcomponents] [imports]: <link rel=import> shouldn't be active when added by innerHTML (bugzilla: 26898) (#193) (Monday, 13 February)

Takeshi Yoshino

• Re: [whatwg/streams] Execute strategySize first in write() (#680) (Thursday, 16 February)
• Re: [whatwg/streams] Writable stream spec fixes (#681) (Thursday, 16 February)

TAMURA, Kent

• [w3c/selection-api] Bahavior without browsing context (#82) (Monday, 20 February)
• Re: [w3c/selection-api] Selection should detach associated Range when Range move to another root. (#79) (Friday, 17 February)
• Re: [w3c/selection-api] Selection should detach associated Range when Range move to another root. (#79) (Wednesday, 15 February)
• Re: [w3c/selection-api] Let addRange not update existing range (#80) (Tuesday, 14 February)
• Re: [w3c/selection-api] Let addRange not update existing range (#80) (Tuesday, 14 February)

Ted Dinklocker

• Re: [whatwg/fetch] Add several ports to the "bad ports" list. (#482) (Tuesday, 7 February)

Till Schneidereit

• Re: [whatwg/streams] Writable stream spec fixes (#681) (Monday, 13 February)
• Re: [whatwg/streams] Fix queue total size tracking logic (#661) (Saturday, 11 February)
• [whatwg/streams] Writable stream spec fixes (#681) (Saturday, 11 February)

Timothy Gu

• Re: [whatwg/url] new URLSearchParams(entries) (#256) (Tuesday, 21 February)
• [whatwg/url] Editorial: remove one more instance of "simply" (#249) (Tuesday, 14 February)
• Re: [whatwg/url] Should URL constructors prepend ? when initializing query objects? (#248) (Tuesday, 14 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Tuesday, 14 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Monday, 13 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Tuesday, 7 February)
• Re: [heycam/webidl] `any` type conversion does not take into account of symbols (#301) (Tuesday, 7 February)
• [heycam/webidl] `any` type conversion does not take into account of symbols (#301) (Tuesday, 7 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Thursday, 2 February)
• Re: [whatwg/url] Define URL's toJSON() (#229) (Thursday, 2 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Wednesday, 1 February)
• Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204) (Wednesday, 1 February)

Tobie Langel

• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 28 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 28 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 28 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 28 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 28 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 28 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 28 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 27 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 27 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 27 February)
• [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 27 February)
• [heycam/webidl] Cleanup DOMException. (#320) (Thursday, 23 February)
• Re: [heycam/webidl] Base sequences, dictionaries, and records on Infra types (#317) (Wednesday, 22 February)
• Re: [heycam/webidl] Base sequences, dictionaries, and records on Infra types (#317) (Wednesday, 22 February)
• Re: [heycam/webidl] Base sequences, dictionaries, and records on Infra types (#317) (Wednesday, 22 February)
• Re: [heycam/webidl] Base sequences, dictionaries, and records on Infra types (#317) (Wednesday, 22 February)
• Re: [heycam/webidl] Carry out math operations on real numbers, not IEEE 754. (#316) (Wednesday, 22 February)
• Re: [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Wednesday, 22 February)
• Re: [heycam/webidl] Carry out math operations on real numbers, not IEEE 754. (#316) (Wednesday, 22 February)
• Re: [heycam/webidl] Carry out math operations on real numbers, not IEEE 754. (#316) (Wednesday, 22 February)
• Re: [heycam/webidl] Carry out math operations on real numbers, not IEEE 754. (#316) (Wednesday, 22 February)
• Re: [heycam/webidl] Carry out math operations on real numbers, not IEEE 754. (#316) (Wednesday, 22 February)
• [heycam/webidl] Carry out math operations on real numbers, not IEEE 754. (#316) (Wednesday, 22 February)
• Re: [heycam/webidl] Code-points, code-units, characters, oh my! (#312) (Wednesday, 22 February)
• Re: [heycam/webidl] Code-points, code-units, characters, oh my! (#312) (Wednesday, 22 February)
• Re: [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Wednesday, 22 February)
• Re: [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Wednesday, 22 February)
• Re: [heycam/webidl] Is -0 < 0, regarding [EnforceRange]? (#306) (Wednesday, 22 February)
• Re: [heycam/webidl] Meta: Fix scroll jank (#315) (Tuesday, 21 February)
• Re: [heycam/webidl] Scroll script causes jank (#314) (Tuesday, 21 February)
• Re: [heycam/webidl] Scroll script causes jank (#314) (Tuesday, 21 February)
• [heycam/webidl] Meta: Fix scroll jank (#315) (Tuesday, 21 February)
• Re: [heycam/webidl] Scroll script causes jank (#314) (Tuesday, 21 February)
• [heycam/webidl] Scroll script causes jank (#314) (Tuesday, 21 February)
• Re: [heycam/webidl] Require `new` for named constructors (#275) (Monday, 20 February)
• Re: [heycam/webidl] Check if NodeFilter.length is defined correctly. (#83) (Monday, 20 February)
• Re: [heycam/webidl] Should callback interface objects have a "length" property? (#279) (Monday, 20 February)
• Re: [heycam/webidl] Constants require an interface prototype object which callback interfaces don't have (#281) (Monday, 20 February)
• Re: [heycam/webidl] Revamp interface bindings (#313) (Monday, 20 February)
• Re: [heycam/webidl] Revamp interface bindings (#283) (Monday, 20 February)
• Re: [heycam/webidl] Legacy callback interface objects are badly defined (#78) (Monday, 20 February)
• Re: [heycam/webidl] Revamp interface bindings (#283) (Monday, 20 February)
• Re: [heycam/webidl] Revamp interface bindings (#313) (Monday, 20 February)
• [heycam/webidl] Revamp interface bindings (#313) (Monday, 20 February)
• [whatwg/url] Meta: make .pr-preview.json valid json (#251) (Wednesday, 15 February)
• Re: [whatwg/url] Meta: update .pr-preview.json config file (#250) (Wednesday, 15 February)
• [whatwg/url] Meta: update .pr-preview.json config file (#250) (Wednesday, 15 February)
• Re: [heycam/webidl] Meta: fix broken deploy script (#311) (Tuesday, 14 February)
• [heycam/webidl] Meta: fix broken deploy script (#311) (Tuesday, 14 February)
• Re: [heycam/webidl] Editorial: fix readme line breaks (#310) (Tuesday, 14 February)
• [heycam/webidl] Editorial: fix readme line breaks (#310) (Tuesday, 14 February)
• Re: [heycam/webidl] Revamp interface bindings (#283) (Tuesday, 14 February)
• Re: [heycam/webidl] Set up auto-deploy to GitHub pages from master (#221) (Tuesday, 14 February)
• Re: [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) (Thursday, 9 February)
• Re: [whatwg/url] Meta: enable preview and diffs for all pull requests (#236) (Thursday, 9 February)
• Re: [whatwg/url] Meta: enable preview and diffs for all pull requests (#236) (Thursday, 9 February)
• Re: [whatwg/url] Meta: enable preview and diffs for all pull requests (#236) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Wednesday, 8 February)
• Re: [heycam/webidl] Disambiguate / explain maplike vs record (#303) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Wednesday, 8 February)
• Re: [heycam/webidl] Allow records to be omitted (#304) (Wednesday, 8 February)
• Re: [heycam/webidl] Disambiguate / explain maplike vs record (#303) (Wednesday, 8 February)
• Re: [heycam/webidl] Clarify [[Call]] + [[Construct]] for named (and possibly non-named) constructors (#278) (Thursday, 2 February)
• Re: [heycam/webidl] Revamp interface bindings (#283) (Thursday, 2 February)
• Re: [heycam/webidl] Revamp interface bindings (#283) (Wednesday, 1 February)
• Re: [heycam/webidl] Revamp interface bindings (#283) (Wednesday, 1 February)
• Re: [heycam/webidl] Revamp interface bindings (#283) (Wednesday, 1 February)
• Re: [heycam/webidl] Editorial: use recently added ids to ES math equations. (#290) (Wednesday, 1 February)
• Re: [heycam/webidl] Links to ECMA-262 abstract math functions should be more specific (#288) (Wednesday, 1 February)

Tom Schuster

• Re: [whatwg/fetch] Add several ports to the "bad ports" list. (#482) (Tuesday, 7 February)

toriningen

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

Travis Leithead

• Re: [w3ctag/spec-reviews] TV Control API (#111) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] Audio Output Device APIs (#132) (Thursday, 9 February)
• Re: [w3ctag/spec-reviews] MediaSession (#149) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] IFrame support in web payments (#147) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] Performance API's, Security and Privacy (#120) (Wednesday, 8 February)
• Re: [w3ctag/spec-reviews] IFrame support in web payments (#147) (Wednesday, 8 February)

Trevor Rowbotham

• Re: [whatwg/url] Explain how syntax relates to the parser for hosts and URLs (#228) (Wednesday, 8 February)

Trey Shugart

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

Valentin Gosu

• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Thursday, 16 February)
• Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464) (Thursday, 16 February)

vanupam

• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 7 February)

Victor Costan

• Re: [w3c/IndexedDB] Indicate 2.0 feature support in Chrome/Firefox/Safari (#157) (Friday, 24 February)
• Re: [w3ctag/spec-reviews] IndexedDB 2.0 features review (#153) (Wednesday, 22 February)
• Re: [w3ctag/spec-reviews] IndexedDB 2.0 features review (#153) (Tuesday, 21 February)
• [w3ctag/spec-reviews] IndexedDB 2.0 features review (#153) (Friday, 17 February)
• Re: [w3c/FileAPI] Please set the repository's URL to https://w3c.github.io/FileAPI/ (#64) (Sunday, 5 February)
• [w3c/FileAPI] Please set the repository's URL to https://w3c.github.io/FileAPI/ (#64) (Sunday, 5 February)

Vincent

• Re: [w3c/webcomponents] Support renaming, aliasing, or namespacing imported elements (#344) (Monday, 13 February)
• Re: [w3c/webcomponents] Support renaming, aliasing, or namespacing imported elements (#344) (Monday, 13 February)
• Re: [w3c/webcomponents] Support renaming, aliasing, or namespacing imported elements (#344) (Monday, 13 February)

Vincent Scheib

• Re: [heycam/webidl] Disambiguate / explain maplike vs record (#303) (Wednesday, 8 February)
• Re: [heycam/webidl] Disambiguate / explain maplike vs record (#303) (Wednesday, 8 February)
• [heycam/webidl] Disambiguate / explain maplike vs record (#303) (Wednesday, 8 February)

Vsevolod Shmyroff

• Re: [w3c/FileAPI] Remove FileList (Migrate to | typedef FileList FrozenArray<File>; | (#19) (Tuesday, 28 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 28 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 28 February)
• Re: [w3c/FileAPI] Remove FileList (Migrate to | typedef FileList FrozenArray<File>; | (#19) (Tuesday, 28 February)
• [w3c/FileAPI] FileList.drop method (#72) (Tuesday, 28 February)
• Re: [w3c/FileAPI] where is this document for "utils.regexp.isChinese"? (#70) (Tuesday, 28 February)
• Re: [w3c/FileAPI] Update feedback info (#69) (Monday, 20 February)
• Re: [w3c/FileAPI] Update feedback info (#69) (Thursday, 16 February)
• Re: [w3c/FileAPI] Update feedback info (#69) (Thursday, 16 February)
• Re: [w3c/FileAPI] Update feedback info (#49) (Thursday, 16 February)
• [w3c/FileAPI] Update feedback info (#69) (Thursday, 16 February)

Xiaoqian Wu

• Re: [w3c/selection-api] Let addRange not update existing range (#80) (Monday, 27 February)
• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Monday, 27 February)

Xidorn Quan

• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Friday, 24 February)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Tuesday, 14 February)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Tuesday, 14 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Change algorithm of "collect documents to unfullscreen" (#72) (Tuesday, 14 February)
• Re: [whatwg/dom] Fallback to legacy type only when event is trusted (#406) (Wednesday, 8 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Friday, 3 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Thursday, 2 February)
• Re: [whatwg/dom] Consider adding Promise-based API for listerning event (#333) (Wednesday, 1 February)
• Re: [whatwg/dom] Event not dispatched by the user agent should not fallback to legacy (#404) (Wednesday, 1 February)
• [whatwg/dom] Fallback to legacy type only when event is trusted (#406) (Wednesday, 1 February)

Yoav Weiss

• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Tuesday, 21 February)
• Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Tuesday, 21 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Friday, 10 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Friday, 10 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Friday, 10 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Friday, 10 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Friday, 10 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 9 February)
• Re: [whatwg/fetch] preload, destinations, and module scripts (#486) (Thursday, 9 February)

Yoichi Osato

• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Monday, 27 February)
• Re: [w3c/selection-api] Let addRange not update existing range (#80) (Wednesday, 22 February)
• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Friday, 17 February)
• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Thursday, 16 February)
• Re: [w3c/selection-api] Change addRange (closes #80) (#81) (Thursday, 16 February)
• Re: [w3c/selection-api] Let addRange not update existing range (#80) (Thursday, 16 February)
• [w3c/selection-api] Change addRange (#81) (Wednesday, 15 February)
• [w3c/selection-api] Let addRange not update existing range (#80) (Tuesday, 14 February)

yosin

• [w3c/selection-api] Selection should detach associated Range when Range move to another root. (#79) (Monday, 13 February)

youennf

• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 27 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Thursday, 9 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Thursday, 9 February)
• Re: [whatwg/fetch] Constructing a Headers from another Headers is lossy (#481) (Tuesday, 7 February)

yuhong

• Re: [whatwg/encoding] Add UTF-7 to replacement encoding list? / Encoding sniffing (#68) (Saturday, 4 February)

Yutaka Hirano

• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Monday, 20 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Wednesday, 15 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Wednesday, 15 February)
• Re: [whatwg/url] Needs to ignore repeated slashes in file URL (#232) (Wednesday, 15 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Monday, 13 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Thursday, 9 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Thursday, 9 February)
• Re: [whatwg/fetch] Stop lowercasing header names (#476) (Thursday, 9 February)

Yves Lafon

• Re: [w3c/push-api] Enable auto publishing of Push API drafts (#241) (Wednesday, 22 February)
• Re: [w3c/push-api] Enable auto publishing of Push API drafts (#241) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Add Client type for ServiceWorkerGlobalScope environments (#1074) (Thursday, 16 February)
• Re: [w3c/FileAPI] Please set the repository's URL to https://w3c.github.io/FileAPI/ (#64) (Sunday, 5 February)
• Re: [w3c/FileAPI] Please set the repository's URL to https://w3c.github.io/FileAPI/ (#64) (Sunday, 5 February)
• Re: [w3c/ServiceWorker] Create F2F agenda - 3-4 April 2017 (#1053) (Wednesday, 1 February)

Zakor Gyula

• [w3c/permissions] May reorder the permission state read steps (#137) (Tuesday, 7 February)

Zambonifofex

• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Friday, 10 February)

Zbyszek Tenerowicz

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Tuesday, 21 February)

Zhiqiang Zhang

• Re: [w3c/manifest] Should the scope terminate by "/"? (#554) (Tuesday, 14 February)
• Re: [w3c/manifest] Should the scope terminate by "/"? (#554) (Tuesday, 14 February)
• [w3c/manifest] Should the scope terminate by "/"? (#554) (Friday, 10 February)

芝麻飞来

• Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252) (Saturday, 25 February)
• Re: [whatwg/fetch] Allow * for Access-Control-Allow-Headers and Access-Control-Allow-Methods (#251) (Saturday, 25 February)

Last message date: Tuesday, 28 February 2017 23:34:42 UTC