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

Adam Rice

• Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798) (Friday, 7 November)

Alexandra Borovova

• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Wednesday, 19 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Wednesday, 19 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Wednesday, 19 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Tuesday, 18 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Tuesday, 18 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Tuesday, 18 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Tuesday, 18 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Monday, 10 November)

Alexey Rodionov

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

Andrew Sutherland

• Re: [w3c/ServiceWorker] Preserve sec-fetch-dest for passed navigate requests (Issue #1803) (Wednesday, 26 November)
• Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215) (Wednesday, 12 November)
• Re: [w3c/ServiceWorker] Add name param to Clients.openWindow() method (#711) (Friday, 7 November)
• Re: [w3c/ServiceWorker] Need for a mechanism to detect supported conditions and sources in the SW Static Routing API (Issue #1793) (Friday, 7 November)
• Re: [w3c/ServiceWorker] Preserve sec-fetch-dest for passed navigate requests (Issue #1803) (Friday, 7 November)
• Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798) (Friday, 7 November)
• Re: [w3c/ServiceWorker] Support CacheStorage.match() options in SW Static Routing API cache source (Issue #1797) (Friday, 7 November)
• Re: [w3c/ServiceWorker] A way to specify a pattern of destination URLs to hit/skip SW (#1454) (Thursday, 6 November)
• Re: [w3c/IndexedDB] treat writes to the DB that have no success handler as having called commit (Issue #482) (Monday, 3 November)

Andrew Williams

• Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Tuesday, 25 November)
• Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Tuesday, 25 November)
• Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Tuesday, 25 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Tuesday, 25 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Tuesday, 25 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Tuesday, 25 November)
• Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Thursday, 20 November)
• Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Thursday, 20 November)
• [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Thursday, 20 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Wednesday, 19 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Wednesday, 19 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Wednesday, 19 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Wednesday, 19 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Wednesday, 19 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Wednesday, 19 November)
• Re: [w3c/FileAPI] Top-level navigations to blob URLs with media mime types result in resource load subject to partitioning (Issue #210) (Friday, 14 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Friday, 14 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Friday, 14 November)
• [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Friday, 14 November)

Anne van Kesteren

• Re: [whatwg/dom] setAttributeNS incorrect context for validation (Issue #1417) (Friday, 28 November)
• Re: [whatwg/dom] Correct setAttributeNS() validation context (PR #1434) (Friday, 28 November)
• Re: [whatwg/dom] Editorial: modernize mutation observers (PR #1436) (Friday, 28 November)
• [whatwg/dom] Editorial: modernize mutation observers (PR #1436) (Friday, 28 November)
• [whatwg/dom] Editorial: modernize convert nodes into a node (PR #1435) (Friday, 28 November)
• Re: [whatwg/webidl] When creating a global object the realm is not yet initialized (Issue #1547) (Friday, 28 November)
• Re: [whatwg/dom] MutationObserver attribute filter ignores attributes with a namespace (Issue #1364) (Friday, 28 November)
• Re: [whatwg/dom] MutationObserver attribute filter ignores attributes with a namespace (Issue #1364) (Friday, 28 November)
• Re: [whatwg/dom] Scoped custom element registry issues (Issue #1379) (Friday, 28 November)
• Re: [whatwg/dom] Scoped custom element registry issues (Issue #1379) (Friday, 28 November)
• Re: [whatwg/dom] Correct setAttributeNS() validation context (PR #1434) (Friday, 28 November)
• [whatwg/dom] Correct setAttributeNS() validation context (PR #1434) (Friday, 28 November)
• Re: [whatwg/dom] Support `getElementsByTagName(tag)` for DocumentFragment (Issue #1382) (Friday, 28 November)
• [whatwg/dom] Address infinite loop in TreeWalker's nextNode() (PR #1433) (Friday, 28 November)
• Re: [whatwg/dom] Editorial: modernize Traversal (PR #1432) (Friday, 28 November)
• [whatwg/dom] Editorial: modernize Traversal (PR #1432) (Friday, 28 November)
• Re: [whatwg/dom] Make DOMTokenList's supported token concept also depend on element (PR #1431) (Friday, 28 November)
• [whatwg/dom] Make DOMTokenList's supported token concept also depend on element (PR #1431) (Friday, 28 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Friday, 28 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Friday, 28 November)
• Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430) (Friday, 28 November)
• Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430) (Friday, 28 November)
• Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430) (Friday, 28 November)
• Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430) (Friday, 28 November)
• [whatwg/webidl] Create an operation does not care about [LegacyLenientThis] (PR #1548) (Friday, 28 November)
• [whatwg/webidl] When creating a global object the realm is not yet initialized (Issue #1547) (Friday, 28 November)
• Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430) (Thursday, 27 November)
• Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430) (Thursday, 27 November)
• [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430) (Thursday, 27 November)
• Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876) (Thursday, 27 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Thursday, 27 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Thursday, 27 November)
• Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Thursday, 27 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Thursday, 27 November)
• Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Thursday, 27 November)
• Re: [whatwg/dom] Adopting children of an intentional null shadow root goes wrong (Issue #1429) (Thursday, 27 November)
• [whatwg/dom] Adopting children of an intentional null shadow root goes wrong (Issue #1429) (Thursday, 27 November)
• [whatwg/dom] adoptNode() needs to account for <iframe> and friends (Issue #1428) (Wednesday, 26 November)
• [whatwg/dom] Editorial: make adopt traverse the tree less (PR #1427) (Wednesday, 26 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 26 November)
• Re: [w3c/ServiceWorker] Better hooks for functional events (Issue #1808) (Wednesday, 26 November)
• Re: [w3c/push-api] Editorial: replace RFC7231 reference with RFC9110 (PR #415) (Tuesday, 25 November)
• Re: [w3c/push-api] Normative references to discontinued specs in Push API (Issue #390) (Tuesday, 25 November)
• Re: [w3c/push-api] Holding "Fire a Functional Event" incorrectly (Issue #389) (Tuesday, 25 November)
• [w3c/ServiceWorker] Better hooks for functional events (Issue #1808) (Tuesday, 25 November)
• [w3c/push-api] Editorial: replace RFC7231 reference with RFC9110 (PR #415) (Tuesday, 25 November)
• Re: [w3c/push-api] PushMessageData is poorly defined and seems broken (Issue #380) (Tuesday, 25 November)
• Re: [w3c/push-api] PushMessageData is poorly defined and seems broken (Issue #380) (Tuesday, 25 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Tuesday, 25 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Tuesday, 25 November)
• Re: [whatwg/dom] Editorial: modernize mutation algorithms (PR #1426) (Tuesday, 25 November)
• Re: [whatwg/dom] Editorial: modernize mutation algorithms (PR #1426) (Tuesday, 25 November)
• Re: [whatwg/dom] Editorial: modernize mutation algorithms (PR #1426) (Tuesday, 25 November)
• Re: [whatwg/dom] Editorial: modernize mutation algorithms (PR #1426) (Tuesday, 25 November)
• Re: [whatwg/dom] Editorial: modernize mutation algorithms (PR #1426) (Tuesday, 25 November)
• [whatwg/dom] Editorial: modernize mutation algorithms (PR #1426) (Tuesday, 25 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Tuesday, 25 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Tuesday, 25 November)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413) (Tuesday, 25 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Tuesday, 25 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Tuesday, 25 November)
• Re: [whatwg/webidl] Change enum syntax to reflect real constraints (Issue #1545) (Tuesday, 25 November)
• Re: [w3c/push-api] Remove the note that suggests subscribe()'s step order does not matter (PR #413) (Monday, 24 November)
• Re: [w3c/push-api] Remove the note that suggests subscribe()'s step order does not matter (PR #413) (Monday, 24 November)
• Re: [whatwg/fetch] Body's json(): add reviver argument (#104) (Monday, 24 November)
• Re: [whatwg/fetch] Body's json(): add reviver argument (#104) (Monday, 24 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Monday, 24 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Monday, 24 November)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Monday, 24 November)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Monday, 24 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Monday, 24 November)
• Re: [whatwg/streams] Editorial: fix ref for break (PR #1361) (Monday, 24 November)
• Re: [whatwg/streams] Editorial: fix ref for break (PR #1361) (Monday, 24 November)
• Re: [w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807) (Friday, 21 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Friday, 21 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Friday, 21 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Friday, 21 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Friday, 21 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Friday, 21 November)
• Re: [w3c/ServiceWorker] Preserve sec-fetch-dest for passed navigate requests (Issue #1803) (Thursday, 20 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Thursday, 20 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Thursday, 20 November)
• Re: [w3c/clipboard-apis] Standardize Clipboard Source url (Issue #244) (Thursday, 20 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Thursday, 20 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Thursday, 20 November)
• Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Thursday, 20 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Thursday, 20 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Thursday, 20 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Wednesday, 19 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Wednesday, 19 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Wednesday, 19 November)
• Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Wednesday, 19 November)
• Re: [whatwg/fetch] Add a "webtransport" request mode (Issue #1808) (Wednesday, 19 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Wednesday, 19 November)
• [whatwg/fetch] Support serverCertificateHashes in obtain a connection for WebTransport (Issue #1880) (Wednesday, 19 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Wednesday, 19 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Wednesday, 19 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Wednesday, 19 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Wednesday, 19 November)
• Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Wednesday, 19 November)
• Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Wednesday, 19 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• [w3c/push-api] Remove the note that suggests subscribe()'s step order does not matter (PR #413) (Tuesday, 18 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Tuesday, 18 November)
• Re: [w3c/FileAPI] Top-level navigations to blob URLs with media mime types result in resource load subject to partitioning (Issue #210) (Tuesday, 18 November)
• Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839) (Tuesday, 18 November)
• Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Tuesday, 18 November)
• Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] docs: add example for X-Content-Type-Options header (PR #1872) (Tuesday, 18 November)
• Re: [whatwg/fetch] docs: add example for X-Content-Type-Options header (PR #1872) (Tuesday, 18 November)
• Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839) (Tuesday, 18 November)
• Re: [whatwg/fetch] Allow user agents to use more permissive header validation in extensions (Issue #1878) (Tuesday, 18 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Tuesday, 18 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Tuesday, 18 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Tuesday, 18 November)
• Re: [w3c/push-api] Does PushManager subscribe() need transient activation check? (Issue #346) (Tuesday, 18 November)
• Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412) (Friday, 14 November)
• Re: [whatwg/dom] CDATA section can be imported into HTML document (Issue #1420) (Friday, 14 November)
• Re: [whatwg/dom] `compareDocumentPosition` should allow comparison of elements in the same shadow-including root (#320) (Thursday, 13 November)
• Re: [whatwg/dom] `compareDocumentPosition` should allow comparison of elements in the same shadow-including root (#320) (Thursday, 13 November)
• Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215) (Wednesday, 12 November)
• Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215) (Wednesday, 12 November)
• Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839) (Wednesday, 12 November)
• Re: [whatwg/webidl] async_iterable not exported (Issue #1540) (Wednesday, 12 November)
• Re: [whatwg/webidl] Editorial: export async_iterable (PR #1541) (Wednesday, 12 November)
• Re: [whatwg/webidl] Editorial: export async_iterable (PR #1541) (Wednesday, 12 November)
• Re: [whatwg/dom] "Set an existing attribute value" algorithm checks twice if attributes element is null (Issue #1421) (Wednesday, 12 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Tuesday, 11 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Tuesday, 11 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Tuesday, 11 November)
• Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737) (Monday, 10 November)
• Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876) (Monday, 10 November)
• Re: [whatwg/webidl] Parameter types that must be JSON serializable (Issue #1537) (Thursday, 6 November)
• Re: [whatwg/webidl] Parameter types that must be JSON serializable (Issue #1537) (Thursday, 6 November)
• Re: [whatwg/dom] Element's display property affects composedPath() calculation unexpectedly (Issue #1419) (Wednesday, 5 November)
• Re: [whatwg/dom] Element's display property affects composedPath() calculation unexpectedly (Issue #1419) (Wednesday, 5 November)
• Re: [whatwg/dom] Element's display property affects composedPath() calculation unexpectedly (Issue #1419) (Wednesday, 5 November)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Tuesday, 4 November)
• Re: [whatwg/encoding] Text(De|En)coder in WorkletGlobalScope (Issue #356) (Monday, 3 November)

Ari Chivukula

• Re: [w3ctag/design-reviews] Private Proof API (Issue #1071) (Wednesday, 12 November)
• Re: [w3ctag/design-reviews] Private Proof API (Issue #1071) (Wednesday, 12 November)
• Re: [w3ctag/design-reviews] Early Design Review: Partitioned Popins (Issue #956) (Wednesday, 12 November)

ASISBUSINESS ECI GROUP

• Re: [w3c/push-api] check and consume user activation (PR #348) (Sunday, 9 November)

Barry Pollard

• [whatwg/fetch] Allow updating of render-blocking status (Issue #1875) (Wednesday, 5 November)

Ben Francis

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

Ben Kelly

• Re: [w3c/ServiceWorker] Preserve sec-fetch-dest for passed navigate requests (Issue #1803) (Thursday, 20 November)

boselyjerry158-blip

• Re: [whatwg/webidl] Driver LLC (Issue #1544) (Friday, 21 November)
• [whatwg/webidl] Driver LLC (Issue #1544) (Friday, 21 November)
• [whatwg/webidl] Intent to use Constants (Issue #1543) (Friday, 21 November)

Brett Zamir

• Re: [w3c/IndexedDB] TPAC 2025 status report (Issue #469) (Tuesday, 4 November)

Bruce B. Anderson

• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Saturday, 1 November)

Carla Archuleta

• [whatwg/fetch] FETCHING (Issue #1882) (Friday, 21 November)

carlosjeurissen

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

Christian Liebel

• Re: [w3ctag/design-reviews] [ig/webai] Web&AI Interest Group (Issue #1149) (Thursday, 27 November)
• Re: [w3ctag/design-reviews] [ig/webai] Web&AI Interest Group (Issue #1149) (Thursday, 27 November)
• Re: [w3c/manifest] TPAC 2025 status report (Issue #1181) (Thursday, 27 November)

Christian Stewart

• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Monday, 10 November)
• Re: [w3c/ServiceWorker] should FetchEvent.request.signal reflect abort status of outer request? (#1544) (Monday, 10 November)

Copilot

• Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273) (Wednesday, 26 November)

Daniel Herr

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

Daniel Murphy

• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Thursday, 13 November)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Tuesday, 11 November)
• Re: [w3c/manifest] Web Manifest Overrides (Issue #1045) (Tuesday, 11 November)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Tuesday, 11 November)
• Re: [w3c/manifest] Web Install (Issue #1178) (Tuesday, 11 November)
• [w3c/manifest] Navigation Capturing / Management (Issue #1196) (Monday, 10 November)
• [w3c/manifest] WPT/dev testability: Create way to test features related to / currently dependent on install (Issue #1194) (Monday, 10 November)
• [w3c/manifest] Manifest-url-only install (Issue #1193) (Thursday, 6 November)

David A

• [w3ctag/design-reviews] WG New Spec: Scroll-Triggered Animations (Issue #1167) (Monday, 10 November)

davidsgrogan

• [w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172) (Monday, 24 November)

daxpedda

• Re: [whatwg/encoding] Text(De|En)coder in WorkletGlobalScope (Issue #356) (Monday, 3 November)

Diego Gonzalez

• [w3c/manifest] Manifest Editors Meetings (Issue #1198) (Monday, 17 November)
• [w3c/manifest] Discussion on potential uses for Vibration/Haptics? (Issue #1197) (Monday, 10 November)

Domenic Denicola

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

Dominic Farolino

• Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876) (Tuesday, 25 November)
• Re: [w3c/FileAPI] Top-level navigations to blob URLs with media mime types result in resource load subject to partitioning (Issue #210) (Wednesday, 19 November)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Wednesday, 19 November)
• [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876) (Sunday, 9 November)

Dominique Hazael-Massieux

• Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804) (Monday, 17 November)
• [w3c/ServiceWorker] Problem with spec-prod/gh-pages mismatch (Issue #1806) (Monday, 17 November)
• Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804) (Monday, 17 November)

dontcallmedom-bot

• [w3c/ServiceWorker] Broken links in Service Workers Nightly (Issue #1801) (Monday, 3 November)

Edgar Chen

• Re: [w3c/clipboard-apis] Clipboard API for text/html serialization and associated style attributes. (Issue #246) (Thursday, 27 November)

Emilio Cobos Álvarez

• Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273) (Tuesday, 11 November)

Erik Witt

• [w3c/ServiceWorker] Preserve sec-fetch-dest for passed navigate requests (Issue #1803) (Friday, 7 November)

Evan Stade

• Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Thursday, 6 November)

fergald

• Re: [whatwg/fetch] New Proposal: Fetch retry (Issue #1838) (Wednesday, 19 November)

Frederik Braun

• Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Wednesday, 19 November)

Gary Kacmarcik

• Re: [w3c/uievents] TPAC 2025 status report (Issue #399) (Monday, 10 November)

helo-sky

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

Henrik Skupin

• Re: [w3c/permissions] WebDriver: Make it possible to pass a different origin to "Set Permission" (Issue #419) (Friday, 21 November)

husseinyusuf492-max

• [whatwg/url] Hussein (Issue #891) (Wednesday, 19 November)
• [whatwg/url] H-Y-O (Issue #890) (Wednesday, 19 November)

Igor Sheludko

• [whatwg/webidl] Issues with legacy platform object [[Set]] (Issue #1536) (Monday, 3 November)

Jake Archibald

• Re: [whatwg/streams] Allow error to be provided to reader.releaseLock() (Issue #1358) (Sunday, 23 November)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Thursday, 20 November)
• [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Thursday, 20 November)

James Babcock

• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Tuesday, 4 November)

James Craig

• [w3c/FileAPI] Web Share API images have optional title, but seem to be missing alt. (Issue #215) (Wednesday, 12 November)

Jan-Ivar Bruaroey

• [whatwg/fetch] Fill in CONNECT pseudo-headers automatically (e.g. from request mode) (Issue #1881) (Friday, 21 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873) (Tuesday, 18 November)

Jayson Chen

• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 26 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 26 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Tuesday, 25 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Tuesday, 25 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Monday, 24 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Monday, 24 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Monday, 24 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Friday, 21 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Friday, 21 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Friday, 21 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Friday, 21 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Thursday, 20 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Wednesday, 19 November)
• [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Tuesday, 18 November)
• [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Monday, 17 November)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413) (Thursday, 13 November)

Jeffrey Yasskin

• Re: [w3ctag/design-reviews] WG New Spec: Scroll-Triggered Animations (Issue #1167) (Wednesday, 19 November)
• Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013) (Wednesday, 19 November)
• Re: [w3ctag/design-reviews] Explicitly tell people to use the Other Spec Review template for non-WG-driven reviews (PR #1168) (Friday, 14 November)
• [w3ctag/design-reviews] Explicitly tell people to use the Other Spec Review template for non-WG-driven reviews (PR #1168) (Tuesday, 11 November)

Jeric-RMR

• [whatwg/fetch] Client report (Issue #1877) (Tuesday, 11 November)

Jimmy Wärting

• Re: [whatwg/fetch] Proposal: response.base64() (Issue #1800) (Saturday, 22 November)

jmdyck

• Re: [whatwg/webidl] When creating a global object the realm is not yet initialized (Issue #1547) (Friday, 28 November)
• Re: [whatwg/webidl] When creating a global object the realm is not yet initialized (Issue #1547) (Friday, 28 November)

Joe Pea

• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)

Johannes Wilm

• Re: [w3c/clipboard-apis] Add privacy considerations for the clipboardchange event (Issue #230) (Monday, 24 November)
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event API specification (PR #239) (Monday, 24 November)
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event API specification (PR #239) (Monday, 24 November)
• Re: [w3c/editing] Add ability to control native undo/redo stack (Issue #509) (Tuesday, 18 November)
• Re: [w3c/editing] Safari/Chrome Desktop: Caret movement with up/down arrow keys breaks when DOM is constructed programmatically (Issue #513) (Tuesday, 18 November)
• Re: [w3c/editing] Add repro for #512 and fixes for #497 (PR #514) (Tuesday, 18 November)
• Re: [w3c/editing] Add repro for #512 and fixes for #497 (PR #514) (Tuesday, 18 November)
• Re: [w3c/editing] Add repro for #512 and fixes for #497 (PR #514) (Tuesday, 18 November)
• Re: [w3c/editing] Expose event.getTargetRanges() in oncompositionstart (and possibly oncompositionend as well) (Issue #511) (Tuesday, 18 November)
• Re: [w3c/editing] Repros (PR #512) (Monday, 17 November)
• Re: [w3c/editing] Repros (PR #512) (Monday, 17 November)
• Re: [w3c/clipboard-apis] Update Editor List - Add New Editors and Move Former Editors (PR #245) (Friday, 14 November)

Julien Cayzac

• [w3c/screen-orientation] "natural" is ambiguous (Issue #275) (Tuesday, 11 November)

juner

• [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359) (Saturday, 15 November)

jurahanmisnan225-pixel

• Re: [whatwg/webidl] Intent to use Constants (Issue #1538) (Sunday, 9 November)
• Re: [whatwg/webidl] Intent to use Constants (Issue #1538) (Sunday, 9 November)
• [whatwg/webidl] Intent to use Constants (Issue #1538) (Sunday, 9 November)

Justin Fagnani

• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Friday, 14 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Thursday, 13 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Thursday, 13 November)
• Re: [whatwg/dom] `compareDocumentPosition` should allow comparison of elements in the same shadow-including root (#320) (Wednesday, 12 November)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Wednesday, 12 November)
• Re: [whatwg/dom] Proposal to improve the DOM creation api (#150) (Monday, 10 November)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Sunday, 9 November)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Sunday, 9 November)
• Re: [WICG/webcomponents] Idea: A tree-aware task scheduler (Issue #1055) (Sunday, 9 November)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Sunday, 9 November)

Kagami Sascha Rosylight

• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Friday, 28 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Friday, 28 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Friday, 28 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Friday, 28 November)
• Re: [w3c/push-api] Editorial: replace RFC7231 reference with RFC9110 (PR #415) (Tuesday, 25 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Tuesday, 25 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Tuesday, 25 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Tuesday, 25 November)
• [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Monday, 24 November)
• Re: [w3c/push-api] Remove the note that suggests subscribe()'s step order does not matter (PR #413) (Monday, 24 November)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Friday, 21 November)
• Re: [w3c/push-api] Does PushManager subscribe() need transient activation check? (Issue #346) (Tuesday, 18 November)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Wednesday, 12 November)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Wednesday, 12 November)
• Re: [whatwg/webidl] Editorial: export async_iterable (PR #1541) (Tuesday, 11 November)

Karl Dubost

• Re: [w3c/clipboard-apis] Clipboard API for text/html serialization and associated style attributes. (Issue #246) (Friday, 28 November)
• Re: [w3c/clipboard-apis] Clipboard API for text/html serialization and associated style attributes. (Issue #246) (Friday, 28 November)
• [w3c/clipboard-apis] Clipboard API for text/html serialization and associated style attributes. (Issue #246) (Thursday, 20 November)
• Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215) (Thursday, 13 November)

Keita Suzuki

• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Friday, 28 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Thursday, 27 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Thursday, 27 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Thursday, 20 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Thursday, 20 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Thursday, 20 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Thursday, 20 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Monday, 17 November)

Keith Cirkel

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

Kevin Gibbons

• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Thursday, 20 November)

khimb8889-cmyk

• [whatwg/dom] Facebook page (Issue #1418) (Sunday, 2 November)

konginit

• [whatwg/webidl] Intent to use Constants /1 (Issue #1546) (Tuesday, 25 November)

Lea Verou

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Friday, 14 November)
• Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Friday, 14 November)
• [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) (Friday, 14 November)
• Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Friday, 14 November)
• Re: [whatwg/dom] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #1189) (Friday, 14 November)
• Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287) (Wednesday, 12 November)

Luke Warlow

• Re: [whatwg/dom] Correct setAttributeNS() validation context (PR #1434) (Friday, 28 November)
• Re: [whatwg/dom] Correct setAttributeNS() validation context (PR #1434) (Friday, 28 November)
• Re: [whatwg/dom] Correct setAttributeNS() validation context (PR #1434) (Friday, 28 November)

Marcos Cáceres

• Re: [w3c/manifest] Web Install (Issue #1178) (Thursday, 27 November)
• Re: [w3c/manifest] chore: Add retiredDate for Kenneth Rohde Christiansen (PR #1192) (Thursday, 27 November)
• Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273) (Wednesday, 26 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Wednesday, 26 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Wednesday, 26 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Wednesday, 26 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Wednesday, 26 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Wednesday, 26 November)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Wednesday, 26 November)
• Re: [w3c/pointerlock] TPAC 2025 status report (Issue #103) (Wednesday, 12 November)
• Re: [w3c/screen-orientation] TPAC 2025 status report (Issue #258) (Wednesday, 12 November)
• Re: [w3c/IndexedDB] TPAC 2025 status report (Issue #469) (Wednesday, 12 November)
• Re: [w3c/gamepad] TPAC 2025 status report (Issue #226) (Wednesday, 12 November)
• Re: [w3c/push-api] TPAC 2025 status report (Issue #404) (Wednesday, 12 November)
• Re: [w3c/FileAPI] TPAC 2025 status report (Issue #211) (Wednesday, 12 November)
• Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215) (Wednesday, 12 November)
• Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273) (Tuesday, 11 November)
• Re: [w3c/screen-orientation] Promise for unlock()? (#104) (Tuesday, 11 November)
• Re: [w3c/screen-orientation] Promise for unlock()? (#104) (Tuesday, 11 November)
• Re: [w3c/screen-orientation] Allow unlock() to return a promise (PR #231) (Tuesday, 11 November)
• Re: [w3c/screen-orientation] Allow unlock() to return a promise (PR #231) (Tuesday, 11 November)
• Re: [w3c/screen-orientation] Require a gesture? (Issue #210) (Tuesday, 11 November)
• Re: [w3c/screen-orientation] Require a gesture? (Issue #210) (Tuesday, 11 November)
• Re: [w3c/screen-orientation] Consume user activation (PR #218) (Tuesday, 11 November)
• Re: [w3c/screen-orientation] Consume user activation (PR #218) (Tuesday, 11 November)
• Re: [w3c/screen-orientation] Standardize window.orientation API (PR #271) (Tuesday, 11 November)
• Re: [w3c/screen-orientation] Standardize window.orientation API (PR #271) (Tuesday, 11 November)
• Re: [whatwg/webidl] Editorial: export async_iterable (PR #1541) (Tuesday, 11 November)
• [whatwg/webidl] Editorial: export async_iterable (PR #1541) (Tuesday, 11 November)
• Re: [w3ctag/design-reviews] Prompt API (Issue #1093) (Tuesday, 11 November)
• Re: [w3ctag/design-reviews] Prompt API (Issue #1093) (Tuesday, 11 November)
• [whatwg/webidl] async_iterable not exported (Issue #1540) (Tuesday, 11 November)
• Re: [w3c/manifest] Add API to retrieve document's computed manifest (Issue #1179) (Thursday, 6 November)
• Re: [w3ctag/design-reviews] `<geolocation>` element (part of PEPC) (Issue #1140) (Thursday, 6 November)
• Re: [w3ctag/design-reviews] `<geolocation>` element (part of PEPC) (Issue #1140) (Thursday, 6 November)
• Re: [w3c/gamepad] TPAC 2025 status report (Issue #226) (Wednesday, 5 November)

Marijn Kruisselbrink

• Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215) (Wednesday, 12 November)
• Re: [w3c/FileAPI] TPAC 2025 status report (Issue #211) (Sunday, 9 November)

Martin Thomson

• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Tuesday, 25 November)
• [whatwg/webidl] Change enum syntax to reflect real constraints (Issue #1545) (Tuesday, 25 November)
• Re: [w3ctag/design-reviews] Explicitly tell people to use the Other Spec Review template for non-WG-driven reviews (PR #1168) (Wednesday, 12 November)

Masayuki Nakano

• Re: [w3c/editing] Expose event.getTargetRanges() in oncompositionstart (and possibly oncompositionend as well) (Issue #511) (Tuesday, 18 November)

Mason Freed

• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Thursday, 13 November)

Mateusz Krzeszowiak

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

Mattias Buelens

• Re: [whatwg/streams] Add explainer for resizable buffers for BYOB readers (PR #1360) (Friday, 28 November)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Tuesday, 25 November)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Tuesday, 25 November)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Tuesday, 25 November)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Monday, 24 November)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Monday, 24 November)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Monday, 24 November)
• Re: [whatwg/streams] Allow error to be provided to reader.releaseLock() (Issue #1358) (Saturday, 22 November)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Saturday, 22 November)
• Re: [whatwg/streams] Add explainer for resizable buffers for BYOB readers (PR #1360) (Saturday, 22 November)
• Re: [whatwg/streams] Editorial: fix ref for break (PR #1361) (Saturday, 22 November)
• [whatwg/streams] Editorial: fix ref for break (PR #1361) (Saturday, 22 November)
• [whatwg/streams] Add explainer for resizable buffers for BYOB readers (PR #1360) (Saturday, 22 November)

max.lee

• Re: [whatwg/dom] Element's display property affects composedPath() calculation unexpectedly (Issue #1419) (Wednesday, 5 November)
• [whatwg/dom] Element's display property affects composedPath() calculation unexpectedly (Issue #1419) (Wednesday, 5 November)

Maxim Devaev

• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Thursday, 27 November)

Meghan Denny

• Re: [whatwg/webidl] Intent to use Constants /1 (Issue #1546) (Tuesday, 25 November)
• Re: [whatwg/fetch] FETCHING (Issue #1882) (Friday, 21 November)
• Re: [whatwg/url] Hussein (Issue #891) (Wednesday, 19 November)
• Re: [whatwg/url] H-Y-O (Issue #890) (Wednesday, 19 November)
• Re: [whatwg/fetch] Client report (Issue #1877) (Tuesday, 11 November)
• Re: [whatwg/webidl] Intent to use Constants (Issue #1538) (Sunday, 9 November)
• Re: [whatwg/fetch] Need ya help with (Issue #1874) (Saturday, 1 November)

meiqinyan

• [whatwg/dom] CDATA section can be imported into HTML document (Issue #1420) (Thursday, 6 November)

Mert Can Altin

• Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Friday, 28 November)
• Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Friday, 28 November)
• Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Friday, 28 November)
• Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Saturday, 15 November)
• Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Saturday, 15 November)
• Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874) (Thursday, 6 November)

mfigueroamaradiagastudent-hue

• Re: [whatwg/storage] Editorial: add a diagram for storage model (8b93c4c) (Wednesday, 5 November)

Michael Aufreiter

• Re: [w3c/editing] Expose event.getTargetRanges() in oncompositionstart (and possibly oncompositionend as well) (Issue #511) (Tuesday, 18 November)
• Re: [w3c/editing] Safari/Chrome Desktop: Caret movement with up/down arrow keys breaks when DOM is constructed programmatically (Issue #513) (Tuesday, 18 November)
• [w3c/editing] Add repro for #512 and fixes of #497 (PR #514) (Monday, 17 November)
• [w3c/editing] Safari/Chrome Desktop: Caret movement with up/down arrow keys breaks when DOM is constructed programmatically (Issue #513) (Monday, 17 November)
• Re: [w3c/editing] Repros (PR #512) (Monday, 17 November)
• [w3c/editing] [WIP] Repros (PR #512) (Monday, 17 November)
• Re: [w3c/editing] Expose event.getTargetRanges() in oncompositionstart (and possibly oncompositionend as well) (Issue #511) (Monday, 17 November)
• [w3c/editing] Expose event.getTargetRanges() in oncompositionstart (and possibly oncompositionend as well) (Issue #511) (Monday, 17 November)
• Re: [w3c/editing] Ability to rollback changes after IME, so that editors that manage their own incremental rendering can assume the same DOM as before the IME (Issue #510) (Monday, 17 November)
• [w3c/editing] Ability to rollback changes after IME, so that editors that manage their own incremental rendering can assume the same DOM as before the IME (Issue #510) (Monday, 17 November)
• Re: [w3c/editing] Add ability to control native undo/redo stack (Issue #509) (Monday, 17 November)
• [w3c/editing] Add ability to control native undo/redo stack (Issue #509) (Monday, 17 November)
• Re: [w3c/editing] All browsers: Impossible to cancel inputs when they are starting character composition (IME) (Issue #508) (Monday, 17 November)
• Re: [w3c/editing] All browsers: Impossible to cancel inputs when they are starting character composition (IME) (Issue #508) (Monday, 17 November)
• [w3c/editing] All browsers: Impossible to cancel inputs when they are starting character composition (IME) (Issue #508) (Monday, 17 November)
• [w3c/editing] Safari Desktop: When aborting a soft-keyboard-driven IME, the new selection is not set (Issue #507) (Monday, 17 November)
• [w3c/editing] Safari Desktop: Autosuggest/correct only works when native contenteditable is doing the rendering (Issue #506) (Monday, 17 November)
• [w3c/editing] Safari Desktop: When aborting a composition after pressing a dead key (e.g. `^`) in oncompositionend event.data will have `""` while `"^"` is expected (Issue #505) (Monday, 17 November)
• [w3c/editing] Chrome Desktop + Android: document.execCommand does not trigger a 'historyUndo' onbeforinput event after running document.execCommand('undo') (Issue #504) (Monday, 17 November)
• [w3c/editing] Speccing placeholders (Issue #503) (Monday, 17 November)
• [w3c/editing] Firefox: Clicking a placeholder inside a contenteditable element does not focus the element (Issue #502) (Monday, 17 November)
• [w3c/editing] Firefox: Cursor is misaligned on centered text with placeholder (Issue #501) (Monday, 17 November)
• [w3c/editing] Firefox: Empty fields with placeholder are not keyboard selectable (Issue #500) (Monday, 17 November)
• [w3c/editing] Safari Desktop: Conditional Show/ Hide of br element in contenteditable element make caret disappear (Issue #499) (Monday, 17 November)
• [w3c/editing] Safari/Chrome: Caret Rendering inconsistent with empty placeholder across browsers (Issue #498) (Monday, 17 November)
• [w3c/editing] Safari Desktop: Editing an empty `<a>` makes content leak outside the `<a>` (Issue #497) (Monday, 17 November)
• [w3c/editing] Safari Desktop: position: relative on parent of empty text div makes content leak outside the text div. (Issue #496) (Monday, 17 November)
• [w3c/editing] Android: At onbeforeinput always fires 'deleteContentBackward' and never 'deleteWordBackward' (Issue #495) (Monday, 17 November)
• [w3c/editing] Safari Desktop: `insertReplacementText` not fired (Issue #494) (Monday, 17 November)
• [w3c/editing] Firefox: event.getTargetRanges() in beforeinput not consistent with window.getSelection() (Issue #493) (Monday, 17 November)
• [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Monday, 17 November)

Mike West

• [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173) (Tuesday, 25 November)
• Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Wednesday, 19 November)
• Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Wednesday, 19 November)
• Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Wednesday, 19 November)
• Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Wednesday, 19 November)
• Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867) (Wednesday, 5 November)

Ming-Ying Chung

• Re: [whatwg/fetch] New Proposal: Fetch retry (Issue #1838) (Thursday, 13 November)

Monica Chintala

• Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Tuesday, 18 November)
• Re: [w3c/ServiceWorker] Restrict openWindow() to http(s) schemes? (#699) (Tuesday, 18 November)
• Re: [w3c/ServiceWorker] Add name param to Clients.openWindow() method (#711) (Monday, 17 November)
• Re: [w3c/ServiceWorker] Expose environment ids? (#643) (Monday, 17 November)
• Re: [w3c/ServiceWorker] registration.ready promise (#770) (Monday, 17 November)
• Re: [w3c/ServiceWorker] Problem with spec-prod/gh-pages mismatch (Issue #1806) (Monday, 17 November)
• Re: [w3c/ServiceWorker] add implementation report (PR #1805) (Thursday, 13 November)
• Re: [w3c/ServiceWorker] Editorial: Fix lint error (PR #1802) (Monday, 3 November)

Ms2ger

• Re: [whatwg/webidl] Create an operation does not care about [LegacyLenientThis] (PR #1548) (Friday, 28 November)
• Re: [whatwg/webidl] Create an operation does not care about [LegacyLenientThis] (PR #1548) (Friday, 28 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Tuesday, 11 November)

Nicholas Car

• [w3ctag/design-reviews] WG Revision: SHACL 1.2 Core (Issue #1166) (Thursday, 6 November)

Noam Rosenthal

• Re: [whatwg/dom] Make DOMTokenList's supported token concept also depend on element (PR #1431) (Saturday, 29 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)
• Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013) (Wednesday, 19 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Tuesday, 18 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Tuesday, 18 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Friday, 14 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Thursday, 13 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Thursday, 13 November)
• [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Thursday, 13 November)
• Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839) (Wednesday, 12 November)

Nolan Lawson

• Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Thursday, 27 November)
• Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Sunday, 9 November)
• Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Sunday, 9 November)

NullVoxPopuli

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

Patrick Meenan

• Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839) (Tuesday, 18 November)
• Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839) (Tuesday, 18 November)
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Thursday, 13 November)
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Thursday, 13 November)
• Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839) (Thursday, 13 November)
• Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839) (Wednesday, 12 November)
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Tuesday, 11 November)
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Tuesday, 11 November)
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Tuesday, 11 November)
• Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839) (Tuesday, 11 November)

Philippe Le Hegaret

• Re: [w3c/uievents] TPAC 2025 status report (Issue #399) (Monday, 10 November)

Praveen Ponnusamy

• Re: [whatwg/fetch] Body.json reviver (#104) (Monday, 24 November)

Rakesh Goulikar

• [w3c/clipboard-apis] Standardize Clipboard Source url (Issue #244) (Wednesday, 12 November)
• [w3c/editing] Standardize Clipboard Source url (Issue #491) (Wednesday, 12 November)

rdcronin

• [whatwg/fetch] Allow user agents to use more permissive header validation in extensions (Issue #1878) (Thursday, 13 November)

Reilly Grant

• Re: [whatwg/webidl] Parameter types that must be JSON serializable (Issue #1537) (Thursday, 6 November)
• [whatwg/webidl] Parameter types that must be JSON serializable (Issue #1537) (Thursday, 6 November)

Rob Eisenberg

• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Sunday, 9 November)

roraja

• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event API specification (PR #239) (Friday, 14 November)
• [w3c/clipboard-apis] Update Editor List - Add New Editors and Move Former Editors (PR #245) (Friday, 14 November)
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) (Friday, 14 November)
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) (Friday, 14 November)

Ryosuke Niwa

• Re: [WICG/webcomponents] https://github.com/WICG/webcomponents/issues/1029 (Issue #1117) (Sunday, 23 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Wednesday, 19 November)
• Re: [w3c/editing] Add ability to control native undo/redo stack (Issue #509) (Tuesday, 18 November)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413) (Sunday, 16 November)
• Re: [whatwg/dom] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #1189) (Friday, 14 November)

Sajib chowdhury

• [WICG/webcomponents] https://github.com/WICG/webcomponents/issues/1029 (Issue #1117) (Sunday, 23 November)

Sam Atkins

• Re: [whatwg/dom] Scoped custom element registry issues (Issue #1379) (Friday, 28 November)

Sam Goto

• [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Wednesday, 12 November)
• Re: [w3ctag/design-reviews] Delegation-oriented FedCM (Issue #1039) (Monday, 10 November)

Sam Richard

• [w3c/manifest] Discuss PWA Widgets (Issue #1195) (Monday, 10 November)

ShinWonho

• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Wednesday, 12 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Wednesday, 12 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Wednesday, 12 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Wednesday, 12 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Wednesday, 12 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Tuesday, 11 November)
• Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Tuesday, 11 November)
• [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539) (Monday, 10 November)

Shunya Shishido

• Re: [w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807) (Tuesday, 25 November)
• Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737) (Thursday, 20 November)
• [w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807) (Thursday, 20 November)

sideshowbarker

• Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876) (Thursday, 27 November)
• Re: [whatwg/dom] Facebook page (Issue #1418) (Sunday, 2 November)

Simon Pieters

• Re: [w3c/ServiceWorker] object/embed (#249) (Wednesday, 26 November)

smaug----

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

Stephen Chenney

• Re: [w3ctag/design-reviews] CSS find-in-page highlight pseudos (Issue #1120) (Monday, 17 November)
• Re: [w3ctag/design-reviews] CSS find-in-page highlight pseudos (Issue #1120) (Monday, 17 November)

Steve Orvell

• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 26 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Monday, 24 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Saturday, 22 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Saturday, 22 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Wednesday, 19 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Wednesday, 19 November)
• Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424) (Wednesday, 19 November)
• Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423) (Wednesday, 19 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Tuesday, 18 November)
• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Tuesday, 18 November)
• Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413) (Sunday, 16 November)

Steven Becker

• Re: [w3c/IndexedDB] TPAC 2025 status report (Issue #469) (Wednesday, 5 November)
• Re: [w3c/IndexedDB] TPAC 2025 status report (Issue #469) (Tuesday, 4 November)
• Re: [w3c/gamepad] TPAC 2025 status report (Issue #226) (Tuesday, 4 November)

tamannaaharia-ui

• [w3ctag/design-reviews] #Faizzan$* (Issue #1170) (Tuesday, 18 November)

Tarek Ziade

• Re: [w3ctag/design-reviews] Updated review of Web Neural Network API (Issue #1072) (Wednesday, 12 November)

tersayang3552

• [whatwg/storage] Wan (Issue #187) (Wednesday, 5 November)
• [whatwg/storage] Tersayang6183 (Issue #188) (Wednesday, 5 November)

Tete17

• Re: [whatwg/dom] "Set an existing attribute value" algorithm checks twice if attributes element is null (Issue #1421) (Sunday, 23 November)
• Re: [whatwg/dom] "Set an existing attribute value" algorithm checks twice if attributes element is null (Issue #1421) (Sunday, 23 November)
• [whatwg/dom] "Set an existing attribute value" algorithm checks twice if attributes element is null (Issue #1421) (Tuesday, 11 November)

Thomas Steiner

• Re: [w3c/manifest] Add `navigator.install()` (PR #1175) (Tuesday, 11 November)

Tobias Fahleson (ThinLinc team)

• Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Wednesday, 19 November)

ud2

• Re: [whatwg/streams] Allow error to be provided to reader.releaseLock() (Issue #1358) (Sunday, 23 November)

Valery Zinchenko

• Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116) (Monday, 17 November)

W3C Bot

• [w3ctag/design-reviews] [wg/dx] Dataset Exchange Working Group Charter (Issue #1171) (Friday, 21 November)
• [w3ctag/design-reviews] [wg/pointer-events] Pointer Events Working Group rechartering (Issue #1165) (Tuesday, 4 November)

warrengspurlock-dot

• Re: [whatwg/webidl] Upgrade QuotaExceededError to a DOMException derived interface (PR #1465) (Monday, 17 November)

Xiaoqian Wu

• Re: [w3c/ServiceWorker] add implementation report (PR #1805) (Thursday, 13 November)
• [w3c/ServiceWorker] add implementation report (PR #1805) (Thursday, 13 November)
• Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804) (Thursday, 13 November)
• Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804) (Thursday, 13 November)
• Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804) (Tuesday, 11 November)
• [w3c/ServiceWorker] chore: setup autopub (PR #1804) (Tuesday, 11 November)
• [w3c/FileAPI] Self-Review Questionnaire for FileAPI: Security and Privacy (Issue #214) (Tuesday, 11 November)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] object/embed (#249) (Friday, 28 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Friday, 28 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Thursday, 27 November)
• Re: [w3c/ServiceWorker] Better hooks for functional events (Issue #1808) (Wednesday, 26 November)
• [w3c/ServiceWorker] Editorial: export "Fire Functional Event" arguments (PR #1809) (Wednesday, 26 November)
• Re: [w3c/ServiceWorker] Better hooks for functional events (Issue #1808) (Wednesday, 26 November)
• Re: [w3c/ServiceWorker] Better hooks for functional events (Issue #1808) (Wednesday, 26 November)
• Re: [w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807) (Wednesday, 26 November)
• Re: [w3c/ServiceWorker] Need for a mechanism to detect supported conditions and sources in the SW Static Routing API (Issue #1793) (Tuesday, 25 November)
• Re: [w3c/ServiceWorker] Need for a mechanism to detect supported conditions and sources in the SW Static Routing API (Issue #1793) (Monday, 24 November)
• Re: [w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807) (Friday, 21 November)
• Re: [w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807) (Friday, 21 November)
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) (Friday, 21 November)
• Re: [w3c/ServiceWorker] Support CacheStorage.match() options in SW Static Routing API cache source (Issue #1797) (Wednesday, 19 November)
• Re: [w3c/ServiceWorker] Problem with spec-prod/gh-pages mismatch (Issue #1806) (Wednesday, 19 November)
• Re: [w3c/ServiceWorker] Problem with spec-prod/gh-pages mismatch (Issue #1806) (Wednesday, 19 November)
• Re: [w3c/ServiceWorker] Problem with spec-prod/gh-pages mismatch (Issue #1806) (Wednesday, 19 November)
• Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804) (Wednesday, 12 November)
• Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804) (Wednesday, 12 November)
• Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804) (Tuesday, 11 November)
• Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Sunday, 9 November)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Sunday, 9 November)
• Re: [w3c/ServiceWorker] Editorial: Fix lint error (PR #1802) (Monday, 3 November)
• Re: [w3c/ServiceWorker] Broken links in Service Workers Nightly (Issue #1801) (Monday, 3 November)
• Re: [w3c/ServiceWorker] Editorial: Fix lint error (PR #1802) (Monday, 3 November)
• Re: [w3c/ServiceWorker] Editorial: Fix lint error (PR #1802) (Monday, 3 November)
• [w3c/ServiceWorker] Editorial: Fix lint error (PR #1802) (Monday, 3 November)
• Re: [w3c/ServiceWorker] Broken links in Service Workers Nightly (Issue #1801) (Monday, 3 November)
• Re: [w3c/ServiceWorker] Broken links in Service Workers Nightly (Issue #1801) (Monday, 3 November)

youennf

• Re: [w3c/ServiceWorker] Need for a mechanism to detect supported conditions and sources in the SW Static Routing API (Issue #1793) (Monday, 24 November)
• Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Monday, 10 November)

YTERGamer

• [whatwg/fetch] Need ya help with (Issue #1874) (Saturday, 1 November)

zavinzaman-wq

• Re: [whatwg/streams] Meta: replace IRC link with Matrix (5c9a34c) (Sunday, 2 November)
• Re: [whatwg/streams] Meta: replace IRC link with Matrix (5c9a34c) (Sunday, 2 November)

Zgroza (Luke Klimek)

• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) (Wednesday, 12 November)

Last message date: Saturday, 29 November 2025 13:03:03 UTC