public-webapps-github@w3.org from October 2018 by author

Aaron Adams

Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 4 October)

Adam Rice

Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 31 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282) (Tuesday, 30 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Tuesday, 30 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Monday, 29 October)
Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Thursday, 25 October)
Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Thursday, 25 October)
Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Friday, 19 October)
[whatwg/streams] Demos need updating to use TextDecoderStream (#959) (Monday, 15 October)
Re: [whatwg/streams] Using fetch streams API without recursion (#958) (Monday, 15 October)
Re: [whatwg/streams] Using fetch streams API without recursion (#958) (Monday, 15 October)
Re: [whatwg/streams] Add explainer for transferable streams (#956) (Friday, 12 October)
Re: [whatwg/streams] Add explainer for transferable streams (#956) (Friday, 12 October)
Re: [whatwg/streams] Meta: fix realm issues in reference implementation testing setup (#957) (Friday, 12 October)
Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Thursday, 11 October)
Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Thursday, 11 October)
Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa) (Thursday, 11 October)
Re: [whatwg/streams] Add explainer for transferable streams (#956) (Thursday, 11 October)
[whatwg/streams] Add explainer for transferable streams (#956) (Wednesday, 10 October)
Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa) (Friday, 5 October)
Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa) (Friday, 5 October)
Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Friday, 5 October)
Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Friday, 5 October)
Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Friday, 5 October)
Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954) (Thursday, 4 October)
Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa) (Thursday, 4 October)
Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954) (Thursday, 4 October)
Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Thursday, 4 October)
Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Thursday, 4 October)
Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Monday, 1 October)
Re: [whatwg/encoding] bind encoder to self (#159) (Monday, 1 October)

Alex Godoy Wolff

Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)

Alex Russell

Re: [w3ctag/design-reviews] OffscreenCanvas new commit() and DedicatedWorker.requestAnimationFrame (#288) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] HTML General Review: Server-Sent Events (#267) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] import.meta.url, and import.meta generally (#208) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] import.meta.url, and import.meta generally (#208) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] ads.txt (#201) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Intersection Observer review (#197) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614) (Wednesday, 24 October)
[w3ctag/design-reviews] [TPAC][HTML General Review]: how to decide if workers are subresources or separate contexts (#310) (Tuesday, 23 October)

Alexey Lyakhov

Re: [whatwg/fetch] [3.0.0] SSR build error after update from 2.0.4 (#820) (Monday, 29 October)
Re: [whatwg/fetch] [3.0.0] SSR build error after update from 2.0.4 (#820) (Monday, 29 October)
[whatwg/fetch] [3.0.0] SSR build error after update from 2.0.4 (#820) (Friday, 26 October)

Alexey Rodionov

Re: [w3c/ServiceWorker] [Proposal] ServiceWorkerContainer.installing(scope) promise (#1364) (Monday, 29 October)
Re: [w3c/ServiceWorker] [Proposal] ServiceWorkerContainer.installing(scope) promise (#1364) (Monday, 29 October)
[w3c/ServiceWorker] [Proposal] ServiceWorkerContainer.installing(scope) promise (#1364) (Sunday, 28 October)
Re: [w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362) (Thursday, 25 October)
[w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362) (Wednesday, 24 October)

aliams

Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 26 October)
Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Tuesday, 9 October)
Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Tuesday, 9 October)
Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Tuesday, 9 October)
Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Tuesday, 9 October)

Alice

Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134) (Tuesday, 30 October)
Re: [w3c/webcomponents] Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? (#762) (Friday, 26 October)

Amelia Bellamy-Royds

Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Monday, 29 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Monday, 29 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Wednesday, 24 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Tuesday, 23 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Thursday, 11 October)

Andrea Giammarchi

Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Sunday, 21 October)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 20 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Saturday, 20 October)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 19 October)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 19 October)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 19 October)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 18 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 18 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Wednesday, 17 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 17 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Tuesday, 16 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 16 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 16 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 16 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Sunday, 14 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Sunday, 14 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Saturday, 13 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)

andreas-butler

[w3ctag/design-reviews] IndexedDB Transaction Explicit Commit API (#316) (Tuesday, 30 October)
Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Friday, 5 October)

Andrew

[whatwg/streams] Using fetch streams API without recursion (#958) (Monday, 15 October)

Andrew Sutherland

Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331) (Tuesday, 30 October)
Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Tuesday, 9 October)
Re: [w3c/IndexedDB] Proposal: Add explicit IDBTransaction.commit() (was: add "writeonly" mode) (#234) (Saturday, 6 October)
Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Saturday, 6 October)

Anne van Kesteren

