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

Aaron Selya

• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) (Friday, 21 February)
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) (Friday, 21 February)
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) (Friday, 21 February)
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) (Friday, 21 February)

Adam Rice

• Re: [whatwg/encoding] Standardize x-mac-greek, x-mac-centraleurroman, and x-mac-turkish (Issue #342) (Friday, 14 February)
• Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) (Friday, 14 February)

Addison Phillips

• Re: [w3c/manifest] "internationalization" section (Issue #1090) (Friday, 7 February)

Alex

• Re: [WICG/webcomponents] Sessions for March 26th W3C Breakout Day 2025 (Issue #1095) (Saturday, 15 February)
• [WICG/webcomponents] [Template Element] directive expressions (PR #1096) (Saturday, 15 February)
• [WICG/webcomponents] [Template Element] template-* attributes (PR #1094) (Friday, 14 February)

Alex N. Jose

• Re: [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014) (Monday, 3 February)

Alice

• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) (Friday, 21 February)
• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) (Friday, 21 February)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Friday, 21 February)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Tuesday, 18 February)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Monday, 17 February)

Alwin Blok

• Re: [whatwg/url] Are drive letters always invalid? (#612) (Saturday, 15 February)
• Re: [whatwg/url] Parser generates invalid URLs (#379) (Saturday, 15 February)
• [whatwg/url] Include invalid outputs in the table with valid versus invalid parser inputs (Issue #856) (Saturday, 15 February)
• [whatwg/url] Express validity, error correction and percent encode sets in a single table (Issue #855) (Saturday, 15 February)
• Re: [whatwg/url] Parser generates invalid URLs (#379) (Saturday, 15 February)
• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Saturday, 15 February)
• Re: [whatwg/url] Parser generates invalid URLs (#379) (Saturday, 15 February)
• Re: [whatwg/url] Support relative URLs (#531) (Sunday, 9 February)
• Re: [whatwg/url] Support relative URLs (#531) (Sunday, 9 February)

Andrea Giammarchi

• Re: [whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361) (Wednesday, 19 February)
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Friday, 14 February)
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 13 February)
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 13 February)

Andreas Farre

• Re: [whatwg/webidl] Variable in step 9.2 of #wait-for-all should be renamed `fulfillmentHandlerSteps` (Issue #1470) (Wednesday, 12 February)
• [whatwg/webidl] Variable in step 9.2 of #wait-for-all should be renamed `fulfillmentHandlerSteps` (Issue #1470) (Wednesday, 12 February)

Andrew Sutherland

• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Saturday, 8 February)
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Friday, 7 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Thursday, 6 February)

Andrew Williams

• Re: [whatwg/fetch] Should network state be keyed beyond the top-level site (#1035) (Friday, 14 February)

andruud

• Re: [w3ctag/design-reviews] Custom Functions (@function) (Issue #1031) (Wednesday, 5 February)

Andy Luhrs

• Re: [w3ctag/design-reviews] Call stacks in crash reports from unresponsive web pages (Issue #981) (Wednesday, 19 February)

aneeshali

• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Wednesday, 19 February)

Anne van Kesteren

• Re: [whatwg/webidl] Intent to use Constants (Issue #1472) (Friday, 21 February)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Friday, 21 February)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Friday, 21 February)
• Re: [whatwg/dom] Add Scoped Custom Element Registries (PR #1341) (Friday, 21 February)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Friday, 21 February)
• Re: [whatwg/dom] setNamedItem doesn't adopt the attr node to the ownerDocument of the relevant element (Issue #1359) (Friday, 21 February)
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) (Friday, 21 February)
• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) (Friday, 21 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 20 February)
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) (Thursday, 20 February)
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) (Thursday, 20 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 20 February)
• Re: [whatwg/fetch] x content types added (PR #1810) (Wednesday, 19 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361) (Wednesday, 19 February)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Wednesday, 19 February)
• Re: [whatwg/url] Review Draft Publication: February 2025 (PR #857) (Tuesday, 18 February)
• Re: [whatwg/url] Review Draft Publication: February 2025 (PR #857) (Tuesday, 18 February)
• Re: [whatwg/url] Meta: address Bikeshed errors (PR #858) (Tuesday, 18 February)
• [whatwg/url] Meta: address Bikeshed errors (PR #858) (Tuesday, 18 February)
• Re: [whatwg/dom] setNamedItem doesn't adopt the attr node to the ownerDocument of the relevant element (Issue #1359) (Tuesday, 18 February)
• [whatwg/dom] Update an attribute's node document (PR #1360) (Tuesday, 18 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Tuesday, 18 February)
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) (Tuesday, 18 February)
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) (Tuesday, 18 February)
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) (Tuesday, 18 February)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Tuesday, 18 February)
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) (Monday, 17 February)
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) (Monday, 17 February)
• Re: [whatwg/streams] Review Draft Publication: February 2025 (PR #1340) (Monday, 17 February)
• Re: [whatwg/url] Review Draft Publication: February 2025 (PR #857) (Monday, 17 February)
• [whatwg/url] Review Draft Publication: February 2025 (PR #857) (Monday, 17 February)
• [whatwg/streams] Review Draft Publication: February 2025 (PR #1340) (Monday, 17 February)
• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) (Monday, 17 February)
• Re: [whatwg/url] Parser generates invalid URLs (#379) (Sunday, 16 February)
• Re: [whatwg/url] Parser generates invalid URLs (#379) (Saturday, 15 February)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Friday, 14 February)
• Re: [WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072) (Friday, 14 February)
• [whatwg/webidl] Consider renaming ByteString to IsomorphicString (Issue #1471) (Friday, 14 February)
• Re: [whatwg/dom] Add definition for composed selection range (PR #1342) (Thursday, 13 February)
• Re: [whatwg/dom] Add definition for composed selection range (PR #1342) (Thursday, 13 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Thursday, 13 February)
• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Thursday, 13 February)
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) (Thursday, 13 February)
• [whatwg/encoding] Standardize x-mac-greek, x-mac-centraleurroman, and x-mac-turkish (Issue #342) (Thursday, 13 February)
• Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) (Thursday, 13 February)
• [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) (Thursday, 13 February)
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) (Wednesday, 12 February)
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) (Wednesday, 12 February)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Wednesday, 12 February)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Wednesday, 12 February)
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) (Wednesday, 12 February)
• Re: [whatwg/dom] Clarify composedPath() method steps with an assert (PR #1358) (Wednesday, 12 February)
• Re: [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352) (Tuesday, 11 February)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Monday, 10 February)
• Re: [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352) (Monday, 10 February)
• [whatwg/dom] Clarify composedPath() method steps with an assert (PR #1358) (Monday, 10 February)
• Re: [w3c/push-api] Declarative Web Push (Issue #360) (Monday, 10 February)
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) (Monday, 10 February)
• Re: [whatwg/fullscreen] Meta: disambiguate "document" for Bikeshed (PR #244) (Monday, 10 February)
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) (Monday, 10 February)
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) (Saturday, 1 February)
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) (Saturday, 1 February)

Anssi Kostiainen

• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Thursday, 6 February)

