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

Alex Keng

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

Alex Rudenko

• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Sunday, 12 October)

Alice

• Re: [WICG/webcomponents] Reference Target: Rethinking attribute reflection for invalid reference targets (Issue #1114) (Saturday, 11 October)
• [WICG/webcomponents] Reference Target: Rethinking attribute reflection for invalid reference targets (Issue #1114) (Thursday, 2 October)

Alison Maher

• [w3ctag/design-reviews] WG Revision: CSS Color Adjust Level 1 (Issue #1156) (Monday, 6 October)

Amit Bansal

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

Anne van Kesteren

• Re: [w3c/uievents] Proposal: use `relatedTarget` for click events originated from labels (Issue #402) (Thursday, 16 October)
• Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243) (Wednesday, 15 October)
• Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Monday, 13 October)
• Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Monday, 13 October)
• Re: [WICG/webcomponents] Reference Target: Rethinking attribute reflection for invalid reference targets (Issue #1114) (Monday, 13 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Saturday, 11 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [WICG/webcomponents] Reference Target: Rethinking attribute reflection for invalid reference targets (Issue #1114) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/dom] Add reference target to shadow root (PR #1353) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400) (Friday, 10 October)
• Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400) (Friday, 10 October)
• Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412) (Friday, 10 October)
• Re: [whatwg/dom] custom element registry mutability in an element (Issue #1414) (Friday, 10 October)
• Re: [w3c/editing] Nested editing hosts do not need to be wrapped in insertParagraph (Issue #490) (Thursday, 9 October)
• Re: [w3c/editing] Nested editing hosts do not need to be wrapped in insertParagraph (Issue #490) (Thursday, 9 October)
• Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412) (Thursday, 9 October)
• Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Wednesday, 8 October)
• Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Tuesday, 7 October)
• Re: [whatwg/dom] attachShadow default custom element registry (Issue #1407) (Tuesday, 7 October)
• Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409) (Tuesday, 7 October)
• Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409) (Tuesday, 7 October)
• Re: [whatwg/fetch] static method: `Response.html`? (Issue #1865) (Monday, 6 October)
• Re: [whatwg/fetch] static method: `Response.html`? (Issue #1865) (Monday, 6 October)
• Re: [whatwg/xhr] Clarify if `ProgressEvent.loaded` should indicate the size of compress, or uncompressed, data (Issue #388) (Monday, 6 October)
• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Monday, 6 October)
• Re: [w3c/ServiceWorker] Expose fragments cross-origin for subresources (#910) (Sunday, 5 October)
• Re: [whatwg/xhr] Clarify if `ProgressEvent.loaded` should indicate the size of compress, or uncompressed, data (Issue #388) (Sunday, 5 October)
• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Sunday, 5 October)
• [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409) (Saturday, 4 October)
• Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408) (Thursday, 2 October)
• Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862) (Thursday, 2 October)
• Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861) (Thursday, 2 October)
• Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861) (Thursday, 2 October)
• Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862) (Thursday, 2 October)
• Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861) (Thursday, 2 October)
• Re: [whatwg/encoding] Text(De|En)coder in WorkletGlobalScope (Issue #356) (Thursday, 2 October)
• Re: [whatwg/dom] attachShadow default custom element registry (Issue #1407) (Wednesday, 1 October)
• Re: [whatwg/dom] [ElementInternals] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Wednesday, 1 October)
• Re: [whatwg/dom] [ElementInternals] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Wednesday, 1 October)
• Re: [whatwg/dom] attachShadow default custom element registry (Issue #1407) (Wednesday, 1 October)

Ari Chivukula

• Re: [w3ctag/design-reviews] Other Spec Review: TCP Socket Pool Limit Randomization (Issue #1151) (Wednesday, 15 October)
• Re: [w3ctag/design-reviews] Incubation: Preventing User Dictionary Leaks via ::spelling-error and ::grammar-error CSS Pseudo-Elements (Issue #1148) (Thursday, 9 October)

basmatiraghman19-sketch

• [whatwg/url] URL (Issue #886) (Monday, 13 October)

Bruce B. Anderson

• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Sunday, 12 October)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Saturday, 11 October)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Saturday, 11 October)

bvandersloot-mozilla

• Re: [w3c/screen-orientation] Address privacy review feedback (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Friday, 17 October)
• Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Friday, 17 October)