Re: [whatwg/fetch] Deduplicate 'the' (#822) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 31 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 31 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Wednesday, 31 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 31 October)
Re: [whatwg/fetch] Remove Gecko-only quirk (#816) (Wednesday, 31 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Wednesday, 31 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Wednesday, 31 October)
Re: [whatwg/fetch] Editorial: remove leftover sentence (#815) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] import.meta.url, and import.meta generally (#208) (Wednesday, 31 October)
[w3c/ServiceWorker] Module scripts to be fetched with "same-origin" for credentials (#1365) (Tuesday, 30 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Tuesday, 30 October)
Re: [whatwg/xhr] Limit Content-Type overrides to when charset isn't already UTF-8 (#224) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282) (Tuesday, 30 October)
Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Tuesday, 30 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Tuesday, 30 October)
Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Tuesday, 30 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292) (Tuesday, 30 October)
Re: [whatwg/xhr] Limit Content-Type overrides to when charset isn't already UTF-8 (#224) (Tuesday, 30 October)
Re: [w3c/webcomponents] JSON "modules" (#770) (Monday, 29 October)
Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344) (Monday, 29 October)
Re: [w3ctag/design-reviews] TAG Review Request: Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Monday, 29 October)
Re: [whatwg/fetch] Split `document` destination for top-level and nested contexts. (#819) (Monday, 29 October)
Re: [w3ctag/design-reviews] TAG Review Request: Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Monday, 29 October)
Re: [w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359) (Monday, 29 October)
Re: [w3ctag/design-reviews] TAG Review Request: Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Monday, 29 October)
Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253) (Monday, 29 October)
Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253) (Monday, 29 October)
Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253) (Monday, 29 October)
Re: [whatwg/dom] Remove redundant <dd> (#712) (Monday, 29 October)
Re: [whatwg/dom] Remove redundant <dd> (#712) (Monday, 29 October)
Re: [whatwg/dom] Remove redundant <dd> (#712) (Monday, 29 October)
Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344) (Monday, 29 October)
Re: [w3c/DOM-Parsing] Define the origin of the documents returned from DOMParser (#24) (Monday, 29 October)
Re: [whatwg/fetch] [3.0.0] SSR build error after update from 2.0.4 (#820) (Monday, 29 October)
Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769) (Monday, 29 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Monday, 29 October)
[w3c/webcomponents] JSON "modules" (#770) (Monday, 29 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Friday, 26 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Friday, 26 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Friday, 26 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Friday, 26 October)
Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755) (Friday, 26 October)
Re: [whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710) (Friday, 26 October)
Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Friday, 26 October)
Re: [whatwg/dom] window.event and shadow trees (#679) (Thursday, 25 October)
Re: [whatwg/dom] window.event and shadow trees (#679) (Thursday, 25 October)
Re: [whatwg/dom] Allow <slot> to find slottables by slottables's IDs as well (#677) (Thursday, 25 October)
Re: [whatwg/dom] Allow <slot> to find slottables by slottables's IDs as well (#677) (Thursday, 25 October)
Re: [whatwg/dom] Allow <slot> to find slottables by slottables's IDs as well (#677) (Thursday, 25 October)
Re: [whatwg/dom] Allow <menu>, <ul>, <ol>, <li> to attach shadow (#676) (Thursday, 25 October)
Re: [whatwg/dom] A faster way to find open shadow roots (or shadow hosts) (#665) (Thursday, 25 October)
Re: [whatwg/dom] `compareDocumentPosition` should allow comparison of elements in the same shadow-including root (#320) (Thursday, 25 October)
Re: [whatwg/dom] `compareDocumentPosition` should allow comparison of elements in the same shadow-including root (#320) (Thursday, 25 October)
Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Thursday, 25 October)
[whatwg/dom] Figure out if we want getComposedPath() for Event (#711) (Thursday, 25 October)
Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Wednesday, 24 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Tuesday, 23 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Tuesday, 23 October)
Re: [w3c/webcomponents] Add new proposal (#768) (Tuesday, 23 October)
Re: [whatwg/dom] [spec bug?] Element with name attribute breaks Document (#708) (Tuesday, 23 October)
Re: [w3c/ServiceWorker] NavigationPreloadManager.setHeaderValue should reject invalid HTTP header field values (#1000) (Tuesday, 23 October)
Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Monday, 22 October)
Re: [whatwg/fetch] Redesign "extract header values" and "extract header list values" (#814) (Friday, 19 October)
Re: [whatwg/fetch] Redesign "extract header values" and "extract header list values" (#814) (Thursday, 18 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Thursday, 18 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Thursday, 18 October)
Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Thursday, 18 October)
Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707) (Thursday, 18 October)
Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707) (Thursday, 18 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Thursday, 18 October)
Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707) (Thursday, 18 October)
Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707) (Thursday, 18 October)
Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707) (Thursday, 18 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Thursday, 18 October)
Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Thursday, 18 October)
[whatwg/dom] May return the same HTMLCollection object (#706) (Thursday, 18 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Wednesday, 17 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Wednesday, 17 October)
Re: [whatwg/fetch] What does "combined value" return for a name not in the header list? (#752) (Wednesday, 17 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Wednesday, 17 October)
[whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Wednesday, 17 October)
[whatwg/fetch] Editorial: drop parenthesis around variables (#817) (Wednesday, 17 October)
[whatwg/fetch] Remove Gecko-only quirk (#816) (Wednesday, 17 October)
[whatwg/fetch] Editorial: remove leftover sentence (#815) (Wednesday, 17 October)
Re: [whatwg/encoding] bind encoder to self (#159) (Wednesday, 17 October)
Re: [whatwg/encoding] bind encoder to self (#159) (Wednesday, 17 October)
Re: [whatwg/encoding] ISO 2022-jp encoding/decoding support (#60) (Wednesday, 17 October)
Re: [whatwg/encoding] ISO 2022-jp encoding/decoding support (#60) (Wednesday, 17 October)
Re: [whatwg/encoding] Shift-JIS encoding/decoding support (#61) (Wednesday, 17 October)
Re: [whatwg/encoding] Shift-JIS encoding/decoding support (#61) (Wednesday, 17 October)
Re: [whatwg/encoding] EUK-kr encoding/decoding support (#62) (Wednesday, 17 October)
Re: [whatwg/encoding] EUK-kr encoding/decoding support (#62) (Wednesday, 17 October)
Re: [whatwg/encoding] EUC-jp encoding/decoding support (#59) (Wednesday, 17 October)
Re: [whatwg/encoding] EUC-jp encoding/decoding support (#59) (Wednesday, 17 October)
Re: [whatwg/encoding] Big5 encoding/decoding support (#58) (Wednesday, 17 October)
Re: [whatwg/encoding] Big5 encoding/decoding support (#58) (Wednesday, 17 October)
Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Wednesday, 17 October)
Re: [whatwg/encoding] GBK encoding/decoding support (#56) (Wednesday, 17 October)
Re: [whatwg/url] Do not remove newline and tab characters (#419) (Wednesday, 17 October)
Re: [whatwg/xhr] Limit Content-Type overrides to when charset isn't already UTF-8 (#224) (Tuesday, 16 October)
[whatwg/xhr] Limit Content-Type overrides to when charset isn't already UTF-8 (#224) (Tuesday, 16 October)
Re: [whatwg/fetch] "combined value" is wrong (#757) (Tuesday, 16 October)
Re: [whatwg/fetch] "combined value" is wrong (#757) (Tuesday, 16 October)
Re: [whatwg/fetch] Change combined values (#813) (Tuesday, 16 October)
Re: [whatwg/fetch] Change combined values (#813) (Tuesday, 16 October)
Re: [whatwg/dom] Upstream `delegatesFocus` property of ShadowRootInit from W3C spec. (#367) (Tuesday, 16 October)
Re: [whatwg/dom] Upstream `delegatesFocus` property of ShadowRootInit from W3C spec. (#367) (Tuesday, 16 October)
Re: [whatwg/fetch] "combined value" is wrong (#757) (Tuesday, 16 October)
Re: [whatwg/fetch] Change combined values (#813) (Tuesday, 16 October)
Re: [whatwg/fetch] Change combined values (#813) (Tuesday, 16 October)
Re: [whatwg/fetch] Change combined values (#813) (Monday, 15 October)
Re: [whatwg/url] How are hosts in custom schemes to be handled? (#418) (Monday, 15 October)
Re: [whatwg/url] How are hosts in custom schemes to be handled? (#418) (Monday, 15 October)
Re: [whatwg/url] Consider adding non-throwing URL.parse(input, base) (#372) (Monday, 15 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Monday, 15 October)
Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Monday, 15 October)
Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Monday, 15 October)
Re: [w3c/FileAPI] "Null"ing out the Origin of a BLOB (#74) (Monday, 15 October)
[w3c/ServiceWorker] Redesign of "extract header list values" expected (#1360) (Friday, 12 October)
[whatwg/fetch] Redesign "extract header values" and "extract header list values" (#814) (Friday, 12 October)
Re: [whatwg/fetch] What does "combined value" return for a name not in the header list? (#752) (Friday, 12 October)
Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Friday, 12 October)
Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Friday, 12 October)
Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Friday, 12 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [whatwg/fetch] Change combined values (#813) (Thursday, 11 October)
Re: [whatwg/fetch] Change combined values (#813) (Thursday, 11 October)
[whatwg/fetch] Change combined values (#813) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Thursday, 11 October)
Re: [whatwg/fetch] "combined value" is wrong (#757) (Thursday, 11 October)
Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Thursday, 11 October)
Re: [w3c/ServiceWorker] Order of messages to clients in same unit of related browsing contexts unclear (#1355) (Thursday, 11 October)
Re: [whatwg/encoding] Коды (#161) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Wednesday, 10 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Wednesday, 10 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Wednesday, 10 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Tuesday, 9 October)
Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Tuesday, 9 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Tuesday, 9 October)
Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Monday, 8 October)
Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Monday, 8 October)
Re: [whatwg/dom] Make NodeIterator Iterable (#704) (Monday, 8 October)
Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Monday, 8 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Monday, 8 October)
Re: [whatwg/dom] Make NodeIterator Iterable (#704) (Monday, 8 October)
Re: [whatwg/dom] Make NodeIterator Iterable (#704) (Monday, 8 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)
Re: [w3c/webcomponents] HTML module should require a new MIME type (#742) (Friday, 5 October)
Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Friday, 5 October)
Re: [heycam/webidl] Intent to use Constants (#587) (Friday, 5 October)
Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Friday, 5 October)
Re: [whatwg/xhr] Spell out implicit serialization (#223) (Thursday, 4 October)
Re: [whatwg/fetch] Check Feature Policy before attaching Client Hints (#811) (Tuesday, 2 October)
Re: [w3ctag/design-reviews] Tag Review Request: Canvas TextMetrics (#302) (Tuesday, 2 October)
Re: [whatwg/xhr] Do not reset override MIME type (#218) (Monday, 1 October)
Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Monday, 1 October)
Re: [whatwg/encoding] bind encoder to self (#159) (Monday, 1 October)
Re: [whatwg/encoding] Bad (#160) (Monday, 1 October)

Asa Kusuma

Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614) (Wednesday, 31 October)
Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614) (Wednesday, 31 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Wednesday, 31 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Wednesday, 31 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292) (Monday, 29 October)
Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331) (Monday, 29 October)
Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331) (Monday, 29 October)
Re: [w3c/ServiceWorker] Confusion around new events after skipWaiting (#1295) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Confusion around new events after skipWaiting (#1295) (Thursday, 25 October)
Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614) (Wednesday, 24 October)
Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614) (Wednesday, 24 October)
Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614) (Wednesday, 24 October)
Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292) (Sunday, 21 October)
Re: [w3c/ServiceWorker] Allow active worker to immediately evict itself (#1296) (Sunday, 21 October)
Re: [w3c/ServiceWorker] Confusion around new events after skipWaiting (#1295) (Wednesday, 10 October)
Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336) (Wednesday, 10 October)
Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336) (Wednesday, 10 October)

Asami

Re: [w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359) (Wednesday, 24 October)
Re: [w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359) (Wednesday, 24 October)
[w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359) (Thursday, 4 October)
[w3c/ServiceWorker] Should add “script type” and “update via cache” when check two jobs are equivalent. (#1358) (Thursday, 4 October)

Asanka Herath

Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Wednesday, 31 October)

Ashley (Scirra)

Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)

Ben Kelly

[w3ctag/design-reviews] FetchEvent Worker Timing (#317) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331) (Monday, 29 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 29 October)
Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331) (Monday, 29 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Thursday, 25 October)
Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614) (Wednesday, 24 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Saturday, 20 October)
[w3c/ServiceWorker] clarify how navigation preload fetches can be measured using performance API (#1361) (Friday, 19 October)
Re: [w3c/ServiceWorker] Prevent opaque requests being used in response to client requests (#590) (Monday, 1 October)

Ben Smith

Re: [w3ctag/design-reviews] TAG review request: WebAssembly Threads (#299) (Tuesday, 2 October)

Benoit Girard

Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Friday, 26 October)

BigBlueHat

Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Wednesday, 31 October)

Bo Cupp

Re: [w3c/webcomponents] HTML Modules (#645) (Tuesday, 23 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Monday, 22 October)

Boris Zbarsky

Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Friday, 26 October)
Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Thursday, 25 October)
Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Friday, 19 October)
Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Thursday, 18 October)
Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Thursday, 18 October)
Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Monday, 1 October)

C. Van Wiemeersch

Re: [w3c/gamepad] spec `gamepadbuttondown` and `gamepadbuttonup` events (issue #4) (#15) (Monday, 22 October)

Cabdiqaadir Barwaaqo

[heycam/webidl] Intent to use Constants (#587) (Thursday, 4 October)

Caridy Patiño

Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769) (Tuesday, 30 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Friday, 26 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 26 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 25 October)
Re: [w3c/webcomponents] Custom pseudo-classes for host elements via shadow roots (:state) (#738) (Wednesday, 24 October)
Re: [whatwg/dom] Upstream `delegatesFocus` property of ShadowRootInit from W3C spec. (#367) (Monday, 15 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Wednesday, 10 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Tuesday, 9 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Monday, 8 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Sunday, 7 October)

Carter Li

Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769) (Wednesday, 31 October)
Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769) (Tuesday, 30 October)
Re: [w3c/webcomponents] JSON "modules" (#770) (Monday, 29 October)
Re: [w3c/webcomponents] JSON "modules" (#770) (Monday, 29 October)
Re: [w3c/webcomponents] JSON "modules" (#770) (Monday, 29 October)
Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769) (Monday, 29 October)
Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769) (Monday, 29 October)
Re: [w3c/webcomponents] CSS Modules (#759) (Monday, 29 October)
Re: [w3c/webcomponents] CSS Modules (#759) (Saturday, 27 October)
[w3c/webcomponents] Provide an option which allows global CSSes styling elements inside a shadow tree (#769) (Saturday, 27 October)
Re: [w3c/webcomponents] CSS Modules (#759) (Saturday, 27 October)

chaals

Re: [w3c/webcomponents] Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? (#762) (Friday, 26 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 25 October)
Re: [w3c/DOM-Parsing] Time at TPAC? (#27) (Monday, 22 October)
Re: [w3c/DOM-Parsing] Time at TPAC? (#27) (Monday, 22 October)
Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763) (Wednesday, 3 October)

Charles Samborski

Re: [whatwg/url] Do not remove newline and tab characters (#419) (Wednesday, 17 October)
[whatwg/url] Do not remove newline and tab characters (#419) (Tuesday, 16 October)

chcunningham

Re: [w3ctag/design-reviews] Media Capabilities (#218) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Media Capabilities (#218) (Wednesday, 31 October)

Chris Mills

Re: [whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710) (Wednesday, 31 October)
Re: [whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710) (Tuesday, 30 October)

Chris Wilson

Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 18 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 18 October)
Re: [w3ctag/design-reviews] Review request for WebVR (#185) (Thursday, 4 October)

cliff denney

[whatwg/dom] tr (#709) (Monday, 22 October)

Cuuhootohanoisos

Re: [whatwg/dom] Meta: define merge policy and add CONTRIBUTING.md (676fcbe) (Wednesday, 31 October)

cynthia

Re: [w3ctag/design-reviews] Carriage of Web Resource in ISOBMFF (#285) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Spatial Navigation (#287) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Background fetch (#279) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Async local storage (#278) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Carriage of Web Resource in ISOBMFF (#285) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Carriage of Web Resource in ISOBMFF (#285) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Sensor APIs (#207) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Sensor APIs (#207) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Media Capabilities (#218) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Media Capabilities (#218) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Support codec and container switching with MSE using SourceBuffer.changeType() (#298) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Support codec and container switching with MSE using SourceBuffer.changeType() (#298) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] HTML General Review: HTML Ruby (#248) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Sensor APIs (#207) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Request Review: Gesture Delegation (#199) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253) (Monday, 29 October)
Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253) (Monday, 29 October)
Re: [w3ctag/design-reviews] TAG Review Request: Support codec and container switching with MSE using SourceBuffer.changeType() (#298) (Tuesday, 9 October)
Re: [w3ctag/design-reviews] TAG Review Request: RTCIceTransport (#304) (Tuesday, 9 October)
Re: [w3ctag/design-reviews] TAG Review Request: RTCQuicTransport (#303) (Tuesday, 9 October)

Cyril Concolato

Re: [w3ctag/design-reviews] Carriage of Web Resource in ISOBMFF (#285) (Wednesday, 31 October)

Dan Clark

Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 25 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Saturday, 6 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 4 October)

Daniel Appelquist

Re: [w3ctag/design-reviews] `sec-metadata` (#280) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] HTTP State Tokens (#297) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] User Activation API (#300) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Screen Capture API (#309) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Screen Capture API (#309) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Review MathML (#313) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Web Components Guidelines Doc? (#227) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Web Components Guidelines Doc? (#227) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Review request for WebVR (#185) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Clear Site Data (#62) (Tuesday, 30 October)

Daniel Ehrenberg

Re: [w3ctag/design-reviews] JavaScript Decorators (#314) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 31 October)
[w3ctag/design-reviews] TAG Review Request: JavaScript Decorators (#314) (Monday, 29 October)
Re: [w3ctag/design-reviews] Review MathML (#313) (Monday, 29 October)
[w3ctag/design-reviews] Tag Review Request: Temporal proposal (#311) (Saturday, 27 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Saturday, 27 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 25 October)
Re: [heycam/webidl] Should "perform some steps once a promise is settled" use %PromiseProto_then%? (#583) (Monday, 22 October)
Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526) (Saturday, 20 October)

Daniel Murphy

Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Monday, 22 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Monday, 22 October)

Dark-Dredd

[whatwg/encoding] Коды (#161) (Wednesday, 10 October)

Dave Rupert

Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)

Dave Tapuska

Re: [w3ctag/design-reviews] User Activation API (#300) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344) (Monday, 29 October)
Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91) (Wednesday, 17 October)
Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91) (Wednesday, 17 October)
Re: [w3ctag/design-reviews] TAG Review Request: User Activation API (#300) (Tuesday, 2 October)

David Duarte

Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Friday, 26 October)

David Singer

Re: [w3ctag/design-reviews] Carriage of Web Resource in ISOBMFF (#285) (Wednesday, 31 October)

dfabulich

Re: [w3c/ServiceWorker] serviceworker.skipWaiting (#1016) (Monday, 29 October)
Re: [w3c/ServiceWorker] [Proposal] ServiceWorkerContainer.installing(scope) promise (#1364) (Monday, 29 October)
Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222) (Wednesday, 24 October)

Dirk Schulze

Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Friday, 26 October)

Domenic Denicola

Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 31 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 31 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 31 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Monday, 29 October)
Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344) (Friday, 26 October)
[w3c/ServiceWorker] "waiting for all" definition changed (#1363) (Friday, 26 October)
Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Friday, 26 October)
Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74) (Friday, 26 October)
Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74) (Friday, 26 October)
Re: [whatwg/xhr] Ecommerce Websites (#226) (Thursday, 25 October)
Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760) (Thursday, 25 October)
Re: [whatwg/dom] tr (#709) (Monday, 22 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Monday, 22 October)
Re: [w3c/DOM-Parsing] DOMParser's parseFromString should have CEReactions (#22) (Monday, 22 October)
Re: [w3c/DOM-Parsing] Serialization algorithm never preserves attribute prefixes (#29) (Monday, 22 October)
Re: [w3c/DOM-Parsing] Fragment serialization algorithm serializes node itself (#28) (Monday, 22 October)
Re: [w3c/DOM-Parsing] Define the origin of the documents returned from DOMParser (#24) (Monday, 22 October)
Re: [w3c/DOM-Parsing] innerHTML should be defined on ShadowRoot interface in addition to Element interface (#21) (Monday, 22 October)
Re: [w3c/DOM-Parsing] How should createContextualFragment interact with `<script>` inside `<template>`? (#19) (Monday, 22 October)
Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Thursday, 18 October)
Re: [whatwg/streams] WHATWG icon is broken in Chrome in combination with ServiceWorker (#955) (Thursday, 18 October)
Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Thursday, 18 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Wednesday, 17 October)
[w3c/clipboard-apis] IDL doesn't link correctly (#83) (Wednesday, 17 October)
Re: [whatwg/xhr] cant login to porn (#225) (Tuesday, 16 October)
Re: [whatwg/xhr] Limit Content-Type overrides to when charset isn't already UTF-8 (#224) (Tuesday, 16 October)
Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767) (Monday, 15 October)
Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767) (Monday, 15 October)
Re: [whatwg/dom] async disconnectedCallback? (#705) (Sunday, 14 October)
Re: [whatwg/dom] async disconnectedCallback? (#705) (Sunday, 14 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [whatwg/streams] Meta: fix realm issues in reference implementation testing setup (#957) (Friday, 12 October)
Re: [whatwg/streams] Add explainer for transferable streams (#956) (Thursday, 11 October)
[whatwg/streams] Meta: fix realm issues in reference implementation testing setup (#957) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Thursday, 11 October)
Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Thursday, 11 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Wednesday, 10 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Wednesday, 10 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Wednesday, 10 October)
Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Monday, 8 October)
Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Monday, 8 October)
Re: [whatwg/streams] A couple Bikeshed warnings (#929) (Friday, 5 October)
Re: [whatwg/streams] A couple Bikeshed warnings (#929) (Friday, 5 October)
Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa) (Friday, 5 October)
Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa) (Friday, 5 October)
Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa) (Friday, 5 October)
Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa) (Thursday, 4 October)
Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa) (Thursday, 4 October)
Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa) (Thursday, 4 October)
Re: [whatwg/dom] MohammedNoh (#703) (Monday, 1 October)

Dominic Farolino

Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821) (Monday, 29 October)

Dominick Ng

Re: [w3c/manifest] MIME type in HTML <link type="application/manifest+json" rel="manifest"> (#721) (Friday, 5 October)
Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Friday, 5 October)
Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Thursday, 4 October)

Dominique Hazael-Massieux

Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74) (Friday, 26 October)

Dr. Ken Lunde

Re: [whatwg/encoding] If gb18030 is revised, consider aligning the Encoding Standard (#27) (Monday, 22 October)

dshepsis

Re: [whatwg/dom] Make NodeIterator Iterable (#704) (Monday, 8 October)
[whatwg/dom] Make NodeIterator Iterable (#704) (Sunday, 7 October)

Ella Ge

Re: [w3c/touch-events] Remove createTouch and createTouch list (#96) (Friday, 12 October)

Emilio Cobos Álvarez

Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769) (Monday, 29 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 18 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 18 October)

Emircan Uysaler

[w3ctag/design-reviews] TAG Review Request: Screen Capture API (#309) (Tuesday, 9 October)

EnnexMB

Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Monday, 8 October)
Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Monday, 8 October)
Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Monday, 8 October)
Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Monday, 8 October)
Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Monday, 8 October)
Re: [whatwg/url] Add a neato informative table of various URL pieces (#337) (Friday, 5 October)

Eric Willigers

Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Thursday, 25 October)

Erik Hellman

Re: [w3ctag/design-reviews] Screen Capture API (#309) (Wednesday, 31 October)

fanbinghuadev

Felix Becker

Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Monday, 15 October)
Re: [whatwg/url] How are hosts in custom schemes to be handled? (#418) (Monday, 15 October)
Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Sunday, 14 October)
Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Sunday, 14 October)
Re: [whatwg/url] Consider adding non-throwing URL.parse(input, base) (#372) (Sunday, 14 October)
[whatwg/url] How are hosts in custom schemes to be handled? (#418) (Sunday, 14 October)

Fernando Serboncini

[w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) (Tuesday, 30 October)

Frank Topel

Re: [whatwg/dom] Custom element callback/promise for "connected and parsed" (#662) (Tuesday, 23 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Sunday, 21 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Saturday, 20 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Saturday, 20 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Saturday, 20 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Friday, 19 October)
Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 19 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 18 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Wednesday, 17 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Sunday, 14 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)

freshp86

Re: [whatwg/dom] A faster way to find open shadow roots (or shadow hosts) (#665) (Thursday, 25 October)

Frédéric Wang

Re: [w3ctag/design-reviews] Review MathML (#313) (Tuesday, 30 October)

Fuqiao Xue

Re: [w3c/screen-orientation] Add interaction with WCAG 2.1 (#117) (Friday, 12 October)
Re: [w3c/screen-orientation] Add interaction with WCAG 2.1 (#117) (Friday, 12 October)
Re: [w3c/screen-orientation] Lacks a privacy and security consideration section (#96) (Friday, 12 October)
Re: [w3c/screen-orientation] Lacks a privacy and security consideration section (#96) (Friday, 12 October)
Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115) (Friday, 12 October)
Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115) (Friday, 12 October)
Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115) (Friday, 12 October)

Gary Kacmarcik

Re: [w3c/editing] Move execCommand to WICG (#184) (Saturday, 27 October)
Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74) (Friday, 26 October)
Re: [w3c/uievents] Need algorithm for how mouse events are fired (#196) (Wednesday, 24 October)
[w3c/editing] Need API for retrieving/providing geometry of editing UI (#183) (Tuesday, 23 October)
[w3c/editing] Browsers should help in maximising the available space (#182) (Tuesday, 23 October)
Re: [w3c/editing] Need spec for how HTML is serialized to be placed on the clipboard (#181) (Tuesday, 23 October)
Re: [w3c/editing] Need spec for how HTML is serialized to be placed on the clipboard (#181) (Tuesday, 23 October)
Re: [w3c/editing] Need spec for how HTML is serialized to be placed on the clipboard (#181) (Tuesday, 23 October)
[w3c/editing] Need spec for how HTML is serialized to be placed on the clipboard (#181) (Tuesday, 23 October)
Re: [w3c/uievents] Consider to make mouseenter/leave (and pointerenter/leave) uncomposed (#208) (Thursday, 18 October)

Geoffrey Sneddon

Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 18 October)

Gerard Davison

[w3c/ServiceWorker] Should CacheStorage.match allow partial matches on cache names? (#1357) (Wednesday, 3 October)

gked

Re: [w3c/editing] Move execCommand to WICG (#184) (Monday, 29 October)
Re: [w3c/editing] Move execCommand to WICG (#184) (Monday, 29 October)
Re: [w3c/editing] Move execCommand to WICG (#184) (Friday, 26 October)
Re: [w3c/editing] Should contenteditable have break-word behavior by default? (#145) (Wednesday, 24 October)
Re: [w3c/editing] Should browsers support ContentEditable for <option> elements? (#180) (Tuesday, 23 October)
Re: [w3c/editing] contenteditable-disabled (#176) (Friday, 5 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Friday, 5 October)
Re: [w3c/editing] spellching - how to give JS devs more control (#166) (Wednesday, 3 October)
Re: [w3c/editing] contenteditable-disabled (#176) (Wednesday, 3 October)

Goffert van Gool

Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767) (Monday, 15 October)
Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767) (Monday, 15 October)
Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767) (Monday, 15 October)
Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767) (Monday, 15 October)
[w3c/webcomponents] Unspecified behaviour with regards to attributeChangedCallback and DOM access (#767) (Sunday, 14 October)

Gordon P. Hemsley

Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Sunday, 28 October)

Gus Caplan

Re: [whatwg/url] Do not remove newline and tab characters (#419) (Tuesday, 16 October)
Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954) (Thursday, 4 October)

Hadley Beeman

Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] RTCIceTransport (#304) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Privacy Mode (#101) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Request Formal Review of Vehicle Information Service Specification (VISS) CR (#234) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Monday, 29 October)

Harald Alvestrand

Re: [w3ctag/design-reviews] TAG Review Request: RTCIceTransport (#304) (Tuesday, 2 October)

Hayato Ito

Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769) (Tuesday, 30 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Wednesday, 24 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Wednesday, 24 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 23 October)
Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763) (Monday, 22 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 17 October)

Hiroki Nakagawa

Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Tuesday, 30 October)

Ian Storm Taylor

Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)

Ibrahim Tanyalcin

iecompattest

Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Wednesday, 24 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Wednesday, 24 October)

irhadkul

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

Ivan Herman

Jackson Loper

Re: [w3c/FileAPI] "Null"ing out the Origin of a BLOB (#74) (Monday, 15 October)

Jacob Bearce

Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Monday, 29 October)
Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Friday, 5 October)
Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Wednesday, 3 October)

Jake Archibald

Re: [w3ctag/design-reviews] Background fetch (#279) (Wednesday, 31 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Thursday, 25 October)
Re: [w3c/ServiceWorker] is the browser required to start the ServiceWorker for postMessage() if there is no message event handler? (#1200) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Thursday, 25 October)
Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204) (Thursday, 25 October)
Re: [w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362) (Thursday, 25 October)
Re: [w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362) (Thursday, 25 October)
Re: [w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362) (Thursday, 25 October)
Re: [w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Tuesday, 23 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Tuesday, 23 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Tuesday, 23 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Tuesday, 23 October)
Re: [whatwg/dom] Improving ergonomics of events with Observable (#544) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Monday, 22 October)
Re: [w3c/ServiceWorker] Clean up Clients interface methods (#1332) (Thursday, 4 October)
Re: [w3c/ServiceWorker] Add Client.frameType back (#1329) (Thursday, 4 October)
Re: [w3c/ServiceWorker] Make Client.postMessage to unloaded client not throw (#1293) (Thursday, 4 October)
Re: [w3c/ServiceWorker] Use ASCII serialization for origins (#1151) (Thursday, 4 October)

James Browning

Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 26 October)

James M Snell

Re: [whatwg/url] Do not remove newline and tab characters (#419) (Wednesday, 17 October)

Jan Miksovsky

Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 16 October)

Jan Olaf Krems

Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)

Jan-Ivar Bruaroey

Re: [w3c/permissions] Allow Feature Policy-based permission models (#185) (Sunday, 21 October)
Re: [w3c/permissions] Allow Feature Policy-based permission models (#185) (Sunday, 21 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Saturday, 20 October)
Re: [w3c/permissions] A new permission for screen-sharing with getDisplayMedia() (#182) (Thursday, 18 October)
[w3c/permissions] Allow Feature Policy-based permission models (#185) (Wednesday, 17 October)
Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Tuesday, 16 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Friday, 12 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Friday, 12 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Friday, 12 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Friday, 12 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Friday, 12 October)
[w3c/permissions] Add 'display' permission for screen-capture. (#184) (Thursday, 11 October)
Re: [w3c/permissions] Add support for permissions that have an associated Feature Policy (#163) (Thursday, 11 October)

Javier Fernandez Garcia-Boente

Re: [w3c/editing] Should a styled paragraph maintain its own style when inserting it in a list ? (#179) (Monday, 22 October)
Re: [w3c/editing] Should a styled paragraph maintain its own style when inserting it in a list ? (#179) (Monday, 22 October)

Jdragon

Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34) (Monday, 15 October)

Jeffrey Posnick

Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Monday, 29 October)
Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222) (Wednesday, 24 October)

jfrazzano

Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Saturday, 13 October)

Jimmy Wärting

Re: [whatwg/encoding] bind encoder to self (#159) (Wednesday, 17 October)

Jitendra Kumar Pal

Re: [w3c/ServiceWorker] Prevent opaque requests being used in response to client requests (#590) (Monday, 1 October)

Johanna

Re: [w3c/screen-orientation] Fix ReSpec errors (#122) (Tuesday, 16 October)
Re: [w3c/screen-orientation] Fix ReSpec errors (#122) (Tuesday, 16 October)
Re: [w3c/screen-orientation] Fix ReSpec errors (#122) (Tuesday, 16 October)
Re: [w3c/screen-orientation] Steps for updating orientation information are misleading (#100) (Sunday, 14 October)
Re: [w3c/screen-orientation] Fix ReSpec errors (#122) (Saturday, 13 October)
[w3c/screen-orientation] Fix ReSpec errors (#122) (Friday, 12 October)
Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115) (Friday, 12 October)
[w3c/screen-orientation] Edit Privacy and Security Consideration Section (#121) (Thursday, 11 October)

Johannes Wilm

Re: [w3c/editing] copy/cut and text-transform (#178) (Tuesday, 23 October)
Re: [w3c/editing] copy/cut and text-transform (#178) (Tuesday, 23 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] contenteditable-disabled (#176) (Wednesday, 3 October)
Re: [w3c/editing] contenteditable-disabled (#176) (Wednesday, 3 October)

Joshua Bell

Re: [w3c/IndexedDB] Add IDBFactory/databases() (#240) (Tuesday, 30 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Monday, 15 October)
[w3c/FileAPI] Add implementation report link. For issue #111 (#112) (Monday, 15 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)

juj

Re: [w3c/pointerlock] Option needed to disable OS-level adjustment for mouse acceleration (#36) (Wednesday, 10 October)

Jungkee Song

Re: [w3c/ServiceWorker] Clean up Clients interface methods (#1332) (Friday, 19 October)
Re: [w3c/ServiceWorker] Clean up Clients interface methods (#1332) (Friday, 19 October)
Re: [w3c/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Friday, 19 October)
Re: [w3c/ServiceWorker] Add Client.frameType back (#1329) (Friday, 19 October)

Justin Fagnani

Re: [w3c/webcomponents] CSS Modules (#759) (Monday, 29 October)
Re: [w3c/webcomponents] CSS Modules (#759) (Saturday, 27 October)
Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Thursday, 25 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Wednesday, 17 October)
Re: [w3c/webcomponents] @trusktr you're not returning the right object from the constructor. You're creating an HTMLElement, then implicitly returning MyEl, which is not an HTMLElement. Regardless of setting the prototype and what `instanceof` says, it doesn't wrap a native element object like HTMLElement does. (#766) (Monday, 8 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)

jvanbec

Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Friday, 12 October)

kael

Re: [w3c/manifest] MIME type in HTML <link type="application/manifest+json" rel="manifest"> (#721) (Friday, 5 October)
[w3c/manifest] MIME type in HTML <link type="application/manifest+json" rel="manifest"> (#721) (Friday, 5 October)

Kagami Sascha Rosylight

[whatwg/fetch] Deduplicate 'the' (#822) (Wednesday, 31 October)
[whatwg/dom] Remove redundant <dd> (#712) (Sunday, 28 October)

Ken Russell

Re: [w3ctag/design-reviews] OffscreenCanvas new commit() and DedicatedWorker.requestAnimationFrame (#288) (Wednesday, 31 October)

Kenneth Rohde Christiansen

Re: [w3ctag/design-reviews] User Activation API (#300) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Screen Capture API (#309) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Screen Capture API (#309) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] JavaScript Decorators (#314) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Display Locking (#306) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Layered APIs (#276) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Constructable Stylesheets (#308) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Constructable Stylesheets (#308) (Tuesday, 30 October)
Re: [w3c/manifest] [chore] Fix id of Icon masks section. (#725) (Wednesday, 10 October)
Re: [w3c/manifest] Added new definition "within scope of a manifest". (#724) (Tuesday, 9 October)
Re: [w3c/manifest] [chore] Fix normative references in informative sections (#723) (Tuesday, 9 October)
Re: [w3c/manifest] [chore] Run tidy on new icon masking section. (#722) (Tuesday, 9 October)

Koji Ishii

Re: [w3c/editing] Should contenteditable have break-word behavior by default? (#145) (Thursday, 25 October)

L. David Baron

Re: [w3ctag/design-reviews] HTTP State Tokens (#297) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] HTTP State Tokens (#297) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] User Activation v2 (#295) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] User Activation v2 (#295) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] HTTP State Tokens (#297) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] User Activation API (#300) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Canvas TextMetrics (#302) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Canvas TextMetrics (#302) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] WebUSB on Dedicated and Shared Workers (#277) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] WebUSB on Dedicated and Shared Workers (#277) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Canvas TextMetrics (#302) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] User Activation v2 (#295) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Monday, 29 October)
Re: [w3ctag/design-reviews] TAG Review Request: RTCIceTransport (#304) (Saturday, 20 October)
Re: [w3ctag/design-reviews] TAG review request: User Activation v2 (#295) (Saturday, 20 October)
Re: [w3ctag/design-reviews] Tag Review Request: Canvas TextMetrics (#302) (Monday, 8 October)
Re: [w3ctag/design-reviews] Tag Review Request: Canvas TextMetrics (#302) (Monday, 8 October)
Re: [w3ctag/design-reviews] Tag Review Request: Canvas TextMetrics (#302) (Tuesday, 2 October)

Leo7k

Re: [w3c/editing] Should browsers support ContentEditable for <option> elements? (#180) (Saturday, 27 October)
Re: [w3c/editing] Should browsers support ContentEditable for <option> elements? (#180) (Saturday, 27 October)
[w3c/editing] Should browsers support ContentEditable for <option> elements? (#180) (Saturday, 20 October)

Lukasz Olejnik

Re: [w3ctag/design-reviews] Review Request: Priority Hints API (#241) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] TAG Review Request: HTTP State Tokens (#297) (Friday, 12 October)

Luke Wagner

Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 31 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 31 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 31 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 31 October)
Re: [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367) (Tuesday, 30 October)
[w3c/ServiceWorker] Tee-ing Cache.put()? (#1367) (Tuesday, 30 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Tuesday, 30 October)

Léonie Watson

Re: [w3c/editing] Move execCommand to WICG (#184) (Saturday, 27 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Friday, 19 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Friday, 19 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Friday, 19 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 18 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Tuesday, 16 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Sunday, 14 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Tuesday, 2 October)

Malte Ubl

Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Wednesday, 17 October)

Malthe Jørgensen

Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Friday, 12 October)
Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Friday, 12 October)
Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Friday, 12 October)
Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Thursday, 11 October)

Manu Sporny

Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Monday, 29 October)

Marco Colli

[w3c/push-api] Make PushSubscription.expirationTime mandatory (#302) (Monday, 1 October)

Marcos Cáceres

Re: [w3c/editing] Move execCommand to WICG (#184) (Monday, 29 October)
Re: [w3c/editing] Move execCommand to WICG (#184) (Monday, 29 October)
Re: [w3c/editing] Move execCommand to WICG (#184) (Monday, 29 October)
[w3c/editing] Move execCommand to WICG (#184) (Friday, 26 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Friday, 26 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Friday, 26 October)
Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Thursday, 25 October)
Re: [w3c/webcomponents] <iframe> and the History API (#184) (Thursday, 25 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Friday, 19 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 18 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 18 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 18 October)
Re: [w3c/gamepad] Cleanup (#84) (Wednesday, 17 October)
Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68) (Wednesday, 17 October)
Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68) (Wednesday, 17 October)
Re: [w3c/gamepad] spec `gamepadbuttondown` and `gamepadbuttonup` events (issue #4) (#15) (Wednesday, 17 October)
Re: [w3c/gamepad] Cleanup (#84) (Wednesday, 17 October)
Re: [w3c/gamepad] Fix Promise type (#78) (Wednesday, 17 October)
Re: [w3c/gamepad] Fix Promise type (#78) (Wednesday, 17 October)
Re: [w3c/screen-orientation] Fix ReSpec errors (#122) (Wednesday, 17 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Tuesday, 16 October)
Re: [w3c/screen-orientation] Fix ReSpec errors (#122) (Tuesday, 16 October)
Re: [w3c/screen-orientation] Fix ReSpec errors (#122) (Tuesday, 16 October)
Re: [w3c/gamepad] Cleanup (#84) (Tuesday, 16 October)
Re: [w3c/gamepad] Cleanup (#84) (Tuesday, 16 October)
Re: [w3c/gamepad] fix inline refs (#81) (Tuesday, 16 October)
Re: [w3c/gamepad] fix inline refs (#81) (Tuesday, 16 October)
[w3c/gamepad] Cleanup (#84) (Tuesday, 16 October)
Re: [w3c/screen-orientation] Fix ReSpec errors (#122) (Tuesday, 16 October)
Re: [w3c/FileAPI] Add implementation report link. For issue #111 (#112) (Monday, 15 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Monday, 15 October)
Re: [w3c/gamepad] fix inline refs (#81) (Sunday, 14 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Friday, 12 October)
Re: [w3c/screen-orientation] Fix ReSpec errors (#122) (Friday, 12 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115) (Friday, 12 October)
Re: [w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
[w3c/FileAPI] Implementer interest in this spec (#111) (Friday, 12 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Friday, 12 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Friday, 12 October)
Re: [w3c/screen-orientation] Add interaction with WCAG 2.1 (#117) (Friday, 12 October)
Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115) (Friday, 12 October)
Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115) (Friday, 12 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Friday, 12 October)
Re: [w3c/permissions] Add support for permissions that have an associated Feature Policy (#163) (Friday, 12 October)
Re: [w3c/permissions] Add support for permissions that have an associated Feature Policy (#163) (Friday, 12 October)
Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115) (Thursday, 11 October)
Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115) (Thursday, 11 October)
Re: [w3c/screen-orientation] Edit Privacy and Security Consideration Section (#121) (Thursday, 11 October)
Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115) (Thursday, 11 October)
Re: [w3c/screen-orientation] Edit Privacy and Security Consideration Section (#121) (Thursday, 11 October)
Re: [w3c/screen-orientation] Edit Privacy and Security Consideration Section (#121) (Thursday, 11 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 11 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 11 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 11 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 11 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 11 October)
Re: [w3c/manifest] Breaking: Change requirement to block off-scope navigation. (#701) (Tuesday, 9 October)

Marijn Kruisselbrink

Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Monday, 22 October)
Re: [w3c/FileAPI] Add implementation report link. For issue #111 (#112) (Tuesday, 16 October)
Re: [w3c/FileAPI] Add implementation report link. For issue #111 (#112) (Tuesday, 16 October)
Re: [w3c/FileAPI] "Null"ing out the Origin of a BLOB (#74) (Monday, 15 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Wednesday, 10 October)
Re: [w3c/ServiceWorker] Order of messages to clients in same unit of related browsing contexts unclear (#1355) (Wednesday, 10 October)
Re: [w3c/FileAPI] Fix "undefined" reference in parsable MIME type Note (#110) (Thursday, 4 October)
Re: [w3c/FileAPI] Fix "undefined" reference in parsable MIME type Note (#110) (Thursday, 4 October)
Re: [w3c/FileAPI] Fix "undefined" reference in parsable MIME type Note (#110) (Thursday, 4 October)

Mark Kennedy

[whatwg/dom] async disconnectedCallback? (#705) (Sunday, 14 October)

Mark Vickers

Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105) (Tuesday, 30 October)

Martin Thomson

Re: [w3c/push-api] Make PushSubscription.expirationTime mandatory (#302) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] RTCIceTransport (#304) (Wednesday, 31 October)

Matt Bell

Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) (Monday, 22 October)

Matt Falkenhagen

Re: [w3c/ServiceWorker] Clarify "uncaught runtime script error". (#1346) (Wednesday, 31 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Wednesday, 31 October)
Re: [w3c/ServiceWorker] Clarify "uncaught runtime script error". (#1346) (Wednesday, 31 October)
Re: [w3c/ServiceWorker] Clarify "uncaught runtime script error". (#1346) (Wednesday, 31 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Wednesday, 31 October)
Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Monday, 29 October)
Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Saturday, 27 October)
Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292) (Saturday, 27 October)
Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Friday, 26 October)
Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Friday, 26 October)
Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Friday, 26 October)
Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Friday, 26 October)
Re: [w3c/ServiceWorker] cache.match should create partial responses if given a range request (#913) (Friday, 26 October)
Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331) (Friday, 26 October)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Friday, 26 October)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Friday, 26 October)
Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189) (Friday, 26 October)
Re: [w3c/ServiceWorker] ready promise is kind of weird after you call unregister() (#1279) (Friday, 26 October)
Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Friday, 26 October)
Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 26 October)
Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336) (Thursday, 25 October)
Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336) (Wednesday, 24 October)
Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336) (Wednesday, 24 October)
Re: [w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359) (Wednesday, 24 October)
Re: [w3c/ServiceWorker] Confusion around new events after skipWaiting (#1295) (Thursday, 11 October)
Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292) (Wednesday, 10 October)
Re: [w3c/ServiceWorker] Confusion around new events after skipWaiting (#1295) (Wednesday, 10 October)
Re: [w3c/ServiceWorker] Does ServiceWorkerContainer.onmessage also get ExtendableMessageEvent object? (#1301) (Wednesday, 10 October)
Re: [w3c/ServiceWorker] Is resultingClientId preserved over redirects? (#1316) (Wednesday, 10 October)
Re: [w3c/ServiceWorker] Is resultingClientId preserved over redirects? (#1316) (Wednesday, 10 October)
Re: [w3c/ServiceWorker] importScripts() on ServiceWorkerGlobalScope (#1319) (Wednesday, 10 October)
Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336) (Wednesday, 10 October)
Re: [w3c/ServiceWorker] Order of messages to clients in same unit of related browsing contexts unclear (#1355) (Wednesday, 10 October)
Re: [w3c/ServiceWorker] Should add “script type” and “update via cache” when check two jobs are equivalent. (#1358) (Friday, 5 October)
Re: [w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359) (Friday, 5 October)
[w3ctag/design-reviews] TAG Review Request: FetchEvent.resultingClientId (#307) (Monday, 1 October)

Matt Giuca

Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 25 October)
[w3c/manifest] Icon matching algorithm: unrecognised purposes can result in "any" (#728) (Thursday, 25 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Friday, 19 October)
Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Wednesday, 17 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Thursday, 11 October)
Re: [w3c/manifest] Install button on another domain (#726) (Thursday, 11 October)
Re: [w3c/manifest] [chore] Fix id of Icon masks section. (#725) (Wednesday, 10 October)
Re: [w3c/manifest] [chore] Fix id of Icon masks section. (#725) (Wednesday, 10 October)
[w3c/manifest] [chore] Fix id of Icon masks section. (#725) (Wednesday, 10 October)
Re: [w3c/manifest] Added new definition "within scope of a manifest". (#724) (Tuesday, 9 October)
Re: [w3c/manifest] [chore] Fix normative references in informative sections (#723) (Tuesday, 9 October)
Re: [w3c/manifest] [chore] Run tidy on new icon masking section. (#722) (Tuesday, 9 October)
[w3c/manifest] Added new definition "within scope of a manifest". (#724) (Tuesday, 9 October)
[w3c/manifest] [chore] Fix normative references in informative sections (#723) (Tuesday, 9 October)
[w3c/manifest] [chore] Run tidy on new icon masking section. (#722) (Tuesday, 9 October)
Re: [w3c/manifest] Breaking: Change requirement to block off-scope navigation. (#701) (Tuesday, 9 October)
Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646) (Tuesday, 9 October)
Re: [w3c/manifest] Breaking: Change requirement to block off-scope navigation. (#701) (Tuesday, 9 October)
Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Monday, 8 October)
Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Thursday, 4 October)
Re: [w3c/manifest] Icon shapes and masking (#555) (Thursday, 4 October)
Re: [w3c/manifest] Icon shapes and masking (#555) (Thursday, 4 October)
Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Monday, 1 October)
Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Monday, 1 October)

Matt Johnson

Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 31 October)

Matt Menke

Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Wednesday, 31 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Tuesday, 30 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Tuesday, 30 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Tuesday, 30 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Tuesday, 23 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Friday, 19 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Thursday, 18 October)
Re: [whatwg/fetch] Change combined values (#813) (Tuesday, 16 October)
Re: [whatwg/fetch] Change combined values (#813) (Monday, 15 October)
Re: [whatwg/fetch] Change combined values (#813) (Friday, 12 October)

Matthew Phillips

Re: [w3c/webcomponents] JSON "modules" (#770) (Monday, 29 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 25 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 25 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)

Mattias Buelens

Re: [whatwg/streams] Add explainer for transferable streams (#956) (Wednesday, 10 October)

Michael[tm] Smith

Re: [whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710) (Wednesday, 31 October)
Re: [w3c/FileAPI] Add implementation report link. For issue #111 (#112) (Tuesday, 16 October)

Mike West

Re: [w3ctag/design-reviews] HTTP State Tokens (#297) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] HTTP State Tokens (#297) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] `sec-metadata` (#280) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] HTTP State Tokens (#297) (Wednesday, 31 October)
Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755) (Friday, 26 October)
[whatwg/fetch] Split `document` destination for top-level and nested contexts. (#819) (Friday, 26 October)
Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755) (Wednesday, 24 October)
Re: [w3ctag/design-reviews] [TPAC][HTML General Review]: how to decide if workers are subresources or separate contexts (#310) (Tuesday, 23 October)
Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) (Thursday, 18 October)
Re: [w3ctag/design-reviews] `sec-metadata` (#280) (Tuesday, 16 October)
Re: [w3ctag/design-reviews] TAG Review Request: HTTP State Tokens (#297) (Friday, 12 October)
Re: [w3ctag/design-reviews] TAG Review Request: HTTP State Tokens (#297) (Thursday, 11 October)

MohammedNoh

Re: [whatwg/dom] MohammedNoh (#703) (Monday, 1 October)
Re: [whatwg/dom] MohammedNoh (#703) (Monday, 1 October)
[whatwg/dom] MohammedNoh (#703) (Monday, 1 October)

Mounir Lamouri

Re: [w3ctag/design-reviews] Gesture Delegation (#199) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Gesture Delegation (#199) (Wednesday, 31 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Tuesday, 16 October)
Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184) (Friday, 12 October)
Re: [w3c/screen-orientation] Edit Privacy and Security Consideration Section (#121) (Thursday, 11 October)

Muhammad Haris Baig

Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Saturday, 6 October)

Mustaq Ahmed

Re: [w3ctag/design-reviews] User Activation v2 (#295) (Tuesday, 30 October)

Navid Zolghadr

Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91) (Wednesday, 17 October)

Nick Fitzgerald

Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 31 October)
Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Monday, 29 October)

Nicole Saunders

[whatwg/fetch] Fixed typo (#823) (Wednesday, 31 October)

OvermindDL1

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

Patrick H. Lauke

Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91) (Wednesday, 17 October)
Re: [w3c/touch-events] Clarify cancelability during scroll (#79) (Wednesday, 17 October)
Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80) (Wednesday, 17 October)
Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80) (Wednesday, 17 October)
Re: [w3c/touch-events] update "Changes Since Last Publication" section (#101) (Wednesday, 17 October)
[w3c/touch-events] update "Changes Since Last Publication" section (#101) (Wednesday, 17 October)
Re: [w3c/touch-events] Remove note about initTouchEvent / createTouchList from the "5 TouchEvent Interface" section (#100) (Wednesday, 17 October)
[w3c/touch-events] Remove note about initTouchEvent / createTouchList from the "5 TouchEvent Interface" section (#100) (Wednesday, 17 October)

Peter Beverloo

Re: [w3c/push-api] Security policies WRT Push traffic (#270) (Friday, 26 October)
Re: [w3c/push-api] Security policies WRT Push traffic (#270) (Friday, 26 October)

Peter Linss

Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Constructable Stylesheets (#308) (Tuesday, 30 October)

Peter Snyder

Re: [w3ctag/design-reviews] Privacy Mode (#101) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Privacy Mode (#101) (Wednesday, 31 October)

Peter Thatcher

Re: [w3ctag/design-reviews] TAG Review Request: RTCIceTransport & RTCQuicTransport (#296) (Friday, 5 October)

Philip Jägenstedt

Re: [w3c/touch-events] Remove createTouch and createTouch list (#96) (Wednesday, 17 October)
Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34) (Monday, 15 October)
Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34) (Monday, 15 October)

Philip Walton

Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Monday, 29 October)
Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222) (Thursday, 25 October)

Philipp Dunkel

Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 31 October)

Philippe Le Hegaret

Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Wednesday, 24 October)

Photopea

[w3c/manifest] API for discovering details about browser heuristics. (#727) (Tuesday, 23 October)
Re: [w3c/manifest] Install button on another domain (#726) (Wednesday, 10 October)
[w3c/manifest] Install button on another domain (#726) (Wednesday, 10 October)

Piotrek Koszuliński

Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 4 October)
Re: [w3c/editing] contenteditable-disabled (#176) (Wednesday, 3 October)
Re: [w3c/editing] contenteditable-disabled (#176) (Wednesday, 3 October)

r12a

Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Wednesday, 31 October)

Rahat-3858

Re: [w3c/WebPlatformWG] Updates HTML F2F meeting info (b817ef3) (Tuesday, 16 October)
Re: [w3c/WebPlatformWG] Updates HTML F2F meeting info (b817ef3) (Tuesday, 16 October)

Rakina Zata Amni

Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Tuesday, 30 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 18 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 17 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 16 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 16 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 16 October)
[w3ctag/design-reviews] TAG Review Request: Constructable Stylesheets (#308) (Wednesday, 3 October)

raymeskhoury

Re: [w3c/permissions] Allow Feature Policy-based permission models (#185) (Friday, 19 October)

Reilly Grant

Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74) (Friday, 26 October)
Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74) (Friday, 26 October)
Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74) (Friday, 26 October)

Rhy Moore

Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Saturday, 20 October)

Rick Byers

Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80) (Wednesday, 17 October)
Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80) (Wednesday, 17 October)
Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80) (Wednesday, 17 October)
Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80) (Wednesday, 17 October)
Re: [w3c/touch-events] Remove createTouch and createTouch list (#96) (Wednesday, 17 October)

Rob Buis

[w3c/FileAPI] Fix "undefined" reference in parsable MIME type Note (#110) (Thursday, 4 October)
Re: [whatwg/xhr] Spell out implicit serialization (#223) (Thursday, 4 October)
Re: [whatwg/xhr] Spell out implicit serialization (#223) (Thursday, 4 October)
[whatwg/xhr] Spell out implicit serialization (#223) (Thursday, 4 October)

Rob Sanderson

Robert Linder

Re: [w3c/manifest] Add a way to query whether there is a UA-provided back button (#693) (Tuesday, 23 October)
Re: [w3c/manifest] Add a way to query whether there is a UA-provided back button (#693) (Tuesday, 23 October)

Ronny Rook

Re: [w3c/manifest] Allow for multiple scopes (#449) (Monday, 8 October)

Ryosuke Niwa

Re: [w3c/editing] Move execCommand to WICG (#184) (Monday, 29 October)
Re: [w3c/editing] Move execCommand to WICG (#184) (Monday, 29 October)
Re: [w3c/editing] Need spec for how HTML is serialized to be placed on the clipboard (#181) (Sunday, 28 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Friday, 26 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Friday, 26 October)
Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497) (Friday, 26 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Friday, 26 October)
Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760) (Thursday, 25 October)
Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760) (Thursday, 25 October)
Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760) (Thursday, 25 October)
Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 25 October)
Re: [w3c/webcomponents] <iframe> and the History API (#184) (Thursday, 25 October)
Re: [w3c/webcomponents] <iframe> and the History API (#184) (Thursday, 25 October)
Re: [w3c/DOM-Parsing] DOMParser's parseFromString should have CEReactions (#22) (Monday, 22 October)
Re: [w3c/DOM-Parsing] DOMParser's parseFromString should have CEReactions (#22) (Monday, 22 October)
Re: [w3c/DOM-Parsing] DOMParser's parseFromString should have CEReactions (#22) (Monday, 22 October)
Re: [w3c/DOM-Parsing] innerHTML should be defined on ShadowRoot interface in addition to Element interface (#21) (Monday, 22 October)
Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763) (Monday, 22 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 18 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 17 October)
Re: [w3c/selection-api] edge 中selection.focusOffset计算错误 (#97) (Wednesday, 17 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Wednesday, 17 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Monday, 15 October)
Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34) (Monday, 15 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Saturday, 13 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 12 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Friday, 12 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Friday, 12 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Wednesday, 10 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Wednesday, 10 October)
Re: [w3c/webcomponents] @trusktr you're not returning the right object from the constructor. You're creating an HTMLElement, then implicitly returning MyEl, which is not an HTMLElement. Regardless of setting the prototype and what `instanceof` says, it doesn't wrap a native element object like HTMLElement does. (#766) (Saturday, 6 October)
Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763) (Thursday, 4 October)
Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763) (Wednesday, 3 October)
Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763) (Wednesday, 3 October)
Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763) (Wednesday, 3 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Tuesday, 2 October)

Samuel Williams

Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 5 October)
Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Friday, 5 October)
Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Friday, 5 October)
Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Friday, 5 October)
Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Thursday, 4 October)
Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Thursday, 4 October)
Re: [whatwg/fetch] Request should allow WritableStream as body (#378) (Thursday, 4 October)

Sandro Hawke

Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Wednesday, 31 October)

Sebastian Mayr

Re: [w3c/DOM-Parsing] Fragment serialization algorithm serializes node itself (#28) (Monday, 22 October)

Sebastian Müller

Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Wednesday, 24 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Friday, 12 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Friday, 12 October)

Serhii Kulykov

Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 4 October)

slikts

Re: [whatwg/dom] Improving ergonomics of events with Observable (#544) (Monday, 22 October)

smaug----

Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821) (Monday, 29 October)
Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821) (Monday, 29 October)
[whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821) (Saturday, 27 October)
Re: [whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710) (Friday, 26 October)
Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760) (Thursday, 25 October)
Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 25 October)
[whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710) (Thursday, 25 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Wednesday, 24 October)
Re: [w3c/editing] Need API for retrieving/providing geometry of editing UI (#183) (Tuesday, 23 October)
Re: [w3c/DOM-Parsing] innerHTML should be defined on ShadowRoot interface in addition to Element interface (#21) (Monday, 22 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Tuesday, 16 October)
Re: [w3c/pointerlock] Option needed to disable OS-level adjustment for mouse acceleration (#36) (Tuesday, 2 October)

spanicker

Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821) (Monday, 29 October)

spinnuch

[whatwg/xhr] cant login to porn (#225) (Tuesday, 16 October)

Stef Busking

Re: [w3c/DOM-Parsing] Serialization algorithm never preserves attribute prefixes (#29) (Monday, 22 October)

Steve Agoston

Re: [w3c/gamepad] Obsolete dependencies (#79) (Thursday, 25 October)

Steve Phillips

Re: [w3c/ServiceWorker] Feature request: Provide a way to delay execution of a new service worker (#1208) (Wednesday, 24 October)

Sukhdew gupta

Re: [whatwg/xhr] Ecommerce Websites (#226) (Thursday, 25 October)
[whatwg/xhr] Ecommerce Websites (#226) (Thursday, 25 October)

sunnygoyal2

Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Thursday, 4 October)
Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Thursday, 4 October)
Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Monday, 1 October)

suns

Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 25 October)

Sérgio Faria

Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Friday, 12 October)

Tab Atkins Jr.

Re: [w3ctag/design-reviews] Constructable Stylesheets (#308) (Tuesday, 30 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Monday, 29 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Monday, 29 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Thursday, 25 October)
Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Monday, 22 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Monday, 22 October)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 18 October)
Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Monday, 1 October)

TAMURA, Kent

Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Friday, 26 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Friday, 26 October)
Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Thursday, 25 October)
Re: [w3c/DOM-Parsing] innerHTML should be defined on ShadowRoot interface in addition to Element interface (#21) (Thursday, 25 October)
Re: [whatwg/dom] May return the same HTMLCollection object (#706) (Friday, 19 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Thursday, 11 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Thursday, 11 October)
Re: [w3ctag/design-reviews] TAG Review Request: Form Participation API (#305) (Wednesday, 10 October)
Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Tuesday, 9 October)

Tarun Bansal

Re: [whatwg/fetch] Check Feature Policy before attaching Client Hints (#811) (Tuesday, 2 October)

Ted Mielczarek

Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74) (Friday, 26 October)

Thomas Di Grégorio

Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Wednesday, 24 October)
Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Wednesday, 24 October)

Thomas Steiner

Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Tuesday, 30 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Monday, 29 October)
Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Thursday, 25 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Tuesday, 23 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Tuesday, 23 October)
Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Tuesday, 23 October)
Re: [w3c/manifest] Add a way to query whether there is a UA-provided back button (#693) (Monday, 22 October)

Timothy Gu

Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Sunday, 14 October)

Tobias Buschor

Re: [w3c/manifest] Install button on another domain (#726) (Wednesday, 10 October)

Tomek Wytrębowicz

Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 26 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 25 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 25 October)
Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760) (Thursday, 25 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 25 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 25 October)
Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Friday, 19 October)

TomPradat

[w3c/ServiceWorker] Why does spec set redirect's mode to error ? (#1366) (Tuesday, 30 October)

Travis Leithead

Re: [w3ctag/design-reviews] Background fetch (#279) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Async local storage (#278) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Async local storage (#278) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Async local storage (#278) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Layered APIs (#276) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] OffscreenCanvas new commit() and DedicatedWorker.requestAnimationFrame (#288) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Task Scheduling (#72) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] HTML General Review: Web Sockets (#268) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187) (Tuesday, 30 October)
Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253) (Monday, 29 October)
[w3ctag/design-reviews] Review MathML (#313) (Monday, 29 October)
Re: [w3c/DOM-Parsing] Tests (#37) (Tuesday, 23 October)
[w3c/webcomponents] Add new proposal (#768) (Monday, 22 October)
[w3c/DOM-Parsing] Tests (#37) (Monday, 22 October)
Re: [w3c/DOM-Parsing] Time at TPAC? (#27) (Monday, 22 October)
Re: [w3ctag/design-reviews] TAG Review Request: Support codec and container switching with MSE using SourceBuffer.changeType() (#298) (Tuesday, 9 October)
Re: [w3ctag/design-reviews] TAG Review Request: Form Participation API (#305) (Tuesday, 9 October)
Re: [w3ctag/design-reviews] TAG review request: WebAssembly Threads (#299) (Tuesday, 2 October)
Re: [w3ctag/design-reviews] TAG review request: WebAssembly Threads (#299) (Tuesday, 2 October)

Tzviya

Re: [w3ctag/design-reviews] Review MathML (#313) (Tuesday, 30 October)

Victor Costan

Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120) (Friday, 19 October)
[w3c/IndexedDB] Transaction storm in idb-transaction-commit explainer sample (#245) (Wednesday, 17 October)
Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Tuesday, 9 October)
Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Tuesday, 9 October)

Vincent Scheib

Re: [w3c/pointerlock] Option needed to disable OS-level adjustment for mouse acceleration (#36) (Monday, 8 October)

Walle Cyril

Re: [w3c/ServiceWorker] What is the correct way to notify the DOM thread about files that have been cached ? (#1260) (Thursday, 18 October)
Re: [w3c/ServiceWorker] What is the correct way to notify the DOM thread about files that have been cached ? (#1260) (Thursday, 18 October)
Re: [w3c/gamepad] [Extensions] make pulse() more like navigator.vibrate (#66) (Thursday, 18 October)
Re: [w3c/gamepad] [Extensions] make pulse() more like navigator.vibrate (#66) (Thursday, 18 October)
Re: [w3c/gamepad] About the id (#65) (Thursday, 18 October)
Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 5 October)

wanttofly88

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

whoami1312

Re: [heycam/webidl] Intent to use [LegacyNamespace] (#588) (Friday, 19 October)
[heycam/webidl] Intent to use [LegacyNamespace] (#588) (Friday, 19 October)

xgqfrms

Re: [whatwg/fetch] upload progress? (#21) (Monday, 8 October)

Xiaoqian Wu

Re: [w3c/gamepad] Cleanup (#84) (Wednesday, 17 October)
Re: [w3c/gamepad] Cleanup (#84) (Wednesday, 17 October)

Xidorn Quan

Re: [whatwg/fullscreen] Re-introduce the hierarchy restrictions (#140) (Friday, 19 October)

xun

Re: [whatwg/fetch] Using multipart/form-data with multer occasionally causes React app to crash and refresh (#677) (Saturday, 20 October)

Yoav Weiss

Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821) (Monday, 29 October)
Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Monday, 29 October)
Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821) (Monday, 29 October)
Re: [whatwg/fetch] Check Feature Policy before attaching Client Hints (#811) (Monday, 1 October)

Yoichi Osato

Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Friday, 19 October)
Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Friday, 5 October)
Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763) (Wednesday, 3 October)

Yonggang Luo

Re: [whatwg/encoding] If gb18030 is revised, consider aligning the Encoding Standard (#27) (Monday, 22 October)

yosin

Re: [w3c/selection-api] setBaseAndExtent should clear selection when baseNode or extentNode is null (#72) (Friday, 12 October)
Re: [w3c/editing] contenteditable-disabled (#176) (Wednesday, 3 October)

youennf

Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Monday, 29 October)
Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Monday, 29 October)

Yutaka Hirano

Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Wednesday, 31 October)
Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821) (Wednesday, 31 October)
Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Monday, 29 October)
Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Wednesday, 24 October)

Yves Lafon

Re: [w3ctag/design-reviews] Stale-While-Revalidate handling in browser (#293) (Wednesday, 31 October)
Re: [w3ctag/design-reviews] Stale-While-Revalidate handling in browser (#293) (Wednesday, 31 October)
Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Tuesday, 30 October)
Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Tuesday, 30 October)
Re: [w3c/gamepad] Obsolete dependencies (#79) (Friday, 26 October)
Re: [w3c/gamepad] Obsolete dependencies (#79) (Friday, 26 October)
Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Tuesday, 23 October)
Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Monday, 22 October)

zhangyonglan

[w3c/selection-api] edge 中selection.focusOffset计算错误 (#97) (Wednesday, 17 October)

森建

Re: [whatwg/dom] [spec bug?] Element with name attribute breaks Document (#708) (Tuesday, 23 October)
Re: [whatwg/dom] [spec bug?] Element with name attribute breaks Document (#708) (Tuesday, 23 October)
[whatwg/dom] [spec bug?] Element with name attribute breaks Document (#708) (Sunday, 21 October)

Last message date: Wednesday, 31 October 2018 23:57:01 UTC