Antonio Sartori

• [w3c/permissions] Aspects and integration with Permissions Policy (Issue #459) (Tuesday, 18 February)

aspiring484

• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Tuesday, 4 February)

Ben Francis

• Re: [w3c/manifest] editorial: Refine the definition of an installable web application (PR #1164) (Saturday, 8 February)
• [w3c/manifest] editorial: Refine the definition of an installable web application (PR #1164) (Saturday, 8 February)
• Re: [w3c/manifest] Editorial: Add installable web application definition (PR #1163) (Friday, 7 February)

Bill Collins

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 17 February)

Bradley Needham

• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Wednesday, 12 February)
• Re: [w3c/gamepad] chore(auto-publish.yml): enable VALIDATE_INPUT_MARKUP (PR #218) (Monday, 10 February)

Bruce B. Anderson

• Re: [WICG/webcomponents] [Proposal] Stylesheet Observer (Issue #1041) (Saturday, 1 February)

Brunojoe1995

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

Burberrysmart

• [whatwg/webidl] Leader (Issue #1466) (Saturday, 1 February)

bvandersloot-mozilla

• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Wednesday, 5 February)
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Tuesday, 4 February)
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Tuesday, 4 February)
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Monday, 3 February)

Chris Lilley

• [w3ctag/design-reviews] Incremental Font Transfer (Issue #1057) (Thursday, 20 February)

Christian Liebel

• Re: [w3c/manifest] Link incubations (PR #1153) (Friday, 7 February)
• Re: [w3c/manifest] Link incubations (PR #1153) (Friday, 7 February)

Cypto-os

• [whatwg/webidl] Cypto-os (Issue #1473) (Friday, 21 February)

Dan Clark

• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) (Friday, 21 February)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Friday, 21 February)
• [whatwg/dom] Add reference target to shadow root (PR #1353) (Tuesday, 4 February)

Daniel Abrecht

• Re: [w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690) (Tuesday, 4 February)

Daniel Adams

• Re: [w3c/gamepad] Interop 2025 investigation effort - Gamepad API testing (Issue #219) (Friday, 14 February)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Monday, 10 February)
• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Monday, 10 February)
• Re: [w3ctag/design-reviews] CSS if() function (Issue #1045) (Sunday, 9 February)

Daniel Montalvo

• Re: [w3ctag/design-reviews] Accessibility conformance Testing (ACT) Rules Format 1.1 (Issue #977) (Friday, 21 February)

Daniel Murphy

• Re: [w3c/manifest] Add installable web application definition (PR #1163) (Friday, 7 February)
• Re: [w3c/manifest] Add installable web application definition (PR #1163) (Friday, 7 February)
• [w3c/manifest] Add installable web application definition (PR #1163) (Friday, 7 February)
• Re: [w3c/manifest] "internationalization" section (Issue #1090) (Thursday, 6 February)
• Re: [w3c/manifest] "internationalization" section (Issue #1090) (Thursday, 6 February)
• Re: [w3c/manifest] "link capturing" on the web platform into an installed web app (Issue #1138) (Thursday, 6 February)
• Re: [w3c/manifest] "link capturing" on the web platform into an installed web app (Issue #1138) (Thursday, 6 February)
• Re: [w3c/manifest] Add guidance for user agents about how to prevent malicious localization strings (Issue #1150) (Thursday, 6 February)
• Re: [w3c/manifest] Add guidance for user agents about how to prevent malicious localization strings (Issue #1150) (Thursday, 6 February)

Daniel Rubery

• [w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052) (Tuesday, 18 February)

Daniel Vogelheim

• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 13 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Friday, 7 February)

Danny Engelman

• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 13 February)

Denis Ah-Kang

• [w3c/DOM-Parsing] GitHub actions: replace ubuntu-20.04 with ubuntu-latest (PR #86) (Wednesday, 12 February)

Denis Migdal

• Re: [whatwg/fetch] Proposal: `Request.json` helper (Issue #1791) (Wednesday, 19 February)
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) (Tuesday, 18 February)
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) (Tuesday, 18 February)
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) (Tuesday, 18 February)
• Re: [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) (Monday, 17 February)
• [WICG/webcomponents] Creating non-ugraded defined custom element : `createElement(tagname, {upgrade:false})` (Issue #1097) (Monday, 17 February)
• Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960) (Monday, 17 February)

Di Zhang

• Re: [whatwg/dom] Add definition for composed selection range (PR #1342) (Wednesday, 19 February)

Diego Gonzalez

• [w3ctag/design-reviews] (brand new ✨) Web Install API (Issue #1051) (Monday, 17 February)

Dino Reić

• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 13 February)

Domenic Denicola

• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Friday, 21 February)
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Friday, 21 February)
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) (Friday, 21 February)
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) (Wednesday, 19 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [whatwg/webidl] Consider renaming ByteString to IsomorphicString (Issue #1471) (Friday, 14 February)
• Re: [w3c/DOM-Parsing] GitHub actions: replace ubuntu-20.04 with ubuntu-latest (PR #86) (Wednesday, 12 February)
• Re: [w3c/DOM-Parsing] GitHub actions: replace ubuntu-20.04 with ubuntu-latest (PR #86) (Wednesday, 12 February)
• Re: [whatwg/dom] Clarify composedPath() method steps with an assert (PR #1358) (Wednesday, 12 February)
• Re: [whatwg/dom] Meta: export "signal abort" (PR #1354) (Friday, 7 February)
• Re: [whatwg/dom] Meta: export "signal abort" (PR #1354) (Friday, 7 February)
• Re: [w3ctag/design-reviews] Navigation API deferred commit (Issue #1040) (Friday, 7 February)
• [whatwg/dom] Meta: export "signal abort" (PR #1354) (Thursday, 6 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Thursday, 6 February)

Dylan Cutler

• [w3ctag/design-reviews] Early Design Review: Related Website Partition API (Issue #1047) (Tuesday, 4 February)

edbaafi

• Re: [WICG/webcomponents] HTML Modules (#645) (Friday, 21 February)

Edgar Chen

• Re: [whatwg/fullscreen] Document fullscreening vs. modal dialog (Issue #227) (Monday, 10 February)

Fernando Fiori

• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) (Friday, 14 February)
• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) (Wednesday, 12 February)

Fiyaas

• [whatwg/webidl] Intent to use Constants (Issue #1469) (Sunday, 9 February)

Florian Rivoal

• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) (Wednesday, 5 February)

Frank Topel

• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 13 February)

Frederik Braun

• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Monday, 3 February)

Frédéric Wang

• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Monday, 10 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Friday, 7 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Friday, 7 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Friday, 7 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Friday, 7 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Monday, 3 February)

Gabriel Brito

• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)

guidou

• [w3ctag/design-reviews] WebRTC Encoded Transform Timestamps (Issue #1049) (Friday, 7 February)

Henri Sivonen

• Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) (Friday, 14 February)
• Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) (Friday, 14 February)

hober

• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Tuesday, 11 February)

Howard Wolosky

• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) (Wednesday, 12 February)

Ivan Čurić

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Sunday, 16 February)

J. S. Choi

• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Saturday, 8 February)
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Thursday, 6 February)

James M Snell

• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Friday, 21 February)
• Re: [whatwg/url] Support relative URLs (#531) (Saturday, 8 February)

Jan-Ivar Bruaroey

• [whatwg/fetch] Add a "webtransport" request mode (Issue #1808) (Wednesday, 5 February)

Jannis Rautenstrauch

• Re: [whatwg/fetch] Define what consequences NULL bytes (0x00) or other invalid values in header names have (Issue #1747) (Tuesday, 11 February)

Jeffrey Yasskin

• Re: [w3ctag/design-reviews] Call stacks in crash reports from unresponsive web pages (Issue #981) (Wednesday, 19 February)
• Re: [w3ctag/design-reviews] View Transition Classes (Issue #938) (Wednesday, 12 February)
• Re: [w3ctag/design-reviews] View Transition Classes (Issue #938) (Wednesday, 12 February)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Tuesday, 11 February)
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Tuesday, 11 February)
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) (Tuesday, 11 February)
• Re: [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014) (Monday, 10 February)
• Re: [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014) (Monday, 10 February)

jgraham

• Re: [w3c/uievents] Converge with CSSOM-View (#24) (Thursday, 13 February)
• Re: [w3c/uievents] Converge with CSSOM-View (#24) (Monday, 10 February)

Joe Pea

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Saturday, 15 February)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Saturday, 15 February)
• Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270) (Saturday, 15 February)

Johann Hofmann

• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Wednesday, 12 February)
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) (Wednesday, 12 February)
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) (Friday, 7 February)

Johannes Wilm

• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [w3c/editing] Valid text element declaration for rich text editing caret accessibility (Issue #481) (Monday, 17 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Thursday, 13 February)
• Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468) (Wednesday, 12 February)
• Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468) (Wednesday, 12 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) (Wednesday, 12 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) (Wednesday, 12 February)
• [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and the immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 12 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) (Wednesday, 5 February)
• [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) (Monday, 3 February)

John A Bilicki III

• [w3c/editing] Valid text element declaration for rich text editing caret accessibility (Issue #481) (Monday, 17 February)

Joshua Bell

• Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439) (Friday, 21 February)
• Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439) (Friday, 21 February)
• Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439) (Friday, 21 February)
• [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439) (Friday, 21 February)
• Re: [whatwg/encoding] Standardize x-mac-greek, x-mac-centraleurroman, and x-mac-turkish (Issue #342) (Thursday, 13 February)
• Re: [whatwg/encoding] Add windows-936-2000 as label for GBK (PR #341) (Thursday, 13 February)

Joshua Chen

• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Friday, 21 February)
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Thursday, 20 February)

Jun

• [w3ctag/design-reviews] Permissions Policy reports for iframes (Issue #1050) (Tuesday, 11 February)

Kagami Sascha Rosylight

• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Tuesday, 18 February)
• Re: [w3c/ServiceWorker] Require `[SecureContext]` for interfaces with `[Exposed=ServiceWorker]` or not? (Issue #1749) (Thursday, 13 February)
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) (Thursday, 13 February)
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) (Thursday, 13 February)
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) (Wednesday, 12 February)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Tuesday, 11 February)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Tuesday, 11 February)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Monday, 10 February)
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) (Monday, 10 February)
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) (Monday, 10 February)

