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

Tuesday, 20 January 2026

• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) Aaron Gustafson
• 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) fluentaztaskmanager
• [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) fluentaztaskmanager
• Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253) Anne van Kesteren
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) Anne van Kesteren
• Re: [whatwg/fetch] Block 416 alongside 206 (PR #1907) Anne van Kesteren
• Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253) sideshowbarker
• Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253) sideshowbarker
• Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253) Anne van Kesteren
• [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253) Anne van Kesteren
• Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183) Xiaocheng Hu
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) Marcos Cáceres
• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) Yoshisato Yanagisawa

Monday, 19 January 2026

• Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217) Sam Weinig
• Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176) Kevin Babbitt
• Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176) Christian Liebel
• Re: [w3ctag/design-reviews] Incubation: PWA (same-site) Origin Migration (Issue #1164) Christian Liebel
• Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152) Matthew Tylee Atkinson
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Maxim Devaev
• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) Mitar
• Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442) Anne van Kesteren
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Marcos Cáceres
• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) Val Packett
• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) Yoshisato Yanagisawa

Sunday, 18 January 2026

• Re: [w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172) Matthew Tylee Atkinson
• Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442) Bruce B. Anderson
• Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442) yashwant singh
• [w3c/uievents] Proposal: Provide OS specific shortcut key (Issue #412) Martin Auswöger

Friday, 16 January 2026

• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) Christian Stewart
• Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163) Andrew Sutherland
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) Anne van Kesteren
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) Kagami Sascha Rosylight
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) Anne van Kesteren
• Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) Yoshisato Yanagisawa
• Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) Ryosuke Niwa

Thursday, 15 January 2026

• Re: [whatwg/dom] [meta] MutationObserver improvements tracking issue (Issue #1439) Chris Wilson
• Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) NullVoxPopuli
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) Shu-yu Guo
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) Christian Liebel
• Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) Anne van Kesteren
• Re: [whatwg/fullscreen] Fix ambiguous reference to 'allowed to use' (PR #246) Luke Warlow
• Re: [whatwg/fullscreen] Fix ambiguous reference to 'allowed to use' (PR #246) Luke Warlow
• Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163) Andrew Sutherland
• Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) Andrew Sutherland
• Re: [whatwg/streams] Allow error to be provided to reader.releaseLock() (Issue #1358) Kagami Sascha Rosylight
• [w3ctag/design-reviews] Other Spec Review: named-feature() function for CSS @supports (Issue #1186) L. David Baron
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) Kagami Sascha Rosylight
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) Jacob Smith
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) Kagami Sascha Rosylight
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) Jacob Smith
• Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) Kagami Sascha Rosylight
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) Diego Gonzalez
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) Yoshisato Yanagisawa
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) Valentin Gosu
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) Philippe Le Hegaret
• Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784) Christian Liebel
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Marcos Cáceres
• [w3ctag/design-reviews] [wg/webediting] Web Editing Working Group Charter (Issue #1185) W3C Bot
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) Marcos Cáceres
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) carlosjeurissen
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) Christian Liebel
• Re: [whatwg/fullscreen] Fix #245 - Addressing new popover values (PR #247) Anne van Kesteren
• Re: [whatwg/fullscreen] Fix ambiguous reference to 'allowed to use' (PR #246) Anne van Kesteren
• Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445) Anne van Kesteren
• Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) Mattias Buelens
• Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445) Anne van Kesteren
• Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445) Anne van Kesteren
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) Anne van Kesteren
• Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013) Noam Rosenthal
• Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013) Xiaocheng Hu
• Re: [w3ctag/design-reviews] MiniApp Packaging (Issue #762) Xiaocheng Hu
• Re: [w3ctag/design-reviews] MiniApp Packaging (Issue #762) Xiaocheng Hu
• Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) Anne van Kesteren
• Re: [w3ctag/design-reviews] WG Revision: CSS Anchor Positioning Level 1 (Issue #1182) Xiaocheng Hu
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) Yoshisato Yanagisawa
• Re: [whatwg/fetch] Block 416 alongside 206 (PR #1907) Yoshisato Yanagisawa

Wednesday, 14 January 2026

• Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) James M Snell
• Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) James M Snell
• [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362) James M Snell
• Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445) Jayson Chen
• [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445) Jayson Chen
• Re: [whatwg/dom] Add OpaqueRange interface (PR #1404) Stephanie Zhang
• Re: [whatwg/dom] Add PlainTextRange interface (PR #1404) Stephanie Zhang
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) Philippe Le Hegaret
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) Philippe Le Hegaret
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) Philippe Le Hegaret
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) Philippe Le Hegaret
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) Robert Flack
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) Lea Verou
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) Anne van Kesteren
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) Yoshisato Yanagisawa
• [whatwg/fetch] Block 416 alongside 206 (PR #1907) Anne van Kesteren
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) Anne van Kesteren
• Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) Anne van Kesteren
• [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906) Yoshisato Yanagisawa
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Anne van Kesteren
• Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183) Clqsin45

Tuesday, 13 January 2026

