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

aa0550160163aa-crypto

• [whatwg/webidl] Intent to use Constants (Issue #1561) (Sunday, 11 January)

Aaron Gustafson

• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 22 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Tuesday, 20 January)

Adam Rice

• Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359) (Thursday, 29 January)

Adam Sobieski

• [w3c/clipboard-apis] Clipboarding and Multipart MIME (Issue #247) (Saturday, 31 January)

alsalhahmad523-dotcom

• [w3c/ServiceWorker] 1.1 (Issue #1815) (Saturday, 24 January)

Andrea Giammarchi

• Re: [whatwg/dom] Should `Attr.isConnected` return `false` if element is connected? (Issue #1448) (Tuesday, 27 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Tuesday, 27 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Friday, 23 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Friday, 23 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Thursday, 22 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Thursday, 22 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Thursday, 22 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Thursday, 22 January)

Andrew Sutherland

• Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163) (Wednesday, 21 January)
• Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163) (Friday, 16 January)
• Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163) (Thursday, 15 January)
• Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) (Thursday, 15 January)

Anne van Kesteren

• Re: [whatwg/webidl] Support syntax for specifying that an optional record<K, V> has a default value of an empty record<K, V> (Issue #1566) (Saturday, 31 January)
• Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) (Friday, 30 January)
• Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) (Friday, 30 January)
• Re: [whatwg/webidl] Is nullable dictionary member a footgun? (Issue #1565) (Friday, 30 January)
• Re: [whatwg/fetch] Support serverCertificateHashes in obtain a connection for WebTransport (Issue #1880) (Wednesday, 28 January)
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Wednesday, 28 January)
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Wednesday, 28 January)
• Re: [whatwg/fetch] main fetch assumes file:// URLs are tuple origin (Issue #1908) (Sunday, 25 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Sunday, 25 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Sunday, 25 January)
• Re: [whatwg/url] What happens on non scalar value strings? (Issue #897) (Saturday, 24 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Saturday, 24 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Saturday, 24 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Saturday, 24 January)
• Re: [whatwg/url] Percent encoding examples seem to be wrong (Issue #895) (Saturday, 24 January)
• [whatwg/url] Correct example that did not encode backslash in userinfo (PR #896) (Saturday, 24 January)
• Re: [whatwg/url] Percent encoding examples seem to be wrong (Issue #895) (Saturday, 24 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Thursday, 22 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Thursday, 22 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253) (Tuesday, 20 January)
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) (Tuesday, 20 January)
• Re: [whatwg/fetch] Block 416 alongside 206 (PR #1907) (Tuesday, 20 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253) (Tuesday, 20 January)
• [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253) (Tuesday, 20 January)
• Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442) (Monday, 19 January)
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Friday, 16 January)
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Friday, 16 January)
• Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) (Thursday, 15 January)
• Re: [whatwg/fullscreen] Fix #245 - Addressing new popover values (PR #247) (Thursday, 15 January)
• Re: [whatwg/fullscreen] Fix ambiguous reference to 'allowed to use' (PR #246) (Thursday, 15 January)
• Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445) (Thursday, 15 January)
• Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445) (Thursday, 15 January)
• Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445) (Thursday, 15 January)
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) (Thursday, 15 January)
• Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) (Thursday, 15 January)
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) (Wednesday, 14 January)
• [whatwg/fetch] Block 416 alongside 206 (PR #1907) (Wednesday, 14 January)
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) (Wednesday, 14 January)
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) (Wednesday, 14 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Wednesday, 14 January)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Tuesday, 13 January)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Tuesday, 13 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 13 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 13 January)
• Re: [whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903) (Tuesday, 13 January)
• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) (Tuesday, 13 January)
• Re: [whatwg/webidl] Meta: update repository files (PR #1562) (Sunday, 11 January)
• Re: [whatwg/webidl] Meta: update repository files (PR #1562) (Sunday, 11 January)
• Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) (Saturday, 10 January)
• Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) (Saturday, 10 January)
• Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) (Saturday, 10 January)
• Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) (Saturday, 10 January)
• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) (Friday, 9 January)
• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) (Friday, 9 January)
• Re: [whatwg/dom] Editorial: correct misleading node equals sentence (PR #1444) (Friday, 9 January)
• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) (Friday, 9 January)
• Re: [whatwg/fetch] Accept header for `image` destination should be updated for modern image formats (Issue #1905) (Thursday, 8 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Thursday, 8 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Thursday, 8 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Wednesday, 7 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Wednesday, 7 January)
• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) (Wednesday, 7 January)
• [whatwg/dom] Editorial: correct misleading node equals sentence (PR #1444) (Wednesday, 7 January)
• Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442) (Wednesday, 7 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Monday, 5 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Monday, 5 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Monday, 5 January)
• Re: [whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Saturday, 3 January)
• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) (Friday, 2 January)

barthogibon-beep

• Re: [whatwg/webidl] Enumeration order of interface members (#432) (Monday, 12 January)

Ben Francis

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

Bruce B. Anderson

• Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442) (Sunday, 18 January)

