public-webapps-github@w3.org from February 2025 by date

Saturday, 22 February 2025

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) Valery Zinchenko
• Re: [w3c/clipboard-apis] [clipboard-apis] .write() for text/html doesn't define a canonical form (Issue #233) Karl Dubost

Friday, 21 February 2025

• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Monica Chintala
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Monica Chintala
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Monica Chintala
• Re: [WICG/webcomponents] HTML Modules (#645) edbaafi
• Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439) Joshua Bell
• Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439) Joshua Bell
• Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439) Steven Becker
• Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439) Joshua Bell
• Re: [whatwg/webidl] Cypto-os (Issue #1473) Meghan Denny
• [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439) Joshua Bell
• [whatwg/webidl] Cypto-os (Issue #1473) Cypto-os
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) Aaron Selya
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) Aaron Selya
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) Aaron Selya
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) Aaron Selya
• Re: [whatwg/webidl] Intent to use Constants (Issue #1472) Anne van Kesteren
• [whatwg/webidl] Intent to use Constants (Issue #1472) pikaroofficial
• Re: [w3ctag/design-reviews] (brand new ✨) Web Install API (Issue #1051) Simon Pieters
• Re: [w3ctag/design-reviews] Accessibility conformance Testing (ACT) Rules Format 1.1 (Issue #977) Daniel Montalvo
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) Anne van Kesteren
• [w3c/clipboard-apis] [clipboard-apis] .write() for text/html doesn't define a canonical form (Issue #233) Karl Dubost
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) Anne van Kesteren
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) Anne van Kesteren
• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) Keith Cirkel
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) Anne van Kesteren
• Re: [whatwg/dom] setNamedItem doesn't adopt the attr node to the ownerDocument of the relevant element (Issue #1359) Anne van Kesteren
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) Anne van Kesteren
• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) Anne van Kesteren
• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) Alice
• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) Alice
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) Domenic Denicola
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) James M Snell
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) Joshua Chen
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) Domenic Denicola
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) Domenic Denicola
• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) Rob Eisenberg
• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) Dan Clark
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) Dan Clark
• [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) Mason Freed
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) Alice

Thursday, 20 February 2025