• [w3ctag/design-reviews] Incubation: IdP-Initiated FedCM (Issue #1184) Sam Goto
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) Keith Cirkel
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) Jeffrey Yasskin
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) Philippe Le Hegaret
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) Philippe Le Hegaret
• Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) Philippe Le Hegaret
• [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411) Philippe Le Hegaret
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Jayson Chen
• Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183) Jeffrey Yasskin
• Re: [w3c/uievents] Proposal: use `relatedTarget` for click events originated from labels (Issue #402) sb3nder
• Re: [w3c/uievents] Events do not have "default action"s (#104) Philippe Le Hegaret
• Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183) Jeremy Roman
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) Anne van Kesteren
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) Anne van Kesteren
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Anne van Kesteren
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Anne van Kesteren
• Re: [whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903) Anne van Kesteren
• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) Anne van Kesteren
• [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183) Clqsin45
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) Jan-Ivar Bruaroey
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) Jan-Ivar Bruaroey
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) Jan-Ivar Bruaroey
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) Jan-Ivar Bruaroey

Monday, 12 January 2026

• Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422) Jonathan Kingston
• Re: [w3c/uievents] [Proposal] Add "Zoom" event (#31) Philippe Le Hegaret
• Re: [w3ctag/design-reviews] [wg/dx] Dataset Exchange Working Group Charter (Issue #1171) Sarven Capadisli
• Re: [w3ctag/design-reviews] [wg/dx] Dataset Exchange Working Group Charter (Issue #1171) Sarven Capadisli
• Re: [w3c/clipboard-apis] `ClipboardItem`: clarify mime parsing (Issue #242) Edgar Chen
• Re: [whatwg/webidl] Enumeration order of interface members (#432) barthogibon-beep
• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) Edgar Chen
• Re: [whatwg/dom] [meta] MutationObserver improvements tracking issue (Issue #1439) smaug----
• [w3c/editing] `insertText` should move to parent node if range's start container is a void element (Issue #522) Jelle Raaijmakers
• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) Noam Rosenthal
• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) Noam Rosenthal

Sunday, 11 January 2026

• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) Mattias Buelens
• Re: [whatwg/webidl] Meta: update repository files (PR #1562) Anne van Kesteren
• Re: [whatwg/webidl] Meta: update repository files (PR #1562) Anne van Kesteren
• [WICG/webcomponents] Fix HTML Modules inline module script (PR #1121) Dominic Farolino
• [whatwg/webidl] Meta: update repository files (PR #1562) Mattias Buelens
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) Mattias Buelens
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) Mattias Buelens
• Re: [whatwg/webidl] Intent to use Constants (Issue #1561) Meghan Denny
• Re: [w3c/gamepad] Add device orientation support (Issue #211) Jibb Smart
• [whatwg/webidl] Intent to use Constants (Issue #1561) aa0550160163aa-crypto

Saturday, 10 January 2026

• Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) Anne van Kesteren
• Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) Anne van Kesteren
• Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) Meghan Denny
• Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) Anne van Kesteren
• Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) Anne van Kesteren
• [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894) Meghan Denny

Friday, 9 January 2026

• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) Daniel Murphy
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Jayson Chen
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Jayson Chen
• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) Anne van Kesteren
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) Mattias Buelens
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) Mattias Buelens
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) Mattias Buelens
• Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523) Xiaocheng Hu
• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) Anne van Kesteren
• Re: [whatwg/dom] Editorial: correct misleading node equals sentence (PR #1444) Anne van Kesteren
• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) Anne van Kesteren
• [w3c/selection-api] the steps of `Selection.setBaseAndExtent()` do not check the node type (Issue #354) Masayuki Nakano
• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) Evgeny Kapun
• Re: [w3c/selection-api] the steps of Selection.extend() does not check whether the given offset is valid in the container (Issue #353) Masayuki Nakano
• [w3c/selection-api] the steps of Selection.extend() does not check whether the given offset is valid in the container (Issue #353) Masayuki Nakano

Thursday, 8 January 2026

• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) CSS Meeting Bot
• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) Noam Rosenthal
• Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) Tim van der Lippe
• Re: [w3ctag/design-reviews] WG New Spec: RDF 1.2 Semantics (Issue #1160) Sarven Capadisli
• Re: [w3ctag/design-reviews] WG New Spec: RDF 1.2 Semantics (Issue #1160) Sarven Capadisli
• Re: [whatwg/fetch] Accept header for `image` destination should be updated for modern image formats (Issue #1905) Anne van Kesteren
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Anne van Kesteren
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Anne van Kesteren
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Jayson Chen
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Jayson Chen

Wednesday, 7 January 2026

• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Anne van Kesteren
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Anne van Kesteren
• [whatwg/fetch] Accept header for `image` destination should be updated for modern image formats (Issue #1905) Luke Wilde
• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) Anne van Kesteren
• [whatwg/dom] Editorial: correct misleading node equals sentence (PR #1444) Anne van Kesteren
• Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442) Anne van Kesteren
• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) Maksim Sadym
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) Julian Descottes
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) Julian Descottes
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) Julian Descottes
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) Julian Descottes
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) Julian Descottes
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) Julian Descottes
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) Julian Descottes

Tuesday, 6 January 2026