Carly BigEagle Whiteman

• Re: [whatwg/fetch] Http parsing Carlyluminatti (Issue #1866) (Tuesday, 7 October)
• [whatwg/fetch] Http parsing Carlyluminatti (Issue #1866) (Tuesday, 7 October)

Christian Biesinger

• Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support showing third-party iframe origins in the UI (Issue #1145) (Thursday, 9 October)

Christian Liebel

• Re: [w3ctag/design-reviews] WG Revision: Screen Orientation (Issue #1155) (Wednesday, 15 October)
• Re: [w3ctag/design-reviews] WG Revision: Screen Orientation (Issue #1155) (Wednesday, 15 October)
• Re: [w3ctag/design-reviews] WG Revision: Geolocation (Issue #1144) (Thursday, 9 October)
• Re: [w3ctag/design-reviews] WG Revision: Geolocation (Issue #1144) (Thursday, 9 October)
• Re: [w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188) (Monday, 6 October)

communicator47

• Re: [w3c/uievents] Need virtual key codes (Issue #377) (Tuesday, 14 October)

Copilot

• Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273) (Friday, 17 October)
• Re: [w3c/screen-orientation] Add hidden document monitoring in parallel orientation lock steps (PR #272) (Friday, 17 October)
• Re: [w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270) (Friday, 17 October)
• Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269) (Friday, 17 October)
• Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269) (Friday, 17 October)
• Re: [w3c/screen-orientation] Address privacy review feedback (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Fix iframe promise rejection in unloading document cleanup (PR #268) (Thursday, 16 October)

cutiful

• [whatwg/xhr] `ProgressEvent.loaded` references decompressed length, but `total` references the Content-Length header (Issue #403) (Thursday, 16 October)
• Re: [whatwg/xhr] Clarify if `ProgressEvent.loaded` should indicate the size of compress, or uncompressed, data (Issue #388) (Sunday, 5 October)
• Re: [whatwg/xhr] Clarify if `ProgressEvent.loaded` should indicate the size of compress, or uncompressed, data (Issue #388) (Sunday, 5 October)

Dan Clark

• Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409) (Monday, 6 October)
• Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134) (Wednesday, 1 October)

Daniel Murphy

• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Friday, 17 October)
• Re: [w3c/manifest] Use URLPattern for scope member (#1002) (Friday, 17 October)
• [w3c/manifest] PWA Migration (Issue #1189) (Thursday, 16 October)

Dominique Hazael-Massieux

• Re: [w3c/ServiceWorker] Broken references in Service Workers Nightly (Issue #1669) (Wednesday, 8 October)

ehind67

• Re: [w3c/screen-orientation] Wording change; adjust term "clicking" to "Select" to reflect multiple ways to activate Lock/Unlock (Issue #263) (Thursday, 16 October)
• [w3c/screen-orientation] Some Code Samples have code references in orange/light blue color combination which has 2.9:1 contrast (should be 4.5:1) (Issue #264) (Tuesday, 14 October)
• [w3c/screen-orientation] Wording change; adjust term "clicking" to "Select" to reflect multiple ways to activate Lock/Unlock (Issue #263) (Tuesday, 14 October)

Ehsan Toreini

• Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135) (Tuesday, 7 October)

fadol83-lab

• [whatwg/webidl] Intent to use constructor steps (Issue #1530) (Monday, 13 October)

glatengcatabay-dotcom

• Re: [whatwg/webidl] Add disposer and async_disposer (PR #1488) (Sunday, 12 October)

Guy Bedford

• [whatwg/encoding] Text(De|En)coder in WorkletGlobalScope (Issue #356) (Thursday, 2 October)

Henrik Skupin

• Re: [w3c/permissions] Add an optional `topLevelOrigin` argument to `permissions.setPermission` WebDriver BiDi command (Issue #450) (Monday, 13 October)

ja-y-son

• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Saturday, 11 October)
• Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412) (Friday, 10 October)
• Re: [whatwg/dom] custom element registry mutability in an element (Issue #1414) (Friday, 10 October)
• [whatwg/dom] custom element registry mutability in an element (Issue #1414) (Thursday, 9 October)
• Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412) (Thursday, 9 October)
• [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412) (Wednesday, 8 October)

Jacques Newman

• Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152) (Tuesday, 14 October)

Jake Archibald

• [whatwg/streams] Allow error to be provided to reader.releaseLock() (Issue #1358) (Tuesday, 7 October)

jalonthomas

• [w3c/permissions] Use embeddedOrigin instead of topLevelOrigin in setPermission (PR #469) (Wednesday, 1 October)

James M Snell

• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Sunday, 5 October)

jamiewalch

• Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243) (Wednesday, 15 October)
• Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243) (Wednesday, 15 October)
• [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243) (Wednesday, 1 October)

Jeffrey Yasskin

• Re: [w3ctag/design-reviews] [wg/json-ld] JSON-LD Working Group Charter (Issue #1150) (Wednesday, 15 October)
• Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134) (Thursday, 9 October)
• Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134) (Thursday, 9 October)
• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Thursday, 9 October)
• Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135) (Tuesday, 7 October)
• Re: [w3ctag/design-reviews] [wg/json-ld] JSON-LD Working Group Charter (Issue #1150) (Monday, 6 October)

Jelle Raaijmakers

• Re: [w3c/editing] Nested editing hosts do not need to be wrapped in insertParagraph (Issue #490) (Friday, 17 October)

Jeremy Scheff

• [w3c/IndexedDB] In "object store storage operation", be more explicit about how to handle ConstraintError from an index (Issue #477) (Monday, 13 October)

Joe Pea

• Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408) (Friday, 3 October)
• Re: [whatwg/dom] [ElementInternals] `ElementInternals.shadowRoot` is `null` but `this.shadowRoot` is not (its a `ShadowRoot`) (Issue #1365) (Wednesday, 1 October)

Johannes Wilm

• Re: [w3c/uievents] Add new property to `InputEvent` to determine whether the text being input by IME has just been confirmed without help of `compositionend` (Issue #403) (Monday, 13 October)
• Re: [w3c/uievents] Add new property to `InputEvent` to determine whether the text being input by IME has just been confirmed without help of `compositionend` (Issue #403) (Monday, 13 October)
• Re: [w3c/editing] July 2025 meeting cancelled due to summer holidays (Issue #489) (Thursday, 9 October)
• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) (Thursday, 9 October)

Josh Matthews

• Re: [whatwg/fetch] Throw `SecurityError` on non-trustworthy URLs in `fetchLater` (PR #1858) (Thursday, 2 October)

Julian Descottes

• [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) (Wednesday, 1 October)

Julian Dominguez-Schatz

• [w3c/IndexedDB] Explicitly define how to handle `queryOrOptions` being omitted in `getAll`/`getAllKeys` (Issue #475) (Saturday, 4 October)

Julien Wajsberg

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

Justin Fagnani

• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Friday, 10 October)
• Re: [WICG/webcomponents] Observe ShadowRoot attachment (#204) (Tuesday, 7 October)
• Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406) (Tuesday, 7 October)
• Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406) (Tuesday, 7 October)
• Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408) (Thursday, 2 October)
• Re: [whatwg/dom] attachShadow default custom element registry (Issue #1407) (Wednesday, 1 October)

Keith Cirkel

• Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406) (Wednesday, 15 October)
• Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409) (Saturday, 4 October)

Kevin Gibbons

• Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861) (Thursday, 2 October)

khanmoin96969-png

• [whatwg/url] 50337978316 (Issue #885) (Thursday, 9 October)
• Re: [whatwg/url] 9930017996@Upi (Issue #884) (Thursday, 9 October)
• Re: [whatwg/url] 9930017996@Upi (Issue #884) (Thursday, 9 October)
• [whatwg/url] 9930017996@Upi (Issue #884) (Thursday, 9 October)

Lea Verou

• Re: [WICG/webcomponents] Observe ShadowRoot attachment (#204) (Tuesday, 7 October)
• Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287) (Tuesday, 7 October)

Lola

• Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support Structured JSON Responses from IdPs (Issue #1147) (Monday, 13 October)
• Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) (Monday, 13 October)
• Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) (Monday, 13 October)
• Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support showing third-party iframe origins in the UI (Issue #1145) (Thursday, 9 October)
• Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support showing third-party iframe origins in the UI (Issue #1145) (Thursday, 9 October)

Luke Warlow

• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) (Thursday, 9 October)
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) (Thursday, 9 October)
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) (Thursday, 9 October)
• Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861) (Thursday, 2 October)

Maksim Sadym

• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Friday, 10 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Thursday, 9 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Thursday, 9 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Wednesday, 8 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Wednesday, 8 October)

Marcos Cáceres

• Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273) (Friday, 17 October)
• Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273) (Friday, 17 October)
• [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273) (Friday, 17 October)
• Re: [w3c/screen-orientation] TPAC 2025 status report (Issue #258) (Friday, 17 October)
• [w3c/screen-orientation] Add hidden document monitoring in parallel orientation lock steps (PR #272) (Friday, 17 October)
• [w3c/screen-orientation] Standardize window.orientation API (PR #271) (Friday, 17 October)
• [w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270) (Friday, 17 October)
• Re: [w3c/screen-orientation] Missing tasks in parallel steps in Screen Orientation (Issue #253) (Friday, 17 October)
• Re: [w3c/screen-orientation] Missing tasks in parallel steps in Screen Orientation (Issue #253) (Friday, 17 October)
• Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269) (Friday, 17 October)
• Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269) (Friday, 17 October)
• Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269) (Friday, 17 October)
• Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269) (Friday, 17 October)
• Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269) (Friday, 17 October)
• Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269) (Friday, 17 October)
• [whatwg/fullscreen] Add pending fullscreen request flag and promise to document state (PR #251) (Friday, 17 October)
• [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269) (Friday, 17 October)
• Re: [w3c/screen-orientation] Address privacy review feedback (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Address privacy review feedback (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Friday, 17 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Friday, 17 October)
• Re: [w3c/gamepad] TPAC 2025 status report (Issue #226) (Friday, 17 October)
• Re: [w3c/screen-orientation] Wording change; adjust term "clicking" to "Select" to reflect multiple ways to activate Lock/Unlock (Issue #263) (Friday, 17 October)
• Re: [w3c/screen-orientation] Editorial: change clicking to selecting (PR #265) (Friday, 17 October)
• Re: [w3c/screen-orientation] Complete self-reviews (#201) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Complete self-reviews (#201) (Thursday, 16 October)
• [w3c/screen-orientation] Fix iframe promise rejection in unloading document cleanup (PR #268) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Must natural orientation be detectable? (Issue #259) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Fingerprinting risk: users that configure their device to not permit screen locking (Issue #260) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Editorial: pre-lock conditions definition placement (Issue #261) (Thursday, 16 October)
• [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Are ScreenOrientation change events scoped as tightly as possible (Issue #262) (Thursday, 16 October)
• [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Wording change; adjust term "clicking" to "Select" to reflect multiple ways to activate Lock/Unlock (Issue #263) (Thursday, 16 October)
• [w3c/screen-orientation] Editorial: change clicking to selecting (PR #265) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Some Code Samples have code references in orange/light blue color combination which has 2.9:1 contrast (should be 4.5:1) (Issue #264) (Thursday, 16 October)
• Re: [w3c/screen-orientation] Some Code Samples have code references in orange/light blue color combination which has 2.9:1 contrast (should be 4.5:1) (Issue #264) (Thursday, 16 October)
• Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140) (Thursday, 16 October)
• Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) (Thursday, 16 October)
• Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) (Thursday, 16 October)
• Re: [w3c/uievents] Proposal: use `relatedTarget` for click events originated from labels (Issue #402) (Thursday, 16 October)
• Re: [w3ctag/design-reviews] Incubation: An `Origin` Object (Issue #1130) (Thursday, 2 October)
• Re: [w3ctag/design-reviews] Incubation: An `Origin` Object (Issue #1130) (Thursday, 2 October)
• Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140) (Thursday, 2 October)
• Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140) (Thursday, 2 October)

Masayuki Nakano

• Re: [w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404) (Friday, 17 October)
• Re: [w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404) (Friday, 17 October)
• Re: [w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404) (Friday, 17 October)
• [w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404) (Friday, 17 October)

Mason Freed

• Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400) (Friday, 10 October)
• Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400) (Friday, 10 October)
• Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409) (Tuesday, 7 October)
• Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409) (Monday, 6 October)
• Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409) (Monday, 6 October)

mathijssomers2013-arch

• Re: [w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188) (Monday, 6 October)
• Re: [w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188) (Monday, 6 October)
• Re: [w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188) (Monday, 6 October)
• Re: [w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188) (Monday, 6 October)
• [w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188) (Monday, 6 October)

Matt Reynolds

• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) (Thursday, 9 October)

Matthew Phillips

• Re: [whatwg/fetch] static method: `Response.html`? (Issue #1865) (Monday, 6 October)

Mattias Buelens

• [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Wednesday, 8 October)
• Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862) (Thursday, 2 October)
• Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862) (Thursday, 2 October)

Meghan Denny

• Re: [whatwg/webidl] Intent to use constructor steps (Issue #1530) (Monday, 13 October)
• Re: [whatwg/url] URL (Issue #886) (Monday, 13 October)
• Re: [whatwg/url] 50337978316 (Issue #885) (Thursday, 9 October)
• Re: [whatwg/url] 9930017996@Upi (Issue #884) (Thursday, 9 October)
• Re: [whatwg/dom] tetooo (Issue #1411) (Tuesday, 7 October)
• Re: [whatwg/dom] https://github.com/Teto-07/Mini-Inventory-and-Sales-Management-System/issues/new/choose (Issue #1410) (Tuesday, 7 October)
• Re: [whatwg/fetch] Http parsing Carlyluminatti (Issue #1866) (Tuesday, 7 October)

Mert Can Altin

• Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Saturday, 11 October)
• Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Sunday, 5 October)

Mike Taylor

• Re: [w3c/permissions] chore(tidy): tidy up document (PR #470) (Monday, 6 October)
• [w3c/permissions] chore(tidy): tidy up document (PR #470) (Monday, 6 October)
• Re: [w3c/permissions] Use embeddedOrigin instead of topLevelOrigin in setPermission (PR #469) (Friday, 3 October)
• Re: [w3c/permissions] Use embeddedOrigin instead of topLevelOrigin in setPermission (PR #469) (Friday, 3 October)

Mike Wasserman

• Re: [w3c/screen-orientation] Editorial: change clicking to selecting (PR #265) (Thursday, 16 October)

Mike West

• Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Tuesday, 14 October)
• Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Tuesday, 14 October)
• [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Tuesday, 14 October)
• Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135) (Thursday, 9 October)
• Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135) (Tuesday, 7 October)
• Re: [w3ctag/design-reviews] Incubation: An `Origin` Object (Issue #1130) (Thursday, 2 October)

Mohammed El Amine Larabi

• Re: [WICG/webcomponents] Proposal: Allow custom elements to be in any namespace (#634) (Saturday, 11 October)

Monica Chintala

• Re: [w3c/ServiceWorker] API to tell developers why the SW was killed (#1101) (Friday, 10 October)
• Re: [w3c/ServiceWorker] API to tell developers why the SW was killed (#1101) (Friday, 10 October)
• Re: [w3c/ServiceWorker] Add ServiceWorker.prototype.registration (#798) (Friday, 10 October)
• Re: [w3c/ServiceWorker] consider exposing self.clients on window and other worker globals (#955) (Friday, 10 October)
• Re: [w3c/ServiceWorker] Auto-cache imported scripts (#908) (Thursday, 9 October)
• Re: [w3c/ServiceWorker] Auto-cache imported scripts (#908) (Thursday, 9 October)
• Re: [w3c/ServiceWorker] Meta: move the specification to the top-level directory (#1009) (Thursday, 9 October)
• Re: [w3c/ServiceWorker] Meta: move the specification to the top-level directory (#1009) (Thursday, 9 October)
• Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794) (Thursday, 9 October)
• Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794) (Thursday, 9 October)
• Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794) (Monday, 6 October)
• Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794) (Monday, 6 October)
• Re: [w3c/ServiceWorker] Auto-cache imported scripts (#908) (Friday, 3 October)
• Re: [w3c/ServiceWorker] Expose fragments cross-origin for subresources (#910) (Friday, 3 October)
• Re: [w3c/ServiceWorker] Expose fragments cross-origin for subresources (#910) (Friday, 3 October)
• Re: [w3c/ServiceWorker] Handle Fetch "shift+reload" (#952) (Thursday, 2 October)
• Re: [w3c/ServiceWorker] Handle the quota exceeded error globally (#971) (Thursday, 2 October)
• Re: [w3c/ServiceWorker] Handle the quota exceeded error globally (#971) (Thursday, 2 October)
• Re: [w3c/ServiceWorker] Get Cache Size (#1059) (Thursday, 2 October)
• Re: [w3c/ServiceWorker] Get Cache Size (#1059) (Thursday, 2 October)
• Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794) (Thursday, 2 October)
• Re: [w3c/ServiceWorker] Move spec files to root directory and remove unused files (PR #1794) (Thursday, 2 October)
• [w3c/ServiceWorker] Move spec files to root directory and remove unused files (PR #1794) (Thursday, 2 October)

Ms2ger

• Re: [whatwg/encoding] Text(De|En)coder in WorkletGlobalScope (Issue #356) (Thursday, 2 October)

Noam Rosenthal

• Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406) (Wednesday, 15 October)
• Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406) (Wednesday, 15 October)
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) (Thursday, 9 October)
• Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852) (Wednesday, 8 October)
• Re: [whatwg/fetch] static method: `Response.html`? (Issue #1865) (Monday, 6 October)
• Re: [whatwg/fetch] static method: `Response.html`? (Issue #1865) (Monday, 6 October)
• [whatwg/fetch] static method: `Response.html`? (Issue #1865) (Monday, 6 October)
• Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134) (Thursday, 2 October)

Nolan Lawson

• [w3c/IndexedDB] Transactions should be marked as inactive during key serialization (Issue #476) (Sunday, 12 October)

Philip Jägenstedt

• Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862) (Thursday, 2 October)
• Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862) (Thursday, 2 October)
• Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861) (Thursday, 2 October)
• Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861) (Thursday, 2 October)
• Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862) (Thursday, 2 October)
• Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862) (Thursday, 2 October)
• Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861) (Thursday, 2 October)
• Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861) (Thursday, 2 October)
• [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862) (Thursday, 2 October)
• [whatwg/fetch] Convenience method to stream a response as text (Issue #1861) (Thursday, 2 October)

Rob Eisenberg

• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Saturday, 11 October)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Saturday, 11 October)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Friday, 10 October)

Robert Flack

• Re: [w3c/uievents] Click event is not fired when the node is removed and then added back (#141) (Friday, 3 October)

roraja

• Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243) (Thursday, 16 October)
• Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243) (Wednesday, 15 October)
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) (Wednesday, 1 October)
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) (Wednesday, 1 October)
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) (Wednesday, 1 October)

Ryosuke Niwa

• Re: [WICG/webcomponents] Observe ShadowRoot attachment (#204) (Tuesday, 7 October)

Sarven Capadisli

• Re: [w3ctag/design-reviews] [wg/json-ld] JSON-LD Working Group Charter (Issue #1150) (Monday, 6 October)
• Re: [w3ctag/design-reviews] Incubation: FormControlRange - Live ranges for <input> and <textarea> (Issue #1142) (Thursday, 2 October)
• Re: [w3ctag/design-reviews] Incubation: FormControlRange - Live ranges for <input> and <textarea> (Issue #1142) (Thursday, 2 October)
• Re: [w3ctag/design-reviews] [wg/json-ld] JSON-LD Working Group Charter (Issue #1150) (Wednesday, 1 October)
• Re: [w3ctag/design-reviews] [wg/json-ld] JSON-LD Working Group Charter (Issue #1150) (Wednesday, 1 October)

sb3nder

• [w3c/uievents] Proposal: use `relatedTarget` for click events originated from labels (Issue #402) (Friday, 10 October)

Schommer475

• [WICG/webcomponents] Manual slot assignment and slot elements in consuming components (Issue #1115) (Friday, 17 October)

Sergsanity-a11y

• Re: [whatwg/webidl] Pls. We are the right family (Issue #1531) (Wednesday, 15 October)
• [whatwg/webidl] Pls. We are the right family (Issue #1531) (Wednesday, 15 October)

Shunya Shishido

• [w3c/ServiceWorker] Synthetic Response via Static Routing API (Issue #1796) (Thursday, 16 October)

sideshowbarker

• Re: [whatwg/webidl] Pls. We are the right family (Issue #1531) (Wednesday, 15 October)
• Re: [whatwg/webidl] Pls. We are the right family (Issue #1531) (Wednesday, 15 October)
• Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400) (Friday, 10 October)
• Re: [whatwg/fetch] done (PR #1863) (Saturday, 4 October)
• Re: [whatwg/fetch] Susant edit (PR #1864) (Saturday, 4 October)

smaug----

• Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406) (Monday, 6 October)

stelar7

• Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478) (Friday, 17 October)
• Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478) (Friday, 17 October)
• Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478) (Friday, 17 October)
• [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478) (Wednesday, 15 October)

Stephanie Zhang

• Re: [whatwg/dom] Add FormControlRange interface (PR #1404) (Thursday, 16 October)
• Re: [whatwg/dom] Add FormControlRange interface (PR #1404) (Wednesday, 1 October)
• Re: [whatwg/dom] Add FormControlRange interface (PR #1404) (Wednesday, 1 October)

Steve Orvell

• Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413) (Thursday, 16 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413) (Sunday, 12 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Saturday, 11 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Friday, 10 October)
• Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412) (Friday, 10 October)
• Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412) (Friday, 10 October)
• Re: [whatwg/dom] custom element registry mutability in an element (Issue #1414) (Friday, 10 October)
• Re: [whatwg/dom] custom element registry mutability in an element (Issue #1414) (Thursday, 9 October)
• [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413) (Thursday, 9 October)
• Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408) (Thursday, 2 October)
• [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408) (Thursday, 2 October)

Steven Becker

• Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478) (Friday, 17 October)
• Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478) (Friday, 17 October)
• Re: [w3c/IndexedDB] TPAC 2025 status report (Issue #469) (Friday, 17 October)
• Re: [w3c/IndexedDB] TPAC 2024: Discussion Topics (Issue #422) (Friday, 17 October)
• Re: [w3c/IndexedDB] Explicitly define how to handle `queryOrOptions` being omitted in `getAll`/`getAllKeys` (Issue #475) (Friday, 17 October)
• Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478) (Friday, 17 October)

Suresh P

• Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support Structured JSON Responses from IdPs (Issue #1147) (Friday, 17 October)

Susant edit

• Re: [whatwg/fetch] Susant edit (PR #1864) (Saturday, 4 October)
• [whatwg/fetch] Susant edit (PR #1864) (Saturday, 4 October)
• [whatwg/fetch] done (PR #1863) (Saturday, 4 October)

Tatsunori Uchino

• [w3c/uievents] Add new property to `InputEvent` to determine whether (Issue #403) (Monday, 13 October)

TechnicallyWeb3

• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Sunday, 5 October)
• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Sunday, 5 October)
• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Saturday, 4 October)
• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Saturday, 4 October)
• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Saturday, 4 October)
• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Friday, 3 October)
• [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Thursday, 2 October)

Tete17

• Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Monday, 13 October)

Teto-07

• Re: [whatwg/dom] tetooo (Issue #1411) (Tuesday, 7 October)
• Re: [whatwg/dom] tetooo (Issue #1411) (Tuesday, 7 October)
• [whatwg/dom] tetooo (Issue #1411) (Tuesday, 7 October)
• Re: [whatwg/dom] https://github.com/Teto-07/Mini-Inventory-and-Sales-Management-System/issues/new/choose (Issue #1410) (Tuesday, 7 October)
• Re: [whatwg/dom] https://github.com/Teto-07/Mini-Inventory-and-Sales-Management-System/issues/new/choose (Issue #1410) (Tuesday, 7 October)
• Re: [whatwg/dom] https://github.com/Teto-07/Mini-Inventory-and-Sales-Management-System/issues/new/choose (Issue #1410) (Tuesday, 7 October)
• [whatwg/dom] https://github.com/Teto-07/Mini-Inventory-and-Sales-Management-System/issues/new/choose (Issue #1410) (Tuesday, 7 October)

The Moisrex

• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Sunday, 5 October)
• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Sunday, 5 October)
• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Saturday, 4 October)
• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Friday, 3 October)

Valentin Gosu

• Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883) (Saturday, 4 October)

Valery Zinchenko

• Re: [whatwg/dom] Proposal to improve the DOM creation api (#150) (Wednesday, 1 October)

Valtteri Laitinen

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

Victor Tan

• Re: [w3ctag/design-reviews] Reduce Accept-Language (Issue #1078) (Friday, 17 October)
• Re: [w3ctag/design-reviews] Reduce Accept-Language (Issue #1078) (Friday, 17 October)

Will Abramson

• [w3ctag/design-reviews] WG New Spec: DID Resolution (Issue #1157) (Thursday, 9 October)

Xiaocheng Hu

• Re: [w3ctag/design-reviews] Incubation: Preventing User Dictionary Leaks via ::spelling-error and ::grammar-error CSS Pseudo-Elements (Issue #1148) (Thursday, 16 October)
• Re: [w3ctag/design-reviews] Incubation: Preventing User Dictionary Leaks via ::spelling-error and ::grammar-error CSS Pseudo-Elements (Issue #1148) (Thursday, 16 October)
• Re: [w3ctag/design-reviews] WG New Spec: Direction feature for `scroll-state()` query (Issue #1153) (Thursday, 16 October)
• Re: [w3ctag/design-reviews] WG Revision: CSS Color Adjust Level 1 (Issue #1156) (Thursday, 16 October)
• Re: [w3ctag/design-reviews] WG Revision: CSS Color Adjust Level 1 (Issue #1156) (Thursday, 16 October)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] Synthetic Response via Static Routing API (Issue #1796) (Thursday, 16 October)
• Re: [w3c/ServiceWorker] Service worker client URL discrepancy (#1515) (Friday, 10 October)
• Re: [w3c/ServiceWorker] Allow the service worker to work in the background without stopping for installed PWA (Issue #1728) (Friday, 10 October)
• Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794) (Wednesday, 8 October)
• Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794) (Monday, 6 October)
• Re: [w3c/ServiceWorker] Auto-cache imported scripts (#908) (Friday, 3 October)
• Re: [w3c/ServiceWorker] A way to specify a pattern of destination URLs to hit/skip SW (#1454) (Wednesday, 1 October)
• [w3c/ServiceWorker] Need for a mechanism to detect supported conditions and sources in the SW Static Routing API (Issue #1793) (Wednesday, 1 October)
• Re: [w3c/ServiceWorker] Broken references in Service Workers Nightly (Issue #1669) (Wednesday, 1 October)
• Re: [w3c/ServiceWorker] Broken references in Service Workers Nightly (Issue #1669) (Wednesday, 1 October)
• Re: [w3c/ServiceWorker] ServiceWorker fetch fast-path (Issue #1670) (Wednesday, 1 October)
• Re: [w3c/ServiceWorker] ServiceWorker fetch fast-path (Issue #1670) (Wednesday, 1 October)

Yves Lafon

• Re: [w3ctag/design-reviews] [ig/me] Media & Entertainment Interest Group Charter (Issue #1154) (Thursday, 16 October)
• Re: [w3ctag/design-reviews] [ig/me] Media & Entertainment Interest Group Charter (Issue #1154) (Thursday, 16 October)
• Re: [w3ctag/design-reviews] Other Spec Review: TCP Socket Pool per-Top-Level-Site (Issue #1151) (Monday, 13 October)
• Re: [w3ctag/design-reviews] Other Spec Review: TCP Socket Pool per-Top-Level-Site (Issue #1151) (Monday, 13 October)

Zgroza (Luke Klimek)

• Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243) (Wednesday, 15 October)

Вадим Бударин

• Re: [w3c/ServiceWorker] Allow the service worker to work in the background without stopping for installed PWA (Issue #1728) (Friday, 10 October)
• Re: [w3c/ServiceWorker] Allow the service worker to work in the background without stopping for installed PWA (Issue #1728) (Friday, 3 October)

Last message date: Friday, 17 October 2025 23:41:20 UTC