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

Saturday, 31 May 2025

• Re: [whatwg/fetch] New Proposal: Making Fetch Promises work better (i.e. abort-able) with other (e.g. Promise Combinators, Promise Vendor) APIs (Issue #1831) Ifeora Okechukwu
• [whatwg/dom] Make it possible to wrap [parts of] the contents of a <textarea> or <input> in a Range (Issue #1375) DavidJCobb

Friday, 30 May 2025

• Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight for navigations (PR #1785) Alexander Petros
• Re: [w3ctag/design-reviews] Controlled Frame (Issue #1067) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Controlled Frame (Issue #1067) Jeffrey Yasskin
• [w3ctag/design-reviews] ScrollIntoViewOptions container attribute (Issue #1105) Robert Flack
• Re: [w3c/IndexedDB] Return transaction from upgrade a database (PR #458) stelar7
• Re: [w3c/ServiceWorker] Fix: Ensure timingInfo is returned on network fallback if SW static routing API is used (PR #1774) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Fix: Ensure timingInfo is returned on network fallback if SW static routing API is used (PR #1774) Keita Suzuki
• Re: [w3c/ServiceWorker] Fix: Ensure timingInfo is returned on network fallback if SW static routing API is used (PR #1774) Yoshisato Yanagisawa
• [w3c/ServiceWorker] Fix: Ensure timingInfo is returned on network fallback if SW static routing API is used (PR #1774) Yoshisato Yanagisawa
• [w3ctag/design-reviews] [wg/apa] Accessible Platform Architectures Group Charter (Issue #1104) W3C Bot
• Re: [w3c/ServiceWorker] Fix: Correct return type and preserve response timing info (PR #1773) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Fix: Correct return type and preserve response timing info (PR #1773) Keita Suzuki
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) Keita Suzuki
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) Keita Suzuki
• Re: [w3c/ServiceWorker] Fix: Correct return type and preserve response timing info (PR #1773) Yoshisato Yanagisawa
• Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) Keita Suzuki
• Re: [w3c/ServiceWorker] Fix: Correct return type and preserve response timing info (PR #1773) Yoshisato Yanagisawa
• [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832) Keita Suzuki
• [w3c/ServiceWorker] Fix: Correct return type and preserve response timing info (PR #1773) Yoshisato Yanagisawa
• Re: [whatwg/url] Public Suffix API (#528) Danny Colin

Thursday, 29 May 2025

• Re: [w3c/ServiceWorker] Update Handle Fetch to return timing info (PR #1772) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Update Handle Fetch to return timing info (PR #1772) Yoshisato Yanagisawa
• Re: [whatwg/streams] Add URL.createObjectURL(stream) support (#480) pqnet
• Re: [whatwg/url] Public Suffix API (#528) James M Snell
• Re: [whatwg/xhr] For sync XHR consider setting the service-workers mode to "none" to align browsers (Issue #397) Martin Thomson
• Re: [whatwg/url] Public Suffix API (#528) pes10k
• Re: [whatwg/url] Public Suffix API (#528) Jeffrey Yasskin
• Re: [whatwg/url] Public Suffix API (#528) pes10k
• Re: [w3ctag/design-reviews] Permissions Policy reports for iframes (Issue #1050) Jun
• Re: [whatwg/xhr] For sync XHR consider setting the service-workers mode to "none" to align browsers (Issue #397) Anne van Kesteren
• [whatwg/xhr] For sync XHR consider setting the service-workers mode to "none" to align browsers (Issue #397) Andrew Sutherland
• Re: [w3c/manifest] http (Issue #1173) Tawhidsdk
• Re: [w3c/manifest] http (Issue #1173) Tawhidsdk
• [w3c/manifest] http (Issue #1173) Tawhidsdk
• Re: [w3ctag/design-reviews] Renaming the Storage Access handle methods for non-cookie StorageAccessAPI (Issue #1087) Christian Liebel
• Re: [w3ctag/design-reviews] Renaming the Storage Access handle methods for non-cookie StorageAccessAPI (Issue #1087) Christian Liebel
• Re: [whatwg/dom] Missing machinery for associated Event data (Issue #1328) Domenic Denicola
• Re: [w3c/ServiceWorker] Update Handle Fetch to return timing info (PR #1772) Keita Suzuki
• Re: [whatwg/dom] Missing machinery for associated Event data (Issue #1328) Domenic Denicola
• Re: [w3c/ServiceWorker] Update Handle Fetch to return timing info (PR #1772) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Update Handle Fetch to return timing info (PR #1772) Yoshisato Yanagisawa
• Re: [w3ctag/design-reviews] Incremental Font Transfer (Issue #1057) Xiaocheng Hu
• Re: [w3ctag/design-reviews] Incremental Font Transfer (Issue #1057) Xiaocheng Hu
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola

Wednesday, 28 May 2025

• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [whatwg/dom] Consider more name validation loosening (Issue #1373) Joey Arhar
• Re: [w3ctag/design-reviews] Expose contentEncoding in resourceTiming (Issue #1064) Guohui Deng
• Re: [w3ctag/design-reviews] Expose contentEncoding in resourceTiming (Issue #1064) Guohui Deng
• Re: [w3ctag/design-reviews] Expose contentEncoding in resourceTiming (Issue #1064) Guohui Deng
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Marcos Cáceres
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Marcos Cáceres
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Marcos Cáceres
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Marcos Cáceres
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Marcos Cáceres
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Marcos Cáceres
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Marcos Cáceres
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Marcos Cáceres
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Marcos Cáceres
• Re: [w3ctag/design-reviews] Isolated Web Apps (Issue #842) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Isolated Web Apps (Issue #842) Jeffrey Yasskin
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Anne van Kesteren
• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) Lola
• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) Anusha Muley
• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) Ari Chivukula
• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) Lola
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Manu Sporny
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Manu Sporny
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Manu Sporny
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Manu Sporny
• Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Manu Sporny
• [w3ctag/design-reviews] CSS Anchored Fallback Container Queries (Issue #1103) Rune Lillesveen
• Re: [w3c/ServiceWorker] Update Handle Fetch to return timing info (PR #1772) Keita Suzuki
• Re: [w3c/ServiceWorker] Update Handle Fetch to return timing info (PR #1772) Keita Suzuki
• [w3c/ServiceWorker] Update Handle Fetch to return timing info (PR #1772) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102) Jeffrey Yasskin
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Maximum file size that cache should support (Issue #1770) fergald
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki

Tuesday, 27 May 2025

• Re: [w3ctag/design-reviews] WebGPU Compatibility Mode (Issue #1063) Stephen White
• Re: [w3ctag/design-reviews] WebGPU Compatibility Mode (Issue #1063) Stephen White
• [whatwg/fetch] New issue proposal: Making Fetch Promises work better with for (Promise Combinator, AbortController & AbortSignal) APIs (Issue #1831) Ifeora Okechukwu
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [w3c/ServiceWorker] Maximum file size that cache should support (Issue #1770) Eriko Kurimoto

Monday, 26 May 2025

• [whatwg/fetch] [Editorial] Shift SVCB to reference RFC9460. (PR #1830) Mike West
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995) Martin Thomson
• Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995) Martin Thomson
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson

Sunday, 25 May 2025

• Re: [whatwg/dom] A slottable's assigned slot is never reset (Issue #1352) Simon Wülker
• [whatwg/webidl] Intent to use Constants (Issue #1492) Lic Victor Manuel Orozco

Saturday, 24 May 2025

• Re: [w3ctag/design-reviews] `Integrity-Policy` header for scripts (Issue #1048) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] `Integrity-Policy` header for scripts (Issue #1048) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Jeffrey Yasskin
• Re: [w3c/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) Natale Raco
• Re: [w3c/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) Natale Raco
• Re: [whatwg/fetch] Fix markup (PR #1829) Anne van Kesteren
• Re: [whatwg/fetch] Fix markup (PR #1829) Anne van Kesteren

Friday, 23 May 2025

• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) zalee3827
• [whatwg/fetch] Fix markup (PR #1829) Tab Atkins Jr.
• [whatwg/fetch] Integrity-Policy integration (PR #1828) Yoav Weiss
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Anne van Kesteren
• [whatwg/webidl] Expected behavior of SharedArrayBuffer with (BufferSource or DOMString) union type (Issue #1491) Anne van Kesteren
• Re: [w3ctag/design-reviews] Add prefetchCache and prerenderCache to Clear-Site-Data header (Issue #1091) Domenic Denicola
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola
• Re: [w3ctag/design-reviews] Add prefetchCache and prerenderCache to Clear-Site-Data header (Issue #1091) Martin Thomson
• Re: [w3ctag/design-reviews] Add prefetchCache and prerenderCache to Clear-Site-Data header (Issue #1091) Martin Thomson
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Mason Freed

Thursday, 22 May 2025

• [w3ctag/design-reviews] env(preferred-text-scale) (Issue #1101) davidsgrogan
• Re: [whatwg/dom] Define mutation events (#305) Simon Pieters
• Re: [whatwg/dom] Define mutation events (#305) Simon Pieters
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Simon Pieters
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Mason Freed
• Re: [w3c/IndexedDB] Return transaction from upgrade a database (PR #458) Joshua Bell
• Re: [w3ctag/design-reviews] Accessibility conformance Testing (ACT) Rules Format 1.1 (Issue #977) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Accessibility conformance Testing (ACT) Rules Format 1.1 (Issue #977) Jeffrey Yasskin
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [w3c/IndexedDB] Return transaction from upgrade a database (PR #458) Evan Stade
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Anne van Kesteren
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Anne van Kesteren
• Re: [w3ctag/design-reviews] Physical and logical resolution for screen-capture MediaStreamTracks (Issue #1060) Christian Liebel
• Re: [w3ctag/design-reviews] Physical and logical resolution for screen-capture MediaStreamTracks (Issue #1060) Christian Liebel
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Anne van Kesteren
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Anne van Kesteren
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Anne van Kesteren
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Anne van Kesteren
• Re: [w3ctag/design-reviews] Permissions Policy reports for iframes (Issue #1050) Hadley Beeman
• Re: [w3ctag/design-reviews] Private Proof API (Issue #1071) Martin Thomson
• Re: [w3c/IndexedDB] Return transaction from upgrade a database (PR #458) stelar7
• Re: [WICG/webcomponents] Custom self-closing elements (Issue #1104) Anatoli Babenia
• [w3c/IndexedDB] Return transaction from upgrade a database (PR #458) stelar7
• Re: [w3c/ServiceWorker] Update index.bs (PR #1771) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Update index.bs (PR #1771) Yoshisato Yanagisawa
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Anne van Kesteren
• Re: [w3c/ServiceWorker] Update index.bs (PR #1771) Peter Reitinger

Wednesday, 21 May 2025

• Re: [w3ctag/design-reviews] Review request for AriaNotify API (Issue #1075) Jacques Newman
• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) J. S. Choi
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [w3ctag/design-reviews] TAG spec review of Stateless Bounce Tracking Mitigations (Issue #1062) Matthew Tylee Atkinson
• Re: [w3ctag/design-reviews] TAG spec review of Stateless Bounce Tracking Mitigations (Issue #1062) Matthew Tylee Atkinson
• Re: [w3ctag/design-reviews] Incremental Font Transfer (Issue #1057) Chris Lilley
• Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962) Aaron Gustafson
• Re: [w3ctag/design-reviews] Review request for AriaNotify API (Issue #1075) Lola
• Re: [w3ctag/design-reviews] Add an accessibility self-review to TAG design reviews. (PR #1088) Matthew Tylee Atkinson
• Re: [w3ctag/design-reviews] Add an accessibility self-review to TAG design reviews. (PR #1088) Matthew Tylee Atkinson
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) Anne van Kesteren
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) Peter Reitinger
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) Anne van Kesteren
• Re: [w3c/ServiceWorker] Update index.bs (PR #1771) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) Yoshisato Yanagisawa
• [w3c/editing] Canonicalize Whitespace algorithm does not respect the `white-space-collapse` CSS property (Issue #486) Callum Law
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) Kagami Sascha Rosylight
• Re: [whatwg/webidl] Specifications which use "invoke a callback function" should be updated to specify their exception handling behavior. (Issue #1425) Domenic Denicola
• Re: [whatwg/webidl] Specifications which use "invoke a callback function" should be updated to specify their exception handling behavior. (Issue #1425) Domenic Denicola
• Re: [w3c/permissions] Aspects and integration with Permissions Policy (Issue #459) Anne van Kesteren
• Re: [whatwg/dom] Consider more name validation loosening (Issue #1373) Anne van Kesteren
• Re: [w3c/permissions] Aspects and integration with Permissions Policy (Issue #459) Antonio Sartori
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola
• Re: [whatwg/dom] Consider more name validation loosening (Issue #1373) Domenic Denicola
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola
• Re: [w3c/permissions] Aspects and integration with Permissions Policy (Issue #459) Anne van Kesteren
• Re: [w3c/permissions] Aspects and integration with Permissions Policy (Issue #459) Antonio Sartori
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) Anne van Kesteren
• Re: [w3c/permissions] Aspects and integration with Permissions Policy (Issue #459) Anne van Kesteren
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) Peter Reitinger
• Re: [w3c/ServiceWorker] Update index.bs (PR #1771) Peter Reitinger
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [whatwg/dom] Consider more name validation loosening (Issue #1373) Domenic Denicola

Tuesday, 20 May 2025

• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Update index.bs (PR #1771) Yoshisato Yanagisawa
• Re: [w3ctag/design-reviews] Review request for AriaNotify API (Issue #1075) Jacques Newman
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [whatwg/dom] Consider more name validation loosening (Issue #1373) Joey Arhar
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• [w3ctag/design-reviews] Browser Bound Keys for Secure Payment Confirmation (Issue #1097) Slobodan Pejić
• Re: [whatwg/fetch] Secure cookies should be permitted on secure requests, not just where there is a `https` scheme (Issue #1827) bvandersloot-mozilla
• Re: [whatwg/dom] Consider more name validation loosening (Issue #1373) C. Scott Ananian
• Re: [whatwg/fetch] Secure cookies should be permitted on secure requests, not just where there is a `https` scheme (Issue #1827) Anne van Kesteren
• Re: [whatwg/fetch] Secure cookies should be permitted on secure requests, not just where there is a `https` scheme (Issue #1827) bvandersloot-mozilla
• Re: [w3ctag/design-reviews] Web Audio API: RenderCapacity API (Issue #843) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Web Audio API: RenderCapacity API (Issue #843) Jeffrey Yasskin
• Re: [whatwg/fetch] Secure cookies should be permitted on secure requests, not just where there is a `https` scheme (Issue #1827) Mike West
• Re: [whatwg/fetch] Secure cookies should be permitted on secure requests, not just where there is a `https` scheme (Issue #1827) Johann Hofmann
• [w3c/ServiceWorker] Update index.bs (PR #1771) Peter Reitinger
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) Anne van Kesteren
• Re: [w3ctag/design-reviews] Web Audio API: RenderCapacity API (Issue #843) Paul Adenot
• Re: [w3ctag/design-reviews] CSS corner-shaping (Issue #1090) Xiaocheng Hu
• Re: [w3ctag/design-reviews] CSS corner-shaping (Issue #1090) Xiaocheng Hu
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) Anne van Kesteren
• Re: [whatwg/webidl] Fix "async iterable" being a single token (PR #1489) Anne van Kesteren
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Anne van Kesteren
• Re: [whatwg/storage] Maximum file size that storage should support (Issue #181) Eriko Kurimoto
• Re: [w3c/ServiceWorker] Maximum file size that cache should support (Issue #1770) Eriko Kurimoto
• [whatwg/storage] Maximum file size that storage should support (Issue #181) Eriko Kurimoto
• Re: [whatwg/fetch] Secure cookies should be permitted on secure requests, not just where there is a `https` scheme (Issue #1827) Mike West
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3ctag/design-reviews] Web Audio API: RenderCapacity API (Issue #843) Jeffrey Yasskin
• Re: [whatwg/fetch] Secure cookies should be permitted on secure requests, not just where there is a `https` scheme (Issue #1827) David Benjamin
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola
• Re: [whatwg/dom] Consider more name validation loosening (Issue #1373) Domenic Denicola
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Jeffrey Yasskin
• Re: [whatwg/fetch] Secure cookies should be permitted on secure requests, not just where there is a `https` scheme (Issue #1827) Johann Hofmann

Monday, 19 May 2025

• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Mathias Bynens
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [w3c/FileAPI] Proposal: `Blob.from()` for creating virtual Blobs with custom backing storage (Issue #209) Jimmy Wärting
• [whatwg/webidl] The new async iterable type broke LL(1) rule (Issue #1490) Kagami Sascha Rosylight
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [whatwg/webidl] Fix "async iterable" being a single token (PR #1489) Kagami Sascha Rosylight
• [whatwg/webidl] Fix "async iterable" being a single token (PR #1489) Kagami Sascha Rosylight
• Re: [whatwg/webidl] Add disposer and async_disposer (PR #1488) James M Snell
• Re: [whatwg/webidl] Add disposer and async_disposer (PR #1488) James M Snell
• Re: [whatwg/webidl] Add disposer and async_disposer (PR #1488) James M Snell
• Re: [whatwg/webidl] Add disposer and async_disposer (PR #1488) James M Snell
• Re: [whatwg/webidl] Add disposer and async_disposer (PR #1488) James M Snell
• Re: [whatwg/webidl] Add a `disposer` keyword for disposal methods (Issue #1459) James M Snell
• Re: [whatwg/webidl] Add disposer and async_disposer (PR #1488) James M Snell
• [whatwg/webidl] Add disposer and async_disposer (PR #1488) James M Snell
• Re: [whatwg/dom] Consider more name validation loosening (Issue #1373) C. Scott Ananian
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [w3c/FileAPI] Proposal: `Blob.from()` for creating virtual Blobs with custom backing storage (Issue #209) Andrew Sutherland
• [w3ctag/design-reviews] WebRTC Encoded Transform Audio Level (Issue #1096) guidou
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• Re: [whatwg/webidl] Add a `disposer` keyword for disposal methods (Issue #1459) Claudia Meadows
• Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) Mason Freed
• Re: [w3c/ServiceWorker] Maximum file size that cache should support (Issue #1770) Andrew Sutherland
• Re: [w3ctag/design-reviews] IP Protection (in Incognito mode) (Issue #1083) Mike Taylor
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) Anne van Kesteren
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• Re: [whatwg/dom] Consider more name validation loosening (Issue #1373) Joey Arhar
• Re: [whatwg/webidl] Add a `disposer` keyword for disposal methods (Issue #1459) James M Snell
• Re: [whatwg/dom] Candidates for AbstractRange (#591) Simon Pieters
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) Anne van Kesteren
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) Anne van Kesteren
• [w3c/FileAPI] Proposal: `Blob.from()` for creating virtual Blobs with custom backing storage (Issue #209) Jimmy Wärting
• [whatwg/fetch] Secure cookies should be permitted on secure requests, not just where there is a `https` scheme (Issue #1827) bvandersloot-mozilla
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• Re: [w3c/ServiceWorker] Maximum file size that cache should support (Issue #1770) Domenic Denicola
• Re: [w3c/ServiceWorker] Maximum file size that cache should support (Issue #1770) Anne van Kesteren
• [whatwg/fetch] Layered Cookies integration (Issue #1826) Anne van Kesteren
• Re: [w3c/FileAPI] Support using AbortController with FileAPI (#159) Jimmy Wärting
• Re: [w3c/ServiceWorker] Maximum file size that cache should support (Issue #1770) Yoshisato Yanagisawa
• Re: [whatwg/dom] Trusted types attributes (PR #1268) Anne van Kesteren
• [whatwg/dom] Consider more name validation loosening (Issue #1373) Domenic Denicola
• Re: [whatwg/dom] Add part attribute and note that part and exportparts are superglobal (PR #1372) Anne van Kesteren
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Anne van Kesteren
• Re: [whatwg/webidl] Add a `disposer` keyword for disposal methods (Issue #1459) Anne van Kesteren
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola
• Re: [whatwg/webidl] Add a `disposer` keyword for disposal methods (Issue #1459) James M Snell
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson

Sunday, 18 May 2025

• Re: [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Jeffrey Yasskin
• [w3ctag/design-reviews] Canvas Text Metrics for Editing, Art and Design (Issue #1095) Stephen Chenney
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) Nate Stringham
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Joe Pea
• [whatwg/dom] Add part attribute and note that part and exportparts are superglobal (PR #1372) Daniel Ethridge
• Re: [whatwg/streams] TransformStream byte streams (#616) Jimmy Wärting

Saturday, 17 May 2025

• Re: [w3ctag/design-reviews] Horizontal Review of Decentralized Identifiers v1.1 (Issue #1086) Manu Sporny
• Re: [whatwg/fetch] Discussion: the term for non-preflighted request ("simple request") (Issue #1824) Uku Sõrmus
• Re: [whatwg/fetch] Discussion: the term for non-preflighted request ("simple request") (Issue #1824) jub0bs
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) Alex Gustafsson
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar

Friday, 16 May 2025

• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) bvandersloot-mozilla
• Re: [w3ctag/design-reviews] Tidy up; add Focus labels by default (PR #953) Daniel Appelquist
• Re: [w3ctag/design-reviews] Tidy up; add Focus labels by default (PR #953) Daniel Appelquist
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) Anne van Kesteren
• Re: [whatwg/webidl] Add [AllowImmutable] extended attribute for immutable array buffers and views (Issue #1487) Anne van Kesteren
• Re: [w3ctag/design-reviews] Horizontal Review of Decentralized Identifiers v1.1 (Issue #1086) Sarven Capadisli
• [whatwg/webidl] Add [AllowImmutable] extended attribute for immutable array buffers and views (Issue #1487) André Bargull
• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) Rafael Kraut
• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) Anne van Kesteren
• Re: [whatwg/fetch] Discussion: the term for non-preflighted request ("simple request") (Issue #1824) Uku Sõrmus
• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) Anne van Kesteren
• Re: [whatwg/fetch] Integrate with new draft cookie spec (draft-annevk-johannhof-httpbis-cookies/00+ε) (PR #1807) Anne van Kesteren
• Re: [WICG/webcomponents] Custom self-closing elements (Issue #1104) kik
• Re: [WICG/webcomponents] Custom self-closing elements (Issue #1104) Anne van Kesteren
• [w3c/ServiceWorker] Maximum file size that cache should support (Issue #1770) Eriko Kurimoto
• Re: [whatwg/fetch] Discussion: the term for non-preflighted request ("simple request") (Issue #1824) Elar Lang
• Re: [whatwg/fetch] Discussion: the term for non-preflighted request ("simple request") (Issue #1824) jub0bs
• Re: [WICG/webcomponents] Custom self-closing elements (Issue #1104) Anatoli Babenia
• Re: [whatwg/fetch] Discussion: the term for non-preflighted request ("simple request") (Issue #1824) Anne van Kesteren
• Re: [whatwg/fetch] Discussion: the term for non-preflighted request ("simple request") (Issue #1824) sideshowbarker
• Re: [WICG/webcomponents] Custom self-closing elements (Issue #1104) Anne van Kesteren
• Re: [WICG/webcomponents] Custom self-closing elements (Issue #1104) Anne van Kesteren
• Re: [whatwg/fetch] Discussion: the term for non-preflighted request ("simple request") (Issue #1824) jub0bs
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) Anatoli Babenia
• [WICG/webcomponents] Custom self-closing elements (Issue #1104) Anatoli Babenia
• Re: [whatwg/fetch] Discussion: the term for non-preflighted request ("simple request") (Issue #1824) Anne van Kesteren
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Anne van Kesteren
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) kik
• Re: [w3c/clipboard-apis] Fix `clipboard.readText()` algorithm (PR #238) Anne van Kesteren
• Re: [w3c/clipboard-apis] chore: fix markup errors for the automatic publication (PR #234) Anne van Kesteren
• Re: [w3c/clipboard-apis] chore: fix markup errors for the automatic publication (PR #234) Anne van Kesteren
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Anne van Kesteren
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Domenic Denicola
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) Russell Beswick

Thursday, 15 May 2025

• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) David Alsh
• Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) Dan Clark
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) Joshua Bell
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) stelar7
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) Steven Becker
• Re: [w3c/IndexedDB] Clarify the direction predicates for cursor iteration (PR #457) Joshua Bell
• Re: [w3c/IndexedDB] Clarify the direction predicates for cursor iteration (PR #457) Joshua Bell
• Re: [w3c/IndexedDB] How to read direction predicates in iterate a cursor? (Issue #450) Joshua Bell
• Re: [w3c/IndexedDB] Clarify the direction predicates for cursor iteration (PR #457) Joshua Bell
• Re: [w3c/IndexedDB] Clarify the direction predicates for cursor iteration (PR #457) Joshua Bell
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Daniel Herr
• Re: [w3c/IndexedDB] Clarify the direction predicates for cursor iteration (PR #457) Joshua Bell
• Re: [w3c/IndexedDB] Add missing parallel step and define queue a database task (PR #456) Joshua Bell
• Re: [w3c/IndexedDB] Missing tasks in parallel steps in Indexed Database API 3.0 (Issue #421) Joshua Bell
• Re: [w3c/IndexedDB] Add missing parallel step and define queue a database task (PR #456) Joshua Bell
• Re: [w3c/IndexedDB] Add missing parallel step and define queue a database task (PR #456) Joshua Bell
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Daniel Herr
• Re: [w3c/clipboard-apis] Fix `clipboard.readText()` algorithm (PR #238) Edgar Chen
• Re: [w3c/clipboard-apis] Fix `clipboard.readText()` algorithm (PR #238) Edgar Chen
• Re: [w3c/clipboard-apis] Fix `clipboard.readText()` algorithm (PR #238) Edgar Chen
• Re: [w3c/clipboard-apis] chore: fix markup errors for the automatic publication (PR #234) Edgar Chen
• Re: [w3ctag/design-reviews] WebGPU Compatibility Mode (Issue #1063) Stephen White
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) kik
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) Anatoli Babenia
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Daniel Murphy
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) Andy Earnshaw
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) Balu M
• Re: [w3ctag/design-reviews] Add an accessibility self-review to TAG design reviews. (PR #1088) Nigel Megitt
• Re: [w3ctag/design-reviews] Add an accessibility self-review to TAG design reviews. (PR #1088) Jeffrey Yasskin
• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) Justin Fagnani
• Re: [w3ctag/design-reviews] [wg/media] Media Working Group Charter (Issue #1082) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] [wg/media] Media Working Group Charter (Issue #1082) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Horizontal Review of Decentralized Identifiers v1.1 (Issue #1086) Sarven Capadisli
• Re: [w3ctag/design-reviews] Horizontal Review of Decentralized Identifiers v1.1 (Issue #1086) Sarven Capadisli
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Ben Francis
• [whatwg/fetch] Discussion: the term for non-preflighted request ("simple request") (Issue #1824) Elar Lang
• Re: [w3ctag/design-reviews] IP Protection (in Incognito mode) (Issue #1083) Mike Taylor
• Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) Xiaocheng Hu
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Ben Francis
• Re: [w3ctag/design-reviews] Add an accessibility self-review to TAG design reviews. (PR #1088) Martin Thomson
• Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058) Xiaocheng Hu
• Re: [w3ctag/design-reviews] TAG review for making app updates more predictable (Issue #1076) Christian Liebel
• Re: [w3ctag/design-reviews] TAG review for making app updates more predictable (Issue #1076) Christian Liebel
• [w3c/IndexedDB] Clarify the direction predicates for cursor iteration (PR #457) stelar7
• [w3ctag/design-reviews] Device-Bound Session Credentials Analysis (PR #1094) Martin Thomson
• Re: [w3ctag/design-reviews] IP Protection (in Incognito mode) (Issue #1083) Hadley Beeman
• Re: [w3ctag/design-reviews] Add an accessibility self-review to TAG design reviews. (PR #1088) Nigel Megitt
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Anne van Kesteren
• Re: [w3c/IndexedDB] Add missing parallel step and define queue a database task (PR #456) stelar7
• Re: [w3c/IndexedDB] Add missing parallel step and define queue a database task (PR #456) stelar7
• Re: [whatwg/fetch] Handle request's window when from browser UI (PR #1821) Domenic Denicola
• Re: [whatwg/fetch] Improve "populate request from client" for null client cases (PR #1820) Domenic Denicola
• Re: [whatwg/fetch] Handle request's window when from browser UI (PR #1821) Domenic Denicola
• Re: [whatwg/fetch] Improve "populate request from client" for null client cases (PR #1820) Domenic Denicola
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Domenic Denicola
• Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849) Joey Arhar

Wednesday, 14 May 2025

• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) Joey Arhar
• Re: [w3c/IndexedDB] Add missing parallel step and define queue a database task (PR #456) Joshua Bell
• Re: [w3c/IndexedDB] Add missing parallel step and define queue a database task (PR #456) stelar7
• Re: [w3c/IndexedDB] Add missing parallel step and define queue a database task (PR #456) Joshua Bell
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) Mitar
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Raad Altaie
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Raad Altaie
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) Patrick Meenan
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) Mitar
• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) RobertMPop
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Anne van Kesteren
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Anne van Kesteren
• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) cepm-nate
• Re: [whatwg/fullscreen] Spec Bug in `exitFullscreen()` (Issue #248) Simon Farre
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) Patrick Meenan
• [whatwg/fullscreen] Spec Bug in `exitFullscreen()` (Issue #248) Simon Farre
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) Matt Menke
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) Patrick Meenan
• Re: [w3c/IndexedDB] Add missing parallel step and define queue a database task (PR #456) stelar7
• [w3c/IndexedDB] Add missing parallel step and define queue a database task (PR #456) stelar7
• Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849) Joey Arhar
• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) ExReVe
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) stelar7
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• [w3ctag/design-reviews] Prompt API (Issue #1093) Domenic Denicola
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849) Domenic Denicola
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki

Tuesday, 13 May 2025

• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Daniel Herr
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Daniel Murphy
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Daniel Murphy
• Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849) C. Scott Ananian
• Re: [whatwg/dom] matchMedia-like API for element matches (Issue #1225) Benoît Rouleau
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) Daniel Herr
• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) Justin Fagnani
• Re: [w3ctag/design-reviews] [SVG 2.0] Allow `use` to reference an external document's root element by omitting the fragment (Issue #1081) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] [SVG 2.0] Allow `use` to reference an external document's root element by omitting the fragment (Issue #1081) Jeffrey Yasskin
• Re: [whatwg/dom] A way for createAttribute() to bypass XML Name validation in HTML documents (#769) C. Scott Ananian
• Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849) C. Scott Ananian
• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) Christophe Coevoet
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Domenic Denicola
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Domenic Denicola
• Re: [w3ctag/design-reviews] Accessibility conformance Testing (ACT) Rules Format 1.1 (Issue #977) Wilco Fiers
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Noam Rosenthal
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Domenic Denicola
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Domenic Denicola
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Domenic Denicola
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Domenic Denicola
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Anne van Kesteren
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Anne van Kesteren
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Anne van Kesteren
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Anne van Kesteren
• Re: [whatwg/dom] What "DOM" stands for, "Document Object Model", was never explicitly mentioned (Issue #1371) Anne van Kesteren
• Re: [whatwg/dom] What "DOM" stands for, "Document Object Model", was never explicitly mentioned (Issue #1371) Anne van Kesteren
• Re: [w3ctag/design-reviews] confidence reporting for PerformanceNavigationTiming (Issue #878) Martin Thomson
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Domenic Denicola
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Domenic Denicola
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Domenic Denicola
• Re: [w3c/gamepad] Add a model section (PR #220) Gabriel Brito
• [whatwg/dom] What "DOM" stands for, "Document Object Model", was never explicitly mentioned (Issue #1371) Thomas Chan

Monday, 12 May 2025

• [w3ctag/design-reviews] Web Authentication Immediate Mediation (Issue #1092) Ken Buchanan
• [w3ctag/design-reviews] Add prefetchCache and prerenderCache to Clear-Site-Data header (Issue #1091) Steven
• [w3ctag/design-reviews] CSS corner-shaping (Issue #1090) Noam Rosenthal
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [w3c/IndexedDB] Add descending order for getAll() and getAllKeys() (#130) Andrew Sutherland
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [whatwg/fetch] Deferred fetching (PR #1647) Noam Rosenthal
• Re: [w3c/permissions] Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (PR #458) Aaron Selya
• Re: [w3c/clipboard-apis] Fix `clipboard.readText()` algorithm (PR #238) Anne van Kesteren
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) kik
• Re: [whatwg/url] Editorial: Use code unit less than algorithm for URLSearchParams sort (PR #872) Anne van Kesteren
• Re: [whatwg/url] Editorial: Use code unit less than algorithm for URLSearchParams sort (PR #872) Anne van Kesteren
• Re: [whatwg/url] Editorial: Use code unit less than algorithm for URLSearchParams sort (PR #872) Anne van Kesteren
• Re: [whatwg/url] Editorial: Use code unit less than algorithm for URLSearchParams sort (PR #872) Anne van Kesteren
• Re: [whatwg/url] Editorial: Use code unit less than algorithm for URLSearchParams sort (PR #872) Shannon Booth
• Re: [whatwg/url] Editorial: Use code unit less than algorithm for URLSearchParams sort (PR #872) Anne van Kesteren
• Re: [whatwg/url] Editorial: Use code unit less than algorithm for URLSearchParams sort (PR #872) Shannon Booth
• Re: [whatwg/url] Editorial: Use code unit less than algorithm for URLSearchParams sort (PR #872) Shannon Booth
• Re: [whatwg/url] Editorial: Use code unit less than algorithm for URLSearchParams sort (PR #872) Anne van Kesteren
• [whatwg/url] Editorial: Use code unit less than algorithm for URLSearchParams sort (PR #872) Shannon Booth

Sunday, 11 May 2025

• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) Yoshisato Yanagisawa
• Re: [whatwg/fetch] Ensure that browsers never send a malformed request except by explicit request from scripts (Issue #1822) Anne van Kesteren

Saturday, 10 May 2025

• Re: [whatwg/fetch] Ensure that browsers never send a malformed request except by explicit request from scripts (Issue #1822) Demi Marie Obenour

Friday, 9 May 2025

• Re: [whatwg/fetch] Ensure that browsers never send a malformed request except by explicit request from scripts (Issue #1822) Ashfitgoc
• Re: [whatwg/fetch] Ensure that browsers never send a malformed request except by explicit request from scripts (Issue #1822) Anne van Kesteren
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Anne van Kesteren
• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) Ben Kelly
• Re: [whatwg/fetch] Ensure that browsers never send a malformed request except by explicit request from scripts (Issue #1822) Ashfitgoc
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Valery Zinchenko
• [w3ctag/design-reviews] Extended lifetime shared workers (Issue #1089) Domenic Denicola
• [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) Domenic Denicola
• Re: [w3c/editing] Behavior of insert* commands for contenteditable=plaintext-only (Issue #419) Masayuki Nakano
• Re: [w3c/editing] Behavior of insert* commands for contenteditable=plaintext-only (Issue #419) Masayuki Nakano
• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) Yoshisato Yanagisawa

Thursday, 8 May 2025

• [w3ctag/design-reviews] Add an accessibility self-review to TAG design reviews. (PR #1088) Jeffrey Yasskin
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) Sneha Agarwal
• Re: [w3c/gamepad] Add a model section (PR #220) Matt Reynolds
• Re: [w3ctag/design-reviews] Incremental Font Transfer (Issue #1057) Chris Lilley
• Re: [w3c/editing] Behavior of insert* commands for contenteditable=plaintext-only (Issue #419) Simon Pieters
• [w3ctag/design-reviews] Renaming the Storage Access handle methods for non-cookie StorageAccessAPI (Issue #1087) Anusha Muley
• [w3c/editing] 2025 May meeting cancelled (Issue #485) Johannes Wilm
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3ctag/design-reviews] Physical and logical resolution for screen-capture MediaStreamTracks (Issue #1060) guidou
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Yoshisato Yanagisawa
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Shiba
• Re: [w3ctag/design-reviews] Incremental Font Transfer (Issue #1057) Xiaocheng Hu
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Andrea Giammarchi
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Valery Zinchenko
• Re: [whatwg/xhr] Wrong upload progress when network interrupts (Issue #361) SHIVAM GAJANAN NIMBALKAR
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [WICG/webcomponents] Reference Target: How should we treat invalid reference targets for relations set via Element IDL attributes? (Issue #1089) Dan Clark

Wednesday, 7 May 2025

• [whatwg/fetch] Ensure that browsers never send a malformed request except by explicit request from scripts (Issue #1822) Demi Marie Obenour
• Re: [w3c/IndexedDB] Add descending order for getAll() and getAllKeys() (#130) Evan Stade
• Re: [w3ctag/design-reviews] Incremental Font Transfer (Issue #1057) Chris Lilley
• Re: [w3ctag/design-reviews] TAG review for making app updates more predictable, `update_token` (Issue #1076) Dibyajyoti Pal
• Re: [w3ctag/design-reviews] Incremental Font Transfer (Issue #1057) Garret Rieger
• Re: [w3ctag/design-reviews] Container Timing API (Issue #1034) Daniel Appelquist
• Re: [w3ctag/design-reviews] Container Timing API (Issue #1034) Daniel Appelquist
• Re: [whatwg/dom] Candidates for AbstractRange (#591) Emilio Cobos Álvarez
• Re: [w3c/permissions] WebDriver: Should Set Permission apply to future browsing contexts? (Issue #437) Alex Rudenko
• Re: [w3c/permissions] WebDriver: Should Set Permission apply to future browsing contexts? (Issue #437) Alexandra Borovova
• Re: [w3ctag/design-reviews] Physical and logical resolution for screen-capture MediaStreamTracks (Issue #1060) Christian Liebel
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Shiba
• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) Valentin Gosu
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Valery Zinchenko
• Re: [w3ctag/design-reviews] Incremental Font Transfer (Issue #1057) Xiaocheng Hu
• Re: [w3c/screen-orientation] Should pending promise be abort if document isn't top-level? (Issue #257) Makoto Kato
• Re: [w3c/gamepad] Rewrite the spec with references to the Model section (PR #222) Maksim Sadym
• Re: [w3c/gamepad] Rewrite the spec with references to the Model section (PR #222) Maksim Sadym
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• [w3c/screen-orientation] Should pending promise be abort if document isn't top-level? (Issue #257) Makoto Kato
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Andrea Giammarchi
• [w3c/ServiceWorker] Add new fields and getter steps for static routing resource timing (PR #1769) Keita Suzuki
• Re: [w3c/ServiceWorker] Update handle fetch algorithm step to consider null of source (PR #1768) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Update handle fetch algorithm step to consider null of source (PR #1768) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Update handle fetch algorithm step to consider null of source (PR #1768) Keita Suzuki
• Re: [w3c/ServiceWorker] Update handle fetch algorithm step to consider null of source (PR #1768) Keita Suzuki
• Re: [w3c/ServiceWorker] Update handle fetch algorithm step to consider null of source (PR #1768) Yoshisato Yanagisawa
• Re: [w3c/ServiceWorker] Update handle fetch algorithm step to consider null of source (PR #1768) Keita Suzuki
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Robbie Speed
• Re: [w3c/uievents] [Proposal] Add "Zoom" event (#31) Gee Law
• Re: [w3c/IndexedDB] Add descending order for getAll() and getAllKeys() (#130) Nolan Lawson
• [w3c/ServiceWorker] Update handle fetch algorithm step to consider null of source (PR #1768) Keita Suzuki
• Re: [w3c/clipboard-apis] Clarifying the Error Types for clipboard APIs (Issue #235) Karl Dubost
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Ryosuke Niwa
• Re: [whatwg/url] A '@' character in the host part of file URLs (Issue #805) Jan Martin

Tuesday, 6 May 2025

• Re: [whatwg/dom] Add reference target to shadow root (PR #1353) Dan Clark
• Re: [whatwg/dom] Add reference target to shadow root (PR #1353) Dan Clark
• Re: [whatwg/dom] Add reference target to shadow root (PR #1353) Dan Clark
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Robbie Speed
• Re: [w3c/IndexedDB] Add descending order for getAll() and getAllKeys() (#130) Steven Becker
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Ryosuke Niwa
• Re: [w3ctag/design-reviews] Scoped Custom Element Registries (Issue #1070) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Scoped Custom Element Registries (Issue #1070) Jeffrey Yasskin
• Re: [w3c/clipboard-apis] Clarifying the Error Types for clipboard APIs (Issue #235) Edgar Chen
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Anne van Kesteren
• Re: [w3c/clipboard-apis] Questions about implementing `clipboard.write` (Issue #237) Tim Flynn
• Re: [w3c/clipboard-apis] Clarifying `clipboard.readText()` behaviour (Issue #236) Tim Flynn
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Robbie Speed
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Valery Zinchenko
• Re: [w3c/clipboard-apis] Fix `clipboard.readText()` algorithm (PR #238) Edgar Chen
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Andrea Giammarchi
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Valery Zinchenko
• Re: [w3ctag/design-reviews] Expose contentEncoding in resourceTiming (Issue #1064) Martin Thomson
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) Jeffrey Yasskin
• Re: [w3ctag/design-reviews] Column wrapping for multicol (Issue #1073) Xiaocheng Hu

Monday, 5 May 2025

• Re: [w3c/IndexedDB] asynchronously execute a request source object confusion (Issue #445) Joshua Bell
• Re: [w3c/IndexedDB] Add handle to cursor to avoid exposing internal state to script (PR #455) Joshua Bell
• Re: [w3c/IndexedDB] Add handle to cursor to avoid exposing internal state to script (PR #455) Joshua Bell
• Re: [w3c/IndexedDB] Add handle to cursor to avoid exposing internal state to script (PR #455) Steven Becker
• Re: [w3c/IndexedDB] Add handle to cursor to avoid exposing internal state to script (PR #455) Steven Becker
• Re: [w3c/IndexedDB] Add handle to cursor to avoid exposing internal state to script (PR #455) Steven Becker
• Re: [w3c/IndexedDB] Add handle to cursor to avoid exposing internal state to script (PR #455) Steven Becker
• Re: [w3c/clipboard-apis] Questions about implementing `clipboard.write` (Issue #237) Edgar Chen
• [w3c/clipboard-apis] Fix `clipboard.readText()` algorithm (PR #238) Edgar Chen
• Re: [w3c/IndexedDB] Add handle to cursor to avoid exposing internal state to script (PR #455) Joshua Bell
• [w3c/IndexedDB] Add handle to cursor to avoid exposing internal state to script (PR #455) Steven Becker
• Re: [w3c/clipboard-apis] Clarifying `clipboard.readText()` behaviour (Issue #236) Edgar Chen
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Robbie Speed
• Re: [w3c/clipboard-apis] Clarifying `clipboard.readText()` behaviour (Issue #236) Gae24
• Re: [w3c/clipboard-apis] Clarifying `clipboard.readText()` behaviour (Issue #236) Edgar Chen
• Re: [w3c/clipboard-apis] Clarifying `clipboard.readText()` behaviour (Issue #236) Edgar Chen
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796) Guohui Deng
• Re: [whatwg/fetch] Editorial: Add guidelines for external specs about CORS, cross-origin isolation and TAO (PR #1806) Noam Rosenthal
• Re: [w3c/manifest] Example suggests that `icons` `sizes` mean a minimum size, but normative text doesn't support that (#925) Christian Liebel
• Re: [w3c/manifest] Editorial: rephrase multiple icon example (PR #1170) Christian Liebel
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Andrea Giammarchi
• [w3ctag/design-reviews] Horizontal Review of Decentralized Identifiers v1.1 (Issue #1086) Manu Sporny

Sunday, 4 May 2025

• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) Robbie Speed
• Re: [whatwg/webidl] Create Ah ny (PR #1486) Kagami Sascha Rosylight
• [whatwg/webidl] Create Ah ny (PR #1486) Explainer8888
• Re: [WICG/webcomponents] Simplified custom element definition (Issue #1064) Claudia Meadows

Friday, 2 May 2025

• Re: [w3c/gamepad] Haptic effect "trigger-rumble" leftTrigger/rightTrigger are flipped [MacOS Chrome 135.0.7049.115] (Issue #223) Reece Como
• Re: [w3c/gamepad] Haptic effect "trigger-rumble" leftTrigger/rightTrigger are flipped [MacOS Chrome 135.0.7049.115] (Issue #223) Gabriel Brito
• Re: [w3c/gamepad] Haptic effect "trigger-rumble" leftTrigger/rightTrigger are flipped [MacOS Chrome 135.0.7049.115] (Issue #223) Gabriel Brito
• Re: [w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052) Arnar Birgisson
• Re: [w3c/IndexedDB] Spec mostly doesn't mention blob expectations (Issue #454) Marijn Kruisselbrink
• [w3c/IndexedDB] Spec mostly doesn't mention blob expectations (Issue #454) Evan Stade
• Re: [w3c/IndexedDB] How to read direction predicates in iterate a cursor? (Issue #450) Joshua Bell
• Re: [w3ctag/design-reviews] Early Design Review for Device Bound Session Credentials (Issue #1052) Arnar Birgisson
• Re: [whatwg/fetch] Handle request's window when from browser UI (PR #1821) Emma Zühlcke
• Re: [whatwg/fetch] Improve "populate request from client" for null client cases (PR #1820) Anne van Kesteren
• Re: [whatwg/fetch] Handle request's window when from browser UI (PR #1821) Anne van Kesteren
• Re: [whatwg/fetch] Handle request's window when from browser UI (PR #1821) Valentin Gosu
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) Anne van Kesteren
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) Anne van Kesteren
• Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818) Anne van Kesteren
• Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171) Ben Francis

Thursday, 1 May 2025

• [w3c/gamepad] Haptic effect "trigger-rumble" leftTrigger/rightTrigger are flipped [MacOS Chrome 135.0.7049.115] (Issue #223) Reece Como
• Re: [w3c/manifest] We should add a character limit to `name` and `short_name` (Issue #1070) Aaron Gustafson
• Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171) Daniel Murphy
• Re: [w3c/manifest] We should add a character limit to `name` and `short_name` (Issue #1070) Daniel Murphy
• Re: [w3c/manifest] Unbind computed id from start_url (Issue #1148) Daniel Murphy
• Re: [w3c/manifest] Editorial: rephrase multiple icon example (PR #1170) Daniel Murphy
• Re: [w3c/IndexedDB] Possible logic inversion in `iterate a cursor` (Issue #452) Joshua Bell
• Re: [w3c/IndexedDB] Correct record value serialization in cursor iteration (PR #453) Joshua Bell
• Re: [w3c/IndexedDB] Correct record value serialization in cursor iteration (PR #453) Joshua Bell
• Re: [w3c/IndexedDB] Correct record value serialization in cursor iteration (PR #453) Joshua Bell
• Re: [w3c/IndexedDB] How to read direction predicates in iterate a cursor? (Issue #450) Joshua Bell
• [w3c/clipboard-apis] Questions about implementing `clipboard.write` (Issue #237) Tim Flynn
• Re: [w3c/IndexedDB] How to read direction predicates in iterate a cursor? (Issue #450) Steven Becker
• Re: [w3c/IndexedDB] Correct record value serialization in cursor iteration (PR #453) Steven Becker
• [w3c/IndexedDB] Correct record value serialization in cursor iteration (PR #453) Steven Becker
• Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038) Evan Liu
• Re: [w3c/clipboard-apis] Clarifying `clipboard.readText()` behaviour (Issue #236) Gae24
• Re: [w3c/clipboard-apis] Clarifying `clipboard.readText()` behaviour (Issue #236) Tim Flynn
• Re: [whatwg/fetch] Accept headers in spec cause confusion (#274) Moonchild
• Re: [w3ctag/design-reviews] Column wrapping for multicol (Issue #1073) Daniel Appelquist
• Re: [w3ctag/design-reviews] Expose contentEncoding in resourceTiming (Issue #1064) Daniel Appelquist
• Re: [w3ctag/design-reviews] WebGPU Compatibility Mode (Issue #1063) Matthew Tylee Atkinson
• Re: [whatwg/fetch] Improve "populate request from client" for null client cases (PR #1820) Domenic Denicola
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) Valery Zinchenko
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) Anne van Kesteren
• Re: [w3c/ServiceWorker] The return value for update() is wrong in WebIDL (#1472) Anne van Kesteren
• Re: [whatwg/fetch] Handle request's window when from browser UI (PR #1821) Domenic Denicola
• Re: [w3c/ServiceWorker] Correct ServiceWorkerRegistration Web IDL (PR #1767) Anne van Kesteren
• Re: [w3c/ServiceWorker] Correct ServiceWorkerRegistration Web IDL (PR #1767) Anne van Kesteren
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) Valery Zinchenko
• Re: [whatwg/fetch] Handle request's window when from browser UI (PR #1821) Domenic Denicola
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) Frederik Wessberg
• Re: [w3c/ServiceWorker] Correct ServiceWorkerRegistration Web IDL (PR #1767) Yoshisato Yanagisawa
• [w3c/ServiceWorker] Correct ServiceWorkerRegistration Web IDL (PR #1767) Yoshisato Yanagisawa
• Re: [w3c/editing] Behavior of insert* commands for contenteditable=plaintext-only (Issue #419) TAMURA, Kent
• Re: [w3ctag/design-reviews] Reduce Accept-Language (Issue #1078) Mike Taylor
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) James Diacono

Last message date: Saturday, 31 May 2025 20:43:18 UTC