Re: [whatwg/dom] setAttributeNS incorrect context for validation (Issue #1417)
[whatwg/dom] Editorial: modernize mutation observers (PR #1436)
[whatwg/dom] Editorial: modernize convert nodes into a node (PR #1435)
Re: [whatwg/dom] MutationObserver attribute filter ignores attributes with a namespace (Issue #1364)
- Re: [whatwg/dom] MutationObserver attribute filter ignores attributes with a namespace (Issue #1364)
Re: [whatwg/dom] Scoped custom element registry issues (Issue #1379)
- Re: [whatwg/dom] Scoped custom element registry issues (Issue #1379)
- Re: [whatwg/dom] Scoped custom element registry issues (Issue #1379)
[whatwg/dom] Correct setAttributeNS() validation context (PR #1434)
- Re: [whatwg/dom] Correct setAttributeNS() validation context (PR #1434)
- Re: [whatwg/dom] Correct setAttributeNS() validation context (PR #1434)
- Re: [whatwg/dom] Correct setAttributeNS() validation context (PR #1434)
- Re: [whatwg/dom] Correct setAttributeNS() validation context (PR #1434)
- Re: [whatwg/dom] Correct setAttributeNS() validation context (PR #1434)
Re: [whatwg/dom] Support `getElementsByTagName(tag)` for DocumentFragment (Issue #1382)
[whatwg/dom] Address infinite loop in TreeWalker's nextNode() (PR #1433)
[whatwg/dom] Editorial: modernize Traversal (PR #1432)
[whatwg/dom] Make DOMTokenList's supported token concept also depend on element (PR #1431)
- Re: [whatwg/dom] Make DOMTokenList's supported token concept also depend on element (PR #1431)
- Re: [whatwg/dom] Make DOMTokenList's supported token concept also depend on element (PR #1431)
[whatwg/webidl] Create an operation does not care about [LegacyLenientThis] (PR #1548)
- Re: [whatwg/webidl] Create an operation does not care about [LegacyLenientThis] (PR #1548)
- Re: [whatwg/webidl] Create an operation does not care about [LegacyLenientThis] (PR #1548)
[whatwg/webidl] When creating a global object the realm is not yet initialized (Issue #1547)
- Re: [whatwg/webidl] When creating a global object the realm is not yet initialized (Issue #1547)
- Re: [whatwg/webidl] When creating a global object the realm is not yet initialized (Issue #1547)
- Re: [whatwg/webidl] When creating a global object the realm is not yet initialized (Issue #1547)
[whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430)
- Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430)
- Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430)
- Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430)
- Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430)
- Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430)
- Re: [whatwg/dom] Editorial: modernize Ranges and CharacterData (PR #1430)
Re: [w3ctag/design-reviews] [ig/webai] Web&AI Interest Group (Issue #1149)
Re: [w3c/manifest] TPAC 2025 status report (Issue #1181)
Re: [w3c/manifest] chore: Add retiredDate for Kenneth Rohde Christiansen (PR #1192)
[whatwg/dom] Adopting children of an intentional null shadow root goes wrong (Issue #1429)
Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
Re: [w3c/ServiceWorker] object/embed (#249)
[whatwg/dom] adoptNode() needs to account for <iframe> and friends (Issue #1428)
[whatwg/dom] Editorial: make adopt traverse the tree less (PR #1427)
[w3c/ServiceWorker] Editorial: export "Fire Functional Event" arguments (PR #1809)
Re: [w3c/push-api] Normative references to discontinued specs in Push API (Issue #390)
Re: [w3c/push-api] Holding "Fire a Functional Event" incorrectly (Issue #389)
[w3c/ServiceWorker] Better hooks for functional events (Issue #1808)
- Re: [w3c/ServiceWorker] Better hooks for functional events (Issue #1808)
- Re: [w3c/ServiceWorker] Better hooks for functional events (Issue #1808)
- Re: [w3c/ServiceWorker] Better hooks for functional events (Issue #1808)
- Re: [w3c/ServiceWorker] Better hooks for functional events (Issue #1808)
[w3c/push-api] Editorial: replace RFC7231 reference with RFC9110 (PR #415)
- Re: [w3c/push-api] Editorial: replace RFC7231 reference with RFC9110 (PR #415)
- Re: [w3c/push-api] Editorial: replace RFC7231 reference with RFC9110 (PR #415)
Re: [w3c/push-api] PushMessageData is poorly defined and seems broken (Issue #380)
[w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173)
[whatwg/dom] Editorial: modernize mutation algorithms (PR #1426)
- Re: [whatwg/dom] Editorial: modernize mutation algorithms (PR #1426)
- Re: [whatwg/dom] Editorial: modernize mutation algorithms (PR #1426)
- Re: [whatwg/dom] Editorial: modernize mutation algorithms (PR #1426)
- Re: [whatwg/dom] Editorial: modernize mutation algorithms (PR #1426)
- Re: [whatwg/dom] Editorial: modernize mutation algorithms (PR #1426)
Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015)
[whatwg/webidl] Intent to use Constants /1 (Issue #1546)
[whatwg/webidl] Change enum syntax to reflect real constraints (Issue #1545)
[w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172)
[w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
- Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414)
Re: [whatwg/fetch] Body's json(): add reviver argument (#104)
Re: [whatwg/fetch] Body.json reviver (#104)
Re: [w3c/clipboard-apis] Add privacy considerations for the clipboardchange event (Issue #230)
[WICG/webcomponents] https://github.com/WICG/webcomponents/issues/1029 (Issue #1117)
Re: [whatwg/streams] Allow error to be provided to reader.releaseLock() (Issue #1358)
- Re: [whatwg/streams] Allow error to be provided to reader.releaseLock() (Issue #1358)
- Re: [whatwg/streams] Allow error to be provided to reader.releaseLock() (Issue #1358)
Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
[whatwg/streams] Editorial: fix ref for break (PR #1361)
- Re: [whatwg/streams] Editorial: fix ref for break (PR #1361)
- Re: [whatwg/streams] Editorial: fix ref for break (PR #1361)
- Re: [whatwg/streams] Editorial: fix ref for break (PR #1361)
[whatwg/streams] Add explainer for resizable buffers for BYOB readers (PR #1360)
- Re: [whatwg/streams] Add explainer for resizable buffers for BYOB readers (PR #1360)
- Re: [whatwg/streams] Add explainer for resizable buffers for BYOB readers (PR #1360)
Re: [whatwg/fetch] Proposal: response.base64() (Issue #1800)
[whatwg/fetch] FETCHING (Issue #1882)
[whatwg/fetch] Fill in CONNECT pseudo-headers automatically (e.g. from request mode) (Issue #1881)
Re: [w3c/permissions] WebDriver: Make it possible to pass a different origin to "Set Permission" (Issue #419)
[w3ctag/design-reviews] [wg/dx] Dataset Exchange Working Group Charter (Issue #1171)
[whatwg/webidl] Driver LLC (Issue #1544)
[whatwg/webidl] Intent to use Constants (Issue #1543)
[w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807)
- Re: [w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807)
- Re: [w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807)
- Re: [w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807)
- Re: [w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807)
- Re: [w3c/ServiceWorker] Do not remove the race response map entry in Lookup Race Response (PR #1807)
[w3c/clipboard-apis] Clipboard API for text/html serialization and associated style attributes. (Issue #246)
- Re: [w3c/clipboard-apis] Clipboard API for text/html serialization and associated style attributes. (Issue #246)
- Re: [w3c/clipboard-apis] Clipboard API for text/html serialization and associated style attributes. (Issue #246)
- Re: [w3c/clipboard-apis] Clipboard API for text/html serialization and associated style attributes. (Issue #246)
[whatwg/dom] Add abortSignal.addAbortCallback (PR #1425)
- Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425)
- Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425)
- Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425)
[w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216)
- Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216)
- Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216)
- Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216)
- Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216)
- Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216)
- Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216)
- Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216)
- Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216)
[whatwg/url] Hussein (Issue #891)
[whatwg/url] H-Y-O (Issue #890)
Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163)
Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013)
Re: [whatwg/fetch] Add a "webtransport" request mode (Issue #1808)
[whatwg/fetch] Support serverCertificateHashes in obtain a connection for WebTransport (Issue #1880)
[whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
- Re: [whatwg/dom] Allow the creation of null registry element and shadow root (PR #1424)
Re: [w3c/ServiceWorker] Restrict openWindow() to http(s) schemes? (#699)
[w3c/push-api] Remove the note that suggests subscribe()'s step order does not matter (PR #413)
- Re: [w3c/push-api] Remove the note that suggests subscribe()'s step order does not matter (PR #413)
- Re: [w3c/push-api] Remove the note that suggests subscribe()'s step order does not matter (PR #413)
- Re: [w3c/push-api] Remove the note that suggests subscribe()'s step order does not matter (PR #413)
Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
- Re: [whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
Re: [whatwg/fetch] docs: add example for X-Content-Type-Options header (PR #1872)
Re: [w3c/push-api] Does PushManager subscribe() need transient activation check? (Issue #346)
[w3ctag/design-reviews] #Faizzan$* (Issue #1170)
[whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
- Re: [whatwg/dom] Set registry on null registry element on adopt instead of on insert (PR #1423)
Re: [w3c/ServiceWorker] Expose environment ids? (#643)
[w3c/editing] Add repro for #512 and fixes of #497 (PR #514)
- Re: [w3c/editing] Add repro for #512 and fixes for #497 (PR #514)
- Re: [w3c/editing] Add repro for #512 and fixes for #497 (PR #514)
- Re: [w3c/editing] Add repro for #512 and fixes for #497 (PR #514)
[w3c/editing] Safari/Chrome Desktop: Caret movement with up/down arrow keys breaks when DOM is constructed programmatically (Issue #513)
- Re: [w3c/editing] Safari/Chrome Desktop: Caret movement with up/down arrow keys breaks when DOM is constructed programmatically (Issue #513)
- Re: [w3c/editing] Safari/Chrome Desktop: Caret movement with up/down arrow keys breaks when DOM is constructed programmatically (Issue #513)
[w3c/manifest] Manifest Editors Meetings (Issue #1198)
Re: [w3ctag/design-reviews] CSS find-in-page highlight pseudos (Issue #1120)
Re: [w3c/ServiceWorker] registration.ready promise (#770)
[w3c/editing] [WIP] Repros (PR #512)
- Re: [w3c/editing] Repros (PR #512)
- Re: [w3c/editing] Repros (PR #512)
- Re: [w3c/editing] Repros (PR #512)
[w3c/editing] Expose event.getTargetRanges() in oncompositionstart (and possibly oncompositionend as well) (Issue #511)
- Re: [w3c/editing] Expose event.getTargetRanges() in oncompositionstart (and possibly oncompositionend as well) (Issue #511)
- Re: [w3c/editing] Expose event.getTargetRanges() in oncompositionstart (and possibly oncompositionend as well) (Issue #511)
- Re: [w3c/editing] Expose event.getTargetRanges() in oncompositionstart (and possibly oncompositionend as well) (Issue #511)
- Re: [w3c/editing] Expose event.getTargetRanges() in oncompositionstart (and possibly oncompositionend as well) (Issue #511)
[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)
[w3c/editing] Add ability to control native undo/redo stack (Issue #509)
- Re: [w3c/editing] Add ability to control native undo/redo stack (Issue #509)
- Re: [w3c/editing] Add ability to control native undo/redo stack (Issue #509)
- Re: [w3c/editing] Add ability to control native undo/redo stack (Issue #509)
[w3c/editing] All browsers: Impossible to cancel inputs when they are starting character composition (IME) (Issue #508)
- Re: [w3c/editing] All browsers: Impossible to cancel inputs when they are starting character composition (IME) (Issue #508)
- Re: [w3c/editing] All browsers: Impossible to cancel inputs when they are starting character composition (IME) (Issue #508)
[w3c/editing] Safari Desktop: When aborting a soft-keyboard-driven IME, the new selection is not set (Issue #507)
[w3c/editing] Safari Desktop: Autosuggest/correct only works when native contenteditable is doing the rendering (Issue #506)
[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)
[w3c/editing] Chrome Desktop + Android: document.execCommand does not trigger a 'historyUndo' onbeforinput event after running document.execCommand('undo') (Issue #504)
[w3c/editing] Speccing placeholders (Issue #503)
[w3c/editing] Firefox: Clicking a placeholder inside a contenteditable element does not focus the element (Issue #502)
[w3c/editing] Firefox: Cursor is misaligned on centered text with placeholder (Issue #501)
[w3c/editing] Firefox: Empty fields with placeholder are not keyboard selectable (Issue #500)
[w3c/editing] Safari Desktop: Conditional Show/ Hide of br element in contenteditable element make caret disappear (Issue #499)
[w3c/editing] Safari/Chrome: Caret Rendering inconsistent with empty placeholder across browsers (Issue #498)
[w3c/editing] Safari Desktop: Editing an empty `<a>` makes content leak outside the `<a>` (Issue #497)
[w3c/editing] Safari Desktop: position: relative on parent of empty text div makes content leak outside the text div. (Issue #496)
[w3c/editing] Android: At onbeforeinput always fires 'deleteContentBackward' and never 'deleteWordBackward' (Issue #495)
[w3c/editing] Safari Desktop: `insertReplacementText` not fired (Issue #494)
[w3c/editing] Firefox: event.getTargetRanges() in beforeinput not consistent with window.getSelection() (Issue #493)
[w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492)
[w3c/ServiceWorker] Problem with spec-prod/gh-pages mismatch (Issue #1806)
- Re: [w3c/ServiceWorker] Problem with spec-prod/gh-pages mismatch (Issue #1806)
- Re: [w3c/ServiceWorker] Problem with spec-prod/gh-pages mismatch (Issue #1806)
- Re: [w3c/ServiceWorker] Problem with spec-prod/gh-pages mismatch (Issue #1806)
- Re: [w3c/ServiceWorker] Problem with spec-prod/gh-pages mismatch (Issue #1806)
Re: [whatwg/webidl] Upgrade QuotaExceededError to a DOMException derived interface (PR #1465)
Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
- Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
[whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359)
Re: [w3c/FileAPI] Top-level navigations to blob URLs with media mime types result in resource load subject to partitioning (Issue #210)
- Re: [w3c/FileAPI] Top-level navigations to blob URLs with media mime types result in resource load subject to partitioning (Issue #210)
- Re: [w3c/FileAPI] Top-level navigations to blob URLs with media mime types result in resource load subject to partitioning (Issue #210)
[whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
- Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879)
Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412)
[whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422)
Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321)
Re: [whatwg/dom] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #1189)
Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event API specification (PR #239)
- Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event API specification (PR #239)
- Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event API specification (PR #239)
[w3c/clipboard-apis] Update Editor List - Add New Editors and Move Former Editors (PR #245)
Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413)
[whatwg/fetch] Allow user agents to use more permissive header validation in extensions (Issue #1878)
[w3c/ServiceWorker] add implementation report (PR #1805)
- Re: [w3c/ServiceWorker] add implementation report (PR #1805)
- Re: [w3c/ServiceWorker] add implementation report (PR #1805)
[WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
- Re: [WICG/webcomponents] Addressable comments (a very small DOM parts subset) (Issue #1116)
Re: [whatwg/fetch] New Proposal: Fetch retry (Issue #1838)
[w3c/clipboard-apis] Standardize Clipboard Source url (Issue #244)
Re: [w3ctag/design-reviews] Private Proof API (Issue #1071)
Re: [w3ctag/design-reviews] Early Design Review: Partitioned Popins (Issue #956)
Re: [whatwg/dom] `compareDocumentPosition` should allow comparison of elements in the same shadow-including root (#320)
- Re: [whatwg/dom] `compareDocumentPosition` should allow comparison of elements in the same shadow-including root (#320)
- Re: [whatwg/dom] `compareDocumentPosition` should allow comparison of elements in the same shadow-including root (#320)
[w3c/editing] Standardize Clipboard Source url (Issue #491)
Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287)
- Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287)
- Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287)
Re: [w3c/pointerlock] TPAC 2025 status report (Issue #103)
Re: [w3c/screen-orientation] TPAC 2025 status report (Issue #258)
Re: [w3c/push-api] TPAC 2025 status report (Issue #404)
Re: [w3ctag/design-reviews] Updated review of Web Neural Network API (Issue #1072)
[w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169)
[w3c/FileAPI] Web Share API images have optional title, but seem to be missing alt. (Issue #215)
- Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215)
- Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215)
- Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215)
- Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215)
- Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215)
- Re: [w3c/FileAPI] Should some files provide an alt? (Issue #215)
Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239)
- Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239)
- Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239)
Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
- Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
- Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
- Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
- Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
- Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
[whatwg/fetch] Client report (Issue #1877)
[w3ctag/design-reviews] Explicitly tell people to use the Other Spec Review template for non-WG-driven reviews (PR #1168)
- Re: [w3ctag/design-reviews] Explicitly tell people to use the Other Spec Review template for non-WG-driven reviews (PR #1168)
- Re: [w3ctag/design-reviews] Explicitly tell people to use the Other Spec Review template for non-WG-driven reviews (PR #1168)
[whatwg/dom] "Set an existing attribute value" algorithm checks twice if attributes element is null (Issue #1421)
- Re: [whatwg/dom] "Set an existing attribute value" algorithm checks twice if attributes element is null (Issue #1421)
- Re: [whatwg/dom] "Set an existing attribute value" algorithm checks twice if attributes element is null (Issue #1421)
- Re: [whatwg/dom] "Set an existing attribute value" algorithm checks twice if attributes element is null (Issue #1421)
Re: [w3c/screen-orientation] Promise for unlock()? (#104)
Re: [w3c/screen-orientation] Allow unlock() to return a promise (PR #231)
[w3c/screen-orientation] "natural" is ambiguous (Issue #275)
Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
- Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
- Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
- Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
Re: [w3c/screen-orientation] Require a gesture? (Issue #210)
Re: [w3c/screen-orientation] Consume user activation (PR #218)
Re: [w3c/screen-orientation] Standardize window.orientation API (PR #271)
[whatwg/webidl] Editorial: export async_iterable (PR #1541)
- Re: [whatwg/webidl] Editorial: export async_iterable (PR #1541)
- Re: [whatwg/webidl] Editorial: export async_iterable (PR #1541)
- Re: [whatwg/webidl] Editorial: export async_iterable (PR #1541)
- Re: [whatwg/webidl] Editorial: export async_iterable (PR #1541)
Re: [w3c/manifest] Add `navigator.install()` (PR #1175)
Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
Re: [w3c/manifest] Web Install (Issue #1178)
Re: [w3ctag/design-reviews] Prompt API (Issue #1093)
[w3c/ServiceWorker] chore: setup autopub (PR #1804)
- Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804)
- Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804)
- Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804)
- Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804)
- Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804)
- Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804)
- Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804)
- Re: [w3c/ServiceWorker] chore: setup autopub (PR #1804)
[whatwg/webidl] async_iterable not exported (Issue #1540)
Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839)
- Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839)
- Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839)
- Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839)
- Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839)
- Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839)
- Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839)
- Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839)
- Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839)
[w3c/FileAPI] Self-Review Questionnaire for FileAPI: Security and Privacy (Issue #214)
Re: [whatwg/dom] Proposal to improve the DOM creation api (#150)
Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
Re: [w3c/ServiceWorker] should FetchEvent.request.signal reflect abort status of outer request? (#1544)
[w3ctag/design-reviews] WG New Spec: Scroll-Triggered Animations (Issue #1167)
[whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
- Re: [whatwg/webidl] Editorial: add missing args for CreateBuiltinFunction (PR #1539)
Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737)
[w3c/manifest] Discussion on potential uses for Vibration/Haptics? (Issue #1197)
Re: [w3ctag/design-reviews] Delegation-oriented FedCM (Issue #1039)
[w3c/manifest] Navigation Capturing / Management (Issue #1196)
[w3c/manifest] Discuss PWA Widgets (Issue #1195)
Re: [w3c/uievents] TPAC 2025 status report (Issue #399)
[w3c/manifest] WPT/dev testability: Create way to test features related to / currently dependent on install (Issue #1194)
[whatwg/webidl] Intent to use Constants (Issue #1538)
- Re: [whatwg/webidl] Intent to use Constants (Issue #1538)
- Re: [whatwg/webidl] Intent to use Constants (Issue #1538)
- Re: [whatwg/webidl] Intent to use Constants (Issue #1538)
Re: [w3c/push-api] check and consume user activation (PR #348)
Re: [WICG/webcomponents] Idea: A tree-aware task scheduler (Issue #1055)
Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719)
- Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719)
- Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719)
- Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719)
Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026)
[whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876)
- Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876)
- Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876)
- Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876)
- Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876)
Re: [w3c/FileAPI] TPAC 2025 status report (Issue #211)
Re: [w3c/ServiceWorker] Add name param to Clients.openWindow() method (#711)
Re: [w3c/ServiceWorker] Need for a mechanism to detect supported conditions and sources in the SW Static Routing API (Issue #1793)
- Re: [w3c/ServiceWorker] Need for a mechanism to detect supported conditions and sources in the SW Static Routing API (Issue #1793)
- Re: [w3c/ServiceWorker] Need for a mechanism to detect supported conditions and sources in the SW Static Routing API (Issue #1793)
- Re: [w3c/ServiceWorker] Need for a mechanism to detect supported conditions and sources in the SW Static Routing API (Issue #1793)
[w3c/ServiceWorker] Preserve sec-fetch-dest for passed navigate requests (Issue #1803)
- Re: [w3c/ServiceWorker] Preserve sec-fetch-dest for passed navigate requests (Issue #1803)
- Re: [w3c/ServiceWorker] Preserve sec-fetch-dest for passed navigate requests (Issue #1803)
- Re: [w3c/ServiceWorker] Preserve sec-fetch-dest for passed navigate requests (Issue #1803)
- Re: [w3c/ServiceWorker] Preserve sec-fetch-dest for passed navigate requests (Issue #1803)
Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798)
Re: [w3c/ServiceWorker] Support CacheStorage.match() options in SW Static Routing API cache source (Issue #1797)
Re: [w3c/ServiceWorker] A way to specify a pattern of destination URLs to hit/skip SW (#1454)
Re: [w3c/manifest] Add API to retrieve document's computed manifest (Issue #1179)
[w3c/manifest] Manifest-url-only install (Issue #1193)
Re: [w3ctag/design-reviews] `<geolocation>` element (part of PEPC) (Issue #1140)
[whatwg/dom] CDATA section can be imported into HTML document (Issue #1420)
Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
[w3ctag/design-reviews] WG Revision: SHACL 1.2 Core (Issue #1166)
[whatwg/webidl] Parameter types that must be JSON serializable (Issue #1537)
- Re: [whatwg/webidl] Parameter types that must be JSON serializable (Issue #1537)
- Re: [whatwg/webidl] Parameter types that must be JSON serializable (Issue #1537)
- Re: [whatwg/webidl] Parameter types that must be JSON serializable (Issue #1537)
[whatwg/storage] Wan (Issue #187)
[whatwg/storage] Tersayang6183 (Issue #188)
Re: [whatwg/storage] Editorial: add a diagram for storage model (8b93c4c)
[whatwg/fetch] Allow updating of render-blocking status (Issue #1875)
[whatwg/dom] Element's display property affects composedPath() calculation unexpectedly (Issue #1419)
- Re: [whatwg/dom] Element's display property affects composedPath() calculation unexpectedly (Issue #1419)
- Re: [whatwg/dom] Element's display property affects composedPath() calculation unexpectedly (Issue #1419)
- Re: [whatwg/dom] Element's display property affects composedPath() calculation unexpectedly (Issue #1419)
- Re: [whatwg/dom] Element's display property affects composedPath() calculation unexpectedly (Issue #1419)
Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
- Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
- Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
- Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
- Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
- Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
- Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
- Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
- Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
Re: [w3c/IndexedDB] TPAC 2025 status report (Issue #469)
- Re: [w3c/IndexedDB] TPAC 2025 status report (Issue #469)
- Re: [w3c/IndexedDB] TPAC 2025 status report (Issue #469)
- Re: [w3c/IndexedDB] TPAC 2025 status report (Issue #469)
[w3ctag/design-reviews] [wg/pointer-events] Pointer Events Working Group rechartering (Issue #1165)
Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457)
Re: [w3c/gamepad] TPAC 2025 status report (Issue #226)
- Re: [w3c/gamepad] TPAC 2025 status report (Issue #226)
- Re: [w3c/gamepad] TPAC 2025 status report (Issue #226)
Re: [w3c/IndexedDB] treat writes to the DB that have no success handler as having called commit (Issue #482)
[whatwg/webidl] Issues with legacy platform object [[Set]] (Issue #1536)
[w3c/ServiceWorker] Editorial: Fix lint error (PR #1802)
- Re: [w3c/ServiceWorker] Editorial: Fix lint error (PR #1802)
- Re: [w3c/ServiceWorker] Editorial: Fix lint error (PR #1802)
- Re: [w3c/ServiceWorker] Editorial: Fix lint error (PR #1802)
- Re: [w3c/ServiceWorker] Editorial: Fix lint error (PR #1802)
Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
[w3c/ServiceWorker] Broken links in Service Workers Nightly (Issue #1801)
- Re: [w3c/ServiceWorker] Broken links in Service Workers Nightly (Issue #1801)
- Re: [w3c/ServiceWorker] Broken links in Service Workers Nightly (Issue #1801)
- Re: [w3c/ServiceWorker] Broken links in Service Workers Nightly (Issue #1801)