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

Thursday, 25 September 2025

• Re: [w3c/push-api] Add Kagami as Editor (PR #412) Kagami Sascha Rosylight
• Re: [w3c/push-api] Add Kagami as Editor (PR #412) Kagami Sascha Rosylight
• Re: [w3c/push-api] Add Kagami as Editor (PR #412) Kagami Sascha Rosylight
• Re: [whatwg/fetch] Automatic decompression should sanitize `Content-Encoding` and `Content-Length` headers from the response (Issue #1729) Edun Omatseye
• Re: [w3c/push-api] Add Kagami as Editor (PR #412) Peter Beverloo
• Re: [w3c/push-api] Add Kagami as Editor (PR #412) Martin Thomson
• [w3c/push-api] Add Kagami as Editor (PR #412) Martin Thomson
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Luke Warlow
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Luke Warlow
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Luke Warlow
• Re: [w3c/push-api] TPAC 2025 status report (Issue #404) Kagami Sascha Rosylight
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) Anne van Kesteren
• Re: [whatwg/webidl] Create npm-grunt.yml (PR #1527) Domenic Denicola
• [whatwg/webidl] Create npm-grunt.yml (PR #1527) Gg860ren
• Re: [whatwg/streams] Meta: move explainers to subdirectory (PR #1355) Domenic Denicola
• Re: [whatwg/streams] Meta: move explainers to subdirectory (PR #1355) Domenic Denicola
• Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140) Jeffrey Yasskin
• Re: [w3c/push-api] TPAC 2025 status report (Issue #404) Martin Thomson
• Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140) Martin Thomson

Wednesday, 24 September 2025

• Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140) Jeffrey Yasskin
• Re: [whatwg/streams] Meta: move explainers to subdirectory (PR #1355) Mattias Buelens
• Re: [whatwg/streams] Meta: move explainers to subdirectory (PR #1355) Mattias Buelens
• [whatwg/dom] Disposable AbortController (Issue #1405) Kevin Gibbons
• Re: [w3c/push-api] TPAC 2025 status report (Issue #404) Peter Beverloo
• Re: [whatwg/storage] consider setting StorageKey on environment explicitly (Issue #142) brisamariellunadiaz-gif
• Re: [whatwg/storage] consider setting StorageKey on environment explicitly (Issue #142) brisamariellunadiaz-gif
• Re: [w3c/push-api] TPAC 2025 status report (Issue #404) Kagami Sascha Rosylight
• Re: [whatwg/fetch] Add the "speculationrules" destination (PR #1841) Anne van Kesteren
• Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140) andypaicu
• Re: [whatwg/fetch] Add the "speculationrules" destination (PR #1841) Antonio Sartori
• Re: [whatwg/fetch] Add the "speculationrules" destination (PR #1841) Anne van Kesteren
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) roraja
• Re: [whatwg/fetch] Add the "speculationrules" destination (PR #1841) Domenic Denicola
• Re: [whatwg/fetch] Add the "speculationrules" destination (PR #1841) Anne van Kesteren
• Re: [whatwg/fetch] Add the "speculationrules" destination (PR #1841) Domenic Denicola
• Re: [whatwg/fetch] Add the "speculationrules" destination (PR #1841) Anne van Kesteren
• Re: [whatwg/fetch] Add the "speculationrules" destination (PR #1841) Anne van Kesteren
• Re: [w3c/push-api] TPAC 2025 status report (Issue #404) Anne van Kesteren
• Re: [w3c/push-api] TPAC 2025 status report (Issue #404) Marcos Cáceres
• Re: [w3c/push-api] TPAC 2025 status report (Issue #404) Marcos Cáceres
• Re: [whatwg/streams] Fix typo: correct 'folowing' to 'following' in closeAlgorithm definition (PR #1356) Domenic Denicola
• Re: [whatwg/streams] Fix typo: correct 'folowing' to 'following' in closeAlgorithm definition (PR #1356) Domenic Denicola
• Re: [whatwg/fetch] Add the "speculationrules" destination (PR #1841) Domenic Denicola

Tuesday, 23 September 2025

• Re: [whatwg/dom] Add FormControlRange interface (PR #1404) Stephanie Zhang
• Re: [w3ctag/design-reviews] ScrollIntoViewOptions container attribute (Issue #1105) Robert Flack
• Re: [w3c/IndexedDB] Add descending order for getAll() and getAllKeys() (#130) Nikita
• Re: [w3ctag/design-reviews] ScrollIntoViewOptions container attribute (Issue #1105) Jacob Groß
• Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) Anne van Kesteren
• Re: [whatwg/url] New UTS46 version (Issue #881) Anne van Kesteren
• Re: [whatwg/url] New UTS46 version (Issue #881) François Daoust
• Re: [whatwg/url] New UTS46 version (Issue #881) Marcos Del Sol Vives
• Re: [whatwg/url] New UTS46 version (Issue #881) Anne van Kesteren
• Re: [whatwg/url] New UTS46 version (Issue #881) Marcos Del Sol Vives
• Re: [whatwg/url] New UTS46 version (Issue #881) Anne van Kesteren

Monday, 22 September 2025

• Re: [w3c/IndexedDB] Should IDBDatabase::close() be in parallel? (Issue #474) Andrew Sutherland
• [whatwg/url] New UTS46 version (Issue #881) Marcos Del Sol Vives
• [w3c/screen-orientation] Are ScreenOrientation change events scoped as tightly as possible (Issue #262) bvandersloot-mozilla
• [w3c/screen-orientation] Editorial: pre-lock conditions definition placement (Issue #261) bvandersloot-mozilla
• [w3c/screen-orientation] Fingerprinting risk: users that configure their device to not permit screen locking (Issue #260) bvandersloot-mozilla
• [w3c/screen-orientation] Must natural orientation be detectable? (Issue #259) bvandersloot-mozilla
• Re: [w3c/IndexedDB] Should IDBDatabase::close() be in parallel? (Issue #474) Steven Becker
• Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) Jeffrey Yasskin
• Re: [w3c/IndexedDB] Add descending order for getAll() and getAllKeys() (#130) Steven Becker
• Re: [w3ctag/design-reviews] [wg/png] PNG Working Group Charter (Issue #1143) Chris Lilley
• [w3ctag/design-reviews] WG Revision: Screen Orientation (Issue #1155) Xiaoqian Wu
• Re: [w3ctag/design-reviews] [wg/png] PNG Working Group Charter (Issue #1143) Christian Liebel
• Re: [w3ctag/design-reviews] [wg/png] PNG Working Group Charter (Issue #1143) Christian Liebel
• [w3ctag/design-reviews] [ig/me] Media & Entertainment Interest Group Charter (Issue #1154) W3C Bot
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [w3ctag/design-reviews] [wg/png] PNG Working Group Charter (Issue #1143) Chris Lilley
• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Maksim Sadym
• Re: [whatwg/encoding] "For logical right shifts operands must have at ..." (#250) tz-maker
• Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) Anne van Kesteren
• Re: [w3ctag/design-reviews] Approximate Geolocation (Issue #1131) Martin Thomson
• [whatwg/webidl] mn4198900@gmail.com (Issue #1526) mn4198900-droid
• Re: [whatwg/webidl] mn4198900@gmail.com (Issue #1525) mn4198900-droid
• Re: [whatwg/webidl] mn4198900@gmail.com (Issue #1525) mn4198900-droid
• Re: [whatwg/webidl] mn4198900@gmail.com (Issue #1525) mn4198900-droid
• [whatwg/webidl] mn4198900@gmail.com (Issue #1525) mn4198900-droid

Sunday, 21 September 2025

• [w3c/clipboard-apis] `ClipboardItem`: clarify mime parsing (Issue #242) Gae24
• Re: [whatwg/webidl] Intent to use Constants (Issue #1524) sideshowbarker
• [whatwg/streams] Fix typo: correct 'folowing' to 'following' in closeAlgorithm definition (PR #1356) Shivendra Kumar
• [whatwg/webidl] Intent to use Constants (Issue #1524) andyjoris112-pixel

Friday, 19 September 2025

• [w3c/selection-api] StaticRange.getBoundingClientRect() (Issue #352) fregante
• Re: [whatwg/streams] Meta: implement TransferArrayBuffer correctly in reference implementation (ae5fbaa) Andrus89119
• [w3ctag/design-reviews] WG New Spec: Direction feature for `scroll-state()` query (Issue #1153) Munira
• [w3c/IndexedDB] Should IDBDatabase::close() be in parallel? (Issue #474) stelar7
• Re: [w3c/ServiceWorker] Restrict openWindow() to http(s) schemes? (#699) Anne van Kesteren
• Re: [w3c/ServiceWorker] Restrict openWindow() to http(s) schemes? (#699) Anne van Kesteren
• Re: [w3c/ServiceWorker] Allow preventing the update process to finish (#761) Monica Chintala
• Re: [w3c/permissions] Add an optional `topLevelOrigin` parameter to the `permissions.setPermission` command (PR #468) Chris Fredrickson
• Re: [w3c/ServiceWorker] consult document CSP in Register algorithm (#755) Monica Chintala
• Re: [w3c/ServiceWorker] Worker-As-A-Service service workers (#744) Monica Chintala
• Re: [w3c/ServiceWorker] Worker-As-A-Service service workers (#744) Monica Chintala
• Re: [w3c/ServiceWorker] ServiceWorker scriptURL XSS Filtering (#743) Monica Chintala
• Re: [w3c/ServiceWorker] ServiceWorker scriptURL XSS Filtering (#743) Monica Chintala
• Re: [w3c/ServiceWorker] support updating multiple service workers coherently (#727) Monica Chintala
• Re: [w3c/ServiceWorker] support updating multiple service workers coherently (#727) Monica Chintala

Thursday, 18 September 2025

• Re: [w3c/ServiceWorker] Add name param to Clients.openWindow() method (#711) Monica Chintala
• Re: [w3c/ServiceWorker] Restrict openWindow() to http(s) schemes? (#699) Monica Chintala
• Re: [w3c/ServiceWorker] Restrict openWindow() to http(s) schemes? (#699) Monica Chintala
• Re: [w3c/permissions] Add an optional `topLevelOrigin` parameter to the `permissions.setPermission` command (PR #468) Marcos Cáceres
• Re: [w3c/selection-api] setPosition/collapse should taken an optional argument for whether the caret is before or after a line break (#51) Marijn Haverbeke
• Re: [w3c/selection-api] setPosition/collapse should taken an optional argument for whether the caret is before or after a line break (#51) Ruby
• Re: [whatwg/webidl] Legacy platform objects' [[DefineOwnProperty]] refers to possibly nonexistent Desc.[[Value]] (Issue #1460) Nicolò Ribaudo
• Re: [whatwg/webidl] Legacy platform objects' [[DefineOwnProperty]] refers to possibly nonexistent Desc.[[Value]] (Issue #1460) ud2
• Re: [whatwg/fetch] Add note that `signal` is always initialized (PR #1856) Anne van Kesteren
• Re: [whatwg/fetch] Add note that `signal` is always initialized (PR #1856) Anne van Kesteren
• Re: [whatwg/fetch] Add note that `signal` is always initialized (PR #1856) Tim van der Lippe
• Re: [w3c/uievents] Define what layerX/layerY do in presence of transforms. (Issue #398) Emilio Cobos Álvarez
• Re: [w3c/permissions] Add an optional `topLevelOrigin` parameter to the `permissions.setPermission` command (PR #468) Mike Taylor
• Re: [whatwg/webidl] Legacy platform objects' [[DefineOwnProperty]] refers to possibly nonexistent Desc.[[Value]] (Issue #1460) Nicolò Ribaudo
• Re: [w3c/DOM-Parsing] Proposal on how to deal with <script>-blocks when appending to the DOM (Issue #76) Luke Warlow
• Re: [w3c/DOM-Parsing] Proposal on how to deal with <script>-blocks when appending to the DOM (Issue #76) Simon Pieters
• Re: [w3c/DOM-Parsing] Proposal on how to deal with <script>-blocks when appending to the DOM (Issue #76) lukas
• Re: [w3c/DOM-Parsing] Proposal on how to deal with <script>-blocks when appending to the DOM (Issue #76) Simon Pieters
• Re: [whatwg/fetch] Add note that `signal` is always initialized (PR #1856) Anne van Kesteren
• Re: [whatwg/dom] Make it possible to wrap [parts of] the contents of a <textarea> or <input> in a Range (Issue #1375) Anne van Kesteren
• [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152) Jacques Newman

Wednesday, 17 September 2025

• Re: [whatwg/dom] Make it possible to wrap [parts of] the contents of a <textarea> or <input> in a Range (Issue #1375) Pascal Vos
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Tim van der Lippe
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Tim van der Lippe
• Re: [whatwg/fetch] Accept headers in spec cause confusion (#274) Valentin Gosu
• Re: [w3c/ServiceWorker] Optimization opportunity for SW (Should sync/push event target a specific server?) (#644) Jonathan Jeon
• Re: [w3c/ServiceWorker] Optimization opportunity for SW (Should sync/push event target a specific server?) (#644) Anne van Kesteren
• Re: [whatwg/fetch] Accept headers in spec cause confusion (#274) Anne van Kesteren
• Re: [whatwg/fetch] Accept headers in spec cause confusion (#274) Moonchild
• Re: [whatwg/fetch] Accept headers in spec cause confusion (#274) Valentin Gosu
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [w3ctag/design-reviews] Canvas Text Metrics for Editing, Art and Design (Issue #1095) Florin Malita
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Anne van Kesteren
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Anne van Kesteren
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Anne van Kesteren

Tuesday, 16 September 2025

• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Tim van der Lippe
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Tim van der Lippe
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Tim van der Lippe
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) jgraham
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Anne van Kesteren
• Re: [whatwg/fetch] upload progress? (#21) Jake Archibald
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Anne van Kesteren
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Anne van Kesteren
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Anne van Kesteren
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Anne van Kesteren
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Jake Archibald
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Jake Archibald
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Anne van Kesteren
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Noam Rosenthal
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] [WebDriver BiDi] emulate `user-agent` string (PR #1851) Maksim Sadym
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Christopher
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Anne van Kesteren
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Tim van der Lippe
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Jake Archibald
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Jake Archibald
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Jake Archibald
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Jake Archibald
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) Anne van Kesteren
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) roraja
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) roraja
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) roraja
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) roraja
• Re: [w3ctag/design-reviews] Other Spec Review: TCP Socket Pool per-Top-Level-Site (Issue #1151) Ari Chivukula

Monday, 15 September 2025

• Re: [w3ctag/design-reviews] Other Spec Review: TCP Socket Pool per-Top-Level-Site (Issue #1151) Jeffrey Yasskin
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Luke Warlow
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Rasmus Schultz
• Re: [w3ctag/design-reviews] Approximate Geolocation (Issue #1131) Alvin Ji
• Re: [w3c/charter-html] IDs and style (c1962d3) bcopeland2025-byte
• [w3ctag/design-reviews] Other Spec Review: TCP Socket Pool per-Top-Level-Site (Issue #1151) Ari Chivukula
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Luke Warlow
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Anne van Kesteren
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Luke Warlow
• Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843) Jake Archibald
• Re: [whatwg/fetch] Investigate usage of "append" for headers (Issue #1850) Valentin Sarychev
• Re: [whatwg/webidl] Review Draft Publication: September 2025 (PR #1523) Anne van Kesteren
• Re: [whatwg/webidl] Review Draft Publication: September 2025 (PR #1523) sideshowbarker
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Tim van der Lippe
• [whatwg/webidl] Review Draft Publication: September 2025 (PR #1523) Anne van Kesteren
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Anne van Kesteren
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Tim van der Lippe
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Anne van Kesteren
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Marcos Cáceres
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Marcos Cáceres
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Marcos Cáceres
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Marcos Cáceres

Sunday, 14 September 2025

• Re: [WICG/webcomponents] Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? (#762) Isaiah Thomason

Saturday, 13 September 2025

• Re: [w3ctag/design-reviews] Approximate Geolocation (Issue #1131) Jeffrey Yasskin
• Re: [w3c/selection-api] setPosition/collapse should taken an optional argument for whether the caret is before or after a line break (#51) Marijn Haverbeke
• Re: [w3c/selection-api] setPosition/collapse should taken an optional argument for whether the caret is before or after a line break (#51) Ruby
• Re: [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Tim van der Lippe
• [whatwg/fetch] Mark `AbortSignal` as nullable (PR #1856) Tim van der Lippe
• Re: [whatwg/fetch] Should network state be keyed beyond the top-level site (#1035) amr01060

Friday, 12 September 2025

• Re: [w3c/selection-api] setPosition/collapse should taken an optional argument for whether the caret is before or after a line break (#51) Marijn Haverbeke
• Re: [w3ctag/design-reviews] Approximate Geolocation (Issue #1131) Alvin Ji
• Re: [w3ctag/design-reviews] Approximate Geolocation (Issue #1131) Alvin Ji
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) Alice
• Re: [WICG/webcomponents] Reference Target: what type should the `referenceTarget` attribute be? (Issue #1093) Alice
• Re: [w3ctag/design-reviews] Approximate Geolocation (Issue #1131) Jeffrey Yasskin
• [whatwg/dom] initial changes (PR #1404) Stephanie Y Zhang
• Re: [w3ctag/design-reviews] Approximate Geolocation (Issue #1131) Yves Lafon
• Re: [w3ctag/design-reviews] Approximate Geolocation (Issue #1131) Yves Lafon
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) Michael Aufreiter
• Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) Dennis Richter
• Re: [whatwg/fetch] Pass in Content-Encoding to resource-timing (PR #1742) Anne van Kesteren
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) Zgroza (Luke Klimek)
• Re: [w3c/selection-api] setPosition/collapse should taken an optional argument for whether the caret is before or after a line break (#51) Ruby
• Re: [w3c/selection-api] Need to be able to tell if the caret is displayed at the beginning or the end of the line (#32) Ruby
• Re: [whatwg/fetch] Pass in Content-Encoding to resource-timing (PR #1742) Anne van Kesteren
• Re: [whatwg/fetch] Pass in Content-Encoding to resource-timing (PR #1742) Yoav Weiss
• Re: [whatwg/url] Resolving relative `file:` URL strings without explicit base into URL objects (Issue #879) Anne van Kesteren

Thursday, 11 September 2025

• Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224) Matt Reynolds
• Re: [whatwg/url] مشكلة (Issue #880) Meghan Denny
• [whatwg/url] مشكلة (Issue #880) صالح عبد الله صالح الشهري، معيار المحاسبة العالمية
• [whatwg/url] Resolving relative `file:` URL strings without explicit base into URL objects (Issue #879) Livia Medeiros
• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) Monica Chintala
• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) Monica Chintala
• Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232) Zgroza (Luke Klimek)
• Re: [w3c/editing] TPAC 2025 - What points should we add to the agenda? (Issue #487) Johannes Wilm
• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) Anne van Kesteren
• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) Ashish Kumar
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) Anne van Kesteren
• Re: [w3c/ServiceWorker] Revise cache storage lookup using the "obtain a local storage bottle map" algorithm (Issue #1788) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Revise cache storage lookup using the "obtain a local storage bottle map" algorithm (Issue #1788) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: CacheStorage/global object definition is unnecessary (Issue #1791) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Editorial: remove unnecessary CacheStorage global object definition (PR #1792) Yoshisato Yanagisawa

Wednesday, 10 September 2025

• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) Zgroza (Luke Klimek)
• Re: [w3c/ServiceWorker] Editorial: remove unnecessary CacheStorage global object definition (PR #1792) Monica Chintala
• Re: [w3ctag/design-reviews] CSS find-in-page highlight pseudos (Issue #1120) Matthew Tylee Atkinson
• Re: [w3ctag/design-reviews] [wg/didmethods] DID Methods Working Group (Issue #1137) Sarven Capadisli
• Re: [w3ctag/design-reviews] [wg/didmethods] DID Methods Working Group (Issue #1137) Sarven Capadisli
• [w3ctag/design-reviews] [wg/json-ld] JSON-LD Working Group Charter (Issue #1150) W3C Bot
• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) Anne van Kesteren
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239) Anne van Kesteren
• Re: [w3c/push-api] Remove redundant requirements around permissions and secure contexts (PR #411) Anne van Kesteren
• Re: [w3c/push-api] The security consideration section still requires service worker unregistration to unsubscribe push (Issue #409) Anne van Kesteren
• Re: [w3c/push-api] Move deactivation requirement out of security section (PR #410) Anne van Kesteren
• Re: [w3c/push-api] Remove redundant requirements around permissions and secure contexts (PR #411) Kagami Sascha Rosylight
• Re: [w3c/push-api] Move deactivation requirement out of security section (PR #410) Kagami Sascha Rosylight
• [w3c/push-api] Remove redundant requirements around permissions and secure contexts (PR #411) Anne van Kesteren
• [w3c/push-api] Move deactivation requirement out of security section (PR #410) Anne van Kesteren
• Re: [w3c/push-api] The security consideration section still requires service worker unregistration to unsubscribe push (Issue #409) Anne van Kesteren
• [w3c/push-api] The security consideration section still requires service worker unregistration to unsubscribe push (Issue #409) Kagami Sascha Rosylight
• Re: [w3c/push-api] Declarative Web Push (Issue #360) Anne van Kesteren
• Re: [w3c/push-api] Declarative Web Push (Issue #360) Anne van Kesteren
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Anne van Kesteren
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Anne van Kesteren
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Anne van Kesteren
• Re: [w3c/ServiceWorker] Editorial: remove unnecessary CacheStorage global object definition (PR #1792) Yoshisato Yanagisawa
• Re: [whatwg/fetch] Encourage web browser User-Agent value to start with `Mozilla/5.0 (` (PR #1855) Anne van Kesteren
• Re: [whatwg/fetch] Encourage web browser User-Agent value to start with `Mozilla/5.0 (` (PR #1855) Anne van Kesteren
• Re: [whatwg/dom] Clarify that addEventListener() callback accepts regular function (Issue #1403) Runbing
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Marcos Cáceres
• Re: [w3c/ServiceWorker] Editorial: remove unnecessary CacheStorage global object definition (PR #1792) Domenic Denicola
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Marcos Cáceres
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Marcos Cáceres
• Re: [whatwg/url] Return null origin of "blob:" URL containing inner non-"http(s):" URL (PR #771) masuodhbarazndhmahmuod
• Re: [whatwg/url] Return null origin of "blob:" URL containing inner non-"http(s):" URL (PR #771) masuodhbarazndhmahmuod
• Re: [whatwg/url] Return null origin of "blob:" URL containing inner non-"http(s):" URL (PR #771) masuodhbarazndhmahmuod
• Re: [whatwg/url] Return null origin of "blob:" URL containing inner non-"http(s):" URL (PR #771) masuodhbarazndhmahmuod
• Re: [whatwg/url] Return null origin of "blob:" URL containing inner non-"http(s):" URL (PR #771) masuodhbarazndhmahmuod
• Re: [whatwg/url] Return null origin of "blob:" URL containing inner non-"http(s):" URL (PR #771) masuodhbarazndhmahmuod
• Re: [whatwg/url] Return null origin of "blob:" URL containing inner non-"http(s):" URL (PR #771) masuodhbarazndhmahmuod
• Re: [w3c/ServiceWorker] Editorial: remove unnecessary CacheStorage global object definition (PR #1792) Yoshisato Yanagisawa
• [w3c/ServiceWorker] Editorial: remove unnecessary CacheStorage global object definition (PR #1792) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Yoshisato Yanagisawa
• Re: [whatwg/dom] Clarify that addEventListener() callback accepts regular function (Issue #1403) Domenic Denicola
• Re: [whatwg/dom] Clarify that addEventListener() callback accepts regular function (Issue #1403) Domenic Denicola
• Re: [whatwg/fetch] Encourage web browser User-Agent value to start with `Mozilla/5.0 (` (PR #1855) Domenic Denicola

Tuesday, 9 September 2025

• Re: [w3c/FileAPI] Editorial: Refactor blob URL store definition (PR #213) W3C Bot
• [whatwg/dom] Clarify that addEventListener() callback accepts regular function (Issue #1403) Runbing
• [whatwg/fetch] Encourage web browser User-Agent value to start with `Mozilla/5.0 (` (PR #1855) Anne van Kesteren
• Re: [whatwg/fetch] Introduce "override fetch". (PR #1840) Anne van Kesteren
• Re: [whatwg/fetch] Introduce "override fetch". (PR #1840) Anne van Kesteren
• Re: [whatwg/fetch] Accept headers in spec cause confusion (#274) Anne van Kesteren
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Anne van Kesteren
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Anne van Kesteren
• Re: [w3c/FileAPI] Editorial: Refactor blob URL store definition (PR #213) Anne van Kesteren
• Re: [w3c/FileAPI] Editorial: Refactor blob URL store definition (PR #213) Anne van Kesteren
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Anne van Kesteren
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [w3c/selection-api] Should onselectstart and onselectionchange have content attributes or just IDL attributes? (Issue #351) Anne van Kesteren
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Anne van Kesteren
• Re: [w3ctag/design-reviews] CSS find-in-page highlight pseudos (Issue #1120) Bramus
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Anne van Kesteren
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Monica Chintala
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] What does "the registration’s storage key’s name to cache map" mean? (Issue #1784) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Handle Fetch: Use correct storage key for subresource requests (PR #1790) Yoshisato Yanagisawa
• Re: [w3c/selection-api] Should onselectstart and onselectionchange have content attributes or just IDL attributes? (Issue #351) Masayuki Nakano

Monday, 8 September 2025

• Re: [w3c/selection-api] Should onselectstart and onselectionchange have content attributes or just IDL attributes? (Issue #351) Joey Arhar
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [w3c/ServiceWorker] Handle Fetch: Use correct storage key for subresource requests (PR #1790) Ben Kelly
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Anne van Kesteren
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Anne van Kesteren
• [w3c/push-api] Relationship between push messages and push subscription unclear (Issue #408) Anne van Kesteren
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Anne van Kesteren
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Anne van Kesteren
• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) Edgar Chen
• [w3ctag/design-reviews] [ig/webai] Web&AI Interest Group (Issue #1149) W3C Bot
• [w3ctag/design-reviews] Incubation: Preventing User Dictionary Leaks via ::spelling-error and ::grammar-error CSS Pseudo-Elements (Issue #1148) Ari Chivukula
• Re: [w3ctag/design-reviews] CSS find-in-page highlight pseudos (Issue #1120) Matthew Tylee Atkinson
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Yoshisato Yanagisawa
• Re: [w3c/IndexedDB] Add descending order for getAll() and getAllKeys() (#130) Nikita
• Re: [WICG/webcomponents] Reference Target "phase 2": seeking feedback and use cases (Issue #1111) Alice
• [w3c/ServiceWorker] Editorial: CacheStorage/global object definition is unnecessary (Issue #1791) Domenic Denicola
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Domenic Denicola
• Re: [whatwg/webidl] `IsResizableArrayBuffer` abstract operation now invalid (Issue #1520) Domenic Denicola
• Re: [whatwg/webidl] Editorial: replace `IsResizableArrayBuffer` with `IsFixedLengthArrayBuffer` (PR #1521) Domenic Denicola
• Re: [whatwg/webidl] Editorial: replace `IsResizableArrayBuffer` with `IsFixedLengthArrayBuffer` (PR #1521) Domenic Denicola

Saturday, 6 September 2025

• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Monica Chintala
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Monica Chintala

Friday, 5 September 2025

• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Monica Chintala
• [whatwg/webidl] `ReadableStream.return(Promise)` inconsistent with async generator behavior (Issue #1522) Hans Brende
• Re: [w3c/ServiceWorker] Handle Fetch: Use correct storage key for subresource requests (PR #1790) Monica Chintala
• Re: [w3c/ServiceWorker] Handle Fetch: Use correct storage key for subresource requests (PR #1790) Monica Chintala
• Re: [w3ctag/design-reviews] [wg/webextensions] Web Extensions Working Group (Issue #1138) Sarven Capadisli
• Re: [w3ctag/design-reviews] [wg/webextensions] Web Extensions Working Group (Issue #1138) Sarven Capadisli
• [w3ctag/design-reviews] WG New Spec: FedCM—Support Structured JSON Responses from IdPs (Issue #1147) Suresh P
• Re: [w3c/ServiceWorker] Handle Fetch: Use correct storage key for subresource requests (PR #1790) Yoshisato Yanagisawa
• [w3c/ServiceWorker] Handle Fetch: Use correct storage key for subresource requests (PR #1790) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Replaying POST requests (#693) Monica Chintala
• Re: [w3c/ServiceWorker] Replaying POST requests (#693) Monica Chintala
• Re: [w3c/ServiceWorker] SW's default lifetime limit (#679) Monica Chintala
• Re: [w3c/ServiceWorker] Pattern for handling fingerprinted assets in cache? (#657) Monica Chintala
• Re: [w3c/ServiceWorker] Pattern for handling fingerprinted assets in cache? (#657) Monica Chintala

Thursday, 4 September 2025

• Re: [w3c/ServiceWorker] Should UUID for unique IDs be mandated? (#647) Monica Chintala
• Re: [w3c/ServiceWorker] Should UUID for unique IDs be mandated? (#647) Monica Chintala
• Re: [w3c/ServiceWorker] Optimization opportunity for SW (Should sync/push event target a specific server?) (#644) Monica Chintala
• Re: [w3c/ServiceWorker] Expose environment ids? (#643) Monica Chintala
• Re: [w3c/ServiceWorker] [Feature request] Clients should know their own IDs (#1557) Monica Chintala
• Re: [w3c/ServiceWorker] [Feature request] Clients should know their own IDs (#1557) Monica Chintala
• Re: [w3c/manifest] Add API to fetch the current document's calculated manifest (Issue #1179) Marcos Cáceres
• Re: [w3c/manifest] Add API to fetch the current document's calculated manifest (Issue #1179) Daniel Murphy
• Re: [w3c/manifest] Add API to fetch the current document's calculated manifest (Issue #1179) Daniel Murphy
• Re: [w3c/manifest] Add API to fetch the current document's calculated manifest (Issue #1179) Marcos Cáceres
• Re: [w3c/ServiceWorker] What does "the registration’s storage key’s name to cache map" mean? (Issue #1784) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] What does "the registration’s storage key’s name to cache map" mean? (Issue #1784) Yoshisato Yanagisawa
• Re: [w3c/manifest] multiple pwa on same origin could be conflicting for app scoped to path (Issue #1180) Daniel Murphy
• [whatwg/webidl] Editorial: replace `IsResizableArrayBuffer` with `IsFixedLengthArrayBuffer` (PR #1521) Mattias Buelens
• [w3ctag/design-reviews] Incubation: Proofreader API (Issue #1146) QueenieZqq
• [w3ctag/design-reviews] WG New Spec: FedCM—Support showing third-party iframe origins in the UI (Issue #1145) Christian Biesinger
• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) Rob Eisenberg
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052) Jeffrey Yasskin
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [w3c/push-api] Expose pushManager on Window (PR #393) Kagami Sascha Rosylight
• Re: [w3c/ServiceWorker] What does "the registration’s storage key’s name to cache map" mean? (Issue #1784) Ben Kelly
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Ben Kelly
• Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838) Lola
• Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838) Lola
• Re: [w3c/screen-orientation] Complete self-reviews (#201) Xiaoqian Wu
• Re: [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Yoshisato Yanagisawa
• [w3c/ServiceWorker] Fix: Align Cache API definitions with Storage spec (PR #1789) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] What does "the registration’s storage key’s name to cache map" mean? (Issue #1784) Yoshisato Yanagisawa
• [w3c/ServiceWorker] Revise cache storage lookup using the "obtain a local storage bottle map" algorithm (Issue #1788) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] What does "the registration’s storage key’s name to cache map" mean? (Issue #1784) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] What does "the registration’s storage key’s name to cache map" mean? (Issue #1784) Yoshisato Yanagisawa
• Re: [whatwg/storage] Add an algorithm to get a storage bottle map given a storage key (PR #185) Yoshisato Yanagisawa
• Re: [whatwg/storage] Add an algorithm to get a storage bottle map given a storage key (PR #185) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Clarify cache access in Handle Fetch (PR #1786) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Clarify cache access in Handle Fetch (PR #1786) Yoshisato Yanagisawa

Wednesday, 3 September 2025

• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) Patrick Meenan
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) Patrick Meenan
• Re: [w3c/ServiceWorker] Clarify cache access in Handle Fetch (PR #1786) Monica Chintala
• Re: [WICG/webcomponents] Samsung pass (Issue #1113) Keith Cirkel
• [WICG/webcomponents] Samsung pass (Issue #1113) aliarain00447487666775-ctrl
• [w3c/editing] Nested editing hosts do not need to be wrapped in insertParagraph (Issue #490) Jelle Raaijmakers
• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) Ashish Kumar
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Marcos Cáceres
• Re: [w3c/ServiceWorker] Clarify cache access in Handle Fetch (PR #1786) Yoshisato Yanagisawa
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Marcos Cáceres
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Marcos Cáceres
• Re: [w3c/push-api] Add app badge to Declarative Web Push (PR #402) Marcos Cáceres
• Re: [w3c/manifest] chore: export Installed Web Application Identity (PR #1187) Marcos Cáceres
• Re: [w3c/manifest] chore: export Installed Web Application Identity (PR #1187) Marcos Cáceres
• Re: [w3c/manifest] chore: export Installed Web Application Identity (PR #1187) Copilot

Tuesday, 2 September 2025

• Re: [w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052) Daniel Rubery
• Re: [w3ctag/design-reviews] CSS find-in-page highlight pseudos (Issue #1120) Bramus
• Re: [WICG/webcomponents] Reference Target "phase 2": seeking feedback and use cases (Issue #1111) Tony Ward
• Re: [w3c/manifest] chore: export Installed Web Application Identity (PR #1187) Marcos Cáceres
• [w3c/manifest] chore: export Installed Web Application Identity (PR #1187) Marcos Cáceres
• Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217) Marcos Cáceres
• Re: [w3ctag/design-reviews] Delegation-oriented FedCM (Issue #1039) Martin Thomson
• Re: [w3ctag/design-reviews] Delegation-oriented FedCM (Issue #1039) Martin Thomson
• Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217) Tim Ledbetter
• Re: [whatwg/streams] Meta: move explainers to subdirectory (PR #1355) Domenic Denicola

Monday, 1 September 2025

• [w3ctag/design-reviews] WG Revision: Geolocation (Issue #1144) Xiaoqian Wu
• Re: [w3c/permissions] Add an optional `topLevelOrigin` parameter to the `permissions.setPermission` command (PR #468) jalonthomas
• Re: [w3c/permissions] Add an optional `topLevelOrigin` parameter to the `permissions.setPermission` command (PR #468) jalonthomas
• [whatwg/dom] Method to populated multiple form fields from a single url-encoded string (Issue #1402) Paul Kiddle
• Re: [w3c/permissions] Add an optional `topLevelOrigin` parameter to the `permissions.setPermission` command (PR #468) Mike Taylor
• [whatwg/streams] Meta: move explainers to subdirectory (PR #1355) Mattias Buelens
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) Samuel Williams
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) James Addison
• [w3c/push-api] Missing tasks in parallel steps in Push API (Issue #407) dontcallmedom-bot

Last message date: Thursday, 25 September 2025 14:05:35 UTC