Kaido Kert

• [w3c/manifest] Feature Request: Support video ( webm ) icons in manifest (Issue #1162) (Thursday, 6 February)

Karl

• Re: [whatwg/url] Support relative URLs (#531) (Saturday, 8 February)

Karl Dubost

• Re: [w3c/clipboard-apis] [clipboard-apis] .write() for text/html doesn't define a canonical form (Issue #233) (Saturday, 22 February)
• [w3c/clipboard-apis] [clipboard-apis] .write() for text/html doesn't define a canonical form (Issue #233) (Friday, 21 February)

Keith Cirkel

• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) (Friday, 21 February)
• Re: [whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361) (Wednesday, 19 February)
• Re: [whatwg/dom] 9021345194 (Issue #1357) (Sunday, 9 February)
• Re: [whatwg/dom] 7040724019 (Issue #1356) (Sunday, 9 February)
• Re: [whatwg/dom] https://t.me/elon_reeve_musk_tesla_spx (Issue #1355) (Sunday, 9 February)

kkmuffme

• [whatwg/dom] getElementById should not return the first but no element if id exists multiple times (Issue #1361) (Wednesday, 19 February)

Kyra Seevers

• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) (Tuesday, 11 February)

Lea Verou

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 17 February)
• Re: [w3ctag/design-reviews] Custom Functions (@function) (Issue #1031) (Wednesday, 5 February)

lili2012

• Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203) (Friday, 14 February)

Luke (Zgroza) Klimek

• Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232) (Wednesday, 12 February)

Luke Warlow

• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 20 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 20 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 20 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 20 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 20 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 20 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 20 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 20 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 20 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Tuesday, 18 February)
• Re: [w3ctag/design-reviews] Invokers API (Issue #920) (Thursday, 13 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 6 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 6 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 6 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 6 February)

Maksim Sadym

• Re: [w3c/gamepad] Add a means to test the API (Issue #175) (Thursday, 20 February)

mangelozzi

• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Saturday, 15 February)
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Saturday, 15 February)
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 13 February)

