Re: [WICG/webcomponents] HTML Modules (#645)
[w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439)
- Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439)
- Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439)
- Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439)
- Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439)
[whatwg/webidl] Cypto-os (Issue #1473)
[whatwg/webidl] Intent to use Constants (Issue #1472)
[w3c/clipboard-apis] [clipboard-apis] .write() for text/html doesn't define a canonical form (Issue #233)
Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341)
- Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341)
- Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341)
Re: [WICG/webcomponents] Reference Target naming (Issue #1087)
- Re: [WICG/webcomponents] Reference Target naming (Issue #1087)
- Re: [WICG/webcomponents] Reference Target naming (Issue #1087)
- Re: [WICG/webcomponents] Reference Target naming (Issue #1087)
- Re: [WICG/webcomponents] Reference Target naming (Issue #1087)
- Re: [WICG/webcomponents] Reference Target naming (Issue #1087)
[w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058)
[w3c/permissions] Proposed Testing Plan for Geolocation Permission (Issue #460)
Re: [w3c/permissions] Editorial: Prepare for CR (PR #457)
Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307)
- Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307)
- Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307)
- Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307)
- Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307)
[w3ctag/design-reviews] Incremental Font Transfer (Issue #1057)
Re: [w3c/gamepad] Add a means to test the API (Issue #175)
[w3ctag/design-reviews] CSS Stylable Columns (Issue #1056)
[w3ctag/design-reviews] CSS inert (Issue #1055)
[w3ctag/design-reviews] CSS Scroll Buttons (Issue #1054)
[w3ctag/design-reviews] CSS Scroll Markers (Issue #1053)
Re: [w3ctag/design-reviews] Call stacks in crash reports from unresponsive web pages (Issue #981)
Re: [whatwg/fetch] Proposal: `Request.json` helper (Issue #1791)
Re: [w3c/selection-api] Change Selection to be associated with a composed live range (PR #345)
[whatwg/fetch] x content types added (PR #1810)
[whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361)
- Re: [whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361)
- Re: [whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361)
- Re: [whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361)
Re: [w3ctag/design-reviews] CSS Overflow Navigation Controls (Issue #1037)
Re: [w3ctag/design-reviews] CSS `dynamic-range-limit` (Issue #1027)
Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033)
- Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033)
- Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033)
- Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033)
- Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033)
- Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033)
- Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033)
[w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052)
[whatwg/url] Meta: address Bikeshed errors (PR #858)
[whatwg/dom] Update an attribute's node document (PR #1360)
- Re: [whatwg/dom] Update an attribute's node document (PR #1360)
- Re: [whatwg/dom] Update an attribute's node document (PR #1360)
- Re: [whatwg/dom] Update an attribute's node document (PR #1360)
- Re: [whatwg/dom] Update an attribute's node document (PR #1360)
- Re: [whatwg/dom] Update an attribute's node document (PR #1360)
- Re: [whatwg/dom] Update an attribute's node document (PR #1360)
[w3c/permissions] Aspects and integration with Permissions Policy (Issue #459)
Re: [w3ctag/design-reviews] Signature-Based Integrity. (Issue #1041)
[WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097)
- Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097)
- Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097)
- Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097)
- Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097)
- Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097)
- Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097)
- Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097)
- Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097)
- Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097)
Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960)
[w3ctag/design-reviews] (brand new ✨) Web Install API (Issue #1051)
Re: [whatwg/url] IDNA: avoid defining valid domain string in terms of the parser (#245)
[w3c/editing] Valid text element declaration for rich text editing caret accessibility (Issue #481)
[whatwg/url] Review Draft Publication: February 2025 (PR #857)
- Re: [whatwg/url] Review Draft Publication: February 2025 (PR #857)
- Re: [whatwg/url] Review Draft Publication: February 2025 (PR #857)
- Re: [whatwg/url] Review Draft Publication: February 2025 (PR #857)
[whatwg/streams] Review Draft Publication: February 2025 (PR #1340)
- Re: [whatwg/streams] Review Draft Publication: February 2025 (PR #1340)
- Re: [whatwg/streams] Review Draft Publication: February 2025 (PR #1340)
Re: [w3c/ServiceWorker] Editorial: "mutual exclusive" (Issue #1716)
Re: [w3c/ServiceWorker] Can we make to avoid to invoke ServiceWorker _by default_ for if user code call `event.addRoutes(rules)` in `install` event handler? (Issue #1712)
- Re: [w3c/ServiceWorker] Can we make to avoid to invoke ServiceWorker _by default_ for if user code call `event.addRoutes(rules)` in `install` event handler? (Issue #1712)
- Re: [w3c/ServiceWorker] Can we make to avoid to invoke ServiceWorker _by default_ for if user code call `event.addRoutes(rules)` in `install` event handler? (Issue #1712)
- Re: [w3c/ServiceWorker] Can we make to avoid to invoke ServiceWorker _by default_ for if user code call `event.addRoutes(rules)` in `install` event handler? (Issue #1712)
- Re: [w3c/ServiceWorker] Can we make to avoid to invoke ServiceWorker _by default_ for if user code call `event.addRoutes(rules)` in `install` event handler? (Issue #1712)
Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495)
- Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495)
- Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495)
Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)
- Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)
- Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)
Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
Re: [whatwg/fetch] Use tasks to manipulate streams (#1270)
[WICG/webcomponents] [Template Element] directive expressions (PR #1096)
Re: [whatwg/url] Are drive letters always invalid? (#612)
[whatwg/url] Include invalid outputs in the table with valid versus invalid parser inputs (Issue #856)
[whatwg/url] Express validity, error correction and percent encode sets in a single table (Issue #855)
Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852)
Re: [whatwg/url] Parser generates invalid URLs (#379)
- Re: [whatwg/url] Parser generates invalid URLs (#379)
- Re: [whatwg/url] Parser generates invalid URLs (#379)
- Re: [whatwg/url] Parser generates invalid URLs (#379)
- Re: [whatwg/url] Parser generates invalid URLs (#379)
Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270)
- Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270)
- Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270)
[WICG/webcomponents] Sessions for March 26th W3C Breakout Day (Issue #1095)
[w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
[WICG/webcomponents] [Template Element] template-* attributes (PR #1094)
Re: [WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072)
Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203)
[whatwg/webidl] Consider renaming ByteString to IsomorphicString (Issue #1471)
[w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754)
- Re: [w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754)
- Re: [w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754)
- Re: [w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754)
Re: [w3c/ServiceWorker] No examples around addRoutes() API (Issue #1717)
Re: [w3c/editing] Disable `formatBlock` for `contenteditable=plaintext-only` (Issue #478)
Re: [whatwg/fetch] Should network state be keyed beyond the top-level site (#1035)
Re: [w3c/gamepad] Fold extensions.html into main spec (Issue #165)
Re: [w3c/gamepad] Vibrate feature for Gamepad (#19)
[w3c/gamepad] Interop 2025 investigation effort - Gamepad API testing (Issue #219)
Re: [w3ctag/design-reviews] Invokers API (Issue #920)
Re: [whatwg/dom] Add definition for composed selection range (PR #1342)
- Re: [whatwg/dom] Add definition for composed selection range (PR #1342)
- Re: [whatwg/dom] Add definition for composed selection range (PR #1342)
- Re: [whatwg/dom] Add definition for composed selection range (PR #1342)
- Re: [whatwg/dom] Add definition for composed selection range (PR #1342)
Re: [w3c/ServiceWorker] Require `[SecureContext]` for interfaces with `[Exposed=ServiceWorker]` or not? (Issue #1749)
Re: [w3ctag/design-reviews] CSS Gap Decorations (Issue #1035)
[whatwg/encoding] Standardize x-mac-greek, x-mac-centraleurroman, and x-mac-turkish (Issue #342)
- Re: [whatwg/encoding] Standardize x-mac-greek, x-mac-centraleurroman, and x-mac-turkish (Issue #342)
- Re: [whatwg/encoding] Standardize x-mac-greek, x-mac-centraleurroman, and x-mac-turkish (Issue #342)
[whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341)
- Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341)
- Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341)
- Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341)
- Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341)
- Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341)
[whatwg/xhr] Xbox sign in (Issue #396)
Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
Re: [w3ctag/design-reviews] safe-area-max-inset-* variables (Issue #1046)
Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015)
- Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015)
- Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015)
- Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015)
Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232)
- Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232)
- Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232)
Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468)
[w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and the immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)
Re: [w3c/ServiceWorker] Fixing some spec linking issues (PR #1640)
[w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753)
- Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753)
- Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753)
- Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753)
- Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753)
[whatwg/webidl] Variable in step 9.2 of #wait-for-all should be renamed `fulfillmentHandlerSteps` (Issue #1470)
Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043)
- Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043)
- Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043)
- Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043)
- Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043)
[w3c/DOM-Parsing] GitHub actions: replace ubuntu-20.04 with ubuntu-latest (PR #86)
- Re: [w3c/DOM-Parsing] GitHub actions: replace ubuntu-20.04 with ubuntu-latest (PR #86)
- Re: [w3c/DOM-Parsing] GitHub actions: replace ubuntu-20.04 with ubuntu-latest (PR #86)
[whatwg/fetch] Added example for X-Content-Type-Options in Fetch Standard (PR #1809)
Re: [w3c/ServiceWorker] serviceworker for iframes with srcdoc (#765)
Re: [w3c/pointerlock] Unclear if `pointermove` should set `movementX/Y` (Issue #100)
[w3ctag/design-reviews] Permissions Policy reports for iframes (Issue #1050)
Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917)
Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038)
Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896)
Re: [whatwg/fullscreen] Deal with two fullscreen elements in top layer and one element being removed (#133)
Re: [whatwg/fetch] Define what consequences NULL bytes (0x00) or other invalid values in header names have (Issue #1747)
[whatwg/dom] setNamedItem doesn't adopt the attr node to the ownerDocument of the relevant element (Issue #1359)
- Re: [whatwg/dom] setNamedItem doesn't adopt the attr node to the ownerDocument of the relevant element (Issue #1359)
- Re: [whatwg/dom] setNamedItem doesn't adopt the attr node to the ownerDocument of the relevant element (Issue #1359)
Re: [w3ctag/design-reviews] Delegation-oriented FedCM (Issue #1039)
Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
Re: [w3c/push-api] Expose pushManager on Window (PR #393)
Re: [whatwg/fullscreen] How should UAs hide root element scrollbars? (Issue #236)
[whatwg/dom] Clarify composedPath() method steps with an assert (PR #1358)
- Re: [whatwg/dom] Clarify composedPath() method steps with an assert (PR #1358)
- Re: [whatwg/dom] Clarify composedPath() method steps with an assert (PR #1358)
Re: [w3c/push-api] Declarative Web Push (Issue #360)
Re: [w3c/uievents] Converge with CSSOM-View (#24)
[whatwg/fullscreen] Meta: disambiguate "document" for Bikeshed (PR #244)
- Re: [whatwg/fullscreen] Meta: disambiguate "document" for Bikeshed (PR #244)
- Re: [whatwg/fullscreen] Meta: disambiguate "document" for Bikeshed (PR #244)
Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106)
Re: [whatwg/fullscreen] Document fullscreening vs. modal dialog (Issue #227)
Re: [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217)
- Re: [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217)
- Re: [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217)
Re: [w3c/gamepad] chore(auto-publish.yml): enable VALIDATE_INPUT_MARKUP (PR #218)
Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746)
- Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746)
- Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746)
Re: [w3c/ServiceWorker] Editorial: Add notice on the _or condition depth. (PR #1714)
- Re: [w3c/ServiceWorker] Editorial: Add notice on the _or condition depth. (PR #1714)
- Re: [w3c/ServiceWorker] Editorial: Add notice on the _or condition depth. (PR #1714)
[whatwg/dom] 9021345194 (Issue #1357)
[whatwg/dom] 7040724019 (Issue #1356)
[whatwg/dom] https://t.me/elon_reeve_musk_tesla_spx (Issue #1355)
[whatwg/webidl] Intent to use Constants (Issue #1469)
Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391)
- Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391)
- Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391)
- Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391)
- Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391)
- Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391)
- Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391)
- Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391)
Re: [w3ctag/design-reviews] CSS if() function (Issue #1045)
[w3c/manifest] editorial: Refine the definition of an installable web application (PR #1164)
Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
Re: [WICG/webcomponents] [exportparts] support exporting via wildcards `exportparts="*, primary-*"` (Issue #1051)
Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083)
- Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083)
- Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083)
- Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083)
- Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083)
- Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083)
- Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083)
[w3ctag/design-reviews] WebRTC Encoded Transform Timestamps (Issue #1049)
Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458)
- Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458)
- Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458)
- Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458)
- Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458)
- Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458)
- Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458)
- Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458)
Re: [w3ctag/design-reviews] Navigation API deferred commit (Issue #1040)
Re: [w3c/manifest] Define "web application" (Issue #1097)
[w3c/manifest] Add installable web application definition (PR #1163)
- Re: [w3c/manifest] Add installable web application definition (PR #1163)
- Re: [w3c/manifest] Add installable web application definition (PR #1163)
- Re: [w3c/manifest] Add installable web application definition (PR #1163)
- Re: [w3c/manifest] Add installable web application definition (PR #1163)
- Re: [w3c/manifest] Add installable web application definition (PR #1163)
- Re: [w3c/manifest] Editorial: Add installable web application definition (PR #1163)
- Re: [w3c/manifest] Editorial: Add installable web application definition (PR #1163)
- Re: [w3c/manifest] Editorial: Add installable web application definition (PR #1163)
Re: [w3c/manifest] Link incubations (PR #1153)
Re: [w3c/manifest] "internationalization" section (Issue #1090)
- Re: [w3c/manifest] "internationalization" section (Issue #1090)
- Re: [w3c/manifest] "internationalization" section (Issue #1090)
Re: [w3c/manifest] "link capturing" on the web platform into an installed web app (Issue #1138)
Re: [w3c/manifest] Add guidance for user agents about how to prevent malicious localization strings (Issue #1150)
Re: [w3c/manifest] Add a manifest option for the declaration the "version" of the web application (Issue #1036)
Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)
- Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)
- Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)
- Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)
- Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)
- Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)
- Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)
- Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)
- Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)
- Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)
- Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)
Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157)
- Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157)
- Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157)
[w3ctag/design-reviews] `require-sri-for` CSP directive (Issue #1048)
Re: [w3ctag/design-reviews] Accessibility conformance Testing (ACT) Rules Format 1.1 (Issue #977)
Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
[whatwg/dom] Meta: export "signal abort" (PR #1354)
- Re: [whatwg/dom] Meta: export "signal abort" (PR #1354)
- Re: [whatwg/dom] Meta: export "signal abort" (PR #1354)
[w3c/manifest] Feature Request: Support video ( webm ) icons in manifest (Issue #1162)
- Re: [w3c/manifest] Feature Request: Support video ( webm ) icons in manifest (Issue #1162)
- Re: [w3c/manifest] Feature Request: Support video ( webm ) icons in manifest (Issue #1162)
[whatwg/fetch] Add a "webtransport" request mode (Issue #1808)
Re: [w3c/ServiceWorker] Responding to cross-origin requests using a worker? (#130)
Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093)
- Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093)
- Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093)
- Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093)
- Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093)
- Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093)
- Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093)
- Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093)
- Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533)
Re: [w3ctag/design-reviews] Custom Functions (@function) (Issue #1031)
[w3c/uievents] Clarify `mousemove` event target if preceding `mouseout`, `mouseleave`, `mouseover` or `mouseenter` event listener removes the `mouseover` target (Issue #393)
Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932)
- Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932)
- Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932)
- Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932)
- Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932)
[whatwg/dom] Add reference target to shadow root (PR #1353)
Re: [w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690)
[w3ctag/design-reviews] Early Design Review: Related Website Partition API (Issue #1047)
[whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243)
- Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243)
- Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243)
- Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243)
- Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243)
- Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243)
- Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243)
- Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243)
- Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243)
- Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243)
Re: [w3c/ServiceWorker] InstallEvent.addRoutes is resolving/rejecting the returned promise synchronously (Issue #1742)
Re: [w3c/ServiceWorker] Should InstallEvent.addRoutes reject if the the install event is not active? (Issue #1743)
Re: [whatwg/dom] Declarative Shadow DOM (#510)
Re: [w3c/ServiceWorker] Allow the addRoutes() to be called during installing (PR #1744)
[whatwg/webidl] Intent to use Constants (Issue #1468)
Re: [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014)
- Re: [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014)
- Re: [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014)
Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807)
- Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807)
- Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807)
- Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807)
- Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807)
[whatwg/webidl] Intent to use Constants (Issue #1467)
[w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479)
- Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479)
Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
- Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752)
Re: [WICG/webcomponents] [Proposal] Stylesheet Observer (Issue #1041)
Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343)
- Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343)
- Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343)
- Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343)
- Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343)
- Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343)
[whatwg/dom] A slottable's assigned slot is never reset (Issue #1352)
- Re: [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352)
- Re: [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352)
- Re: [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352)