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

804k

• Re: [w3c/manifest] Feature request: access to menu bar and context menus (Issue #1025) (Friday, 10 February)

Aaron Gustafson

• Re: [w3c/manifest] Feature request: access to menu bar and context menus (Issue #1025) (Friday, 10 February)
• Re: [w3c/manifest] Transparent Bottom Navigation Bar (#804) (Thursday, 9 February)
• Re: [w3c/manifest] We should add a character limit to `name` and `short_name` (Issue #1070) (Monday, 6 February)

Abdoulfatah Omar Abdillahi

• [whatwg/webidl] Hataf Omar (Issue #1266) (Sunday, 12 February)

Adam Klein

• [w3ctag/design-reviews] WebAssembly Garbage Collection extensions (Issue #814) (Friday, 3 February)

Adam Rice

• Re: [whatwg/streams] Should cancelation error from UnderlyingSource be transferred too? (Issue #1259) (Monday, 27 February)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Monday, 20 February)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Monday, 20 February)
• Re: [whatwg/streams] Meta: make fetch() reference more precise (PR #1258) (Monday, 20 February)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Friday, 17 February)
• Re: [whatwg/url] Expose a URLHost class to JavaScript (#288) (Friday, 17 February)
• Re: [whatwg/url] Expose a URLHost class to JavaScript (#288) (Friday, 17 February)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Friday, 17 February)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Friday, 17 February)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Friday, 17 February)
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Thursday, 2 February)
• Re: [whatwg/streams] Should the "set up" algorithm for IDL-created WritableStreams wrap the write algorithm? (Issue #1253) (Wednesday, 1 February)

Addison Phillips

• [w3c/uievents-key] Use of uppercase hex for code points (editorial) (Issue #60) (Thursday, 9 February)
• Re: [w3c/uievents-code] Unicode terminology (Issue #36) (Friday, 3 February)

Alon Gamliel

• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) (Saturday, 11 February)
• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) (Saturday, 11 February)
• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) (Friday, 10 February)
• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) (Friday, 10 February)

Amelia Bellamy-Royds

• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Monday, 27 February)

Amy Guy

• Re: [w3ctag/design-reviews] CR Snapshot Review for EPUB 3.3 (Issue #816) (Tuesday, 28 February)
• Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Thursday, 23 February)
• Re: [w3ctag/design-reviews] Autoplay Policy Detection API (Issue #810) (Wednesday, 15 February)
• Re: [w3ctag/design-reviews] Pre-CR review: DOM Review Draft — Published 21 June 2021 (#658) (Thursday, 9 February)
• [whatwg/dom] [TAG review] Explain the difference between this.shadowRoot and this.internals.shadowRoot (Issue #1158) (Thursday, 9 February)
• [whatwg/dom] [TAG review] Describe delegatesFocus propery (Issue #1157) (Thursday, 9 February)
• Re: [w3ctag/design-reviews] Autoplay Policy Detection API (Issue #810) (Thursday, 9 February)
• [whatwg/dom] [TAG review] Define "is available to element internals flag" (Issue #1156) (Thursday, 9 February)
• Re: [w3ctag/design-reviews] VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport (Issue #768) (Thursday, 9 February)
• Re: [w3ctag/design-reviews] WebAuthn PRF extension (Issue #806) (Wednesday, 8 February)
• Re: [w3ctag/design-reviews] WebAuthn PRF extension (Issue #806) (Wednesday, 8 February)

Andrea Giammarchi

• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 10 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 10 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Thursday, 9 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Thursday, 9 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Thursday, 9 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Tuesday, 7 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Tuesday, 7 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 3 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 3 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 3 February)

Andreu Botella

• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Thursday, 23 February)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Thursday, 16 February)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 6 February)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 6 February)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 6 February)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 6 February)
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Saturday, 4 February)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Wednesday, 1 February)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Wednesday, 1 February)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Wednesday, 1 February)

Anne van Kesteren

• Re: [whatwg/webidl] PR changed the setlike `add` method to return the value that was added to the setlike object instead of the object itself. Was that an accident? (Issue #1268) (Tuesday, 28 February)
• Re: [whatwg/webidl] setlike.add() is meant to return the setlike. Fixes #1268 (PR #1269) (Tuesday, 28 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 28 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 28 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Monday, 27 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 24 February)
• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Friday, 24 February)
• Re: [whatwg/url] "host-missing" validation error should be a failure (Issue #757) (Friday, 24 February)
• Re: [whatwg/url] host-missing validation error is fatal (PR #758) (Friday, 24 February)
• [whatwg/url] host-missing validation error is fatal (PR #758) (Friday, 24 February)
• Re: [whatwg/dom] Allow ExtendableEvent within Document (Issue #1167) (Thursday, 23 February)
• Re: [whatwg/dom] Allow ExtendableEvent within Document (Issue #1167) (Thursday, 23 February)
• Re: [whatwg/url] Proposal: Functional chaining on URLSearchParams (Issue #756) (Thursday, 23 February)
• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Thursday, 23 February)
• Re: [w3c/FileAPI] "Null"ing out the Origin of a BLOB (#74) (Thursday, 23 February)
• Re: [w3c/FileAPI] "Null"ing out the Origin of a BLOB (#74) (Thursday, 23 February)
• Re: [whatwg/url] Removing trailing C0 control or space at basic URL parser makes difference with override (#542) (Thursday, 23 February)
• Re: [whatwg/url] Expand which hostnames are considered IPv4 addresses (Issue #679) (Thursday, 23 February)
• Re: [whatwg/url] Expand which hostnames are considered IPv4 addresses (Issue #679) (Thursday, 23 February)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Thursday, 23 February)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Thursday, 23 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Wednesday, 22 February)
• Re: [whatwg/fetch] Exporting terms for service worker spec (PR #1608) (Wednesday, 22 February)
• Re: [whatwg/fetch] Exporting terms for service worker spec (PR #1608) (Wednesday, 22 February)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Wednesday, 22 February)
• Re: [whatwg/dom] Update createNSResolver and lookupNamespaceURI() (PR #1165) (Wednesday, 22 February)
• Re: [whatwg/dom] lookupNamespaceURI('xml') (#857) (Wednesday, 22 February)
• Re: [whatwg/dom] Update createNSResolver and lookupNamespaceURI() (PR #1165) (Wednesday, 22 February)
• Re: [whatwg/dom] Update createNSResolver and lookupNamespaceURI() (PR #1165) (Wednesday, 22 February)
• Re: [whatwg/dom] Update createNSResolver and lookupNamespaceURI() (PR #1165) (Wednesday, 22 February)
• Re: [whatwg/webidl] setlike.add() is meant to return the setlike. Fixes #1268 (PR #1269) (Wednesday, 22 February)
• Re: [whatwg/webidl] setlike.add() is meant to return the setlike. Fixes #1268 (PR #1269) (Wednesday, 22 February)
• Re: [whatwg/dom] Editorial: minor reflect cleanup (PR #1166) (Wednesday, 22 February)
• [whatwg/dom] Editorial: minor reflect cleanup (PR #1166) (Wednesday, 22 February)
• Re: [whatwg/fetch] Feature detecting streaming requests (Issue #1470) (Wednesday, 22 February)
• Re: [whatwg/fetch] Feature detecting streaming requests (Issue #1470) (Wednesday, 22 February)
• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [whatwg/fetch] Proposal: Support GET bodies (#83) (Wednesday, 22 February)
• Re: [whatwg/streams] Review Draft Publication: February 2023 (PR #1257) (Monday, 20 February)
• Re: [whatwg/streams] Meta: make fetch() reference more precise (PR #1258) (Monday, 20 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 20 February)
• Re: [whatwg/streams] Meta: make fetch() reference more precise (PR #1258) (Monday, 20 February)
• Re: [whatwg/streams] Meta: make fetch() reference more precise (PR #1258) (Monday, 20 February)
• Re: [whatwg/streams] Review Draft Publication: February 2023 (PR #1257) (Monday, 20 February)
• Re: [whatwg/streams] Meta: make fetch() reference more precise (PR #1258) (Monday, 20 February)
• [whatwg/streams] Meta: make fetch() reference more precise (PR #1258) (Monday, 20 February)
• Re: [whatwg/xhr] Review Draft Publication: February 2023 (PR #370) (Monday, 20 February)
• Re: [whatwg/url] Review Draft Publication: February 2023 (PR #755) (Monday, 20 February)
• Re: [whatwg/storage] Review Draft Publication: February 2023 (PR #160) (Monday, 20 February)
• [whatwg/xhr] Review Draft Publication: February 2023 (PR #370) (Monday, 20 February)
• [whatwg/url] Review Draft Publication: February 2023 (PR #755) (Monday, 20 February)
• [whatwg/streams] Review Draft Publication: February 2023 (PR #1257) (Monday, 20 February)
• [whatwg/storage] Review Draft Publication: February 2023 (PR #160) (Monday, 20 February)
• Re: [whatwg/fetch] blob: URLs and range requests (#1070) (Monday, 20 February)
• Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Monday, 20 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Monday, 20 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 20 February)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Monday, 20 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 20 February)
• Re: [whatwg/dom] MutationObserver GC section looks bogus (Issue #1159) (Monday, 20 February)
• Re: [whatwg/dom] MutationObserver invocation order (#713) (Monday, 20 February)
• Re: [whatwg/dom] "Append mo to unit of related similar-origin bro..." (#720) (Monday, 20 February)
• Re: [whatwg/dom] "Append mo to unit of related similar-origin bro..." (#720) (Monday, 20 February)
• Re: [whatwg/dom] Correct MutationObserver ownership story (PR #1160) (Monday, 20 February)
• Re: [whatwg/url] Named validation errors (#406) (Monday, 20 February)
• Re: [whatwg/url] Named validation errors (#502) (Monday, 20 February)
• Re: [whatwg/url] Named validation errors (#502) (Saturday, 18 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Friday, 17 February)
• Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Friday, 17 February)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Friday, 17 February)
• Re: [whatwg/url] Expose a URLHost class to JavaScript (#288) (Friday, 17 February)
• Re: [whatwg/url] Expose a URLHost class to JavaScript (#288) (Friday, 17 February)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 17 February)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 17 February)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Friday, 17 February)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 17 February)
• Re: [whatwg/url] Expose a URLHost class to JavaScript (#288) (Friday, 17 February)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Friday, 17 February)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Friday, 17 February)
• Re: [whatwg/dom] Correct MutationObserver ownership story (PR #1160) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [whatwg/dom] Correct MutationObserver ownership story (PR #1160) (Friday, 17 February)
• Re: [whatwg/xhr] XHR: how can I read request headers? (Issue #369) (Friday, 17 February)
• Re: [whatwg/xhr] XHR: how can I read request headers? (Issue #369) (Friday, 17 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Friday, 17 February)
• Re: [whatwg/fetch] CI test (PR #1605) (Friday, 17 February)
• Re: [whatwg/url] The web needs a stable definition of a Query Parameter in a URL (#617) (Friday, 17 February)
• Re: [whatwg/webidl] Switch maplike/setlike to use infra maps and sets (PR #1138) (Friday, 17 February)
• [whatwg/webidl] PR changed the setlike `add` method to return the value that was added to the setlike object instead of the object itself. Was that an accident? (Issue #1268) (Friday, 17 February)
• Re: [whatwg/fetch] CI test (PR #1605) (Thursday, 16 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Thursday, 16 February)
• Re: [w3ctag/design-reviews] Exposing predefined instances of an object as static properties on the class (Discussion #817) (Thursday, 16 February)
• Re: [w3c/permissions] Export permissions task source (PR #407) (Wednesday, 15 February)
• Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Wednesday, 15 February)
• Re: [w3ctag/design-reviews] Storage Access API (Issue #807) (Wednesday, 15 February)
• Re: [whatwg/dom] Allow subclassing of AbortController / AbortSignal (Issue #1162) (Wednesday, 15 February)
• Re: [whatwg/fetch] Cannot get next URL for redirect="manual" (#763) (Wednesday, 15 February)
• Re: [whatwg/fetch] Cannot get next URL for redirect="manual" (#763) (Wednesday, 15 February)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)
• Re: [whatwg/fetch] CI test (PR #1605) (Wednesday, 15 February)
• Re: [whatwg/dom] Allow subclassing of AbortController / AbortSignal (Issue #1162) (Wednesday, 15 February)
• Re: [whatwg/fetch] Cannot get next URL for redirect="manual" (#763) (Wednesday, 15 February)
• [whatwg/fetch] CI test (PR #1605) (Wednesday, 15 February)
• Re: [whatwg/dom] Side effects due to tree insertion or removal (script, iframe) (#808) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)
• Re: [whatwg/webidl] Make [SameObject] beneficial (#212) (Wednesday, 15 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 14 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 14 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 14 February)
• Re: [whatwg/fetch] Conditional headers presense add `Cache-Control: no-cache` by default (Issue #1604) (Tuesday, 14 February)
• Re: [whatwg/fetch] Conditional headers presense add `Cache-Control: no-cache` by default (Issue #1604) (Tuesday, 14 February)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 14 February)
• Re: [whatwg/dom] Don't store is value when it won't be useful (#661) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Specify behavior of popovers with fullscreen API (Issue #216) (Tuesday, 14 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 14 February)
• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Monday, 13 February)
• Re: [whatwg/dom] Correct MutationObserver ownership story (PR #1160) (Monday, 13 February)
• [whatwg/dom] Correct MutationObserver ownership story (PR #1160) (Monday, 13 February)
• Re: [whatwg/dom] MutationObserver GC section looks bogus (Issue #1159) (Monday, 13 February)
• Re: [whatwg/dom] MutationObserver GC section looks bogus (Issue #1159) (Monday, 13 February)
• [whatwg/dom] MutationObserver GC section looks bogus (Issue #1159) (Monday, 13 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Monday, 13 February)
• Re: [whatwg/url] Meta: UTS46 feedback (Issue #744) (Monday, 13 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Monday, 13 February)
• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Monday, 13 February)
• Re: [whatwg/url] Allow `[` and `]` as URL code-points (Issue #753) (Monday, 13 February)
• Re: [whatwg/url] Clarify return value of the IPv4 number parser (PR #754) (Monday, 13 February)
• Re: [whatwg/url] Clarify return value of the IPv4 number parser (PR #754) (Monday, 13 February)
• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Monday, 13 February)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 10 February)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 10 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 10 February)
• Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Thursday, 9 February)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 9 February)
• Re: [w3ctag/design-reviews] Pre-CR review: DOM Review Draft — Published 21 June 2021 (#658) (Thursday, 9 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Thursday, 9 February)
• Re: [w3ctag/design-reviews] Pre-CR review: DOM Review Draft — Published 21 June 2021 (#658) (Thursday, 9 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Thursday, 9 February)
• Re: [whatwg/fetch] Cache-mode and upstream Cache-Control (#722) (Wednesday, 8 February)
• Re: [whatwg/url] meta: add Ada to pull request template (PR #752) (Wednesday, 8 February)
• Re: [whatwg/url] meta: add Ada to pull request template (PR #752) (Wednesday, 8 February)
• Re: [whatwg/url] Add Ada to implementations section of readme (PR #750) (Wednesday, 8 February)
• Re: [whatwg/url] Add Ada to implementations section of readme (PR #750) (Wednesday, 8 February)
• Re: [whatwg/url] Fix reference to resolve a blob URL (PR #751) (Wednesday, 8 February)
• Re: [whatwg/fetch] s/early-hint/early-hints/ (PR #1562) (Wednesday, 8 February)
• Re: [whatwg/fetch] s/early-hint/early-hints/ (PR #1562) (Wednesday, 8 February)
• Re: [whatwg/fetch] Process subresource link headers (PR #1409) (Wednesday, 8 February)
• Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429) (Wednesday, 8 February)
• Re: [whatwg/fetch] s/early-hint/early-hints/ (PR #1562) (Wednesday, 8 February)
• Re: [whatwg/url] Add Ada to implementations section of readme (PR #750) (Wednesday, 8 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Wednesday, 8 February)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Wednesday, 8 February)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Wednesday, 8 February)
• Re: [w3c/touch-events] Update retargeting steps link (PR #135) (Tuesday, 7 February)
• Re: [w3ctag/design-reviews] FYI - Add optional `submitter` parameter to the `FormData` constructor (Issue #812) (Tuesday, 7 February)
• Re: [w3c/touch-events] Update retargeting steps link (PR #135) (Tuesday, 7 February)
• Re: [w3c/touch-events] Update retargeting steps link (PR #135) (Tuesday, 7 February)
• Re: [w3c/permissions] Add a hook for implicitly granting or denying before requesting permission to use (Issue #413) (Tuesday, 7 February)
• Re: [w3c/permissions] Add another permission state "positive" or "granted last time"? (Issue #414) (Tuesday, 7 February)
• Re: [whatwg/fetch] If a resource allows credentials but omits Vary, shouldn't responses to non-CORS requests also contain Access-Control-Allow-Credentials? (Issue #1601) (Tuesday, 7 February)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 7 February)
• Re: [whatwg/fetch] Specify how/if response status code & content type are exposed for cross-origin navigations (Issue #1602) (Tuesday, 7 February)
• Re: [whatwg/fetch] Cache-mode and upstream Cache-Control (#722) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Tuesday, 7 February)
• Re: [whatwg/xhr] xmlhttprequest.responseText occasionally appears Chinese garbled characters (Issue #368) (Tuesday, 7 February)
• Re: [whatwg/xhr] xmlhttprequest.responseText occasionally appears Chinese garbled characters (Issue #368) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891) (Tuesday, 7 February)
• Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891) (Tuesday, 7 February)
• Re: [whatwg/url] Allow specifying additional "special" schemes. (Issue #749) (Monday, 6 February)
• Re: [whatwg/fetch] Cache-mode and upstream Cache-Control (#722) (Monday, 6 February)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 6 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Monday, 6 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Monday, 6 February)
• Re: [w3c/FileAPI] Don't export "resolve" (Issue #190) (Monday, 6 February)
• Re: [w3c/FileAPI] Update the exported text for resolve (PR #191) (Monday, 6 February)
• Re: [w3c/FileAPI] Update the exported text for resolve (PR #191) (Monday, 6 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Monday, 6 February)
• Re: [whatwg/fetch] If a resource allows credentials but omits Vary, shouldn't responses to non-CORS requests also contain Access-Control-Allow-Credentials? (Issue #1601) (Monday, 6 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 6 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 6 February)
• Re: [whatwg/fetch] worker timing doesn't need to be TAO protected for subresources (Issue #1597) (Monday, 6 February)
• Re: [w3c/FileAPI] Update the exported text for resolve (PR #191) (Monday, 6 February)
• Re: [whatwg/url] Allow specifying additional "special" schemes. (Issue #749) (Monday, 6 February)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Monday, 6 February)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Monday, 6 February)
• Re: [whatwg/dom] Broken references in DOM Standard (Issue #1149) (Monday, 6 February)
• Re: [whatwg/dom] Editorial: remove reference to time origin (PR #1151) (Monday, 6 February)
• [whatwg/dom] Editorial: remove reference to time origin (PR #1151) (Monday, 6 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Monday, 6 February)
• Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891) (Monday, 6 February)
• Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891) (Monday, 6 February)
• Re: [whatwg/dom] Allow custom "get the parent" algorithms for EventTargets (#583) (Saturday, 4 February)
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Thursday, 2 February)

Antonio Sartori

• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Monday, 13 February)
• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Monday, 13 February)

Arnaud Budkiewicz

• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Thursday, 2 February)

Artem Skoretskiy

• Re: [whatwg/fetch] Cannot get next URL for redirect="manual" (#763) (Wednesday, 15 February)

Arthur Hemery

• Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Tuesday, 28 February)
• Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Tuesday, 14 February)

bashi

• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Tuesday, 21 February)

Ben Lesh

• Re: [whatwg/dom] Improving ergonomics of events with Observable (#544) (Friday, 17 February)

Benjamin Gruenbaum

• Re: [whatwg/dom] Improving ergonomics of events with Observable (#544) (Monday, 20 February)
• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) (Saturday, 11 February)
• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) (Friday, 10 February)

Bergi

• Re: [whatwg/url] The web needs a stable definition of a Query Parameter in a URL (#617) (Friday, 17 February)

bigopon

• Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819) (Wednesday, 15 February)

bleistivt

• Re: [whatwg/dom] Improving ergonomics of events with Observable (#544) (Saturday, 18 February)

Boris Letocha

• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Monday, 6 February)

Brad Kemper

• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Tuesday, 28 February)

Bradley Needham

• Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Tuesday, 21 February)
• Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Tuesday, 21 February)
• Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Tuesday, 21 February)
• Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Tuesday, 21 February)
• Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Tuesday, 21 February)

Brian Louis Ramirez

• Re: [w3c/ServiceWorker] ServiceWorker fetch fast-path (Issue #1670) (Thursday, 16 February)

bvandersloot-mozilla

• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Thursday, 9 February)

Caleb Williams

• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Monday, 27 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Saturday, 25 February)

caraitto

• Re: [whatwg/webidl] Enums that does not throw? (#893) (Tuesday, 28 February)

Caridy Patiño

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 7 February)

Carlos Lopez

• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 28 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Monday, 27 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Friday, 24 February)
• Re: [w3c/ServiceWorker] Allow users to extend ExtendableEvent, anywhere (#1290) (Thursday, 23 February)
• [whatwg/dom] Allow ExtendableEvent within Document (Issue #1167) (Thursday, 23 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 14 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 14 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Monday, 13 February)

Charlie Harrison

• Re: [w3ctag/design-reviews] Review Request for Attribution Reporting API (Issue #724) (Tuesday, 28 February)

Cherie1984

• [whatwg/dom] chrome on android (Issue #1153) (Tuesday, 7 February)

Chris Harrelson

• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Tuesday, 7 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Monday, 6 February)
• Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891) (Monday, 6 February)
• Re: [w3ctag/design-reviews] FYI - Add optional `submitter` parameter to the `FormData` constructor (Issue #812) (Friday, 3 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 3 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Thursday, 2 February)

Chris Needham

• Re: [w3ctag/design-reviews] Autoplay Policy Detection API (Issue #810) (Thursday, 9 February)

Christian Ramelow

• Re: [whatwg/fetch] Cannot get next URL for redirect="manual" (#763) (Wednesday, 15 February)

Claudia Meadows

• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Tuesday, 7 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Tuesday, 7 February)

csotiMatyas

• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) (Monday, 13 February)

cynthia

• Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Monday, 20 February)
• Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Tuesday, 14 February)
• Re: [w3ctag/design-reviews] Spec review for CSS Nesting (Issue #791) (Tuesday, 14 February)
• Re: [w3ctag/design-reviews] AbortSignal.timeout() (Issue #711) (Thursday, 9 February)
• Re: [w3ctag/design-reviews] Collection of Screensharing-related UX Hints (Issue #744) (Wednesday, 8 February)
• Re: [w3ctag/design-reviews] Collection of Screensharing-related UX Hints (Issue #744) (Wednesday, 8 February)

Dan Robertson

• [whatwg/fetch] Editorial: add <div algorithm> wrappers to Request class (PR #1612) (Tuesday, 28 February)
• Re: [w3c/uievents] Wheel event groups are not defined (Issue #338) (Tuesday, 28 February)
• Re: [w3c/uievents] Wheel event groups are not defined (Issue #338) (Monday, 27 February)
• [w3c/uievents] Define behavior for wheel event group when the scroll is handed off (Issue #342) (Tuesday, 21 February)
• Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Tuesday, 21 February)
• Re: [whatwg/fetch] blob: URLs and range requests (#1070) (Tuesday, 21 February)
• Re: [w3c/uievents] Define behavior for wheel event group when the initial target is mutated (Issue #341) (Sunday, 19 February)
• [w3c/uievents] Define behavior for wheel event group when the initial target is mutated (Issue #341) (Sunday, 19 February)
• Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Saturday, 18 February)
• Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Saturday, 18 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Friday, 17 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Friday, 17 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Thursday, 16 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Thursday, 16 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Thursday, 16 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Sunday, 5 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Sunday, 5 February)
• Re: [whatwg/fetch] Add HTTP OWS handling to single range header parsing (PR #1564) (Sunday, 5 February)
• Re: [whatwg/fetch] Create Rage header section in HTTP extensions section (Issue #1553) (Sunday, 5 February)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Multi-Screen Window Placement on the Web - Initiating Multi-Screen Experiences (Issue #767) (Tuesday, 28 February)
• Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Tuesday, 28 February)
• Re: [w3ctag/design-reviews] Review Request for Attribution Reporting API (Issue #724) (Tuesday, 28 February)
• Re: [w3ctag/design-reviews] Review request for TURTLEDOVE (Issue #723) (Tuesday, 28 February)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Tuesday, 14 February)
• Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721) (Monday, 13 February)
• Re: [w3ctag/design-reviews] Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 (Issue #811) (Monday, 13 February)
• Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Monday, 13 February)
• Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Wednesday, 8 February)
• Re: [w3ctag/design-reviews] Two changes to Secure Payment Confirmation prior to CR (Issue #802) (Wednesday, 8 February)
• Re: [w3ctag/design-reviews] Two changes to Secure Payment Confirmation prior to CR (Issue #802) (Wednesday, 8 February)

Daniel Murphy

• Re: [w3c/manifest] We should add a character limit to `name` and `short_name` (Issue #1070) (Monday, 6 February)
• [w3c/manifest] Titles, subtitles, and spoofing mitigations. (Issue #1071) (Monday, 6 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Saturday, 4 February)
• [w3c/manifest] We should add a character limit to `name` and `short_name` (Issue #1070) (Friday, 3 February)

Daniel Stenberg

• Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703) (Monday, 6 February)

Danny Engelman

• [WICG/webcomponents] Chrome doesn't repaint with :last-of-type AND shadowRoot AND :host(:active) (Issue #985) (Friday, 24 February)

Darien Maillet Valentine

• Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969) (Sunday, 26 February)
• Re: [whatwg/dom] Allow subclassing of AbortController / AbortSignal (Issue #1162) (Wednesday, 15 February)
• Re: [w3c/ServiceWorker] ServiceWorker fetch fast-path (Issue #1670) (Monday, 13 February)

DarkWiiPlayer

• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Monday, 27 February)
• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Monday, 27 February)

David Dworken

• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Wednesday, 22 February)

David Zero

• Re: [whatwg/url] Clarify return value of the IPv4 number parser (PR #754) (Monday, 13 February)
• [whatwg/url] Clarify return value of the IPv4 number parser (PR #754) (Monday, 13 February)

Deepak0320Singhal

• Re: [whatwg/fetch] Rename "extract-value flag" to "extract-value" and define it as a boolean (Issue #1567) (Monday, 6 February)

Denis Bittencourt Muniz

• [whatwg/xhr] XHR: how can I read request headers? (Issue #369) (Thursday, 16 February)

Denis Pushkarev

• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Sunday, 26 February)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Friday, 17 February)

Diego Gonzalez

• [w3ctag/design-reviews] (Document Subtitle): Early review for adding a new value to the standard list of `name`s for a meta tag (Issue #819) (Monday, 20 February)

Dino Reić

• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 9 February)
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 9 February)

Domenic Denicola

• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Monday, 27 February)
• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Monday, 27 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [whatwg/fetch] The fetch pull algorithm does not pass proper bytesWritten to ReadableByteStreamControllerRespond (Issue #1610) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [whatwg/streams] Should terminating a worker close/error streams? (Issue #1256) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Monday, 20 February)
• Re: [whatwg/streams] Review Draft Publication: February 2023 (PR #1257) (Monday, 20 February)
• Re: [whatwg/streams] Review Draft Publication: February 2023 (PR #1257) (Monday, 20 February)
• Re: [whatwg/streams] Should terminating a worker close/error streams? (Issue #1256) (Saturday, 18 February)
• Re: [w3ctag/design-reviews] Exposing predefined instances of an object as static properties on the class (Discussion #817) (Thursday, 16 February)
• Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Thursday, 16 February)
• Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Wednesday, 15 February)
• Re: [whatwg/url] Named validation errors (#502) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)

Dominic Farolino

• Re: [whatwg/dom] Improving ergonomics of events with Observable (#544) (Friday, 17 February)
• Re: [whatwg/dom] Improving ergonomics of events with Observable (#544) (Wednesday, 15 February)
• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Thursday, 9 February)
• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Thursday, 9 February)

dontcallmedom-bot

• [whatwg/fullscreen] Broken references in Fullscreen API Standard (Issue #215) (Thursday, 2 February)
• [whatwg/dom] Broken references in DOM Standard (Issue #1149) (Thursday, 2 February)
• [w3c/uievents-code] Broken references in UI Events KeyboardEvent code Values (Issue #37) (Wednesday, 1 February)

Eli Grey

• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Wednesday, 15 February)

Ertuğrul Kürşat Kemaloğlu

• [w3c/ServiceWorker] Service Worker Redirect (Issue #1673) (Sunday, 26 February)

Fady Makram

• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Wednesday, 1 February)

feibirds

• [whatwg/xhr] xmlhttprequest.responseText occasionally appears Chinese garbled characters (Issue #368) (Tuesday, 7 February)

ferchoran

• [whatwg/storage] Fernando Rangel (Issue #159) (Friday, 17 February)
• [whatwg/storage] Fernando Rangel (Issue #158) (Friday, 17 February)

fergald

• Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Tuesday, 21 February)
• Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Monday, 20 February)
• Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Thursday, 2 February)

flachware

• Re: [w3c/manifest] Feature request: access to menu bar and context menus (Issue #1025) (Monday, 13 February)

Forrest

• Re: [WICG/webcomponents] define behavior of `@import` in Cascading Style Sheet (CSS) modules (#870) (Monday, 20 February)

François REMY

• Re: [whatwg/dom] Correct MutationObserver ownership story (PR #1160) (Thursday, 16 February)

Hadley Beeman

• Re: [w3ctag/design-reviews] FedCM Auto Re-authentication API (Issue #813) (Monday, 20 February)
• Re: [w3ctag/design-reviews] Private State Tokens (formerly Trust Tokens) (Issue #780) (Wednesday, 15 February)
• Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808) (Wednesday, 15 February)
• Re: [w3ctag/design-reviews] Storage Access API (Issue #807) (Wednesday, 15 February)
• Re: [w3ctag/design-reviews] Storage Access API (Issue #807) (Wednesday, 15 February)
• Re: [w3ctag/design-reviews] Review of IMSC-HRM (Issue #788) (Wednesday, 8 February)
• Re: [w3ctag/design-reviews] Private State Tokens (formerly Trust Tokens) (Issue #780) (Wednesday, 8 February)
• Re: [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240) (Wednesday, 8 February)

Hamish Willee

• Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Wednesday, 15 February)
• Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Friday, 10 February)
• Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Wednesday, 8 February)
• [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Tuesday, 7 February)

Harald Alvestrand

• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Monday, 6 February)

Henri Sivonen

• Re: [w3c/clipboard-apis] Replacing no-break spaces when converting HTML to plain text upon clipboard export (Issue #173) (Tuesday, 7 February)

Hermann Stanew

• Re: [WICG/webcomponents] define behavior of `@import` in Cascading Style Sheet (CSS) modules (#870) (Thursday, 23 February)
• Re: [WICG/webcomponents] define behavior of `@import` in Cascading Style Sheet (CSS) modules (#870) (Thursday, 23 February)

ianbjacobs

• Re: [w3ctag/design-reviews] Two changes to Secure Payment Confirmation prior to CR (Issue #802) (Wednesday, 8 February)

Jake Archibald

• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 28 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Broken references in Service Workers Nightly (Issue #1669) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 February)
• [whatwg/fetch] Exporting terms for service worker spec (PR #1608) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 15 February)
• Re: [whatwg/webidl] Make [SameObject] beneficial (#212) (Wednesday, 15 February)
• Re: [whatwg/webidl] Make [SameObject] beneficial (#212) (Wednesday, 15 February)
• Re: [w3c/ServiceWorker] Skip service worker no-op fetch handler (Issue #1671) (Monday, 13 February)
• Re: [w3c/ServiceWorker] ServiceWorker fetch fast-path (Issue #1670) (Monday, 13 February)
• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) (Saturday, 11 February)
• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) (Friday, 10 February)
• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) (Friday, 10 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Thursday, 9 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Thursday, 9 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Wednesday, 8 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Tuesday, 7 February)

James M Snell

• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Saturday, 4 February)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Wednesday, 1 February)

Jamieson Roberts

• Re: [whatwg/url] Proposal: Functional chaining on URLSearchParams (Issue #756) (Friday, 24 February)
• [whatwg/url] Proposal: Functional chaining on URLSearchParams (Issue #756) (Thursday, 23 February)

Jan-Ivar Bruaroey

• Re: [w3c/permissions] Add another permission state "positive" or "granted last time"? (Issue #414) (Tuesday, 14 February)
• [w3c/permissions] Add another permission state "positive" or "granted last time"? (Issue #414) (Monday, 6 February)

Jay

• Re: [w3c/manifest] Transparent Bottom Navigation Bar (#804) (Wednesday, 8 February)

Jeffrey Yasskin

• Re: [w3c/permissions] Add a hook for implicitly granting or denying before requesting permission to use (Issue #413) (Wednesday, 8 February)

Jerry Green

• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 2 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 2 February)

Jimmy Wärting

• Re: [w3c/ServiceWorker] ServiceWorker lifetime and respondWith() with a user-constructed ReadableStream (#882) (Saturday, 25 February)
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Monday, 6 February)
• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Monday, 6 February)
• Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Saturday, 4 February)
• Re: [w3c/push-api] userVisibleOnly should be standardized to match browser behaviour (#313) (Thursday, 2 February)
• Re: [w3c/ServiceWorker] Spec how extendable events are given time to execute (#1566) (Wednesday, 1 February)

Joe Pea

• Re: [WICG/webcomponents] custom pseudo elements like ::before ::after, but using custom elements (Issue #983) (Thursday, 23 February)
• Re: [WICG/webcomponents] custom pseudo elements like ::before ::after, but using custom elements (Issue #983) (Monday, 20 February)
• Re: [WICG/webcomponents] custom pseudo elements like ::before ::after, but using custom elements (Issue #983) (Monday, 13 February)
• [WICG/webcomponents] custom pseudo elements like ::before ::after, but using custom elements (Issue #983) (Monday, 13 February)

Joey Arhar

• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Wednesday, 15 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Specify behavior of popovers with fullscreen API (Issue #216) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204) (Tuesday, 14 February)
• Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204) (Tuesday, 14 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 10 February)

Johann Hofmann

• Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Thursday, 23 February)
• Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808) (Wednesday, 22 February)
• [whatwg/url] Fix reference to resolve a blob URL (PR #751) (Wednesday, 8 February)
• Re: [w3c/FileAPI] Update the exported text for resolve (PR #191) (Monday, 6 February)
• Re: [w3c/FileAPI] Update the exported text for resolve (PR #191) (Monday, 6 February)
• Re: [w3c/FileAPI] Update the exported text for resolve (PR #191) (Monday, 6 February)
• Re: [w3c/FileAPI] Don't export "resolve" (Issue #190) (Monday, 6 February)
• [w3c/FileAPI] Update the exported text for resolve (PR #191) (Friday, 3 February)
• Re: [w3c/FileAPI] Don't export "resolve" (Issue #190) (Friday, 3 February)
• [w3c/FileAPI] Don't export "resolve" (Issue #190) (Friday, 3 February)
• [w3c/permissions] Allow for implicitly denied / implicitly granted more explicitly (Issue #413) (Friday, 3 February)

Johannes Wilm

• Re: [w3c/editing] Proposal: compositionborder attribute (Issue #414) (Thursday, 9 February)
• Re: [w3c/editing] Status of specs we are working on (Issue #413) (Thursday, 9 February)
• Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Thursday, 9 February)
• Re: [w3c/editing] Status of specs we are working on (Issue #413) (Thursday, 9 February)
• Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Thursday, 9 February)

Joshua Bell

• Re: [w3c/IndexedDB] Editorial: Link fixes/simplifications (PR #395) (Friday, 10 February)
• Re: [w3c/IndexedDB] 2 (Issue #396) (Thursday, 9 February)
• Re: [w3c/IndexedDB] Editorial: Link fixes/simplifications (PR #395) (Monday, 6 February)
• Re: [w3c/IndexedDB] Editorial: Link fixes/simplifications (PR #395) (Monday, 6 February)
• [w3c/IndexedDB] Editorial: Link fixes/simplifications (PR #395) (Monday, 6 February)

JR Conlin

• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Monday, 6 February)

jub0bs

• Re: [whatwg/fetch] If a resource allows credentials but omits Vary, shouldn't responses to non-CORS requests also contain Access-Control-Allow-Credentials? (Issue #1601) (Tuesday, 7 February)
• Re: [whatwg/fetch] If a resource allows credentials but omits Vary, shouldn't responses to non-CORS requests also contain Access-Control-Allow-Credentials? (Issue #1601) (Tuesday, 7 February)
• [whatwg/fetch] If a resource allows credentials but omits Vary, shouldn't response to non-CORS requests also contain ACAC? (Issue #1601) (Thursday, 2 February)

Jun

• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Friday, 24 February)
• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Thursday, 23 February)
• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Monday, 13 February)
• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Monday, 13 February)
• Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Friday, 10 February)
• [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Friday, 10 February)

Justin Fagnani

• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 24 February)

Kagami Sascha Rosylight

• [whatwg/streams] Why resolve backpressurePromise by an error message in SetUpCrossRealmTransformWritable? (Issue #1260) (Friday, 24 February)
• [whatwg/streams] Should cancelation error from UnderlyingSource be transferred too? (Issue #1259) (Friday, 24 February)
• Re: [whatwg/fetch] The fetch pull algorithm does not pass proper bytesWritten to ReadableByteStreamControllerRespond (Issue #1610) (Wednesday, 22 February)
• Re: [whatwg/fetch] The fetch pull algorithm does not pass proper bytesWritten to ReadableByteStreamControllerRespond (Issue #1610) (Tuesday, 21 February)
• [whatwg/fetch] The fetch pull algorithm does not pass proper bytesWritten to ReadableByteStreamControllerRespond (Issue #1610) (Tuesday, 21 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 20 February)
• Re: [whatwg/streams] Should terminating a worker close/error streams? (Issue #1256) (Saturday, 18 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 17 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 17 February)
• [whatwg/streams] Should terminating a worker close/error streams? (Issue #1256) (Friday, 17 February)
• Re: [w3c/FileAPI] Byte stream support for `stream()`? (Issue #186) (Friday, 17 February)
• Re: [w3c/FileAPI] Return a byte stream from "get stream" algorithm (PR #188) (Friday, 17 February)
• Re: [w3c/FileAPI] Return a byte stream from "get stream" algorithm (PR #188) (Friday, 17 February)
• Re: [whatwg/fetch] CI test (PR #1605) (Thursday, 16 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Thursday, 16 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Thursday, 16 February)
• Re: [whatwg/fetch] CI test (PR #1605) (Thursday, 16 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Thursday, 16 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Thursday, 16 February)
• Re: [whatwg/fetch] CI test (PR #1605) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Wednesday, 15 February)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 6 February)
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Saturday, 4 February)
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Saturday, 4 February)
• Re: [w3c/FileAPI] Update the exported text for resolve (PR #191) (Friday, 3 February)
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Thursday, 2 February)

Karl

• Re: [whatwg/url] Allow `[` and `]` as URL code-points (Issue #753) (Thursday, 23 February)
• [whatwg/url] Allow `[` and `]` as URL code-points (Issue #753) (Saturday, 11 February)

Karl Horky

• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Saturday, 18 February)

Keith Cirkel

• Re: [whatwg/dom] Allow subclassing of AbortController / AbortSignal (Issue #1162) (Wednesday, 15 February)
• Re: [whatwg/dom] Allow subclassing of AbortController / AbortSignal (Issue #1162) (Wednesday, 15 February)
• [whatwg/dom] Allow subclassing of AbortController / AbortSignal (Issue #1162) (Wednesday, 15 February)

Kenton Varda

• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Wednesday, 1 February)

Kevin McNee

• Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721) (Monday, 13 February)

Kieran Pilkington

• Re: [whatwg/fetch] Cannot get next URL for redirect="manual" (#763) (Wednesday, 15 February)

Kingmoohaa

• [w3c/IndexedDB] 2 (Issue #396) (Thursday, 9 February)

Koji Ishii

• [w3ctag/design-reviews] text-wrap: balance (Issue #822) (Tuesday, 28 February)

Lea Verou

• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Tuesday, 28 February)
• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Monday, 27 February)
• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Monday, 27 February)
• [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Monday, 27 February)
• Re: [w3ctag/design-reviews] View Transitions API (Issue #748) (Monday, 20 February)
• Re: [w3ctag/design-reviews] View Transitions API (Issue #748) (Monday, 20 February)
• Re: [w3ctag/design-reviews] Exposing predefined instances of an object as static properties on the class (Discussion #817) (Thursday, 16 February)
• [w3ctag/design-reviews] Exposing predefined instances of an object as static properties on the class (Discussion #817) (Wednesday, 15 February)
• Re: [w3ctag/design-reviews] Pre-CR review: DOM Review Draft — Published 21 June 2021 (#658) (Thursday, 9 February)
• Re: [w3ctag/design-reviews] Pre-CR review: DOM Review Draft — Published 21 June 2021 (#658) (Thursday, 9 February)
• Re: [w3ctag/design-reviews] Pre-CR review: HTML Review Draft — Published 18 January 2021 (#657) (Thursday, 9 February)
• Re: [w3ctag/design-reviews] FYI - Add optional `submitter` parameter to the `FormData` constructor (Issue #812) (Tuesday, 7 February)
• Re: [w3ctag/design-reviews] FYI - Add optional `submitter` parameter to the `FormData` constructor (Issue #812) (Tuesday, 7 February)

Luca Casonato

• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Saturday, 4 February)
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Saturday, 4 February)
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Wednesday, 1 February)
• [whatwg/streams] Add maxByteLength option to "read all bytes" algo (PR #1254) (Wednesday, 1 February)
• [whatwg/fetch] Add maxByteLength option to Body consume utilities (PR #1600) (Wednesday, 1 February)

Magajian121

• [whatwg/dom] Ttt (Issue #1155) (Thursday, 9 February)

Marco Colli

• Re: [w3c/push-api] userVisibleOnly should be standardized to match browser behaviour (#313) (Wednesday, 1 February)

Marcos Cáceres

• Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034) (Tuesday, 28 February)
• Re: [w3c/gamepad] Restrict getGamepads() to [SecureContext] (#113) (Monday, 27 February)
• Re: [WICG/webcomponents] Is this still an "incubation"? (Issue #984) (Tuesday, 21 February)
• [WICG/webcomponents] Is this still an "incubation"? (Issue #984) (Tuesday, 21 February)
• Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Friday, 17 February)
• Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Friday, 17 February)
• Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Friday, 17 February)
• Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Friday, 17 February)
• Re: [w3c/manifest] First pass as adding a Client Hint for Display Mode (#977) (Thursday, 16 February)
• Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034) (Thursday, 16 February)
• Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039) (Thursday, 16 February)
• [w3c/screen-orientation] Screen orientation change need to queue a task to fire an event properly (Issue #244) (Wednesday, 15 February)
• Re: [w3c/screen-orientation] Should hidden documents be allowed to change the orientation? (Issue #221) (Wednesday, 15 February)
• Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Wednesday, 15 February)
• Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Wednesday, 15 February)
• Re: [w3c/screen-orientation] Tidied up document using tidy-html5 (PR #242) (Wednesday, 15 February)
• [w3c/screen-orientation] Monitoring for preconditions (and fully unlocking) (Issue #243) (Wednesday, 15 February)
• [w3c/screen-orientation] Tidied up document using tidy-html5 (PR #242) (Wednesday, 15 February)
• Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Wednesday, 15 February)
• Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Wednesday, 15 February)
• Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Monday, 13 February)
• Re: [w3c/IndexedDB] Editorial: Link fixes/simplifications (PR #395) (Friday, 10 February)
• Re: [w3c/gamepad] Editorial: fix broken xref (PR #184) (Friday, 10 February)
• Re: [w3c/gamepad] Editorial: fix broken xref (PR #184) (Friday, 10 February)
• [w3c/gamepad] Editorial: fix broken xref (PR #184) (Friday, 10 February)
• Re: [w3c/permissions] add accessibility considerations (PR #412) (Thursday, 9 February)
• Re: [w3c/gamepad] Specify milliseconds for duration and startDelay (PR #180) (Thursday, 9 February)
• Re: [w3c/gamepad] Specify milliseconds for duration and startDelay (PR #180) (Thursday, 9 February)
• Re: [w3c/gamepad] Make vibrationActuator nullable (PR #181) (Thursday, 9 February)
• Re: [w3c/gamepad] Make vibrationActuator nullable (PR #181) (Thursday, 9 February)
• Re: [w3c/gamepad] Update playingEffectPromise synchronously (PR #182) (Thursday, 9 February)
• Re: [w3c/gamepad] Update playingEffectPromise synchronously (PR #182) (Thursday, 9 February)
• Re: [w3c/gamepad] Update playingEffectPromise synchronously (PR #182) (Thursday, 9 February)
• Re: [w3c/uievents-key] Tasks for wide review (Issue #57) (Monday, 6 February)
• Re: [w3c/manifest] We should add a character limit to `name` and `short_name` (Issue #1070) (Monday, 6 February)

Marijn Kruisselbrink

• Re: [w3c/FileAPI] Update the exported text for resolve (PR #191) (Friday, 3 February)
• Re: [w3c/FileAPI] Don't export "resolve" (Issue #190) (Friday, 3 February)
• Re: [w3c/FileAPI] Don't export "resolve" (Issue #190) (Friday, 3 February)

Mark Davis

• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 7 February)

Mark Nottingham

• Re: [whatwg/fetch] Cache-mode and upstream Cache-Control (#722) (Tuesday, 7 February)

Mason Freed

• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Saturday, 25 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Friday, 24 February)
• Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819) (Wednesday, 22 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Wednesday, 22 February)

Matt Garrish

• [w3ctag/design-reviews] Review of DPUB-ARIA 1.1 and DPUB-AAM 1.1 (Issue #821) (Friday, 24 February)

Matt Giuca

• Re: [w3c/manifest] We should add a character limit to `name` and `short_name` (Issue #1070) (Monday, 6 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Friday, 3 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 2 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 2 February)

Matt Reynolds

• Re: [w3c/gamepad] Update playingEffectPromise synchronously (PR #182) (Friday, 10 February)
• Re: [w3c/gamepad] Shouldn't Gamepad.vibrationActuator be nullable? (Issue #178) (Friday, 10 February)
• Re: [w3c/gamepad] Make vibrationActuator nullable (PR #181) (Friday, 10 February)
• Re: [w3c/gamepad] Make vibrationActuator nullable (PR #181) (Friday, 10 February)
• Re: [w3c/gamepad] Specify that GamepadEffectParameters.startDelay is a value in milliseconds (Issue #177) (Friday, 10 February)
• Re: [w3c/gamepad] Specify milliseconds for duration and startDelay (PR #180) (Friday, 10 February)
• Re: [w3c/gamepad] Specify milliseconds for duration and startDelay (PR #180) (Friday, 10 February)
• Re: [w3c/gamepad] Update to actions/checkout@v3 (PR #183) (Friday, 10 February)
• Re: [w3c/gamepad] Update to actions/checkout@v3 (PR #183) (Friday, 10 February)
• Re: [w3c/gamepad] Editorial: fix broken xref (PR #184) (Friday, 10 February)
• Re: [w3c/gamepad] Update playingEffectPromise synchronously (PR #182) (Thursday, 9 February)
• Re: [w3c/gamepad] Update playingEffectPromise synchronously (PR #182) (Thursday, 9 February)
• [w3c/gamepad] Update to actions/checkout@v3 (PR #183) (Thursday, 9 February)
• Re: [w3c/gamepad] Specify milliseconds for duration and startDelay (PR #180) (Thursday, 9 February)
• Re: [w3c/gamepad] Specify milliseconds for duration and startDelay (PR #180) (Thursday, 9 February)
• [w3c/gamepad] Update playingEffectPromise synchronously (PR #182) (Thursday, 9 February)
• [w3c/gamepad] Make vibrationActuator nullable (PR #181) (Thursday, 9 February)
• [w3c/gamepad] Specify milliseconds for duration and startDelay (PR #180) (Thursday, 9 February)

Mattias Buelens

• Re: [whatwg/streams] Meta: make fetch() reference more precise (PR #1258) (Monday, 20 February)
• Re: [whatwg/streams] Meta: make fetch() reference more precise (PR #1258) (Monday, 20 February)
• Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Wednesday, 15 February)
• Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Wednesday, 8 February)
• Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Wednesday, 8 February)
• Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Wednesday, 8 February)

Michael Kleber

• Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Thursday, 16 February)
• Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Thursday, 9 February)

Michael McCool

• [w3ctag/design-reviews] Web of Things (WoT) Profile - Review Requested (Issue #818) (Friday, 17 February)

Mike Taylor

• Re: [w3c/permissions] Export permissions task source (PR #407) (Thursday, 9 February)
• Re: [w3c/permissions] add accessibility considerations (PR #412) (Thursday, 9 February)

Ming-Ying Chung

• Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Thursday, 16 February)

Miniontoby

• Re: [w3c/gamepad] Restrict getGamepads() to [SecureContext] (#113) (Monday, 27 February)
• Re: [w3c/gamepad] Require secure context for gamepad state and events (#120) (Sunday, 26 February)

Ms2ger

• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Wednesday, 22 February)
• [whatwg/fetch] Response static methods use null this value to specify the realm (Issue #1603) (Monday, 13 February)

Naiyer Asif

• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Tuesday, 28 February)

Nfgh0533160051

• Re: [whatwg/fetch] ESP عن تحديث NAV TMC السعودية إصدار قاعدة البيانات الحالية: M 207 0749 تحديثات قاعدة بيانات التنقل متوفرة على: قائمة طعام www.navteq.com ستحتاج إلى رقم تعريف السيارة الخاص بك عند =?U (Tuesday, 21 February)
• Re: [whatwg/fetch] ESP عن تحديث NAV TMC السعودية إصدار قاعدة البيانات الحالية: M 207 0749 تحديثات قاعدة بيانات التنقل متوفرة على: قائمة طعام www.navteq.com ستحتاج إلى رقم تعريف السيارة الخاص بك عند =?U (Tuesday, 21 February)
• Re: [whatwg/fetch] ESP عن تحديث NAV TMC السعودية إصدار قاعدة البيانات الحالية: M 207 0749 تحديثات قاعدة بيانات التنقل متوفرة على: قائمة طعام www.navteq.com ستحتاج إلى رقم تعريف السيارة الخاص بك عند =?U (Tuesday, 21 February)
• Re: [whatwg/fetch] ESP عن تحديث NAV TMC السعودية إصدار قاعدة البيانات الحالية: M 207 0749 تحديثات قاعدة بيانات التنقل متوفرة على: قائمة طعام www.navteq.com ستحتاج إلى رقم تعريف السيارة الخاص بك عند =?U (Tuesday, 21 February)
• Re: [whatwg/fetch] ESP عن تحديث NAV TMC السعودية إصدار قاعدة البيانات الحالية: M 207 0749 تحديثات قاعدة بيانات التنقل متوفرة على: قائمة طعام www.navteq.com ستحتاج إلى رقم تعريف السيارة الخاص بك عند =?U (Tuesday, 21 February)
• [whatwg/fetch] ESP عن تحديث NAV TMC السعودية إصدار قاعدة البيانات الحالية: M 207 0749 تحديثات قاعدة بيانات التنقل متوفرة على: قائمة طعام www.navteq.com ستحتاج إلى رقم تعريف السيارة الخاص بك عند =?UTF-8 (Tuesday, 21 February)

Nick Williams

• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 14 February)

Nicolas Gilbert

• Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969) (Sunday, 26 February)
• Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969) (Sunday, 26 February)

Nigel Megitt

• Re: [w3ctag/design-reviews] Review of IMSC-HRM (Issue #788) (Thursday, 9 February)

nightlyherb

• Re: [whatwg/dom] Proposal: A Range.prototype.replaceContents(...) (#837) (Tuesday, 28 February)

Nina Satragno

• [w3ctag/design-reviews] Web Authentication: Large Blob extension (Issue #820) (Tuesday, 21 February)

Noam Rosenthal

• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Monday, 27 February)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Monday, 27 February)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Thursday, 9 February)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Thursday, 9 February)
• Re: [whatwg/fetch] Process subresource link headers (PR #1409) (Wednesday, 8 February)
• Re: [whatwg/fetch] Process subresource link headers (PR #1409) (Wednesday, 8 February)
• Re: [whatwg/fetch] Process subresource link headers (PR #1409) (Wednesday, 8 February)
• Re: [whatwg/fetch] s/early-hint/early-hints/ (PR #1562) (Wednesday, 8 February)
• Re: [whatwg/fetch] Specify how/if response status code & content type are exposed for cross-origin navigations (Issue #1602) (Tuesday, 7 February)
• [whatwg/fetch] Specify how/if response status code & content type are exposed for cross-origin navigations (Issue #1602) (Tuesday, 7 February)
• Re: [whatwg/fetch] worker timing doesn't need to be TAO protected for subresources (Issue #1597) (Monday, 6 February)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 2 February)

Nolan Lawson

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Monday, 27 February)

Omar Castro

• Re: [WICG/webcomponents] custom pseudo elements like ::before ::after, but using custom elements (Issue #983) (Monday, 20 February)

Patrick H. Lauke

• Re: [w3c/touch-events] Update retargeting steps link (PR #135) (Tuesday, 7 February)

Patrick Meenan

• Re: [whatwg/fetch] Cache-mode and upstream Cache-Control (#722) (Wednesday, 8 February)
• Re: [whatwg/fetch] Cache-mode and upstream Cache-Control (#722) (Wednesday, 1 February)
• Re: [whatwg/fetch] Specify cache mode impact on request headers (Issue #1599) (Wednesday, 1 February)
• Re: [whatwg/fetch] Specify cache mode impact on request headers (Issue #1599) (Wednesday, 1 February)

Paul Mason

• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Tuesday, 28 February)

Pedro Lopez

• [whatwg/dom] JavaScript (Issue #1164) (Monday, 20 February)

Peter Linss

• Re: [w3ctag/design-reviews] Review request on `blocking=render` attribute for scripts and stylesheets (Issue #727) (Monday, 20 February)
• Re: [w3ctag/design-reviews] Review request on `blocking=render` attribute for scripts and stylesheets (Issue #727) (Monday, 20 February)
• Re: [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240) (Wednesday, 8 February)
• Re: [w3ctag/design-reviews] FedCM multi IDP support (Issue #803) (Wednesday, 8 February)
• Re: [w3ctag/design-reviews] FedCM multi IDP support (Issue #803) (Wednesday, 8 February)
• Re: [w3ctag/design-reviews] Early design review for Range API improvements (Issue #725) (Tuesday, 7 February)
• Re: [w3ctag/design-reviews] Early design review for Range API improvements (Issue #725) (Tuesday, 7 February)

Philip Jägenstedt

• Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204) (Thursday, 16 February)
• Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Saturday, 4 February)

Pierre-Yves Gérardy

• Re: [whatwg/dom] Side effects due to tree insertion or removal (script, iframe) (#808) (Wednesday, 15 February)
• Re: [whatwg/dom] Side effects due to tree insertion or removal (script, iframe) (#808) (Wednesday, 15 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Tuesday, 14 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Tuesday, 14 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 10 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Thursday, 9 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Thursday, 9 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Thursday, 9 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Thursday, 9 February)
• [whatwg/dom] DOMParser and MathML (Issue #1154) (Wednesday, 8 February)

Qing An

• Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523) (Wednesday, 22 February)

ray007

• Re: [whatwg/fetch] Cannot get next URL for redirect="manual" (#763) (Wednesday, 15 February)

Reilly Grant

• Re: [w3c/gamepad] Restrict getGamepads() to [SecureContext] (#113) (Monday, 27 February)
• Re: [w3c/gamepad] Editorial: fix broken xref (PR #184) (Friday, 10 February)
• Re: [w3c/gamepad] Update to actions/checkout@v3 (PR #183) (Thursday, 9 February)

rektide

• Re: [whatwg/fetch] HTTP/2 server push support (#51) (Wednesday, 22 February)

Rick Byers

• Re: [w3c/uievents] Consider integrating InputDeviceCapabilities (#108) (Thursday, 23 February)

Romain Petit

• Re: [whatwg/dom] Element.matches and :scope (Issue #1081) (Tuesday, 21 February)

Ryosuke Niwa

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Monday, 27 February)
• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Monday, 27 February)
• Re: [WICG/webcomponents] Chrome doesn't repaint with :last-of-type AND shadowRoot AND :host(:active) button (Issue #985) (Friday, 24 February)
• Re: [WICG/webcomponents] Chrome doesn't repaint with :last-of-type AND shadowRoot AND :host(:active) button (Issue #985) (Friday, 24 February)
• Re: [WICG/webcomponents] Is this still an "incubation"? (Issue #984) (Tuesday, 21 February)
• Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Tuesday, 14 February)
• Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Monday, 13 February)
• Re: [WICG/webcomponents] custom pseudo elements like ::before ::after, but using custom elements (Issue #983) (Monday, 13 February)
• Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Thursday, 9 February)
• Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Thursday, 9 February)
• Re: [whatwg/dom] [TAG review] Explain the difference between this.shadowRoot and this.internals.shadowRoot (Issue #1158) (Thursday, 9 February)

Sampson Crowley

• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Thursday, 9 February)

Sasha Firsov

• Re: [WICG/webcomponents] custom pseudo elements like ::before ::after, but using custom elements (Issue #983) (Monday, 13 February)

Scott Haseley

• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Tuesday, 28 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Tuesday, 28 February)
• Re: [whatwg/dom] Correct MutationObserver ownership story (PR #1160) (Wednesday, 15 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Thursday, 9 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Wednesday, 8 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Wednesday, 8 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Wednesday, 8 February)
• [whatwg/dom] Add AbortSignal.any() (PR #1152) (Tuesday, 7 February)

Seph Reed

• Re: [w3c/push-api] userVisibleOnly should be standardized to match browser behaviour (#313) (Wednesday, 1 February)

Shivani Sharma

• Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735) (Friday, 3 February)

Shunya Shishido

• [w3c/ServiceWorker] ServiceWorker fetch fast-path (Issue #1670) (Friday, 10 February)

Simon Pieters

• Re: [w3c/uievents] Wheel event groups are not defined (Issue #338) (Tuesday, 28 February)
• Re: [whatwg/fullscreen] Add pointer to HTML about top layer and inertness (#15) (Thursday, 23 February)

slaneyrw

• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Monday, 13 February)

smaug----

• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Tuesday, 28 February)
• Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Tuesday, 28 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 28 February)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 28 February)
• Re: [whatwg/fullscreen] How :fullscreen CSS pseudo class works in shadow dom? (#149) (Monday, 27 February)
• Re: [whatwg/dom] MutationObserver GC section looks bogus (Issue #1159) (Monday, 13 February)

steimelchrome

• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Wednesday, 1 February)

stoffeltje

• [whatwg/encoding] Welkom bij het Gboard-klembord. Gekopieerde tekst wordt hier opgeslagen. (Issue #301) (Saturday, 11 February)

Sylvain Bellone

• Re: [whatwg/fetch] Conditional headers presense add `Cache-Control: no-cache` by default (Issue #1604) (Tuesday, 14 February)
• [whatwg/fetch] Conditional headers presense add `Cache-Control: no-cache` by default (Issue #1604) (Tuesday, 14 February)

Tab Atkins Jr.

• Re: [whatwg/webidl] setlike.add() is meant to return the setlike. Fixes #1268 (PR #1269) (Tuesday, 28 February)
• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Tuesday, 28 February)
• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Tuesday, 28 February)
• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Wednesday, 22 February)
• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Wednesday, 22 February)
• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Tuesday, 21 February)
• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Tuesday, 21 February)
• [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Tuesday, 21 February)
• Re: [whatwg/webidl] setlike.add() is meant to return the setlike. Fixes #1268 (PR #1269) (Tuesday, 21 February)
• [whatwg/webidl] setlike.add() is meant to return the setlike. Fixes #1268 (PR #1269) (Tuesday, 21 February)
• Re: [whatwg/webidl] PR changed the setlike `add` method to return the value that was added to the setlike object instead of the object itself. Was that an accident? (Issue #1268) (Tuesday, 21 February)
• Re: [whatwg/webidl] PR changed the setlike `add` method to return the value that was added to the setlike object instead of the object itself. Was that an accident? (Issue #1268) (Friday, 17 February)
• Re: [whatwg/fetch] CI test (PR #1605) (Thursday, 16 February)
• Re: [whatwg/fetch] CI test (PR #1605) (Thursday, 16 February)
• Re: [whatwg/fetch] CI test (PR #1605) (Thursday, 16 February)
• [whatwg/webidl] `record<>` should allow the keytype to be a typedef that resolves to one of the allowed string types (Issue #1267) (Monday, 13 February)
• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Friday, 10 February)

TAMURA, Kent

• [whatwg/dom] Update createNSResolver and lookupNamespaceURI() (PR #1165) (Tuesday, 21 February)

Thayne McCombs

• Re: [whatwg/url] Allow specifying additional "special" schemes. (Issue #749) (Monday, 6 February)
• Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703) (Sunday, 5 February)
• [whatwg/url] Allow specifying additional "special" schemes. (Issue #749) (Sunday, 5 February)

Thomas Steiner

• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Saturday, 18 February)
• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Tuesday, 14 February)
• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Thursday, 2 February)

Tim Nguyen

• [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217) (Tuesday, 28 February)
• [whatwg/fullscreen] Specify behavior of popovers with fullscreen API (Issue #216) (Tuesday, 14 February)

Timothy Gu

• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Tuesday, 28 February)
• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Tuesday, 28 February)
• Re: [whatwg/webidl] setlike.add() is meant to return the setlike. Fixes #1268 (PR #1269) (Tuesday, 28 February)
• [whatwg/url] "host-missing" validation error should be a failure (Issue #757) (Thursday, 23 February)
• Re: [whatwg/webidl] Fix links, remove as many anchor definitions as possible (PR #1270) (Wednesday, 22 February)
• Re: [whatwg/webidl] Switch maplike/setlike to use infra maps and sets (PR #1138) (Thursday, 16 February)
• Re: [whatwg/url] Allow `[` and `]` as URL code-points (Issue #753) (Monday, 13 February)
• Re: [whatwg/url] meta: add Ada to pull request template (PR #752) (Wednesday, 8 February)

Todd Gifford

• [whatwg/fetch] https://github.com/whatwg/fetch/issues/new (Issue #1607) (Friday, 17 February)
• [whatwg/fetch] Issue (Issue #1606) (Friday, 17 February)

Trevor Rowbotham

• Re: [whatwg/url] Named validation errors (#502) (Monday, 20 February)

trusted217

• [whatwg/webidl] Unlock device key (Issue #1272) (Wednesday, 22 February)
• [whatwg/webidl] Unlock device key (Issue #1271) (Wednesday, 22 February)

Tushar

• Re: [whatwg/fetch] Create Rage header section in HTTP extensions section (Issue #1553) (Sunday, 5 February)

Valentin Gosu

• Re: [whatwg/url] Expose a URLHost class to JavaScript (#288) (Friday, 17 February)
• Re: [whatwg/url] Expose a URLHost class to JavaScript (#288) (Friday, 17 February)

Verekia

• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Saturday, 18 February)
• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Tuesday, 14 February)

Vincent Morneau

• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Wednesday, 1 February)

Wareesali

• [whatwg/webidl] International human (Issue #1261) (Saturday, 4 February)

Wendy Reid

• Re: [w3ctag/design-reviews] CR Snapshot Review for EPUB 3.3 (Issue #816) (Tuesday, 14 February)
• [w3ctag/design-reviews] CR Snapshot Review for EPUB 3.3 (Issue #816) (Monday, 13 February)

Westbrook Johnson

• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Monday, 27 February)
• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Monday, 27 February)
• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Thursday, 23 February)
• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Wednesday, 8 February)

WestFarmer

• Re: [whatwg/fetch] Proposal: Support GET bodies (#83) (Wednesday, 22 February)

Yagiz Nizipli

• [whatwg/url] meta: add Ada to pull request template (PR #752) (Wednesday, 8 February)
• Re: [whatwg/url] Add Ada to implementations section of readme (PR #750) (Wednesday, 8 February)
• Re: [whatwg/url] Add Ada to implementations section of readme (PR #750) (Wednesday, 8 February)
• Re: [whatwg/url] Add Ada to implementations section of readme (PR #750) (Wednesday, 8 February)
• [whatwg/url] Add Ada to implementations section of readme (PR #750) (Tuesday, 7 February)

yi-gu

• [w3ctag/design-reviews] FedCM Auto Re-authentication API (Issue #813) (Friday, 3 February)

Yoav Weiss

• Re: [WICG/webcomponents] Is this still an "incubation"? (Issue #984) (Tuesday, 21 February)
• Re: [whatwg/fetch] s/early-hint/early-hints/ (PR #1562) (Wednesday, 8 February)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 27 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 24 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 24 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 22 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 21 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 February)
• Re: [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161) (Wednesday, 15 February)
• [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161) (Wednesday, 15 February)
• [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 15 February)
• [w3ctag/design-reviews] Skip no-op service worker fetch handler (Issue #815) (Monday, 13 February)
• [w3c/ServiceWorker] Skip service worker no-op fetch handler (Issue #1671) (Monday, 13 February)

Yrobot

• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Tuesday, 28 February)
• Re: [w3c/ServiceWorker] consider register a service worker for a sandbox iframe? (#1601) (Wednesday, 15 February)

Yves Lafon

• Re: [w3ctag/design-reviews] No-Vary-Search HTTP header (Issue #797) (Monday, 13 February)
• Re: [w3ctag/design-reviews] No-Vary-Search HTTP header (Issue #797) (Monday, 13 February)
• Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523) (Monday, 13 February)
• Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Tuesday, 7 February)

Zach Inglis

• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Monday, 27 February)
• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Monday, 27 February)

Last message date: Tuesday, 28 February 2023 23:50:30 UTC