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

Aaron Leventhal

• Re: [WICG/webcomponents] Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements (Issue #1073) (Friday, 22 November)

Adam Rice

• Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326) (Friday, 29 November)
• Re: [whatwg/streams] Shouldn't WritableStreamDefaultWriter.write() reject if underlyingSink.write calls controller.error()? (Issue #1332) (Friday, 22 November)
• Re: [whatwg/streams] define semantics of {source,sink}.finally() (#636) (Friday, 8 November)

Addison Phillips

• Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Thursday, 21 November)

Alex N. Jose

• [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014) (Thursday, 14 November)

Alexander Petros

• Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785) (Wednesday, 20 November)
• Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785) (Wednesday, 13 November)
• Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785) (Wednesday, 13 November)
• [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785) (Monday, 11 November)

Alice

• Re: [WICG/webcomponents] Reference Target Tracking Issue (Issue #1086) (Thursday, 28 November)
• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) (Thursday, 28 November)
• [WICG/webcomponents] Reference Target naming (Issue #1087) (Thursday, 28 November)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Monday, 18 November)
• Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Tuesday, 5 November)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Tuesday, 5 November)

Andrea Giammarchi

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 29 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Tuesday, 26 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Saturday, 23 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Friday, 22 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 21 November)
• Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287) (Thursday, 21 November)
• Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308) (Wednesday, 20 November)
• Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308) (Tuesday, 19 November)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Sunday, 17 November)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Friday, 15 November)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 14 November)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 14 November)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Monday, 4 November)

Andreas Kling

• Re: [whatwg/dom] Browsers don't throw when using replaceChild() to replace existing doctype (Issue #1327) (Wednesday, 20 November)
• Re: [whatwg/dom] Browsers don't throw when using replaceChild() to replace existing doctype (Issue #1327) (Wednesday, 20 November)
• [whatwg/dom] Browsers don't throw when using replaceChild() to replace existing doctype (Issue #1327) (Wednesday, 20 November)
• Re: [whatwg/dom] Correct once handling for "nested" events (PR #1324) (Monday, 18 November)
• Re: [whatwg/dom] "inner invoke" of event listener with "once" doesn't mark listener as "removed" (Issue #1323) (Monday, 18 November)
• [w3c/uievents] Replace Window with WindowProxy in IDL throughout? (Issue #388) (Sunday, 17 November)
• [whatwg/dom] "inner invoke" of event listener with "once" doesn't mark listener as "removed" (Issue #1323) (Sunday, 17 November)
• [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342) (Saturday, 16 November)

Andrew Sutherland

• Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734) (Friday, 8 November)
• Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734) (Friday, 8 November)

Andrew Williams

• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Thursday, 28 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Thursday, 28 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Thursday, 28 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Thursday, 28 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Thursday, 28 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Thursday, 28 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Thursday, 28 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Wednesday, 27 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Monday, 25 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Monday, 25 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Monday, 25 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Monday, 25 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Monday, 25 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Monday, 25 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Monday, 25 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Friday, 22 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Friday, 22 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Friday, 22 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Friday, 22 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Friday, 22 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Monday, 18 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Tuesday, 12 November)

Andrii Natiahlyi

