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

Aaron Gustafson

• Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) (Thursday, 30 January)
• Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) (Thursday, 30 January)
• Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) (Tuesday, 7 January)

Aaron Selya

• [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) (Monday, 27 January)

aboallayl

• Re: [whatwg/fetch] Editorial: parsing application/x-www-form-urlencoded never fails (5dfed9d) (Thursday, 16 January)
• [whatwg/fetch] Herr (Issue #1801) (Thursday, 16 January)
• Re: [whatwg/fetch] Editorial: parsing application/x-www-form-urlencoded never fails (5dfed9d) (Thursday, 16 January)
• Re: [whatwg/fetch] Editorial: parsing application/x-www-form-urlencoded never fails (5dfed9d) (Thursday, 16 January)
• Re: [whatwg/fetch] Editorial: parsing application/x-www-form-urlencoded never fails (5dfed9d) (Thursday, 16 January)
• Re: [whatwg/fetch] Editorial: parsing application/x-www-form-urlencoded never fails (5dfed9d) (Thursday, 16 January)
• Re: [whatwg/fetch] Editorial: parsing application/x-www-form-urlencoded never fails (5dfed9d) (Thursday, 16 January)

Adam Rice

• Re: [whatwg/streams] Add WritableStream#write convenience method (PR #1339) (Wednesday, 29 January)

Addison Phillips

• [w3ctag/design-reviews] Unicode MessageFormat 2.0 (Issue #1042) (Tuesday, 21 January)

Alice

• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Thursday, 30 January)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Thursday, 30 January)
• Re: [WICG/webcomponents] Reference Target: How should we treat invalid reference targets for relations set via Element IDL attributes? (Issue #1089) (Wednesday, 29 January)
• [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Wednesday, 29 January)
• Re: [whatwg/fullscreen] Clarification for Accessibility requested (#197) (Tuesday, 21 January)
• Re: [WICG/webcomponents] Reference Target: Which attributes are in scope? (Issue #1091) (Tuesday, 21 January)
• Re: [WICG/webcomponents] Reference Target: How should we treat invalid reference targets for relations set via Element IDL attributes? (Issue #1089) (Tuesday, 21 January)
• Re: [WICG/webcomponents] Reference Target: How to handle invalid ID references? (Issue #1071) (Tuesday, 7 January)
• Re: [WICG/webcomponents] Reference Target naming (Issue #1087) (Wednesday, 1 January)

Andrea Giammarchi

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Thursday, 16 January)

Andrew Sutherland

• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Thursday, 23 January)
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Wednesday, 22 January)

Andrew Williams

• Re: [w3c/FileAPI] Blob URL store partitioning (#153) (Thursday, 9 January)

andruud

• Re: [w3ctag/design-reviews] Custom Functions (@function) (Issue #1031) (Tuesday, 14 January)
• Re: [w3ctag/design-reviews] Custom Functions (@function) (Issue #1031) (Friday, 3 January)

Andy Luhrs

• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) (Friday, 17 January)
• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Friday, 17 January)

Anne van Kesteren

• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Friday, 31 January)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Friday, 31 January)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Friday, 31 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Saturday, 25 January)
• Re: [whatwg/webidl] Meta: address Bikeshed errors (PR #1464) (Friday, 24 January)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Friday, 24 January)
• Re: [whatwg/webidl] Meta: address Bikeshed errors (PR #1464) (Friday, 24 January)
• Re: [whatwg/webidl] Meta: address Bikeshed errors (PR #1464) (Friday, 24 January)
• [whatwg/webidl] Meta: address Bikeshed errors (PR #1464) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream#write convenience method (PR #1339) (Friday, 24 January)
• Re: [whatwg/streams] Use `async iterable` webidl type in ReadableStream.from (PR #1310) (Friday, 24 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Friday, 24 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Friday, 24 January)
• [whatwg/dom] Define maximum length and handling of CharacterData nodes (Issue #1351) (Friday, 24 January)
• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Thursday, 23 January)
• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Thursday, 23 January)
• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Thursday, 23 January)
• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Thursday, 23 January)
• Re: [whatwg/xhr] Allow doubles for ProgressEvent's loaded and total (PR #394) (Wednesday, 22 January)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Tuesday, 21 January)
• Re: [whatwg/fetch] Fetch (Issue #1805) (Tuesday, 21 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Tuesday, 21 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Tuesday, 21 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Tuesday, 21 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Tuesday, 21 January)
• Re: [whatwg/streams] Editorial: fix markup errors (PR #1338) (Tuesday, 21 January)
• Re: [whatwg/fetch] [Editorial] Fix build issues from recent updates to bikeshed (PR #1804) (Tuesday, 21 January)
• Re: [whatwg/fetch] [Editorial] Fix build issues from recent updates to bikeshed (PR #1804) (Tuesday, 21 January)
• Re: [whatwg/fetch] [Editorial] Fix build issues from recent updates to bikeshed (PR #1804) (Tuesday, 21 January)
• Re: [whatwg/xhr] Allow doubles for ProgressEvent's loaded and total (PR #394) (Tuesday, 21 January)
• Re: [whatwg/xhr] Editorial: fix Bikeshed linking errors (PR #395) (Tuesday, 21 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Monday, 20 January)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Monday, 20 January)
• Re: [whatwg/dom] Editorial: modernize the slot algorithms (PR #1350) (Monday, 20 January)
• Re: [whatwg/dom] Redundant step in `find slottables` (Issue #1349) (Monday, 20 January)
• Re: [whatwg/dom] Redundant step in `find slottables` (Issue #1349) (Monday, 20 January)
• Re: [whatwg/dom] Editorial: modernize the slot algorithms (PR #1350) (Monday, 20 January)
• [whatwg/dom] Editorial: modernize the slot algorithms (PR #1350) (Monday, 20 January)
• Re: [whatwg/dom] Redundant step in `find slottables` (Issue #1349) (Monday, 20 January)
• Re: [w3c/push-api] `SecureContext` attribute is redundant for interfaces with `Exposed=ServiceWorker` (Issue #397) (Monday, 20 January)
• Re: [whatwg/dom] Shadow DOM style ordering and cascade penetration (Issue #1348) (Monday, 20 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Friday, 17 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Friday, 17 January)
• Re: [whatwg/fetch] blob() method: define behavior when get the MIME type return null (Issue #1802) (Friday, 17 January)
• Re: [whatwg/fetch] 0x00 byte (%00) in a data: URL (Issue #1748) (Friday, 17 January)
• Re: [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788) (Thursday, 16 January)
• Re: [whatwg/dom] Event::dispatch uses possibly uninitialized `clearTargets` (Issue #1344) (Wednesday, 15 January)
• Re: [whatwg/dom] Event::dispatch uses possibly uninitialized `clearTargets` (Issue #1344) (Wednesday, 15 January)
• Re: [whatwg/dom] Editorial: initialize clearTargets in event dispatch correctly (PR #1347) (Wednesday, 15 January)
• Re: [whatwg/dom] Editorial: initialize clearTargets in event dispatch correctly (PR #1347) (Wednesday, 15 January)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 14 January)
• Re: [whatwg/fetch] Proposal: response.base64() (Issue #1800) (Thursday, 9 January)
• Re: [whatwg/fetch] Proposal: response.base64() (Issue #1800) (Thursday, 9 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 7 January)
• Re: [whatwg/webidl] Accept `iterable` and `async iterable` in functions? (Issue #1461) (Tuesday, 7 January)
• Re: [whatwg/webidl] Accept `iterable` and `async iterable` in functions? (Issue #1461) (Monday, 6 January)
• Re: [whatwg/fetch] If a resource allows credentials but omits Vary, shouldn't responses to non-CORS requests also contain Access-Control-Allow-Credentials? (Issue #1601) (Monday, 6 January)
• Re: [whatwg/dom] Event::ComposedPath doesn't handle `this.currentTarget == null` (Issue #1343) (Monday, 6 January)
• [whatwg/dom] Editorial: initialize clearTargets in event dispatch correctly (PR #1347) (Monday, 6 January)
• Re: [whatwg/dom] Event::dispatch uses possibly uninitialized `clearTargets` (Issue #1344) (Monday, 6 January)
• Re: [whatwg/dom] [EventTarget] Abort controller from a past subscription can remove events from future subscriptions (Issue #1346) (Monday, 6 January)
• Re: [whatwg/url] URLSearchParams with repeated parameters (Issue #851) (Thursday, 2 January)
• Re: [whatwg/url] URLSearchParams with repeated parameters (Issue #851) (Thursday, 2 January)

Anssi Kostiainen

• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Wednesday, 15 January)

Ari Chivukula

• Re: [w3ctag/design-reviews] Early Design Review: Partitioned Popins (Issue #956) (Friday, 10 January)

Audun Meek Olsen

• Re: [whatwg/fetch] Proposal: Easier request/response rewrites (#671) (Monday, 27 January)

Ben Francis

• Re: [w3c/manifest] Prevent Screenshots in PWAs (Issue #1154) (Monday, 6 January)
• Re: [w3c/manifest] Prevent Screenshots in PWAs (Issue #1154) (Monday, 6 January)

Bill Collins

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 14 January)

Bradley Needham

• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 10 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Thursday, 9 January)

Brian Kardell

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

bvandersloot-mozilla

• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00++) (PR #1807) (Thursday, 30 January)
• [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00++) (PR #1807) (Thursday, 30 January)
• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Friday, 24 January)
• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Friday, 24 January)

Chris Lilley

• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Monday, 13 January)

Christian Indra

• Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Tuesday, 28 January)

Christian Liebel

• Re: [w3c/manifest] Softslink PWA Mobile App (Issue #1161) (Friday, 31 January)
• Re: [w3c/manifest] Preparing for Candidate Recommendation (#865) (Thursday, 30 January)
• Re: [w3c/manifest] Preparing for Candidate Recommendation (#865) (Thursday, 30 January)
• Re: [w3c/manifest] Create web3 (PR #1158) (Tuesday, 28 January)
• Re: [w3c/manifest] Modified (PR #1159) (Tuesday, 28 January)
• Re: [w3c/manifest] Create web3 (PR #1160) (Tuesday, 28 January)
• Re: [w3c/push-api] Http new (Issue #398) (Tuesday, 28 January)
• Re: [w3c/manifest] Prevent Screenshots in PWAs (Issue #1154) (Tuesday, 7 January)
• Re: [w3c/manifest] Prevent Screenshots in PWAs (Issue #1154) (Tuesday, 7 January)
• Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) (Tuesday, 7 January)
• Re: [w3c/manifest] Mainfiest (Issue #1155) (Saturday, 4 January)
• Re: [w3c/manifest] w3c1 (Issue #1156) (Saturday, 4 January)
• Re: [w3c/push-api] Update README.md (PR #395) (Wednesday, 1 January)

Christopher Cameron

• [w3ctag/design-reviews] [HTML] Fix divergence of CanvasRenderingContext2D and Offscreen with CanvasSettings (Issue #1036) (Wednesday, 8 January)

Claudia Meadows

• Re: [whatwg/dom] Shadow DOM style ordering and cascade penetration (Issue #1348) (Monday, 20 January)
• Re: [whatwg/dom] Shadow DOM style ordering and cascade penetration (Issue #1348) (Monday, 20 January)
• [whatwg/dom] Transparent mode for shadow DOM (Issue #1348) (Saturday, 18 January)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Thursday, 16 January)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Thursday, 16 January)

codecodecodephone

• [w3c/manifest] Create web3 (PR #1160) (Tuesday, 28 January)
• [w3c/manifest] Modified (PR #1159) (Tuesday, 28 January)
• [w3c/manifest] Create web3 (PR #1158) (Tuesday, 28 January)

crystalthoughts

• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Wednesday, 22 January)

cynthia

• Re: [w3ctag/design-reviews] Add a link to the early design review in the specification review request (PR #1032) (Tuesday, 14 January)

Dan Clark

• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Thursday, 30 January)
• Re: [WICG/webcomponents] Reference Target: How to handle invalid ID references? (Issue #1071) (Thursday, 30 January)
• Re: [WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072) (Wednesday, 29 January)
• Re: [WICG/webcomponents] Reference Target: How should we treat invalid reference targets for relations set via Element IDL attributes? (Issue #1089) (Wednesday, 22 January)
• Re: [WICG/webcomponents] Reference Target: How should we treat invalid reference targets for relations set via Element IDL attributes? (Issue #1089) (Thursday, 16 January)
• Re: [WICG/webcomponents] Reference Target: Which attributes are in scope? (Issue #1091) (Wednesday, 15 January)
• Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232) (Saturday, 11 January)

Daniel Appelquist

• Re: [w3ctag/design-reviews] FYI - Web Authentication API: PublicKeyCredential’s getClientCapabilities() method (Issue #1016) (Monday, 27 January)
• Re: [w3ctag/design-reviews] FYI - Web Authentication API: PublicKeyCredential’s getClientCapabilities() method (Issue #1016) (Monday, 27 January)
• Re: [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014) (Monday, 27 January)
• Re: [w3ctag/design-reviews] ClipboardChange event API (Issue #1017) (Monday, 27 January)
• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Wednesday, 8 January)
• Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838) (Monday, 6 January)

Daniel Huigens

• Re: [whatwg/webidl] Accept `iterable` and `async iterable` in functions? (Issue #1461) (Tuesday, 7 January)
• Re: [whatwg/webidl] Accept `iterable` and `async iterable` in functions? (Issue #1461) (Tuesday, 7 January)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Monday, 6 January)
• Re: [whatwg/webidl] Accept `iterable` and `async iterable` in functions? (Issue #1461) (Monday, 6 January)
• [whatwg/webidl] Accept `iterable` and `async iterable` in functions? (Issue #1461) (Monday, 6 January)

Daniel Murphy

• Re: [w3c/manifest] Link incubations (PR #1153) (Friday, 31 January)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Friday, 31 January)

Daniel Soto

• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Wednesday, 8 January)

Di Zhang

• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 28 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 28 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 28 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 28 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Monday, 27 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Friday, 24 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Friday, 24 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Friday, 24 January)
• Re: [w3c/selection-api] Change Selection to be associated with a composed live range (PR #345) (Friday, 24 January)
• [w3c/selection-api] Change Selection to be associated with a composed live range (PR #345) (Friday, 24 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Thursday, 23 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 21 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 21 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 21 January)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Wednesday, 15 January)

Diego Gonzalez

• Re: [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) (Thursday, 30 January)

DM

• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Tuesday, 21 January)

Domenic Denicola

• Re: [whatwg/webidl] Bikeshedding help needed for generic over-limit error (Issue #1463) (Monday, 27 January)
• [whatwg/webidl] Upgrade QuotaExceededError to a DOMException derived interface (PR #1465) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690) (Monday, 27 January)
• Re: [whatwg/streams] Add WritableStream#write convenience method (PR #1339) (Monday, 27 January)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Saturday, 25 January)
• Re: [w3c/ServiceWorker] Update usages of module fetching html algorithms (PR #1658) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Check requestMethod (PR #1748) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [whatwg/webidl] Bikeshedding help needed for generic over-limit error (Issue #1463) (Friday, 24 January)
• Re: [whatwg/webidl] Bikeshedding help needed for generic over-limit error (Issue #1463) (Friday, 24 January)
• Re: [whatwg/webidl] Bikeshedding help needed for generic over-limit error (Issue #1463) (Friday, 24 January)
• [whatwg/webidl] Bikeshedding help needed for generic over-limit error (Issue #1463) (Friday, 24 January)
• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Friday, 24 January)
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Thursday, 23 January)
• Re: [whatwg/xhr] Allow doubles for ProgressEvent's loaded and total (PR #394) (Thursday, 23 January)
• Re: [whatwg/xhr] Allow doubles for ProgressEvent's loaded and total (PR #394) (Wednesday, 22 January)
• Re: [whatwg/streams] Fix `[[ViewedArrayBuffer]].[[ByteLength]]` name in ReadableStreamBYOBRequest doc (PR #1337) (Wednesday, 22 January)
• Re: [whatwg/streams] Fix `[[ViewedArrayBuffer]].[[ByteLength]]` name in ReadableStreamBYOBRequest doc (PR #1337) (Wednesday, 22 January)
• Re: [whatwg/streams] Editorial: fix markup errors (PR #1338) (Wednesday, 22 January)
• [whatwg/xhr] Editorial: fix Bikeshed linking errors (PR #395) (Tuesday, 21 January)
• [whatwg/xhr] Allow doubles for ProgressEvent's loaded and total (PR #394) (Tuesday, 21 January)
• Re: [whatwg/streams] Fix `[[ViewedArrayBuffer]].[[ByteLength]]` name in ReadableStreamBYOBRequest doc (PR #1337) (Tuesday, 21 January)
• [whatwg/streams] Editorial: fix markup errors (PR #1338) (Tuesday, 21 January)
• Re: [whatwg/streams] Fix `[[ViewedArrayBuffer]].[[ByteLength]]` name in ReadableStreamBYOBRequest doc (PR #1337) (Tuesday, 21 January)
• Re: [whatwg/dom] Editorial: initialize clearTargets in event dispatch correctly (PR #1347) (Wednesday, 15 January)
• Re: [whatwg/dom] Editorial: initialize clearTargets in event dispatch correctly (PR #1347) (Wednesday, 15 January)
• Re: [whatwg/webidl] Accept `iterable` and `async iterable` in functions? (Issue #1461) (Tuesday, 7 January)

Dominic Farolino

• Re: [whatwg/dom] Add definition for composed selection range (PR #1342) (Thursday, 30 January)
• Re: [whatwg/fetch] Editorial: Add guidelines for external specs about CORS, cross-origin isolation and TAO (PR #1806) (Thursday, 30 January)
• Re: [whatwg/fetch] Editorial: Add guidelines for external specs about CORS, cross-origin isolation and TAO (PR #1806) (Thursday, 30 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 28 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 28 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 28 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 28 January)
• Re: [w3c/selection-api] Change Selection to be associated with a composed live range (PR #345) (Tuesday, 28 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 28 January)
• Re: [whatwg/dom] Add definition for composed live range (PR #1342) (Tuesday, 28 January)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Saturday, 25 January)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Saturday, 25 January)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Saturday, 25 January)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Saturday, 18 January)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 14 January)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 14 January)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 14 January)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 14 January)

dontcallmedom-bot

• [w3c/ServiceWorker] Missing tasks in parallel steps in Service Workers Nightly (Issue #1740) (Tuesday, 7 January)
• [w3c/screen-orientation] Missing tasks in parallel steps in Screen Orientation (Issue #253) (Tuesday, 7 January)

Edgar Chen

• Re: [w3c/screen-orientation] Should the fullscreen pre-lock condition also check for fullscreen state of parent document? (Issue #255) (Friday, 10 January)
• [w3c/screen-orientation] Should the fullscreen pre-lock condition also check for fullscreen state of parent document? (Issue #255) (Friday, 10 January)
• [w3c/screen-orientation] Should the fullscreen pre-lock condition also check for a pending fullscreen request? (Issue #254) (Friday, 10 January)

Espen Hovlandsdal

• Re: [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788) (Wednesday, 15 January)
• Re: [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788) (Wednesday, 15 January)

Evan Liu

• [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Thursday, 9 January)

Evan Stade

• [w3c/IndexedDB] Remove "otherwise" language after throwing in algorithms. (PR #438) (Friday, 10 January)
• Re: [w3c/IndexedDB] Can a "committing" transaction be aborted? (Issue #437) (Friday, 10 January)
• Re: [w3c/IndexedDB] Can a "committing" transaction be aborted? (Issue #437) (Friday, 10 January)
• [w3c/IndexedDB] Can a "committing" transaction be aborted? (Issue #437) (Thursday, 9 January)

Felix

• Re: [w3c/selection-api] Having a matching `selectend` event? (#146) (Saturday, 11 January)

Feng Yu

• [whatwg/fetch] blob() method: define behavior when get the MIME type return null (Issue #1802) (Friday, 17 January)

Fernando Fiori

• [w3ctag/design-reviews] highlightsFromPoint API (Issue #1043) (Wednesday, 22 January)

fort

• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) (Wednesday, 22 January)
• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) (Wednesday, 22 January)

frybox

• Re: [w3c/ServiceWorker] Support modifying cookies on an intercepted fetch (#837) (Monday, 20 January)
• Re: [w3c/ServiceWorker] Support modifying cookies on an intercepted fetch (#837) (Monday, 20 January)

Frédéric Wang

• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 30 January)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Wednesday, 29 January)

Gabriel Corona

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Monday, 20 January)

Gary Kacmarcik

• Re: [w3ctag/design-reviews] ClipboardChange event API (Issue #1017) (Wednesday, 15 January)
• Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52) (Wednesday, 15 January)

Guohui Deng

• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 29 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 29 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 23 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 23 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 23 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 23 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 23 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 21 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 21 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 14 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 14 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 14 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 14 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 14 January)

Hadley Beeman

• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Wednesday, 15 January)
• Re: [w3ctag/design-reviews] Final Review Request of seven (7) W3C VCWG Specifications (Issue #1029) (Wednesday, 8 January)

Hemanth HM

• Re: [whatwg/fetch] Proposal: response.base64() (Issue #1800) (Thursday, 9 January)
• Re: [whatwg/fetch] Proposal: response.base64() (Issue #1800) (Wednesday, 8 January)
• [whatwg/fetch] Proposal: response.base64() (Issue #1800) (Wednesday, 8 January)

hmd123pm

• [w3c/manifest] w3c1 (Issue #1156) (Saturday, 4 January)

Jack Duvall

• Re: [w3c/uievents] Need virtual key codes (Issue #377) (Friday, 17 January)

Jakub T. Jankiewicz

• Re: [w3c/ServiceWorker] Support modifying cookies on an intercepted fetch (#837) (Monday, 20 January)

James

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 22 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 22 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 22 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Tuesday, 21 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Tuesday, 21 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Monday, 20 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Sunday, 19 January)

James M Snell

• Re: [whatwg/streams] Add WritableStream#write convenience method (PR #1339) (Friday, 24 January)
• Re: [whatwg/webidl] Bikeshedding help needed for generic over-limit error (Issue #1463) (Friday, 24 January)
• Re: [whatwg/webidl] Bikeshedding help needed for generic over-limit error (Issue #1463) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Thursday, 23 January)

janvarga

• Re: [whatwg/streams] Add WritableStream#write convenience method (PR #1339) (Friday, 24 January)

Jeffrey Yasskin

• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• [w3ctag/design-reviews] Encourage feature owners to list all relevant standards groups. (PR #1044) (Friday, 24 January)
• Re: [w3ctag/design-reviews] Observable API (Issue #902) (Tuesday, 21 January)
• Re: [w3ctag/design-reviews] Observable API (Issue #902) (Tuesday, 21 January)
• Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886) (Tuesday, 21 January)
• Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886) (Tuesday, 21 January)
• Re: [w3ctag/design-reviews] CSS calc-size() function (Issue #955) (Tuesday, 21 January)
• Re: [w3ctag/design-reviews] CSS calc-size() function (Issue #955) (Tuesday, 21 January)
• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Saturday, 18 January)
• Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Thursday, 16 January)
• Re: [w3ctag/design-reviews] Add a link to the early design review in the specification review request (PR #1032) (Tuesday, 14 January)
• Re: [w3ctag/design-reviews] Early Design Review: Partitioned Popins (Issue #956) (Monday, 13 January)
• Re: [w3ctag/design-reviews] Early Design Review: Partitioned Popins (Issue #956) (Monday, 13 January)
• Re: [w3ctag/design-reviews] ClipboardChange event API (Issue #1017) (Monday, 13 January)
• Re: [w3ctag/design-reviews] ClipboardChange event API (Issue #1017) (Wednesday, 8 January)
• Re: [w3ctag/design-reviews] CSS advanced attr() function (#513) (Tuesday, 7 January)
• Re: [w3ctag/design-reviews] CSS advanced attr() function (#513) (Tuesday, 7 January)

Jelle Raaijmakers

• [w3c/editing] Disable `formatBlock` for `contenteditable=plaintext-only` (Issue #478) (Friday, 24 January)
• [w3c/editing] Recursively executing `execCommand()` should be prevented (Issue #477) (Thursday, 23 January)
• [w3c/editing] Invalid or identical colors provided to `backColor`/`foreColor`/`hiliteColor` should return `true` instead of `false` (Issue #476) (Thursday, 23 January)
• [w3c/editing] `selectAll` command should be disabled if no selection exists on the context object (Issue #475) (Monday, 20 January)
• [w3c/editing] Indeterminate state for formatBlock mentions "return the empty string" (Issue #474) (Thursday, 9 January)

Jeremy Impson

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 22 January)

jjjalkanen

• Re: [whatwg/streams] Add WritableStream#write convenience method (PR #1339) (Monday, 27 January)

Jonas Konrad

• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Thursday, 23 January)
• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Thursday, 23 January)
• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Thursday, 23 January)
• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Thursday, 23 January)
• Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Thursday, 23 January)
• [whatwg/url] Confusion about pipe characters in paths (Issue #852) (Thursday, 23 January)

Jordan Harband

• Re: [whatwg/fetch] Proposal: response.base64() (Issue #1800) (Thursday, 9 January)
• Re: [whatwg/fetch] Proposal: response.base64() (Issue #1800) (Thursday, 9 January)
• Re: [whatwg/fetch] Proposal: response.base64() (Issue #1800) (Wednesday, 8 January)
• Re: [whatwg/fetch] Proposal: response.base64() (Issue #1800) (Wednesday, 8 January)

Josh Karlin

• Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Friday, 10 January)

Joshua Bell

• Re: [w3c/IndexedDB] Remove "otherwise" language after throwing in algorithms. (PR #438) (Friday, 10 January)
• Re: [w3c/IndexedDB] Remove "otherwise" language after throwing in algorithms. (PR #438) (Friday, 10 January)
• Re: [w3c/IndexedDB] Remove "otherwise" language after throwing in algorithms. (PR #438) (Friday, 10 January)
• Re: [w3c/IndexedDB] Can a "committing" transaction be aborted? (Issue #437) (Thursday, 9 January)
• Re: [w3c/IndexedDB] Wait loop questions (Issue #436) (Monday, 6 January)
• Re: [w3c/IndexedDB] Storage Keys are used directly, rather than a Storage Bottle Map (Issue #435) (Monday, 6 January)

jub0bs

• Re: [whatwg/fetch] If a resource allows credentials but omits Vary, shouldn't responses to non-CORS requests also contain Access-Control-Allow-Credentials? (Issue #1601) (Monday, 6 January)

Junhui He

• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Thursday, 23 January)
• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Friday, 17 January)
• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Saturday, 11 January)

Justin Fagnani

• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Friday, 17 January)

Kagami Sascha Rosylight

• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) (Friday, 31 January)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Friday, 31 January)
• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Friday, 31 January)
• Re: [whatwg/streams] Add WritableStream#write convenience method (PR #1339) (Monday, 27 January)
• [w3c/ServiceWorker] Require `[SecureContext]` for interfaces with `[Exposed=ServiceWorker]` or not? (Issue #1749) (Sunday, 26 January)
• Re: [whatwg/streams] Add WritableStream#write convenience method (PR #1339) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Thursday, 23 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Thursday, 23 January)
• [w3c/push-api] `SecureContext` attribute is redundant for interfaces with `Exposed=ServiceWorker` (Issue #397) (Friday, 17 January)
• [w3c/push-api] Add dictionary for the type of `PushSubscriptionJSON.keys`? (Issue #396) (Friday, 17 January)

Keith Cirkel

• Re: [WICG/webcomponents] [Proposal] Stylesheet Observer (Issue #1041) (Friday, 31 January)
• Re: [WICG/webcomponents] fix typo (PR #1092) (Tuesday, 28 January)
• Re: [WICG/webcomponents] fix typo (PR #1092) (Tuesday, 28 January)
• Re: [WICG/webcomponents] fix typo (PR #1092) (Tuesday, 28 January)
• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Wednesday, 8 January)
• [w3ctag/design-reviews] Container Timing API (Issue #1034) (Tuesday, 7 January)

Kevin Babbitt

• Re: [w3ctag/design-reviews] CSS Gap Decorations (Issue #1035) (Monday, 13 January)
• [w3ctag/design-reviews] CSS Gap Decorations (Issue #1035) (Tuesday, 7 January)

Kevin Gibbons

• Re: [whatwg/webidl] Bikeshedding help needed for generic over-limit error (Issue #1463) (Friday, 24 January)
• Re: [whatwg/webidl] Bikeshedding help needed for generic over-limit error (Issue #1463) (Friday, 24 January)
• Re: [whatwg/webidl] Bikeshedding help needed for generic over-limit error (Issue #1463) (Friday, 24 January)

kimolamoo

• [whatwg/url] Kimo.Fox onlyfans (Issue #853) (Friday, 31 January)

Lea Verou

• Re: [w3ctag/design-reviews] CSS if() function (Issue #1045) (Friday, 31 January)
• Re: [w3ctag/design-reviews] Custom Functions (@function) (Issue #1031) (Saturday, 11 January)
• Re: [w3ctag/design-reviews] CSS Gap Decorations (Issue #1035) (Saturday, 11 January)

Luca Casonato

• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Saturday, 25 January)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Saturday, 25 January)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Saturday, 25 January)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Friday, 24 January)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Friday, 24 January)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Friday, 24 January)
• Re: [whatwg/streams] Use `async iterable` webidl type in ReadableStream.from (PR #1310) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream#write convenience method (PR #1339) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Thursday, 23 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Thursday, 23 January)
• Re: [whatwg/streams] Should we add writableStream.write()? readableStream.read()? (#1072) (Thursday, 23 January)
• [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Thursday, 23 January)
• Re: [whatwg/streams] Use `async iterable` webidl type in ReadableStream.from (PR #1310) (Thursday, 23 January)

luis Allen

• Re: [w3ctag/design-reviews] How should web standards use the new JavaScript Symbol.dispose protocol? (Discussion #800) (Monday, 20 January)

Lukas Spirig

• Re: [WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072) (Friday, 24 January)

Lukasz Olejnik

• Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723) (Thursday, 9 January)

Luke (Zgroza) Klimek

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

Manu Sporny

• Re: [w3ctag/design-reviews] Final Review Request of seven (7) W3C VCWG Specifications (Issue #1029) (Wednesday, 8 January)

Marcos Cáceres

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

Marijn Kruisselbrink

• Re: [w3c/ServiceWorker] Update editors (PR #1750) (Monday, 27 January)
• Re: [w3c/FileAPI] Blob URL store partitioning (#153) (Thursday, 9 January)
• Re: [w3c/FileAPI] Blob URL store partitioning (#153) (Thursday, 9 January)

Masayuki Nakano

• Re: [w3c/uievents] Event order between "compositionend" and "input" (#202) (Thursday, 16 January)
• Re: [w3c/uievents] Event order between "compositionend" and "input" (#202) (Wednesday, 15 January)

Matt Giuca

• Re: [w3c/manifest] Prevent Screenshots in PWAs (Issue #1154) (Tuesday, 7 January)

Matthew Tylee Atkinson

• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Thursday, 23 January)
• Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013) (Wednesday, 15 January)
• Re: [w3ctag/design-reviews] User-defined script "entry points" for performance timing (Issue #1012) (Wednesday, 15 January)
• Re: [w3ctag/design-reviews] Early Design Review: Partitioned Popins (Issue #956) (Thursday, 9 January)
• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Thursday, 9 January)

Mattias Buelens

• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Friday, 24 January)
• Re: [whatwg/streams] Add WritableStream.write convenience method (PR #1339) (Friday, 24 January)
• Re: [whatwg/streams] Editorial: fix markup errors (PR #1338) (Tuesday, 21 January)
• Re: [whatwg/streams] Editorial: small cleanup after #1326 (PR #1336) (Saturday, 11 January)
• Re: [whatwg/streams] Editorial: small cleanup after #1326 (PR #1336) (Saturday, 11 January)

Meghan Denny

• Re: [whatwg/url] Kimo.Fox onlyfans (Issue #853) (Friday, 31 January)
• Re: [whatwg/fetch] Herr (Issue #1801) (Thursday, 16 January)
• Re: [whatwg/webidl] Intent to use bigint/numeric union (Issue #1462) (Thursday, 16 January)
• Re: [whatwg/fetch] Proposal: response.base64() (Issue #1800) (Wednesday, 8 January)

Merwan

• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) (Wednesday, 22 January)

Mike Taylor

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

Mike West

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

Mikey Stengel

• [w3c/manifest] Feature Request: Support version field in Web App Manifest to align with app store requirements (Issue #1157) (Monday, 6 January)

Ming-Ying Chung

• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 22 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Tuesday, 21 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Friday, 17 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 16 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 15 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Tuesday, 14 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Friday, 10 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Friday, 10 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Friday, 10 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Friday, 10 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)

MOHAMED EZZAT ABDALLA FAHMI

• Re: [whatwg/webidl] Bikeshedding help needed for generic over-limit error (Issue #1463) (Friday, 24 January)

Monica Chintala

• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Wednesday, 29 January)
• Re: [w3c/ServiceWorker] Editorial: Fix linking errors on [=document=] (PR #1751) (Wednesday, 29 January)
• Re: [w3c/ServiceWorker] Ensure "race-network-and-fetch-handler" is used with a fetch handler (PR #1719) (Tuesday, 28 January)

MrKleiner

• Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299) (Monday, 27 January)

Ms2ger

• Re: [whatwg/webidl] Meta: address Bikeshed errors (PR #1464) (Friday, 24 January)

Munira

• [w3ctag/design-reviews] CSS if() function (Issue #1045) (Tuesday, 28 January)

Nicolò Ribaudo

• Re: [w3c/ServiceWorker] Update usages of module fetching html algorithms (PR #1658) (Friday, 24 January)

Nidhi Jaju

• Re: [whatwg/streams] Add WritableStream#write convenience method (PR #1339) (Monday, 27 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Thursday, 23 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Wednesday, 22 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Tuesday, 21 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Tuesday, 21 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Tuesday, 21 January)
• Re: [whatwg/fetch] [Editorial] Fix build issues from recent updates to bikeshed (PR #1804) (Tuesday, 21 January)
• [whatwg/fetch] [Editorial] Fix build issues from recent updates to bikeshed (PR #1804) (Tuesday, 21 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Tuesday, 21 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Friday, 17 January)
• [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Friday, 17 January)

nin-jin

• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Thursday, 2 January)

Noam Rosenthal

• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 30 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 29 January)
• Re: [whatwg/fetch] Editorial: Add guidelines for external specs about CORS, cross-origin isolation and TAO (PR #1806) (Wednesday, 29 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Wednesday, 29 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Wednesday, 29 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 23 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Thursday, 23 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Thursday, 23 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Wednesday, 22 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 22 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 22 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Wednesday, 22 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 21 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Tuesday, 21 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Tuesday, 21 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Tuesday, 21 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Monday, 20 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 20 January)
• [w3ctag/design-reviews] Navigation API deferred commit (Issue #1040) (Thursday, 16 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 16 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 16 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 16 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 15 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Tuesday, 14 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 13 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 13 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 13 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 13 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 13 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Wednesday, 8 January)
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) (Tuesday, 7 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Tuesday, 7 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Tuesday, 7 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Tuesday, 7 January)
• [w3ctag/design-reviews] CSS `shape()` function (Issue #1033) (Monday, 6 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 6 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 6 January)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 2 January)

Nolan Lawson

• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Saturday, 18 January)

Olivier Tassinari

• Re: [w3c/uievents] Need virtual key codes (Issue #377) (Friday, 17 January)

PandaPlayz2373

• [whatwg/fetch] Fetch (Issue #1805) (Tuesday, 21 January)

Paul Draper

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Friday, 17 January)

Peter H. Jin

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 22 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 22 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 22 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 22 January)

Peter Linss

• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Monday, 13 January)
• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Monday, 13 January)
• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Tuesday, 7 January)

Rakesh Goulikar

• Re: [w3ctag/design-reviews] ClipboardChange event API (Issue #1017) (Monday, 13 January)

Rick Byers

• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) (Wednesday, 22 January)

Robert Flack

• [w3ctag/design-reviews] CSS Overflow Navigation Controls (Issue #1037) (Thursday, 9 January)

Robin Salkeld

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Tuesday, 21 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Tuesday, 21 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Monday, 20 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Saturday, 18 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Saturday, 18 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Friday, 17 January)

Rouslan Solomakhin

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

Rubén Norte

• Re: [whatwg/dom] [EventTarget] Abort controller from a past subscription can remove events from future subscriptions (Issue #1346) (Monday, 6 January)

Ryosuke Niwa

• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Friday, 31 January)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Tuesday, 7 January)
• Re: [w3c/selection-api] Tidied up document using tidy-html5 (PR #340) (Sunday, 5 January)

Sam Goto

• [w3ctag/design-reviews] Delegation-oriented FedCM (Issue #1039) (Thursday, 16 January)

Sam Morris

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 22 January)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Tuesday, 21 January)

samsulkj1

• [w3c/push-api] Http new (Issue #398) (Tuesday, 28 January)

schwering

• Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Thursday, 16 January)
• Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Thursday, 16 January)

Shannon Booth

• [w3c/FileAPI] revokeObjectURL does not error check URL parsing and passes string to "remove an entry" (Issue #207) (Sunday, 19 January)

Shiba

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Wednesday, 29 January)

Shikho18

• Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299) (Tuesday, 28 January)
• Re: [whatwg/fetch] Editorial: Add prose about CORS, cross-origin isolation and TAO (PR #1806) (Tuesday, 28 January)

Shunya Shishido

• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add 1024 as the number of router rule registration limit (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add 1024 as the number of router rule registration limit (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add 1024 as the number of router rule registration limit (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add 1024 as the number of router rule registration limit (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add 1024 as the number of router rule registration limit (PR #1752) (Thursday, 30 January)
• Re: [w3c/ServiceWorker] Add 1024 as the number of router rule registration limit (PR #1752) (Thursday, 30 January)
• [w3c/ServiceWorker] Add 1024 as the number of router rule registration limit (PR #1752) (Thursday, 30 January)
• Re: [w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Check requestMethod (PR #1748) (Friday, 24 January)
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Thursday, 23 January)
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Wednesday, 22 January)

sideshowbarker

• Re: [whatwg/dom] [infra] Integrating generation of W3C-ready review drafts into build pipeline (#832) (Friday, 24 January)
• [w3c/uievents] Fire keypress event for Enter, Shift+Enter, and Ctrl+Enter keys (PR #392) (Friday, 24 January)

Simon Pieters

• Re: [whatwg/fullscreen] Clarification for Accessibility requested (#197) (Monday, 20 January)

Simon Wülker

• [whatwg/dom] Redundant step in `find slottables` (Issue #1349) (Sunday, 19 January)

Simone Onofri

• Re: [w3c/permissions] Bring this document to CR (Issue #454) (Friday, 3 January)

smaug----

• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Friday, 31 January)
• Re: [whatwg/xhr] Allow doubles for ProgressEvent's loaded and total (PR #394) (Friday, 24 January)
• Re: [whatwg/xhr] Allow doubles for ProgressEvent's loaded and total (PR #394) (Wednesday, 22 January)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 15 January)

Softslink

• [w3c/manifest] Softslink PWA Mobile App (Issue #1161) (Friday, 31 January)

stelar7

• [w3c/IndexedDB] Database upgrade wait loop question (Issue #436) (Wednesday, 1 January)

Steve Orvell

• Re: [WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072) (Friday, 24 January)
• Re: [WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072) (Friday, 10 January)

syduki

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Thursday, 16 January)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Thursday, 16 January)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Wednesday, 15 January)

Taym Haddadi

• Re: [whatwg/streams] Fix `[[ViewedArrayBuffer]].[[ByteLength]]` name in ReadableStreamBYOBRequest doc (PR #1337) (Tuesday, 21 January)
• [whatwg/streams] Fix `[[ViewedArrayBuffer]].[[ByteLength]]` name in ReadableStreamBYOBRequest doc (PR #1337) (Sunday, 19 January)

Thomas Steiner

• Re: [w3c/manifest] Prevent Screenshots in PWAs (Issue #1154) (Wednesday, 8 January)

Tyoneb

• [WICG/webcomponents] fix typo (PR #1092) (Tuesday, 28 January)

ud2

• [whatwg/webidl] Legacy platform objects' [[DefineOwnProperty]] refers to possibly nonexistent Desc.[[Value]] (Issue #1460) (Sunday, 5 January)

veeanne0305

• [whatwg/webidl] Intent to use bigint/numeric union (Issue #1462) (Thursday, 16 January)

vmpstr

• [w3ctag/design-reviews] safe-area-max-inset-* variables (Issue #1046) (Thursday, 30 January)

W3C Bot

• Re: [WICG/webcomponents] fix typo (PR #1092) (Tuesday, 28 January)

Westbrook Johnson

• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Friday, 31 January)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Friday, 31 January)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Friday, 31 January)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Thursday, 30 January)
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) (Thursday, 30 January)
• Re: [WICG/webcomponents] Reference Target: How to handle invalid ID references? (Issue #1071) (Thursday, 30 January)
• Re: [WICG/webcomponents] Reference Target: How to handle invalid ID references? (Issue #1071) (Thursday, 30 January)
• Re: [WICG/webcomponents] [exportparts] support exporting via wildcards `exportparts="*, primary-*"` (Issue #1051) (Monday, 27 January)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Monday, 20 January)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Tuesday, 14 January)
• Re: [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083) (Tuesday, 7 January)

Xiaoqian Wu

• [w3c/ServiceWorker] CfC: publish a new Candidate Recommendation Snapshot of Service Worker in the WebApps WG (Issue #1741) (Monday, 20 January)

Yash Raj Bharti

• Re: [w3c/manifest] Prevent Screenshots in PWAs (Issue #1154) (Tuesday, 7 January)
• Re: [w3c/manifest] Prevent Screenshots in PWAs (Issue #1154) (Tuesday, 7 January)
• Re: [w3c/manifest] Prevent Screenshots in PWAs (Issue #1154) (Monday, 6 January)

Yoav Weiss

• Re: [w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690) (Friday, 24 January)
• Re: [whatwg/fetch] Skip unnecessary checks when we have a preloaded response candidate in main fetch (PR #1803) (Thursday, 23 January)
• Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440) (Friday, 3 January)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add limits to the number of router rule registration (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Allow the addRoutes() to be called during installing (PR #1744) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add 1024 as the number of router rule registration limit (PR #1752) (Friday, 31 January)
• Re: [w3c/ServiceWorker] Add 1024 as the number of router rule registration limit (PR #1752) (Thursday, 30 January)
• Re: [w3c/ServiceWorker] Add 1024 as the number of router rule registration limit (PR #1752) (Thursday, 30 January)
• Re: [w3c/ServiceWorker] Add 1024 as the number of router rule registration limit (PR #1752) (Thursday, 30 January)
• Re: [w3c/ServiceWorker] Allow the addRoutes() to be called during installing (PR #1744) (Thursday, 30 January)
• Re: [w3c/ServiceWorker] Editorial: Fix linking errors on [=document=] (PR #1751) (Thursday, 30 January)
• Re: [w3c/ServiceWorker] Allow the addRoutes() to be called during installing (PR #1744) (Thursday, 30 January)
• Re: [w3c/ServiceWorker] Allow the addRoutes() to be called during installing (PR #1744) (Thursday, 30 January)
• Re: [w3c/ServiceWorker] Make cache.put() drain the internal response body. (Fixes #1617) (PR #1619) (Wednesday, 29 January)
• Re: [w3c/ServiceWorker] Use fetch algorithms when getting VARY header values. (Fixes #1609) (PR #1618) (Wednesday, 29 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Wednesday, 29 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Wednesday, 29 January)
• Re: [w3c/ServiceWorker] Editorial: Fix linking errors on [=document=] (PR #1751) (Wednesday, 29 January)
• [w3c/ServiceWorker] Fix linking errors on [=document=] (PR #1751) (Wednesday, 29 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Ensure "race-network-and-fetch-handler" is used with a fetch handler (PR #1719) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Ensure "race-network-and-fetch-handler" is used with a fetch handler (PR #1719) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Ensure "race-network-and-fetch-handler" is used with a fetch handler (PR #1719) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Update editors (PR #1750) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Update editors (PR #1750) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Require `[SecureContext]` for interfaces with `[Exposed=ServiceWorker]` or not? (Issue #1749) (Monday, 27 January)
• Re: [w3c/ServiceWorker] addRoutes should check for requestMethod (Issue #1747) (Monday, 27 January)
• Re: [w3c/ServiceWorker] addRoutes should check for requestMethod (Issue #1747) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Check requestMethod (PR #1748) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Update editors (PR #1750) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Update editors (PR #1750) (Sunday, 26 January)
• Re: [w3c/ServiceWorker] Update editors (PR #1750) (Sunday, 26 January)
• [w3c/ServiceWorker] Update editors (PR #1750) (Sunday, 26 January)
• Re: [w3c/ServiceWorker] Update usages of module fetching html algorithms (PR #1658) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Fixing some spec linking issues (PR #1640) (Friday, 24 January)
• Re: [w3c/ServiceWorker] align default metadata used for both ED and CRD (PR #1647) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Editorial: HTML removed JavaScript from the realm (PR #1659) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Editorial: HTML removed JavaScript from the realm (PR #1659) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure "race-network-and-fetch-handler" is used with a fetch handler (PR #1719) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Check requestMethod (PR #1748) (Friday, 24 January)
• Re: [w3c/ServiceWorker] addRoutes should check for requestMethod (Issue #1747) (Thursday, 23 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Thursday, 23 January)
• Re: [w3c/ServiceWorker] addRoutes should check for requestMethod (Issue #1747) (Thursday, 23 January)
• [w3c/ServiceWorker] Check requestMethod (PR #1748) (Thursday, 23 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Thursday, 23 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Thursday, 23 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Thursday, 23 January)
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Thursday, 23 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] InstallEvent.addRoutes is resolving/rejecting the returned promise synchronously (Issue #1742) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Update workflow (PR #1745) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Update workflow (PR #1745) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Update workflow (PR #1745) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Update workflow (PR #1745) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Update workflow (PR #1745) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Update workflow (PR #1745) (Wednesday, 22 January)
• [w3c/ServiceWorker] Update workflow (PR #1745) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Should InstallEvent.addRoutes reject if the the install event is not active? (Issue #1743) (Wednesday, 22 January)
• [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] InstallEvent.addRoutes is resolving/rejecting the returned promise synchronously (Issue #1742) (Tuesday, 21 January)

youennf

• Re: [w3c/ServiceWorker] Allow the addRoutes() to be called during installing (PR #1744) (Thursday, 30 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Tuesday, 28 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Monday, 27 January)
• Re: [whatwg/streams] Add WritableStream#write convenience method (PR #1339) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Friday, 24 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Thursday, 23 January)
• [w3c/ServiceWorker] addRoutes should check for requestMethod (Issue #1747) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Wednesday, 22 January)
• [w3c/ServiceWorker] What should happen in case of large number of added routes? (Issue #1746) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] InstallEvent.addRoutes is resolving/rejecting the returned promise synchronously (Issue #1742) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Ensure the addRoutes() to be called within the install event (PR #1744) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734) (Tuesday, 21 January)
• [w3c/ServiceWorker] Should InstallEvent.addRoutes reject if the the install event is not active? (Issue #1743) (Tuesday, 21 January)
• [w3c/ServiceWorker] InstallEvent.addRoutes is resolving/rejecting the returned promise synchronously (Issue #1742) (Tuesday, 21 January)

Yves Lafon

• Re: [w3c/ServiceWorker] Update editors (PR #1750) (Monday, 27 January)
• Re: [w3c/ServiceWorker] Update workflow (PR #1745) (Wednesday, 22 January)
• Re: [w3c/ServiceWorker] Update workflow (PR #1745) (Wednesday, 22 January)

Zhou Shuangshuang

• [w3c/selection-api] Inconsistent selectionchange event behavior across browsers when the added input element is not focused (Issue #344) (Monday, 20 January)

Last message date: Friday, 31 January 2025 23:44:20 UTC