carlosjeurissen

• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 22 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 15 January)

Chris Swithinbank

• Re: [w3ctag/design-reviews] CSS Overflow Navigation Controls (Carousels) (Issue #1037) (Monday, 26 January)

Chris Wilson

• Re: [whatwg/dom] [meta] MutationObserver improvements tracking issue (Issue #1439) (Thursday, 15 January)

Christian Liebel

• Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (PR #1205) (Thursday, 29 January)
• Re: [w3c/manifest] [Editorial] Fixes "default display mode" terminology (PR #1204) (Thursday, 29 January)
• [w3c/manifest] Add `color_scheme_dark` member and themeable members (PR #1205) (Thursday, 29 January)
• Re: [w3c/manifest] Editorial: map definition of `minimal-ui` to `window.open()` with `features` set to `"popup"` (PR #1203) (Thursday, 29 January)
• Re: [w3c/manifest] Editorial: add a note on out-of-scope manifest linking behavior (PR #1202) (Thursday, 29 January)
• [w3c/manifest] Editorial: map definition of `minimal-ui` to `window.open()` with `features` set to `"popup"` (PR #1203) (Thursday, 29 January)
• [w3c/manifest] Editorial: add a note on out-of-scope manifest linking behavior (PR #1202) (Thursday, 29 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 29 January)
• Re: [w3ctag/design-reviews] Other Spec Review: named-feature() function for CSS @supports (Issue #1186) (Monday, 26 January)
• Re: [w3ctag/design-reviews] Other Spec Review: named-feature() function for CSS @supports (Issue #1186) (Monday, 26 January)
• Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176) (Monday, 26 January)
• Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176) (Monday, 26 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Friday, 23 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 22 January)
• Re: [w3ctag/design-reviews] [wg/webediting] Web Editing Working Group Charter (Issue #1185) (Thursday, 22 January)
• Re: [w3ctag/design-reviews] [wg/webediting] Web Editing Working Group Charter (Issue #1185) (Thursday, 22 January)
• Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176) (Monday, 19 January)
• Re: [w3ctag/design-reviews] Incubation: PWA (same-site) Origin Migration (Issue #1164) (Monday, 19 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 15 January)
• Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784) (Thursday, 15 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 15 January)
• Re: [w3ctag/design-reviews] Incubation: seamless page transition with deferred commit (Issue #1177) (Monday, 5 January)

Christian Stewart

• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Friday, 16 January)

Claas Augner

• Re: [whatwg/dom] Should `Attr.isConnected` return `false` if element is connected? (Issue #1448) (Tuesday, 27 January)
• Re: [whatwg/dom] Should `Attr.isConnected` return `false` if element is connected? (Issue #1448) (Tuesday, 27 January)
• [whatwg/dom] Should `Attr.isConnected` return `false` if element is connected? (Issue #1448) (Tuesday, 27 January)

Clqsin45

• Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183) (Wednesday, 14 January)
• [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183) (Tuesday, 13 January)

Copilot

• Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (PR #1205) (Thursday, 29 January)
• Re: [w3c/manifest] Editorial: map definition of `minimal-ui` to `window.open()` with `features` set to `"popup"` (PR #1203) (Thursday, 29 January)
• Re: [w3c/manifest] Editorial: add a note on out-of-scope manifest linking behavior (PR #1202) (Thursday, 29 January)

CSS Meeting Bot

• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) (Thursday, 8 January)

Cyberpunk-00

• Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384) (Thursday, 29 January)

Dan Clark

• Re: [whatwg/dom] Add reference target to shadow root (PR #1353) (Thursday, 29 January)
• Re: [whatwg/dom] Add reference target to shadow root (PR #1353) (Thursday, 29 January)

Daniel Murphy

• Re: [w3c/manifest] user initiated 'uninstall' event (#1201) (Friday, 23 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 22 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Tuesday, 20 January)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Friday, 9 January)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Monday, 5 January)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Monday, 5 January)

Daniil Sakhapov

• Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413) (Tuesday, 27 January)
• Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413) (Tuesday, 27 January)
• [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413) (Tuesday, 27 January)

Dev Sharma

• Re: [whatwg/fetch] Update Note on Request Destination / CSP directive (Issue #1466) (Monday, 5 January)

Diego Gonzalez

• [w3c/manifest] [Editorial] Fixes "default display mode" terminology (PR #1204) (Thursday, 29 January)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Thursday, 29 January)
• Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176) (Tuesday, 27 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 15 January)

Domenic Denicola

• Re: [whatwg/webidl] Fix IsDetachedBuffer check in ArrayBuffer transfer (PR #1557) (Friday, 2 January)
• [whatwg/webidl] Fix IsDetachedBuffer check in ArrayBuffer transfer (PR #1557) (Friday, 2 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) (Friday, 2 January)

Dominic Farolino

• Re: [whatwg/webidl] Support syntax for specifying that an optional record<K, V> has a default value of an empty record<K, V> (Issue #1566) (Saturday, 31 January)
• [WICG/webcomponents] Fix HTML Modules inline module script (PR #1121) (Sunday, 11 January)
• Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876) (Friday, 2 January)

Dominique Hazael-Massieux

• Re: [whatwg/webidl] Add disposer and async_disposer (PR #1488) (Wednesday, 28 January)

Edgar Chen

• Re: [w3c/clipboard-apis] `ClipboardItem`: clarify mime parsing (Issue #242) (Monday, 12 January)
• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) (Monday, 12 January)

Ehsan Toreini

• Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) (Monday, 5 January)

Evgeny Kapun

• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) (Friday, 9 January)
• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) (Friday, 2 January)

fluentaztaskmanager

• Re: [w3c/permissions] Editorial: add an introduction (#381) (5ef3f03) (Tuesday, 20 January)
• Re: [w3c/permissions] Businesses provide emails and say to email with any inquiries, when emailed they say don't email or respond to email. (Issue #472) (Tuesday, 20 January)
• [w3c/permissions] Businesses provide emails and say to email with any inquiries, when emailed they say don't email or respond to email. (Issue #472) (Tuesday, 20 January)

github-actions[bot]

• [w3c/manifest] Tidied up document using tidy-html5 (PR #1200) (Monday, 5 January)

Gregory Terzian

• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) (Tuesday, 6 January)
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) (Tuesday, 6 January)
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) (Monday, 5 January)
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) (Monday, 5 January)
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) (Monday, 5 January)
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) (Monday, 5 January)
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) (Monday, 5 January)
• [w3c/IndexedDB] Remove redundant task queueing to start transaction (Issue #487) (Monday, 5 January)
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) (Monday, 5 January)
• [w3c/IndexedDB] Old db version is lost when aborting upgrade (Issue #486) (Monday, 5 January)
• [w3c/IndexedDB] Replace connection queue with parallel queue (Issue #485) (Monday, 5 January)
• [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) (Monday, 5 January)

hsingh-moz

• Re: [w3c/IndexedDB] In "object store storage operation", be more explicit about how to handle ConstraintError from an index (Issue #477) (Thursday, 29 January)

InvalidUsernameException

• [w3c/editing] [execCommand] Incorrect condition in 9.9 toggle-lists (Issue #521) (Thursday, 1 January)

Jacob Smith

• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Thursday, 15 January)
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Thursday, 15 January)

Jacques Newman

• Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152) (Tuesday, 20 January)
• Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152) (Monday, 5 January)

Jake Archibald

• Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) (Friday, 30 January)
• Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) (Friday, 30 January)
• Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) (Tuesday, 27 January)
• Re: [whatwg/dom] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #1189) (Monday, 26 January)
• Re: [w3c/ServiceWorker] Express the job queue in terms of parallel queues (#1197) (Friday, 23 January)

James M Snell

• Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359) (Saturday, 31 January)
• Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) (Saturday, 31 January)
• Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) (Saturday, 31 January)
• Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) (Wednesday, 14 January)
• Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) (Wednesday, 14 January)
• [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) (Wednesday, 14 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Saturday, 3 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Saturday, 3 January)

Jan-Ivar Bruaroey

• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Wednesday, 21 January)
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Tuesday, 13 January)
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Tuesday, 13 January)
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Tuesday, 13 January)
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Tuesday, 13 January)