• [w3ctag/design-reviews] FYI - Web Authentication API: PublicKeyCredential’s getClientCapabilities() method (Issue #1016) (Wednesday, 20 November)

Andy Edwards

• Re: [whatwg/streams] Shouldn't WritableStreamDefaultWriter.write() reject if underlyingSink.write calls controller.error()? (Issue #1332) (Friday, 22 November)
• Re: [whatwg/streams] Shouldn't WritableStreamDefaultWriter.write() reject if underlyingSink.write calls controller.error()? (Issue #1332) (Friday, 22 November)
• [whatwg/streams] Shouldn't WritableStreamDefaultWriter.write() reject if underlyingSink.write calls controller.error()? (Issue #1332) (Thursday, 21 November)

Anne van Kesteren

• Re: [whatwg/streams] Meta: improve test coverage (PR #1334) (Saturday, 30 November)
• Re: [whatwg/url] invalid-reverse-solidus error definition has character mixed up. (Issue #772) (Friday, 29 November)
• Re: [whatwg/url] HISTORY & SECURITY: URL Parsing Differences Between Implementations Security Issues (Issue #766) (Friday, 29 November)
• Re: [whatwg/url] HISTORY & SECURITY: URL Parsing Differences Between Implementations Security Issues (Issue #766) (Friday, 29 November)
• Re: [whatwg/url] Proposal for new version of parsing spec (Issue #778) (Friday, 29 November)
• Re: [whatwg/url] Proposal for new version of parsing spec (Issue #778) (Friday, 29 November)
• Re: [whatwg/url] Enforce UTF-8 when url is given to the basic URL parser (Issue #783) (Friday, 29 November)
• Re: [whatwg/url] "valid domain" does not match validation errors in the host parser (Issue #797) (Friday, 29 November)
• Re: [whatwg/url] Should we escape \ in non-special non-opaque paths? (Issue #675) (Friday, 29 November)
• Re: [whatwg/url] Should we escape \ in non-special non-opaque paths? (Issue #675) (Friday, 29 November)
• Re: [whatwg/url] Request for review: URLPattern (#635) (Friday, 29 November)
• Re: [whatwg/url] Request for review: URLPattern (#635) (Friday, 29 November)
• Re: [whatwg/url] Issues with UTS #46 tests (#341) (Friday, 29 November)
• Re: [whatwg/url] Issues with UTS #46 tests (#341) (Friday, 29 November)
• Re: [whatwg/url] Hoist "forbidden domain code point" check into "domain to ASCII" (Issue #818) (Friday, 29 November)
• Re: [whatwg/url] Editorial: check forbidden domain code points in domain to ASCII (PR #841) (Friday, 29 November)
• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Friday, 29 November)
• Re: [whatwg/url] Set IDNA's IgnoreInvalidPunycode to false (PR #843) (Friday, 29 November)
• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Friday, 29 November)
• Re: [whatwg/url] More IDNA roundtrippability issues (Issue #760) (Friday, 29 November)
• Re: [whatwg/url] More IDNA roundtrippability issues (Issue #760) (Friday, 29 November)
• Re: [whatwg/url] IdnaTestV2.json "xn--xn--a--gua.pt" test case problem (Issue #803) (Friday, 29 November)
• Re: [whatwg/url] IdnaTestV2.json "xn--xn--a--gua.pt" test case problem (Issue #803) (Friday, 29 November)
• [whatwg/url] Set IDNA's IgnoreInvalidPunycode to false (PR #843) (Friday, 29 November)
• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Friday, 29 November)
• Re: [whatwg/url] Encourage denoting character-attributable errors by the REPLACEMENT CHARACTER (Issue #819) (Friday, 29 November)
• Re: [whatwg/url] CheckHyphens isn't set to beStrict (Issue #820) (Friday, 29 November)
• Re: [whatwg/url] CheckHyphens isn't set to beStrict (Issue #820) (Friday, 29 November)
• Re: [whatwg/url] Set IDNA's CheckHyphens to the value of beStrict (PR #842) (Friday, 29 November)
• Re: [whatwg/url] Explain why valid domain needs to run ToUnicode (Issue #817) (Friday, 29 November)
• Re: [whatwg/url] Explain why valid domain needs to run ToUnicode (Issue #817) (Friday, 29 November)
• Re: [whatwg/url] Remove redundant domain to Unicode call from valid domain (PR #840) (Friday, 29 November)
• [whatwg/url] Set IDNA's CheckHyphens to the value of beStrict (PR #842) (Friday, 29 November)
• Re: [whatwg/url] Encourage denoting character-attributable errors by the REPLACEMENT CHARACTER (Issue #819) (Friday, 29 November)
• Re: [whatwg/url] Hoist "forbidden domain code point" check into "domain to ASCII" (Issue #818) (Friday, 29 November)
• [whatwg/url] Editorial: check forbidden domain code points in domain to ASCII (PR #841) (Friday, 29 November)
• Re: [whatwg/url] Explain why valid domain needs to run ToUnicode (Issue #817) (Friday, 29 November)
• [whatwg/url] Remove redundant domain to Unicode call from valid domain (PR #840) (Friday, 29 November)
• Re: [whatwg/url] Update to Unicode 16.0.0 (Issue #836) (Friday, 29 November)
• Re: [whatwg/url] Clearly mark conformance checking-only aspects of the IDNA section (Issue #816) (Friday, 29 November)
• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Wednesday, 27 November)
• Re: [whatwg/url] Proposal: Functional chaining on URLSearchParams (Issue #756) (Tuesday, 26 November)
• Re: [whatwg/url] Proposal: Functional chaining on URLSearchParams (Issue #756) (Tuesday, 26 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Tuesday, 26 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 26 November)
• Re: [whatwg/url] "IPv6 serializer" does not define an algorithm for longest sequence of IPv6 pieces that are 0 (#321) (Tuesday, 26 November)
• Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Tuesday, 26 November)
• [whatwg/url] Formal IPv6 address definition (Issue #839) (Tuesday, 26 November)
• Re: [whatwg/url] Update to Unicode 16.0.0 (Issue #836) (Monday, 25 November)
• Re: [whatwg/dom] Missing machinery for associated Event data (Issue #1328) (Monday, 25 November)
• Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Monday, 25 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Monday, 25 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Monday, 25 November)
• Re: [whatwg/dom] Should a Range object be able to update a Selection object (#772) (Monday, 25 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Monday, 25 November)
• Re: [w3c/push-api] Meta: address xref issue (PR #394) (Monday, 25 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Monday, 25 November)
• Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Saturday, 23 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Friday, 22 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Friday, 22 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Friday, 22 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Friday, 22 November)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Friday, 22 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Thursday, 21 November)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Wednesday, 20 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Wednesday, 20 November)
• Re: [whatwg/webidl] Editorial: define boolean and integer types in terms of Infra (PR #1452) (Wednesday, 20 November)
• Re: [w3c/push-api] Declarative Web Push (Issue #360) (Tuesday, 19 November)
• [whatwg/webidl] Editorial: define boolean and integer types in terms of Infra (PR #1452) (Tuesday, 19 November)
• Re: [w3c/push-api] Meta: address xref issue (PR #394) (Tuesday, 19 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Tuesday, 19 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Tuesday, 19 November)
• [w3c/push-api] Meta: address xref issue (PR #394) (Tuesday, 19 November)
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) (Tuesday, 19 November)
• [w3c/push-api] Expose pushManager on Window (PR #393) (Tuesday, 19 November)
• Re: [w3c/push-api] Expose pushManager on Navigator (PR #368) (Tuesday, 19 November)
• Re: [w3c/push-api] Expose pushManager on Navigator (PR #368) (Tuesday, 19 November)
• Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Tuesday, 19 November)
• Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Tuesday, 19 November)
• Re: [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788) (Tuesday, 19 November)
• Re: [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788) (Tuesday, 19 November)
• Re: [whatwg/dom] Improve readability. maybe.. (PR #1326) (Tuesday, 19 November)
• Re: [whatwg/fetch] Editorial: make JSON parsing wording match Infra spec (PR #1787) (Tuesday, 19 November)
• Re: [whatwg/fetch] Editorial: make JSON parsing wording match Infra spec (PR #1787) (Tuesday, 19 November)
• Re: [whatwg/fetch] Editorial: make JSON parsing wording match Infra spec (PR #1787) (Tuesday, 19 November)
• Re: [whatwg/dom] Improve readability. maybe.. (PR #1326) (Tuesday, 19 November)
• Re: [whatwg/dom] Editorial: break from the inner invoke loop rather than returning (PR #1325) (Tuesday, 19 November)
• Re: [w3c/push-api] Expose pushManager on Navigator (PR #368) (Monday, 18 November)
• [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Monday, 18 November)
• [whatwg/dom] Editorial: break from the inner invoke loop rather than returning (PR #1325) (Monday, 18 November)
• Re: [whatwg/dom] "inner invoke" of event listener with "once" doesn't mark listener as "removed" (Issue #1323) (Monday, 18 November)
• Re: [whatwg/dom] Correct once handling for "nested" events (PR #1324) (Monday, 18 November)
• Re: [whatwg/dom] Correct once handling for "nested" events (PR #1324) (Monday, 18 November)
• [whatwg/dom] Correct once handling for "nested" events (PR #1324) (Monday, 18 November)
• Re: [whatwg/dom] "inner invoke" of event listener with "once" doesn't mark listener as "removed" (Issue #1323) (Monday, 18 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Monday, 18 November)
• Re: [whatwg/dom] "inner invoke" of event listener with "once" doesn't mark listener as "removed" (Issue #1323) (Monday, 18 November)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Friday, 15 November)
• [whatwg/fetch] HTTP/2 and Content-Length (Issue #1786) (Thursday, 14 November)
• Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Thursday, 14 November)
• Re: [w3c/push-api] Declarative Web Push (Issue #360) (Wednesday, 13 November)
• Re: [w3c/push-api] Declarative Web Push (Issue #360) (Wednesday, 13 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 13 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 13 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 13 November)
• Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Wednesday, 13 November)
• [w3c/push-api] "a service worker registration has at most one push subscription" seems wrong (Issue #392) (Tuesday, 12 November)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Tuesday, 12 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Friday, 8 November)
• Re: [whatwg/webidl] https://code.google.com (Issue #1448) (Thursday, 7 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Thursday, 7 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Thursday, 7 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Thursday, 7 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Thursday, 7 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Thursday, 7 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Wednesday, 6 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Wednesday, 6 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Wednesday, 6 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Wednesday, 6 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Wednesday, 6 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Wednesday, 6 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Tuesday, 5 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Tuesday, 5 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Tuesday, 5 November)
• Re: [whatwg/fetch] Skip localhost when evaluating HSTS upgrades (PR #1781) (Tuesday, 5 November)
• Re: [whatwg/fetch] Exclude localhost from HTTPS upgrades (Issue #1780) (Tuesday, 5 November)
• Re: [whatwg/fetch] Exclude localhost from HTTPS upgrades (Issue #1780) (Tuesday, 5 November)
• Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320) (Monday, 4 November)
• Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Monday, 4 November)
• Re: [whatwg/storage] StorageEstimate.quota + Storage Pressure (#73) (Monday, 4 November)
• Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203) (Monday, 4 November)
• Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Monday, 4 November)
• Re: [whatwg/xhr] `FormData` `has()` should include a second param for matching the value like `URLSearchParams` (Issue #392) (Sunday, 3 November)

Anonyme2900

• Re: [w3c/ServiceWorker] > Wanted to start adding the changed/added guidelines, SC and sections to a list here to help the AG WG know what sections are ready to review. This will be a draft PR until we are ready to send the document to the AG WG for their first review. See [Issue #65]. (Issue #1736) (Thursday, 14 November)
• [w3c/ServiceWorker] > Wanted to start adding the changed/added guidelines, SC and sections to a list here to help the AG WG know what sections are ready to review. This will be a draft PR until we are ready to send the document to the AG WG for their first review. See [Issue #65]. (Issue #1736) (Thursday, 14 November)

Belhassen Gharsallah

• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Sunday, 3 November)

Ben Francis

• Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784) (Wednesday, 13 November)
• Re: [w3c/manifest] Manifest processing should not be a function of document URL (#668) (Friday, 8 November)

Bradley Needham

• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 14 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 14 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 14 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 14 November)

bRADLEYALANS30

• [whatwg/webidl] Enumeration Emulator (Issue #1450) (Tuesday, 12 November)

Christian Liebel

• Re: [w3c/manifest] Link incubations (PR #1153) (Friday, 22 November)
• Re: [w3c/manifest] Link incubations (PR #1153) (Friday, 22 November)
• [w3c/manifest] Link incubations (PR #1153) (Wednesday, 13 November)
• Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784) (Wednesday, 13 November)
• Re: [w3c/manifest] Clarification needed for document URL (Issue #1147) (Saturday, 9 November)
• Re: [w3c/manifest] Add protocol handlers to the explainer and spec (#863) (Thursday, 7 November)
• Re: [w3c/manifest] Add protocol handlers to the explainer and spec (#863) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] Clarify case-insensitive parsing for enum values (Issue #1142) (Thursday, 7 November)
• Re: [w3c/manifest] Make enums case-insensitive (PR #1149) (Thursday, 7 November)
• Re: [w3c/manifest] Make enums case-insensitive (PR #1149) (Thursday, 7 November)
• Re: [w3c/manifest] related_applications is single engine feature (#956) (Thursday, 7 November)
• Re: [w3c/manifest] prefer_related_applications is single engine feature (#957) (Thursday, 7 November)
• Re: [w3c/manifest] Move `prefer_related_applications` and `related_applications` to manifest incubation (PR #1152) (Thursday, 7 November)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Monday, 4 November)
• Re: [w3c/manifest] related_applications is single engine feature (#956) (Friday, 1 November)
• [w3c/manifest] Move `prefer_related_applications` and `related_applications` to manifest incubation (PR #1152) (Friday, 1 November)

Christian Stewart

• Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224) (Saturday, 23 November)

Claudia Meadows

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Sunday, 24 November)
• Re: [whatwg/dom] Selecting Events with Style (Issue #1233) (Friday, 22 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 21 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 21 November)

Dan Clark

• Re: [WICG/webcomponents] Reference Target Tracking Issue (Issue #1086) (Wednesday, 27 November)
• [WICG/webcomponents] Reference Target Tracking Issue (Issue #1086) (Wednesday, 27 November)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Friday, 1 November)

Daniel Appelquist

• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) (Thursday, 21 November)
• Re: [w3ctag/design-reviews] Early review request for "Explicit JavaScript Compile Hints" (Issue #947) (Wednesday, 13 November)
• Re: [w3ctag/design-reviews] Early review request for "Explicit JavaScript Compile Hints" (Issue #947) (Wednesday, 13 November)
• Re: [w3ctag/design-reviews] Early Design Review: Partitioned Popins (Issue #956) (Monday, 11 November)

Daniel Ethridge

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Saturday, 23 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Saturday, 23 November)

Daniel Murphy

• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Thursday, 21 November)
• Re: [w3c/manifest] Link incubations (PR #1153) (Thursday, 21 November)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Wednesday, 20 November)

Dapeng(Max) Liu

• Re: [w3ctag/design-reviews] Web Authentication's PublicKeyCredential signal methods (Issue #996) (Wednesday, 13 November)

David A

• Re: [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011) (Friday, 8 November)
• [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011) (Tuesday, 5 November)

David Benjamin

• Re: [whatwg/fetch] Define HSTS as "internal" redirect (Issue #1426) (Tuesday, 26 November)
• [whatwg/fetch] HTTPS-RR upgrades are in the wrong place (Issue #1789) (Tuesday, 26 November)

Di Zhang

• Re: [whatwg/dom] Should a Range object be able to update a Selection object (#772) (Wednesday, 27 November)
• Re: [whatwg/dom] Should a Range object be able to update a Selection object (#772) (Thursday, 21 November)
• Re: [w3ctag/design-reviews] CSS reading-flow property (Issue #978) (Thursday, 21 November)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Thursday, 21 November)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Tuesday, 19 November)
• Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168) (Thursday, 14 November)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Thursday, 14 November)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Thursday, 14 November)
• Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168) (Tuesday, 12 November)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Tuesday, 12 November)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Tuesday, 12 November)
• Re: [w3ctag/design-reviews] CSS reading-flow property (Issue #978) (Wednesday, 6 November)

Dietrich Ayala

• [w3c/ServiceWorker] Feedback on the ServiceWorker feature in the web-platform-dx/web-features project (Issue #1738) (Thursday, 28 November)

Dipika Bhattacharya

• Re: [w3c/manifest] Clarification needed for document URL (Issue #1147) (Thursday, 14 November)
• Re: [w3c/manifest] Clarification needed for document URL (Issue #1147) (Thursday, 14 November)
• Re: [w3c/manifest] Clarification needed for document URL (Issue #1147) (Tuesday, 5 November)

Domenic Denicola

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 29 November)
• Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326) (Friday, 29 November)
• Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326) (Thursday, 28 November)
• Re: [whatwg/streams] `.throw()`ing an async iterator (Issue #1284) (Wednesday, 27 November)
• Re: [whatwg/streams] `.throw()`ing an async iterator (Issue #1284) (Wednesday, 27 November)
• Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326) (Wednesday, 27 November)
• Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331) (Wednesday, 27 November)
• Re: [whatwg/streams] Fix attempting to get the chunk size after strategy is cleared (PR #1333) (Wednesday, 27 November)
• [whatwg/streams] Fix attempting to get the chunk size after strategy is cleared (PR #1333) (Tuesday, 26 November)
• Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331) (Tuesday, 26 November)
• Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Tuesday, 26 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Friday, 22 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Friday, 22 November)
• Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Friday, 22 November)
• Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331) (Friday, 22 November)
• Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331) (Thursday, 21 November)
• Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Thursday, 21 November)
• Re: [whatwg/webidl] Editorial: define boolean and integer types in terms of Infra (PR #1452) (Wednesday, 20 November)
• Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Wednesday, 20 November)
• Re: [whatwg/dom] Editorial: break from the inner invoke loop rather than returning (PR #1325) (Tuesday, 19 November)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Friday, 1 November)

Dominic Farolino

• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 27 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 27 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 27 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 27 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 27 November)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Friday, 22 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 21 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 21 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 20 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 20 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 20 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 20 November)
• Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight for navigations (PR #1785) (Wednesday, 20 November)
• Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785) (Tuesday, 19 November)
• Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785) (Tuesday, 19 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 19 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 19 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 13 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 13 November)
• Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785) (Tuesday, 12 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 12 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 12 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 12 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Monday, 11 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Monday, 11 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Monday, 11 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Monday, 11 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Monday, 11 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Sunday, 10 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Sunday, 10 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Sunday, 10 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 7 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 7 November)

Espen Hovlandsdal

• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Wednesday, 20 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Tuesday, 19 November)
• Re: [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788) (Tuesday, 19 November)
• Re: [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788) (Tuesday, 19 November)
• [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788) (Tuesday, 19 November)
• [whatwg/fetch] Editorial: make JSON parsing wording match Infra spec (PR #1787) (Tuesday, 19 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Saturday, 16 November)

Ethan Gardner

• Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308) (Friday, 15 November)

Evan Stade

• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) (Tuesday, 5 November)

fantasai

• Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003) (Tuesday, 5 November)

Frederik Held

• Re: [w3c/editing] Should we propose "::caret" pseudo-element to CSS WG? (#158) (Friday, 22 November)

Frédéric Wang

• Re: [whatwg/dom] Integration with trusted types inside of node conversion (PR #1258) (Wednesday, 6 November)

Fuqiao Xue

• Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Thursday, 14 November)
• Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Wednesday, 13 November)
• Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Wednesday, 13 November)
• [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Wednesday, 13 November)

Gabriel Brito

• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)

Gastón Rodríguez

• Re: [w3ctag/design-reviews] [Handwriting] Add Handwriting CSS Value (Issue #1018) (Wednesday, 27 November)
• [w3c/editing] Add mechanism to control enablement of handwriting (Issue #472) (Wednesday, 27 November)
• Re: [w3ctag/design-reviews] [Handwriting] Add Handwriting CSS Value (Issue #1018) (Monday, 25 November)
• [w3ctag/design-reviews] [Handwriting] Add Handwriting CSS Value (Issue #1018) (Monday, 25 November)

gima

• Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Sunday, 24 November)

github-actions[bot]

• Re: [w3c/selection-api] Tidied up document using tidy-html5 (PR #340) (Wednesday, 20 November)

helo-sky

• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Sunday, 10 November)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Sunday, 10 November)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Sunday, 10 November)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Tuesday, 5 November)

Henri Sivonen

• Re: [whatwg/url] Editorial: check forbidden domain code points in domain to ASCII (PR #841) (Friday, 29 November)
• Re: [whatwg/url] Set IDNA's IgnoreInvalidPunycode to false (PR #843) (Friday, 29 November)
• Re: [whatwg/url] Encourage denoting character-attributable errors by the REPLACEMENT CHARACTER (Issue #819) (Friday, 29 November)
• Re: [whatwg/url] Encourage denoting character-attributable errors by the REPLACEMENT CHARACTER (Issue #819) (Friday, 29 November)
• Re: [whatwg/url] Set IDNA's CheckHyphens to the value of beStrict (PR #842) (Friday, 29 November)
• Re: [whatwg/url] Explain why valid domain needs to run ToUnicode (Issue #817) (Friday, 29 November)
• Re: [whatwg/url] Remove redundant domain to Unicode call from valid domain (PR #840) (Friday, 29 November)
• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Thursday, 28 November)
• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Thursday, 28 November)
• Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Wednesday, 13 November)

hiroshige-g

• Re: [w3c/ServiceWorker] active service worker should be reset for same-origin redirects during navigation (Issue #1735) (Monday, 4 November)
• [w3c/ServiceWorker] active service worker should be reset for same-origin redirects during navigation (Issue #1735) (Monday, 4 November)

intimate6degree

• [whatwg/webidl] https://code.google.com (Issue #1448) (Thursday, 7 November)

Isaac King

• [w3c/uievents] Mandate a minimum dispatch frequency for continuous UI input events (Issue #389) (Friday, 29 November)
• [w3c/pointerlock] Allow applications to access higher-precision mouse movement data (Issue #102) (Thursday, 28 November)

Isaiah Inuwa

• Re: [w3c/manifest] related_applications is single engine feature (#956) (Friday, 1 November)

Jake Archibald

• Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320) (Tuesday, 5 November)
• Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320) (Tuesday, 5 November)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 4 November)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 4 November)

Jamie Mansfield

• Re: [w3c/uievents] Replace Window with WindowProxy in IDL throughout? (Issue #388) (Monday, 18 November)

Jeffrey Yasskin

• Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975) (Saturday, 30 November)
• [w3c/clipboard-apis] Add privacy considerations for the clipboardchange event (Issue #230) (Wednesday, 27 November)
• Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975) (Wednesday, 27 November)
• Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975) (Wednesday, 27 November)
• Re: [w3ctag/design-reviews] [Handwriting] Add Handwriting CSS Value (Issue #1018) (Tuesday, 26 November)
• Re: [w3ctag/design-reviews] [Handwriting] Add Handwriting CSS Value (Issue #1018) (Monday, 25 November)
• Re: [w3ctag/design-reviews] Vision for W3C: request horizontal architectural review and wide TAG review (Issue #1008) (Friday, 22 November)
• Re: [w3ctag/design-reviews] DOM state-preserving move (Issue #976) (Thursday, 21 November)
• Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003) (Thursday, 21 November)
• Re: [w3ctag/design-reviews] Review for Protected Audiences Bidding and Auction Services API (Issue #1009) (Thursday, 21 November)
• Re: [w3ctag/design-reviews] Web Install API - Cross-Origin (Issue #946) (Wednesday, 20 November)
• Re: [w3ctag/design-reviews] Web Install API - Cross-Origin (Issue #946) (Wednesday, 20 November)
• Re: [w3ctag/design-reviews] Review for Protected Audiences Bidding and Auction Services API (Issue #1009) (Wednesday, 20 November)
• Re: [w3ctag/design-reviews] Review for Protected Audiences Bidding and Auction Services API (Issue #1009) (Wednesday, 20 November)
• Re: [w3ctag/design-reviews] Customizable select element (Issue #1007) (Wednesday, 20 November)
• Re: [w3ctag/design-reviews] Customizable select element (Issue #1007) (Wednesday, 20 November)
• Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003) (Wednesday, 20 November)
• Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003) (Wednesday, 20 November)
• Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994) (Thursday, 14 November)
• Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994) (Thursday, 14 November)
• Re: [w3ctag/design-reviews] Web Authentication's PublicKeyCredential signal methods (Issue #996) (Wednesday, 13 November)
• Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994) (Tuesday, 12 November)
• Re: [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011) (Tuesday, 12 November)
• Re: [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011) (Tuesday, 12 November)
• Re: [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011) (Saturday, 9 November)
• Re: [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011) (Wednesday, 6 November)
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) (Monday, 4 November)
• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Monday, 4 November)
• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Monday, 4 November)
• Re: [w3ctag/design-reviews] Review for Protected Audiences Bidding and Auction Services API (Issue #1009) (Monday, 4 November)

jimmyfrasche

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 4 November)

Joejoshara

• Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Sunday, 3 November)

Johann Hofmann

• Re: [w3ctag/design-reviews] Early Design Review: Partitioned Popins (Issue #956) (Friday, 22 November)

Johannes Wilm

• Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468) (Thursday, 14 November)

Jon Nyman

• Re: [w3c/ServiceWorker] Expose the Fetch Metadata Request Headers (#1513) (Tuesday, 5 November)

Josh Soref

• Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203) (Thursday, 7 November)
• [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203) (Friday, 1 November)

Joshua Bell

• [w3c/IndexedDB] Return explicit failure from object store retrieval operations (Issue #432) (Thursday, 7 November)
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) (Tuesday, 5 November)

JR Conlin

• Re: [w3c/push-api] Declarative Web Push (Issue #360) (Wednesday, 13 November)
• Re: [w3c/push-api] Declarative Web Push (Issue #360) (Wednesday, 13 November)

Juan5212

• [whatwg/webidl] MP4Box (Issue #1449) (Saturday, 9 November)

Julian Reschke

• Re: [whatwg/fetch] Can the set of safelisted methods be extended? (Issue #1774) (Wednesday, 13 November)

Junhui He

• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Tuesday, 26 November)
• [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Friday, 15 November)

Justin Fagnani

• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Saturday, 2 November)
• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Friday, 1 November)

Justin Grote

• Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Sunday, 24 November)

Kagami Sascha Rosylight

• Re: [w3c/push-api] Expose pushManager on Window (PR #393) (Tuesday, 19 November)
• Re: [w3c/push-api] Meta: address xref issue (PR #394) (Tuesday, 19 November)

Keith Cirkel

• Re: [WICG/webcomponents] Reference Target: How to handle invalid ID references? (Issue #1071) (Wednesday, 27 November)
• [whatwg/dom] Missing machinery for associated Event data (Issue #1328) (Monday, 25 November)
• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Friday, 8 November)
• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Monday, 4 November)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 4 November)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 4 November)
• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Monday, 4 November)

L. David Baron

• Re: [w3ctag/design-reviews] CSS advanced attr() function (#513) (Thursday, 14 November)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Friday, 1 November)

lattaai6

• Re: [w3c/push-api] "a service worker registration has at most one push subscription" seems wrong (Issue #392) (Tuesday, 12 November)

Lea Verou

• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Monday, 11 November)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Tuesday, 5 November)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Tuesday, 5 November)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Tuesday, 5 November)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 4 November)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 4 November)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 4 November)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Saturday, 2 November)
• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) (Friday, 1 November)

Lu

• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) (Thursday, 14 November)

Luca Casonato

• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Tuesday, 26 November)

Lucas Pardue

• Re: [whatwg/fetch] HTTP/2 and Content-Length (Issue #1786) (Thursday, 14 November)

Léonie Watson

• Re: [w3c/uievents-key] CFC to publish UI Events KeyboardEvent key Values as a Proposed Recommendation in the WebApps WG (Issue #68) (Tuesday, 5 November)
• Re: [w3c/uievents-key] CFC to publish UI Events KeyboardEvent key Values as a Proposed Recommendation in the WebApps WG (Issue #68) (Tuesday, 5 November)
• Re: [w3c/uievents-code] CFC to publish UI Events KeyboardEvent code Values as a Proposed Recommendation in the WebApps WG (Issue #43) (Tuesday, 5 November)
• Re: [w3c/uievents-code] CFC to publish UI Events KeyboardEvent code Values as a Proposed Recommendation in the WebApps WG (Issue #43) (Tuesday, 5 November)

Manu Sporny

• Re: [w3ctag/design-reviews] Controller Documents v1.0 (Issue #960) (Saturday, 16 November)

Marcelo Volmaro

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)

Marcos Cáceres

• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Thursday, 21 November)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Thursday, 21 November)
• Re: [w3c/manifest] Link incubations (PR #1153) (Thursday, 21 November)
• Re: [w3c/manifest] Link incubations (PR #1153) (Thursday, 21 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 15 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Thursday, 7 November)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Thursday, 7 November)
• Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784) (Thursday, 7 November)
• Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784) (Thursday, 7 November)
• Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784) (Thursday, 7 November)
• Re: [w3c/manifest] Require document to be in scope to be styled by the manifest (#791) (Thursday, 7 November)
• Re: [w3c/manifest] Require document to be in scope to be styled by the manifest (#791) (Thursday, 7 November)
• Re: [w3c/manifest] First pass as adding a Client Hint for Display Mode (#977) (Thursday, 7 November)
• Re: [w3c/manifest] First pass as adding a Client Hint for Display Mode (#977) (Thursday, 7 November)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 7 November)
• Re: [w3c/manifest] What theme color should be used when a PWA window is out of scope? (#755) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 7 November)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Thursday, 7 November)
• Re: [w3c/manifest] Move `prefer_related_applications` and `related_applications` to manifest incubation (PR #1152) (Thursday, 7 November)
• Re: [w3c/manifest] Make enums case-insensitive (PR #1149) (Thursday, 7 November)

Marcos Del Sol Vives

• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Friday, 29 November)
• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Thursday, 28 November)
• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Wednesday, 27 November)
• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Wednesday, 27 November)
• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Tuesday, 26 November)

Marijn Kruisselbrink

• Re: [w3c/FileAPI] Update auto-publish.yml (PR #204) (Friday, 22 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Friday, 22 November)
• [w3c/FileAPI] Update auto-publish.yml (PR #204) (Friday, 22 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Wednesday, 20 November)
• Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203) (Wednesday, 6 November)

Mark Davis

• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Tuesday, 26 November)

Markus Scherer

• Re: [whatwg/url] Update to Unicode 16.0.0 (Issue #836) (Tuesday, 26 November)

Martin Thomson

• Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975) (Wednesday, 27 November)
• Re: [w3ctag/design-reviews] Element Capture (Issue #954) (Thursday, 14 November)

Matt Giuca

• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Monday, 11 November)

Matthew Tylee Atkinson

• Re: [w3ctag/design-reviews] Accessibility conformance Testing (ACT) Rules Format 1.1 (Issue #977) (Monday, 25 November)
• Re: [w3ctag/design-reviews] CSS reading-flow property (Issue #978) (Wednesday, 20 November)
• Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962) (Wednesday, 20 November)
• Re: [w3ctag/design-reviews] Element Capture (Issue #954) (Tuesday, 19 November)
• Re: [w3ctag/design-reviews] Element Capture (Issue #954) (Tuesday, 19 November)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Monday, 18 November)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Monday, 18 November)
• Re: [w3ctag/design-reviews] CSS reading-flow property (Issue #978) (Wednesday, 6 November)

Mattias Buelens

• Re: [whatwg/streams] Meta: improve test coverage (PR #1334) (Friday, 29 November)
• [whatwg/streams] Meta: improve test coverage (PR #1334) (Friday, 29 November)
• Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326) (Wednesday, 27 November)
• Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326) (Wednesday, 27 November)
• Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326) (Wednesday, 27 November)
• Re: [whatwg/streams] Fix attempting to get the chunk size after strategy is cleared (PR #1333) (Tuesday, 26 November)

meacer

• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 26 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 26 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 26 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 26 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 26 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Monday, 18 November)

Meghan Denny

• Re: [whatwg/webidl] 0327482776 (Issue #1453) (Tuesday, 26 November)
• Re: [whatwg/webidl] Enumeration Emulator (Issue #1450) (Tuesday, 12 November)
• Re: [whatwg/fetch] SSTTATUS (Issue #1784) (Saturday, 9 November)
• Re: [whatwg/url] metro (Issue #837) (Saturday, 9 November)
• Re: [whatwg/webidl] MP4Box (Issue #1449) (Saturday, 9 November)

Michael Rochelle

• Re: [WICG/webcomponents] Why can't the registry enumerate the custom elements? (#775) (Tuesday, 12 November)

Michal Mocny

• Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308) (Wednesday, 20 November)
• Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308) (Wednesday, 20 November)

Mike Taylor

• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Friday, 22 November)
• Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Wednesday, 13 November)

Ming-Ying Chung

• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Friday, 29 November)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Friday, 29 November)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Friday, 29 November)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Friday, 29 November)
• Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Tuesday, 12 November)

Ms2ger

• Re: [whatwg/dom] Use the principal realm to initialize Event.timeStamp (PR #1329) (Wednesday, 27 November)
• [whatwg/dom] Use the principal realm to initialize Event.timeStamp (PR #1329) (Wednesday, 27 November)
• Re: [whatwg/webidl] Update to HTML changes for ShadowRealms (PR #1437) (Friday, 15 November)

Munira

• Re: [w3ctag/design-reviews] CSS advanced attr() function (#513) (Thursday, 14 November)

Nathan Knowler

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 4 November)
• [whatwg/xhr] `FormData` `has()` should include a second param for matching the value like `URLSearchParams` (Issue #392) (Saturday, 2 November)

Ndrasana998

• Re: [whatwg/webidl] 0327482776 (Issue #1453) (Monday, 25 November)
• Re: [whatwg/webidl] 0327482776 (Issue #1453) (Monday, 25 November)
• Re: [whatwg/webidl] 0327482776 (Issue #1453) (Monday, 25 November)
• Re: [whatwg/webidl] 0327482776 (Issue #1453) (Monday, 25 November)
• Re: [whatwg/webidl] 0327482776 (Issue #1453) (Monday, 25 November)
• [whatwg/webidl] 0327482776 (Issue #1453) (Monday, 25 November)

Nidhi Jaju

• Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326) (Friday, 29 November)

Noam Rosenthal

• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 27 November)
• Re: [w3ctag/design-reviews] DOM state-preserving move (Issue #976) (Wednesday, 27 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 21 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 21 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 21 November)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 20 November)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 20 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 13 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 13 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 12 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 12 November)
• [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013) (Tuesday, 12 November)
• [w3ctag/design-reviews] User-defined script "entry points" for performance timing (Issue #1012) (Wednesday, 6 November)

Nolan Lawson

• Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224) (Saturday, 23 November)

Patrick McDougle

• Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287) (Wednesday, 20 November)

Peter Linss

• Re: [w3ctag/design-reviews] CSS :open pseudo-class (Issue #1010) (Wednesday, 13 November)
• Re: [w3ctag/design-reviews] CSS :open pseudo-class (Issue #1010) (Wednesday, 13 November)

Rimas Misevičius

• Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Wednesday, 27 November)
• Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Saturday, 23 November)
• Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838) (Friday, 22 November)

Rob Eisenberg

• Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Friday, 22 November)
• [WICG/webcomponents] Update reference-target-explainer supported attributes (PR #1084) (Thursday, 21 November)

Romain Lebesle

• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Friday, 15 November)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 14 November)

roraja

• [w3ctag/design-reviews] ClipboardChange event API (Issue #1017) (Friday, 22 November)

Ryosuke Niwa

• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) (Thursday, 28 November)
• Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Friday, 22 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] CustomElementRegistry to support SDLC of generic browser entities (Issue #976) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] CustomElementRegistry to support SDLC of generic browser entities (Issue #976) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Moving elements with shadow roots between documents (#907) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Moving elements with shadow roots between documents (#907) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] How does customElements.upgrade() work? (Issue #1001) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] How does customElements.upgrade() work? (Issue #1001) (Thursday, 21 November)
• Re: [WICG/webcomponents] Idea: Alternative Ways to Control Registry Scoping (Issue #1058) (Thursday, 21 November)
• Re: [WICG/webcomponents] Idea: Alternative Ways to Control Registry Scoping (Issue #1058) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Thursday, 21 November)
• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Thursday, 21 November)
• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Thursday, 21 November)
• Re: [w3c/selection-api] Throw correct exceptions from collapse/selectAllChildren on detached doctypes (#86) (Wednesday, 20 November)
• Re: [w3c/selection-api] Throw correct exceptions from collapse/selectAllChildren on detached doctypes (#86) (Wednesday, 20 November)
• Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342) (Wednesday, 20 November)
• Re: [w3c/selection-api] Throw InvalidNodeTypeError on DocumentType nodes (#118) (Wednesday, 20 November)
• Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342) (Wednesday, 20 November)
• Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342) (Tuesday, 19 November)
• Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342) (Saturday, 16 November)
• Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Sunday, 10 November)
• Re: [WICG/webcomponents] Clonning shadowroot , example : element.cloneNode({ deep: true, includeShadowDOM: true }); (Issue #1082) (Sunday, 10 November)
• Re: [WICG/webcomponents] Clonning shadowroot , example : element.cloneNode({ deep: true, includeShadowDOM: true }); (Issue #1082) (Sunday, 10 November)
• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Friday, 8 November)
• Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Monday, 4 November)
• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Saturday, 2 November)
• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Friday, 1 November)
• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Friday, 1 November)

Saad513744

• Re: [w3c/ServiceWorker] No idea. I think we should remove that restriction. (Issue #1737) (Sunday, 17 November)
• Re: [w3c/ServiceWorker] No idea. I think we should remove that restriction. (Issue #1737) (Sunday, 17 November)
• [w3c/ServiceWorker] No idea. I think we should remove that restriction. (Issue #1737) (Sunday, 17 November)

Shannon Booth

• Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331) (Thursday, 21 November)
• Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331) (Wednesday, 13 November)
• [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331) (Saturday, 9 November)

Shiba

• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Saturday, 16 November)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Saturday, 2 November)

Shivani Sharma

• Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975) (Wednesday, 27 November)

Sid Vishnoi

• Re: [w3c/push-api] Meta: address xref issue (PR #394) (Monday, 25 November)
• Re: [w3c/push-api] Meta: address xref issue (PR #394) (Monday, 25 November)

sideshowbarker

• Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342) (Tuesday, 19 November)
• Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342) (Monday, 18 November)

Simon Friedberger

• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 26 November)

Simon Pieters

• [whatwg/dom] Define iteration order of inclusive ancestors in "remove" (Issue #1322) (Wednesday, 6 November)

smaug----

• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 12 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 12 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 12 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Monday, 11 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Monday, 11 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Monday, 11 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Monday, 11 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Monday, 11 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Saturday, 9 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Saturday, 9 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Saturday, 9 November)
• Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320) (Monday, 4 November)

Sora2455

• Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995) (Thursday, 21 November)

Steve Orvell

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Tuesday, 26 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Thursday, 21 November)
• Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Sunday, 10 November)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Tuesday, 5 November)

Steven Becker

• Re: [w3c/IndexedDB] Return explicit failure from object store retrieval operations (Issue #432) (Friday, 8 November)

STR

• [whatwg/fetch] SSTTATUS (Issue #1784) (Saturday, 9 November)
• [whatwg/url] metro (Issue #837) (Saturday, 9 November)

Subhan Ahmed

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Monday, 4 November)

Switcherfaiz

• [WICG/webcomponents] Clonning shadowroot , example : element.cloneNode({ deep: true, includeShadowDOM: true }); (Issue #1082) (Saturday, 9 November)

Sébastien Lorber

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Monday, 25 November)

Tab Atkins Jr.

• Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994) (Wednesday, 13 November)
• Re: [w3ctag/design-reviews] CSS reading-flow property (Issue #978) (Wednesday, 6 November)

Thomas Steiner

• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Sunday, 10 November)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Thursday, 7 November)

Tim Nguyen

• Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003) (Thursday, 21 November)

Timo Tijhof

• Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320) (Wednesday, 13 November)
• Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320) (Tuesday, 5 November)

Tito

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Tuesday, 26 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Saturday, 23 November)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 22 November)

tjallingt

• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 21 November)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 20 November)

Traxx

• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Tuesday, 19 November)

Treasure Uvietobore

• Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Wednesday, 13 November)

Tristan Fraipont

• Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203) (Friday, 1 November)

Viktor

• Re: [w3c/selection-api] Selection.toString is under specified (#7) (Tuesday, 5 November)

vyv03354

• Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Thursday, 21 November)
• Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Wednesday, 13 November)

Westbrook Johnson

• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) (Thursday, 28 November)
• Re: [WICG/webcomponents] Reference Target Tracking Issue (Issue #1086) (Wednesday, 27 November)
• Re: [WICG/webcomponents] Reference Target: How to handle invalid ID references? (Issue #1071) (Wednesday, 27 November)
• Re: [WICG/webcomponents] Update reference-target-explainer supported attributes (PR #1084) (Thursday, 21 November)
• Re: [WICG/webcomponents] Update reference-target-explainer supported attributes (PR #1084) (Thursday, 21 November)
• [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Thursday, 21 November)

Xiaoqian Wu

• [w3ctag/design-reviews] Normative Changes of the Input Events Level 2 (Issue #1019) (Tuesday, 26 November)
• Re: [w3c/uievents-key] The link to [WEB4CE] is unavailable (Issue #69) (Thursday, 21 November)
• Re: [w3c/uievents-key] The link to [WEB4CE] is unavailable (Issue #69) (Thursday, 21 November)
• [w3c/uievents-key] The link to [WEB4CE] is unavailable (Issue #69) (Thursday, 14 November)

Yoav Weiss

• [w3ctag/design-reviews] CSP report-hash directive (Issue #1020) (Tuesday, 26 November)

Yoichi Osato

• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Wednesday, 20 November)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Monday, 11 November)
• Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734) (Tuesday, 5 November)

youennf

• Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734) (Wednesday, 27 November)
• Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734) (Friday, 8 November)
• Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734) (Monday, 4 November)
• [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734) (Monday, 4 November)

zhangenming

• Re: [whatwg/dom] Improve readability. maybe.. (PR #1326) (Tuesday, 19 November)
• Re: [whatwg/dom] Improve readability. maybe.. (PR #1326) (Tuesday, 19 November)
• Re: [whatwg/dom] Improve readability. maybe.. (PR #1326) (Tuesday, 19 November)
• Re: [whatwg/dom] Improve readability. maybe.. (PR #1326) (Tuesday, 19 November)
• Re: [whatwg/dom] Improve readability. maybe.. (PR #1326) (Tuesday, 19 November)
• [whatwg/dom] Improve readability. maybe.. (PR #1326) (Tuesday, 19 November)

Last message date: Saturday, 30 November 2024 22:42:38 UTC