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

1JamieGarner3

Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Tuesday, 28 October)
Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Tuesday, 28 October)

2400030206

[whatwg/fetch] Clarify handling of request body streams during redirects (Issue #1871) (Wednesday, 22 October)
[whatwg/fetch] Fix memory leak in Fetch with large stream responses (Issue #1870) (Wednesday, 22 October)

Adam Rice

Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798) (Thursday, 30 October)
Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798) (Wednesday, 29 October)
Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798) (Tuesday, 28 October)

alethkit

Re: [whatwg/dom] Define XSLTProcessor (#181) (Tuesday, 21 October)

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)

Alexander Vorobyev

Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889) (Wednesday, 29 October)
Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889) (Wednesday, 29 October)
Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889) (Wednesday, 29 October)
Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889) (Wednesday, 29 October)
Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889) (Wednesday, 29 October)
[whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889) (Wednesday, 22 October)

Alexandra Borovova

Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Thursday, 23 October)
Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Thursday, 23 October)
Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Thursday, 23 October)
Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Thursday, 23 October)
Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Wednesday, 22 October)
[whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Wednesday, 22 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)

Andrew Quan

Re: [whatwg/url] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888) (Thursday, 30 October)
[whatwg/url] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888) (Monday, 20 October)

Andrew Sutherland

Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Thursday, 30 October)
Re: [w3c/IndexedDB] treat writes to the DB that have no success handler as having called commit (Issue #482) (Thursday, 30 October)
Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Monday, 27 October)
Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Sunday, 26 October)
Re: [w3c/IndexedDB] Transactions should be marked as inactive during key serialization (Issue #476) (Monday, 20 October)

andypaicu

Re: [w3ctag/design-reviews] `<geolocation>` element (part of PEPC) (Issue #1140) (Friday, 24 October)

Anne van Kesteren

Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Friday, 31 October)
Re: [whatwg/dom] Trusted Types integration (#789) (Friday, 31 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Friday, 31 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Friday, 31 October)
Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) (Friday, 31 October)
Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) (Friday, 31 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Thursday, 30 October)
Re: [whatwg/dom] setAttributeNS incorrect context for validation (Issue #1417) (Thursday, 30 October)
Re: [whatwg/url] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888) (Thursday, 30 October)
Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Thursday, 30 October)
Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Thursday, 30 October)
Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Thursday, 30 October)
Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889) (Wednesday, 29 October)
Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Wednesday, 29 October)
Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889) (Wednesday, 29 October)
Re: [whatwg/url] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888) (Wednesday, 29 October)
Re: [whatwg/url] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888) (Wednesday, 29 October)
Re: [whatwg/dom] Autofill Event Needed (Issue #1416) (Wednesday, 29 October)
Re: [whatwg/dom] Autofill Event Needed (Issue #1416) (Wednesday, 29 October)
Re: [whatwg/dom] Define XSLTProcessor (#181) (Wednesday, 29 October)
Re: [w3c/permissions] Can permissions.setPermission not use context? (Issue #471) (Wednesday, 29 October)
Re: [whatwg/fullscreen] Add pending fullscreen request flag and promise to document state (PR #251) (Tuesday, 28 October)
[w3c/permissions] Can permissions.setPermission not use context? (Issue #471) (Thursday, 23 October)
Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Thursday, 23 October)
Re: [whatwg/fetch] `Response.redirect` should return object whose headers are mutable, as well as `Response.json` (Issue #1868) (Thursday, 23 October)
Re: [whatwg/fetch] Fix memory leak in Fetch with large stream responses (Issue #1870) (Thursday, 23 October)
Re: [whatwg/fetch] Fix memory leak in Fetch with large stream responses (Issue #1870) (Thursday, 23 October)
Re: [whatwg/fetch] Clarify handling of request body streams during redirects (Issue #1871) (Thursday, 23 October)
Re: [whatwg/fetch] Clarify handling of request body streams during redirects (Issue #1871) (Thursday, 23 October)
Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Sunday, 19 October)
Re: [whatwg/fetch] `Response.error` / `Response.redirect` should return object whose headers are mutable, as well as `Response.json` (Issue #1868) (Saturday, 18 October)
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)

armandoaguirreperez656-sketch

Re: [whatwg/storage] Add a nonce (ephemeral token) to the Storage Key (Issue #183) (Tuesday, 21 October)

Ashish-coder-gif

[whatwg/fetch] docs: add example for X-Content-Type-Options header (PR #1872) (Wednesday, 22 October)

basmatiraghman19-sketch

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

Ben Kelly

Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798) (Wednesday, 29 October)
Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798) (Wednesday, 29 October)
Re: [w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799) (Tuesday, 21 October)

Bruce B. Anderson

Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Sunday, 26 October)
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/permissions] Can permissions.setPermission not use context? (Issue #471) (Monday, 27 October)
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)

Chris Fredrickson

Re: [w3c/permissions] Can permissions.setPermission not use context? (Issue #471) (Wednesday, 29 October)
Re: [w3c/permissions] Can permissions.setPermission not use context? (Issue #471) (Tuesday, 28 October)
Re: [w3c/permissions] Can permissions.setPermission not use context? (Issue #471) (Friday, 24 October)

Christian Biesinger

Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) (Friday, 24 October)
Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) (Thursday, 23 October)
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] Incubation: Proofreader API (Issue #1146) (Thursday, 30 October)
Re: [w3c/manifest] TPAC 2025 status report (Issue #1181) (Thursday, 30 October)
Re: [w3ctag/design-reviews] Prompt API (Issue #1093) (Thursday, 30 October)
Re: [w3ctag/design-reviews] ViewTransitions: waitUntil() method (Issue #1158) (Thursday, 30 October)
Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191) (Wednesday, 29 October)
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) (Tuesday, 28 October)
Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273) (Tuesday, 28 October)
Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Address privacy review feedback (PR #266) (Tuesday, 21 October)
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)

Dark Devil

Re: [whatwg/webidl] Intent to use Constants (Issue #1535) (Wednesday, 22 October)
[whatwg/webidl] Intent to use Constants (Issue #1535) (Wednesday, 22 October)

Diego Gonzalez

Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191) (Tuesday, 28 October)
Re: [w3c/manifest] TPAC 2025 status report (Issue #1181) (Tuesday, 28 October)
Re: [w3c/gamepad] TPAC 2025 status report (Issue #226) (Monday, 27 October)

Domenic Denicola

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

Dominic Elm

Re: [w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799) (Wednesday, 22 October)
[w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799) (Tuesday, 21 October)

Dominique Hazael-Massieux

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

dujavi

[whatwg/dom] Autofill Event Needed (Issue #1416) (Monday, 27 October)

ehind67

Ehsan Toreini

Re: [w3ctag/design-reviews] Other Spec Review: Extend CSP script-src hashes (Issue #1128) (Wednesday, 29 October)
Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) (Thursday, 23 October)
Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) (Thursday, 23 October)
Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) (Thursday, 23 October)
Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135) (Wednesday, 22 October)
Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135) (Wednesday, 22 October)
Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135) (Tuesday, 7 October)

Evan Stade

Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Thursday, 30 October)
Re: [w3c/IndexedDB] Transactions should be marked as inactive during key serialization (Issue #476) (Monday, 20 October)
Re: [w3c/IndexedDB] Transactions should be marked as inactive during key serialization (Issue #476) (Monday, 20 October)

fadol83-lab

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

fergald

Re: [w3c/IndexedDB] treat writes to the DB that have no success handler as having called commit (Issue #482) (Friday, 31 October)
[w3c/IndexedDB] treat writes to the DB that have no success handler as having called commit (Issue #482) (Thursday, 30 October)

Frédéric Wang

Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Friday, 31 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)

Hanno Böck

[w3ctag/design-reviews] Reconsider W3C Recommendation status of XSLT 2.0 and XSLT 3.0 (Issue #1163) (Monday, 27 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] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888) (Monday, 20 October)
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)

Jan-Ivar Bruaroey

Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 28 October)
[whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 28 October)

Jayson Chen

Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413) (Tuesday, 28 October)
Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408) (Tuesday, 28 October)
Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413) (Wednesday, 22 October)
Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408) (Wednesday, 22 October)
Re: [whatwg/dom] custom element registry mutability in an element (Issue #1414) (Tuesday, 21 October)

Jeffrey Yasskin

Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) (Thursday, 23 October)
Re: [w3ctag/design-reviews] WG New Spec: DID Resolution (Issue #1157) (Thursday, 23 October)
Re: [w3c/screen-orientation] Are ScreenOrientation change events scoped as tightly as possible (Issue #262) (Tuesday, 21 October)
Re: [w3ctag/design-reviews] [wg/webextensions] Web Extensions Working Group (Issue #1138) (Monday, 20 October)
Re: [w3ctag/design-reviews] [wg/webextensions] Web Extensions Working Group (Issue #1138) (Monday, 20 October)
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)

Jeroen Zwartepoorte

[whatwg/dom] Allow `MutationObserver` to observe across `<slot>`s (Issue #1415) (Tuesday, 21 October)

JerryJWChan

Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191) (Friday, 31 October)
Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191) (Thursday, 30 October)
[w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191) (Sunday, 26 October)

Joe Pea

Re: [WICG/webcomponents] Reference Target "phase 2": seeking feedback and use cases (Issue #1111) (Friday, 24 October)
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)

Johann Hofmann

Re: [w3c/permissions] Can permissions.setPermission not use context? (Issue #471) (Friday, 24 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) (Thursday, 23 October)
Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Wednesday, 8 October)

Justin Fagnani

Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Wednesday, 29 October)
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)

keccake256blockchain

[whatwg/webidl] Help (Issue #1534) (Saturday, 18 October)
[whatwg/webidl] Help (Issue #1533) (Saturday, 18 October)
[whatwg/webidl] Hacker in my old account (Issue #1532) (Saturday, 18 October)

Keita Suzuki

Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Wednesday, 29 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)

Kenta Moriuchi

Re: [whatwg/fetch] `Response.redirect` should return object whose headers are mutable, as well as `Response.json` (Issue #1868) (Wednesday, 22 October)
[whatwg/fetch] `Response.error` / `Response.redirect` should return object whose headers are mutable, as well as `Response.json` (Issue #1868) (Saturday, 18 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)

L. David Baron

Re: [w3ctag/design-reviews] Reconsider W3C Recommendation status of XSLT 2.0 and XSLT 3.0 (Issue #1163) (Monday, 27 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) (Tuesday, 28 October)
Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support Structured JSON Responses from IdPs (Issue #1147) (Tuesday, 28 October)
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/dom] Trusted Types integration (#789) (Friday, 31 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Thursday, 30 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Thursday, 30 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Thursday, 30 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Thursday, 30 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Thursday, 30 October)
[whatwg/dom] setAttributeNS incorrect context for validation (Issue #1417) (Thursday, 30 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Tuesday, 28 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Tuesday, 28 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Tuesday, 28 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Tuesday, 28 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] 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] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Friday, 31 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) (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: [w3ctag/design-reviews] Prompt API (Issue #1093) (Friday, 31 October)
[w3c/manifest] chore: Add retiredDate for Kenneth Rohde Christiansen (PR #1192) (Friday, 31 October)
Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191) (Thursday, 30 October)
Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191) (Thursday, 30 October)
Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191) (Thursday, 30 October)
Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191) (Wednesday, 29 October)
Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273) (Tuesday, 28 October)
Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273) (Tuesday, 28 October)
Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191) (Tuesday, 28 October)
Re: [w3c/pointerlock] TPAC 2025 status report (Issue #103) (Tuesday, 28 October)
Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269) (Tuesday, 28 October)
Re: [w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270) (Tuesday, 28 October)
Re: [w3c/screen-orientation] Add hidden document monitoring in parallel orientation lock steps (PR #272) (Tuesday, 28 October)
Re: [w3ctag/design-reviews] `<geolocation>` element (part of PEPC) (Issue #1140) (Tuesday, 28 October)
Re: [w3c/screen-orientation] Are ScreenOrientation change events scoped as tightly as possible (Issue #262) (Friday, 24 October)
Re: [w3ctag/design-reviews] Incubation: An `Origin` Object (Issue #1130) (Friday, 24 October)
Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140) (Thursday, 23 October)
Re: [w3ctag/design-reviews] Prompt API (Issue #1093) (Wednesday, 22 October)
Re: [w3c/screen-orientation] Fix iframe promise rejection in unloading document cleanup (PR #268) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Tuesday, 21 October)
Re: [w3c/screen-orientation] chore: tidy up document (PR #274) (Tuesday, 21 October)
[w3c/screen-orientation] chore: tidy up document (PR #274) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Allow unlock() to return a promise (PR #231) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Fingerprinting risk: users that configure their device to not permit screen locking (Issue #260) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Are ScreenOrientation change events scoped as tightly as possible (Issue #262) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Use "user attention" of top-level traversable (Issue #252) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Editorial: pre-lock conditions definition placement (Issue #261) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Must natural orientation be detectable? (Issue #259) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Address privacy review feedback (PR #266) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Use "user attention" of top-level traversable (Issue #252) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Fingerprinting risk: users that configure their device to not permit screen locking (Issue #260) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Are ScreenOrientation change events scoped as tightly as possible (Issue #262) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Address privacy review feedback (PR #266) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Address privacy review feedback (PR #266) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Address privacy review feedback (PR #266) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Address privacy review feedback (PR #266) (Tuesday, 21 October)
Re: [w3c/screen-orientation] Address privacy review feedback (PR #266) (Tuesday, 21 October)
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)

Marijn Kruisselbrink

[w3ctag/design-reviews] Incubation: PWA (same-site) Origin Migration (Issue #1164) (Thursday, 30 October)
Re: [w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799) (Tuesday, 21 October)

Martin Thomson

Re: [w3ctag/design-reviews] Signature-Based Integrity. (Issue #1041) (Thursday, 30 October)

Masayuki Nakano

Re: [w3c/editing] Nested editing hosts do not need to be wrapped in insertParagraph (Issue #490) (Tuesday, 21 October)
Re: [w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404) (Saturday, 18 October)
Re: [w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404) (Saturday, 18 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)
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] TPAC 2025 status report (Issue #226) (Thursday, 30 October)
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)

Matthew Tylee Atkinson

Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152) (Wednesday, 29 October)
Re: [w3ctag/design-reviews] WG Revision: Dubbing and Audio description Profiles of TTML2 (for 2nd CRS) (Issue #1139) (Thursday, 23 October)
Re: [w3ctag/design-reviews] WG Revision: Dubbing and Audio description Profiles of TTML2 (for 2nd CRS) (Issue #1139) (Thursday, 23 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] Help (Issue #1534) (Saturday, 18 October)
Re: [whatwg/webidl] Help (Issue #1533) (Saturday, 18 October)
Re: [whatwg/webidl] Hacker in my old account (Issue #1532) (Saturday, 18 October)
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) (Sunday, 26 October)
Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Sunday, 26 October)
Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Wednesday, 22 October)
Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Tuesday, 21 October)
Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Saturday, 18 October)
Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Saturday, 18 October)
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: [w3ctag/design-reviews] Signature-Based Integrity. (Issue #1041) (Thursday, 30 October)
Re: [w3ctag/design-reviews] `<geolocation>` element (part of PEPC) (Issue #1140) (Tuesday, 28 October)
Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140) (Thursday, 23 October)
Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Wednesday, 22 October)
Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140) (Wednesday, 22 October)
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)

mohsen9876-hue

Re: [whatwg/dom] DOM Events introduction: clarify how listeners are invoked (12beda2) (Friday, 31 October)

Monica Chintala

Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Friday, 24 October)
Re: [w3c/ServiceWorker] Recovering from fetch failures (#939) (Friday, 24 October)
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)

Mustaq Ahmed

Re: [w3c/pointerlock] TPAC 2025 status report (Issue #103) (Wednesday, 22 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

Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Monday, 27 October)
Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Monday, 27 October)
Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Monday, 27 October)
Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Sunday, 26 October)
Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Saturday, 25 October)
Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Saturday, 25 October)
Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Saturday, 25 October)
[w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Saturday, 25 October)
[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)

Philippe Cloutier

Re: [w3c/uievents] Event order of onKeyDown, onKeyPress, onKeyUp, and onPaste when using pasting (CMD + v) in Mac OS X (#261) (Wednesday, 29 October)

Pierre-Antoine Champin

[w3ctag/design-reviews] WG New Spec: RDF 1.2 N-Triples (Issue #1161) (Tuesday, 21 October)
[w3ctag/design-reviews] WG New Spec: RDF 1.2 Semantics (Issue #1160) (Tuesday, 21 October)
[w3ctag/design-reviews] WG New Spec: RDF 1.2 Concepts and Abstract Data Model (Issue #1159) (Tuesday, 21 October)

Rakina Zata Amni

Re: [whatwg/fetch] New Proposal: Fetch retry (Issue #1838) (Wednesday, 22 October)

Reilly Grant

Re: [w3ctag/design-reviews] Prompt API (Issue #1093) (Thursday, 30 October)
Re: [w3ctag/design-reviews] Prompt API (Issue #1093) (Tuesday, 21 October)

Relaxx422

[w3c/ServiceWorker] E (Issue #1800) (Thursday, 30 October)

Rimas Misevičius

Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Wednesday, 29 October)
Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Wednesday, 29 October)
Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Wednesday, 29 October)
Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Wednesday, 29 October)
Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Sunday, 19 October)
Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Sunday, 19 October)
[whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Saturday, 18 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] Initial 'source' defn (PR #405) (Tuesday, 21 October)
Re: [w3c/uievents] Click event is not fired when the node is removed and then added back (#141) (Friday, 3 October)

ROKI303

Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384) (Monday, 27 October)

roraja

Re: [w3c/clipboard-apis] Remove clipboardchange event (and replace it possibly with a promise returning method) (Issue #228) (Thursday, 23 October)
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)

Shannon Booth

Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887) (Sunday, 19 October)

Shunya Shishido

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

sideshowbarker

Re: [w3c/ServiceWorker] E (Issue #1800) (Thursday, 30 October)
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)

skking9236-stack

[w3ctag/design-reviews] Incubation: template (Issue #1162) (Friday, 24 October)

smaug----

Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Thursday, 30 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Thursday, 30 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Thursday, 30 October)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268) (Thursday, 30 October)
Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406) (Monday, 6 October)

stelar7

[w3c/IndexedDB] Clarify cursor iteration predicates some more (PR #481) (Wednesday, 29 October)
[w3c/IndexedDB] `retrieve multiple items from an index` index out of bounds error (Issue #480) (Tuesday, 28 October)
Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478) (Saturday, 25 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)
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) (Friday, 31 October)
Re: [whatwg/dom] Allow `MutationObserver` to observe across `<slot>`s (Issue #1415) (Friday, 24 October)
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, 24 October)
Re: [w3c/IndexedDB] Transactions should be marked as inactive during key serialization (Issue #476) (Tuesday, 21 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)
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)

vmpstr

Re: [w3c/uievents] Initial 'source' defn (PR #405) (Tuesday, 21 October)
[w3c/uievents] Initial 'source' defn (PR #405) (Tuesday, 21 October)
Re: [w3ctag/design-reviews] ViewTransitions: waitUntil() method (Issue #1158) (Monday, 20 October)
[w3ctag/design-reviews] ViewTransitions: waitUntil() method (Issue #1158) (Monday, 20 October)

Will Abramson

Re: [w3ctag/design-reviews] WG New Spec: DID Resolution (Issue #1157) (Friday, 24 October)
[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)

Yard-nonpolitical801

Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384) (Monday, 20 October)

Yoshisato Yanagisawa

Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163) (Friday, 31 October)
Re: [w3c/ServiceWorker] Dynamic Event Handler Registration (#1156) (Friday, 31 October)
Re: [w3c/ServiceWorker] Dynamic Event Handler Registration (#1156) (Friday, 31 October)
Re: [w3c/ServiceWorker] Register HTTP header fields with IANA (#1134) (Friday, 31 October)
Re: [w3c/ServiceWorker] Make object equality of service workers clearer (#1140) (Friday, 31 October)
Re: [w3c/ServiceWorker] Make object equality of service workers clearer (#1140) (Friday, 31 October)
Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) (Friday, 31 October)
Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) (Friday, 31 October)
Re: [w3c/ServiceWorker] respondWith uses the wrong targetRealm (#1055) (Thursday, 30 October)
Re: [w3c/ServiceWorker] consider how clients.claim() should work with srcdoc iframes (#1093) (Thursday, 30 October)
Re: [w3c/ServiceWorker] Lifetime of service workers in relation to dedicated and shared workers (#1119) (Thursday, 30 October)
Re: [w3c/ServiceWorker] What does it mean to wait "for a task to be executed (including its asynchronous steps)"? (#1109) (Thursday, 30 October)
Re: [w3c/ServiceWorker] What does it mean to wait "for a task to be executed (including its asynchronous steps)"? (#1109) (Thursday, 30 October)
Re: [w3c/ServiceWorker] Write tests for MIX behaviour (#1105) (Thursday, 30 October)
Re: [w3c/ServiceWorker] Spec uses incorrect settings object when fetching a module worker (#849) (Thursday, 30 October)
Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798) (Wednesday, 29 October)
Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798) (Monday, 27 October)
Re: [w3c/ServiceWorker] TPAC 2025 status report (Issue #1787) (Friday, 24 October)
Re: [w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799) (Wednesday, 22 October)
Re: [w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799) (Wednesday, 22 October)
Re: [w3c/ServiceWorker] Support CacheStorage.match() options in SW Static Routing API cache source (Issue #1797) (Wednesday, 22 October)
Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798) (Tuesday, 21 October)
Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798) (Tuesday, 21 October)
Re: [w3c/ServiceWorker] Support CacheStorage.match() options in SW Static Routing API cache source (Issue #1797) (Tuesday, 21 October)
[w3c/ServiceWorker] Proposal: Support No-Vary-Search header in Cache API (Issue #1798) (Tuesday, 21 October)
Re: [w3c/ServiceWorker] Feature Request: Support CacheStorage.match() options in SW Static Routing API cache source (Issue #1797) (Tuesday, 21 October)
[w3c/ServiceWorker] Feature Request: Support CacheStorage.match() options in SW Static Routing API cache source (Issue #1797) (Tuesday, 21 October)
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)

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

Last message date: Friday, 31 October 2025 16:40:15 UTC