public-webapps-github@w3.org from April 2025 by author

Abad1244

• Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001) (Wednesday, 16 April)

Adam Rice

• Re: [whatwg/encoding] Add support for [AllowResizable] inputs (Issue #344) (Wednesday, 30 April)

Addison Phillips

• Re: [w3ctag/design-reviews] Reduce Accept-Language (Issue #1078) (Thursday, 24 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Sunday, 13 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Friday, 11 April)

Alex Yang

• [w3c/uievents] Can KeyboardEvent.repeat ever be true for a keyup event? (Issue #396) (Saturday, 12 April)

Alexandra Borovova

• [w3c/permissions] Support `*` pattern as a value for `origin` argument in `permissions.setPermission` command (Issue #463) (Tuesday, 22 April)
• [w3c/permissions] Add WebDriver BiDi command to restore the permission state set before the update with `permissions.setPermission` command (Issue #462) (Tuesday, 22 April)

Alice

• Re: [WICG/webcomponents] Reference Target Tracking Issue (Issue #1086) (Friday, 18 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Wednesday, 16 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Wednesday, 16 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Wednesday, 16 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Tuesday, 15 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Tuesday, 15 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Tuesday, 15 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Tuesday, 15 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Tuesday, 15 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Tuesday, 15 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Tuesday, 15 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Tuesday, 15 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Monday, 14 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Monday, 14 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Friday, 11 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Friday, 11 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Monday, 7 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Monday, 7 April)
• [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Monday, 7 April)

Andrea Giammarchi

• Re: [whatwg/dom] MutationObserver callbacks happen in unexpected order. (Issue #1105) (Monday, 28 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 24 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 24 April)
• Re: [whatwg/encoding] TextEncoder and TextDecoder performance concern around all libraries / runtimes (Issue #343) (Thursday, 24 April)
• Re: [whatwg/encoding] Add support for [AllowResizable] inputs (Issue #344) (Thursday, 24 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 24 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 24 April)
• Re: [whatwg/encoding] TextEncoder and TextDecoder performance concern around all libraries / runtimes (Issue #343) (Thursday, 24 April)
• Re: [whatwg/encoding] TextEncoder and TextDecoder memory issue due resizable/shared buffers (Issue #344) (Thursday, 24 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Friday, 18 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Friday, 18 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 17 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 17 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 15 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 15 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 1 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 1 April)

Andrew

• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Wednesday, 2 April)

Andrew Sutherland

• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) (Wednesday, 30 April)

andruud

• Re: [w3ctag/design-reviews] Custom Functions (@function) (Issue #1031) (Thursday, 10 April)

andypaicu

• [w3ctag/design-reviews] Page-Embedded Permission Controls (Issue #1079) (Friday, 11 April)

Anne van Kesteren

• Re: [whatwg/encoding] Add support for [AllowResizable] inputs (Issue #344) (Wednesday, 30 April)
• Re: [whatwg/fetch] Handle request's window when from browser UI (PR #1821) (Wednesday, 30 April)
• Re: [whatwg/fetch] Improve "populate request from client" for null client cases (PR #1820) (Wednesday, 30 April)
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) (Wednesday, 30 April)
• Re: [whatwg/fetch] Improve "populate request from client" for null client cases (PR #1820) (Wednesday, 30 April)
• Re: [whatwg/fetch] Improve "populate request from client" for null client cases (PR #1820) (Wednesday, 30 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Monday, 28 April)
• Re: [whatwg/fetch] Redirect loop handling not discussed (Issue #1738) (Monday, 28 April)
• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) (Friday, 25 April)
• Re: [whatwg/encoding] Throw exception when text encode alloc memory fail. (Issue #334) (Thursday, 24 April)
• Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485) (Thursday, 24 April)
• Re: [whatwg/encoding] TextEncoder and TextDecoder performance concern around all libraries / runtimes (Issue #343) (Thursday, 24 April)
• Re: [whatwg/encoding] Add support for [AllowResizable] inputs (Issue #344) (Thursday, 24 April)
• Re: [whatwg/encoding] TextEncoder and TextDecoder memory issue due resizable/shared buffers (Issue #344) (Thursday, 24 April)
• Re: [whatwg/encoding] TextEncoder and TextDecoder memory issue due resizable/shared buffers (Issue #344) (Thursday, 24 April)
• Re: [whatwg/encoding] TextEncoder and TextDecoder performance concern around all libraries / runtimes (Issue #343) (Thursday, 24 April)
• Re: [whatwg/encoding] Need to define global used to create the ArrayBuffer and Uint8Array in TextEncoder's encode() (#150) (Thursday, 24 April)
• Re: [whatwg/encoding] Properly create Uint8Array objects (PR #350) (Thursday, 24 April)
• Re: [whatwg/encoding] Properly create Uint8Array objects (PR #350) (Thursday, 24 April)
• Re: [whatwg/encoding] Properly create Uint8Array objects (PR #350) (Thursday, 24 April)
• Re: [whatwg/encoding] Following your own style guide... (#242) (Thursday, 24 April)
• Re: [whatwg/encoding] Preface punctuation (Issue #304) (Thursday, 24 April)
• Re: [whatwg/encoding] Preface punctuation (Issue #304) (Thursday, 24 April)
• Re: [whatwg/encoding] Editorial: align even more with Infra (PR #349) (Thursday, 24 April)
• Re: [whatwg/encoding] Editorial: align even more with Infra (PR #349) (Thursday, 24 April)
• Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Wednesday, 23 April)
• Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338) (Wednesday, 23 April)
• Re: [whatwg/encoding] Properly create Uint8Array objects (PR #350) (Wednesday, 23 April)
• [whatwg/encoding] Properly create Uint8Array objects (PR #350) (Wednesday, 23 April)
• Re: [whatwg/encoding] Throw exception when text encode alloc memory fail. (Issue #334) (Wednesday, 23 April)
• [whatwg/encoding] Editorial: align even more with Infra (PR #349) (Wednesday, 23 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Wednesday, 23 April)
• Re: [whatwg/encoding] Editorial: align with Infra (PR #348) (Wednesday, 23 April)
• Re: [whatwg/encoding] Editorial: align with Infra (PR #348) (Wednesday, 23 April)
• Re: [whatwg/encoding] Editorial: align with Infra (PR #348) (Wednesday, 23 April)
• [whatwg/encoding] Editorial: align with Infra (PR #348) (Tuesday, 22 April)
• Re: [whatwg/encoding] Meta: add algorithm attribute to encoding sections (PR #347) (Tuesday, 22 April)
• Re: [whatwg/encoding] Meta: add algorithm attribute to encoding sections (PR #347) (Tuesday, 22 April)
• [whatwg/encoding] Meta: add algorithm attribute to encoding sections (PR #347) (Tuesday, 22 April)
• Re: [whatwg/encoding] Meta: add <div algorithm> everywhere except for the encoding handlers (PR #346) (Tuesday, 22 April)
• Re: [whatwg/encoding] Meta: add <div algorithm> everywhere except for the encoding handlers (PR #346) (Tuesday, 22 April)
• [whatwg/encoding] Meta: add <div algorithm> everywhere except for the encoding handlers (PR #346) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [whatwg/fetch] Redirect loop handling not discussed (Issue #1738) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [whatwg/encoding] Make encodeInto() throw when given a detached buffer (Issue #324) (Tuesday, 22 April)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) (Tuesday, 22 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Thursday, 17 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Thursday, 17 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 16 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Wednesday, 16 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Wednesday, 16 April)
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Tuesday, 15 April)
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Tuesday, 15 April)
• Re: [WICG/webcomponents] Scoped Custom Element Registry: Open Design Issues (#895) (Monday, 14 April)
• Re: [WICG/webcomponents] Moving elements with shadow roots between documents (#907) (Monday, 14 April)
• Re: [WICG/webcomponents] Interaction with declarative shadow DOM (#914) (Monday, 14 April)
• Re: [WICG/webcomponents] Element upgrade ordering (#923) (Monday, 14 April)
• Re: [WICG/webcomponents] Interaction with HTML element's overridden constructor steps (Issue #969) (Monday, 14 April)
• Re: [WICG/webcomponents] Finding a definition for disconnected elements (Issue #1040) (Monday, 14 April)
• Re: [WICG/webcomponents] Consider future expansion to allow using a registry without new API (Issue #1043) (Monday, 14 April)
• Re: [whatwg/dom] Revamped Scoped Custom Element Registries (DOM side) (Issue #1339) (Monday, 14 April)
• Re: [whatwg/dom] Revamped Scoped Custom Element Registries (DOM side) (Issue #1339) (Monday, 14 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 14 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 14 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Monday, 14 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 14 April)
• Re: [whatwg/dom] Revamped Scoped Custom Element Registries (DOM side) (Issue #1339) (Monday, 14 April)
• Re: [whatwg/dom] Revamped Scoped Custom Element Registries (DOM side) (Issue #1339) (Monday, 14 April)
• Re: [whatwg/dom] Define maximum length and handling of CharacterData nodes (Issue #1351) (Friday, 11 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Friday, 11 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Friday, 11 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Friday, 11 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Friday, 11 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Friday, 11 April)
• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Thursday, 10 April)
• Re: [whatwg/webidl] Consider renaming ByteString to IsomorphicString (Issue #1471) (Thursday, 10 April)
• Re: [whatwg/webidl] Consider renaming ByteString to IsomorphicString (Issue #1471) (Thursday, 10 April)
• Re: [whatwg/webidl] Consider renaming ByteString to IsomorphicString (Issue #1471) (Thursday, 10 April)
• Re: [whatwg/dom] Proposal: Enable Custom Form Controls to (Optionally) Conceal Internal/Irrelevant Events (Issue #1368) (Thursday, 10 April)
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] A resource timing entry is not created if the end of a non-null response body is not reached and there is no consume body steps (Issue #1813) (Wednesday, 9 April)
• Re: [whatwg/fetch] A resource timing entry is not created if the end of a non-null response body is not reached and there is no consume body steps (Issue #1813) (Wednesday, 9 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 9 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 9 April)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 9 April)
• Re: [whatwg/fetch] Redirect loop handling not discussed (Issue #1738) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/webidl] Define ModuleNamespace to ECMA-262 Module Namespace Exotic Object (PR #1483) (Wednesday, 9 April)
• Re: [whatwg/dom] [ElementInternals] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Wednesday, 9 April)
• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 8 April)
• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 8 April)
• Re: [WICG/webcomponents] Scoped Custom Element Registry: Open Design Issues (#895) (Tuesday, 8 April)
• Re: [WICG/webcomponents] Moving elements with shadow roots between documents (#907) (Tuesday, 8 April)
• Re: [WICG/webcomponents] Interaction with declarative shadow DOM (#914) (Tuesday, 8 April)
• Re: [WICG/webcomponents] Element upgrade ordering (#923) (Tuesday, 8 April)
• Re: [WICG/webcomponents] Interaction with HTML element's overridden constructor steps (Issue #969) (Tuesday, 8 April)
• Re: [WICG/webcomponents] Finding a definition for disconnected elements (Issue #1040) (Tuesday, 8 April)
• Re: [WICG/webcomponents] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 8 April)
• Re: [whatwg/dom] Should Live Range expose endpoints inside a shadow tree? (Issue #1362) (Tuesday, 8 April)
• [whatwg/dom] Blame stopped working (Issue #1367) (Tuesday, 8 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 7 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 7 April)
• [whatwg/dom] Cloning of a document does not copy "allow declarative shadow roots" (Issue #1366) (Monday, 7 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 7 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 7 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 7 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 7 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 7 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 7 April)
• Re: [whatwg/dom] Add reference target to shadow root (PR #1353) (Monday, 7 April)
• Re: [whatwg/webidl] Add package-lock.json or explicitly prevent it (Issue #1482) (Monday, 7 April)
• Re: [whatwg/webidl] Add package-lock.json or explicitly prevent it (Issue #1482) (Monday, 7 April)
• Re: [whatwg/webidl] Main (PR #1480) (Monday, 7 April)
• Re: [whatwg/dom] Naming of Composed Range (Issue #1363) (Monday, 7 April)
• Re: [whatwg/dom] [ElementInternals] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Monday, 7 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Friday, 4 April)
• Re: [whatwg/streams] Fix assertion when writing to a closed writable stream (PR #1342) (Thursday, 3 April)
• Re: [w3c/selection-api] mdanowar (Issue #348) (Wednesday, 2 April)
• Re: [whatwg/fetch] Add `Signature` to `CORS non-wildcard request-header name` (Issue #1819) (Tuesday, 1 April)

Antonio Sartori

• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Monday, 28 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Monday, 28 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Wednesday, 23 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Wednesday, 23 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Wednesday, 23 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Firing `pushsubscriptionchange` when permission is regranted (#236) (Tuesday, 22 April)
• [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)

Anusha Muley

• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) (Tuesday, 29 April)

Ardis Lu

• [whatwg/streams] Clarify that `ReadableStream`'s `cancel` may be invoked before `start` is complete (Issue #1344) (Monday, 28 April)

Barry Pollard

• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 7 April)

Burton Smith

• Re: [WICG/webcomponents] [declarative-custom-elements] Use case: framework integration (Issue #1100) (Tuesday, 15 April)

bvandersloot-mozilla

• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Tuesday, 15 April)
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Tuesday, 15 April)
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Monday, 14 April)
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Monday, 14 April)
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Monday, 14 April)

Camille Lamy

• Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995) (Friday, 25 April)
• Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995) (Thursday, 24 April)
• Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995) (Thursday, 3 April)

Chris Lilley

• Re: [w3ctag/design-reviews] Incremental Font Transfer (Issue #1057) (Friday, 25 April)
• Re: [w3ctag/design-reviews] Column wrapping for multicol (Issue #1073) (Tuesday, 22 April)

Christian Biesinger

• Re: [w3ctag/design-reviews] FedCM: Alternative Fields in Account Selection (Issue #1074) (Wednesday, 16 April)

Christian Liebel

• Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171) (Thursday, 24 April)
• Re: [w3c/manifest] Editorial: rephrase multiple icon example (PR #1170) (Thursday, 24 April)
• Re: [w3c/manifest] Editorial: rephrase multiple icon example (PR #1170) (Thursday, 24 April)
• [w3c/manifest] Editorial: rephrase multiple icon example (PR #1170) (Thursday, 24 April)

Claudia Meadows

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Wednesday, 30 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Wednesday, 30 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Tuesday, 29 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Tuesday, 29 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Monday, 28 April)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Wednesday, 23 April)

D++

• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Sunday, 27 April)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Saturday, 26 April)

Daniel Appelquist

• Re: [w3ctag/design-reviews] ClipboardChange event API (Issue #1017) (Thursday, 3 April)
• Re: [w3ctag/design-reviews] ClipboardChange event API (Issue #1017) (Thursday, 3 April)

Daniel Montalvo

• Re: [w3ctag/design-reviews] Accessibility conformance Testing (ACT) Rules Format 1.1 (Issue #977) (Monday, 14 April)

Daniel Rubery

• Re: [w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052) (Tuesday, 15 April)
• Re: [w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052) (Tuesday, 8 April)

Domenic Denicola

• Re: [whatwg/fetch] Improve "populate request from client" for null client cases (PR #1820) (Wednesday, 30 April)
• [whatwg/fetch] Handle request's window when from browser UI (PR #1821) (Wednesday, 30 April)
• Re: [whatwg/fetch] Improve "populate request from client" for null client cases (PR #1820) (Wednesday, 30 April)
• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) (Friday, 25 April)
• Re: [whatwg/fetch] Improve "populate request from client" for null client cases (PR #1820) (Friday, 25 April)
• [whatwg/fetch] Improve "populate request from client" for null client cases (PR #1820) (Friday, 25 April)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Thursday, 24 April)
• Re: [whatwg/encoding] Properly create Uint8Array objects (PR #350) (Thursday, 24 April)
• Re: [whatwg/encoding] Editorial: align even more with Infra (PR #349) (Thursday, 24 April)
• Re: [whatwg/encoding] Editorial: align with Infra (PR #348) (Wednesday, 23 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 17 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Thursday, 17 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Thursday, 17 April)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Wednesday, 16 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Wednesday, 16 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Wednesday, 16 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Tuesday, 15 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Tuesday, 15 April)
• Re: [w3c/IndexedDB] Adjust spec to take into account ResizableArrayBuffers / GrowableSharedArrayBuffers (Issue #446) (Monday, 14 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Monday, 14 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Saturday, 12 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Saturday, 12 April)
• Re: [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Saturday, 12 April)
• [whatwg/encoding] Explain the relationship between windows-1252, Latin1, and ASCII (PR #345) (Friday, 11 April)
• Re: [whatwg/webidl] Consider renaming ByteString to IsomorphicString (Issue #1471) (Thursday, 10 April)
• Re: [whatwg/webidl] Add package-lock.json or explicitly prevent it (Issue #1482) (Tuesday, 8 April)
• Re: [whatwg/streams] strategySizeAlgorithm validation in WritableStreamDefaultControllerGetChunkSize (Issue #1341) (Thursday, 3 April)
• Re: [whatwg/streams] Fix assertion when writing to a closed writable stream (PR #1342) (Thursday, 3 April)
• Re: [whatwg/streams] Fix assertion when writing to a closed writable stream (PR #1342) (Thursday, 3 April)
• [whatwg/streams] Fix assertion when writing to a closed writable stream (PR #1342) (Thursday, 3 April)

Dp-Goog

• [w3ctag/design-reviews] TAG review for making app updates more predictable, `update_token` (Issue #1076) (Wednesday, 2 April)

Edgar Chen

• Re: [w3c/clipboard-apis] Clarify "8.1. The copy action" in regards to copying selected data (#49) (Wednesday, 9 April)

Evan Liu

• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Monday, 28 April)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Friday, 25 April)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Friday, 18 April)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Wednesday, 2 April)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Wednesday, 2 April)

Frederik Bosch

• Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Friday, 11 April)

Frederik Braun

• Re: [whatwg/fetch] Add `Signature` to `CORS non-wildcard request-header name` (Issue #1819) (Tuesday, 1 April)

Frederik Wessberg

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Monday, 28 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Sunday, 27 April)

Gabriel Brito

• [w3ctag/design-reviews] media-playback-while-not-visible Permission Policy (Issue #1084) (Wednesday, 23 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Tuesday, 22 April)
• Re: [w3ctag/design-reviews] Web Audio AudioContext "interrupted" state (Issue #1069) (Monday, 21 April)

Gabriel Prates

• [w3c/ServiceWorker] Word stuck together in "Origin restriction" section (Issue #1765) (Friday, 25 April)

Gae24

• [w3c/clipboard-apis] Clarifying `clipboard.readText()` behaviour (Issue #236) (Monday, 28 April)

Glenn Skrzypczak

• Re: [whatwg/encoding] Make encodeInto() throw when given a detached buffer (Issue #324) (Saturday, 19 April)

goldenboy777

• [w3ctag/design-reviews] [SVG 2.0] Allow `use` to reference an external document's root element by omitting the fragment (Issue #1081) (Tuesday, 15 April)

Guohui Deng

• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 16 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 15 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Monday, 14 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Monday, 14 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Monday, 14 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Monday, 14 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Monday, 14 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 10 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 10 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 10 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 10 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 10 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 10 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 10 April)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 10 April)

Guy Bedford

• Re: [whatwg/webidl] Define ModuleNamespace to ECMA-262 Module Namespace Exotic Object (PR #1483) (Wednesday, 9 April)
• [whatwg/webidl] Define ModuleNamespace to ECMA-262 Module Namespace Exotic Object (PR #1483) (Tuesday, 8 April)

Hadley Beeman

• Re: [w3ctag/design-reviews] Container Timing API (Issue #1034) (Thursday, 10 April)

HE Shi-Jun

• Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023) (Monday, 28 April)

Henri Sivonen

• Re: [whatwg/encoding] Standardize x-mac-greek, x-mac-centraleurroman, and x-mac-turkish (Issue #342) (Monday, 14 April)

Henrik Skupin

• Re: [w3c/permissions] WebDriver: Should Set Permission apply to future browsing contexts? (Issue #437) (Thursday, 17 April)

Isaiah Thomason

• Re: [whatwg/dom] Proposal: Enable Custom Form Controls to (Optionally) Conceal Internal/Irrelevant Events (Issue #1368) (Wednesday, 23 April)
• [whatwg/dom] Proposal: Enable Custom Form Controls to (Optionally) Conceal Internal/Irrelevant Events (Issue #1368) (Wednesday, 9 April)

Jake Archibald

• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Tuesday, 15 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Monday, 14 April)
• Re: [whatwg/dom] Proposal: Enable Custom Form Controls to (Optionally) Conceal Internal/Irrelevant Events (Issue #1368) (Thursday, 10 April)
• Re: [whatwg/dom] Proposal: Enable Custom Form Controls to (Optionally) Conceal Internal/Irrelevant Events (Issue #1368) (Thursday, 10 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Wednesday, 9 April)
• Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001) (Tuesday, 1 April)

Jason Williams

• Re: [w3ctag/design-reviews] Container Timing API (Issue #1034) (Tuesday, 1 April)

Jeffrey Yasskin

• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) (Tuesday, 29 April)
• Re: [w3ctag/design-reviews] Update QuotaExceededError to a DOMException derived interface (Issue #1065) (Monday, 28 April)
• Re: [w3ctag/design-reviews] Update QuotaExceededError to a DOMException derived interface (Issue #1065) (Monday, 28 April)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Monday, 28 April)
• Re: [w3ctag/design-reviews] IP Protection (in Incognito mode) (Issue #1083) (Tuesday, 22 April)
• Re: [w3ctag/design-reviews] Controlled Frame (Issue #1067) (Tuesday, 22 April)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Monday, 21 April)
• Re: [w3ctag/design-reviews] `require-sri-for` CSP directive (Issue #1048) (Monday, 21 April)
• Re: [w3ctag/design-reviews] FedCM: Alternative Fields in Account Selection (Issue #1074) (Friday, 18 April)
• Re: [w3ctag/design-reviews] FedCM: Alternative Fields in Account Selection (Issue #1074) (Friday, 18 April)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Wednesday, 16 April)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Tuesday, 15 April)
• Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001) (Tuesday, 15 April)
• Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001) (Tuesday, 15 April)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Wednesday, 2 April)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Wednesday, 2 April)
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) (Tuesday, 1 April)
• Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001) (Tuesday, 1 April)
• Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001) (Tuesday, 1 April)

Jesse Jurman

• Re: [WICG/webcomponents] Clarify that declarative custom element definitions don't contain declarative shadow roots. (PR #1101) (Friday, 18 April)

Joe Pea

• Re: [whatwg/dom] Disconnect single target instead of all (#126) (Monday, 28 April)
• Re: [whatwg/dom] Disconnect single target instead of all (#126) (Monday, 28 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Sunday, 27 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Sunday, 27 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Sunday, 27 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Sunday, 27 April)
• Re: [WICG/webcomponents] [idea] making builtin elements more like custom elements (#785) (Sunday, 27 April)
• Re: [whatwg/dom] [ElementInternals] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Friday, 18 April)
• Re: [WICG/webcomponents] Clarify that declarative custom element definitions don't contain declarative shadow roots. (PR #1101) (Wednesday, 16 April)
• Re: [whatwg/dom] [ElementInternals] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Tuesday, 8 April)
• Re: [whatwg/dom] [ElementInternals] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Tuesday, 8 April)
• Re: [whatwg/dom] [ElementInternals] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Tuesday, 8 April)
• Re: [whatwg/dom] [ElementInternals] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Sunday, 6 April)
• Re: [whatwg/dom] [ElementInternals] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Sunday, 6 April)
• [whatwg/dom] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Sunday, 6 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Saturday, 5 April)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Tuesday, 1 April)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Tuesday, 1 April)

Johann Hofmann

• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Thursday, 24 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Saturday, 12 April)
• Re: [w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052) (Wednesday, 9 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Friday, 4 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Wednesday, 2 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Tuesday, 1 April)

Joshua Bell

• Re: [w3c/IndexedDB] Possible logic inversion in `iterate a cursor` (Issue #452) (Tuesday, 29 April)
• Re: [w3c/IndexedDB] How to compare a Record to a Key? (Issue #451) (Tuesday, 29 April)
• Re: [w3c/IndexedDB] How to compare a Record to a Key? (Issue #451) (Tuesday, 29 April)
• Re: [w3c/IndexedDB] How to read direction predicates in iterate a cursor? (Issue #450) (Tuesday, 29 April)
• Re: [w3c/IndexedDB] Wait loop questions (Issue #436) (Thursday, 24 April)
• Re: [w3c/IndexedDB] Wait loop questions (Issue #436) (Thursday, 24 April)
• Re: [w3c/IndexedDB] Wait loop questions (Issue #436) (Thursday, 24 April)
• Re: [w3c/IndexedDB] Address transaction state edge cases (PR #447) (Thursday, 24 April)
• Re: [w3c/IndexedDB] Wait loop questions (Issue #436) (Thursday, 24 April)
• Re: [w3c/IndexedDB] Address transaction state edge cases (PR #447) (Thursday, 24 April)
• Re: [w3c/IndexedDB] Possible wrong WPT test? (Issue #442) (Thursday, 24 April)
• Re: [w3c/IndexedDB] Do not include databases with version 0 in databases() results (PR #448) (Thursday, 24 April)
• Re: [whatwg/encoding] Editorial: align with Infra (PR #348) (Tuesday, 22 April)
• Re: [w3c/IndexedDB] Possibly unnecessary step in `evaluate a key path on a value` (Issue #449) (Friday, 18 April)
• Re: [w3c/IndexedDB] Possibly unnecessary step in `evaluate a key path on a value` (Issue #449) (Thursday, 17 April)
• Re: [w3c/IndexedDB] Adjust spec to take into account ResizableArrayBuffers / GrowableSharedArrayBuffers (Issue #446) (Thursday, 17 April)
• Re: [w3c/IndexedDB] Possibly unnecessary step in `evaluate a key path on a value` (Issue #449) (Thursday, 17 April)
• Re: [w3c/IndexedDB] Do not include databases with version 0 in databases() results (PR #448) (Friday, 11 April)
• [w3c/IndexedDB] Do not include databases with version 0 in databases() results (PR #448) (Friday, 11 April)
• Re: [w3c/IndexedDB] Address transaction state edge cases (PR #447) (Friday, 11 April)
• Re: [w3c/IndexedDB] Possible wrong WPT test? (Issue #442) (Friday, 11 April)
• Re: [w3c/IndexedDB] Adjust spec to take into account ResizableArrayBuffers / GrowableSharedArrayBuffers (Issue #446) (Friday, 11 April)
• Re: [w3c/IndexedDB] Address transaction state edge cases (PR #447) (Friday, 11 April)
• [w3c/IndexedDB] Address transaction state edge cases (PR #447) (Friday, 11 April)
• Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Friday, 11 April)
• Re: [w3c/IndexedDB] Rename 'array key' to 'composite key' (PR #392) (Friday, 11 April)
• Re: [w3c/IndexedDB] Normalize negative zero (PR #386) (Friday, 11 April)
• Re: [w3c/IndexedDB] Wait loop questions (Issue #436) (Thursday, 10 April)
• Re: [w3c/IndexedDB] asynchronously execute a request source object confusion (Issue #445) (Thursday, 3 April)

José Dapena Paz

• Re: [w3ctag/design-reviews] Container Timing API (Issue #1034) (Wednesday, 16 April)
• Re: [w3ctag/design-reviews] Container Timing API (Issue #1034) (Friday, 4 April)

JR Conlin

• Re: [w3c/push-api] Declarative Web Push (Issue #360) (Saturday, 12 April)

Julian Reschke

• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 16 April)

Justin Fagnani

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Tuesday, 29 April)
• Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023) (Monday, 28 April)
• Re: [whatwg/dom] Disconnect single target instead of all (#126) (Monday, 28 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: Bulk mutation methods for working with ranges of nodes (Issue #1369) (Wednesday, 16 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Tuesday, 15 April)
• [whatwg/dom] Proposal: Bulk mutation methods for working with ranges of nodes (Issue #1369) (Monday, 14 April)
• [WICG/webcomponents] Clarify that declarative custom element definitions don't contain declarative shadow roots. (PR #1101) (Saturday, 12 April)
• [WICG/webcomponents] [declarative-custom-elements] Use case: framework integration (Issue #1100) (Saturday, 12 April)
• [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Saturday, 12 April)
• Re: [WICG/webcomponents] HTML Modules (#645) (Thursday, 10 April)
• Re: [WICG/webcomponents] Idea: A tree-aware task scheduler (Issue #1055) (Wednesday, 9 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] do we need DOM parts or any template mechanism in spec? (Issue #1090) (Wednesday, 9 April)
• Re: [WICG/webcomponents] HTML Modules (#645) (Monday, 7 April)

Justin Richer

• Re: [whatwg/fetch] Add `Signature` to `CORS non-wildcard request-header name` (Issue #1819) (Tuesday, 1 April)

Kagami Sascha Rosylight

• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) (Tuesday, 29 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Monday, 28 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Monday, 28 April)
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) (Monday, 28 April)
• Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485) (Thursday, 24 April)
• [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485) (Thursday, 24 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Wednesday, 23 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Wednesday, 23 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Wednesday, 23 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Allow firing pushsubscriptionchange on all permission changes (PR #400) (Tuesday, 22 April)
• Re: [w3c/push-api] Firing `pushsubscriptionchange` when permission is regranted (#236) (Monday, 14 April)
• Re: [w3c/push-api] Declarative Web Push (Issue #360) (Saturday, 12 April)
• Re: [w3c/push-api] Firing `pushsubscriptionchange` when permission is regranted (#236) (Friday, 11 April)
• Re: [whatwg/webidl] Add package-lock.json or explicitly prevent it (Issue #1482) (Monday, 7 April)
• [whatwg/webidl] Add package-lock.json or explicitly prevent it (Issue #1482) (Monday, 7 April)
• Re: [whatwg/webidl] Main (PR #1481) (Monday, 7 April)
• Re: [whatwg/webidl] Main (PR #1480) (Monday, 7 April)

Karl Dubost

• [w3c/clipboard-apis] Clarifying the Error Types for clipboard APIs (Issue #235) (Thursday, 3 April)

Keith Cirkel

• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Monday, 14 April)

Kevin Gibbons

• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) (Tuesday, 22 April)

Koji Ishii

• Re: [w3c/editing] Behavior of insert* commands for contenteditable=plaintext-only (Issue #419) (Wednesday, 30 April)

Kurt Catti-Schmidt

• [whatwg/dom] cloneNode with nodes with resources such as <link rel="stylesheet"> (Issue #1370) (Tuesday, 22 April)

Lea Verou

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Tuesday, 29 April)

LEVIANA

• Re: [w3c/manifest] What happend (Issue #1167) (Tuesday, 1 April)

Lola

• Re: [w3ctag/design-reviews] Early Design Review: Related Website Partition API (Issue #1047) (Wednesday, 16 April)
• Re: [w3ctag/design-reviews] Early Design Review: Related Website Partition API (Issue #1047) (Wednesday, 16 April)
• Re: [w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052) (Wednesday, 9 April)

lukasIO

• [whatwg/streams] Clarify expected behaviour when breaking async iteration of teed ReadableStream (Issue #1343) (Thursday, 17 April)

Lukasz Olejnik

• Re: [w3ctag/design-reviews] TAG spec review of Stateless Bounce Tracking Mitigations (Issue #1062) (Friday, 11 April)
• Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838) (Friday, 11 April)

Luke Warlow

• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 24 April)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 24 April)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 24 April)

Makoto Kato

• [w3c/screen-orientation] Does orienation lock should be aborted or ignore when document is hidden in pararel step of 8.3? (Issue #256) (Monday, 21 April)

Maksim Sadym

• Re: [w3c/gamepad] Rewrite the spec with references to the Model section (PR #222) (Wednesday, 2 April)
• Re: [w3c/gamepad] Rewrite the spec with references to the Model section (PR #222) (Wednesday, 2 April)
• Re: [w3c/gamepad] Rewrite the spec with references to the Model section (PR #222) (Wednesday, 2 April)
• Re: [w3c/gamepad] Interop 2025 investigation effort - Gamepad API testing (Issue #219) (Tuesday, 1 April)

Marco Colli

• Re: [w3c/push-api] Firing `pushsubscriptionchange` when permission is regranted (#236) (Monday, 14 April)

Marcos Cáceres

• Re: [w3c/manifest] Editorial: rephrase multiple icon example (PR #1170) (Thursday, 24 April)
• Re: [w3c/manifest] Editorial: rephrase multiple icon example (PR #1170) (Thursday, 24 April)
• [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171) (Thursday, 24 April)
• Re: [w3c/manifest] Clarify how images are loaded, and that they don't depend on CSP (#910) (Thursday, 24 April)
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) (Tuesday, 1 April)

Marja Hölttä

• [w3c/IndexedDB] Adjust spec to take into account ResizableArrayBuffers / GrowableSharedArrayBuffers (Issue #446) (Tuesday, 8 April)

Mark Nottingham

• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Thursday, 3 April)
• Re: [whatwg/fetch] Add `Signature` to `CORS non-wildcard request-header name` (Issue #1819) (Tuesday, 1 April)
• [whatwg/fetch] Add `Signature` to `CORS non-wildcard request-header name` (Issue #1819) (Tuesday, 1 April)

Martin Thomson

• Re: [w3ctag/design-reviews] TAG review for making app updates more predictable, `update_token` (Issue #1076) (Tuesday, 29 April)
• Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995) (Thursday, 24 April)
• Re: [w3ctag/design-reviews] Navigation API deferred commit (Issue #1040) (Thursday, 24 April)
• Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995) (Thursday, 24 April)
• Re: [w3ctag/design-reviews] Navigation API deferred commit (Issue #1040) (Thursday, 24 April)
• Re: [w3ctag/design-reviews] Navigation API deferred commit (Issue #1040) (Thursday, 24 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Thursday, 24 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Friday, 11 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Friday, 11 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Friday, 11 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Wednesday, 2 April)
• Re: [w3ctag/design-reviews] CSP report-hash keyword (Issue #1020) (Wednesday, 2 April)
• Re: [w3ctag/design-reviews] CSP report-hash keyword (Issue #1020) (Wednesday, 2 April)
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) (Tuesday, 1 April)
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) (Tuesday, 1 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Tuesday, 1 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Tuesday, 1 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Tuesday, 1 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Tuesday, 1 April)

Mason Freed

• Re: [whatwg/dom] Define mutation events (#305) (Friday, 4 April)

Matt Reynolds

• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Add a model section (PR #220) (Saturday, 26 April)
• Re: [w3c/gamepad] Rewrite the spec with references to the Model section (PR #222) (Friday, 4 April)
• Re: [w3c/gamepad] Rewrite the spec with references to the Model section (PR #222) (Friday, 4 April)
• Re: [w3c/gamepad] Rewrite the spec with references to the Model section (PR #222) (Thursday, 3 April)
• Re: [w3c/gamepad] Interop 2025 investigation effort - Gamepad API testing (Issue #219) (Tuesday, 1 April)

Matthew Tylee Atkinson

• Re: [w3ctag/design-reviews] 'focus-without-user-activation' permissions policy (Issue #1066) (Wednesday, 30 April)
• Re: [w3ctag/design-reviews] Web Audio AudioContext "interrupted" state (Issue #1069) (Sunday, 20 April)
• Re: [w3ctag/design-reviews] Web Audio AudioContext "interrupted" state (Issue #1069) (Sunday, 20 April)
• Re: [w3ctag/design-reviews] [HTML] 2D canvas floating point support (Issue #1030) (Thursday, 3 April)
• Re: [w3ctag/design-reviews] [HTML] 2D canvas floating point support (Issue #1030) (Thursday, 3 April)
• Re: [w3ctag/design-reviews] CSS inert (Issue #1055) (Tuesday, 1 April)

Mattias Buelens

• Re: [whatwg/streams] Fix assertion when writing to a closed writable stream (PR #1342) (Thursday, 3 April)

MD ANOWARUL ISLAM

• Re: [w3c/selection-api] mdanowar (Issue #348) (Wednesday, 2 April)
• [w3c/selection-api] mdanowar (Issue #348) (Wednesday, 2 April)

meacer

• Re: [whatwg/fetch] Redirect loop handling not discussed (Issue #1738) (Saturday, 26 April)
• Re: [whatwg/fetch] Redirect loop handling not discussed (Issue #1738) (Thursday, 17 April)

Meghan Denny

• Re: [whatwg/webidl] bfnjf780@gmail.com (Issue #1484) (Sunday, 20 April)
• Re: [whatwg/webidl] Consider renaming ByteString to IsomorphicString (Issue #1471) (Thursday, 10 April)
• Re: [whatwg/webidl] Consider renaming ByteString to IsomorphicString (Issue #1471) (Thursday, 10 April)

MGit93

• [whatwg/webidl] Main (PR #1481) (Monday, 7 April)
• [whatwg/webidl] Main (PR #1480) (Monday, 7 April)

Mike Taylor

• [w3ctag/design-reviews] IP Protection (Issue #1083) (Tuesday, 22 April)

Mike West

• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Tuesday, 1 April)

Monica Chintala

• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Tuesday, 22 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Tuesday, 22 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Sunday, 20 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Sunday, 20 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Sunday, 20 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Friday, 18 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 17 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 17 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Wednesday, 16 April)
• [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Wednesday, 16 April)
• Re: [w3c/ServiceWorker] Avoid using "anchors" block for referencing other specs in Bikeshed (Issue #1763) (Thursday, 3 April)
• Re: [w3c/ServiceWorker] Editorial: Revise reference links with bikeshed (PR #1762) (Thursday, 3 April)
• Re: [w3c/ServiceWorker] Avoid Using "anchors" Block for Referencing Other Specs in Bikeshed (Issue #1763) (Thursday, 3 April)
• [w3c/ServiceWorker] Avoid Using "anchors" Block for Referencing Other Specs in Bikeshed (Issue #1763) (Thursday, 3 April)

Morten Stenshorne

• Re: [w3ctag/design-reviews] Column wrapping for multicol (Issue #1073) (Tuesday, 22 April)
• Re: [w3ctag/design-reviews] Column wrapping for multicol (Issue #1073) (Tuesday, 22 April)

Noam Rosenthal

• Re: [w3ctag/design-reviews] Navigation API deferred commit (Issue #1040) (Thursday, 24 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] A resource timing entry is not created if the end of a non-null response body is not reached and there is no consume body steps (Issue #1813) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 9 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Tuesday, 8 April)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Tuesday, 8 April)
• Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001) (Tuesday, 1 April)

Ophir LOJKINE

• [w3c/editing] Clarification on [NoInterfaceObject] for SVGPathSegment and Usage of setPathData() (Issue #483) (Friday, 4 April)

Orko Garai

• Re: [w3c/uievents] Clarification about whether requirement to send key events during composition extends to platforms (Issue #395) (Tuesday, 15 April)
• [w3c/uievents] Clarification about whether requirement to send key events during composition extends to platforms (Issue #395) (Thursday, 10 April)

Pascal Vos

• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Sunday, 27 April)

Philip Jägenstedt

• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Friday, 25 April)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 23 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Thursday, 10 April)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Thursday, 10 April)

Philippe Le Hegaret

• Re: [w3c/uievents-code] Tasks for wide review (Issue #35) (Friday, 18 April)
• Re: [w3c/permissions] Editorial: Prepare for CR (PR #457) (Friday, 4 April)

pranavmodi25

• Re: [w3c/selection-api] Inconsistent Behavior of Softwrap Property in Textarea Across Browsers (Issue #349) (Thursday, 3 April)
• [w3c/editing] Inconsistent Behavior of Softwrap Property in Textarea Across Browsers (Issue #482) (Thursday, 3 April)
• [w3c/selection-api] Inconsistent Behavior of Softwrap Property in Textarea Across Browsers (Issue #349) (Thursday, 3 April)

Rachel Andrew

• Re: [w3ctag/design-reviews] Column wrapping for multicol (Issue #1073) (Tuesday, 22 April)
• Re: [w3ctag/design-reviews] Column wrapping for multicol (Issue #1073) (Tuesday, 22 April)

Rafael Kraut

• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) (Thursday, 17 April)

Robbie Speed

• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 17 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: Bulk mutation methods for working with ranges of nodes (Issue #1369) (Tuesday, 15 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Monday, 14 April)

Robert Flack

• Re: [w3ctag/design-reviews] CSS Overflow Navigation Controls (Carousels) (Issue #1037) (Friday, 25 April)

Robert Longson

• Re: [w3c/editing] Clarification on [NoInterfaceObject] for SVGPathSegment and Usage of setPathData() (Issue #483) (Saturday, 12 April)

Ryosuke Niwa

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Sunday, 27 April)
• Re: [w3c/selection-api] Fixes https://github.com/w3c/selection-api/issues/170. (PR #172) (Wednesday, 23 April)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Wednesday, 23 April)
• Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Tuesday, 22 April)
• Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Tuesday, 22 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Monday, 14 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Friday, 4 April)

Sasha Firsov

• Re: [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Thursday, 17 April)
• [WICG/webcomponents] [declarative-custom-elements] Use cases: data transformation (Issue #1103) (Thursday, 17 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use case: NO-JS (Issue #1102) (Thursday, 17 April)
• [WICG/webcomponents] [declarative-custom-elements] Use case: NO-JS (Issue #1102) (Thursday, 17 April)
• Re: [WICG/webcomponents] Clarify that declarative custom element definitions don't contain declarative shadow roots. (PR #1101) (Wednesday, 16 April)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Tuesday, 15 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Tuesday, 15 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Tuesday, 15 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Tuesday, 15 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Tuesday, 15 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Tuesday, 15 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Tuesday, 15 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Tuesday, 15 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Tuesday, 15 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use cases (Issue #1099) (Tuesday, 15 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] Use case: framework integration (Issue #1100) (Tuesday, 15 April)
• Re: [WICG/webcomponents] Clarify that declarative custom element definitions don't contain declarative shadow roots. (PR #1101) (Tuesday, 15 April)
• Re: [WICG/webcomponents] [declarative-custom-elements] do we need DOM parts or any template mechanism in spec? (Issue #1090) (Friday, 11 April)
• Re: [w3ctag/design-reviews] DOM merging engine/API (Discussion #882) (Monday, 7 April)

sdammohmd

• [whatwg/webidl] bfnjf780@gmail.com (Issue #1484) (Sunday, 20 April)

Shiba

• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 24 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 24 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 24 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 24 April)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Tuesday, 22 April)

Shunya Shishido

• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Monday, 21 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Friday, 18 April)

Simon Pieters

• Re: [w3c/editing] Behavior of insert* commands for contenteditable=plaintext-only (Issue #419) (Tuesday, 29 April)
• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) (Thursday, 24 April)
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) (Wednesday, 2 April)

smaug----

• Re: [whatwg/dom] Define maximum length and handling of CharacterData nodes (Issue #1351) (Friday, 11 April)

stelar7

• [w3c/IndexedDB] Possible logic inversion in `iterate a cursor` (Issue #452) (Tuesday, 29 April)
• Re: [w3c/IndexedDB] How to compare a Record to a Key? (Issue #451) (Tuesday, 29 April)
• Re: [w3c/IndexedDB] How to compare a Record to a Key? (Issue #451) (Tuesday, 29 April)
• [w3c/IndexedDB] How to compare a Record to a Key? (Issue #451) (Tuesday, 29 April)
• [w3c/IndexedDB] How to read direction predicates in iterate a cursor? (Issue #450) (Tuesday, 29 April)
• Re: [w3c/IndexedDB] Possibly unnecessary step in `evaluate a key path on a value` (Issue #449) (Friday, 18 April)
• Re: [w3c/IndexedDB] Possibly unnecessary step in `evaluate a key path on a value` (Issue #449) (Friday, 18 April)
• Re: [w3c/IndexedDB] Possibly unnecessary step in `evaluate a key path on a value` (Issue #449) (Thursday, 17 April)
• [w3c/IndexedDB] Possibly unnecessary step in `evaluate a key path on a value` (Issue #449) (Wednesday, 16 April)
• Re: [w3c/IndexedDB] Address transaction state edge cases (PR #447) (Saturday, 12 April)
• Re: [w3c/IndexedDB] Do not include databases with version 0 in databases() results (PR #448) (Saturday, 12 April)
• Re: [w3c/IndexedDB] Wait loop questions (Issue #436) (Wednesday, 9 April)
• [w3c/IndexedDB] asynchronously execute a request source object confusion (Issue #445) (Tuesday, 1 April)

Steve Orvell

• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 15 April)

Steven Becker

• Re: [w3c/IndexedDB] Do not include databases with version 0 in databases() results (PR #448) (Thursday, 24 April)
• Re: [w3c/IndexedDB] Address transaction state edge cases (PR #447) (Thursday, 24 April)

Sun Shin

• Re: [w3c/uievents] Suggestion for the support of Keyboard Lock API (Issue #385) (Tuesday, 15 April)
• Re: [w3c/uievents] Suggestion for the support of Keyboard Lock API (Issue #385) (Tuesday, 15 April)

Tatsunori Uchino

• Re: [w3c/uievents] isComposing in onInput is always `true` while you turn on IME until recomposition only in Chromium (Issue #394) (Saturday, 5 April)
• Re: [w3c/uievents] Event order between "compositionend" and "input" (#202) (Saturday, 5 April)
• Re: [w3c/uievents] isComposing in onInput is always `true` while you turn on IME until recomposition in Chromium (Issue #394) (Friday, 4 April)
• [w3c/uievents] isComposing in onInput is always `true` while you turn on IME until recomposition in Chromium (Issue #394) (Friday, 4 April)

Tim Cappalli

• [w3ctag/design-reviews] [wg/webauthn] Web Authentication Level 3 (Issue #1085) (Tuesday, 29 April)

Timo Tijhof

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

Trevor N. Suarez

• Re: [w3c/ServiceWorker] Service worker client URL discrepancy (#1515) (Thursday, 24 April)

Uku Sõrmus

• Re: [whatwg/url] Empty labels (consecutive dots, and trailing dot for host writing + UTS46) (Issue #871) (Tuesday, 22 April)
• [whatwg/url] Empty labels (consecutive dots, and trailing dot for host writing + UTS46) (Issue #871) (Monday, 21 April)
• [whatwg/url] Clarify: "host" definition doesn't include port, but URL host attribute getter can (Issue #870) (Monday, 7 April)
• [whatwg/url] Usage of the term "hostname" may need clarifications as it clashes with popular usage (Issue #869) (Monday, 7 April)

Valery Zinchenko

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Wednesday, 30 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Wednesday, 30 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Tuesday, 29 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Monday, 28 April)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Monday, 28 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Sunday, 27 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Friday, 18 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Friday, 18 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 17 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Wednesday, 16 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 15 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 15 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 15 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 15 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 15 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Monday, 14 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Monday, 14 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 1 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 1 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 1 April)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 1 April)

Victor Tan

• [w3ctag/design-reviews] Reduce Accept-Language (Issue #1078) (Thursday, 3 April)

W3C Bot

• [w3ctag/design-reviews] [wg/media] Media Working Group Charter (Issue #1082) (Friday, 18 April)
• [w3ctag/design-reviews] [wg/payments] Web Payments Working Group Charter (Issue #1080) (Monday, 14 April)
• [w3ctag/design-reviews] [ig/wai] WAI IG recharter (Issue #1077) (Thursday, 3 April)

Westbrook Johnson

• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Saturday, 12 April)
• Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098) (Friday, 11 April)

Xiaocheng Hu

• Re: [w3ctag/design-reviews] Custom Functions (@function) (Issue #1031) (Friday, 25 April)
• Re: [w3ctag/design-reviews] Custom Functions (@function) (Issue #1031) (Friday, 25 April)
• Re: [w3ctag/design-reviews] [HTML] Fix divergence of CanvasRenderingContext2D and Offscreen with CanvasSettings (Issue #1036) (Tuesday, 22 April)
• Re: [w3ctag/design-reviews] [HTML] Fix divergence of CanvasRenderingContext2D and Offscreen with CanvasSettings (Issue #1036) (Tuesday, 22 April)
• Re: [w3ctag/design-reviews] CSS Stylable Columns (Issue #1056) (Tuesday, 22 April)
• Re: [w3ctag/design-reviews] Column wrapping for multicol (Issue #1073) (Thursday, 17 April)
• Re: [w3ctag/design-reviews] CSS inert (Issue #1055) (Tuesday, 15 April)
• Re: [w3ctag/design-reviews] CSS inert (Issue #1055) (Tuesday, 15 April)
• Re: [w3ctag/design-reviews] CSS Scroll Markers (Issue #1053) (Tuesday, 15 April)
• Re: [w3ctag/design-reviews] CSS Scroll Markers (Issue #1053) (Tuesday, 15 April)
• Re: [w3ctag/design-reviews] CSS Scroll Buttons (Issue #1054) (Tuesday, 15 April)
• Re: [w3ctag/design-reviews] CSS Scroll Buttons (Issue #1054) (Tuesday, 15 April)
• Re: [w3ctag/design-reviews] CSS View Transitions - Nested View Transition Groups (Issue #1061) (Monday, 14 April)
• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) (Monday, 7 April)
• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) (Monday, 7 April)

Xiaoqian Wu

• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Tuesday, 22 April)
• [w3c/editing] Recharter the Web Editing WG (Issue #484) (Thursday, 10 April)

Yao Xiao

• Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Thursday, 24 April)

Yehonatan Daniv

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Monday, 28 April)

Yoav Weiss

• Re: [whatwg/fetch] Accept headers in spec cause confusion (#274) (Wednesday, 30 April)
• Re: [w3ctag/design-reviews] Reduce Accept-Language (Issue #1078) (Wednesday, 30 April)
• Re: [w3ctag/design-reviews] `require-sri-for` CSP directive (Issue #1048) (Wednesday, 23 April)
• Re: [w3ctag/design-reviews] `require-sri-for` CSP directive (Issue #1048) (Wednesday, 23 April)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] Service worker client URL discrepancy (#1515) (Wednesday, 30 April)
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) (Tuesday, 29 April)
• Re: [w3c/ServiceWorker] Word stuck together in "Origin Relativity - importScripts(urls)" section (Issue #1765) (Sunday, 27 April)
• Re: [w3c/ServiceWorker] Word stuck together in "Origin Relativity - importScripts(urls)" section (Issue #1765) (Sunday, 27 April)
• Re: [w3c/ServiceWorker] Editorial: Add a space between following and perform the fetch hook (PR #1766) (Sunday, 27 April)
• [w3c/ServiceWorker] Editorial: Add a space between following and perform the fetch hook (PR #1766) (Sunday, 27 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Monday, 21 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Friday, 18 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Friday, 18 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 17 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 17 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 17 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 17 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 17 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 17 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Wednesday, 16 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Wednesday, 16 April)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Wednesday, 16 April)
• Re: [w3c/ServiceWorker] Avoid using "anchors" block for referencing other specs in Bikeshed (Issue #1763) (Thursday, 3 April)
• Re: [w3c/ServiceWorker] Editorial: Revise reference links with bikeshed (PR #1762) (Thursday, 3 April)

Yuval

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

一丝

• Re: [w3c/editing] Behavior of insert* commands for contenteditable=plaintext-only (Issue #419) (Wednesday, 23 April)
• Re: [w3c/editing] Should contenteditable=plaintext-only be standardized? (#162) (Wednesday, 23 April)

Last message date: Wednesday, 30 April 2025 19:21:49 UTC