Jayson Chen

• Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445) (Wednesday, 14 January)
• [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445) (Wednesday, 14 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 13 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Friday, 9 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Friday, 9 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Thursday, 8 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Thursday, 8 January)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Sunday, 4 January)

Jeffrey Yasskin

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Tuesday, 13 January)
• Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183) (Tuesday, 13 January)
• Re: [w3ctag/design-reviews] [HTML] Canvas place element (Issue #997) (Monday, 5 January)

Jelle Raaijmakers

• [w3c/editing] `insertText` should move to parent node if range's start container is a void element (Issue #522) (Monday, 12 January)

Jeremy Roman

• Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183) (Tuesday, 13 January)

Jibb Smart

• Re: [w3c/gamepad] Add device orientation support (Issue #211) (Sunday, 11 January)

jinesrodrigo7-blip

• Re: [whatwg/fetch] Allow `new Response` with 101 status code (Issue #1759) (Saturday, 31 January)

Jonathan Kingston

• Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) (Friday, 30 January)
• Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) (Friday, 30 January)
• Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) (Friday, 30 January)
• Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) (Tuesday, 27 January)
• Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) (Monday, 12 January)

Josh Matthews

• [whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903) (Sunday, 4 January)

Julian Descottes

• Re: [whatwg/fetch] Add WebDriver BiDi network logging with stable request IDs (PR #1860) (Thursday, 29 January)
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) (Wednesday, 7 January)
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) (Wednesday, 7 January)
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) (Wednesday, 7 January)
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) (Wednesday, 7 January)
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) (Wednesday, 7 January)
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) (Wednesday, 7 January)
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) (Wednesday, 7 January)
• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Tuesday, 6 January)
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) (Tuesday, 6 January)
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) (Tuesday, 6 January)

juliettreyes12-ui

