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

Aaron David Goldman

• Re: [w3c/permissions] Add optional consent due to GDPR (#169) (Wednesday, 7 February)

Abdón Rodríguez Davila

• Re: [w3c/WebPlatformWG] Add references to Template instantiation & HTML modules (#110) (Monday, 26 February)
• Re: [w3c/WebPlatformWG] Add references to Template instantiation & HTML modules (#110) (Monday, 26 February)
• [w3c/WebPlatformWG] Add references to Template instantiation & HTML modules (#110) (Monday, 19 February)
• [w3c/WebPlatformWG] Update Attending (#109) (Monday, 19 February)
• Re: [w3c/WebPlatformWG] Add Github profile links to attendees (#107) (Thursday, 15 February)
• [w3c/WebPlatformWG] Add Github profile links to attendees (#107) (Thursday, 15 February)

Adam Rice

• Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Tuesday, 27 February)
• Re: [whatwg/streams] pipeTo() text appears to say all queued writable chunks must be written on readable error (#738) (Tuesday, 27 February)
• Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882) (Tuesday, 27 February)
• Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Tuesday, 27 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 27 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 27 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Friday, 23 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 22 February)
• Re: [whatwg/streams] Fix miscellaneous spelling mistakes (#888) (Wednesday, 21 February)
• [whatwg/streams] Fix miscellaneous spelling mistakes (#888) (Wednesday, 21 February)
• Re: [whatwg/streams] Editorial: fix some double-word typos (#887) (Wednesday, 21 February)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Monday, 19 February)
• Re: [whatwg/streams] Write tests for the fixes in #870 (#879) (Monday, 19 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Monday, 19 February)
• Re: [whatwg/streams] Suppress Bikeshed warnings about <vars> used once (#883) (Monday, 19 February)
• Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Friday, 16 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Friday, 16 February)
• Re: [whatwg/streams] Write tests for the fixes in #870 (#879) (Friday, 16 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 15 February)
• [whatwg/streams] Suppress Bikeshed warnings about <vars> used once (#883) (Thursday, 15 February)
• Re: [whatwg/streams] Provide a way for the underlying sink to signal write progress? (#876) (Thursday, 15 February)
• Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877) (Thursday, 15 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 15 February)
• Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882) (Thursday, 15 February)
• Re: [whatwg/streams] Fix example for identity transform (#881) (Wednesday, 14 February)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Friday, 9 February)
• [whatwg/streams] Write tests for the fixes in #870 (#879) (Friday, 9 February)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Friday, 9 February)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Friday, 9 February)
• [whatwg/streams] Disambiguate links to "resolve" (#878) (Friday, 9 February)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Friday, 9 February)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Friday, 9 February)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Friday, 9 February)
• Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877) (Friday, 9 February)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Thursday, 8 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 8 February)
• Re: [whatwg/streams] "await writer.write(bytes);" in example seems wrong (#874) (Thursday, 8 February)
• Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668) (Thursday, 8 February)
• Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668) (Thursday, 8 February)
• Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877) (Thursday, 8 February)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Wednesday, 7 February)
• Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877) (Wednesday, 7 February)
• [whatwg/fetch] "If signal is not null, then add the following a..." (#668) (Wednesday, 7 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 6 February)
• Re: [whatwg/streams] Provide a way for the underlying sink to signal write progress? (#876) (Thursday, 1 February)

ahulab

• [w3c/uievents] single character typo fix (#182) (Tuesday, 13 February)

Aleksandar Totic

• Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187) (Wednesday, 28 February)

Alex Russell

• Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Saturday, 24 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 16 February)
• Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Friday, 16 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 9 February)
• Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Friday, 2 February)
• Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Friday, 2 February)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Friday, 2 February)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Friday, 2 February)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Friday, 2 February)
• Re: [w3ctag/design-reviews] CSS Layout API (#224) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Trusted Types (#198) (Thursday, 1 February)
• Re: [w3ctag/design-reviews] ads.txt (#201) (Thursday, 1 February)

aliams

• Re: [w3c/IndexedDB] Track ES BigInt work (#230) (Monday, 19 February)
• Re: [w3c/IndexedDB] Track ES BigInt work (#230) (Monday, 19 February)

Andrea Giammarchi

• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 28 February)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 28 February)
• Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Thursday, 22 February)
• Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Wednesday, 21 February)

Andrew Betts