Marcos Cáceres

• Re: [w3c/permissions] Proposed Testing Plan for Geolocation Permission (Issue #460) (Thursday, 20 February)
• [w3c/permissions] Proposed Testing Plan for Geolocation Permission (Issue #460) (Thursday, 20 February)
• Re: [w3c/permissions] Editorial: Prepare for CR (PR #457) (Thursday, 20 February)
• Re: [w3c/permissions] Editorial: Prepare for CR (PR #457) (Thursday, 20 February)
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) (Thursday, 20 February)
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) (Thursday, 20 February)
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) (Thursday, 20 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] chore(auto-publish.yml): enable VALIDATE_INPUT_MARKUP (PR #218) (Friday, 14 February)
• Re: [w3c/manifest] Define "web application" (Issue #1097) (Friday, 7 February)
• Re: [w3c/manifest] Editorial: Add installable web application definition (PR #1163) (Friday, 7 February)
• Re: [w3c/manifest] Editorial: Add installable web application definition (PR #1163) (Friday, 7 February)
• Re: [w3c/manifest] Add installable web application definition (PR #1163) (Friday, 7 February)
• Re: [w3c/manifest] Add installable web application definition (PR #1163) (Friday, 7 February)
• Re: [w3c/manifest] Add installable web application definition (PR #1163) (Friday, 7 February)
• Re: [w3c/manifest] Link incubations (PR #1153) (Thursday, 6 February)
• Re: [w3c/manifest] Add a manifest option for the declaration the "version" of the web application (Issue #1036) (Thursday, 6 February)
• Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) (Thursday, 6 February)
• Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) (Thursday, 6 February)
• Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) (Thursday, 6 February)
• Re: [w3c/manifest] Feature Request: Support video ( webm ) icons in manifest (Issue #1162) (Thursday, 6 February)
• Re: [w3c/manifest] Feature Request: Support video ( webm ) icons in manifest (Issue #1162) (Thursday, 6 February)

Mark S. Miller

• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) (Monday, 17 February)

Martin Thomson

• Re: [w3ctag/design-reviews] Invokers API (Issue #920) (Thursday, 20 February)
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) (Wednesday, 19 February)
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) (Wednesday, 19 February)
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) (Wednesday, 19 February)
• Re: [w3ctag/design-reviews] Signature-Based Integrity. (Issue #1041) (Tuesday, 18 February)
• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Wednesday, 12 February)
• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Tuesday, 11 February)
• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Tuesday, 11 February)
• Re: [w3ctag/design-reviews] Delegation-oriented FedCM (Issue #1039) (Tuesday, 11 February)
• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Thursday, 6 February)
• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Wednesday, 5 February)

Masayuki Nakano

• Re: [w3c/editing] Disable `formatBlock` for `contenteditable=plaintext-only` (Issue #478) (Friday, 14 February)
• Re: [w3c/uievents] Clarify `mousemove` event target if preceding `mouseout`, `mouseleave`, `mouseover` or `mouseenter` event listener removes the `mouseover` target (Issue #393) (Wednesday, 5 February)
• [w3c/uievents] Clarify `mousemove` event target if preceding `mouseout`, `mouseleave`, `mouseover` or `mouseenter` event listener removes the `mouseover` target (Issue #393) (Wednesday, 5 February)

Mason Freed

• [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) (Friday, 21 February)
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) (Friday, 14 February)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Friday, 14 February)

Matt

• Re: [whatwg/url] Support relative URLs (#531) (Saturday, 8 February)

Matt Menke

• Re: [whatwg/fetch] Should network state be keyed beyond the top-level site (#1035) (Friday, 14 February)

Matt Reynolds

• Re: [w3c/gamepad] Fold extensions.html into main spec (Issue #165) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 14 February)
• [w3c/gamepad] Interop 2025 investigation effort - Gamepad API testing (Issue #219) (Thursday, 13 February)

Matthew Tylee Atkinson

• Re: [w3ctag/design-reviews] Accessibility conformance Testing (ACT) Rules Format 1.1 (Issue #977) (Thursday, 6 February)

Mattias Buelens

• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) (Monday, 17 February)

Meghan Denny

• Re: [whatwg/webidl] Cypto-os (Issue #1473) (Friday, 21 February)
• Re: [whatwg/webidl] Intent to use Constants (Issue #1468) (Monday, 3 February)
• Re: [whatwg/webidl] Intent to use Constants (Issue #1467) (Monday, 3 February)
• Re: [whatwg/webidl] Leader (Issue #1466) (Saturday, 1 February)

Mike West

• Re: [w3ctag/design-reviews] Signature-Based Integrity. (Issue #1041) (Tuesday, 18 February)

Monica Chintala

• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Friday, 21 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Friday, 21 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Friday, 21 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Saturday, 15 February)
• [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Friday, 14 February)
• Re: [w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754) (Friday, 14 February)
• Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753) (Wednesday, 12 February)
• Re: [w3c/ServiceWorker] Allow the addRoutes() to be called during installing (PR #1744) (Monday, 3 February)

Mustaq Ahmed

• Re: [w3c/uievents] Converge with CSSOM-View (#24) (Tuesday, 11 February)

Navodya Divyanjali

• [whatwg/fetch] x content types added (PR #1810) (Wednesday, 19 February)

nestedloops1

• Re: [whatwg/fetch] Use tasks to manipulate streams (#1270) (Saturday, 15 February)

nickchomey

• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Saturday, 8 February)
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Friday, 7 February)
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Friday, 7 February)
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Friday, 7 February)

Noam Rosenthal

• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) (Wednesday, 19 February)
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) (Wednesday, 19 February)
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) (Wednesday, 19 February)
• Re: [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) (Wednesday, 19 February)
• Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270) (Saturday, 15 February)
• Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270) (Saturday, 15 February)

ODOGwU15yrs

• [whatwg/xhr] Xbox sign in (Issue #396) (Thursday, 13 February)

PaidParker22

• [whatwg/dom] 9021345194 (Issue #1357) (Sunday, 9 February)
• [whatwg/dom] 7040724019 (Issue #1356) (Sunday, 9 February)
• [whatwg/dom] https://t.me/elon_reeve_musk_tesla_spx (Issue #1355) (Sunday, 9 February)

peasantman1

• [whatwg/webidl] Intent to use Constants (Issue #1468) (Monday, 3 February)

perrelet

• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 13 February)
• Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Thursday, 13 February)

Peter Beverloo

• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) (Sunday, 9 February)

Petr Špaček

• Re: [whatwg/url] IDNA: avoid defining valid domain string in terms of the parser (#245) (Monday, 17 February)

Philip Jägenstedt

• Re: [whatwg/fullscreen] Deal with two fullscreen elements in top layer and one element being removed (#133) (Tuesday, 11 February)
• Re: [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217) (Tuesday, 11 February)
• Re: [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217) (Tuesday, 11 February)
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) (Tuesday, 11 February)
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) (Tuesday, 11 February)
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) (Tuesday, 11 February)
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) (Monday, 10 February)
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) (Monday, 10 February)
• Re: [whatwg/fullscreen] Meta: disambiguate "document" for Bikeshed (PR #244) (Monday, 10 February)
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) (Monday, 10 February)
• [whatwg/fullscreen] Meta: disambiguate "document" for Bikeshed (PR #244) (Monday, 10 February)
• Re: [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217) (Monday, 10 February)

Philippe Le Hegaret

• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)

pikaroofficial

• [whatwg/webidl] Intent to use Constants (Issue #1472) (Friday, 21 February)

Rakesh Goulikar

• Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232) (Monday, 17 February)

Rob Eisenberg

• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) (Friday, 21 February)

Robert Flack

• Re: [w3ctag/design-reviews] CSS Overflow Navigation Controls (Issue #1037) (Wednesday, 19 February)

roraja

• Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232) (Wednesday, 19 February)

rossipedia

• Re: [whatwg/fetch] Proposal: `Request.json` helper (Issue #1791) (Wednesday, 19 February)

Ryosuke Niwa

• [WICG/webcomponents] Sessions for March 26th W3C Breakout Day (Issue #1095) (Saturday, 15 February)

Saara Bilyour

• [whatwg/fetch] Added example for X-Content-Type-Options in Fetch Standard (PR #1809) (Wednesday, 12 February)

Sarven Capadisli

• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Wednesday, 12 February)

Sean Feng

• Re: [whatwg/dom] Add definition for composed selection range (PR #1342) (Wednesday, 19 February)
• Re: [w3c/selection-api] Change Selection to be associated with a composed live range (PR #345) (Wednesday, 19 February)

Shunya Shishido

• Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753) (Wednesday, 12 February)
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Monday, 10 February)
• Re: [w3c/ServiceWorker] Editorial: Add notice on the _or condition depth. (PR #1714) (Monday, 10 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Thursday, 6 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Wednesday, 5 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Wednesday, 5 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Tuesday, 4 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Tuesday, 4 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Tuesday, 4 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Monday, 3 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Monday, 3 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Monday, 3 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Monday, 3 February)

sideshowbarker

• Re: [whatwg/streams] Review Draft Publication: February 2025 (PR #1340) (Monday, 17 February)

Simon Pieters

• Re: [w3ctag/design-reviews] (brand new ✨) Web Install API (Issue #1051) (Friday, 21 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 12 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a note (Issue #479) (Wednesday, 12 February)

Simon Wülker

• Re: [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352) (Monday, 10 February)
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) (Saturday, 1 February)
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) (Saturday, 1 February)
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) (Saturday, 1 February)
• [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352) (Saturday, 1 February)

smaug----

• Re: [whatwg/dom] Add definition for composed selection range (PR #1342) (Wednesday, 19 February)
• Re: [whatwg/dom] Update an attribute's node document (PR #1360) (Wednesday, 19 February)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Tuesday, 18 February)
• Re: [WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072) (Friday, 14 February)
• Re: [w3c/pointerlock] Unclear if `pointermove` should set `movementX/Y` (Issue #100) (Wednesday, 12 February)
• [whatwg/dom] setNamedItem doesn't adopt the attr node to the ownerDocument of the relevant element (Issue #1359) (Tuesday, 11 February)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Wednesday, 5 February)

Stephen Crane

• Re: [w3c/ServiceWorker] Responding to cross-origin requests using a worker? (#130) (Wednesday, 5 February)

Stephen McGruer

• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Wednesday, 19 February)

Steve Orvell

• Re: [WICG/webcomponents] [exportparts] support exporting via wildcards `exportparts="*, primary-*"` (Issue #1051) (Friday, 7 February)

Steven Becker

• Re: [w3c/IndexedDB] Editorial: Use newfangled bikeshed issue links (PR #439) (Friday, 21 February)

tahiryousaf313

• [whatwg/webidl] Intent to use Constants (Issue #1467) (Monday, 3 February)

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) (Tuesday, 18 February)
• 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) (Monday, 17 February)
• 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) (Monday, 17 February)

Thayne McCombs

• Re: [whatwg/url] Support relative URLs (#531) (Saturday, 8 February)

Tim Nguyen

• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) (Monday, 10 February)
• Re: [whatwg/fullscreen] How should UAs hide root element scrollbars? (Issue #236) (Monday, 10 February)
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) (Monday, 10 February)
• Re: [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) (Monday, 10 February)
• [whatwg/fullscreen] Fix dangling fullscreen flag when exiting a disconnected element (PR #243) (Tuesday, 4 February)

tophf

• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Saturday, 8 February)
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Friday, 7 February)

Valery Zinchenko

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Saturday, 22 February)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 6 February)

Westbrook Johnson

• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Friday, 14 February)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Friday, 14 February)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Friday, 14 February)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Friday, 14 February)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Friday, 7 February)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Friday, 7 February)