• Re: [whatwg/streams] Should the abort result reflect the close result? (Issue #1203) Kagami Sascha Rosylight
• Re: [w3ctag/design-reviews] Canvas Text Metrics for Editing, Art and Design (Issue #1095) Stephen Chenney
• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) Julian Descottes
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) Julian Descottes
• Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860) Julian Descottes
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) Gregory Terzian
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) Gregory Terzian
• Re: [w3ctag/design-reviews] Canvas Text Metrics for Editing, Art and Design (Issue #1095) Matthew Tylee Atkinson
• [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904) Noam Rosenthal
• Re: [w3ctag/design-reviews] Incubation: seamless page transition with deferred commit (Issue #1177) Noam Rosenthal
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) Mattias Buelens
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) Marcos Cáceres
• Re: [w3c/uievents] Event order between "compositionend" and "input" (#202) Masayuki Nakano
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) Kevin Gibbons
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) Kevin Gibbons
• Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529) Kevin Gibbons

Monday, 5 January 2026

• Re: [whatwg/webidl] Intent to use Constants (Issue #1560) Meghan Denny
• Re: [whatwg/webidl] RL25 (Issue #1559) Meghan Denny
• [whatwg/webidl] Intent to use Constants (Issue #1560) Moh0558665645
• Re: [whatwg/fetch] Should network state be keyed beyond the top-level site (#1035) Simon Farre
• Re: [whatwg/fetch] Update fetch-later spec according to WPT expectations=0D (PR #1902) Tim van der Lippe
• [whatwg/webidl] RL25 (Issue #1559) widiyantilili31-gif
• Re: [w3c/IndexedDB] Old db version is lost when aborting upgrade (Issue #486) stelar7
• [w3c/manifest] Tidied up document using tidy-html5 (PR #1200) github-actions[bot]
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) Daniel Murphy
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) Daniel Murphy
• Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152) Jacques Newman
• Re: [w3ctag/design-reviews] [HTML] Canvas place element (Issue #997) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152) Matthew Tylee Atkinson
• Re: [w3ctag/design-reviews] [HTML] Canvas place element (Issue #997) Matthew Tylee Atkinson
• Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) Ehsan Toreini
• Re: [w3ctag/design-reviews] Incubation: seamless page transition with deferred commit (Issue #1177) Christian Liebel
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) RelunSec
• Re: [whatwg/fetch] Update Note on Request Destination / CSP directive (Issue #1466) Dev Sharma
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) Anne van Kesteren
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) The Moisrex
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) Anne van Kesteren
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) The Moisrex
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) Anne van Kesteren
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) Gregory Terzian
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) Gregory Terzian
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) Gregory Terzian
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) Gregory Terzian
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) Gregory Terzian
• [w3c/IndexedDB] Remove redundant task queueing to start transaction (Issue #487) Gregory Terzian
• Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) Gregory Terzian
• [w3c/IndexedDB] Old db version is lost when aborting upgrade (Issue #486) Gregory Terzian
• [w3c/IndexedDB] Replace connection queue with parallel queue (Issue #485) Gregory Terzian
• [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484) Gregory Terzian

Sunday, 4 January 2026

• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) Martin Thomson
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) The Moisrex
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) swhiteman
• Re: [whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903) Tim van der Lippe
• Re: [whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903) Anne van Kesteren
• [whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903) Josh Matthews
• [whatwg/fetch] Update fetch-later spec according to WPT expectations=0D (PR #1902) Tim van der Lippe
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) James M Snell
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) RelunSec
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) The Moisrex
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) RelunSec
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) Anne van Kesteren
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) RelunSec
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) The Moisrex
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) The Moisrex
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) RelunSec
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) Anne van Kesteren
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) RelunSec
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) swhiteman
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) The Moisrex
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) swhiteman
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) The Moisrex
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) Jayson Chen
• Re: [whatwg/webidl] Intent to use Constantly (Issue #1558) Meghan Denny
• Re: [whatwg/webidl] Intent to use Constantly (Issue #1558) nguyenhung11450-create
• Re: [whatwg/webidl] Intent to use Constantly (Issue #1558) nguyenhung11450-create
• [whatwg/webidl] Intent to use Constantly (Issue #1558) nguyenhung11450-create

Saturday, 3 January 2026

• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) Anne van Kesteren
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) RelunSec
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) Meghan Denny
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) RelunSec
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) James M Snell
• Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) James M Snell
• [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893) RelunSec

Friday, 2 January 2026

• Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876) Dominic Farolino
• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) Evgeny Kapun
• Re: [whatwg/webidl] Fix IsDetachedBuffer check in ArrayBuffer transfer (PR #1557) Domenic Denicola
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) Mattias Buelens
• [whatwg/webidl] Fix IsDetachedBuffer check in ArrayBuffer transfer (PR #1557) Domenic Denicola
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) Domenic Denicola
• Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) Anne van Kesteren

Thursday, 1 January 2026

• [w3c/editing] [execCommand] Incorrect condition in 9.9 toggle-lists (Issue #521) InvalidUsernameException

Last message date: Tuesday, 20 January 2026 14:57:36 UTC