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

=JeffH

[whatwg/fetch] section #connections is vague wrt connection is HTTP or HTTPS or HTTP/2 or QUIC (#641) (Thursday, 30 November)
Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 30 November)
[whatwg/fetch] linking errors upon building fetch? (#639) (Thursday, 30 November)

Adam Rice

Re: [whatwg/streams] How much latitude should implementations have in looking up transformer.transform()? (#691) (Thursday, 30 November)
Re: [whatwg/streams] Lookup methods in constructors (#860) (Thursday, 30 November)
[whatwg/streams] Lookup methods in constructors (#860) (Thursday, 30 November)
Re: [whatwg/streams] How much latitude should implementations have in looking up transformer.transform()? (#691) (Thursday, 30 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Wednesday, 29 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Wednesday, 29 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Wednesday, 29 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Wednesday, 29 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Wednesday, 29 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Tuesday, 28 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Tuesday, 28 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Tuesday, 28 November)
Re: [whatwg/streams] [Question] questions about streaming-element-backpressure.js (#855) (Tuesday, 28 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Monday, 27 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Monday, 27 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Monday, 27 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Wednesday, 22 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Tuesday, 21 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Tuesday, 21 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Tuesday, 21 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Monday, 20 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Monday, 20 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Monday, 20 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Monday, 20 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Monday, 20 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Monday, 20 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Monday, 20 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Friday, 17 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Friday, 17 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Friday, 17 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Friday, 17 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Friday, 17 November)
[whatwg/streams] Branch snapshot missing for algorithm-slots branch (#858) (Friday, 17 November)
Re: [whatwg/streams] Prohibit setting a strategy size for byte streams (#856) (Friday, 17 November)
Re: [whatwg/streams] new ReadableStream({type: 'bytes'}, new CountQueuingStrategy({highWaterMark: 5})) is weird (#729) (Friday, 17 November)
Re: [whatwg/streams] Prohibit setting a strategy size for byte streams (#856) (Friday, 17 November)
Re: [whatwg/streams] Prohibit setting a strategy size for byte streams (#856) (Friday, 17 November)
Re: [whatwg/streams] Prohibit setting a strategy size for byte streams (#856) (Thursday, 16 November)
[whatwg/streams] Prohibit setting a strategy size for byte streams (#856) (Thursday, 16 November)
Re: [whatwg/streams] [Question] questions about streaming-element-backpressure.js (#855) (Tuesday, 14 November)
Re: [whatwg/streams] reader.read() inside strategy.size() doesn't work (#794) (Monday, 13 November)
Re: [whatwg/streams] reader.read() inside strategy.size() doesn't work (#794) (Monday, 13 November)
Re: [whatwg/streams] Remove transform streams tests as they are now upstream (#854) (Monday, 13 November)
Re: [whatwg/streams] Move transform stream tests to web platform tests (#851) (Monday, 13 November)
Re: [whatwg/streams] Remove transform streams tests as they are now upstream (#854) (Monday, 13 November)
Re: [whatwg/streams] Tests contain non-zero timers (#548) (Friday, 10 November)
Re: [whatwg/streams] Remove transform streams tests as they are now upstream (#854) (Thursday, 9 November)
Re: [whatwg/streams] Remove transform streams tests as they are now upstream (#854) (Tuesday, 7 November)
[whatwg/streams] Remove transform streams tests as they are now upstream (#854) (Tuesday, 7 November)
Re: [whatwg/streams] Make it easy to create streams with no underlying source/sink/transformer objects, from specs (#813) (Tuesday, 7 November)
Re: [whatwg/streams] How much latitude should implementations have in looking up transformer.transform()? (#691) (Tuesday, 7 November)
[whatwg/fetch] Nitpick: The user agent can terminate the fetch ... "res => res.body.getReader().closed" (#625) (Monday, 6 November)
Re: [whatwg/streams] Test that TransformStream does not use global constructors (#852) (Monday, 6 November)
Re: [whatwg/streams] Added a couple of examples (#853) (Monday, 6 November)
Re: [whatwg/streams] Added a couple of examples (#853) (Monday, 6 November)
Re: [whatwg/streams] Constructing ReadableStream and WritableStream in TransformStream constructor (#850) (Thursday, 2 November)
[w3ctag/design-reviews] Transform Streams (#211) (Thursday, 2 November)
Re: [whatwg/streams] Standard text for TransformStream (#811) (Thursday, 2 November)
Re: [whatwg/streams] Test that TransformStream does not use global constructors (#852) (Thursday, 2 November)
Re: [whatwg/streams] Test that TransformStream does not use global constructors (#852) (Thursday, 2 November)
Re: [whatwg/streams] Test that TransformStream does not use global constructors (#852) (Thursday, 2 November)
[whatwg/streams] Test that TransformStream does not use global constructors (#852) (Thursday, 2 November)
Re: [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Thursday, 2 November)
Re: [whatwg/streams] Add SyncOneToOneTransformFunctionAdaptor example (#843) (Thursday, 2 November)
Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Thursday, 2 November)
Re: [whatwg/streams] Standard text for TransformStream (#811) (Thursday, 2 November)
Re: [whatwg/streams] Standard text for TransformStream (#811) (Thursday, 2 November)
Re: [whatwg/streams] Constructing ReadableStream and WritableStream in TransformStream constructor (#850) (Thursday, 2 November)
Re: [whatwg/streams] Standard text for TransformStream (#811) (Wednesday, 1 November)
Re: [whatwg/streams] Standard text for TransformStream (#811) (Wednesday, 1 November)
[whatwg/streams] Constructing ReadableStream and WritableStream in TransformStream constructor (#850) (Wednesday, 1 November)

adambet3

[whatwg/xhr] developer (#167) (Wednesday, 1 November)
Re: [w3c/uievents] Change InputEventInit.data default value to null (#148) (Wednesday, 1 November)

Addison Phillips

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

Alec Miller

Re: [w3c/clipboard-apis] Support for putting images on the clipboard (#44) (Wednesday, 29 November)
Re: [w3c/clipboard-apis] Support for delayed clipboard data (#41) (Sunday, 26 November)
Re: [w3c/clipboard-apis] Support for reading custom MIME types from the clipboard (#46) (Sunday, 26 November)
Re: [w3c/clipboard-apis] Support for putting images on the clipboard (#44) (Sunday, 26 November)
Re: [w3c/clipboard-apis] Clipboard API mixes representations of an item with distinct items. (#55) (Sunday, 26 November)

Alessandro

Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Friday, 3 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Friday, 3 November)

Alex Russell

Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Tuesday, 21 November)
Re: [w3ctag/design-reviews] Clear Site Data (#62) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Wednesday, 8 November)

Alexander Shalamov

Re: [w3c/screen-orientation] Clean-up anchors and definitions (#109) (Thursday, 2 November)
Re: [w3c/screen-orientation] Clean-up anchors and definitions (#109) (Thursday, 2 November)
Re: [w3c/screen-orientation] Clean-up anchors and definitions (#109) (Thursday, 2 November)
[w3c/screen-orientation] Clean-up anchors and definitions (#109) (Thursday, 2 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
[w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)

Alfred Morgan

Re: [w3c/ServiceWorker] How do I get extendableEvent.waitUntil() to play nicely with async functions (#1237) (Wednesday, 29 November)
[w3c/ServiceWorker] How do I get extendableEvent.waitUntil() to play nicely with async functions (#1237) (Wednesday, 29 November)
[w3c/ServiceWorker] Allow using async event handlers instead of waitUntil() and respondWith() (#1235) (Monday, 27 November)
Re: [w3c/ServiceWorker] Please default fetch() init credentials to 'same-origin' (#1234) (Sunday, 26 November)
[w3c/ServiceWorker] Please default fetch() init credentials to 'same-origin' (#1234) (Sunday, 26 November)
[w3c/ServiceWorker] Cache.addAll() and .add() needs to accept an init argument to use for fetch() (#1233) (Sunday, 26 November)

Allen Kim

Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Sunday, 19 November)

Amirhosein835

[heycam/webidl] Amirhosein (#481) (Saturday, 25 November)
[heycam/webidl] Active (#480) (Saturday, 25 November)
[heycam/webidl] Intent to use [OverrideBuiltins] (#478) (Saturday, 18 November)

Anders Rundgren

Re: [heycam/webidl] Some means to signal that a method requires user action to be called (#479) (Thursday, 23 November)

Andrea Giammarchi

Re: [whatwg/dom] Adding a `context` property to the listener options. (#472) (Wednesday, 15 November)
Re: [whatwg/dom] Adding a `context` property to the listener options. (#472) (Wednesday, 15 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Wednesday, 8 November)
Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Wednesday, 8 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Saturday, 4 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Friday, 3 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Thursday, 2 November)

Andreas Tolfsen

Re: [w3c/permissions] Introduce "Automation" section (#151) (Wednesday, 8 November)
Re: [w3c/permissions] Introduce "Automation" section (#151) (Wednesday, 8 November)

Andrew Betts

Re: [w3ctag/design-reviews] Request review for PauseFrame API (#196) (Tuesday, 14 November)

Anne van Kesteren

Re: [whatwg/url] Editorial: export "urlencoded parser" for Fetch (#356) (Thursday, 30 November)
[whatwg/url] Editorial: export "urlencoded parser" for Fetch (#356) (Thursday, 30 November)
Re: [whatwg/fetch] Editorial: address Bikeshed and minor wording issues (#640) (Thursday, 30 November)
[whatwg/fetch] Editorial: address Bikeshed and minor wording issues (#640) (Thursday, 30 November)
Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Thursday, 30 November)
Re: [whatwg/fetch] linking errors upon building fetch? (#639) (Thursday, 30 November)
Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Thursday, 30 November)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Wednesday, 29 November)
Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Wednesday, 29 November)
Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Wednesday, 29 November)
Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Wednesday, 29 November)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Wednesday, 29 November)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Tuesday, 28 November)
Re: [w3c/FileAPI] Clarify Lifetime of BlobStore (#89) (Tuesday, 28 November)
Re: [w3c/FileAPI] Clarify Lifetime of BlobStore (#89) (Tuesday, 28 November)
Re: [whatwg/url] Consider adding a constructor to make a URL from parts (#354) (Tuesday, 28 November)
Re: [w3c/FileAPI] Clarify Lifetime of BlobStore (#89) (Tuesday, 28 November)
Re: [w3c/ServiceWorker] Please default fetch() init credentials to 'same-origin' (#1234) (Tuesday, 28 November)
Re: [w3c/ServiceWorker] Please default fetch() init credentials to 'same-origin' (#1234) (Tuesday, 28 November)
Re: [whatwg/xhr] Look at overrideMimeType() again (#157) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
Re: [whatwg/url] Consider adding a constructor to make a URL from parts (#354) (Monday, 27 November)
Re: [whatwg/url] Consider adding a constructor to make a URL from parts (#354) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
Re: [whatwg/encoding] Need more changes for common deploy (#126) (Monday, 27 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Monday, 27 November)
Re: [whatwg/fetch] More eargerly send RST_STREAM on redirects (#638) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Sunday, 26 November)
Re: [whatwg/streams] Branch snapshot missing for algorithm-slots branch (#858) (Sunday, 26 November)
Re: [whatwg/fetch] Safelist Content-Length header (#626) (Saturday, 25 November)
Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Saturday, 25 November)
[whatwg/encoding] Need more changes for common deploy (#126) (Saturday, 25 November)
[whatwg/url] Need more changes for common deploy (#353) (Saturday, 25 November)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Saturday, 25 November)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Friday, 24 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Friday, 24 November)
[whatwg/fetch] More eargerly send RST_STREAM on redirects (#638) (Friday, 24 November)
Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272) (Friday, 24 November)
Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272) (Friday, 24 November)
Re: [whatwg/fetch] what should fetch() do if request's window has been destroyed or stopped? (#153) (Friday, 24 November)
Re: [whatwg/fetch] Cloned responses should not have immutable headers (#608) (Friday, 24 November)
Re: [whatwg/fetch] History behind the decision to make fetch return a Promise (#611) (Friday, 24 November)
Re: [whatwg/fetch] Acknowledge Yehuda Katz (#615) (Friday, 24 November)
Re: [whatwg/fetch] How to set a Basic Authentication headers ? (#623) (Friday, 24 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Friday, 24 November)
[whatwg/fetch] Define RST_STREAM's error code (#637) (Friday, 24 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Friday, 24 November)
Re: [w3c/clipboard-apis] Support for reading custom MIME types from the clipboard (#46) (Thursday, 23 November)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Thursday, 23 November)
Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Thursday, 23 November)
Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Thursday, 23 November)
Re: [heycam/webidl] Some means to signal that a method requires user action to be called (#479) (Thursday, 23 November)
Re: [heycam/webidl] Some means to signal that a method requires user action to be called (#479) (Thursday, 23 November)
Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Thursday, 23 November)
Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Thursday, 23 November)
Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Thursday, 23 November)
Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Thursday, 23 November)
Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Thursday, 23 November)
Re: [heycam/webidl] Some means to signal that a method requires user action to be called (#479) (Thursday, 23 November)
Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Thursday, 23 November)
Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Wednesday, 22 November)
Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Wednesday, 22 November)
Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Wednesday, 22 November)
Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Wednesday, 22 November)
Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Wednesday, 22 November)
Re: [whatwg/dom] Simply MutationObserver callback handling with optional reference property in MutationObserverInit object (#539) (Wednesday, 22 November)
Re: [whatwg/encoding] Meta: TF-8 decode without BOM or fail is used at least once (#124) (Tuesday, 21 November)
[whatwg/dom] Editorial: use JavaScript string length (#538) (Tuesday, 21 November)
[whatwg/dom] Stop using unit of related similar-origin browsing contexts (#537) (Tuesday, 21 November)
Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229) (Tuesday, 21 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Tuesday, 21 November)
Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Tuesday, 21 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Tuesday, 21 November)
Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Tuesday, 21 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 21 November)
Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Tuesday, 21 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Tuesday, 21 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Tuesday, 21 November)
Re: [whatwg/fetch] What to do about requests that should (maybe) preflight but don't? (#567) (Tuesday, 21 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Tuesday, 21 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Tuesday, 21 November)
Re: [whatwg/fetch] Generic Accept header value */* and Service Workers (#634) (Monday, 20 November)
Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Monday, 20 November)
Re: [whatwg/fetch] Generic Accept header value */* and Service Workers (#634) (Monday, 20 November)
Re: [whatwg/storage] Bucket hooks (#18) (Monday, 20 November)
Re: [whatwg/storage] Box hooks (#18) (Monday, 20 November)
Re: [whatwg/fetch] Clarify response's url list state when parsing a 3xx response's Location header value (#631) (Monday, 20 November)
[whatwg/fetch] Use request's current url as base URL in redirects (#633) (Monday, 20 November)
Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Monday, 20 November)
Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Monday, 20 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Monday, 20 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 20 November)
Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Monday, 20 November)
Re: [whatwg/streams] Branch snapshot missing for algorithm-slots branch (#858) (Friday, 17 November)
Re: [whatwg/fetch] WebSocket connections don't appear to send referrers (#630) (Friday, 17 November)
Re: [whatwg/fetch] WebSocket handshake has no referrer (#632) (Friday, 17 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Friday, 17 November)
Re: [whatwg/fullscreen] Define fullscreen in terms of feature policy (#106) (Thursday, 16 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Thursday, 16 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Thursday, 16 November)
Re: [whatwg/fetch] WebSocket handshake has no referrer (#632) (Thursday, 16 November)
Re: [heycam/webidl] Make [Exposed] mandatory, remove [PrimaryGlobal] (#423) (Thursday, 16 November)
Re: [whatwg/fullscreen] Define fullscreen in terms of feature policy (#106) (Thursday, 16 November)
Re: [w3c/filesystem-api] Is this spec deprecated? (#8) (Thursday, 16 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Thursday, 16 November)
Re: [heycam/webidl] Make [Exposed] mandatory, remove [PrimaryGlobal] (#423) (Wednesday, 15 November)
Re: [whatwg/fetch] Clarify response's url list state when parsing a 3xx response's Location header value (#631) (Wednesday, 15 November)
Re: [whatwg/fetch] WebSocket handshake has no referrer (#632) (Wednesday, 15 November)
Re: [heycam/webidl] Proposed solution to make grammar changes less disruptive (#477) (Wednesday, 15 November)
Re: [whatwg/fetch] WebSocket handshake has no referrer (#632) (Wednesday, 15 November)
[whatwg/fetch] WebSocket handshake has no referrer (#632) (Wednesday, 15 November)
Re: [whatwg/fetch] Clarify response's url list state when parsing a 3xx response's Location header value (#631) (Wednesday, 15 November)
Re: [whatwg/dom] Proposal: ParentNode.empty() (#478) (Wednesday, 15 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Wednesday, 15 November)
Re: [w3c/webcomponents] Add `customElements.upgrade` (#710) (Tuesday, 14 November)
Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Tuesday, 14 November)
Re: [heycam/webidl] Proposed solution to make grammar changes less disruptive (#477) (Tuesday, 14 November)
Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Monday, 13 November)
Re: [w3c/DOM-Parsing] should createContextualFragment be added in Document / DocumentFragment? (#33) (Monday, 13 November)
Re: [w3c/DOM-Parsing] should createContextualFragment be added in Document / DocumentFragment? (#33) (Monday, 13 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 13 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Monday, 13 November)
Re: [whatwg/storage] Consider renaming boxes to bins or something (#51) (Saturday, 11 November)
Re: [whatwg/storage] Rename boxes to bins (#52) (Saturday, 11 November)
Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Friday, 10 November)
Re: [whatwg/storage] Rename boxes to bins (#52) (Friday, 10 November)
Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Friday, 10 November)
Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Friday, 10 November)
Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Friday, 10 November)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Friday, 10 November)
Re: [w3c/webcomponents] [idea] Not having <slot> element get in the way of structure. (#589) (Friday, 10 November)
Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Friday, 10 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Friday, 10 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Thursday, 9 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Thursday, 9 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Thursday, 9 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Thursday, 9 November)
Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Thursday, 9 November)
Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Thursday, 9 November)
[whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Thursday, 9 November)
Re: [whatwg/fetch] Why does Fetch specify a max redirect count of 20? (#576) (Thursday, 9 November)
Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Thursday, 9 November)
Re: [w3c/webcomponents] Reserve hyphenated or `$`-including properties for customization (#700) (Thursday, 9 November)
Re: [whatwg/dom] Test multiple text nodes (#528) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] _Update algorithm should unregister SW on 404 and 410 errors (#204) (Wednesday, 8 November)
Re: [whatwg/fetch] Authorisation header not sent for POST requests (#628) (Wednesday, 8 November)
Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] _Update algorithm should unregister SW on 404 and 410 errors (#204) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] What happens to the request body if the fetch isn't handled? (#1191) (Wednesday, 8 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Wednesday, 8 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Wednesday, 8 November)
Re: [whatwg/dom] Touch/Trackpad finger position (#534) (Wednesday, 8 November)
Re: [whatwg/dom] Touch/Trackpad finger position (#534) (Wednesday, 8 November)
Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609) (Wednesday, 8 November)
Re: [whatwg/fetch] Authorisation header not sent for POST requests (#628) (Tuesday, 7 November)
Re: [w3ctag/design-reviews] Editorial: change salutation (#209) (Tuesday, 7 November)
Re: [whatwg/fetch] Authorisation header not sent for POST requests (#628) (Tuesday, 7 November)
Re: [whatwg/fetch] Reject Promise on Error Response (#627) (Tuesday, 7 November)
Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609) (Tuesday, 7 November)
Re: [whatwg/fetch] Reject Promise on Error Response (#627) (Tuesday, 7 November)
Re: [whatwg/fetch] Reject Promise on Error Response (#627) (Tuesday, 7 November)
Re: [whatwg/fetch] Safelist Content-Length header (#626) (Tuesday, 7 November)
Re: [whatwg/fetch] Safelist Content-Length header (#626) (Tuesday, 7 November)
Re: [whatwg/fetch] Safelist Content-Length header (#626) (Tuesday, 7 November)
Re: [whatwg/fetch] Safelist Content-Length header (#626) (Tuesday, 7 November)
Re: [w3ctag/design-reviews] Editorial: change salutation (#209) (Tuesday, 7 November)
Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Tuesday, 7 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Tuesday, 7 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Monday, 6 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Monday, 6 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Monday, 6 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Monday, 6 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 6 November)
Re: [whatwg/fetch] Nitpick: The user agent can terminate the fetch ... "res => res.body.getReader().closed" (#625) (Monday, 6 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 6 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 6 November)
Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Monday, 6 November)
Re: [whatwg/dom] Use mixins in IDL definitions (#529) (Saturday, 4 November)
Re: [whatwg/dom] Use mixins in IDL definitions (#529) (Saturday, 4 November)
Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Friday, 3 November)
Re: [whatwg/dom] label-input association across Shadow DOM boundary (#530) (Friday, 3 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Friday, 3 November)
Re: [whatwg/dom] Use mixins in IDL definitions (#529) (Friday, 3 November)
Re: [whatwg/xhr] I think I have a bug (#170) (Friday, 3 November)
Re: [whatwg/xhr] I think I have a bug (#170) (Friday, 3 November)
Re: [heycam/webidl] Add [InsecureContext] (#471) (Friday, 3 November)
[whatwg/dom] Test multiple text nodes (#528) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Thursday, 2 November)
Re: [whatwg/xhr] Im in need of some guidance please (#168) (Thursday, 2 November)
Re: [whatwg/xhr] Im in need of some guidance please (#168) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [whatwg/fetch] How to set a Basic Authentication headers ? (#623) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [whatwg/dom] "node's tree" seems to be an undefined concept (#526) (Thursday, 2 November)
Re: [whatwg/dom] Why don't we have CSS VR? (#527) (Thursday, 2 November)
Re: [whatwg/dom] Why don't we have CSS VR? (#527) (Thursday, 2 November)
Re: [whatwg/dom] Why don't we have CSS VR? (#527) (Thursday, 2 November)
Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 1 November)
Re: [whatwg/fetch] Use the URL from the response, if it has one (#146) (Wednesday, 1 November)
Re: [whatwg/dom] "node's tree" seems to be an undefined concept (#526) (Wednesday, 1 November)
Re: [whatwg/xhr] developer (#167) (Wednesday, 1 November)
Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 1 November)
Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 1 November)
Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 1 November)
Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 1 November)
Re: [whatwg/url] Should URLSearchParams stringify be called in URL constructor? (#350) (Wednesday, 1 November)

anonymous

Re: [w3c/ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Wednesday, 8 November)

Arnaud Becher

Re: [whatwg/fetch] How to set a Basic Authentication headers ? (#623) (Sunday, 26 November)
[whatwg/fetch] How to set a Basic Authentication headers ? (#623) (Thursday, 2 November)

Arthur Stolyar

Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Friday, 10 November)

Ashley (Scirra)

Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Saturday, 11 November)
Re: [w3c/ServiceWorker] Allow overlapping scopes (#1085) (Friday, 3 November)

beidson

Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Thursday, 16 November)

Ben Kelly

Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Thursday, 30 November)
Re: [w3c/ServiceWorker] How do I get extendableEvent.waitUntil() to play nicely with async functions (#1237) (Wednesday, 29 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Wednesday, 29 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Wednesday, 29 November)
Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Thursday, 23 November)
Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Wednesday, 22 November)
Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Wednesday, 22 November)
Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Wednesday, 22 November)
[w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Wednesday, 22 November)
[w3c/ServiceWorker] consider exposing credentials.get() but only when mediation is set to "silent" (#1231) (Wednesday, 22 November)
Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Tuesday, 21 November)
Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Tuesday, 21 November)
Re: [whatwg/fetch] Generic Accept header value */* and Service Workers (#634) (Tuesday, 21 November)
Re: [whatwg/fetch] Generic Accept header value */* and Service Workers (#634) (Monday, 20 November)
Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Monday, 20 November)
Re: [w3c/ServiceWorker] when will navigation `FetchEvent.resultingClientId` have a reserved client and not an initial about:blank client? (#1228) (Friday, 17 November)
Re: [w3c/ServiceWorker] when will navigation `FetchEvent.resultingClientId` have a reserved client and not an initial about:blank client? (#1228) (Friday, 17 November)
Re: [w3c/ServiceWorker] when will navigation `FetchEvent.resultingClientId` have a reserved client and not an initial about:blank client? (#1228) (Friday, 17 November)
Re: [w3c/ServiceWorker] when will navigation `FetchEvent.resultingClientId` have a reserved client and not an initial about:blank client? (#1228) (Friday, 17 November)
[w3c/ServiceWorker] when will navigation `FetchEvent.resultingClientId` have a reserved client and not an initial about:blank client? (#1228) (Friday, 17 November)
Re: [whatwg/fetch] Clarify response's url list state when parsing a 3xx response's Location header value (#631) (Wednesday, 15 November)
Re: [whatwg/fetch] Clarify response's url list state when parsing a 3xx response's Location header value (#631) (Wednesday, 15 November)
Re: [w3c/ServiceWorker] Why is the scope to registration map and ordered map? (#1225) (Tuesday, 14 November)
Re: [w3c/ServiceWorker] Run Job does not specify which event loop to queue its tasks on (#1224) (Tuesday, 14 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Monday, 13 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Saturday, 11 November)
Re: [w3c/webcomponents] [templates] How to handle expressions in tables (#703) (Friday, 10 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Friday, 10 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Thursday, 9 November)
Re: [whatwg/fetch] Why does Fetch specify a max redirect count of 20? (#576) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221) (Wednesday, 8 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Wednesday, 8 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Wednesday, 8 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Wednesday, 8 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Wednesday, 8 November)
[whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Monday, 6 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Sunday, 5 November)
Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Friday, 3 November)
Re: [w3c/ServiceWorker] async waitUntil() does not allow extension on final promise resolution? (#1039) (Friday, 3 November)
Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Friday, 3 November)
Re: [w3c/ServiceWorker] error handling for aborted streams feeding a navigation request (#1184) (Friday, 3 November)
Re: [w3c/ServiceWorker] Reduce GC exposure (#1127) (Friday, 3 November)
Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Friday, 3 November)
Re: [w3c/ServiceWorker] reflect internal "parsed" state in ServiceWorkerState enum (#1162) (Friday, 3 November)
Re: [w3c/ServiceWorker] error handling for aborted streams feeding a navigation request (#1184) (Friday, 3 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Friday, 3 November)
Re: [whatwg/fetch] Use the URL from the response, if it has one (#146) (Friday, 3 November)
Re: [whatwg/fetch] Use the URL from the response, if it has one (#146) (Thursday, 2 November)
Re: [whatwg/fetch] Use the URL from the response, if it has one (#146) (Wednesday, 1 November)
Re: [whatwg/fetch] Use the URL from the response, if it has one (#146) (Wednesday, 1 November)
Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Wednesday, 1 November)

Benjamin Gruenbaum

Re: [whatwg/fetch] Safelist Content-Length header (#626) (Tuesday, 7 November)
Re: [whatwg/fetch] Safelist Content-Length header (#626) (Tuesday, 7 November)
Re: [whatwg/fetch] Safelist Content-Length header (#626) (Tuesday, 7 November)
Re: [whatwg/fetch] Safelist Content-Length header (#626) (Tuesday, 7 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Monday, 6 November)
[whatwg/fetch] Safelist Content-Length header (#626) (Monday, 6 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Monday, 6 November)

Benoit Girard

Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Wednesday, 1 November)

Bobby Holley

Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Wednesday, 15 November)

Boris Zbarsky

Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Wednesday, 22 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Friday, 17 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Wednesday, 15 November)
Re: [heycam/webidl] Various named property stuff seems confused in the face of symbols (#175) (Monday, 13 November)
[heycam/webidl] Order of includes statements is not a well-defined concept (#473) (Friday, 3 November)
Re: [heycam/webidl] Can SpecialOperation be more simplified? (#470) (Friday, 3 November)

Bradley Meck

Re: [w3c/FileAPI] Async createObjectURL (#84) (Wednesday, 8 November)
[w3c/FileAPI] Clarify Lifetime of BlobStore (#89) (Wednesday, 8 November)

Brandon Jones

Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Wednesday, 15 November)

Brett Zamir

Re: [w3c/webcomponents] Reserve hyphenated or `$`-including properties for customization (#700) (Thursday, 9 November)
Re: [w3c/webcomponents] Reserve hyphenated or `$`-including properties for customization (#700) (Thursday, 9 November)
Re: [w3c/webcomponents] Reserve hyphenated or `$`-including properties for customization (#700) (Wednesday, 8 November)
Re: [w3c/webcomponents] Reserve hyphenated or `$`-including properties for customization (#700) (Wednesday, 8 November)
[w3c/webcomponents] Reserve hyphenated or `$`-including properties/attributes for customization (#700) (Wednesday, 8 November)

Brian Kardell

Re: [w3c/webcomponents] [templates] Contextual auto-escaping (#711) (Tuesday, 14 November)
Re: [w3c/webcomponents] Add `customElements.upgrade` (#710) (Tuesday, 14 November)
Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214) (Tuesday, 7 November)

C. Van Wiemeersch

Re: [w3c/gamepad] `navigator.getGamepads()` should return a `Promise` (#23) (Tuesday, 28 November)

Caleb Williams

Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Monday, 13 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Friday, 3 November)

camillelamy

Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Thursday, 9 November)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Wednesday, 8 November)

Caridy Patiño

Re: [w3c/webcomponents] [template] How to remove a listener registered on createCallback (#708) (Tuesday, 14 November)
[w3c/webcomponents] [template] What if the `type` attribute is specified in the <template> but its processor is not registered? (#709) (Monday, 13 November)
Re: [w3c/webcomponents] [template]How to remove a listener registered on createCallback (#708) (Monday, 13 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 4 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Friday, 3 November)

chaals

Re: [w3c/uievents] Add text around dispatching mouseenter/leave/out/over when an element (#155) (Tuesday, 21 November)
Re: [w3c/uievents] Add text around dispatching mouseenter/leave/out/over when an element (#155) (Wednesday, 15 November)
Re: [w3c/push-api] Rephrase the bit about the UA chosing the push service (#287) (Thursday, 9 November)

chcunningham

[w3ctag/design-reviews] Review Request: Media Capabilities (#218) (Tuesday, 14 November)

Chris Dumez

Re: [w3c/ServiceWorker] Why is the scope to registration map and ordered map? (#1225) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Why is the scope to registration map and ordered map? (#1225) (Tuesday, 14 November)
Re: [w3c/ServiceWorker] Why is the scope to registration map and ordered map? (#1225) (Tuesday, 14 November)
[w3c/ServiceWorker] Why is the scope to registration map and ordered map? (#1225) (Tuesday, 14 November)

Chris Lilley

[w3ctag/design-reviews] TAG review of Web Audio API (round two) (#212) (Tuesday, 7 November)

Chris Matheson

Re: [whatwg/fetch] Authorisation header not sent for POST requests (#628) (Wednesday, 8 November)
Re: [whatwg/fetch] Authorisation header not sent for POST requests (#628) (Wednesday, 8 November)
Re: [whatwg/fetch] Authorisation header not sent for POST requests (#628) (Wednesday, 8 November)
Re: [whatwg/fetch] Authorisation header not sent for POST requests (#628) (Tuesday, 7 November)
[whatwg/fetch] Authorisation header not sent for POST requests (#628) (Tuesday, 7 November)

Chris Rebert

[w3c/uievents] KeyboardEventInit.code section contains broken link to UIEvents-Code spec (#173) (Monday, 20 November)
[w3c/uievents] Broken links to Web IDL spec (#172) (Monday, 20 November)

cynthia

Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Friday, 10 November)
[w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Thursday, 9 November)

Cyril Auburtin

Re: [w3c/DOM-Parsing] should createContextualFragment be added in Document / DocumentFragment? (#33) (Thursday, 23 November)
Re: [w3c/DOM-Parsing] should createContextualFragment be added in Document / DocumentFragment? (#33) (Thursday, 23 November)
Re: [w3c/DOM-Parsing] should createContextualFragment be added in Document / DocumentFragment? (#33) (Monday, 13 November)
[w3c/DOM-Parsing] should createContextualFragment be added in Document / DocumentFragment? (#33) (Monday, 13 November)

d2ydx2

[whatwg/dom] Simply MutationObserver callback handling with optional reference property in MutationObserverInit object (#539) (Tuesday, 21 November)

Daniel Appelquist

Re: [w3ctag/design-reviews] Review request: Web Lifecycle for system initiated Discarding & Stopping (#205) (Wednesday, 29 November)
Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Wednesday, 29 November)
Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Wednesday, 29 November)
Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Wednesday, 29 November)
Re: [w3ctag/design-reviews] WebAssembly Response API / Web Embedding (#167) (Wednesday, 29 November)
Re: [w3ctag/design-reviews] WebAssembly Response API / Web Embedding (#167) (Wednesday, 29 November)
Re: [w3ctag/design-reviews] WebUSB (#108) (Wednesday, 29 November)

Daniel Gidman

Re: [w3c/webcomponents] [proposals]: Template Instantiation typo? (#690) (Thursday, 2 November)
Re: [w3c/webcomponents] [proposals]: Template Instantiation typo? (#690) (Thursday, 2 November)
[w3c/webcomponents] [proposals]: Template Instantiation typo? (#690) (Thursday, 2 November)

Daniel Huigens

Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) (Saturday, 4 November)
Re: [w3c/ServiceWorker] Feature request: Provide a way to delay execution of a new service worker (#1208) (Saturday, 4 November)
Re: [w3c/ServiceWorker] Feature request: Provide a way to conditionally prevent a service worker update (#1208) (Thursday, 2 November)

Daniel Olano

Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 3 November)

Dave Tapuska

Re: [w3c/uievents] Add text around dispatching mouseenter/leave/out/over when an element (#155) (Tuesday, 21 November)
Re: [w3c/uievents] Expose wheel event scrolling state to DOM events (#170) (Monday, 13 November)
Re: [w3c/uievents] Expose wheel event scrolling state to DOM events (#170) (Wednesday, 8 November)

David Bokan

Re: [w3c/uievents] Expose wheel event scrolling state to DOM events (#170) (Thursday, 16 November)

David Hill

Re: [w3c/webcomponents] [templates] Do not specify template binding syntax in spec, make configurable (#697) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Sunday, 5 November)
[w3c/webcomponents] Do not specify template binding syntax in spec, make configurable (#697) (Sunday, 5 November)

davidcblack

Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Thursday, 9 November)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Wednesday, 8 November)

daxiangaikafei

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

ddorwin

[heycam/webidl] Add [InsecureContext] (#471) (Thursday, 2 November)

dejan9393

Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Tuesday, 14 November)

dfabulich

Re: [w3c/ServiceWorker] Provide a way to skipWaiting when the last tab refreshes (#993) (Thursday, 30 November)
Re: [w3c/ServiceWorker] Provide a way to skipWaiting when the last tab refreshes (#993) (Thursday, 30 November)
Re: [w3c/ServiceWorker] Provide a way to skipWaiting when the last tab refreshes (#1238) (Thursday, 30 November)
[w3c/ServiceWorker] Provide a way to skipWaiting when the last tab refreshes (#1238) (Thursday, 30 November)
[w3c/ServiceWorker] Provide a way to ask the waiting Service Worker to skip waiting from the outside (#1223) (Monday, 13 November)
[w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222) (Monday, 13 November)

Dmitri Zagidulin

Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Friday, 10 November)
Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Friday, 10 November)

Domenic Denicola

Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Thursday, 30 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Thursday, 30 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Thursday, 30 November)
Re: [whatwg/streams] How much latitude should implementations have in looking up transformer.transform()? (#691) (Thursday, 30 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Wednesday, 29 November)
Re: [whatwg/streams] Make it easy to create streams with no underlying source/sink/transformer objects, from specs (#813) (Wednesday, 29 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Wednesday, 29 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Wednesday, 29 November)
Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Wednesday, 29 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Tuesday, 28 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Tuesday, 28 November)
Re: [w3c/ServiceWorker] Allow using async event handlers instead of waitUntil() and respondWith() (#1235) (Monday, 27 November)
Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Thursday, 23 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Saturday, 18 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Friday, 17 November)
Re: [whatwg/streams] Don't error canceled branches when erroring a teed stream (#859) (Friday, 17 November)
Re: [whatwg/streams] Don't error canceled branches when erroring a teed stream (#859) (Friday, 17 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Friday, 17 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Friday, 17 November)
Re: [whatwg/streams] Branch snapshot missing for algorithm-slots branch (#858) (Friday, 17 November)
Re: [whatwg/streams] Branch snapshot missing for algorithm-slots branch (#858) (Friday, 17 November)
Re: [whatwg/streams] Branch snapshot missing for algorithm-slots branch (#858) (Friday, 17 November)
Re: [whatwg/streams] Branch snapshot missing for algorithm-slots branch (#858) (Friday, 17 November)
Re: [whatwg/streams] [Question] I created a project that explains the spec (#848) (Friday, 17 November)
Re: [whatwg/streams] [Question] I created a project that explains the spec (#848) (Friday, 17 November)
Re: [whatwg/streams] Constructing ReadableStream and WritableStream in TransformStream constructor (#850) (Friday, 17 November)
[whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Thursday, 16 November)
Re: [whatwg/streams] Make it easy to create streams with no underlying source/sink/transformer objects, from specs (#813) (Thursday, 16 November)
Re: [whatwg/streams] Prohibit setting a strategy size for byte streams (#856) (Thursday, 16 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Thursday, 16 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Thursday, 16 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Thursday, 16 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Thursday, 16 November)
Re: [whatwg/fetch] WebSocket connections don't appear to send referrers (#630) (Wednesday, 15 November)
Re: [whatwg/fetch] WebSocket connections don't appear to send referrers (#630) (Wednesday, 15 November)
[whatwg/fetch] WebSocket connections don't appear to send referrers (#630) (Wednesday, 15 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] Is a global registry of template processors the right idea? (#681) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] What is declareCallback? (#693) (Tuesday, 14 November)
Re: [w3c/webcomponents] [template] What if the `type` attribute is specified in the <template> but its processor is not registered? (#709) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] Do not specify template binding syntax in spec, make configurable (#697) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] Do not specify template binding syntax in spec, make configurable (#697) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Tuesday, 14 November)
Re: [heycam/webidl] Proposed solution to make grammar changes less disruptive (#477) (Tuesday, 14 November)
Re: [w3c/webcomponents] Add `customElements.upgrade` (#710) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Tuesday, 14 November)
Re: [whatwg/streams] Remove transform streams tests as they are now upstream (#854) (Sunday, 12 November)
Re: [w3c/uievents] Update event-types.txt: Not all wheel events are cancelable. (#171) (Sunday, 12 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Saturday, 11 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Friday, 10 November)
Re: [w3c/uievents] Update event-types.txt: Not all wheel events are cancelable. (#171) (Friday, 10 November)
Re: [w3c/webcomponents] Reserve hyphenated or `$`-including properties for customization (#700) (Wednesday, 8 November)
Re: [w3c/webcomponents] Reserve hyphenated or `$`-including properties for customization (#700) (Wednesday, 8 November)
Re: [w3c/webcomponents] Reserve hyphenated or `$`-including properties/attributes for customization (#700) (Wednesday, 8 November)
Re: [w3c/webcomponents] Reserve hyphenated or `$`-including properties/attributes for customization (#700) (Wednesday, 8 November)
Re: [whatwg/streams] How much latitude should implementations have in looking up transformer.transform()? (#691) (Tuesday, 7 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Monday, 6 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Monday, 6 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Monday, 6 November)
Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Friday, 3 November)
[w3c/webcomponents] [templates] What is declareCallback? (#693) (Thursday, 2 November)
Re: [whatwg/streams] Constructing ReadableStream and WritableStream in TransformStream constructor (#850) (Thursday, 2 November)
Re: [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Thursday, 2 November)
Re: [whatwg/streams] Test that TransformStream does not use global constructors (#852) (Thursday, 2 November)
[w3c/webcomponents] [templates] API for updating (#685) (Thursday, 2 November)
[w3c/webcomponents] [templates] No need for -Callback suffix (#684) (Thursday, 2 November)
[w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
[w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Thursday, 2 November)
[w3c/webcomponents] [templates] Is a global registry of template processors the right idea? (#681) (Thursday, 2 November)
[w3c/webcomponents] [templates] Parts APIs surface concerns (#680) (Thursday, 2 November)
Re: [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Thursday, 2 November)
[whatwg/streams] Move transform stream tests to web platform tests (#851) (Thursday, 2 November)
Re: [whatwg/streams] Constructing ReadableStream and WritableStream in TransformStream constructor (#850) (Wednesday, 1 November)
Re: [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Wednesday, 1 November)
Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Wednesday, 1 November)
Re: [whatwg/streams] Add SyncOneToOneTransformFunctionAdaptor example (#843) (Wednesday, 1 November)

Dominique Hazael-Massieux

Re: [w3c/uievents] Update event-types.txt: Not all wheel events are cancelable. (#171) (Monday, 13 November)
Re: [w3c/webcomponents] typo (#707) (Monday, 13 November)

drwez

Re: [w3c/uievents] Add specification for AltGraph key & modifier behaviour (#147) (Monday, 6 November)

Elliott Sprehn

Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Wednesday, 15 November)
Re: [whatwg/dom] Proposal: ParentNode.empty() (#478) (Wednesday, 15 November)
[whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Wednesday, 15 November)

Emily Stark

Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 20 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 20 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Saturday, 18 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Saturday, 18 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 6 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Friday, 3 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Friday, 3 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Friday, 3 November)

Emrah Bilbay

Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Thursday, 2 November)

Eric Newport

Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Monday, 13 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Friday, 3 November)
[w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Friday, 3 November)

Eric Oyler

Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Tuesday, 7 November)

Evan You

Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Monday, 27 November)

Felipe Nascimento de Moura

[whatwg/dom] Touch/Trackpad finger position (#534) (Wednesday, 8 November)

Fuqiao Xue

Re: [w3c/screen-orientation] Wide review tracker (#102) (Monday, 13 November)

Gary Kacmarcik

Re: [w3c/uievents] Update event-types.txt: Not all wheel events are cancelable. (#171) (Wednesday, 22 November)
Re: [w3c/uievents] Add text around dispatching mouseenter/leave/out/over when an element (#155) (Tuesday, 21 November)
Re: [w3c/uievents] Add text around dispatching mouseenter/leave/out/over when an element (#155) (Tuesday, 14 November)

Gerard Tyedmers

Re: [w3c/manifest] multilingual description (#628) (Wednesday, 29 November)
Re: [w3c/manifest] multilingual description (#628) (Wednesday, 29 November)
Re: [w3c/manifest] multilingual description (#628) (Monday, 27 November)
[w3c/manifest] multilingual description (#628) (Monday, 27 November)

Giovanni Lovato

Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Friday, 10 November)
Re: [w3c/webcomponents] Support for pseudo elements with ::slotted() selectors (#655) (Friday, 10 November)
Re: [w3c/webcomponents] [idea] Not having <slot> element get in the way of structure. (#589) (Friday, 10 November)
[w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Friday, 10 November)
Re: [w3c/webcomponents] [idea] Not having <slot> element get in the way of structure. (#589) (Friday, 10 November)

Govza

Re: [w3ctag/design-reviews] Privacy Mode (#101) (Monday, 6 November)

guest271314

Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Thursday, 30 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Thursday, 30 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Thursday, 30 November)
Re: [whatwg/streams] WIP: allow creating streams from specs while using fewer JS objects (#857) (Thursday, 30 November)
Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Sunday, 12 November)

Hadley Beeman

[w3ctag/design-reviews] Review Decentralised identifiers (DIDs) (#216) (Thursday, 9 November)
Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186) (Tuesday, 7 November)

Hannan Ali

Re: [whatwg/streams] [Question] questions about streaming-element-backpressure.js (#855) (Tuesday, 28 November)
Re: [whatwg/streams] [Question] questions about streaming-element-backpressure.js (#855) (Tuesday, 28 November)
[whatwg/streams] [Question] Need help with a few lines in a demo (#855) (Tuesday, 14 November)

Haroen Viaene

Re: [whatwg/url] Consider adding a constructor to make a URL from parts (#354) (Monday, 27 November)
Re: [whatwg/url] Consider adding a constructor to make a URL from parts (#354) (Monday, 27 November)
[whatwg/url] Consider adding a constructor to make a URL from parts (#354) (Monday, 27 November)

Harris Hancock

Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Tuesday, 21 November)
[whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Monday, 20 November)
Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Monday, 20 November)
Re: [whatwg/fetch] Clarify response's url list state when parsing a 3xx response's Location header value (#631) (Wednesday, 15 November)
[whatwg/fetch] Clarify response's url list state when parsing a 3xx response's Location header value (#631) (Wednesday, 15 November)

Hayato Ito

Re: [w3c/webcomponents] <iframe> and the History API (#184) (Thursday, 30 November)
Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Tuesday, 21 November)
Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Monday, 20 November)
Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Friday, 10 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Thursday, 9 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Thursday, 9 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Wednesday, 8 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Wednesday, 8 November)
Re: [whatwg/dom] Composed shadow DOM (#531) (Friday, 3 November)

Henri Sivonen

Re: [whatwg/dom] Declarative Shadow DOM (#510) (Thursday, 9 November)
Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Tuesday, 7 November)
Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Tuesday, 7 November)
Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Monday, 6 November)
Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Monday, 6 November)

Hiroki Nakagawa

Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Monday, 6 November)

Honza Bambas

Re: [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308) (Friday, 24 November)

Ian Clelland

Re: [whatwg/fullscreen] Define fullscreen in terms of feature policy (#106) (Thursday, 16 November)
[whatwg/fullscreen] Refer to feature policy spec (#107) (Wednesday, 15 November)
[whatwg/fullscreen] Define fullscreen in terms of feature policy (#106) (Wednesday, 15 November)

Ilya Grigorik

Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Thursday, 2 November)

Jake Archibald

Re: [w3c/ServiceWorker] Cache.addAll() and .add() needs to accept an init argument to use for fetch() (#1233) (Monday, 27 November)
Re: [w3c/ServiceWorker] Cache.addAll() and .add() needs to accept an init argument to use for fetch() (#1233) (Monday, 27 November)
Re: [w3c/ServiceWorker] Allow using async event handlers instead of waitUntil() and respondWith() (#1235) (Monday, 27 November)
Re: [w3c/ServiceWorker] WindowClient.navigate() behavior for reserved clients and in-flight navigations (#1123) (Thursday, 23 November)
Re: [w3c/ServiceWorker] Client.reserved references wrong context state? (#1030) (Thursday, 23 November)
Re: [w3c/ServiceWorker] Client.reserved references wrong context state? (#1030) (Thursday, 23 November)
Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Thursday, 23 November)
Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Thursday, 23 November)
Re: [w3c/ServiceWorker] clarify that Client "creation order" means when reserved Client created (#1078) (Thursday, 23 November)
Re: [w3c/ServiceWorker] clarify that Client "creation order" means when reserved Client created (#1078) (Thursday, 23 November)
Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Thursday, 23 November)
Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Thursday, 23 November)
Re: [w3c/ServiceWorker] postMessage() to a reserved client throws (#1035) (Thursday, 23 November)
Re: [w3c/ServiceWorker] postMessage() to a reserved client throws (#1035) (Thursday, 23 November)
Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Thursday, 23 November)
Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Thursday, 23 November)
Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229) (Tuesday, 21 November)
Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Tuesday, 21 November)
Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229) (Tuesday, 21 November)
Re: [whatwg/fetch] Generic Accept header value */* and Service Workers (#634) (Monday, 20 November)
[w3c/ServiceWorker] Merge with storage (#1230) (Monday, 20 November)
Re: [whatwg/storage] Bucket hooks (#18) (Monday, 20 November)
Re: [whatwg/storage] Bucket hooks (#18) (Monday, 20 November)
Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229) (Monday, 20 November)
Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229) (Monday, 20 November)
Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Handing fetch termination (#1178) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Handing fetch termination (#1178) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Block 206s entering the cache (via put & addAll) (#937) (Thursday, 16 November)
Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Saturday, 11 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] How to handle expressions in tables (#703) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
[w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] How to handle expressions in tables (#703) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] How to handle expressions in tables (#703) (Friday, 10 November)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Thursday, 9 November)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Thursday, 9 November)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Thursday, 9 November)
Re: [w3c/ServiceWorker] _Update algorithm should unregister SW on 404 and 410 errors (#204) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] consider firing a "clientcontrolled" event on ServiceWorkerGlobalScope (#886) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] _Update algorithm should unregister SW on 404 and 410 errors (#204) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] _Update algorithm should unregister SW on 404 and 410 errors (#204) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] is the browser required to start the ServiceWorker for postMessage() if there is no message event handler? (#1200) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] What happens to the request body if the fetch isn't handled? (#1191) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] WindowClient.navigate() behavior for reserved clients and in-flight navigations (#1123) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] consider Client behavior for windows where initial about:blank is replaced with a loaded document (#1091) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] Should we expose reserved clients? (#1216) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Monday, 6 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Monday, 6 November)
Re: [w3c/ServiceWorker] Find a way for service workers to get their current state (#1077) (Friday, 3 November)
Re: [w3c/ServiceWorker] Support restarting download when storing large resources in Cache (#713) (Friday, 3 November)
Re: [w3c/ServiceWorker] Support restarting download when storing large resources in Cache (#713) (Friday, 3 November)
Re: [w3c/ServiceWorker] Allow overlapping scopes (#1085) (Friday, 3 November)
Re: [w3c/ServiceWorker] Feature request: Provide a way to delay execution of a new service worker (#1208) (Friday, 3 November)
Re: [w3c/ServiceWorker] Feature request: Provide a way to delay execution of a new service worker (#1208) (Friday, 3 November)
Re: [w3c/ServiceWorker] Installing a foreign SW as part of a subresource request (#825) (Friday, 3 November)
Re: [w3c/ServiceWorker] Installing a foreign SW as part of a subresource request (#825) (Friday, 3 November)
Re: [w3c/ServiceWorker] Foreign fetch vs non-credentialed requests (#878) (Friday, 3 November)
Re: [w3c/ServiceWorker] Foreign fetch vs non-credentialed requests (#878) (Friday, 3 November)
Re: [w3c/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Friday, 3 November)
Re: [w3c/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Friday, 3 November)
Re: [w3c/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899) (Friday, 3 November)
Re: [w3c/ServiceWorker] Foreign fetch and no-referrer Referrer Policy (#899) (Friday, 3 November)
Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Friday, 3 November)
Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Friday, 3 November)
Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 3 November)
Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 3 November)
Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Friday, 3 November)
Re: [w3c/ServiceWorker] Define procedure to convert options object of `sw.register()` to `Link` header (#979) (Friday, 3 November)
Re: [w3c/ServiceWorker] registerForeignFetch({ origins, scope }) optional (#982) (Friday, 3 November)
Re: [w3c/ServiceWorker] registerForeignFetch({ origins, scope }) optional (#982) (Friday, 3 November)
Re: [w3c/ServiceWorker] async waitUntil() does not allow extension on final promise resolution? (#1039) (Friday, 3 November)
Re: [w3c/ServiceWorker] async waitUntil() does not allow extension on final promise resolution? (#1039) (Friday, 3 November)
Re: [w3c/ServiceWorker] clientId on ForeignFetchEvents (#1017) (Friday, 3 November)
Re: [w3c/ServiceWorker] clientId on ForeignFetchEvents (#1017) (Friday, 3 November)
Re: [w3c/ServiceWorker] consider allowing static routing only for "foreign fetch" for anonymous requests (#1024) (Friday, 3 November)
Re: [w3c/ServiceWorker] consider allowing static routing only for "foreign fetch" for anonymous requests (#1024) (Friday, 3 November)
Re: [w3c/ServiceWorker] `Clients.matchAll()` should exclude the current environment (#1037) (Friday, 3 November)
Re: [w3c/ServiceWorker] Find a way for service workers to get their current state (#1077) (Friday, 3 November)
Re: [w3c/ServiceWorker] Find a way for service workers to get their current state (#1077) (Friday, 3 November)
Re: [w3c/ServiceWorker] async waitUntil() does not allow extension on final promise resolution? (#1039) (Friday, 3 November)
Re: [w3c/ServiceWorker] Add async iteration to the cache API (#1066) (Friday, 3 November)
Re: [w3c/ServiceWorker] no way for using a websocket inside a service worker (#1072) (Friday, 3 November)
Re: [w3c/ServiceWorker] no way for using a websocket inside a service worker (#1072) (Friday, 3 November)
Re: [w3c/ServiceWorker] Service worker ID - remove? (#1076) (Friday, 3 November)
Re: [w3c/ServiceWorker] Find a way for service workers to get their current state (#1077) (Friday, 3 November)
Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Friday, 3 November)
Re: [w3c/ServiceWorker] No event for knowing when service worker is not available (#1082) (Friday, 3 November)
Re: [w3c/ServiceWorker] No event for knowing when service worker is not available (#1082) (Friday, 3 November)
Re: [w3c/ServiceWorker] Allow overlapping scopes (#1085) (Friday, 3 November)
Re: [w3c/ServiceWorker] Allow overlapping scopes (#1085) (Friday, 3 November)
Re: [w3c/ServiceWorker] Safety versus simplicity in specification tests (#1087) (Friday, 3 November)
Re: [w3c/ServiceWorker] Safety versus simplicity in specification tests (#1087) (Friday, 3 November)
Re: [w3c/ServiceWorker] Is there any way for a web page to see if their requests will be intercepted by a foreign fetch handler? (#1092) (Friday, 3 November)
Re: [w3c/ServiceWorker] Is there any way for a web page to see if their requests will be intercepted by a foreign fetch handler? (#1092) (Friday, 3 November)
Re: [w3c/ServiceWorker] how does service worker interact with html imports? (#1095) (Friday, 3 November)
Re: [w3c/ServiceWorker] how does service worker interact with html imports? (#1095) (Friday, 3 November)
Re: [w3c/ServiceWorker] Change the spec so that when a new SW is being registered it's set to not use cache the first time (#1103) (Friday, 3 November)
Re: [w3c/ServiceWorker] Touching documents in an "in parallel" section makes no sense (#1108) (Friday, 3 November)
Re: [w3c/ServiceWorker] Confusing "Updating a service worker" section in explainer (#1111) (Friday, 3 November)
Re: [w3c/ServiceWorker] Confusing "Updating a service worker" section in explainer (#1111) (Friday, 3 November)
[w3c/ServiceWorker] FetchEvent init preloadResponse should be option. Fixes #1114. (#1219) (Friday, 3 November)
Re: [w3c/ServiceWorker] Should a service worker be allowed to register new service workers? (#1117) (Friday, 3 November)
Re: [w3c/ServiceWorker] Reduce GC exposure (#1127) (Friday, 3 November)
Re: [w3c/ServiceWorker] clients.get() should resolve with null instead of undefined (#1133) (Friday, 3 November)
Re: [w3c/ServiceWorker] clients.get() should resolve with null instead of undefined (#1133) (Friday, 3 November)
Re: [w3c/ServiceWorker] Priority of requests (feature request) (#1137) (Friday, 3 November)
Re: [w3c/ServiceWorker] Priority of requests (feature request) (#1137) (Friday, 3 November)
Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Friday, 3 November)
Re: [w3c/ServiceWorker] Use ASCII serialization for origins (#1151) (Friday, 3 November)
Re: [w3c/ServiceWorker] event.waitUntil/respondWith vs return promise (#1148) (Friday, 3 November)
Re: [w3c/ServiceWorker] event.waitUntil/respondWith vs return promise (#1148) (Friday, 3 November)
Re: [w3c/ServiceWorker] Proposal: pass custom params in ServiceWorkerRegistration for future use (#1157) (Friday, 3 November)
Re: [w3c/ServiceWorker] Proposal: pass custom params in ServiceWorkerRegistration for future use (#1157) (Friday, 3 November)
Re: [w3c/ServiceWorker] reflect internal "parsed" state in ServiceWorkerState enum (#1162) (Friday, 3 November)
Re: [w3c/ServiceWorker] Allow `None` as value for `Service-Worker-Allowed`. (#1165) (Friday, 3 November)
Re: [w3c/ServiceWorker] Cross origin error due to htaccess restrictions (#1181) (Friday, 3 November)
Re: [w3c/ServiceWorker] Cross origin error due to htaccess restrictions (#1181) (Friday, 3 November)
Re: [w3c/ServiceWorker] error handling for aborted streams feeding a navigation request (#1184) (Friday, 3 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Friday, 3 November)
Re: [w3c/ServiceWorker] Making functional events simpler (#1199) (Friday, 3 November)
Re: [w3c/ServiceWorker] Feature request: Provide a way to delay execution of a new service worker (#1208) (Friday, 3 November)
Re: [w3c/ServiceWorker] add w3cid for editors to help publication (#1218) (Friday, 3 November)
Re: [w3c/ServiceWorker] Feature request: Make updatefound an ExtendableEvent (#1208) (Thursday, 2 November)
Re: [w3c/ServiceWorker] Meta: mention type:untestable and type:missing-coverage wpt labels (#1211) (Thursday, 2 November)
Re: [w3c/ServiceWorker] Meta: mention type:untestable and type:missing-coverage wpt labels (#1211) (Thursday, 2 November)
Re: [w3c/ServiceWorker] Block partial responses entering the cache (#1210) (Thursday, 2 November)
Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Thursday, 2 November)
Re: [w3c/ServiceWorker] add w3cid for editors to help publication (#1218) (Thursday, 2 November)
Re: [w3c/ServiceWorker] Clarity: "is dispatched a set of" (#1214) (Thursday, 2 November)
Re: [w3c/ServiceWorker] Clarity: "is dispatched a set of" (#1214) (Thursday, 2 November)
[w3c/ServiceWorker] Minor grammar issue. Fixes #1214. (#1217) (Thursday, 2 November)
Re: [w3c/ServiceWorker] Should we expose reserved clients? (#1216) (Thursday, 2 November)
Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Thursday, 2 November)
Re: [whatwg/fetch] Use the URL from the response, if it has one (#146) (Wednesday, 1 November)

James Browning

Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Wednesday, 8 November)
Re: [w3c/webcomponents] [templates] Is a global registry of template processors the right idea? (#681) (Saturday, 4 November)

Jason Sebring

Re: [whatwg/fetch] Aborting a fetch (#27) (Saturday, 4 November)

Jeremy Danyow

[w3c/webcomponents] Consider ${foo} instead of {{foo}} (#688) (Thursday, 2 November)

JF Bastien

Re: [w3ctag/design-reviews] WebAssembly Response API / Web Embedding (#167) (Wednesday, 29 November)

JingAn Chen

Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Friday, 3 November)

Joe Pea

Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Sunday, 19 November)
Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Tuesday, 14 November)
Re: [w3c/webcomponents] Why do we really need hyphens? (#658) (Saturday, 4 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Friday, 3 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Friday, 3 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Friday, 3 November)
Re: [whatwg/dom] Why don't we have CSS VR? (#527) (Friday, 3 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Friday, 3 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Thursday, 2 November)
Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488) (Thursday, 2 November)
[whatwg/dom] Why don't we have CSS VR? (#527) (Thursday, 2 November)

Johannes Wilm

Re: [w3ctag/design-reviews] Request for TAG review of Input events level 2 (#173) (Tuesday, 21 November)

Jonathon Kereliuk

Re: [w3c/permissions] Introduce "Automation" section (#151) (Wednesday, 29 November)
Re: [w3c/permissions] Introduce "Automation" section (#151) (Monday, 13 November)
Re: [w3c/permissions] Introduce "Automation" section (#151) (Monday, 13 November)
Re: [w3c/permissions] Introduce "Automation" section (#151) (Monday, 6 November)

Josh Karlin

Re: [w3ctag/design-reviews] Request review for PauseFrame API (#196) (Wednesday, 15 November)
Re: [w3ctag/design-reviews] Request review for PauseFrame API (#196) (Wednesday, 15 November)

Joshua Bell

Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Wednesday, 29 November)
Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Monday, 27 November)
Re: [w3c/IndexedDB] indexedDb The first time using the index query takes too long (#225) (Friday, 24 November)
Re: [w3c/IndexedDB] indexedDb The first time using the index query takes too long (#225) (Friday, 24 November)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Friday, 24 November)
[w3ctag/design-reviews] Web Locks API (#217) (Friday, 10 November)
Re: [whatwg/storage] Rename boxes to bins (#52) (Friday, 10 November)
Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Thursday, 9 November)
Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224) (Thursday, 9 November)
Re: [w3c/IndexedDB] boolean should be a valid key (#76) (Thursday, 9 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Friday, 3 November)

juj

Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Wednesday, 15 November)
Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Wednesday, 15 November)
Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Wednesday, 15 November)

Jungkee Song

Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Tuesday, 28 November)
Re: [w3c/ServiceWorker] Please default fetch() init credentials to 'same-origin' (#1234) (Tuesday, 28 November)
Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Thursday, 23 November)
Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Thursday, 23 November)
Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232) (Thursday, 23 November)
Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229) (Tuesday, 21 November)
Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229) (Tuesday, 21 November)
Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229) (Tuesday, 21 November)
Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229) (Tuesday, 21 November)
Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229) (Tuesday, 21 November)
[w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229) (Friday, 17 November)
Re: [w3c/ServiceWorker] Remove <link rel=serviceworker> (#1220) (Friday, 17 November)
Re: [w3c/ServiceWorker] when will navigation `FetchEvent.resultingClientId` have a reserved client and not an initial about:blank client? (#1228) (Friday, 17 November)
Re: [w3c/ServiceWorker] Clarity: "is dispatched a set of" (#1214) (Friday, 17 November)
Re: [w3c/ServiceWorker] Minor grammar issue. Fixes #1214. (#1217) (Friday, 17 November)
Re: [w3c/ServiceWorker] Remove <link rel=serviceworker> (#1220) (Friday, 17 November)
Re: [w3c/ServiceWorker] Block 206s entering the cache (via put & addAll) (#937) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Block partial responses entering the cache (#1210) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Block 206s entering the cache (via put & addAll) (#937) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Block 206s entering the cache (via put & addAll) (#937) (Thursday, 16 November)
Re: [w3c/ServiceWorker] FetchEvent init preloadResponse should be optional. Fixes #1114. (#1219) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Thursday, 16 November)
[w3c/ServiceWorker] Clean up prose about waitUntil on install & activate events (#1227) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Making functional events simpler (#1199) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Making functional events simpler (#1199) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Handing fetch termination (#1178) (Thursday, 16 November)
Re: [w3c/ServiceWorker] Run Job does not specify which event loop to queue its tasks on (#1224) (Wednesday, 15 November)
Re: [w3c/ServiceWorker] Minor grammar issue. Fixes #1214. (#1217) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Friday, 3 November)
Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Thursday, 2 November)

Justin Fagnani

Re: [w3c/webcomponents] [templates] Contextual auto-escaping (#711) (Tuesday, 14 November)
[w3c/webcomponents] [templates] Contextual auto-escaping (#711) (Tuesday, 14 November)
Re: [w3c/webcomponents] Add `customElements.upgrade` (#710) (Monday, 13 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Monday, 13 November)
Re: [w3c/webcomponents] HTML Modules (#645) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] How to handle expressions in tables (#703) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] How to handle expressions in tables (#703) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] implement a polyfill of template-instantiation before even considering to add the API natively to the platform (#702) (Friday, 10 November)
[w3c/webcomponents] [templates] How to handle expressions in tables (#703) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Saturday, 4 November)
Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Friday, 3 November)

Justin Novosad

Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Thursday, 16 November)
Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Tuesday, 14 November)
Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Tuesday, 14 November)

JustOff

Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Wednesday, 22 November)

Jxck

Re: [w3c/WebPlatformWG] TPAC agenda: Fri Nov 10 (Web Components) (#95) (Tuesday, 14 November)
[w3c/webcomponents] typo (#707) (Monday, 13 November)

Kagami Sascha Rosylight

[heycam/webidl] Replace remaining emu-t.symbol (#475) (Sunday, 5 November)
Re: [heycam/webidl] static/stringifer RegularOperation (#474) (Saturday, 4 November)
[heycam/webidl] static/stringifer RegularOperation (#474) (Saturday, 4 November)
[heycam/webidl] Can SpecialOperation be more simplified? (#470) (Thursday, 2 November)

Keith Cirkel

[w3c/uievents] Bug in spec? event.key and casing (#169) (Monday, 6 November)

Ken Wilson

Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226) (Wednesday, 22 November)

Kenneth Rohde Christiansen

Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 14 November)
Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Friday, 10 November)

Kirtan Gajjar

Re: [w3c/filesystem-api] Is this spec deprecated? (#8) (Wednesday, 15 November)

Kunihiko Sakamoto

[w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Tuesday, 7 November)

L. David Baron

Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Wednesday, 29 November)
Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Wednesday, 29 November)
Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Wednesday, 29 November)
Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Tuesday, 28 November)
Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Tuesday, 28 November)
Re: [w3ctag/design-reviews] Request review for Scroll Boundary Behavior (#193) (Tuesday, 21 November)
Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Tuesday, 21 November)
Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Tuesday, 21 November)
Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Wednesday, 15 November)
Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Tuesday, 7 November)
Re: [w3ctag/design-reviews] Privacy Mode (#101) (Tuesday, 7 November)

Léonie Watson

Re: [w3c/WebPlatformWG] TPAC agenda: Fri Nov 10 (Web Components) (#95) (Tuesday, 14 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Fri Nov 10 (Web Components) (#95) (Tuesday, 14 November)
Re: [w3c/screen-orientation] Wide review tracker (#102) (Friday, 10 November)
Re: [w3c/IndexedDB] Implementation report (#213) (Friday, 10 November)
Re: [w3c/IndexedDB] Implementation report (#213) (Friday, 10 November)
Re: [w3c/screen-orientation] Wide review tracker (#102) (Friday, 10 November)
Re: [w3c/screen-orientation] Wide review tracker (#102) (Friday, 10 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Friday, 10 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Friday, 10 November)
Re: [w3c/screen-orientation] Wide review tracker (#102) (Friday, 10 November)
Re: [w3c/gamepad] Time at TPAC? (#60) (Friday, 10 November)
Re: [w3c/push-api] Wide review tracker (#265) (Thursday, 9 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Thursday, 9 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Thursday, 9 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Thursday, 9 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Saturday, 4 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Fri Nov 10 (Web Components) (#95) (Saturday, 4 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Saturday, 4 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Saturday, 4 November)

Maciej Stachowiak

Re: [whatwg/fullscreen] Define fullscreen in terms of feature policy (#106) (Friday, 17 November)

Maga D. Zandaqo

Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Thursday, 30 November)

Majid Valipour

Re: [w3ctag/design-reviews] Request review for Scroll Boundary Behavior (#193) (Tuesday, 21 November)

Marcos Cáceres

Re: [w3c/manifest] multilingual description (#628) (Wednesday, 29 November)
Re: [w3c/manifest] multilingual description (#628) (Wednesday, 29 November)
Re: [w3c/manifest] Extension point should come after processing other members (#629) (Tuesday, 28 November)
Re: [w3c/manifest] multilingual description (#628) (Monday, 27 November)
Re: [w3c/manifest] multilingual description (#628) (Monday, 27 November)
Re: [heycam/webidl] Some means to signal that a method requires user action to be called (#479) (Friday, 24 November)
Re: [heycam/webidl] Some means to signal that a method requires user action to be called (#479) (Friday, 24 November)
[heycam/webidl] Some means to signal that a method requires user action to be called (#479) (Thursday, 23 November)
Re: [w3c/permissions] Introduce "Automation" section (#151) (Thursday, 16 November)
Re: [w3c/manifest] Which "platform" should I use for Windows 10 UWP apps? (#580) (Tuesday, 14 November)
Re: [w3c/manifest] Which "platform" should I use for Windows 10 UWP apps? (#580) (Tuesday, 14 November)
Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 14 November)
Re: [heycam/webidl] Proposed solution to make grammar changes less disruptive (#477) (Tuesday, 14 November)
Re: [heycam/webidl] Proposed solution to make grammar changes less disruptive (#477) (Monday, 13 November)
Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Saturday, 11 November)
Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Friday, 10 November)
[w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Friday, 10 November)
Re: [w3c/screen-orientation] Wide review tracker (#102) (Friday, 10 November)
Re: [w3c/screen-orientation] Wide review tracker (#102) (Friday, 10 November)
Re: [w3c/permissions] Linked testing policy and fixed a few links (#164) (Tuesday, 7 November)
Re: [w3c/permissions] Linked testing policy and fixed a few links (#164) (Tuesday, 7 November)
Re: [w3c/screen-orientation] Confusiong between "_pending-promise_" and "doc's pending promise" (#94) (Sunday, 5 November)
Re: [w3c/screen-orientation] Reference correct promise at the "apply an orientation lock" operation (#110) (Sunday, 5 November)
Re: [w3c/screen-orientation] Clean-up anchors and definitions (#109) (Saturday, 4 November)
Re: [w3c/screen-orientation] Clean-up anchors and definitions (#109) (Saturday, 4 November)
Re: [w3c/screen-orientation] Reference correct promise at the "apply an orientation lock" operation (#110) (Saturday, 4 November)
Re: [w3c/screen-orientation] Add [SameObject] to the `Screen.orientation` attribute (#111) (Saturday, 4 November)
Re: [w3c/screen-orientation] Add [SameObject] to the `Screen.orientation` attribute (#111) (Saturday, 4 November)
Re: [w3c/screen-orientation] Clean-up anchors and definitions (#109) (Thursday, 2 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Thursday, 2 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)

Mardav Wala

Re: [w3c/webcomponents] Highlight code blocks, fix emphasis (#712) (Tuesday, 21 November)
Re: [w3c/webcomponents] Highlight code blocks, fix emphasis (#712) (Tuesday, 21 November)
Re: [w3c/webcomponents] Highlight code blocks, fix emphasis (#712) (Monday, 20 November)
[w3c/webcomponents] Highlight code blocks, fix emphasis (#712) (Monday, 20 November)

Marijn Kruisselbrink

Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Thursday, 30 November)
Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Thursday, 30 November)
Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Thursday, 30 November)
Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Thursday, 30 November)
Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Wednesday, 29 November)
Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Wednesday, 29 November)
Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Wednesday, 29 November)
Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Wednesday, 29 November)
Re: [w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Wednesday, 29 November)
[w3c/FileAPI] Add BlobPropertyBag.endings back to the spec. (#90) (Wednesday, 29 November)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Wednesday, 29 November)
[w3c/ServiceWorker] Delete foreign_fetch_explainer.md (#1236) (Tuesday, 28 November)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Tuesday, 28 November)
Re: [w3c/FileAPI] Clarify Lifetime of BlobStore (#89) (Tuesday, 28 November)
Re: [w3c/FileAPI] Clarify Lifetime of BlobStore (#89) (Tuesday, 28 November)
Re: [w3c/ServiceWorker] Run Job does not specify which event loop to queue its tasks on (#1224) (Tuesday, 14 November)
Re: [w3c/ServiceWorker] Why is the scope to registration map and ordered map? (#1225) (Tuesday, 14 November)
[w3c/ServiceWorker] Run Job does not specify which event loop to queue its tasks on (#1224) (Tuesday, 14 November)
Re: [w3c/FileAPI] Clarify Lifetime of BlobStore (#89) (Monday, 13 November)
Re: [w3c/ServiceWorker] Provide a way to ask the waiting Service Worker to skip waiting from the outside (#1223) (Monday, 13 November)
Re: [w3c/ServiceWorker] Provide a way to ask the waiting Service Worker to skip waiting from the outside (#1223) (Monday, 13 November)
Re: [w3c/ServiceWorker] Define procedure to convert options object of `sw.register()` to `Link` header (#979) (Friday, 3 November)

Mark Nottingham

Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Wednesday, 29 November)
Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Wednesday, 29 November)
Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609) (Wednesday, 8 November)

Markus Ast

Re: [w3c/webcomponents] Fix some typos, missing formating and erroneous Markdown in Template-Instantiation.md (#699) (Monday, 6 November)
[w3c/webcomponents] Fix some typos, missing formating and erroneous Markdown in Template-Instantiation.md (#699) (Monday, 6 November)

Masayuki Nakano

Re: [w3c/uievents] Add specification for AltGraph key & modifier behaviour (#147) (Wednesday, 15 November)
Re: [w3c/uievents] Bug in spec? event.key and casing (#169) (Monday, 13 November)

Matt Falkenhagen

Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Thursday, 30 November)
Re: [w3c/ServiceWorker] What happens to the request body if the fetch isn't handled? (#1191) (Monday, 20 November)
Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221) (Thursday, 9 November)
Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Thursday, 9 November)
[w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221) (Wednesday, 8 November)
Re: [w3c/ServiceWorker] is the browser required to start the ServiceWorker for postMessage() if there is no message event handler? (#1200) (Tuesday, 7 November)
Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204) (Tuesday, 7 November)
Re: [whatwg/fetch] Use the URL from the response, if it has one (#146) (Thursday, 2 November)

Matt Giuca

[w3c/manifest] Extension point should come after processing other members (#629) (Monday, 27 November)

Matthew Dean

Re: [w3c/webcomponents] Why do we really need hyphens? (#658) (Thursday, 2 November)

Matthew Phillips

Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Saturday, 11 November)
Re: [w3c/webcomponents] [templates] How to handle expressions in tables (#703) (Friday, 10 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Thursday, 2 November)

Max Nordlund

Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Tuesday, 7 November)

MeritBased

Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Tuesday, 14 November)

Michael Stramel

Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Friday, 3 November)
Re: [w3c/webcomponents] [proposals]: Template Instantiation typo? (#690) (Thursday, 2 November)

Michael[tm] Smith

Re: [whatwg/fetch] Aborting fetch (#523) (Thursday, 23 November)
Re: [w3c/ServiceWorker] Remove <link rel=serviceworker> (#1220) (Friday, 17 November)
[w3c/ServiceWorker] Remove <link rel=serviceworker> (#1220) (Wednesday, 8 November)
[w3c/webcomponents] Copy edits for all remaining parts (#687) (Thursday, 2 November)
[w3c/webcomponents] Copy edits to sections 3.1 and 3.2 (#686) (Thursday, 2 November)
[w3c/webcomponents] Copy-edits to Use Cases & Background sections (#679) (Thursday, 2 November)

Mictronics

Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Sunday, 19 November)
Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Thursday, 16 November)

Mike

Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Friday, 3 November)

Mike Frysinger

Re: [w3c/clipboard-apis] Support for reading custom MIME types from the clipboard (#46) (Thursday, 23 November)

Mike Taylor

Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Thursday, 2 November)
Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Thursday, 2 November)
Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Thursday, 2 November)

Mike West

Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 30 November)
Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Thursday, 23 November)
Re: [w3c/ServiceWorker] consider exposing credentials.get() but only when mediation is set to "silent" (#1231) (Wednesday, 22 November)
Re: [whatwg/storage] Bucket hooks (#18) (Tuesday, 21 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 20 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 13 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 13 November)
Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Monday, 6 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Friday, 3 November)
Re: [heycam/webidl] Add [InsecureContext] (#471) (Thursday, 2 November)

Mikhail Pozdnyakov

Re: [w3c/screen-orientation] Fix event firing (#112) (Friday, 3 November)
[w3c/screen-orientation] Fix event firing (#112) (Friday, 3 November)
Re: [w3c/screen-orientation] Orientation angle cannot be precisely mapped to orientation type for devices with 1:1 screen size ratio (#99) (Thursday, 2 November)
[w3c/screen-orientation] Add [SameObject] to the `Screen.orientation` attribute (#111) (Thursday, 2 November)
Re: [w3c/screen-orientation] Reference correct promise at the "apply an orientation lock" operation (#110) (Thursday, 2 November)
[w3c/screen-orientation] Reference correct promise at the "apply an orientation lock" operation (#110) (Thursday, 2 November)

Moonchild

Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Thursday, 23 November)
Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Thursday, 23 November)
Re: [whatwg/fetch] "3.3.1. ..." Allow on empty content-type (#636) (Wednesday, 22 November)
[whatwg/fetch] "3.3.1. Should response to request be blocked du..." (#636) (Wednesday, 22 November)

Morgan Conrad

Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Sunday, 5 November)

Mounir Lamouri

Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Wednesday, 29 November)
Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Wednesday, 22 November)
Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Thursday, 16 November)
Re: [w3c/screen-orientation] Wide review tracker (#102) (Friday, 10 November)
Re: [w3c/screen-orientation] Fix event firing (#112) (Friday, 3 November)
Re: [w3c/screen-orientation] Event firing needs fixes (#93) (Friday, 3 November)
Re: [w3c/screen-orientation] Fix event firing (#112) (Friday, 3 November)
Re: [w3c/screen-orientation] Add [SameObject] to the `Screen.orientation` attribute (#111) (Thursday, 2 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)
Re: [w3c/screen-orientation] Fix all ReSpec warnings (#108) (Wednesday, 1 November)

Nigel Megitt

Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214) (Tuesday, 7 November)

Nolan Lawson

Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224) (Thursday, 9 November)
Re: [w3c/IndexedDB] boolean should be a valid key (#76) (Thursday, 9 November)
Re: [w3c/manifest] Which "platform" should I use for Windows 10 UWP apps? (#580) (Thursday, 9 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Thursday, 9 November)
[w3c/IndexedDB] Prebuilt IndexedDB format (#224) (Tuesday, 7 November)

nondebug

Re: [w3c/gamepad] [Extensions] make pulse() more like navigator.vibrate (#66) (Tuesday, 28 November)
Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Thursday, 16 November)

Pat Mächler

Re: [w3c/ServiceWorker] Service worker ID - remove? (#1076) (Tuesday, 28 November)

patrick kettner

Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Tuesday, 7 November)

Paul Mason

Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Monday, 13 November)

Pedram Emrouznejad

Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Sunday, 5 November)
Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Saturday, 4 November)
Re: [w3c/webcomponents] Disconnected Events (#678) (Saturday, 4 November)
Re: [w3c/webcomponents] Disconnected Events (#678) (Friday, 3 November)
Re: [w3c/webcomponents] Disconnected Events (#678) (Friday, 3 November)
Re: [w3c/webcomponents] Disconnected Events (#678) (Thursday, 2 November)

Peter Linss

Re: [w3ctag/design-reviews] Request review for Scroll Boundary Behavior (#193) (Saturday, 25 November)
Re: [w3ctag/design-reviews] Request review for Scroll Boundary Behavior (#193) (Saturday, 25 November)
Re: [w3ctag/design-reviews] Editorial: change salutation (#209) (Tuesday, 7 November)

Philip Jägenstedt

Re: [whatwg/encoding] Need more changes for common deploy (#126) (Monday, 27 November)
Re: [whatwg/encoding] Need more changes for common deploy (#126) (Monday, 27 November)
Re: [whatwg/fullscreen] Add pointer to HTML about top layer and inertness (#15) (Thursday, 23 November)
Re: [whatwg/streams] Branch snapshot missing for algorithm-slots branch (#858) (Friday, 17 November)
Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Wednesday, 15 November)
Re: [heycam/webidl] Proposed solution to make grammar changes less disruptive (#477) (Tuesday, 14 November)
Re: [w3c/permissions] Introduce "Automation" section (#151) (Monday, 13 November)
Re: [w3c/permissions] Introduce "Automation" section (#151) (Sunday, 12 November)
Re: [whatwg/url] Meta: use the common deploy.sh (#351) (Saturday, 4 November)
Re: [whatwg/url] Meta: use the common deploy.sh (#351) (Saturday, 4 November)
Re: [w3c/permissions] Introduce "Automation" section (#151) (Saturday, 4 November)
Re: [w3c/DOM-Parsing] Ask for tests for normative changes in CONTRIBUTING.md (#32) (Friday, 3 November)
Re: [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Thursday, 2 November)
Re: [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Thursday, 2 November)
Re: [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Thursday, 2 November)

Philippe Le Hegaret

[w3c/permissions] Linked testing policy and fixed a few links (#164) (Tuesday, 7 November)

Philippe Ombredanne

Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
Re: [whatwg/url] Remove Googlefight links (#352) (Monday, 27 November)
[whatwg/url] Remove Googlefight links (#352) (Sunday, 12 November)

Photopea

Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 14 November)
[w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 13 November)

Przemysław Adamczewski

[w3c/webcomponents] Fix Handlebars typos (#692) (Thursday, 2 November)

RakeshLchanSarma

[w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226) (Wednesday, 15 November)
Re: [w3c/ServiceWorker] Authenticated PWA ? (#909) (Wednesday, 15 November)

rektide

Re: [whatwg/fetch] HTTP/2 server push support (#51) (Monday, 6 November)

Rick Byers

Re: [w3c/uievents] Expose wheel event scrolling state to DOM events (#170) (Thursday, 23 November)
Re: [w3c/uievents] Expose wheel event scrolling state to DOM events (#170) (Saturday, 11 November)
Re: [w3c/uievents] Update event-types.txt: Not all wheel events are cancelable. (#171) (Saturday, 11 November)
Re: [w3c/uievents] Update event-types.txt: Not all wheel events are cancelable. (#171) (Saturday, 11 November)
Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64) (Saturday, 11 November)

Rob Dodson

Re: [w3c/webcomponents] Custom attribute names conflicting with built-in attribute names (#654) (Friday, 3 November)
Re: [w3c/webcomponents] Custom attribute names conflicting with built-in attribute names (#654) (Friday, 3 November)
Re: [whatwg/dom] label-input association across Shadow DOM boundary (#530) (Thursday, 2 November)

Ryosuke Niwa

Re: [w3c/webcomponents] Highlight code blocks, fix emphasis (#712) (Tuesday, 21 November)
Re: [w3c/webcomponents] Highlight code blocks, fix emphasis (#712) (Tuesday, 21 November)
Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Wednesday, 15 November)
Re: [w3c/webcomponents] [template] How to remove a listener registered on createCallback (#708) (Tuesday, 14 November)
Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Tuesday, 14 November)
Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Tuesday, 14 November)
Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Tuesday, 14 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Tuesday, 14 November)
Re: [w3c/webcomponents] Add `customElements.upgrade` (#710) (Tuesday, 14 November)
Re: [w3c/webcomponents] [template]How to remove a listener registered on createCallback (#708) (Tuesday, 14 November)
Re: [w3c/webcomponents] Fix an arguments order of replaceChild (#706) (Tuesday, 14 November)
Re: [w3c/webcomponents] typo (#707) (Tuesday, 14 November)
Re: [w3c/webcomponents] [template] What if the `type` attribute is specified in the <template> but its processor is not registered? (#709) (Tuesday, 14 November)
Re: [w3c/webcomponents] Add `customElements.upgrade` (#710) (Monday, 13 November)
[w3c/webcomponents] Add `customElements.upgrade` (#710) (Monday, 13 November)
Re: [w3c/webcomponents] Add a missing parenthesis (#698) (Monday, 6 November)
Re: [w3c/webcomponents] Fix some typos, missing formating and erroneous Markdown in Template-Instantiation.md (#699) (Monday, 6 November)
Re: [w3c/webcomponents] Fix some typos, missing formating and erroneous Markdown in Template-Instantiation.md (#699) (Monday, 6 November)
Re: [w3c/webcomponents] [templates] Do not specify template binding syntax in spec, make configurable (#697) (Monday, 6 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] Is a global registry of template processors the right idea? (#681) (Saturday, 4 November)
Re: [w3c/webcomponents] Replace Em dash with hyphen minus (#696) (Saturday, 4 November)
Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Saturday, 4 November)
Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Saturday, 4 November)
Re: [w3c/webcomponents] Disconnected Events (#678) (Saturday, 4 November)
[whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Saturday, 4 November)
Re: [w3c/webcomponents] Disconnected Events (#678) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Friday, 3 November)
Re: [w3c/webcomponents] Custom attribute names conflicting with built-in attribute names (#654) (Friday, 3 November)
Re: [w3c/webcomponents] Disconnected Events (#678) (Friday, 3 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Friday, 3 November)
Re: [w3c/webcomponents] Custom attribute names conflicting with built-in attribute names (#654) (Friday, 3 November)
Re: [w3c/webcomponents] Fix template instantiation examples (#694) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] What is declareCallback? (#693) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Unclear usage of markdown-like syntax in state object (#689) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Unclear usage of markdown-like syntax in state object (#689) (Thursday, 2 November)
Re: [w3c/webcomponents] Copy edits for all remaining parts (#687) (Thursday, 2 November)
Re: [w3c/webcomponents] Copy edits for all remaining parts (#687) (Thursday, 2 November)
Re: [w3c/webcomponents] Copy edits for all remaining parts (#687) (Thursday, 2 November)
Re: [w3c/webcomponents] Copy edits for all remaining parts (#687) (Thursday, 2 November)
Re: [w3c/webcomponents] Copy edits for all remaining parts (#687) (Thursday, 2 November)
Re: [w3c/webcomponents] Fix Markdown styles of Template-Instantiation (#691) (Thursday, 2 November)
Re: [w3c/webcomponents] Fix Handlebars typos (#692) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Unclear usage of markdown-like syntax in state object (#689) (Thursday, 2 November)
Re: [w3c/webcomponents] Disconnected Events (#678) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [w3c/webcomponents] Copy edits to sections 3.1 and 3.2 (#686) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] API for updating (#685) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] No need for -Callback suffix (#684) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Is a global registry of template processors the right idea? (#681) (Thursday, 2 November)
Re: [w3c/webcomponents] [templates] Parts APIs surface concerns (#680) (Thursday, 2 November)
Re: [w3c/webcomponents] Copy-edits to Use Cases & Background sections (#679) (Thursday, 2 November)
Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Thursday, 2 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Wednesday, 1 November)

Sahel Sharify

Re: [w3c/uievents] Update event-types.txt: Not all wheel events are cancelable. (#171) (Wednesday, 22 November)
Re: [w3c/uievents] Expose wheel event scrolling state to DOM events (#170) (Monday, 13 November)
Re: [w3c/uievents] Expose wheel event scrolling state to DOM events (#170) (Monday, 13 November)
[w3c/uievents] Update event-types.txt: Not all wheel events are cancelable. (#171) (Friday, 10 November)
[w3c/uievents] Expose wheel event scrolling state to DOM events (#170) (Wednesday, 8 November)

Salvador de la Puente González

Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Tuesday, 7 November)

Sean D

Re: [w3c/webcomponents] Why do we really need hyphens? (#658) (Wednesday, 8 November)
Re: [w3c/webcomponents] Why do we really need hyphens? (#658) (Saturday, 4 November)
Re: [w3c/webcomponents] Why do we really need hyphens? (#658) (Thursday, 2 November)

Shiino Yuki

Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Tuesday, 21 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Monday, 20 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Friday, 17 November)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Friday, 17 November)

Simon Stewart

Re: [w3c/permissions] Introduce "Automation" section (#151) (Friday, 10 November)

sleevi

Re: [whatwg/fetch] section #connections is vague wrt connection is HTTP or HTTPS or HTTP/2 or QUIC (#641) (Thursday, 30 November)
Re: [whatwg/fetch] section #connections is vague wrt connection is HTTP or HTTPS or HTTP/2 or QUIC (#641) (Thursday, 30 November)
Re: [whatwg/fetch] Why does Fetch specify a max redirect count of 20? (#576) (Wednesday, 8 November)

smaug----

Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Tuesday, 14 November)
[w3c/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Friday, 10 November)
[w3c/webcomponents] [templates] implement a polyfill of template-instantiation before even considering to add the API natively to the platform (#702) (Friday, 10 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Thursday, 9 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Thursday, 9 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Wednesday, 8 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Wednesday, 8 November)
Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Tuesday, 7 November)
Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Sunday, 5 November)
Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Saturday, 4 November)
Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Saturday, 4 November)
Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Thursday, 2 November)
Re: [whatwg/dom] "node's tree" seems to be an undefined concept (#526) (Wednesday, 1 November)
Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Wednesday, 1 November)

Snazzypeanuts

Re: [whatwg/xhr] I think I have a bug (#170) (Friday, 3 November)
[whatwg/xhr] I think I have a bug (#170) (Friday, 3 November)
Re: [whatwg/xhr] Im in need of some guidance please (#168) (Thursday, 2 November)
[whatwg/xhr] Im in need of some guidance please (#168) (Thursday, 2 November)

snuggs

Re: [w3c/webcomponents] Add `customElements.upgrade` (#710) (Tuesday, 14 November)
Re: [w3c/webcomponents] Add `customElements.upgrade` (#710) (Tuesday, 14 November)

staktrace

Re: [w3c/uievents] Expose wheel event scrolling state to DOM events (#170) (Monday, 13 November)
Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64) (Monday, 13 November)

Stephan Schneider

Re: [w3c/webcomponents] Fix template instantiation examples (#694) (Thursday, 2 November)
[w3c/webcomponents] Fix template instantiation examples (#694) (Thursday, 2 November)

Tab Atkins Jr.

Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Friday, 17 November)
Re: [whatwg/dom] Compute everything needed for composedPath() during dispatch (#535) (Friday, 17 November)
Re: [w3c/webcomponents] [templates] Consider ${foo} instead of {{foo}} (#688) (Thursday, 2 November)

Takayoshi Kochi

Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Monday, 27 November)
[w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Wednesday, 22 November)
Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Thursday, 16 November)
Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Tuesday, 14 November)
Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Tuesday, 14 November)
Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Tuesday, 14 November)

Takeshi Yoshino

Re: [whatwg/fetch] Define RST_STREAM's error code (#637) (Friday, 24 November)
Re: [whatwg/fetch] WebSocket handshake has no referrer (#632) (Wednesday, 15 November)
Re: [whatwg/fetch] WebSocket handshake has no referrer (#632) (Wednesday, 15 November)
Re: [whatwg/fetch] WebSocket handshake has no referrer (#632) (Wednesday, 15 November)
Re: [whatwg/fetch] WebSocket connections don't appear to send referrers (#630) (Wednesday, 15 November)
Re: [whatwg/fetch] WebSocket connections don't appear to send referrers (#630) (Wednesday, 15 November)

Tantek Çelik

Re: [w3ctag/design-reviews] HTML General Review (#174) (Wednesday, 15 November)
Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Thursday, 9 November)

Ted Mielczarek

Re: [w3c/gamepad] About the id (#65) (Monday, 27 November)

Tejas Kumar

Re: [whatwg/streams] Remove transform streams tests as they are now upstream (#854) (Sunday, 12 November)
Re: [whatwg/fetch] Reject Promise on Error Response (#627) (Tuesday, 7 November)
Re: [whatwg/fetch] Reject Promise on Error Response (#627) (Tuesday, 7 November)
Re: [whatwg/fetch] Reject Promise on Error Response (#627) (Tuesday, 7 November)
Re: [whatwg/fetch] Reject Promise on Error Response (#627) (Tuesday, 7 November)
Re: [whatwg/fetch] Reject Promise on Error Response (#627) (Tuesday, 7 November)
[whatwg/fetch] Reject promise on Error Response (#627) (Tuesday, 7 November)
Re: [whatwg/streams] Add examples by @TejasQ (f29508c) (Monday, 6 November)
Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Friday, 3 November)
Re: [whatwg/streams] Added a couple of examples (#853) (Thursday, 2 November)
[whatwg/streams] Added a couple of examples (#853) (Thursday, 2 November)
Re: [whatwg/streams] Standard text for TransformStream (#811) (Thursday, 2 November)
Re: [whatwg/streams] Standard text for TransformStream (#811) (Thursday, 2 November)
Re: [whatwg/streams] Standard text for TransformStream (#811) (Thursday, 2 November)

Thomas Steiner

Re: [whatwg/fetch] Generic Accept header value */* and Service Workers (#634) (Tuesday, 21 November)
Re: [whatwg/fetch] Generic Accept header value */* and Service Workers (#634) (Monday, 20 November)
[whatwg/fetch] Generic ```Accept``` header value ```*/*``` and Service Workers (#634) (Monday, 20 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Tuesday, 7 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Sunday, 5 November)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Sunday, 5 November)

Till Schneidereit

[whatwg/streams] Don't error canceled branches when erroring a teed stream (#859) (Friday, 17 November)

Tim van der Lippe

[w3c/webcomponents] [templates] Unclear usage of markdown-like syntax in state object (#689) (Thursday, 2 November)

Timo Tijhof

Re: [w3c/ServiceWorker] Mixed feelings about ServiceWorker for module loader (#1203) (Tuesday, 28 November)

Timothy Gu

[whatwg/dom] Use mixins in IDL definitions (#529) (Thursday, 2 November)

Tobie Langel

Re: [heycam/webidl] Amirhosein (#481) (Saturday, 25 November)
Re: [heycam/webidl] Active (#480) (Saturday, 25 November)
Re: [heycam/webidl] Some means to signal that a method requires user action to be called (#479) (Thursday, 23 November)
Re: [heycam/webidl] Some means to signal that a method requires user action to be called (#479) (Thursday, 23 November)
Re: [heycam/webidl] Some means to signal that a method requires user action to be called (#479) (Thursday, 23 November)
Re: [heycam/webidl] [spam] (#478) (Saturday, 18 November)
Re: [whatwg/streams] Branch snapshot missing for algorithm-slots branch (#858) (Friday, 17 November)
Re: [whatwg/streams] Branch snapshot missing for algorithm-slots branch (#858) (Friday, 17 November)
Re: [heycam/webidl] Make [Exposed] mandatory, remove [PrimaryGlobal] (#423) (Wednesday, 15 November)
Re: [heycam/webidl] Proposed solution to make grammar changes less disruptive (#477) (Wednesday, 15 November)
[heycam/webidl] Proposed solution to make grammar changes less disruptive (#477) (Monday, 13 November)
Re: [heycam/webidl] Various named property stuff seems confused in the face of symbols (#175) (Monday, 13 November)
Re: [heycam/webidl] Replace remaining emu-t.symbol (#475) (Monday, 6 November)
Re: [heycam/webidl] static/stringifer RegularOperation (#474) (Monday, 6 November)
Re: [heycam/webidl] Order of includes statements is not a well-defined concept (#473) (Friday, 3 November)
Re: [heycam/webidl] Can SpecialOperation be more simplified? (#470) (Friday, 3 November)
Re: [whatwg/dom] Use mixins in IDL definitions (#529) (Friday, 3 November)
[whatwg/storage] Update WebIDL definition(s) to use new mixin syntax (#53) (Friday, 3 November)
[whatwg/fetch] Update WebIDL definition(s) to use new mixin syntax (#624) (Friday, 3 November)
[whatwg/dom] Update WebIDL definition(s) to use new mixin syntax (#532) (Friday, 3 November)
Re: [heycam/webidl] Track PR #433 (#472) (Friday, 3 November)
[heycam/webidl] Track PR #433 (#472) (Friday, 3 November)
Re: [whatwg/dom] Use mixins in IDL definitions (#529) (Friday, 3 November)
Re: [heycam/webidl] Add [InsecureContext] (#471) (Thursday, 2 November)

Tomek Wytrębowicz

Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Tuesday, 28 November)
Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Tuesday, 28 November)
Re: [whatwg/dom] label-input association across Shadow DOM boundary (#530) (Thursday, 9 November)
Re: [whatwg/dom] label-input association across Shadow DOM boundary (#530) (Thursday, 9 November)
Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Wednesday, 8 November)
Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 8 November)
[whatwg/dom] label-input association across Shadow DOM boundary (#530) (Thursday, 2 November)
Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 1 November)

Tomoyuki Shimizu

Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Thursday, 9 November)

Toni-Jan Keith Monserrat

Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 1 November)

Toru Kobayashi

Re: [w3c/webcomponents] [template] How to remove a listener registered on createCallback (#708) (Tuesday, 14 November)
[w3c/webcomponents] [template]How to remove a listener registered on createCallback (#708) (Monday, 13 November)
Re: [w3c/webcomponents] Fix an arguments order of replaceChild (#706) (Monday, 13 November)
[w3c/webcomponents] Fix an arguments order of replaceChild (#706) (Monday, 13 November)
Re: [w3c/webcomponents] Add a missing parenthesis (#698) (Monday, 6 November)
[w3c/webcomponents] Add a missing parenthesis (#698) (Monday, 6 November)
Re: [w3c/webcomponents] Replace Em dash with hyphen minus (#696) (Sunday, 5 November)
Re: [w3c/webcomponents] Replace Em dash with hyphen minus (#696) (Saturday, 4 November)
[w3c/webcomponents] Replace Em dash with hyphen minus (#696) (Saturday, 4 November)
Re: [w3c/webcomponents] Fix Markdown styles of Template-Instantiation (#691) (Thursday, 2 November)
[w3c/webcomponents] Fix Markdown styles of Template-Instantiation (#691) (Thursday, 2 November)

Travis Leithead

Re: [w3ctag/design-reviews] Request for TAG review of Input events level 2 (#173) (Tuesday, 21 November)
Re: [w3ctag/design-reviews] Review request for WebVR (#185) (Monday, 20 November)
Re: [w3ctag/design-reviews] ReportingObserver (#195) (Monday, 20 November)
Re: [w3ctag/design-reviews] WebAssembly Response API / Web Embedding (#167) (Wednesday, 8 November)
[w3ctag/design-reviews] Dusting off Web Speech API? (#214) (Tuesday, 7 November)
Re: [w3c/DOM-Parsing] Ask for tests for normative changes in CONTRIBUTING.md (#32) (Friday, 3 November)
Re: [w3c/DOM-Parsing] Ask for tests for normative changes in CONTRIBUTING.md (#32) (Friday, 3 November)

Trey Shugart

Re: [whatwg/dom] Composed shadow DOM (#531) (Friday, 3 November)
Re: [whatwg/dom] Composed shadow DOM (#531) (Thursday, 2 November)
[whatwg/dom] Composed shadow DOM (#531) (Thursday, 2 November)
Re: [whatwg/dom] Declarative Shadow DOM (#510) (Thursday, 2 November)
Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 1 November)

triple-underscore

Re: [w3c/uievents] Dispatch mouseenter/leave/out/over when the layout (or scroll) changes (#154) (Wednesday, 29 November)

vanupam

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

Victor Costan

Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Wednesday, 29 November)

victoriasu

[w3ctag/design-reviews] CSS Selectors 4 (#219) (Thursday, 30 November)

Vincent Scheib

[w3c/pointerlock] Add non-normative text describing common implementation concerns (#29) (Thursday, 9 November)
Re: [w3c/pointerlock] Raw movement data, not pixel location clamped (#28) (Thursday, 9 November)
Re: [w3c/pointerlock] Time at TPAC? (#22) (Thursday, 9 November)
Re: [w3c/pointerlock] Time at TPAC? (#22) (Thursday, 9 November)
Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Wednesday, 8 November)

Vitaly Dmitriev

Re: [w3c/webcomponents] Why do we really need hyphens? (#658) (Wednesday, 8 November)

Walle Cyril

Re: [w3c/gamepad] `navigator.getGamepads()` should return a `Promise` (#23) (Tuesday, 28 November)
[w3c/gamepad] [Extensions] make pulse() more like navigator.vibrate (#66) (Tuesday, 28 November)
[w3c/gamepad] About the id (#65) (Saturday, 25 November)
Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Saturday, 25 November)

Wired Earp

Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Saturday, 4 November)
Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695) (Friday, 3 November)

wuyandefeixue

[w3c/IndexedDB] indexedDb The first time using the index query takes too long (#225) (Friday, 24 November)

Xiaocheng Hu

[w3c/clipboard-apis] Should clipboard actions consider whether selection has focus? (#57) (Thursday, 30 November)

Xiaoqian Wu

Re: [w3c/webcomponents] Fix some typos, missing formating and erroneous Markdown in Template-Instantiation.md (#699) (Monday, 6 November)

xtofian

Re: [w3c/webcomponents] [templates] Contextual auto-escaping (#711) (Wednesday, 22 November)

Yoichi Osato

Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79) (Saturday, 11 November)
Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Friday, 10 November)
Re: [w3c/selection-api] Support multi range selection (#41) (Thursday, 9 November)
Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Wednesday, 8 November)

Yutaka Hirano

Re: [whatwg/fetch] More eargerly send RST_STREAM on redirects (#638) (Sunday, 26 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Friday, 24 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Friday, 24 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Friday, 24 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Tuesday, 21 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Tuesday, 21 November)
Re: [whatwg/fetch] Clarify semantics of checking done, closed, etc. states of a null body stream (#635) (Tuesday, 21 November)
Re: [whatwg/url] Should URLSearchParams stringify be called in URL constructor? (#350) (Wednesday, 1 November)

Yves Lafon

Re: [w3c/workers] `SharedWorker` secure context integration. (#6) (Wednesday, 29 November)
Re: [w3c/gamepad] About the id (#65) (Monday, 27 November)
Re: [w3c/ServiceWorker] Cache.addAll() and .add() needs to accept an init argument to use for fetch() (#1233) (Monday, 27 November)
Re: [w3c/ServiceWorker] add w3cid for editors to help publication (#1218) (Friday, 3 November)
Re: [w3c/ServiceWorker] add w3cid for editors to help publication (#1218) (Friday, 3 November)
[w3c/ServiceWorker] add w3cid for editors to help publication (#1218) (Thursday, 2 November)
Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Thursday, 2 November)

王镇

Re: [whatwg/fetch] Add timeout option (#20) (Sunday, 19 November)

Last message date: Thursday, 30 November 2017 22:56:57 UTC