• Re: [w3c/permissions] Proposed Testing Plan for Geolocation Permission (Issue #460) Marcos Cáceres
• [w3c/permissions] Proposed Testing Plan for Geolocation Permission (Issue #460) Marcos Cáceres
• Re: [w3c/permissions] Editorial: Prepare for CR (PR #457) Marcos Cáceres
• Re: [w3c/permissions] Editorial: Prepare for CR (PR #457) Marcos Cáceres
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) Marcos Cáceres
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) Marcos Cáceres
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) Marcos Cáceres
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) Joshua Chen
• [w3ctag/design-reviews] Incremental Font Transfer (Issue #1057) Chris Lilley
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Anne van Kesteren
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) Anne van Kesteren
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) Anne van Kesteren
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Anne van Kesteren
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [w3c/gamepad] Add a means to test the API (Issue #175) Maksim Sadym
• [w3ctag/design-reviews] CSS Stylable Columns (Issue #1056) Xiaocheng Hu
• [w3ctag/design-reviews] CSS inert (Issue #1055) Xiaocheng Hu
• [w3ctag/design-reviews] CSS Scroll Buttons (Issue #1054) Xiaocheng Hu
• [w3ctag/design-reviews] CSS Scroll Markers (Issue #1053) Xiaocheng Hu
• Re: [w3ctag/design-reviews] Invokers API (Issue #920) Martin Thomson

Wednesday, 19 February 2025

• Re: [w3ctag/design-reviews] Call stacks in crash reports from unresponsive web pages (Issue #981) Jeffrey Yasskin
• Re: [whatwg/fetch] Proposal: `Request.json` helper (Issue #1791) Denis Migdal
• Re: [w3ctag/design-reviews] Call stacks in crash reports from unresponsive web pages (Issue #981) Andy Luhrs
• Re: [whatwg/fetch] Proposal: `Request.json` helper (Issue #1791) rossipedia
• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) Stephen McGruer
• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) aneeshali
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Johannes Wilm
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Johannes Wilm
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Philippe Le Hegaret
• Re: [whatwg/dom] Add definition for composed selection range (PR #1342) Sean Feng
• Re: [whatwg/dom] Add definition for composed selection range (PR #1342) smaug----
• Re: [w3ctag/design-reviews] CSS Overflow Navigation Controls (Issue #1037) Robert Flack
• Re: [w3c/selection-api] Change Selection to be associated with a composed live range (PR #345) Sean Feng
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Xiaoqian Wu
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Johannes Wilm
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Xiaoqian Wu
• Re: [whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361) Andrea Giammarchi
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Johannes Wilm
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Johannes Wilm
• Re: [whatwg/fetch] x content types added (PR #1810) Anne van Kesteren
• [whatwg/fetch] x content types added (PR #1810) Navodya Divyanjali
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Xiaoqian Wu
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Xiaoqian Wu
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Anne van Kesteren
• Re: [whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361) Anne van Kesteren
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Johannes Wilm
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Johannes Wilm
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Xiaoqian Wu
• Re: [whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361) Keith Cirkel
• [whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361) kkmuffme
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) smaug----
• Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232) roraja
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) Noam Rosenthal
• Re: [w3ctag/design-reviews] CSS Overflow Navigation Controls (Issue #1037) Xiaocheng Hu
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) Noam Rosenthal
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) Martin Thomson
• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) Xiaocheng Hu
• Re: [w3ctag/design-reviews] CSS `dynamic-range-limit` (Issue #1027) Xiaocheng Hu
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) Noam Rosenthal
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) Martin Thomson
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) Noam Rosenthal
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) Martin Thomson
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) Anne van Kesteren
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) Domenic Denicola
• Re: [whatwg/dom] Add definition for composed selection range (PR #1342) Di Zhang

Tuesday, 18 February 2025

• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) Alice
• Re: [whatwg/dom] Trusted types attributes (PR #1268) smaug----
• [w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052) Daniel Rubery
• Re: [whatwg/url] Review Draft Publication: February 2025 (PR #857) Anne van Kesteren
• Re: [whatwg/url] Review Draft Publication: February 2025 (PR #857) Anne van Kesteren
• Re: [whatwg/url] Meta: address Bikeshed errors (PR #858) Anne van Kesteren
• [whatwg/url] Meta: address Bikeshed errors (PR #858) Anne van Kesteren
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) Kagami Sascha Rosylight
• Re: [whatwg/dom] setNamedItem doesn't adopt the attr node to the ownerDocument of the relevant element (Issue #1359) Anne van Kesteren
• [whatwg/dom] Update an attribute's node document (PR #1360) Anne van Kesteren
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Anne van Kesteren
• [w3c/permissions] Aspects and integration with Permissions Policy (Issue #459) Antonio Sartori
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) Anne van Kesteren
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) Denis Migdal
• 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) Tetsuharu Ohzeki
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) Anne van Kesteren
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) Denis Migdal
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) Denis Migdal
• 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) Yoshisato Yanagisawa
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) Anne van Kesteren
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) Anne van Kesteren
• Re: [w3ctag/design-reviews] Signature-Based Integrity. (Issue #1041) Mike West
• Re: [w3ctag/design-reviews] Signature-Based Integrity. (Issue #1041) Martin Thomson

Monday, 17 February 2025

• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) Alice
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) Denis Migdal
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) Anne van Kesteren
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) Anne van Kesteren
• [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) Denis Migdal
• Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960) Denis Migdal
• 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) Tetsuharu Ohzeki
• 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) Tetsuharu Ohzeki
• Re: [w3c/editing] Valid text element declaration for rich text editing caret accessibility (Issue #481) Johannes Wilm
• Re: [whatwg/streams] Review Draft Publication: February 2025 (PR #1340) Anne van Kesteren
• [w3ctag/design-reviews] (brand new ✨) Web Install API (Issue #1051) Diego Gonzalez
• Re: [whatwg/url] IDNA: avoid defining valid domain string in terms of the parser (#245) Petr Špaček
• [w3c/editing] Valid text element declaration for rich text editing caret accessibility (Issue #481) John A Bilicki III
• Re: [whatwg/streams] Review Draft Publication: February 2025 (PR #1340) sideshowbarker
• Re: [whatwg/url] Review Draft Publication: February 2025 (PR #857) Anne van Kesteren
• [whatwg/url] Review Draft Publication: February 2025 (PR #857) Anne van Kesteren
• [whatwg/streams] Review Draft Publication: February 2025 (PR #1340) Anne van Kesteren
• Re: [w3c/ServiceWorker] Editorial: "mutual exclusive" (Issue #1716) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: "mutual exclusive" (Issue #1716) Yoshisato Yanagisawa
• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) Mattias Buelens
• Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232) Rakesh Goulikar
• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) Anne van Kesteren
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Bill Collins
• 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) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) Mark S. Miller
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Domenic Denicola
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Lea Verou
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Yoshisato Yanagisawa

Sunday, 16 February 2025

• Re: [w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754) Yoshisato Yanagisawa
• Re: [whatwg/url] Parser generates invalid URLs (#379) Anne van Kesteren
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Ivan Čurić
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) Brunojoe1995

Saturday, 15 February 2025

• Re: [whatwg/fetch] Use tasks to manipulate streams (#1270) nestedloops1
• Re: [WICG/webcomponents] Sessions for March 26th W3C Breakout Day 2025 (Issue #1095) Alex
• [WICG/webcomponents] [Template Element] directive expressions (PR #1096) Alex
• Re: [whatwg/url] Are drive letters always invalid? (#612) Alwin Blok
• Re: [whatwg/url] Parser generates invalid URLs (#379) Alwin Blok
• [whatwg/url] Include invalid outputs in the table with valid versus invalid parser inputs (Issue #856) Alwin Blok
• Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270) Noam Rosenthal
• Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270) Noam Rosenthal
• [whatwg/url] Express validity, error correction and percent encode sets in a single table (Issue #855) Alwin Blok
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) Joe Pea
• Re: [whatwg/url] Parser generates invalid URLs (#379) Alwin Blok
• Re: [whatwg/url] Parser generates invalid URLs (#379) Anne van Kesteren
• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) Alwin Blok
• Re: [whatwg/url] Parser generates invalid URLs (#379) Alwin Blok
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) Joe Pea
• Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270) Joe Pea
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) mangelozzi
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) mangelozzi
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Monica Chintala
• [WICG/webcomponents] Sessions for March 26th W3C Breakout Day (Issue #1095) Ryosuke Niwa

Friday, 14 February 2025

• [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) Monica Chintala
• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) Fernando Fiori
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) Mason Freed
• [WICG/webcomponents] [Template Element] template-* attributes (PR #1094) Alex
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) Westbrook Johnson
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) Westbrook Johnson
• Re: [WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072) smaug----
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) Anne van Kesteren
• Re: [WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072) Anne van Kesteren
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) Westbrook Johnson
• Re: [w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754) Monica Chintala
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) Mason Freed
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) Westbrook Johnson
• Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) Henri Sivonen
• Re: [whatwg/fetch] Should network state be keyed beyond the top-level site (#1035) Matt Menke
• Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203) lili2012
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) Andrea Giammarchi
• Re: [whatwg/encoding] Standardize x-mac-greek, x-mac-centraleurroman, and x-mac-turkish (Issue #342) Adam Rice
• Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) Adam Rice
• Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) Henri Sivonen
• Re: [whatwg/webidl] Consider renaming ByteString to IsomorphicString (Issue #1471) Domenic Denicola
• [whatwg/webidl] Consider renaming ByteString to IsomorphicString (Issue #1471) Anne van Kesteren
• Re: [w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754) Yoshisato Yanagisawa
• [w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] No examples around addRoutes() API (Issue #1717) Yoshisato Yanagisawa
• Re: [w3c/editing] Disable `formatBlock` for `contenteditable=plaintext-only` (Issue #478) Masayuki Nakano
• Re: [whatwg/fetch] Should network state be keyed beyond the top-level site (#1035) Andrew Williams
• Re: [w3c/gamepad] Fold extensions.html into main spec (Issue #165) Matt Reynolds
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Matt Reynolds
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Matt Reynolds
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Gabriel Brito
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Matt Reynolds
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Matt Reynolds
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) Matt Reynolds
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Matt Reynolds
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Gabriel Brito
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Matt Reynolds
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Matt Reynolds
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Marcos Cáceres
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Gabriel Brito
• Re: [w3c/gamepad] chore(auto-publish.yml): enable VALIDATE_INPUT_MARKUP (PR #218) Marcos Cáceres
• Re: [w3c/gamepad] Interop 2025 investigation effort - Gamepad API testing (Issue #219) Daniel Adams

Thursday, 13 February 2025

• [w3c/gamepad] Interop 2025 investigation effort - Gamepad API testing (Issue #219) Matt Reynolds
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) Dino Reić
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) perrelet
• Re: [whatwg/encoding] Standardize x-mac-greek, x-mac-centraleurroman, and x-mac-turkish (Issue #342) Joshua Bell
• Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) Joshua Bell
• Re: [w3ctag/design-reviews] Invokers API (Issue #920) Luke Warlow
• Re: [whatwg/dom] Add definition for composed selection range (PR #1342) Anne van Kesteren
• Re: [whatwg/dom] Add definition for composed selection range (PR #1342) Anne van Kesteren
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) Frank Topel
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) Andrea Giammarchi
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) Danny Engelman
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Johannes Wilm
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) Andrea Giammarchi
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Anne van Kesteren
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Daniel Vogelheim
• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) Anne van Kesteren
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) mangelozzi
• Re: [w3c/uievents] Converge with CSSOM-View (#24) jgraham
• Re: [w3c/ServiceWorker] Require `[SecureContext]` for interfaces with `[Exposed=ServiceWorker]` or not? (Issue #1749) Kagami Sascha Rosylight
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) Anne van Kesteren
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) Kagami Sascha Rosylight
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [w3ctag/design-reviews] CSS Gap Decorations (Issue #1035) Xiaocheng Hu
• Re: [w3ctag/design-reviews] CSS Gap Decorations (Issue #1035) Xiaocheng Hu
• [whatwg/encoding] Standardize x-mac-greek, x-mac-centraleurroman, and x-mac-turkish (Issue #342) Anne van Kesteren
• Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) Anne van Kesteren
• [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) Anne van Kesteren
• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) Xiaocheng Hu
• [whatwg/xhr] Xbox sign in (Issue #396) ODOGwU15yrs
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) perrelet
• Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753) Yoshisato Yanagisawa

Wednesday, 12 February 2025

• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) Fernando Fiori
• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) Martin Thomson
• Re: [w3ctag/design-reviews] safe-area-max-inset-* variables (Issue #1046) Xiaocheng Hu
• Re: [w3ctag/design-reviews] safe-area-max-inset-* variables (Issue #1046) Xiaocheng Hu
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) Johann Hofmann
• Re: [w3ctag/design-reviews] View Transition Classes (Issue #938) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] View Transition Classes (Issue #938) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) Sarven Capadisli
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) Johann Hofmann
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) Bradley Needham
• Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753) Monica Chintala
• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) Howard Wolosky
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) Anne van Kesteren
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) Kagami Sascha Rosylight
• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) Yves Lafon
• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) Yves Lafon
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) Anne van Kesteren
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) Anne van Kesteren
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) Anne van Kesteren
• Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232) Luke (Zgroza) Klimek
• Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468) Johannes Wilm
• Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468) Johannes Wilm
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) Simon Pieters
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) Johannes Wilm
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) Johannes Wilm
• [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and the immediately republish as a Discontinued Draft (Issue #480) Johannes Wilm
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) Simon Pieters
• Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753) Shunya Shishido
• Re: [w3c/ServiceWorker] Fixing some spec linking issues (PR #1640) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Fixing some spec linking issues (PR #1640) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753) Yoshisato Yanagisawa
• [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753) Yoshisato Yanagisawa
• Re: [w3c/DOM-Parsing] GitHub actions: replace ubuntu-20.04 with ubuntu-latest (PR #86) Domenic Denicola
• Re: [w3c/DOM-Parsing] GitHub actions: replace ubuntu-20.04 with ubuntu-latest (PR #86) Domenic Denicola
• Re: [whatwg/webidl] Variable in step 9.2 of #wait-for-all should be renamed `fulfillmentHandlerSteps` (Issue #1470) Andreas Farre
• [whatwg/webidl] Variable in step 9.2 of #wait-for-all should be renamed `fulfillmentHandlerSteps` (Issue #1470) Andreas Farre
• Re: [w3ctag/design-reviews] CSS if() function (Issue #1045) Xiaocheng Hu
• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) Xiaocheng Hu
• [w3c/DOM-Parsing] GitHub actions: replace ubuntu-20.04 with ubuntu-latest (PR #86) Denis Ah-Kang
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) Anne van Kesteren
• Re: [whatwg/dom] Clarify composedPath() method steps with an assert (PR #1358) Anne van Kesteren
• [whatwg/fetch] Added example for X-Content-Type-Options in Fetch Standard (PR #1809) Saara Bilyour
• Re: [whatwg/dom] Clarify composedPath() method steps with an assert (PR #1358) Domenic Denicola
• Re: [w3c/ServiceWorker] serviceworker for iframes with srcdoc (#765) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] serviceworker for iframes with srcdoc (#765) Yoshisato Yanagisawa
• Re: [w3c/pointerlock] Unclear if `pointermove` should set `movementX/Y` (Issue #100) smaug----

Tuesday, 11 February 2025

• [w3ctag/design-reviews] Permissions Policy reports for iframes (Issue #1050) Jun
• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) Martin Thomson
• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) Martin Thomson
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) Kyra Seevers
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) hober
• Re: [w3c/uievents] Converge with CSSOM-View (#24) Mustaq Ahmed
• Re: [whatwg/fullscreen] Deal with two fullscreen elements in top layer and one element being removed (#133) Philip Jägenstedt
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) Kagami Sascha Rosylight
• Re: [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217) Philip Jägenstedt
• Re: [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217) Philip Jägenstedt
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) Philip Jägenstedt
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) Philip Jägenstedt
• Re: [whatwg/fetch] Define what consequences NULL bytes (0x00) or other invalid values in header names have (Issue #1747) Jannis Rautenstrauch
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) Philip Jägenstedt
• [whatwg/dom] setNamedItem doesn't adopt the attr node to the ownerDocument of the relevant element (Issue #1359) smaug----
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) Kagami Sascha Rosylight
• Re: [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352) Anne van Kesteren
• Re: [w3ctag/design-reviews] Delegation-oriented FedCM (Issue #1039) Martin Thomson

Monday, 10 February 2025

• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) Daniel Appelquist
• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) Daniel Appelquist
• Re: [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352) Simon Wülker
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) Tim Nguyen
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Frédéric Wang
• Re: [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014) Jeffrey Yasskin
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) Anne van Kesteren
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) Kagami Sascha Rosylight
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) Philip Jägenstedt
• Re: [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352) Anne van Kesteren
• Re: [whatwg/fullscreen] How should UAs hide root element scrollbars? (Issue #236) Tim Nguyen
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) Tim Nguyen
• [whatwg/dom] Clarify composedPath() method steps with an assert (PR #1358) Anne van Kesteren
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) Tim Nguyen
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) Kagami Sascha Rosylight
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) Philip Jägenstedt
• Re: [whatwg/fullscreen] Meta: disambiguate "document" for Bikeshed (PR #244) Philip Jägenstedt
• Re: [w3c/push-api] Declarative Web Push (Issue #360) Anne van Kesteren
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) Anne van Kesteren
• Re: [whatwg/fullscreen] Meta: disambiguate "document" for Bikeshed (PR #244) Anne van Kesteren
• Re: [w3c/uievents] Converge with CSSOM-View (#24) jgraham
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) Philip Jägenstedt
• [whatwg/fullscreen] Meta: disambiguate "document" for Bikeshed (PR #244) Philip Jägenstedt
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) Anne van Kesteren
• Re: [whatwg/fullscreen] Document fullscreening vs. modal dialog (Issue #227) Edgar Chen
• Re: [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217) Philip Jägenstedt
• Re: [w3c/gamepad] chore(auto-publish.yml): enable VALIDATE_INPUT_MARKUP (PR #218) Bradley Needham
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) Shunya Shishido
• Re: [w3c/ServiceWorker] Editorial: Add notice on the _or condition depth. (PR #1714) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Add notice on the _or condition depth. (PR #1714) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: Add notice on the _or condition depth. (PR #1714) Shunya Shishido
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Yoshisato Yanagisawa

Sunday, 9 February 2025

• Re: [whatwg/dom] 9021345194 (Issue #1357) Keith Cirkel
• Re: [whatwg/dom] 7040724019 (Issue #1356) Keith Cirkel
• Re: [whatwg/dom] https://t.me/elon_reeve_musk_tesla_spx (Issue #1355) Keith Cirkel
• [whatwg/dom] 9021345194 (Issue #1357) PaidParker22
• [whatwg/dom] 7040724019 (Issue #1356) PaidParker22
• [whatwg/dom] https://t.me/elon_reeve_musk_tesla_spx (Issue #1355) PaidParker22
• [whatwg/webidl] Intent to use Constants (Issue #1469) Fiyaas
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) Peter Beverloo
• Re: [whatwg/url] Support relative URLs (#531) Alwin Blok
• Re: [whatwg/url] Support relative URLs (#531) Alwin Blok
• Re: [w3ctag/design-reviews] CSS if() function (Issue #1045) Daniel Appelquist

Saturday, 8 February 2025

• Re: [whatwg/url] Support relative URLs (#531) Karl
• Re: [whatwg/url] Support relative URLs (#531) Thayne McCombs
• Re: [whatwg/url] Support relative URLs (#531) James M Snell
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) J. S. Choi
• Re: [w3c/manifest] editorial: Refine the definition of an installable web application (PR #1164) Ben Francis
• [w3c/manifest] editorial: Refine the definition of an installable web application (PR #1164) Ben Francis
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) tophf
• Re: [whatwg/url] Support relative URLs (#531) Matt
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) nickchomey
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) Andrew Sutherland

Friday, 7 February 2025

• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) Westbrook Johnson
• Re: [WICG/webcomponents] [exportparts] support exporting via wildcards `exportparts="*, primary-*"` (Issue #1051) Steve Orvell
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) tophf
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) nickchomey
• Re: [w3c/manifest] Editorial: Add installable web application definition (PR #1163) Ben Francis
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) Westbrook Johnson
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) Andrew Sutherland
• [w3ctag/design-reviews] WebRTC Encoded Transform Timestamps (Issue #1049) guidou
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Daniel Vogelheim
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) Johann Hofmann
• Re: [w3c/manifest] Link incubations (PR #1153) Christian Liebel
• Re: [w3c/manifest] Link incubations (PR #1153) Christian Liebel
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) nickchomey
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Frédéric Wang
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Frédéric Wang
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Frédéric Wang
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Frédéric Wang
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) Yoshisato Yanagisawa
• Re: [whatwg/dom] Meta: export "signal abort" (PR #1354) Domenic Denicola
• Re: [whatwg/dom] Meta: export "signal abort" (PR #1354) Domenic Denicola
• Re: [w3ctag/design-reviews] Navigation API deferred commit (Issue #1040) Domenic Denicola
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) nickchomey
• Re: [w3c/manifest] Define "web application" (Issue #1097) Marcos Cáceres
• Re: [w3c/manifest] Editorial: Add installable web application definition (PR #1163) Marcos Cáceres
• Re: [w3c/manifest] Editorial: Add installable web application definition (PR #1163) Marcos Cáceres
• Re: [w3c/manifest] Add installable web application definition (PR #1163) Marcos Cáceres
• Re: [w3c/manifest] Add installable web application definition (PR #1163) Marcos Cáceres
• Re: [w3c/manifest] Add installable web application definition (PR #1163) Daniel Murphy
• Re: [w3c/manifest] Add installable web application definition (PR #1163) Marcos Cáceres
• Re: [w3c/manifest] Add installable web application definition (PR #1163) Daniel Murphy
• [w3c/manifest] Add installable web application definition (PR #1163) Daniel Murphy
• Re: [w3c/manifest] "internationalization" section (Issue #1090) Addison Phillips

Thursday, 6 February 2025

• Re: [w3c/manifest] Link incubations (PR #1153) Marcos Cáceres
• Re: [w3c/manifest] "internationalization" section (Issue #1090) Daniel Murphy
• Re: [w3c/manifest] "internationalization" section (Issue #1090) Daniel Murphy
• Re: [w3c/manifest] "link capturing" on the web platform into an installed web app (Issue #1138) Daniel Murphy
• Re: [w3c/manifest] "link capturing" on the web platform into an installed web app (Issue #1138) Daniel Murphy
• Re: [w3c/manifest] Add guidance for user agents about how to prevent malicious localization strings (Issue #1150) Daniel Murphy
• Re: [w3c/manifest] Add guidance for user agents about how to prevent malicious localization strings (Issue #1150) Daniel Murphy
• Re: [w3c/manifest] Add a manifest option for the declaration the "version" of the web application (Issue #1036) Marcos Cáceres
• Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) Marcos Cáceres
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) J. S. Choi
• Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) Marcos Cáceres
• Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) Marcos Cáceres
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Andrew Sutherland
• Re: [w3c/manifest] Feature Request: Support video ( webm ) icons in manifest (Issue #1162) Marcos Cáceres
• Re: [w3c/manifest] Feature Request: Support video ( webm ) icons in manifest (Issue #1162) Marcos Cáceres
• [w3ctag/design-reviews] `require-sri-for` CSP directive (Issue #1048) Yoav Weiss
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Luke Warlow
• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) Anssi Kostiainen
• Re: [w3ctag/design-reviews] Accessibility conformance Testing (ACT) Rules Format 1.1 (Issue #977) Matthew Tylee Atkinson
• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) Martin Thomson
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Valery Zinchenko
• [whatwg/dom] Meta: export "signal abort" (PR #1354) Domenic Denicola
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Shunya Shishido
• [w3c/manifest] Feature Request: Support video ( webm ) icons in manifest (Issue #1162) Kaido Kert
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Domenic Denicola
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Yoshisato Yanagisawa

Wednesday, 5 February 2025

• [whatwg/fetch] Add a "webtransport" request mode (Issue #1808) Jan-Ivar Bruaroey
• Re: [w3c/ServiceWorker] Responding to cross-origin requests using a worker? (#130) Stephen Crane
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) smaug----
• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) bvandersloot-mozilla
• Re: [w3ctag/design-reviews] Custom Functions (@function) (Issue #1031) Lea Verou
• Re: [w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690) Yoshisato Yanagisawa
• Re: [w3ctag/design-reviews] Custom Functions (@function) (Issue #1031) andruud
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) Johannes Wilm
• Re: [w3c/uievents] Clarify `mousemove` event target if preceding `mouseout`, `mouseleave`, `mouseover` or `mouseenter` event listener removes the `mouseover` target (Issue #393) Masayuki Nakano
• [w3c/uievents] Clarify `mousemove` event target if preceding `mouseout`, `mouseleave`, `mouseover` or `mouseenter` event listener removes the `mouseover` target (Issue #393) Masayuki Nakano
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) Florian Rivoal
• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) Martin Thomson
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Shunya Shishido
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Shunya Shishido
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Yoshisato Yanagisawa

Tuesday, 4 February 2025

• [whatwg/dom] Add reference target to shadow root (PR #1353) Dan Clark
• Re: [w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690) Daniel Abrecht
• [w3ctag/design-reviews] Early Design Review: Related Website Partition API (Issue #1047) Dylan Cutler
• [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) Tim Nguyen
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Shunya Shishido
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Shunya Shishido
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Shunya Shishido
• Re: [w3c/ServiceWorker] InstallEvent.addRoutes is resolving/rejecting the returned promise synchronously (Issue #1742) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Should InstallEvent.addRoutes reject if the the install event is not active? (Issue #1743) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Should InstallEvent.addRoutes reject if the the install event is not active? (Issue #1743) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Allow the addRoutes() to be called during installing (PR #1744) Yoshisato Yanagisawa
• Re: [whatwg/dom] Declarative Shadow DOM (#510) aspiring484

Monday, 3 February 2025

• Re: [w3c/ServiceWorker] Allow the addRoutes() to be called during installing (PR #1744) Monica Chintala
• Re: [whatwg/webidl] Intent to use Constants (Issue #1468) Meghan Denny
• [whatwg/webidl] Intent to use Constants (Issue #1468) peasantman1
• Re: [whatwg/webidl] Intent to use Constants (Issue #1467) Meghan Denny
• Re: [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014) Alex N. Jose
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• [whatwg/webidl] Intent to use Constants (Issue #1467) tahiryousaf313
• [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) Johannes Wilm
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Frederik Braun
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Frédéric Wang
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Shunya Shishido
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Shunya Shishido
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Shunya Shishido
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) Shunya Shishido

Saturday, 1 February 2025

• Re: [WICG/webcomponents] [Proposal] Stylesheet Observer (Issue #1041) Bruce B. Anderson
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) Simon Wülker
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) Anne van Kesteren
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) Anne van Kesteren
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) Simon Wülker
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) Simon Wülker
• [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352) Simon Wülker
• Re: [whatwg/webidl] Leader (Issue #1466) Meghan Denny
• [whatwg/webidl] Leader (Issue #1466) Burberrysmart

Last message date: Saturday, 22 February 2025 15:15:48 UTC