• [whatwg/webidl] Jul (Issue #1564) (Friday, 23 January)

juner

• Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359) (Saturday, 31 January)
• Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359) (Friday, 30 January)
• Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359) (Friday, 30 January)
• Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359) (Friday, 30 January)

Kagami Sascha Rosylight

• Re: [whatwg/webidl] Support syntax for specifying that an optional record<K, V> has a default value of an empty record<K, V> (Issue #1566) (Saturday, 31 January)
• Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359) (Friday, 30 January)
• [whatwg/webidl] Is nullable dictionary member a footgun? (Issue #1565) (Thursday, 29 January)
• Re: [whatwg/streams] Do the abort steps of ReadableStreamPipeTo really guarantee the abort callback to be called before cancel? (Issue #1229) (Thursday, 29 January)
• Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359) (Wednesday, 28 January)
• Re: [whatwg/webidl] Add typed ReadableStream<type> and WritableStream<type> (#951) (Wednesday, 21 January)
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Friday, 16 January)
• Re: [whatwg/streams] Allow error to be provided to reader.releaseLock() (Issue #1358) (Thursday, 15 January)
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Thursday, 15 January)
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Thursday, 15 January)
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Thursday, 15 January)
• Re: [whatwg/streams] Should the abort result reflect the close result? (Issue #1203) (Tuesday, 6 January)

Keith Cirkel

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

Kevin Babbitt

• Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176) (Monday, 19 January)

Kevin Gibbons

• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Tuesday, 6 January)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Tuesday, 6 January)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Tuesday, 6 January)

L. David Baron

• [w3ctag/design-reviews] Other Spec Review: named-feature() function for CSS @supports (Issue #1186) (Thursday, 15 January)

Lea Verou

• Re: [whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107) (Tuesday, 20 January)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Wednesday, 14 January)

Luke Warlow