• Re: [w3ctag/design-reviews] Web Locks API (#217) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Consider general storage observer that works for cookies (#210) (Friday, 2 February)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Consider general storage observer that works for cookies (#210) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Img decoding attribute (#220) (Friday, 2 February)
• Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Friday, 2 February)
• Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Friday, 2 February)
• Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226) (Friday, 2 February)
• Re: [w3ctag/design-reviews] ReportingObserver (#195) (Thursday, 1 February)
• Re: [w3ctag/design-reviews] Web Locks API (#217) (Thursday, 1 February)
• Re: [w3ctag/design-reviews] ads.txt (#201) (Thursday, 1 February)
• Re: [w3ctag/design-reviews] ads.txt (#201) (Thursday, 1 February)

Anne van Kesteren

• Re: [w3c/uievents] Move focus section to HTML (#185) (Wednesday, 28 February)
• Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674) (Wednesday, 28 February)
• Re: [w3c/uievents] Move focus section to HTML (#185) (Wednesday, 28 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 28 February)
• Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Tuesday, 27 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 27 February)
• [w3c/uievents] Move focus section to HTML (#185) (Tuesday, 27 February)
• Re: [whatwg/dom] chrome, doesn't accept preventDefault and still cancelable is true (#579) (Tuesday, 27 February)
• Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Tuesday, 27 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 27 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 27 February)
• Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674) (Tuesday, 27 February)
• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Monday, 26 February)
• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Monday, 26 February)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Monday, 26 February)
• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Monday, 26 February)
• Re: [w3c/IndexedDB] Define storage operation of non-trivial StructuredSerializeForStorage records (e.g. Blob/File) (#203) (Monday, 26 February)
• Re: [w3c/IndexedDB] Security and Web Worker access for IndexedDB (#141) (Monday, 26 February)
• Re: [w3c/IndexedDB] Add support for URL as one of the basic types like Date (#108) (Monday, 26 February)
• Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Monday, 26 February)
• Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Monday, 26 February)
• Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Monday, 26 February)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Monday, 26 February)
• Re: [whatwg/dom] chrome, doesn't accept preventDefault and still cancelable is true (#579) (Monday, 26 February)
• Re: [whatwg/dom] chrome, doesn't accept preventDefault and still cancelable is true (#579) (Monday, 26 February)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Monday, 26 February)
• Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572) (Monday, 26 February)
• Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Monday, 26 February)
• Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Sunday, 25 February)
• Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572) (Saturday, 24 February)
• Re: [whatwg/dom] Return value for DOMTokenList's replace() (#577) (Saturday, 24 February)
• Re: [whatwg/fetch] :read-only and :read-write selectors: Consistency and cross-UA behavior (#672) (Friday, 23 February)
• Re: [whatwg/fetch] :read-only and :read-write selectors: Consistency and cross-UA behavior (#672) (Friday, 23 February)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Friday, 23 February)
• Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526) (Friday, 23 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Friday, 23 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Friday, 23 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Friday, 23 February)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 22 February)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Thursday, 22 February)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Thursday, 22 February)
• Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737) (Thursday, 22 February)
• Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737) (Thursday, 22 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Thursday, 22 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Thursday, 22 February)
• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Wednesday, 21 February)
• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Wednesday, 21 February)
• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Wednesday, 21 February)
• Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609) (Wednesday, 21 February)
• Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609) (Wednesday, 21 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Wednesday, 21 February)
• Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717) (Wednesday, 21 February)
• Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Close this repository in the future (#652) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Which standard defines :defined (#665) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Which standard defines :defined (#665) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Interface/class-based selector (#719) (Wednesday, 21 February)
• Re: [whatwg/xhr] XMLHttpRequest (#193) (Wednesday, 21 February)
• Re: [whatwg/dom] Extend `attachShadow()` safelist (#571) (Wednesday, 21 February)
• Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572) (Tuesday, 20 February)
• Re: [whatwg/xhr] XMLHttpRequest (#193) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Tuesday, 20 February)
• Re: [whatwg/xhr] XMLHttpRequest (#193) (Tuesday, 20 February)
• Re: [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192) (Tuesday, 20 February)
• Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572) (Tuesday, 20 February)
• [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Tuesday, 20 February)
• Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575) (Tuesday, 20 February)
• Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575) (Tuesday, 20 February)
• Re: [whatwg/dom] Align with Selectors (#573) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Tuesday, 20 February)
• Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813) (Tuesday, 20 February)
• Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Tuesday, 20 February)
• Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Tuesday, 20 February)
• Re: [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192) (Tuesday, 20 February)
• Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Close this repository in the future (#652) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Monday, 19 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Monday, 19 February)
• Re: [whatwg/dom] Batched MutationObserver callbacks make it possibly difficult to reduce changes. (#484) (Monday, 19 February)
• Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575) (Monday, 19 February)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 19 February)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 19 February)
• Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575) (Monday, 19 February)
• [whatwg/dom] Hook for SVG and HTML script element insertion (#575) (Monday, 19 February)
• [heycam/webidl] Change dictionary section to encourage Infra wording (#524) (Monday, 19 February)
• Re: [whatwg/dom] Editorial: consider linking "present" consistently (#574) (Monday, 19 February)
• [whatwg/dom] Editorial: consider linking "present" consistently (#574) (Monday, 19 February)
• Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572) (Monday, 19 February)
• [whatwg/dom] Align with Selectors (#573) (Monday, 19 February)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 19 February)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Monday, 19 February)
• Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572) (Monday, 19 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Monday, 19 February)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Monday, 19 February)
• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Monday, 19 February)
• [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572) (Monday, 19 February)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Monday, 19 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Monday, 19 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Monday, 19 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Monday, 19 February)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 19 February)
• Re: [w3c/webcomponents] Close this repository in the future (#652) (Monday, 19 February)
• Re: [w3c/webcomponents] Close this repository in the future (#652) (Monday, 19 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Monday, 19 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Monday, 19 February)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Sunday, 18 February)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Sunday, 18 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Sunday, 18 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Sunday, 18 February)
• Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Sunday, 18 February)
• [whatwg/dom] Extend `attachShadow()` safelist (#571) (Sunday, 18 February)
• Re: [w3c/webcomponents] aggravate => aggregate (#724) (Sunday, 18 February)
• Re: [w3c/webcomponents] Detecting finally-distributed nodes. (#675) (Sunday, 18 February)
• Re: [w3c/webcomponents] Detecting finally-distributed nodes. (#675) (Sunday, 18 February)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Sunday, 18 February)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Sunday, 18 February)
• Re: [w3c/webcomponents] Why do we really need hyphens? (#658) (Sunday, 18 February)
• Re: [w3c/webcomponents] Why do we really need hyphens? (#658) (Sunday, 18 February)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Sunday, 18 February)
• Re: [w3c/webcomponents] ARIA custom element API (#159) (Sunday, 18 February)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Sunday, 18 February)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Sunday, 18 February)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Sunday, 18 February)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Sunday, 18 February)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Sunday, 18 February)
• Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717) (Sunday, 18 February)
• Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717) (Sunday, 18 February)
• Re: [w3c/webcomponents] Add a CSS subtype selector. (#719) (Sunday, 18 February)
• Re: [w3c/webcomponents] Add a CSS subtype selector. (#719) (Sunday, 18 February)
• Re: [whatwg/xhr] The logic in the WPT send-authentication-competing-names-passwords.htm does not match the spec. (#191) (Sunday, 18 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Sunday, 18 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Sunday, 18 February)
• Re: [whatwg/url] "Let pointer be a pointer to first code point in..." (#373) (Sunday, 18 February)
• Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737) (Sunday, 18 February)
• Re: [w3c/webcomponents] components v1 native implementation - inner components problem (#615) (Saturday, 17 February)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Saturday, 17 February)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Saturday, 17 February)
• Re: [w3c/webcomponents] Bulk property updates (#718) (Saturday, 17 February)
• Re: [w3c/webcomponents] Interfaces for web components (#725) (Saturday, 17 February)
• Re: [w3c/webcomponents] Interfaces for web components (#725) (Saturday, 17 February)
• Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715) (Saturday, 17 February)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Saturday, 17 February)
• Re: [w3c/webcomponents] Disconnected Events (#678) (Saturday, 17 February)
• Re: [w3c/webcomponents] Disconnected Events (#678) (Saturday, 17 February)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Saturday, 17 February)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Saturday, 17 February)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Saturday, 17 February)
• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Saturday, 17 February)
• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Saturday, 17 February)
• Re: [whatwg/fetch] Proposal: Easier request/response rewrites (#671) (Saturday, 17 February)
• Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736) (Friday, 16 February)
• Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736) (Friday, 16 February)
• Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730) (Friday, 16 February)
• Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730) (Friday, 16 February)
• Re: [w3c/webcomponents] Input requested on ARIA/HTML role parity (#729) (Friday, 16 February)
• Re: [w3c/webcomponents] Input requested on ARIA/HTML role parity (#729) (Friday, 16 February)
• Re: [whatwg/fetch] Proposal: Easier request/response rewrites (#671) (Friday, 16 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Friday, 16 February)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Friday, 16 February)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Friday, 16 February)
• Re: [whatwg/fetch] Location header is the empty string (#669) (Friday, 16 February)
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Friday, 16 February)
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Friday, 16 February)
• Re: [whatwg/dom] Removing event listeners through an identifier (#208) (Friday, 16 February)
• Re: [whatwg/dom] DOM ready is error prone, still requires libs, could be simpler: a document#ready Promise (#568) (Friday, 16 February)
• Re: [whatwg/dom] DOM ready is error prone, still requires libs, could be simpler: a document#ready Promise (#568) (Friday, 16 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Friday, 16 February)
• Re: [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522) (Friday, 16 February)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Friday, 16 February)
• Re: [whatwg/xhr] Please add followRedirects=true/false to XMLHttpRequest specification (#189) (Friday, 16 February)
• Re: [whatwg/xhr] Please add followRedirects=true/false to XMLHttpRequest specification (#189) (Friday, 16 February)
• Re: [w3c/gamepad] Add [Exposed] to all interfaces (#63) (Friday, 16 February)
• Re: [w3c/webstorage] Make session/localstorage iteratable (#8) (Friday, 16 February)
• [whatwg/url] Consider adding non-throwing URL.parse(input, base) (#372) (Monday, 5 February)
• Re: [whatwg/xhr] Fix send() charset overriding to use new MIME type infrastructure (#188) (Monday, 5 February)
• Re: [whatwg/xhr] Look at overrideMimeType() again (#157) (Monday, 5 February)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 5 February)
• Re: [heycam/webidl] Is an interface named I exposed in realm R (#518) (Monday, 5 February)
• [heycam/webidl] Is an interface named I exposed in realm R (#518) (Sunday, 4 February)
• Re: [w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728) (Sunday, 4 February)
• Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Saturday, 3 February)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Saturday, 3 February)
• Re: [whatwg/dom] Change handling of is="" in element creation and cloning (#566) (Saturday, 3 February)
• Re: [whatwg/dom] Export attribute change steps (#567) (Saturday, 3 February)
• Re: [whatwg/dom] Export attribute change steps (#567) (Saturday, 3 February)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Friday, 2 February)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Friday, 2 February)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Friday, 2 February)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Friday, 2 February)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Thursday, 1 February)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Thursday, 1 February)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Thursday, 1 February)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Thursday, 1 February)
• Re: [whatwg/fetch] Should fetches to blob URLs be more restricted? (#666) (Thursday, 1 February)

Anssi Kostiainen

• Re: [w3c/manifest] Improve references and minor fixups (#656) (Thursday, 22 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Thursday, 22 February)
• Re: [w3c/manifest] Use infra spec and data-cite (#655) (Tuesday, 20 February)

Anton Rusinov

• Re: [w3c/webcomponents] typo (#732) (Wednesday, 7 February)

Ashley (Scirra)

• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Tuesday, 27 February)
• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Friday, 23 February)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Sunday, 18 February)

Ben Kelly

• Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674) (Wednesday, 28 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Tuesday, 20 February)
• Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221) (Monday, 19 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Monday, 19 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Wednesday, 14 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Tuesday, 13 February)
• Re: [w3c/ServiceWorker] passthrough service worker can break sites using redirected stylesheets (#757) (Tuesday, 13 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Monday, 12 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Monday, 12 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Friday, 9 February)
• [w3c/ServiceWorker] ready promise is kind of weird after you call unregister() (#1279) (Friday, 9 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Friday, 9 February)
• [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221) (Thursday, 8 February)
• Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221) (Thursday, 8 February)
• Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221) (Tuesday, 6 February)
• Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221) (Tuesday, 6 February)
• Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273) (Friday, 2 February)
• Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273) (Friday, 2 February)
• Re: [w3c/ServiceWorker] `Clear Registration` should call `Update Registration State` before `Update Worker State` (#1270) (Friday, 2 February)
• Re: [w3c/ServiceWorker] `Clear Registration` should call `Update Registration State` before `Update Worker State` (#1270) (Friday, 2 February)
• Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273) (Friday, 2 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 2 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 2 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 2 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 2 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 2 February)
• [w3c/ServiceWorker] maybe explicitly set the `self.registration` DOM object on `ServiceWorkerGlobalScope` (#1271) (Thursday, 1 February)
• [w3c/ServiceWorker] `Clear Registration` should call `Update Registration State` before `Update Worker State` (#1270) (Thursday, 1 February)
• Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267) (Thursday, 1 February)
• Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267) (Thursday, 1 February)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Thursday, 1 February)

Benjamin C. Wiley Sittler

• Re: [w3c/ServiceWorker] The Cache objects do not expire unless authors *or users* delete the entries. (#1276) (Saturday, 3 February)
• [w3c/ServiceWorker] The Cache objects do not expire unless authors *or users* delete the entries. (#1276) (Saturday, 3 February)

BigBlueHat

• Re: [w3ctag/packaging-on-the-web] Please "un-gut" this specification (#35) (Thursday, 22 February)
• [w3ctag/packaging-on-the-web] Please "un-gut" this specification (#35) (Friday, 2 February)

billmoser

• Re: [w3c/webcomponents] Consider adding user-defined attributes to slots (#733) (Friday, 9 February)
• Re: [w3c/webcomponents] Consider adding user-defined attributes to slots (#733) (Friday, 9 February)
• [w3c/webcomponents] Consider adding user-defined attributes to slots (#733) (Thursday, 8 February)

Bnaya Peretz

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

bobbypalm68

• [whatwg/fetch] Bob (#673) (Friday, 23 February)

Boris Zbarsky

• Re: [heycam/webidl] ES bindings for constants on Globals (#528) (Tuesday, 27 February)
• Re: [heycam/webidl] Add bigint type (#525) (Tuesday, 27 February)
• Re: [heycam/webidl] ES bindings for constants on Globals (#528) (Tuesday, 27 February)
• Re: [heycam/webidl] Add bigint type (#525) (Tuesday, 27 February)
• Re: [heycam/webidl] Add bigint type (#525) (Tuesday, 27 February)
• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Monday, 26 February)
• Re: [heycam/webidl] Remove definition of class strings of default iterator objects (#501) (Friday, 23 February)
• Re: [heycam/webidl] Add bigint type (#525) (Friday, 23 February)
• Re: [heycam/webidl] Add bigint type (#525) (Thursday, 22 February)
• Re: [heycam/webidl] Add bigint type (#525) (Thursday, 22 February)
• Re: [heycam/webidl] Remove definition of class strings of default iterator objects (#501) (Wednesday, 21 February)
• Re: [heycam/webidl] Return type on identifier-less named/indexed setter is pointless (#523) (Saturday, 17 February)
• [heycam/webidl] Return type on identifier-less named/indexed setter is pointless (#523) (Thursday, 15 February)
• Re: [heycam/webidl] [[MapData]] is not a thing (#521) (Thursday, 15 February)
• Re: [heycam/webidl] [[MapData]] is not a thing (#521) (Thursday, 15 February)
• [heycam/webidl] [[MapData]] is not a thing (#521) (Thursday, 15 February)
• Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100) (Wednesday, 14 February)
• Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100) (Wednesday, 14 February)
• Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100) (Wednesday, 14 February)
• Re: [heycam/webidl] Prototype of @@unscopable object (#496) (Monday, 12 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Saturday, 10 February)
• Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Wednesday, 7 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Wednesday, 7 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Wednesday, 7 February)

Bradley Meck

• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 19 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 19 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 19 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Monday, 12 February)
• [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Monday, 12 February)

Brian Kardell

• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Thursday, 22 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Friday, 16 February)

Caleb Williams

• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Sunday, 18 February)

CaptGrumpyPants

• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Friday, 9 February)

Caridy Patiño

• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Wednesday, 28 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Wednesday, 28 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Friday, 23 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Friday, 23 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Friday, 23 February)
• Re: [w3c/webcomponents] Interface/class-based selector (#719) (Wednesday, 21 February)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Tuesday, 20 February)
• [w3c/WebPlatformWG] Add Diego Ferreiro to Web Components F2F 2018 attendees (#106) (Tuesday, 13 February)
• Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731) (Wednesday, 7 February)
• Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731) (Wednesday, 7 February)

chaals

• Re: [w3c/uievents-code] Need an implementation report (#20) (Wednesday, 28 February)
• Re: [w3c/WebPlatformWG] Update 18-03-Web-components.md (#116) (Monday, 26 February)
• Re: [w3c/WebPlatformWG] Add Salesforce attendees (#115) (Monday, 26 February)
• Re: [w3c/WebPlatformWG] Add references to Template instantiation & HTML modules (#110) (Monday, 26 February)
• Re: [w3c/WebPlatformWG] Update 18-03-Web-components.md (#114) (Monday, 26 February)
• Re: [w3c/WebPlatformWG] Update 18-03-Web-components.md (#114) (Monday, 26 February)
• Re: [w3c/WebPlatformWG] Add declarative Shadow DOM to the Agenda (#113) (Wednesday, 21 February)
• Re: [w3c/WebPlatformWG] Add tkent-google (#111) (Wednesday, 21 February)
• Re: [w3c/WebPlatformWG] Add Chris Joel to confirmed attendees (#112) (Wednesday, 21 February)
• Re: [w3c/WebPlatformWG] Update Attending (#109) (Monday, 19 February)
• Re: [w3c/WebPlatformWG] Add Scoped Custom Element Registries to agenda (#108) (Saturday, 17 February)
• Re: [w3c/WebPlatformWG] Add Github profile links to attendees (#107) (Thursday, 15 February)
• Re: [w3c/WebPlatformWG] Add Github profile links to attendees (#107) (Thursday, 15 February)
• Re: [w3c/WebPlatformWG] Add Diego Ferreiro to Web Components F2F 2018 attendees (#106) (Tuesday, 13 February)
• [w3c/webcomponents] typo (#732) (Wednesday, 7 February)
• Re: [w3c/WebPlatformWG] Add Justin Fagnani to Web Components F2F attendees (#104) (Wednesday, 7 February)
• Re: [w3c/pointerlock] WD for PL2.0 (#25) (Tuesday, 6 February)
• Re: [w3c/manifest] Add Matt Giuca as Co-Editor (#650) (Monday, 5 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (0528ad8) (Monday, 5 February)
• Re: [w3c/WebPlatformWG] Add Patrick Kettner to attendees (#103) (Saturday, 3 February)
• Re: [w3c/WebPlatformWG] Add Tomek Wytrębowicz to attendees (#102) (Thursday, 1 February)
• Re: [w3c/WebPlatformWG] Adds Karl Dubost as a lurker participant (#101) (Thursday, 1 February)
• Re: [w3c/WebPlatformWG] Adds Karl Dubost as a lurker participant (#101) (Thursday, 1 February)

ChocolateCravings

• Re: [w3c/permissions] Preventing blackmail (#171) (Friday, 16 February)
• [w3c/permissions] Preventing blackmail (#171) (Wednesday, 14 February)

Chris

• [whatwg/fetch] ReadableStreamDefaultReader.read() Errors Unavailable to Response Reader Rejection (#676) (Wednesday, 28 February)

Chris Dumez

• Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273) (Friday, 2 February)
• [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273) (Friday, 2 February)

Chris Harrelson

• Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Saturday, 10 February)

Christopher Joel

• Re: [w3c/webcomponents] [templates] Is a global registry of template processors the right idea? (#681) (Tuesday, 27 February)
• Re: [w3c/webcomponents] [templates] What is declareCallback? (#693) (Tuesday, 27 February)
• [w3c/WebPlatformWG] Add Chris Joel to confirmed attendees (#112) (Wednesday, 21 February)

Claudio Gomboli

• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Monday, 26 February)
• Re: [w3c/manifest] feat: add support for adaptive icons (#563) (Monday, 26 February)

cynthia

• Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226) (Monday, 26 February)
• Re: [w3ctag/design-reviews] Img decoding attribute (#220) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Img decoding attribute (#220) (Thursday, 1 February)

Damien Pobel

• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 28 February)

Dan Beam

• [whatwg/dom] DOM ready is error prone, still requires libs, could be simpler: a document#ready Promise (#568) (Wednesday, 7 February)

Daniel Appelquist

• Re: [w3ctag/design-reviews] TAG review of Web Audio API (round two) (#212) (Friday, 2 February)
• Re: [w3ctag/design-reviews] TAG review of Web Audio API (round two) (#212) (Friday, 2 February)
• Re: [w3ctag/design-reviews] TAG review of Web Audio API (round two) (#212) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134) (Friday, 2 February)
• Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Friday, 2 February)
• Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Transform Streams (#211) (Friday, 2 February)

Daniel Ehrenberg

• Re: [heycam/webidl] Add bigint type (#525) (Tuesday, 27 February)
• Re: [heycam/webidl] Add bigint type (#525) (Tuesday, 27 February)
• Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231) (Tuesday, 27 February)
• Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526) (Friday, 23 February)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Friday, 23 February)
• Re: [heycam/webidl] Add bigint type (#525) (Friday, 23 February)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Friday, 23 February)
• Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526) (Friday, 23 February)
• Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526) (Friday, 23 February)
• Re: [heycam/webidl] Add bigint type (#525) (Friday, 23 February)
• Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526) (Friday, 23 February)
• Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526) (Friday, 23 February)
• [heycam/webidl] Add [Exposed=*] to expose on all globals (#526) (Thursday, 22 February)
• [heycam/webidl] Add bigint type (#525) (Thursday, 22 February)
• Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231) (Tuesday, 20 February)
• Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231) (Monday, 19 February)
• [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231) (Monday, 19 February)
• Re: [w3c/IndexedDB] Track ES BigInt work (#230) (Monday, 19 February)
• Re: [w3c/IndexedDB] Track ES BigInt work (#230) (Sunday, 18 February)

Daniel Veditz

• Re: [w3c/permissions] Preventing blackmail (#171) (Tuesday, 20 February)

Dave Tapuska

• Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Tuesday, 27 February)

David Mann

• Re: [w3c/touch-events] Initialize touchList in Chrome (#78) (Thursday, 15 February)

David Singer

• Re: [w3ctag/design-reviews] Privacy Mode (#101) (Friday, 2 February)

David Storey

• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Wednesday, 14 February)

davidcblack

• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Tuesday, 13 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 9 February)

devonj1180

• Re: [whatwg/encoding] Add LICENSE resource (990e16b) (Saturday, 17 February)

Domenic Denicola

• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 28 February)
• Re: [heycam/webidl] ES bindings for constants on Globals (#528) (Tuesday, 27 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 27 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 27 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Monday, 26 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Saturday, 24 February)
• Re: [whatwg/streams] "await writer.write(bytes);" in example seems wrong (#874) (Thursday, 22 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 22 February)
• Re: [heycam/webidl] Add bigint type (#525) (Thursday, 22 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Thursday, 22 February)
• Re: [whatwg/streams] Interface for push based ReadableStream? (#889) (Thursday, 22 February)
• Re: [whatwg/streams] Interface for push based ReadableStream? (#889) (Thursday, 22 February)
• Re: [whatwg/streams] Interface for push based ReadableStream? (#889) (Wednesday, 21 February)
• Re: [whatwg/streams] Interface for push based ReadableStream? (#889) (Wednesday, 21 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Wednesday, 21 February)
• Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572) (Wednesday, 21 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Wednesday, 21 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Wednesday, 21 February)
• Re: [whatwg/streams] Editorial: fix some double-word typos (#887) (Wednesday, 21 February)
• Re: [whatwg/streams] Fix miscellaneous spelling mistakes (#888) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Interface/class-based selector (#719) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Interface/class-based selector (#719) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 20 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 20 February)
• Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Tuesday, 20 February)
• [whatwg/streams] Editorial: fix some double-word typos (#887) (Tuesday, 20 February)
• Re: [whatwg/streams] Bikeshed warnings (#869) (Tuesday, 20 February)
• Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Tuesday, 20 February)
• Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Tuesday, 20 February)
• Re: [whatwg/streams] Suppress Bikeshed warnings about <vars> used once (#883) (Tuesday, 20 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Tuesday, 20 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Tuesday, 20 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Tuesday, 20 February)
• Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572) (Tuesday, 20 February)
• Re: [whatwg/dom] Editorial: consider linking "present" consistently (#574) (Monday, 19 February)
• Re: [whatwg/dom] Editorial: consider linking "present" consistently (#574) (Monday, 19 February)
• Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572) (Monday, 19 February)
• Re: [whatwg/xhr] UnioNas (#190) (Friday, 16 February)
• [whatwg/streams] Use sentence case, not title case, for headings (#886) (Friday, 16 February)
• [whatwg/streams] Make the table of contents more useful/less dense (#885) (Friday, 16 February)
• Re: [whatwg/streams] Suppress Bikeshed warnings about <vars> used once (#883) (Friday, 16 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Friday, 16 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Friday, 16 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Friday, 16 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Friday, 16 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Friday, 16 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Friday, 16 February)
• Re: [whatwg/fetch] Proposal: Easier request/response rewrites (#671) (Friday, 16 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 15 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 15 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Thursday, 15 February)
• Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882) (Wednesday, 14 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Wednesday, 14 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Wednesday, 14 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Wednesday, 14 February)
• Re: [whatwg/fetch] Following signals. Fixes #668. (#670) (Wednesday, 14 February)
• Re: [whatwg/streams] Fix example for identity transform (#881) (Wednesday, 14 February)
• Re: [whatwg/streams] Fix example for identity transform (#881) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Wednesday, 14 February)
• Re: [whatwg/dom] Change handling of is="" in element creation and cloning (#566) (Wednesday, 14 February)
• Re: [whatwg/streams] Meta: Fix CONTRIBUTING.md link (#880) (Tuesday, 13 February)
• Re: [whatwg/streams] Meta: Fix CONTRIBUTING.md link (#880) (Tuesday, 13 February)
• Re: [whatwg/fetch] Following signals. Fixes #668. (#670) (Monday, 12 February)
• Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668) (Monday, 12 February)
• Re: [whatwg/dom] Following an abort signal (#569) (Monday, 12 February)
• Re: [whatwg/dom] Following an abort signal (#569) (Monday, 12 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Saturday, 10 February)
• Re: [whatwg/dom] Following an abort signal (#569) (Friday, 9 February)
• Re: [whatwg/fetch] Location header is the empty string (#669) (Friday, 9 February)
• Re: [whatwg/streams] Disambiguate links to "resolve" (#878) (Friday, 9 February)
• Re: [heycam/webidl] Testing (#520) (Friday, 9 February)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Friday, 9 February)
• Re: [whatwg/dom] Following an abort signal (#569) (Friday, 9 February)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Friday, 9 February)
• Re: [whatwg/fetch] Location header is the empty string (#669) (Friday, 9 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 8 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 8 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 8 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 8 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 8 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Thursday, 8 February)
• Re: [whatwg/streams] "await writer.write(bytes);" in example seems wrong (#874) (Thursday, 8 February)
• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Thursday, 8 February)
• Re: [whatwg/url] Make property accessors into owned properties, or at least enumerable (#301) (Wednesday, 7 February)
• Re: [whatwg/url] Make property accessors into owned properties, or at least enumerable (#301) (Wednesday, 7 February)
• Re: [whatwg/url] Need more changes for common deploy (#353) (Wednesday, 7 February)
• Re: [whatwg/url] Need more changes for common deploy (#353) (Wednesday, 7 February)
• Re: [whatwg/url] "For each code point in input, UTF-8 percent enc..." (#368) (Wednesday, 7 February)
• Re: [whatwg/url] "For each code point in input, UTF-8 percent enc..." (#368) (Wednesday, 7 February)
• Re: [whatwg/url] mailto hostnames (#331) (Wednesday, 7 February)
• Re: [whatwg/url] mailto hostnames (#331) (Wednesday, 7 February)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 7 February)
• Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668) (Wednesday, 7 February)
• Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668) (Wednesday, 7 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Wednesday, 7 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Wednesday, 7 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Wednesday, 7 February)
• Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) (Wednesday, 7 February)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 7 February)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 7 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Wednesday, 7 February)
• Re: [whatwg/dom] DOM ready is error prone, still requires libs, could be simpler: a document#ready Promise (#568) (Wednesday, 7 February)
• Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730) (Tuesday, 6 February)
• Re: [whatwg/streams] Add "was ever locked" flag for Encoding standard? (#873) (Monday, 5 February)
• Re: [whatwg/encoding] Add Streams support (#72) (Monday, 5 February)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Monday, 5 February)
• Re: [whatwg/xhr] Fix send() charset overriding to use new MIME type infrastructure (#188) (Sunday, 4 February)
• [whatwg/xhr] Fix send() charset overriding to use new MIME type infrastructure (#188) (Sunday, 4 February)
• Re: [whatwg/xhr] Look at overrideMimeType() again (#157) (Sunday, 4 February)
• Re: [whatwg/fetch] data: URL generator (#665) (Sunday, 4 February)
• [whatwg/dom] Change handling of is="" in element creation and cloning (#566) (Friday, 2 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 2 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Web Locks API (#217) (Thursday, 1 February)

Dominic Farolino

• [whatwg/streams] Meta: Fix CONTRIBUTING.md link (#880) (Monday, 12 February)

Dominick Ng

• Re: [w3c/manifest] Allow for multiple scopes (#449) (Thursday, 1 February)

Dominique Hazael-Massieux

• [heycam/webidl] Four (not five) kind of special operations (#519) (Thursday, 8 February)

Dylan Barrell

• Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858) (Sunday, 4 February)
• Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858) (Saturday, 3 February)

DZ

• [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730) (Tuesday, 6 February)

elf Pavlik

• Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858) (Saturday, 3 February)
• Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858) (Saturday, 3 February)

Emilio Cobos Álvarez

• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Monday, 19 February)
• Re: [w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728) (Sunday, 4 February)

Eric Willigers

• Re: [w3c/ServiceWorker] Update orphaned references in Query Cache algo (#1281) (Thursday, 22 February)
• [w3c/ServiceWorker] Update orphaned references in Query Cache algo (#1281) (Thursday, 22 February)

fantasai

• Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Saturday, 3 February)

fergald

• [w3c/WebPlatformWG] Update 18-03-Web-components.md (#114) (Monday, 26 February)
• [w3ctag/design-reviews] CSS ::part and ::theme pseudo elements (#230) (Tuesday, 6 February)

François Beaufort

• Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226) (Monday, 26 February)
• Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226) (Monday, 26 February)
• Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226) (Monday, 5 February)
• Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226) (Friday, 2 February)

Fredrik Söderqvist

• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Wednesday, 21 February)

freshp86

• Re: [whatwg/dom] Removing event listeners through an identifier (#208) (Wednesday, 7 February)
• Re: [whatwg/dom] DOM ready is error prone, still requires libs, could be simpler: a document#ready Promise (#568) (Wednesday, 7 February)

frlinw

• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Wednesday, 28 February)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Friday, 23 February)

Fuqiao Xue

• Re: [w3c/uievents-key] Implementation report (#45) (Wednesday, 28 February)
• Re: [w3c/uievents-key] Implementation report (#45) (Wednesday, 28 February)
• Re: [w3c/uievents-code] Need an implementation report (#20) (Wednesday, 28 February)
• Re: [w3c/uievents-code] Need an implementation report (#20) (Wednesday, 28 February)
• [w3ctag/design-reviews] W3C DOM (#229) (Saturday, 3 February)

Gary Kacmarcik

• Re: [w3c/uievents-code] Need an implementation report (#20) (Wednesday, 28 February)
• Re: [w3c/uievents-code] Need an implementation report (#20) (Wednesday, 28 February)
• Re: [w3c/uievents-code] Need an implementation report (#20) (Wednesday, 28 February)
• Re: [w3c/uievents] May the state of modifier keys influence MouseEvent.button? (#184) (Tuesday, 20 February)
• Re: [w3c/clipboard-apis] Spec does not auto-deploy when changes are made (#68) (Sunday, 18 February)
• Re: [w3c/clipboard-apis] Spec does not auto-deploy when changes are made (#68) (Sunday, 18 February)
• Re: [w3c/clipboard-apis] Should clipboard actions consider whether selection has focus? (#57) (Friday, 16 February)
• [w3c/clipboard-apis] Spec does not auto-deploy when changes are made (#68) (Friday, 16 February)
• Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62) (Friday, 16 February)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Friday, 16 February)
• Re: [w3c/clipboard-apis] Emphasize visability in the "pick target"-algorithm (#58) (Friday, 16 February)
• Re: [w3c/clipboard-apis] Emphasize visability in the "pick target"-algorithm (#58) (Friday, 16 February)
• Re: [w3c/clipboard-apis] Should we have an API to return the set of readable/writable data types? (#67) (Thursday, 15 February)
• [w3c/clipboard-apis] Should we have an API to return the set of readable/writable data types? (#67) (Thursday, 15 February)
• Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62) (Thursday, 15 February)
• Re: [w3c/clipboard-apis] Emphasize visability in the "pick target"-algorithm (#58) (Thursday, 15 February)
• Re: [w3c/clipboard-apis] When called without gesture, return an error describing rejection (#66) (Wednesday, 14 February)
• Re: [w3c/uievents] single character typo fix (#182) (Tuesday, 13 February)
• Re: [w3c/uievents-key] Implementation report (#44) (Tuesday, 6 February)

GilSoa

• [whatwg/xhr] UnioNas (#190) (Friday, 16 February)

Goffert van Gool

• Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715) (Tuesday, 20 February)

guest271314

• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Wednesday, 21 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Tuesday, 20 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Monday, 19 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Monday, 19 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 19 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 19 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 19 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 19 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 19 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 19 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 19 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 19 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Sunday, 18 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Sunday, 18 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Sunday, 18 February)
• Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877) (Tuesday, 13 February)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 5 February)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 5 February)
• Re: [whatwg/fetch] Should fetches to blob URLs be more restricted? (#666) (Friday, 2 February)

Harald Alvestrand

• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Thursday, 8 February)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 7 February)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 7 February)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 7 February)

Harris Hancock

• Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674) (Wednesday, 28 February)
• [whatwg/fetch] Allow used body replacement in Request constructor (#675) (Wednesday, 28 February)
• Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674) (Tuesday, 27 February)
• [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674) (Monday, 26 February)

Hayato Ito

• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Thursday, 22 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Thursday, 22 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Thursday, 22 February)
• Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736) (Monday, 19 February)
• Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736) (Friday, 16 February)
• Re: [w3c/webcomponents] elementsFromPoint behavior is unclear (#735) (Friday, 16 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Tuesday, 13 February)
• Re: [w3c/webcomponents] Consider adding user-defined attributes to slots (#733) (Friday, 9 February)
• Re: [w3c/webcomponents] typo (#732) (Thursday, 8 February)
• Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731) (Wednesday, 7 February)
• Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731) (Wednesday, 7 February)

Heaven

• Re: [w3ctag/design-reviews] Request to review First Paint Timing (#177) (Monday, 19 February)

Hugo

• Re: [w3c/clipboard-apis] The "context is editable"-condition in the fire event-algorithm needs clarification (#69) (Wednesday, 21 February)
• [w3c/clipboard-apis] The "context is editable"-condition in the fire event-algorithm needs clarification (#69) (Tuesday, 20 February)
• Re: [w3c/selection-api] No definition of hidden selections (#94) (Tuesday, 20 February)
• Re: [w3c/selection-api] Background section is a mess (#84) (Tuesday, 20 February)
• Re: [w3c/clipboard-apis] Fix algorithm for firing a clipboard event (11619a7) (Sunday, 18 February)
• Re: [w3c/clipboard-apis] Should clipboard actions consider whether selection has focus? (#57) (Friday, 16 February)
• Re: [w3c/clipboard-apis] Emphasize visability in the "pick target"-algorithm (#58) (Friday, 16 February)

Ian Clelland

• Re: [w3ctag/design-reviews] Request Review: Gesture Delegation (#199) (Thursday, 1 February)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Thursday, 1 February)

Ilya Grigorik

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

Isaac Ferreira

• Re: [w3c/webcomponents] [Template Instantiation] Review the cloning step (#740) (Monday, 26 February)
• [w3c/webcomponents] [Template Instantiation] Review the cloning step (#740) (Sunday, 25 February)

Isiah Meadows

• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Monday, 19 February)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 19 February)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 19 February)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Sunday, 18 February)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Sunday, 18 February)

J. S. Choi

• Re: [whatwg/fetch] :read-only and :read-write selectors: Consistency and cross-UA behavior (#672) (Friday, 23 February)
• [whatwg/fetch] :read-only and :read-write selectors: Consistency and cross-UA behavior (#672) (Friday, 23 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Friday, 16 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Sunday, 11 February)

Jake Archibald

• Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Wednesday, 28 February)
• Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Monday, 26 February)
• Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Monday, 26 February)
• Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Friday, 23 February)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Friday, 23 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 16 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Wednesday, 14 February)
• Re: [whatwg/fetch] Following signals. Fixes #668. (#670) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Monday, 12 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Monday, 12 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Monday, 12 February)
• Re: [whatwg/dom] Following an abort signal (#569) (Monday, 12 February)
• Re: [whatwg/fetch] Following signals. Fixes #668. (#670) (Monday, 12 February)
• Re: [whatwg/dom] Following an abort signal (#569) (Monday, 12 February)
• Re: [whatwg/dom] Following an abort signal (#569) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 9 February)
• Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668) (Friday, 9 February)
• [whatwg/fetch] Following signals. Fixes #668. (#670) (Friday, 9 February)
• Re: [whatwg/dom] Following an abort signal (#569) (Friday, 9 February)
• [whatwg/dom] Following an abort signal (#569) (Friday, 9 February)
• Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668) (Thursday, 8 February)
• Re: [w3c/ServiceWorker] Replaying POST requests (#693) (Monday, 5 February)
• Re: [w3c/ServiceWorker] The Cache objects do not expire unless authors *or users* delete the entries. (#1276) (Monday, 5 February)

James Bromwell

• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Thursday, 8 February)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 8 February)

James Browning

• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Thursday, 22 February)
• Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737) (Sunday, 18 February)
• Re: [w3c/webcomponents] Why do we really need hyphens? (#658) (Tuesday, 13 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 13 February)

Jared Adam Smith

• Re: [w3c/webcomponents] Interface/class-based selector (#719) (Wednesday, 21 February)

Jarek Foksa

• Re: [w3c/webcomponents] Proposal: Allow custom elements to be in any namespace (#634) (Saturday, 10 February)

Jeff Burtoft

• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Friday, 23 February)
• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Friday, 23 February)

Jeff17Robbins

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

Jeffrey Yasskin

• Re: [w3c/permissions] Preventing blackmail (#171) (Wednesday, 14 February)
• Re: [w3c/permissions] Preventing blackmail (#171) (Wednesday, 14 February)

Jimmy Wärting

• Re: [w3c/webstorage] Make session/localstorage iteratable (#8) (Friday, 16 February)
• [w3c/webstorage] Make session/localstorage iteratable (#8) (Wednesday, 14 February)

Joe Pea

• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 28 February)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 28 February)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 28 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Saturday, 24 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Saturday, 24 February)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Thursday, 22 February)
• Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737) (Thursday, 22 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Thursday, 22 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Thursday, 22 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 20 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Monday, 19 February)
• [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Monday, 19 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Monday, 19 February)
• Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559) (Sunday, 18 February)
• [w3c/webcomponents] Some sort of guarantee on upgrade order? (#737) (Sunday, 18 February)
• Re: [w3c/webcomponents] Why do we really need hyphens? (#658) (Tuesday, 13 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 13 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 13 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Saturday, 10 February)
• Re: [w3c/webcomponents] Proposal: Allow custom elements to be in any namespace (#634) (Saturday, 10 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Saturday, 10 February)
• Re: [w3c/webcomponents] Interfaces for web components (#725) (Saturday, 10 February)
• Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731) (Saturday, 10 February)
• Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730) (Saturday, 10 February)
• Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730) (Saturday, 10 February)
• Re: [w3c/webcomponents] [idea] Element Behaviors, and the has="" attribute (#727) (Saturday, 10 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 February)
• Re: [w3c/webcomponents] A new attribute similar to is="", but would allow multiple behaviors to be attached to a given element. (#662) (Saturday, 10 February)
• Re: [w3c/webcomponents] A new attribute similar to is="", but would allow multiple behaviors to be attached to a given element. (#662) (Saturday, 10 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 February)
• Re: [w3c/webcomponents] A new attribute similar to is="", but would allow multiple behaviors to be attached to a given element. (#662) (Thursday, 1 February)
• [w3c/webcomponents] [idea] Element Behaviors (#727) (Thursday, 1 February)
• Re: [w3c/webcomponents] A new attribute similar to is="", but would allow multiple behaviors to be attached to a given element. (#662) (Thursday, 1 February)

Joey Parrish

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

Johann Hofmann

• Re: [w3c/permissions] Add optional consent due to GDPR (#169) (Friday, 2 February)

John Firebaugh

• [w3c/uievents] May the state of modifier keys influence MouseEvent.button? (#184) (Tuesday, 20 February)

Jon Ege Ronnenberg

• Re: [whatwg/fetch] CORS protocol and HTTP caches (#402) (Wednesday, 21 February)

Jonathon Kereliuk

• Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62) (Friday, 23 February)

Josh Bruce

• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Sunday, 11 February)

Josh Matthews

• Re: [whatwg/fetch] Bob (#673) (Friday, 23 February)

Joshua Bell

• Re: [w3c/IndexedDB] Add support for URL as one of the basic types like Date (#108) (Monday, 26 February)
• Re: [w3c/IndexedDB] Add support for URL as one of the basic types like Date (#108) (Monday, 26 February)
• [w3c/ServiceWorker] Query Cache algorithm contains orphaned 'f' references (#1280) (Wednesday, 21 February)
• Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231) (Tuesday, 20 February)
• Re: [w3c/IndexedDB] Track ES BigInt work (#230) (Monday, 19 February)
• Re: [w3c/IndexedDB] Track ES BigInt work (#230) (Thursday, 15 February)
• [w3c/IndexedDB] Track ES BigInt work (#230) (Thursday, 15 February)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 7 February)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 7 February)
• Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Web Locks API (#217) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Thursday, 1 February)
• Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Thursday, 1 February)

Jungkee Song

• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Wednesday, 28 February)
• Re: [w3c/ServiceWorker] Update orphaned references in Query Cache algo (#1281) (Friday, 23 February)
• Re: [w3c/ServiceWorker] Update orphaned references in Query Cache algo (#1281) (Friday, 23 February)
• Re: [w3c/ServiceWorker] Query Cache algorithm contains orphaned 'f' references (#1280) (Friday, 23 February)
• Re: [w3c/ServiceWorker] Query Cache algorithm contains orphaned 'f' references (#1280) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] Update orphaned references in Query Cache algo (#1281) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] Query Cache algorithm contains orphaned 'f' references (#1280) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Tuesday, 20 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Monday, 19 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Monday, 19 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Monday, 19 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (Monday, 12 February)
• Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (Monday, 12 February)
• Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (Monday, 12 February)
• Re: [w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274) (Monday, 12 February)
• Re: [w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274) (Monday, 12 February)
• [w3c/ServiceWorker] Improve.ready and Activate (#1277) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Tuesday, 6 February)
• Re: [w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274) (Tuesday, 6 February)
• [w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274) (Friday, 2 February)
• Re: [w3c/ServiceWorker] should `ServiceWorker` interface implement `AbstractWorker` mixin? (#1268) (Thursday, 1 February)
• Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267) (Thursday, 1 February)

Justin Fagnani

• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Friday, 23 February)
• Re: [w3c/webcomponents] [templates] What is declareCallback? (#693) (Friday, 23 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Friday, 23 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Friday, 23 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Friday, 23 February)
• [w3c/WebPlatformWG] Add Scoped Custom Element Registries to agenda (#108) (Friday, 16 February)
• [w3c/WebPlatformWG] Add Justin Fagnani to Web Components F2F attendees (#104) (Wednesday, 7 February)

Karl Dubost

• [w3c/WebPlatformWG] Adds Karl Dubost as a lurker participant (#101) (Thursday, 1 February)

Kelvin Yong

• Re: [w3c/gamepad] Light Indicator (#67) (Monday, 5 February)
• Re: [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27) (Monday, 5 February)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Tuesday, 27 February)
• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Tuesday, 27 February)
• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Tuesday, 27 February)
• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Monday, 26 February)
• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Friday, 23 February)
• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Friday, 23 February)
• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Friday, 23 February)
• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Friday, 23 February)
• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Friday, 23 February)
• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Friday, 23 February)
• Re: [w3c/manifest] feat: add support for adaptive icons (#563) (Friday, 23 February)
• [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Friday, 23 February)
• Re: [w3c/manifest] Allow app to load in parallel to splash screen (#559) (Thursday, 22 February)
• Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646) (Thursday, 22 February)
• Re: [w3c/manifest] Don't use enums, because they throw (#633) (Thursday, 22 February)
• Re: [w3c/manifest] Add info push notifications to extensions registry (#529) (Thursday, 22 February)
• Re: [w3c/manifest] Add shortcuts (#575) (Thursday, 22 February)
• Re: [w3c/manifest] Allow app to load in parallel to splash screen (#559) (Thursday, 22 February)
• Re: [w3c/manifest] Status section has misleading info on filing bugs (#489) (Thursday, 22 February)
• Re: [w3c/manifest] Add shortcuts (#575) (Thursday, 22 February)
• Re: [w3c/manifest] FR: Context menus on app icons. (#582) (Thursday, 22 February)
• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Thursday, 22 February)
• Re: [w3c/manifest] Use data-cite for all references (#573) (Thursday, 22 February)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Thursday, 22 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Thursday, 22 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Use infra spec and data-cite (#655) (Tuesday, 20 February)
• Re: [w3c/manifest] Use infra spec and data-cite (#655) (Tuesday, 20 February)
• Re: [w3c/manifest] Fix references to lower case in spec (#602) (Tuesday, 20 February)
• Re: [w3c/manifest] Use Infra spec for iterations (#621) (Tuesday, 20 February)
• [w3c/manifest] Use infra spec and data-cite (#655) (Tuesday, 20 February)
• Re: [w3c/manifest] Update the Service Worker object to not conflict with SW WebIDL (#654) (Tuesday, 20 February)
• Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641) (Tuesday, 20 February)
• Re: [w3c/manifest] Update the Service Worker object to not conflict with SW WebIDL (#654) (Tuesday, 20 February)
• [w3c/manifest] Update the Service Worker object to not conflict with SW WebIDL (#654) (Monday, 19 February)
• Re: [w3c/manifest] Make start_url relative to scope and not manifest location (#552) (Friday, 9 February)
• Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641) (Thursday, 8 February)
• Re: [w3c/manifest] Payment Handler spec defines IDL types very similar to manifest (#652) (Thursday, 8 February)
• Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641) (Wednesday, 7 February)
• Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641) (Wednesday, 7 February)
• [w3c/manifest] Payment Handler spec defines IDL types very similar to manifest (#652) (Wednesday, 7 February)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Friday, 2 February)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Friday, 2 February)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Friday, 2 February)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Friday, 2 February)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Thursday, 1 February)

Kenton Varda

• Re: [whatwg/fetch] Proposal: Easier request/response rewrites (#671) (Friday, 16 February)
• Re: [whatwg/fetch] Proposal: Easier request/response rewrites (#671) (Friday, 16 February)
• [whatwg/fetch] Proposal: Easier request/response rewrites (#671) (Thursday, 15 February)

Kiko Beats

• Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858) (Wednesday, 14 February)

Kit Cambridge

• Re: [w3c/push-api] pushManager.subscribe should replace applicationServerKey if different (#291) (Saturday, 17 February)

KOLANICH

• Re: [w3c/permissions] Preventing blackmail (#171) (Tuesday, 20 February)
• Re: [w3c/permissions] Preventing blackmail (#171) (Friday, 16 February)
• Re: [w3c/permissions] Preventing blackmail (#171) (Wednesday, 14 February)
• Re: [w3c/permissions] Preventing blackmail (#171) (Wednesday, 14 February)

Kouhei Ueno

• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Wednesday, 21 February)

Krzysztof Kotowicz

• Re: [w3ctag/design-reviews] Trusted Types (#198) (Thursday, 1 February)
• Re: [w3ctag/design-reviews] Trusted Types (#198) (Thursday, 1 February)

Kumar Nitesh

• Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226) (Monday, 5 February)

Kurt Mackey

• Re: [whatwg/streams] Interface for push based ReadableStream? (#889) (Wednesday, 21 February)
• Re: [whatwg/streams] Interface for push based ReadableStream? (#889) (Wednesday, 21 February)
• [whatwg/streams] Interface for push based ReadableStream? (#889) (Wednesday, 21 February)

L. David Baron

• Re: [w3ctag/design-reviews] Payment Handler (#231) (Friday, 16 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Wednesday, 14 February)
• Re: [w3ctag/design-reviews] Payment Handler (#231) (Monday, 12 February)
• Re: [w3ctag/design-reviews] CSS ::part and ::theme pseudo elements (#230) (Wednesday, 7 February)
• Re: [w3ctag/design-reviews] CSS ::part and ::theme pseudo elements (#230) (Wednesday, 7 February)
• Re: [w3ctag/design-reviews] Img decoding attribute (#220) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Web Locks API (#217) (Friday, 2 February)
• Re: [w3ctag/design-reviews] TAG review of Web Audio API (round two) (#212) (Friday, 2 February)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Friday, 2 February)
• Re: [w3ctag/design-reviews] CSS Layout API (#224) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Intersection Observer review (#197) (Thursday, 1 February)
• Re: [w3c/permissions] Add optional consent due to GDPR (#169) (Thursday, 1 February)

Lennart Grahl

• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Wednesday, 14 February)
• Re: [whatwg/streams] Provide a way for the underlying sink to signal write progress? (#876) (Tuesday, 13 February)
• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Wednesday, 7 February)

Lukasz Olejnik

• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Wednesday, 7 February)
• [w3c/permissions] Add optional consent due to GDPR (#169) (Thursday, 1 February)

Léonie Watson

• Re: [w3c/uievents-code] Need an implementation report (#20) (Monday, 26 February)
• Re: [w3c/uievents-code] Need an implementation report (#20) (Monday, 26 February)
• Re: [w3c/uievents-code] Move Keyboard Events Code Values to PR (#22) (Monday, 26 February)
• Re: [w3c/uievents-key] Implementation report (#45) (Monday, 26 February)
• Re: [w3c/uievents-key] Implementation report (#45) (Monday, 26 February)
• Re: [w3c/uievents-key] Implementation report (#45) (Monday, 26 February)
• Re: [w3c/uievents-key] Move Keyboard Events Key Values to PR (#47) (Monday, 26 February)
• [w3c/uievents-code] Move Keyboard Events Code Values to PR (#22) (Monday, 26 February)
• Re: [w3c/uievents-code] Time to exit CR? (#21) (Monday, 26 February)
• [w3c/uievents-key] Move Keyboard Events Key Values to PR (#47) (Monday, 26 February)
• Re: [w3c/uievents-key] Implementation report (#45) (Monday, 26 February)
• Re: [w3c/uievents-key] Time to CR? (#46) (Monday, 26 February)
• Re: [w3c/gamepad] Timeline to Recommendation? (#61) (Friday, 16 February)
• Re: [w3c/gamepad] Timeline to Recommendation? (#61) (Friday, 16 February)
• Re: [w3c/WebPlatformWG] Add Web Share and Web Share Target APIs to charter (#105) (Saturday, 10 February)
• Re: [w3c/uievents-key] Implementation report (#44) (Tuesday, 6 February)
• Re: [w3c/uievents-key] Implementation report (#44) (Tuesday, 6 February)
• [w3c/webcomponents] Input requested on ARIA/HTML role parity (#729) (Tuesday, 6 February)
• Re: [w3c/pointerlock] WD for PL2.0 (#25) (Tuesday, 6 February)
• Re: [w3c/uievents-key] Implementation report (#44) (Tuesday, 6 February)
• Re: [w3c/pointerlock] WD for PL2.0 (#25) (Tuesday, 6 February)

Marco Colli

• [w3c/push-api] pushManager.subscribe should replace applicationServerKey if different (#291) (Saturday, 17 February)

Marcos Cáceres

• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Wednesday, 28 February)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 27 February)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 26 February)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 26 February)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Friday, 23 February)
• Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646) (Thursday, 22 February)
• Re: [w3c/manifest] Use data-cite for all references (#573) (Thursday, 22 February)
• Re: [w3c/manifest] Don't use enums, because they throw (#633) (Thursday, 22 February)
• Re: [w3c/manifest] Use data-cite for all references (#573) (Thursday, 22 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/manifest] Improve references and minor fixups (#656) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 20 February)
• Re: [w3c/manifest] Use infra spec and data-cite (#655) (Tuesday, 20 February)
• Re: [w3c/manifest] Update the Service Worker object to not conflict with SW WebIDL (#654) (Tuesday, 20 February)
• Re: [w3c/manifest] Use infra spec and data-cite (#655) (Tuesday, 20 February)
• Re: [w3c/manifest] Update the Service Worker object to not conflict with SW WebIDL (#654) (Tuesday, 20 February)
• Re: [w3c/manifest] PromptResponseObject definition is missing in "IDL Index" (#637) (Tuesday, 13 February)
• Re: [w3c/manifest] PromptResponseObject definition is missing in "IDL Index" (#637) (Tuesday, 13 February)
• Re: [heycam/webidl] Testing (#520) (Monday, 12 February)
• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Monday, 12 February)
• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Monday, 12 February)
• Re: [w3c/manifest] Move extension point to end of processing steps (#653) (Friday, 9 February)
• Re: [w3c/manifest] Payment Handler spec defines IDL types very similar to manifest (#652) (Thursday, 8 February)
• Re: [w3c/manifest] Payment Handler spec defines IDL types very similar to manifest (#652) (Thursday, 8 February)
• Re: [w3c/manifest] PromptResponseObject definition is missing in "IDL Index" (#637) (Tuesday, 6 February)
• Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641) (Tuesday, 6 February)
• Re: [w3c/manifest] Add Matt Giuca as Co-Editor (#650) (Tuesday, 6 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (0528ad8) (Tuesday, 6 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651) (Tuesday, 6 February)
• Re: [w3c/manifest] Add Matt Giuca as Co-Editor (#650) (Tuesday, 6 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651) (Tuesday, 6 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (0528ad8) (Monday, 5 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651) (Monday, 5 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651) (Monday, 5 February)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Monday, 5 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651) (Monday, 5 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651) (Monday, 5 February)
• [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651) (Monday, 5 February)
• [w3c/manifest] Add Matt Giuca as Co-Editor (#650) (Monday, 5 February)
• Re: [w3c/manifest] Fix or replace instances of "new URL" (#649) (Monday, 5 February)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Thursday, 1 February)

Marijn Kruisselbrink

• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Tuesday, 20 February)
• Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68) (Tuesday, 20 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 12 February)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 5 February)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Friday, 2 February)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Friday, 2 February)
• [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Friday, 2 February)

Mark Nottingham

• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Wednesday, 21 February)
• Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609) (Tuesday, 20 February)
• [w3ctag/design-reviews] BCP56bis (#232) (Tuesday, 20 February)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Friday, 2 February)

Martin Janecke

• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Sunday, 11 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 7 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 7 February)

Masayuki Nakano

• [w3c/uievents] Declare keypress event should be fired when pressing Enter, Shift + Enter and Ctrl + Enter (#183) (Sunday, 18 February)
• Re: [w3c/uievents] Needs alternative WheelEvent.deltaMode, WheelEvent.delat(X|Y|Z) (#181) (Sunday, 11 February)
• [w3c/uievents] Needs alternative WheelEvent.deltaMode, WheelEvent.delat(X|Y|Z) (#181) (Sunday, 11 February)
• Re: [w3c/uievents] preventDefault() of keydown event should not kill composition start caused by the keydown (#180) (Tuesday, 6 February)
• [w3c/uievents] preventDefault() of keydown event should not kill composition start caused by the keydown (#180) (Tuesday, 6 February)
• Re: [w3c/uievents] Add specification for AltGraph key & modifier behaviour (#147) (Saturday, 3 February)
• [w3c/uievents] keydown event should have an attribute which is set to true when it's followed by a beforeinput or keypress event? (#179) (Saturday, 3 February)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Tuesday, 20 February)
• Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Monday, 19 February)
• Re: [whatwg/fetch] Location header is the empty string (#669) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Thursday, 15 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Thursday, 15 February)
• Re: [whatwg/url] "Let pointer be a pointer to first code point in..." (#373) (Tuesday, 13 February)
• Re: [whatwg/fetch] Location header is the empty string (#669) (Monday, 12 February)
• [whatwg/url] "Let pointer be a pointer to first code point in..." (#373) (Monday, 12 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Monday, 12 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Saturday, 10 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird after you call unregister() (#1279) (Saturday, 10 February)
• Re: [whatwg/fetch] Location header is the empty string (#669) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (Friday, 9 February)
• Re: [whatwg/fetch] Location header is the empty string (#669) (Friday, 9 February)
• [whatwg/fetch] Location header is the empty string (#669) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221) (Thursday, 8 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Thursday, 8 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Thursday, 8 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Thursday, 8 February)
• Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273) (Tuesday, 6 February)
• Re: [w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274) (Friday, 2 February)
• Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273) (Friday, 2 February)
• Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273) (Friday, 2 February)
• Re: [w3c/ServiceWorker] What's the possible reason for navigator.serviceWorker.register error？ (#1275) (Friday, 2 February)
• Re: [w3c/ServiceWorker] should local URLs check origin before inheritting a controller? (#1262) (Thursday, 1 February)
• Re: [w3c/ServiceWorker] should blob URL clients have their controlled updated if their parent's controller is changed? (#1265) (Thursday, 1 February)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Thursday, 1 February)

Matt Giuca

• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Wednesday, 28 February)
• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Wednesday, 28 February)
• Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657) (Tuesday, 27 February)
• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Tuesday, 27 February)
• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Tuesday, 27 February)
• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Friday, 23 February)
• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Friday, 23 February)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Friday, 23 February)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Friday, 23 February)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Wednesday, 14 February)
• Re: [w3c/manifest] Make start_url relative to scope and not manifest location (#552) (Monday, 12 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Monday, 12 February)
• Re: [w3c/WebPlatformWG] Add Web Share and Web Share Target APIs to charter (#105) (Monday, 12 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 9 February)
• [w3c/WebPlatformWG] Add Web Share and Web Share Target APIs to charter (#105) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 9 February)
• Re: [w3c/manifest] Make start_url relative to scope and not manifest location (#552) (Friday, 9 February)
• Re: [w3c/manifest] Move extension point to end of processing steps (#653) (Friday, 9 February)
• Re: [w3c/manifest] Extension point should come after processing other members (#629) (Friday, 9 February)
• Re: [w3c/manifest] Move extension point to end of processing steps (#653) (Friday, 9 February)
• [w3c/manifest] Move extension point to end of processing steps (#653) (Friday, 9 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Thursday, 8 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Thursday, 8 February)
• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Thursday, 8 February)
• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Thursday, 8 February)
• Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Thursday, 8 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651) (Tuesday, 6 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (0528ad8) (Tuesday, 6 February)
• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (0528ad8) (Tuesday, 6 February)
• Re: [w3c/manifest] Fix or replace instances of "new URL" (#649) (Monday, 5 February)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Monday, 5 February)
• [w3c/manifest] Fix or replace instances of "new URL" (#649) (Monday, 5 February)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Friday, 2 February)
• [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272) (Friday, 2 February)
• Re: [w3c/manifest] Should the scope terminate by "/"? (#554) (Thursday, 1 February)
• Re: [w3c/manifest] Should the scope terminate by "/"? (#554) (Thursday, 1 February)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Thursday, 1 February)

Matthew Dean

• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Tuesday, 13 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Friday, 9 February)

Matthew Phillips

• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Wednesday, 28 February)
• Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736) (Friday, 16 February)
• Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731) (Wednesday, 7 February)
• Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731) (Wednesday, 7 February)

Matthew Ryan

• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Monday, 19 February)

Mattias Buelens

• Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Tuesday, 27 February)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Friday, 23 February)
• Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Tuesday, 20 February)
• Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Friday, 16 February)
• Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Thursday, 15 February)
• [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Thursday, 15 February)
• Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882) (Thursday, 15 February)
• Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882) (Thursday, 15 February)
• Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877) (Thursday, 15 February)
• Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882) (Wednesday, 14 February)
• [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882) (Wednesday, 14 February)
• [whatwg/streams] Fix example for identity transform (#881) (Tuesday, 13 February)
• Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877) (Thursday, 8 February)
• Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877) (Wednesday, 7 February)
• Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877) (Tuesday, 6 February)
• [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877) (Tuesday, 6 February)

Mauro Junior

• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Sunday, 11 February)

Michael[tm] Smith

• Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884) (Wednesday, 21 February)

Mike Taylor

• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Thursday, 15 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Wednesday, 14 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Wednesday, 14 February)
• [whatwg/dom] Define a target concept that Event.target and Event.srcElement reflect (#570) (Wednesday, 14 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Wednesday, 14 February)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Wednesday, 14 February)

Mike West

• Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186) (Thursday, 1 February)
• Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186) (Thursday, 1 February)

Mikhail-MM

• [whatwg/fetch] Using multipart/form-data with multer occasionally causes React app to crash and refresh (#677) (Wednesday, 28 February)

Monica Dinculescu

• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 20 February)

Mounir Lamouri

• Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651) (Monday, 5 February)
• Re: [w3c/permissions] Media autoplay permission (#150) (Thursday, 1 February)

Nadya678

• Re: [whatwg/dom] chrome, doesn't accept preventDefault and still cancelable is true (#579) (Tuesday, 27 February)
• [whatwg/dom] chrome, doesn't accept preventDefault and stil cancelable is true (#579) (Sunday, 25 February)
• [whatwg/dom] Need a method to fire :hover and :active states (#578) (Saturday, 24 February)
• [whatwg/xhr] Please add followRedirects=true/false to XMLHttpRequest specification (#189) (Sunday, 11 February)

nainar

• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Monday, 5 February)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Friday, 2 February)

Nano Miratus

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

Natan Sągol

• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Tuesday, 27 February)
• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Sunday, 11 February)

Navid Zolghadr

• Re: [w3c/pointerlock] fix references, see #26 (#31) (Wednesday, 7 February)
• Re: [w3c/pointerlock] fix references, see #26 (#31) (Wednesday, 7 February)

Neil Stansbury

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

nhatchett

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Friday, 23 February)
• Re: [whatwg/xhr] XMLHttpRequest (#193) (Tuesday, 20 February)
• [whatwg/xhr] XMLHttpRequest (#193) (Tuesday, 20 February)

Nikolay Alipiev

• [w3c/editing] input setSelection() method workflow, when text overflows input container (#173) (Thursday, 22 February)

Noitidart

• Re: [whatwg/fetch] More informative error types (#526) (Friday, 23 February)

nondebug

• Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68) (Tuesday, 27 February)
• Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68) (Tuesday, 27 February)
• Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68) (Tuesday, 27 February)
• Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68) (Friday, 23 February)
• [w3c/gamepad] spec vibrationActuator gamepad extension (#68) (Friday, 23 February)

OvermindDL1

• Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730) (Friday, 16 February)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 February)

Owen Campbell-Moore

• Re: [w3c/clipboard-apis] When called without gesture, return an error describing rejection (#66) (Wednesday, 14 February)
• [w3c/clipboard-apis] When called without gesture, return an error describing rejection (#66) (Wednesday, 14 February)
• Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Monday, 12 February)

patrick kettner

• [w3c/WebPlatformWG] Add Patrick Kettner to attendees (#103) (Saturday, 3 February)

Paul Adenot

• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Monday, 26 February)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Friday, 23 February)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Friday, 23 February)

Paul Mason

• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Friday, 9 February)

Peter Linss

• Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Request review of Keyboard Lock (#192) (Thursday, 1 February)
• Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186) (Thursday, 1 February)

Peter Rushforth

• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Monday, 19 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Monday, 19 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Monday, 19 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Friday, 16 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Friday, 16 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Friday, 16 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Friday, 16 February)
• Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734) (Wednesday, 14 February)
• [w3c/webcomponents] Please add &lt;map&gt; to the list of elements that support attachShadow(init) (#734) (Wednesday, 14 February)

Philip Jägenstedt

• Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218) (Tuesday, 27 February)
• Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62) (Saturday, 24 February)
• Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62) (Friday, 23 February)
• Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62) (Thursday, 22 February)
• [w3c/clipboard-apis] "context is editable" when firing events needs to be defined (#71) (Thursday, 22 February)
• [w3c/clipboard-apis] The "focused node" when determining event target needs to be defined (#70) (Thursday, 22 February)
• Re: [w3ctag/design-reviews] Payment Handler (#231) (Wednesday, 21 February)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Thursday, 8 February)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Tuesday, 6 February)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Thursday, 1 February)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Thursday, 1 February)
• Re: [whatwg/fullscreen] Meta: make Philip the editor (#121) (Thursday, 1 February)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Thursday, 1 February)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Thursday, 1 February)

Philippe Le Hegaret

• Re: [w3c/uievents] Move focus section to HTML (#185) (Wednesday, 28 February)
• Re: [w3c/uievents] Move focus section to HTML (#185) (Tuesday, 27 February)
• [w3ctag/packaging-on-the-web] Ungutted (#36) (Monday, 26 February)
• Re: [w3ctag/packaging-on-the-web] Please "un-gut" this specification (#35) (Monday, 26 February)

Photopea

• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Wednesday, 28 February)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 26 February)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Friday, 23 February)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Friday, 23 February)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Friday, 23 February)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Thursday, 22 February)

Pierre-Marie Dartus

• [w3c/WebPlatformWG] Add Salesforce attendees (#115) (Monday, 26 February)

Rahul Matte

• Re: [w3c/ServiceWorker] Replaying POST requests (#693) (Monday, 5 February)

Rakina Zata Amni

• Re: [w3c/webcomponents] elementsFromPoint behavior is unclear (#735) (Friday, 16 February)

Ralph Swick

• Re: [w3ctag/packaging-on-the-web] Please "un-gut" this specification (#35) (Friday, 9 February)

raymeskhoury

• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Friday, 2 February)
• Re: [w3c/permissions] Add optional consent due to GDPR (#169) (Thursday, 1 February)

Reilly Grant

• Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68) (Tuesday, 27 February)
• Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68) (Monday, 26 February)

Rick Byers

• Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100) (Wednesday, 14 February)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Wednesday, 14 February)
• Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100) (Wednesday, 14 February)

Rimas Misevičius

• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Friday, 2 February)

Rob Dodson

• [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233) (Monday, 26 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 20 February)

Rob Wormald

• [w3c/WebPlatformWG] Update 18-03-Web-components.md (#116) (Monday, 26 February)

Rouslan Solomakhin

• Re: [w3ctag/design-reviews] Payment Handler (#231) (Friday, 16 February)
• Re: [w3ctag/design-reviews] Payment Handler (#231) (Thursday, 15 February)
• [w3ctag/design-reviews] Payment Handler (#231) (Thursday, 8 February)

Ryosuke Niwa

• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 28 February)
• Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Monday, 26 February)
• Re: [w3c/webcomponents] [Template Instantiation] Review the cloning step (#740) (Monday, 26 February)
• Re: [w3c/webcomponents] [Template Instantiation] Review the cloning step (#740) (Sunday, 25 February)
• Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Sunday, 25 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Sunday, 25 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Sunday, 25 February)
• Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701) (Saturday, 24 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Saturday, 24 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Saturday, 24 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Saturday, 24 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Friday, 23 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Friday, 23 February)
• Re: [w3c/webcomponents] Close this repository in the future (#652) (Friday, 23 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Friday, 23 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Friday, 23 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Thursday, 22 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Thursday, 22 February)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Thursday, 22 February)
• Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Thursday, 22 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Thursday, 22 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Thursday, 22 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Thursday, 22 February)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Wednesday, 21 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Wednesday, 21 February)
• Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Wednesday, 21 February)
• Re: [whatwg/dom] Extend `attachShadow()` safelist (#571) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Close this repository in the future (#652) (Wednesday, 21 February)
• Re: [w3c/selection-api] Background section is a mess (#84) (Wednesday, 21 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Wednesday, 21 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Interface/class-based selector (#719) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 21 February)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Tuesday, 20 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Interface/class-based selector (#719) (Monday, 19 February)
• Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717) (Monday, 19 February)
• Re: [w3c/webcomponents] ARIA custom element API (#159) (Monday, 19 February)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Monday, 19 February)
• Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736) (Monday, 19 February)
• Re: [w3c/webcomponents] Close this repository in the future (#652) (Monday, 19 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Monday, 19 February)
• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Monday, 19 February)
• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Monday, 19 February)
• Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544) (Monday, 19 February)
• Re: [w3c/webcomponents] <iframe> and the History API (#184) (Monday, 19 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Monday, 19 February)
• Re: [w3c/webcomponents] {DocumentOrShadowRoot or Slot}.activePath (#479) (Monday, 19 February)
• Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606) (Monday, 19 February)
• Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Saturday, 17 February)
• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Saturday, 17 February)

Salvador de la Puente González

• Re: [w3c/manifest] Should the scope terminate by "/"? (#554) (Wednesday, 28 February)
• Re: [w3c/ServiceWorker] windowClients state change events - loaded/unloaded (#1269) (Wednesday, 28 February)
• Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278) (Wednesday, 28 February)

Sasha Alex Romanenko

• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 21 February)

Scott Graham

• Re: [w3c/gamepad] Need to spec better support for control mapping (#7) (Wednesday, 14 February)
• Re: [w3c/gamepad] Connected Attribute appears to serve no purpose if the Gamepad object is a snapshot (#10) (Wednesday, 14 February)
• Re: [w3c/gamepad] Standard mapping image should be described in text (#57) (Wednesday, 14 February)
• Re: [w3c/gamepad] Add [Exposed] to all interfaces (#63) (Wednesday, 14 February)
• Re: [w3c/gamepad] Only 4 Gamepads? (#52) (Wednesday, 14 February)
• Re: [w3c/gamepad] Only 4 Gamepads? (#52) (Wednesday, 14 February)
• Re: [w3c/gamepad] About the id (#65) (Wednesday, 14 February)
• Re: [w3c/gamepad] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad (#5) (Wednesday, 14 February)
• Re: [w3c/gamepad] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad (#5) (Wednesday, 14 February)
• Re: [w3c/gamepad] Specify exact length of array returned by Navigator.getGamepads() (#13) (Wednesday, 14 February)
• Re: [w3c/gamepad] Specify exact length of array returned by Navigator.getGamepads() (#13) (Wednesday, 14 February)
• Re: [w3c/gamepad] Order in which index entries should be reused is unspecified (#11) (Wednesday, 14 February)
• Re: [w3c/gamepad] Order in which index entries should be reused is unspecified (#11) (Wednesday, 14 February)
• Re: [w3c/gamepad] Connected Attribute appears to serve no purpose if the Gamepad object is a snapshot (#10) (Wednesday, 14 February)
• Re: [w3c/gamepad] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad (#5) (Wednesday, 14 February)

Sebastian Kippe

• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Tuesday, 27 February)
• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Tuesday, 27 February)

Sergey Rubanov

• Re: [w3ctag/packaging-on-the-web] ECMAScript 2015 is not Draft anymore (#27) (Wednesday, 21 February)

Silviu Marian

• Re: [w3c/permissions] Media autoplay permission (#150) (Thursday, 1 February)

Slawomir Brzezinski

• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Tuesday, 13 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Saturday, 10 February)

sleevi

• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 19 February)

smaug----

• [whatwg/dom] dispatch algorithm doesn't seem to handle the case when target or relatedTarget is Window object (#580) (Wednesday, 28 February)
• Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Wednesday, 21 February)
• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Wednesday, 21 February)
• Re: [w3c/webcomponents] elementsFromPoint behavior is unclear (#735) (Friday, 16 February)
• [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736) (Thursday, 15 February)
• [w3c/webcomponents] elementsFromPoint behavior is unclear (#735) (Thursday, 15 February)
• [w3c/permissions] PermissionStatus's memory management is unclear (#170) (Tuesday, 13 February)

Steve Lee

• Re: [whatwg/fetch] No documentation of which ports are used by default (#667) (Tuesday, 13 February)
• Re: [whatwg/fetch] No documentation of which ports are used by default (#667) (Tuesday, 13 February)
• [whatwg/fetch] No documentation of which ports are used by default (#667) (Tuesday, 6 February)

Surma

• Re: [w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728) (Sunday, 4 February)
• Re: [w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728) (Sunday, 4 February)
• Re: [w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728) (Sunday, 4 February)
• [w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728) (Sunday, 4 February)

Tab Atkins Jr.

• Re: [heycam/webidl] [wip] First pass at adding internal slots (#495) (Friday, 23 February)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 22 February)
• Re: [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522) (Thursday, 22 February)
• Re: [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522) (Thursday, 22 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Wednesday, 21 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Wednesday, 21 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 21 February)
• Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Interface/class-based selector (#719) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Which standard defines :defined (#665) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715) (Tuesday, 20 February)
• Re: [heycam/webidl] Return type on identifier-less named/indexed setter is pointless (#523) (Saturday, 17 February)
• Re: [heycam/webidl] State that by default all objects are created in the relevant realm of `this` (#135) (Friday, 16 February)
• Re: [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522) (Thursday, 15 February)
• [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522) (Thursday, 15 February)
• Re: [heycam/webidl] [[MapData]] is not a thing (#521) (Thursday, 15 February)
• Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100) (Thursday, 15 February)
• Re: [heycam/webidl] [Exposed] section unnecessarily restrictive about partial interface + members (#515) (Thursday, 1 February)
• Re: [heycam/webidl] [Exposed] section unnecessarily restrictive about partial interface + members (#515) (Thursday, 1 February)

Takayoshi Kochi

• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Monday, 26 February)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Monday, 26 February)
• Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62) (Thursday, 22 February)
• Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62) (Thursday, 22 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Thursday, 22 February)
• Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Wednesday, 21 February)
• Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717) (Wednesday, 21 February)
• Re: [whatwg/dom] Extend `attachShadow()` safelist (#571) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Which standard defines :defined (#665) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Which standard defines :defined (#665) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715) (Tuesday, 20 February)
• Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Close this repository in the future (#652) (Tuesday, 20 February)
• Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Tuesday, 20 February)
• Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62) (Friday, 16 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Monday, 5 February)

Takeshi Yoshino

• Re: [whatwg/streams] Meta: Fix CONTRIBUTING.md link (#880) (Wednesday, 14 February)
• Re: [whatwg/streams] Meta: Fix CONTRIBUTING.md link (#880) (Tuesday, 13 February)
• Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668) (Thursday, 8 February)

TAMURA, Kent

• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 28 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 28 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 27 February)
• Re: [w3c/WebPlatformWG] Add tkent-google (#111) (Wednesday, 21 February)
• [w3c/WebPlatformWG] Add tkent-google (#111) (Wednesday, 21 February)
• Re: [whatwg/dom] Change handling of is="" in element creation and cloning (#566) (Wednesday, 14 February)
• Re: [whatwg/dom] Change handling of is="" in element creation and cloning (#566) (Tuesday, 6 February)
• Re: [whatwg/dom] Change handling of is="" in element creation and cloning (#566) (Tuesday, 6 February)

Tantek Çelik

• Re: [w3ctag/design-reviews] Payment Handler (#231) (Friday, 16 February)

Tarun Bansal

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

Thomas Steiner

• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Monday, 26 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Friday, 16 February)
• Re: [w3c/manifest] Richer splash screen backgrounds (#589) (Wednesday, 14 February)
• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Wednesday, 14 February)

Thomas Wisniewski

• [whatwg/xhr] How is the about:blank case in send-non-same-origin supported by the spec? (#194) (Wednesday, 28 February)
• Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609) (Tuesday, 20 February)
• Re: [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192) (Tuesday, 20 February)
• Re: [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192) (Tuesday, 20 February)
• Re: [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192) (Tuesday, 20 February)
• [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192) (Tuesday, 20 February)
• [whatwg/xhr] The logic in the WPT send-authentication-competing-names-passwords.htm does not match the spec. (#191) (Sunday, 18 February)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Sunday, 18 February)

Till Schneidereit

• Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877) (Thursday, 8 February)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Wednesday, 7 February)

Timothy Gu

• Re: [heycam/webidl] Remove definition of class strings of default iterator objects (#501) (Friday, 23 February)
• Re: [heycam/webidl] Remove definition of class strings of default iterator objects (#501) (Saturday, 17 February)
• Re: [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522) (Friday, 16 February)
• Re: [heycam/webidl] [[MapData]] is not a thing (#521) (Thursday, 15 February)
• Re: [whatwg/url] "Let pointer be a pointer to first code point in..." (#373) (Tuesday, 13 February)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 7 February)
• Re: [heycam/webidl] Is an interface named I exposed in realm R (#518) (Sunday, 4 February)

Tobie Langel

• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Wednesday, 28 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Wednesday, 28 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Tuesday, 27 February)
• [heycam/webidl] ES bindings for constants on Globals (#528) (Tuesday, 27 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Tuesday, 27 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Tuesday, 27 February)
• Re: [heycam/webidl] Add bigint type (#525) (Tuesday, 27 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 26 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 26 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 26 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 26 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 26 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 26 February)
• Re: [heycam/webidl] Prototype of @@unscopable object (#496) (Monday, 26 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 26 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 26 February)
• Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526) (Friday, 23 February)
• Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526) (Friday, 23 February)
• Re: [heycam/webidl] Remove definition of class strings of default iterator objects (#501) (Friday, 23 February)
• Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526) (Thursday, 22 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 9 February)
• Re: [heycam/webidl] Testing (#520) (Friday, 9 February)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 9 February)
• Re: [heycam/webidl] Require tests for PR/issues? (#268) (Friday, 9 February)
• Re: [heycam/webidl] Require tests for PR/issues? (#268) (Friday, 9 February)
• Re: [heycam/webidl] Testing (#520) (Friday, 9 February)
• [heycam/webidl] Testing (#520) (Friday, 9 February)
• Re: [heycam/webidl] Definition of "is an array index" makes "-0" an array index (#516) (Friday, 9 February)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Friday, 9 February)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Thursday, 8 February)
• Re: [heycam/webidl] Four (not five) kind of special operations (#519) (Thursday, 8 February)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Thursday, 8 February)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 7 February)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 7 February)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 7 February)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 7 February)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 7 February)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 7 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Wednesday, 7 February)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Wednesday, 7 February)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Tuesday, 6 February)

Tomek Wytrębowicz

• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Friday, 23 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 21 February)
• [w3c/WebPlatformWG] Add declarative Shadow DOM to the Agenda (#113) (Wednesday, 21 February)
• Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731) (Wednesday, 7 February)
• Re: [w3c/webcomponents] typo (#732) (Wednesday, 7 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 7 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 7 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 7 February)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Tuesday, 6 February)
• [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731) (Tuesday, 6 February)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Tuesday, 6 February)
• [w3c/WebPlatformWG] Add Tomek Wytrębowicz to attendees (#102) (Thursday, 1 February)

Toni-Jan Keith Monserrat

• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Wednesday, 21 February)

Travis Leithead

• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Friday, 16 February)
• Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Tuesday, 13 February)
• Re: [w3ctag/design-reviews] Streams General issue (#92) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Streams General issue (#92) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Streams General issue (#92) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Streams General issue (#92) (Friday, 2 February)
• Re: [w3ctag/design-reviews] Request Review: Gesture Delegation (#199) (Thursday, 1 February)
• Re: [w3ctag/design-reviews] HTML General Review (#174) (Thursday, 1 February)

Trey Shugart

• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Thursday, 15 February)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Thursday, 8 February)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Tuesday, 6 February)

Valeriob

• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Monday, 12 February)
• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Monday, 12 February)

Wendy Seltzer

• Re: [w3c/permissions] Preventing blackmail (#171) (Friday, 16 February)

wy

• Re: [w3c/ServiceWorker] What's the possible reason for navigator.serviceWorker.register error？ (#1275) (Monday, 5 February)
• Re: [w3c/ServiceWorker] What's the possible reason for navigator.serviceWorker.register error？ (#1275) (Monday, 5 February)
• [w3c/ServiceWorker] What's the possible reason for navigator.serviceWorker.register error？ (#1275) (Friday, 2 February)

wzup

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

Xiaocheng Hu

• Re: [w3c/clipboard-apis] The "context is editable"-condition in the fire event-algorithm needs clarification (#69) (Tuesday, 20 February)

Xiaoqian Wu

• Re: [w3c/clipboard-apis] Spec does not auto-deploy when changes are made (#68) (Saturday, 17 February)

Xidorn Quan

• [whatwg/dom] Export attribute change steps (#567) (Saturday, 3 February)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Friday, 2 February)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Thursday, 1 February)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Thursday, 1 February)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Thursday, 1 February)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Thursday, 1 February)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Thursday, 1 February)

Yoav Weiss

• [w3c/ServiceWorker] Service Worker handling of first page load subresources (#1282) (Monday, 26 February)

youennf

• Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674) (Wednesday, 28 February)
• Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674) (Wednesday, 28 February)

Yuri Karadzhov

• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Sunday, 25 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Saturday, 24 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Saturday, 24 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Saturday, 24 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Friday, 23 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Wednesday, 21 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Wednesday, 21 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Tuesday, 20 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Tuesday, 20 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Tuesday, 20 February)
• Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Tuesday, 20 February)
• [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739) (Tuesday, 20 February)

Yutaka Hirano

• Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674) (Wednesday, 28 February)
• Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674) (Tuesday, 27 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Wednesday, 21 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Monday, 19 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Monday, 19 February)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Sunday, 18 February)
• Re: [whatwg/fetch] No documentation of which ports are used by default (#667) (Tuesday, 13 February)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Tuesday, 6 February)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Tuesday, 6 February)

Yves Lafon

• Re: [w3c/pointerlock] Don't point to developers.whatwg.org (#26) (Thursday, 8 February)
• Re: [w3c/pointerlock] Don't point to developers.whatwg.org (#26) (Thursday, 8 February)
• Re: [w3c/pointerlock] fix references, see #26 (#31) (Wednesday, 7 February)
• Re: [w3c/pointerlock] fix references, see #26 (#31) (Wednesday, 7 February)
• [w3c/pointerlock] fix references, see #26 (#31) (Wednesday, 7 February)
• Re: [w3c/pointerlock] WD for PL2.0 (#25) (Tuesday, 6 February)
• Re: [w3ctag/design-reviews] Trusted Types (#198) (Thursday, 1 February)

Zambonifofex

• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Sunday, 18 February)

Zirro

• [whatwg/dom] Return value for DOMTokenList's replace() (#577) (Friday, 23 February)

Last message date: Wednesday, 28 February 2018 23:59:09 UTC