Xiaocheng Hu

• [w3ctag/design-reviews] CSS Stylable Columns (Issue #1056) (Thursday, 20 February)
• [w3ctag/design-reviews] CSS inert (Issue #1055) (Thursday, 20 February)
• [w3ctag/design-reviews] CSS Scroll Buttons (Issue #1054) (Thursday, 20 February)
• [w3ctag/design-reviews] CSS Scroll Markers (Issue #1053) (Thursday, 20 February)
• Re: [w3ctag/design-reviews] CSS Overflow Navigation Controls (Issue #1037) (Wednesday, 19 February)
• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) (Wednesday, 19 February)
• Re: [w3ctag/design-reviews] CSS `dynamic-range-limit` (Issue #1027) (Wednesday, 19 February)
• Re: [w3ctag/design-reviews] CSS Gap Decorations (Issue #1035) (Thursday, 13 February)
• Re: [w3ctag/design-reviews] CSS Gap Decorations (Issue #1035) (Thursday, 13 February)
• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) (Thursday, 13 February)
• Re: [w3ctag/design-reviews] safe-area-max-inset-* variables (Issue #1046) (Wednesday, 12 February)
• Re: [w3ctag/design-reviews] safe-area-max-inset-* variables (Issue #1046) (Wednesday, 12 February)
• Re: [w3ctag/design-reviews] CSS if() function (Issue #1045) (Wednesday, 12 February)
• Re: [w3ctag/design-reviews] CSS.highlights.highlightsFromPoint API (Issue #1043) (Wednesday, 12 February)

Xiaoqian Wu

• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)
• Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480) (Wednesday, 19 February)

Yoav Weiss

• [w3ctag/design-reviews] `require-sri-for` CSP directive (Issue #1048) (Thursday, 6 February)

Yoshisato Yanagisawa

• 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) (Tuesday, 18 February)
• Re: [w3c/ServiceWorker] Editorial: "mutual exclusive" (Issue #1716) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: "mutual exclusive" (Issue #1716) (Monday, 17 February)
• 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) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 17 February)
• Re: [w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754) (Sunday, 16 February)
• Re: [w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754) (Friday, 14 February)
• [w3c/ServiceWorker] Editorial: fix typo around "mutual exclusive" (PR #1754) (Friday, 14 February)
• Re: [w3c/ServiceWorker] No examples around addRoutes() API (Issue #1717) (Friday, 14 February)
• Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753) (Thursday, 13 February)
• Re: [w3c/ServiceWorker] Fixing some spec linking issues (PR #1640) (Wednesday, 12 February)
• Re: [w3c/ServiceWorker] Fixing some spec linking issues (PR #1640) (Wednesday, 12 February)
• Re: [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753) (Wednesday, 12 February)
• [w3c/ServiceWorker] Editorial: Fix bikeshed warning (PR #1753) (Wednesday, 12 February)
• Re: [w3c/ServiceWorker] serviceworker for iframes with srcdoc (#765) (Wednesday, 12 February)
• Re: [w3c/ServiceWorker] serviceworker for iframes with srcdoc (#765) (Wednesday, 12 February)
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Monday, 10 February)
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Monday, 10 February)
• Re: [w3c/ServiceWorker] Editorial: Add notice on the _or condition depth. (PR #1714) (Monday, 10 February)
• Re: [w3c/ServiceWorker] Editorial: Add notice on the _or condition depth. (PR #1714) (Monday, 10 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Monday, 10 February)
• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Friday, 7 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Thursday, 6 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Thursday, 6 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Thursday, 6 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Thursday, 6 February)
• Re: [w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690) (Wednesday, 5 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Wednesday, 5 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Wednesday, 5 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Wednesday, 5 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Wednesday, 5 February)
• Re: [w3c/ServiceWorker] InstallEvent.addRoutes is resolving/rejecting the returned promise synchronously (Issue #1742) (Tuesday, 4 February)
• Re: [w3c/ServiceWorker] Should InstallEvent.addRoutes reject if the the install event is not active? (Issue #1743) (Tuesday, 4 February)
• Re: [w3c/ServiceWorker] Should InstallEvent.addRoutes reject if the the install event is not active? (Issue #1743) (Tuesday, 4 February)
• Re: [w3c/ServiceWorker] Allow the addRoutes() to be called during installing (PR #1744) (Tuesday, 4 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Monday, 3 February)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Monday, 3 February)

Yves Lafon

• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) (Wednesday, 12 February)
• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) (Wednesday, 12 February)

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