• Re: [whatwg/fullscreen] Fix ambiguous reference to 'allowed to use' (PR #246) (Thursday, 15 January)
• Re: [whatwg/fullscreen] Fix ambiguous reference to 'allowed to use' (PR #246) (Thursday, 15 January)

Luke Wilde

• [whatwg/fetch] Accept header for `image` destination should be updated for modern image formats (Issue #1905) (Wednesday, 7 January)

Maksim Sadym

• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Wednesday, 7 January)

Marcos Cáceres

• Re: [w3c/manifest] fetched icons fail in chrome when same-origin policy is present (Issue #1065) (Thursday, 29 January)
• Re: [w3c/manifest] fetched icons fail in chrome when same-origin policy is present (Issue #1065) (Thursday, 29 January)
• Re: [w3c/manifest] Icon purpose "splashscreen" and splashscreen text (#844) (Thursday, 29 January)
• Re: [w3c/manifest] Icon purpose "splashscreen" and splashscreen text (#844) (Thursday, 29 January)
• Re: [w3c/manifest] Web Manifest Overrides (Issue #1045) (Thursday, 29 January)
• Re: [w3c/manifest] Web Manifest Overrides (Issue #1045) (Thursday, 29 January)
• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Thursday, 29 January)
• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Thursday, 29 January)
• Re: [w3c/manifest] Add `related_applications` and `prefer_related_applications` to WPT (#950) (Thursday, 29 January)
• Re: [w3c/manifest] Add `related_applications` and `prefer_related_applications` to WPT (#950) (Thursday, 29 January)
• Re: [w3c/manifest] [Proposal] 'maximized' and 'minimized' display modes values (#839) (Thursday, 29 January)
• Re: [w3c/manifest] [Proposal] 'maximized' and 'minimized' display modes values (#839) (Thursday, 29 January)
• Re: [w3c/manifest] Add more than one icon at PWA install (#841) (Thursday, 29 January)
• Re: [w3c/manifest] Add more than one icon at PWA install (#841) (Thursday, 29 January)
• Re: [w3c/manifest] Why is purpose a "unordered set of unique space-separated tokens"? (#903) (Thursday, 29 January)
• Re: [w3c/manifest] Why is purpose a "unordered set of unique space-separated tokens"? (#903) (Thursday, 29 January)
• Re: [w3c/manifest] Add "payment" dictionary for payment app specific properties (#866) (Thursday, 29 January)
• Re: [w3c/manifest] Add "payment" dictionary for payment app specific properties (#866) (Thursday, 29 January)
• Re: [w3c/manifest] Bring back "serviceworker" member (#864) (Thursday, 29 January)
• Re: [w3c/manifest] Bring back "serviceworker" member (#864) (Thursday, 29 January)
• Re: [w3c/manifest] Provide guidance to UAs on appropriate names for "platform" members (#862) (Thursday, 29 January)
• Re: [w3c/manifest] Provide guidance to UAs on appropriate names for "platform" members (#862) (Thursday, 29 January)
• Re: [w3c/manifest] Add support for "share_target" property (#665) (Thursday, 29 January)
• Re: [w3c/manifest] Add support for "share_target" property (#665) (Thursday, 29 January)
• Re: [w3c/manifest] Add an icon "purpose" for displaying on the theme color (#617) (Thursday, 29 January)
• Re: [w3c/manifest] Add an icon "purpose" for displaying on the theme color (#617) (Thursday, 29 January)
• Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171) (Thursday, 29 January)
• Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171) (Thursday, 29 January)
• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1200) (Thursday, 29 January)
• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1200) (Thursday, 29 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Monday, 26 January)
• Re: [w3c/manifest] user initiated 'uninstall' event (#1201) (Monday, 26 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Wednesday, 21 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Tuesday, 20 January)
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Monday, 19 January)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Thursday, 15 January)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 15 January)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 6 January)

marekpawlucy05-maker

• Re: [w3c/IndexedDB] In "object store storage operation", be more explicit about how to handle ConstraintError from an index (Issue #477) (Tuesday, 20 January)

Marijn Kruisselbrink

• Re: [w3c/ServiceWorker] Express the job queue in terms of parallel queues (#1197) (Friday, 23 January)

Martin Auswöger

• [w3c/uievents] Proposal: Provide OS specific shortcut key (Issue #412) (Sunday, 18 January)

Martin Thomson

• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Sunday, 4 January)

Masayuki Nakano

• Re: [w3c/editing] Firefox: Up/Down arrow navigation doesn't work with absolutely positioned elements in contenteditable (Issue #523) (Saturday, 24 January)
• Re: [w3c/editing] Firefox: Up/Down arrow navigation doesn't work with absolutely positioned elements in contenteditable (Issue #523) (Saturday, 24 January)
• Re: [w3c/editing] `insertText` should move to parent node if range's start container is a void element (Issue #522) (Thursday, 22 January)
• [w3c/selection-api] the steps of `Selection.setBaseAndExtent()` do not check the node type (Issue #354) (Friday, 9 January)
• Re: [w3c/selection-api] the steps of Selection.extend() does not check whether the given offset is valid in the container (Issue #353) (Friday, 9 January)
• [w3c/selection-api] the steps of Selection.extend() does not check whether the given offset is valid in the container (Issue #353) (Friday, 9 January)
• Re: [w3c/uievents] Event order between "compositionend" and "input" (#202) (Tuesday, 6 January)

Matthew Tylee Atkinson

• Re: [w3ctag/design-reviews] CSS find-in-page highlight pseudos (Issue #1120) (Friday, 23 January)
• Re: [w3ctag/design-reviews] User-defined script "entry points" for performance timing (Issue #1012) (Thursday, 22 January)
• Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152) (Monday, 19 January)
• Re: [w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172) (Sunday, 18 January)
• Re: [w3ctag/design-reviews] Canvas Text Metrics for Editing, Art and Design (Issue #1095) (Tuesday, 6 January)
• Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152) (Monday, 5 January)
• Re: [w3ctag/design-reviews] [HTML] Canvas place element (Issue #997) (Monday, 5 January)

Mattias Buelens

• Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359) (Friday, 30 January)
• Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) (Thursday, 15 January)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Sunday, 11 January)
• [whatwg/webidl] Meta: update repository files (PR #1562) (Sunday, 11 January)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Sunday, 11 January)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Sunday, 11 January)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Friday, 9 January)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Friday, 9 January)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Friday, 9 January)
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Tuesday, 6 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) (Friday, 2 January)

Max Waterman

• [w3c/manifest] user initiated 'uninstall' event (#1201) (Friday, 23 January)

Maxim Devaev

• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Monday, 19 January)

Meghan Denny

• Re: [whatwg/webidl] Intent to use Constants (Issue #1561) (Sunday, 11 January)
• Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) (Saturday, 10 January)
• [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) (Saturday, 10 January)
• Re: [whatwg/webidl] Intent to use Constants (Issue #1560) (Monday, 5 January)
• Re: [whatwg/webidl] RL25 (Issue #1559) (Monday, 5 January)
• Re: [whatwg/webidl] Intent to use Constantly (Issue #1558) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Saturday, 3 January)

Michael Aufreiter

• Re: [w3c/editing] Firefox: Up/Down arrow navigation doesn't work with absolutely positioned elements in contenteditable (Issue #523) (Monday, 26 January)
• [w3c/editing] Repro for #523. (PR #524) (Friday, 23 January)
• [w3c/editing] Firefox: Up/Down arrow navigation doesn't work with absolutely positioned elements in contenteditable (Issue #523) (Friday, 23 January)

Michal Mocny

• Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013) (Friday, 23 January)

Mike Taylor

• Re: [w3c/permissions] Businesses provide emails and say to email with any inquiries, when emailed they say don't email or respond to email. (Issue #472) (Tuesday, 20 January)

Mike West

• Re: [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173) (Wednesday, 28 January)
• Re: [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173) (Wednesday, 28 January)

Mitar

• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) (Monday, 19 January)

Moh0558665645

• [whatwg/webidl] Intent to use Constants (Issue #1560) (Monday, 5 January)

Monica Chintala

• Re: [w3c/ServiceWorker] Change the spec so that when a new SW is being registered it's set to not use cache the first time (#1103) (Friday, 30 January)
• Re: [w3c/ServiceWorker] Change the spec so that when a new SW is being registered it's set to not use cache the first time (#1103) (Friday, 30 January)
• Re: [w3c/ServiceWorker] Touching documents in an "in parallel" section makes no sense (#1108) (Friday, 30 January)
• Re: [w3c/ServiceWorker] Allow `None` as value for `Service-Worker-Allowed`. (#1165) (Friday, 30 January)
• Re: [w3c/ServiceWorker] Allow `None` as value for `Service-Worker-Allowed`. (#1165) (Friday, 30 January)
• Re: [w3c/ServiceWorker] should FetchEvent.request ever be a range request if we cannot verify if the underlying resource is the same? (#1201) (Friday, 30 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 29 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 29 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Tuesday, 27 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Tuesday, 27 January)
• Re: [w3c/ServiceWorker] messageerror event should use ExtendableMessageEvent (#1193) (Monday, 26 January)
• Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814) (Monday, 26 January)
• Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814) (Monday, 26 January)
• Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814) (Monday, 26 January)
• Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814) (Friday, 23 January)
• [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814) (Friday, 23 January)
• Re: [w3c/ServiceWorker] Editorial: "Update Service Worker Extended Events Set" minor fix (PR #1813) (Friday, 23 January)
• Re: [w3c/ServiceWorker] Issues with "Handle Functional Event" (#1196) (Friday, 23 January)
• Re: [w3c/ServiceWorker] Express the job queue in terms of parallel queues (#1197) (Friday, 23 January)
• Re: [w3c/ServiceWorker] fetch-frame-resource.https.html has a long timeout to detect page load failed (#1194) (Friday, 23 January)
• Re: [w3c/ServiceWorker] messageerror event should use ExtendableMessageEvent (#1193) (Friday, 23 January)
• Re: [w3c/ServiceWorker] How can we use SW module link in backward-compatible manner? (#1186) (Friday, 23 January)
• Re: [w3c/ServiceWorker] How can we use SW module link in backward-compatible manner? (#1186) (Friday, 23 January)
• Re: [w3c/ServiceWorker] respondWith is not implementable as written (#1168) (Friday, 23 January)
• Re: [w3c/ServiceWorker] respondWith touches JS objects in parallel sections (#1169) (Friday, 23 January)
• Re: [w3c/ServiceWorker] respondWith creates JS objects in parallel (#1170) (Friday, 23 January)
• Re: [w3c/ServiceWorker] Carefully audit all uses of "in parallel" in the spec (#1172) (Friday, 23 January)
• Re: [w3c/ServiceWorker] What does it mean to "choose any object"? (#1171) (Friday, 23 January)
• Re: [w3c/ServiceWorker] What does it mean to "choose any object"? (#1171) (Friday, 23 January)
• Re: [w3c/ServiceWorker] Update 'ancestor origins list' xref (PR #1812) (Friday, 23 January)
• Re: [w3c/ServiceWorker] Update 'ancestor origins list' xref (PR #1812) (Friday, 23 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 22 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 22 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 22 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Thursday, 22 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Tuesday, 20 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Tuesday, 20 January)

nguyenhung11450-create

• Re: [whatwg/webidl] Intent to use Constantly (Issue #1558) (Sunday, 4 January)
• Re: [whatwg/webidl] Intent to use Constantly (Issue #1558) (Sunday, 4 January)
• [whatwg/webidl] Intent to use Constantly (Issue #1558) (Sunday, 4 January)

Nikita Skovoroda

• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Monday, 26 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Monday, 26 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Monday, 26 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Monday, 26 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Saturday, 24 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Saturday, 24 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Saturday, 24 January)
• Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896) (Saturday, 24 January)
• Re: [whatwg/url] What happens on non scalar value strings? (Issue #897) (Saturday, 24 January)
• Re: [whatwg/url] What happens on non scalar value strings? (Issue #897) (Saturday, 24 January)
• [whatwg/url] What happens on non-scalar strings? (Issue #897) (Saturday, 24 January)
• Re: [whatwg/url] Correct example that did not encode backslash in userinfo (PR #896) (Saturday, 24 January)
• Re: [whatwg/url] Correct example that did not encode backslash in userinfo (PR #896) (Saturday, 24 January)
• Re: [whatwg/url] Percent encoding examples seem to be wrong (Issue #895) (Saturday, 24 January)
• [whatwg/url] Url encoding examples seem wrong (Issue #895) (Saturday, 24 January)
• Re: [whatwg/encoding] UTF-8 does not reset state when returning error (Issue #359) (Thursday, 22 January)
• Re: [whatwg/encoding] UTF-8 does not reset state when returning error (Issue #359) (Thursday, 22 January)
• Re: [whatwg/encoding] ISO-2022-JP does not reset state when returning error (Issue #358) (Thursday, 22 January)
• [whatwg/encoding] UTF-8 / UTF-16 do not reset state when returning error (Issue #359) (Thursday, 22 January)

Noam Rosenthal

• Re: [whatwg/webidl] Support syntax for specifying that an optional record<K, V> has a default value of an empty record<K, V> (Issue #1566) (Saturday, 31 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Monday, 26 January)
• Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013) (Thursday, 15 January)
• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) (Monday, 12 January)
• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) (Monday, 12 January)
• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) (Thursday, 8 January)
• [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) (Tuesday, 6 January)
• Re: [w3ctag/design-reviews] Incubation: seamless page transition with deferred commit (Issue #1177) (Tuesday, 6 January)

NullVoxPopuli

• Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Thursday, 15 January)

Philip Jägenstedt

• Re: [whatwg/dom] Add Marker interface (PR #1447) (Tuesday, 27 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Tuesday, 27 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Tuesday, 27 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Thursday, 22 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Thursday, 22 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Thursday, 22 January)
• Re: [whatwg/dom] Add Marker interface (PR #1447) (Thursday, 22 January)
• [whatwg/dom] Add Marker interface (PR #1447) (Thursday, 22 January)

Philippe Le Hegaret

• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) (Thursday, 15 January)
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) (Wednesday, 14 January)
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) (Wednesday, 14 January)
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) (Wednesday, 14 January)
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) (Wednesday, 14 January)
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) (Tuesday, 13 January)
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) (Tuesday, 13 January)
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) (Tuesday, 13 January)
• [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) (Tuesday, 13 January)
• Re: [w3c/uievents] Events do not have "default action"s (#104) (Tuesday, 13 January)
• Re: [w3c/uievents] [Proposal] Add "Zoom" event (#31) (Monday, 12 January)

rdcronin

• Re: [whatwg/fetch] Allow user agents to use more permissive header validation in extensions (Issue #1878) (Thursday, 29 January)

Reilly Grant

• Re: [whatwg/webidl] Add typed ReadableStream<type> and WritableStream<type> (#951) (Tuesday, 20 January)

RelunSec

• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Monday, 5 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Saturday, 3 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Saturday, 3 January)
• [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Saturday, 3 January)

Robert Flack

• [w3c/selection-api] Inconsistent selectstart event timing and prevention capability (Issue #355) (Tuesday, 27 January)
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) (Wednesday, 14 January)

roraja

• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) (Wednesday, 28 January)

Ryosuke Niwa

• Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Friday, 16 January)

Sam Goto

• [w3ctag/design-reviews] Incubation: IdP-Initiated FedCM (Issue #1184) (Tuesday, 13 January)

Sam Weinig

• [whatwg/webidl] Reconsider advice to leave dictionary members optional when dictionary is used solely as a return type (Issue #1567) (Saturday, 31 January)
• [whatwg/webidl] Support syntax for specifying that an optional record<K, V> has a default value of an empty record<K, V> (Issue #1566) (Friday, 30 January)
• Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217) (Monday, 19 January)

Sarven Capadisli

• Re: [w3ctag/design-reviews] [wg/vc] Verifiable Credentials Working Group (Issue #1179) (Thursday, 29 January)
• Re: [w3ctag/design-reviews] WG Revision: SHACL 1.2 SPARQL (Issue #1174) (Thursday, 29 January)
• Re: [w3ctag/design-reviews] WG Revision: SHACL 1.2 Core (Issue #1166) (Thursday, 22 January)
• Re: [w3ctag/design-reviews] [wg/dx] Dataset Exchange Working Group Charter (Issue #1171) (Monday, 12 January)
• Re: [w3ctag/design-reviews] [wg/dx] Dataset Exchange Working Group Charter (Issue #1171) (Monday, 12 January)
• Re: [w3ctag/design-reviews] WG New Spec: RDF 1.2 Semantics (Issue #1160) (Thursday, 8 January)
• Re: [w3ctag/design-reviews] WG New Spec: RDF 1.2 Semantics (Issue #1160) (Thursday, 8 January)

Sascha Block

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

sb3nder

• Re: [w3c/uievents] Proposal: use `relatedTarget` for click events originated from labels (Issue #402) (Tuesday, 13 January)

Shannon Booth

• Re: [whatwg/fetch] main fetch assumes file:// URLs are tuple origin (Issue #1908) (Sunday, 25 January)
• Re: [whatwg/fetch] main fetch assumes file:// URLs are tuple origin (Issue #1908) (Sunday, 25 January)
• [whatwg/fetch] main fetch assumes file:// URLs are tuple origin (Issue #1908) (Sunday, 25 January)

Shu-yu Guo

• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) (Thursday, 15 January)

sideshowbarker

• Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253) (Tuesday, 20 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253) (Tuesday, 20 January)

Simon Farre

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

Simon Pieters

• [w3c/ServiceWorker] Update 'ancestor origins list' xref (PR #1812) (Thursday, 22 January)

smaug----

• [whatwg/dom] https://dom.spec.whatwg.org/#dom-range-deletecontents may collapse the Range to an invalid position (Issue #1446) (Wednesday, 21 January)
• Re: [whatwg/dom] [meta] MutationObserver improvements tracking issue (Issue #1439) (Monday, 12 January)

stelar7

• Re: [w3c/IndexedDB] Old db version is lost when aborting upgrade (Issue #486) (Monday, 5 January)

Stephanie Zhang

• Re: [whatwg/dom] Add OpaqueRange interface (PR #1404) (Wednesday, 14 January)
• Re: [whatwg/dom] Add PlainTextRange interface (PR #1404) (Wednesday, 14 January)

Stephen Chenney

• Re: [w3ctag/design-reviews] Canvas Text Metrics for Editing, Art and Design (Issue #1095) (Tuesday, 6 January)

Steve Kobes (Chromium)

• [w3ctag/design-reviews] Other Spec Review: Scoped View Transitions (Issue #1188) (Friday, 30 January)

Steven

• Re: [whatwg/fetch] Add "text" destination type, for JavaScript text imports (PR #1898) (Sunday, 25 January)

swhiteman

• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)

The Moisrex

• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Monday, 5 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Monday, 5 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) (Sunday, 4 January)

Tim van der Lippe

• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) (Thursday, 8 January)
• Re: [whatwg/fetch] Update fetch-later spec according to WPT expectations=0D (PR #1902) (Monday, 5 January)
• Re: [whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903) (Sunday, 4 January)
• [whatwg/fetch] Update fetch-later spec according to WPT expectations=0D (PR #1902) (Sunday, 4 January)

Val Packett

• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) (Monday, 19 January)

Valentin Gosu

• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) (Thursday, 15 January)

W3C Bot

• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1200) (Thursday, 29 January)
• [w3ctag/design-reviews] [wg/das] Devices and Sensors Working Group 2026 Charter (Issue #1187) (Thursday, 29 January)
• [w3ctag/design-reviews] [wg/webediting] Web Editing Working Group Charter (Issue #1185) (Thursday, 15 January)

widiyantilili31-gif

• [whatwg/webidl] RL25 (Issue #1559) (Monday, 5 January)

Xiaocheng Hu

• Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013) (Thursday, 22 January)
• Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183) (Tuesday, 20 January)
• Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013) (Thursday, 15 January)
• Re: [w3ctag/design-reviews] MiniApp Packaging (Issue #762) (Thursday, 15 January)
• Re: [w3ctag/design-reviews] MiniApp Packaging (Issue #762) (Thursday, 15 January)
• Re: [w3ctag/design-reviews] WG Revision: CSS Anchor Positioning Level 1 (Issue #1182) (Thursday, 15 January)
• Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523) (Friday, 9 January)

Xiaoqian Wu

• Re: [w3ctag/design-reviews] [wg/webediting] Web Editing Working Group Charter (Issue #1185) (Thursday, 22 January)

yashwant singh

• Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442) (Sunday, 18 January)

Yoav Weiss

• Re: [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173) (Wednesday, 28 January)
• Re: [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173) (Wednesday, 28 January)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Friday, 30 January)
• Re: [w3c/ServiceWorker] fetch-frame-resource.https.html has a long timeout to detect page load failed (#1194) (Wednesday, 28 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Tuesday, 27 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Tuesday, 27 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Tuesday, 27 January)
• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Tuesday, 27 January)
• Re: [w3c/ServiceWorker] Issues with "Handle Functional Event" (#1196) (Monday, 26 January)
• Re: [w3c/ServiceWorker] Issues with "Handle Functional Event" (#1196) (Monday, 26 January)
• Re: [w3c/ServiceWorker] Editorial: "Update Service Worker Extended Events Set" minor fix (PR #1813) (Monday, 26 January)
• Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814) (Monday, 26 January)
• Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814) (Monday, 26 January)
• Re: [w3c/ServiceWorker] 1.1 (Issue #1815) (Monday, 26 January)
• Re: [w3c/ServiceWorker] 1.1 (Issue #1815) (Monday, 26 January)
• Re: [w3c/ServiceWorker] fetch-frame-resource.https.html has a long timeout to detect page load failed (#1194) (Friday, 23 January)
• Re: [w3c/ServiceWorker] Editorial: "Update Service Worker Extended Events Set" minor fix (PR #1813) (Friday, 23 January)
• [w3c/ServiceWorker] Editorial: "Update Service Worker Extended Events Set" minor fix (PR #1813) (Friday, 23 January)
• Re: [w3c/ServiceWorker] Update 'ancestor origins list' xref (PR #1812) (Friday, 23 January)
• Re: [w3c/ServiceWorker] Update 'ancestor origins list' xref (PR #1812) (Friday, 23 January)
• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) (Tuesday, 20 January)
• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) (Monday, 19 January)
• Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) (Monday, 19 January)
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Friday, 16 January)
• Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163) (Friday, 16 January)
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Friday, 16 January)
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) (Thursday, 15 January)
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) (Thursday, 15 January)
• Re: [whatwg/fetch] Block 416 alongside 206 (PR #1907) (Thursday, 15 January)
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) (Wednesday, 14 January)
• [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) (Wednesday, 14 January)

Last message date: Saturday, 31 January 2026 23:54:26 UTC