Re: [whatwg/fetch] Allow `new Response` with 101 status code (Issue #1759)
[whatwg/webidl] Reconsider advice to leave dictionary members optional when dictionary is used solely as a return type (Issue #1567)
[w3c/clipboard-apis] Clipboarding and Multipart MIME (Issue #247)
[w3ctag/design-reviews] Other Spec Review: Scoped View Transitions (Issue #1188)
[whatwg/webidl] Support syntax for specifying that an optional record<K, V> has a default value of an empty record<K, V> (Issue #1566)
- Re: [whatwg/webidl] Support syntax for specifying that an optional record<K, V> has a default value of an empty record<K, V> (Issue #1566)
- Re: [whatwg/webidl] Support syntax for specifying that an optional record<K, V> has a default value of an empty record<K, V> (Issue #1566)
- Re: [whatwg/webidl] Support syntax for specifying that an optional record<K, V> has a default value of an empty record<K, V> (Issue #1566)
- Re: [whatwg/webidl] Support syntax for specifying that an optional record<K, V> has a default value of an empty record<K, V> (Issue #1566)
Re: [w3c/ServiceWorker] Change the spec so that when a new SW is being registered it's set to not use cache the first time (#1103)
Re: [w3c/ServiceWorker] Touching documents in an "in parallel" section makes no sense (#1108)
Re: [w3c/ServiceWorker] Allow `None` as value for `Service-Worker-Allowed`. (#1165)
Re: [w3c/ServiceWorker] should FetchEvent.request ever be a range request if we cannot verify if the underlying resource is the same? (#1201)
Re: [whatwg/dom] Add reference target to shadow root (PR #1353)
Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384)
[w3c/manifest] Add `color_scheme_dark` member and themeable members (PR #1205)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (PR #1205)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (PR #1205)
[whatwg/webidl] Is nullable dictionary member a footgun? (Issue #1565)
[w3c/manifest] [Editorial] Fixes "default display mode" terminology (PR #1204)
Re: [whatwg/streams] Do the abort steps of ReadableStreamPipeTo really guarantee the abort callback to be called before cancel? (Issue #1229)
[w3c/manifest] Editorial: map definition of `minimal-ui` to `window.open()` with `features` set to `"popup"` (PR #1203)
- Re: [w3c/manifest] Editorial: map definition of `minimal-ui` to `window.open()` with `features` set to `"popup"` (PR #1203)
- Re: [w3c/manifest] Editorial: map definition of `minimal-ui` to `window.open()` with `features` set to `"popup"` (PR #1203)
Re: [w3c/manifest] fetched icons fail in chrome when same-origin policy is present (Issue #1065)
Re: [w3c/manifest] Icon purpose "splashscreen" and splashscreen text (#844)
Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109)
Re: [w3c/manifest] Add `related_applications` and `prefer_related_applications` to WPT (#950)
[w3c/manifest] Editorial: add a note on out-of-scope manifest linking behavior (PR #1202)
- Re: [w3c/manifest] Editorial: add a note on out-of-scope manifest linking behavior (PR #1202)
- Re: [w3c/manifest] Editorial: add a note on out-of-scope manifest linking behavior (PR #1202)
Re: [w3c/manifest] [Proposal] 'maximized' and 'minimized' display modes values (#839)
Re: [w3c/manifest] Add more than one icon at PWA install (#841)
Re: [w3c/manifest] Why is purpose a "unordered set of unique space-separated tokens"? (#903)
Re: [w3c/manifest] Add "payment" dictionary for payment app specific properties (#866)
Re: [w3c/manifest] Bring back "serviceworker" member (#864)
Re: [w3c/manifest] Provide guidance to UAs on appropriate names for "platform" members (#862)
Re: [w3c/manifest] Add support for "share_target" property (#665)
Re: [w3c/manifest] Add an icon "purpose" for displaying on the theme color (#617)
Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
Re: [w3ctag/design-reviews] [wg/vc] Verifiable Credentials Working Group (Issue #1179)
Re: [w3ctag/design-reviews] WG Revision: SHACL 1.2 SPARQL (Issue #1174)
Re: [whatwg/fetch] Add WebDriver BiDi network logging with stable request IDs (PR #1860)
[w3ctag/design-reviews] [wg/das] Devices and Sensors Working Group 2026 Charter (Issue #1187)
Re: [whatwg/fetch] Allow user agents to use more permissive header validation in extensions (Issue #1878)
Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359)
- Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359)
- Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359)
- Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359)
- Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359)
- Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359)
- Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359)
- Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359)
- Re: [whatwg/streams] Proposal: `ReadableStream.withSafeResolvers()` (Issue #1359)
Re: [whatwg/fetch] Support serverCertificateHashes in obtain a connection for WebTransport (Issue #1880)
Re: [whatwg/webidl] Add disposer and async_disposer (PR #1488)
Re: [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173)
- Re: [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173)
- Re: [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173)
- Re: [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173)
[w3c/selection-api] Inconsistent selectstart event timing and prevention capability (Issue #355)
[w3c/uievents] Add .pseudoTarget property to selected event types (PR #413)
- Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413)
- Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413)
[whatwg/dom] Should `Attr.isConnected` return `false` if element is connected? (Issue #1448)
- Re: [whatwg/dom] Should `Attr.isConnected` return `false` if element is connected? (Issue #1448)
- Re: [whatwg/dom] Should `Attr.isConnected` return `false` if element is connected? (Issue #1448)
- Re: [whatwg/dom] Should `Attr.isConnected` return `false` if element is connected? (Issue #1448)
Re: [whatwg/dom] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #1189)
Re: [w3ctag/design-reviews] CSS Overflow Navigation Controls (Carousels) (Issue #1037)
Re: [whatwg/fetch] Add "text" destination type, for JavaScript text imports (PR #1898)
[whatwg/fetch] main fetch assumes file:// URLs are tuple origin (Issue #1908)
- Re: [whatwg/fetch] main fetch assumes file:// URLs are tuple origin (Issue #1908)
- Re: [whatwg/fetch] main fetch assumes file:// URLs are tuple origin (Issue #1908)
- Re: [whatwg/fetch] main fetch assumes file:// URLs are tuple origin (Issue #1908)
[w3c/ServiceWorker] 1.1 (Issue #1815)
[whatwg/url] What happens on non-scalar strings? (Issue #897)
- Re: [whatwg/url] What happens on non scalar value strings? (Issue #897)
- Re: [whatwg/url] What happens on non scalar value strings? (Issue #897)
- Re: [whatwg/url] What happens on non scalar value strings? (Issue #897)
[whatwg/url] Correct example that did not encode backslash in userinfo (PR #896)
- Re: [whatwg/url] Correct example that did not encode backslash in userinfo (PR #896)
- Re: [whatwg/url] Correct example that did not encode backslash in userinfo (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
- Re: [whatwg/url] Document invariants of percent-encode sets better (PR #896)
[whatwg/url] Url encoding examples seem wrong (Issue #895)
- Re: [whatwg/url] Percent encoding examples seem to be wrong (Issue #895)
- Re: [whatwg/url] Percent encoding examples seem to be wrong (Issue #895)
- Re: [whatwg/url] Percent encoding examples seem to be wrong (Issue #895)
[w3c/editing] Repro for #523. (PR #524)
[w3c/editing] Firefox: Up/Down arrow navigation doesn't work with absolutely positioned elements in contenteditable (Issue #523)
- Re: [w3c/editing] Firefox: Up/Down arrow navigation doesn't work with absolutely positioned elements in contenteditable (Issue #523)
- Re: [w3c/editing] Firefox: Up/Down arrow navigation doesn't work with absolutely positioned elements in contenteditable (Issue #523)
- Re: [w3c/editing] Firefox: Up/Down arrow navigation doesn't work with absolutely positioned elements in contenteditable (Issue #523)
[w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814)
- Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814)
- Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814)
- Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814)
- Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814)
- Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814)
- Re: [w3c/ServiceWorker] [Editorial] Use ExtendableMessageEvent for messageerror (minor fix) (PR #1814)
Re: [w3ctag/design-reviews] CSS find-in-page highlight pseudos (Issue #1120)
[w3c/ServiceWorker] Editorial: "Update Service Worker Extended Events Set" minor fix (PR #1813)
- Re: [w3c/ServiceWorker] Editorial: "Update Service Worker Extended Events Set" minor fix (PR #1813)
- Re: [w3c/ServiceWorker] Editorial: "Update Service Worker Extended Events Set" minor fix (PR #1813)
- Re: [w3c/ServiceWorker] Editorial: "Update Service Worker Extended Events Set" minor fix (PR #1813)
[whatwg/webidl] Jul (Issue #1564)
Re: [w3c/ServiceWorker] Issues with "Handle Functional Event" (#1196)
- Re: [w3c/ServiceWorker] Issues with "Handle Functional Event" (#1196)
- Re: [w3c/ServiceWorker] Issues with "Handle Functional Event" (#1196)
Re: [w3c/ServiceWorker] Express the job queue in terms of parallel queues (#1197)
- Re: [w3c/ServiceWorker] Express the job queue in terms of parallel queues (#1197)
- Re: [w3c/ServiceWorker] Express the job queue in terms of parallel queues (#1197)
[w3c/manifest] user initiated 'uninstall' event (#1201)
- Re: [w3c/manifest] user initiated 'uninstall' event (#1201)
- Re: [w3c/manifest] user initiated 'uninstall' event (#1201)
Re: [w3c/ServiceWorker] fetch-frame-resource.https.html has a long timeout to detect page load failed (#1194)
- Re: [w3c/ServiceWorker] fetch-frame-resource.https.html has a long timeout to detect page load failed (#1194)
- Re: [w3c/ServiceWorker] fetch-frame-resource.https.html has a long timeout to detect page load failed (#1194)
Re: [w3c/ServiceWorker] messageerror event should use ExtendableMessageEvent (#1193)
Re: [w3c/ServiceWorker] How can we use SW module link in backward-compatible manner? (#1186)
Re: [w3c/ServiceWorker] respondWith is not implementable as written (#1168)
Re: [w3c/ServiceWorker] respondWith touches JS objects in parallel sections (#1169)
Re: [w3c/ServiceWorker] respondWith creates JS objects in parallel (#1170)
Re: [w3c/ServiceWorker] Carefully audit all uses of "in parallel" in the spec (#1172)
Re: [w3c/ServiceWorker] What does it mean to "choose any object"? (#1171)
[whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
- Re: [whatwg/dom] Add Marker interface (PR #1447)
Re: [w3ctag/design-reviews] User-defined script "entry points" for performance timing (Issue #1012)
Re: [w3ctag/design-reviews] WG Revision: SHACL 1.2 Core (Issue #1166)
[w3c/ServiceWorker] Update 'ancestor origins list' xref (PR #1812)
- Re: [w3c/ServiceWorker] Update 'ancestor origins list' xref (PR #1812)
- Re: [w3c/ServiceWorker] Update 'ancestor origins list' xref (PR #1812)
- Re: [w3c/ServiceWorker] Update 'ancestor origins list' xref (PR #1812)
- Re: [w3c/ServiceWorker] Update 'ancestor origins list' xref (PR #1812)
Re: [whatwg/encoding] ISO-2022-JP does not reset state when returning error (Issue #358)
[whatwg/encoding] UTF-8 / UTF-16 do not reset state when returning error (Issue #359)
- Re: [whatwg/encoding] UTF-8 does not reset state when returning error (Issue #359)
- Re: [whatwg/encoding] UTF-8 does not reset state when returning error (Issue #359)
[whatwg/dom] https://dom.spec.whatwg.org/#dom-range-deletecontents may collapse the Range to an invalid position (Issue #1446)
Re: [w3c/IndexedDB] In "object store storage operation", be more explicit about how to handle ConstraintError from an index (Issue #477)
Re: [whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107)
Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
- Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
Re: [whatwg/webidl] Add typed ReadableStream<type> and WritableStream<type> (#951)
Re: [w3c/permissions] Editorial: add an introduction (#381) (5ef3f03)
[w3c/permissions] Businesses provide emails and say to email with any inquiries, when emailed they say don't email or respond to email. (Issue #472)
- Re: [w3c/permissions] Businesses provide emails and say to email with any inquiries, when emailed they say don't email or respond to email. (Issue #472)
- Re: [w3c/permissions] Businesses provide emails and say to email with any inquiries, when emailed they say don't email or respond to email. (Issue #472)
[whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253)
- Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253)
- Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253)
- Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253)
- Re: [whatwg/fullscreen] Review Draft Publication: January 2026 (PR #253)
Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217)
Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176)
- Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176)
- Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176)
- Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176)
- Re: [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176)
Re: [w3ctag/design-reviews] Incubation: PWA (same-site) Origin Migration (Issue #1164)
Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
Re: [w3c/ServiceWorker] Preventing server-forced updates (#822)
- Re: [w3c/ServiceWorker] Preventing server-forced updates (#822)
- Re: [w3c/ServiceWorker] Preventing server-forced updates (#822)
- Re: [w3c/ServiceWorker] Preventing server-forced updates (#822)
Re: [w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172)
[w3c/uievents] Proposal: Provide OS specific shortcut key (Issue #412)
Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163)
- Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163)
- Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163)
- Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163)
Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122)
- Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122)
- Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122)
Re: [whatwg/streams] Allow error to be provided to reader.releaseLock() (Issue #1358)
[w3ctag/design-reviews] Other Spec Review: named-feature() function for CSS @supports (Issue #1186)
- Re: [w3ctag/design-reviews] Other Spec Review: named-feature() function for CSS @supports (Issue #1186)
- Re: [w3ctag/design-reviews] Other Spec Review: named-feature() function for CSS @supports (Issue #1186)
Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
- Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
- Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
- Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
- Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
- Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
- Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
- Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
- Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
- Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
- Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784)
Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
[w3ctag/design-reviews] [wg/webediting] Web Editing Working Group Charter (Issue #1185)
- Re: [w3ctag/design-reviews] [wg/webediting] Web Editing Working Group Charter (Issue #1185)
- Re: [w3ctag/design-reviews] [wg/webediting] Web Editing Working Group Charter (Issue #1185)
- Re: [w3ctag/design-reviews] [wg/webediting] Web Editing Working Group Charter (Issue #1185)
Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
Re: [whatwg/fullscreen] Fix #245 - Addressing new popover values (PR #247)
Re: [whatwg/fullscreen] Fix ambiguous reference to 'allowed to use' (PR #246)
- Re: [whatwg/fullscreen] Fix ambiguous reference to 'allowed to use' (PR #246)
- Re: [whatwg/fullscreen] Fix ambiguous reference to 'allowed to use' (PR #246)
Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013)
- Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013)
- Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013)
- Re: [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013)
Re: [w3ctag/design-reviews] MiniApp Packaging (Issue #762)
Re: [w3ctag/design-reviews] WG Revision: CSS Anchor Positioning Level 1 (Issue #1182)
[whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362)
- Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362)
- Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362)
- Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362)
- Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362)
- Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362)
- Re: [whatwg/streams] Interesting edge case... queueMicrotask and desiredSize in start algorithm (Issue #1362)
[whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445)
- Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445)
- Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445)
- Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445)
- Re: [whatwg/dom] Include cloning keep custom element registry null while cloning shadow root (PR #1445)
Re: [whatwg/dom] Add OpaqueRange interface (PR #1404)
Re: [whatwg/dom] Add PlainTextRange interface (PR #1404)
[whatwg/fetch] Block 416 alongside 206 (PR #1907)
- Re: [whatwg/fetch] Block 416 alongside 206 (PR #1907)
- Re: [whatwg/fetch] Block 416 alongside 206 (PR #1907)
[whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906)
- Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906)
- Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906)
- Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906)
- Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906)
- Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906)
- Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906)
- Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906)
- Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906)
- Re: [whatwg/fetch] Block opaque 416 responses to range requests (Issue #1906)
[w3ctag/design-reviews] Incubation: IdP-Initiated FedCM (Issue #1184)
Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
[w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411)
- Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411)
- Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411)
- Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411)
- Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411)
- Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411)
- Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411)
- Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411)
- Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411)
- Re: [w3c/uievents] MouseEvent, WheelEvent, and some algorithms moving to pointer events (PR #411)
Re: [w3c/uievents] Proposal: use `relatedTarget` for click events originated from labels (Issue #402)
Re: [w3c/uievents] Events do not have "default action"s (#104)
Re: [whatwg/url] Define the "extract an origin" operation. (PR #892)
[w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183)
- Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183)
- Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183)
- Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183)
- Re: [w3ctag/design-reviews] Incubation: new speculation rules action: prerender_until_script (Issue #1183)
Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896)
- Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896)
- Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896)
- Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896)
- Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896)
- Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896)
- Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896)
Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422)
- Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422)
- Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422)
- Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422)
- Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422)
- Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422)
- Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422)
- Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422)
- Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422)
- Re: [whatwg/dom] Option to allow `querySelector` to query shadow roots (Issue #1422)
Re: [w3c/uievents] [Proposal] Add "Zoom" event (#31)
Re: [w3ctag/design-reviews] [wg/dx] Dataset Exchange Working Group Charter (Issue #1171)
Re: [w3c/clipboard-apis] `ClipboardItem`: clarify mime parsing (Issue #242)
Re: [whatwg/webidl] Enumeration order of interface members (#432)
Re: [whatwg/dom] [meta] MutationObserver improvements tracking issue (Issue #1439)
[w3c/editing] `insertText` should move to parent node if range's start container is a void element (Issue #522)
[WICG/webcomponents] Fix HTML Modules inline module script (PR #1121)
[whatwg/webidl] Meta: update repository files (PR #1562)
- Re: [whatwg/webidl] Meta: update repository files (PR #1562)
- Re: [whatwg/webidl] Meta: update repository files (PR #1562)
Re: [w3c/gamepad] Add device orientation support (Issue #211)
[whatwg/webidl] Intent to use Constants (Issue #1561)
[whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894)
- Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894)
- Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894)
- Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894)
- Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894)
- Re: [whatwg/url] Editorial: fix floating steps in IPv6 parser (PR #894)
Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523)
[w3c/selection-api] the steps of `Selection.setBaseAndExtent()` do not check the node type (Issue #354)
[w3c/selection-api] the steps of Selection.extend() does not check whether the given offset is valid in the container (Issue #353)
Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240)
- Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240)
- Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240)
Re: [w3ctag/design-reviews] WG New Spec: RDF 1.2 Semantics (Issue #1160)
[whatwg/fetch] Accept header for `image` destination should be updated for modern image formats (Issue #1905)
[whatwg/dom] Editorial: correct misleading node equals sentence (PR #1444)
Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442)
- Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442)
- Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442)
- Re: [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442)
Re: [whatwg/streams] Should the abort result reflect the close result? (Issue #1203)
Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860)
- Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860)
- Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860)
- Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860)
- Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860)
- Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860)
- Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860)
- Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860)
- Re: [whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860)
Re: [w3ctag/design-reviews] Canvas Text Metrics for Editing, Art and Design (Issue #1095)
[whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904)
- Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904)
- Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904)
- Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904)
- Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904)
- Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904)
- Re: [whatwg/fetch] Add quota/requested info to the QuotaExceededError (PR #1904)
Re: [w3c/uievents] Event order between "compositionend" and "input" (#202)
Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
- Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
[whatwg/webidl] Intent to use Constants (Issue #1560)
Re: [whatwg/fetch] Should network state be keyed beyond the top-level site (#1035)
[whatwg/webidl] RL25 (Issue #1559)
[w3c/manifest] Tidied up document using tidy-html5 (PR #1200)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1200)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1200)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1200)
Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199)
- Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199)
- Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199)
- Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199)
Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152)
- Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152)
- Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152)
- Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152)
Re: [w3ctag/design-reviews] [HTML] Canvas place element (Issue #997)
Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136)
Re: [w3ctag/design-reviews] Incubation: seamless page transition with deferred commit (Issue #1177)
Re: [whatwg/fetch] Update Note on Request Destination / CSP directive (Issue #1466)
[w3c/IndexedDB] Remove redundant task queueing to start transaction (Issue #487)
[w3c/IndexedDB] Old db version is lost when aborting upgrade (Issue #486)
[w3c/IndexedDB] Replace connection queue with parallel queue (Issue #485)
[w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484)
- Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484)
- Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484)
- Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484)
- Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484)
- Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484)
- Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484)
- Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484)
- Re: [w3c/IndexedDB] Add TLA+ spec for core concurrency of spec (PR #484)
Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169)
[whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903)
- Re: [whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903)
- Re: [whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903)
- Re: [whatwg/fetch] QuotaExceedederror is now a derived interface (Issue #1903)
[whatwg/fetch] Update fetch-later spec according to WPT expectations=0D (PR #1902)
Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
- Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
[whatwg/webidl] Intent to use Constantly (Issue #1558)
- Re: [whatwg/webidl] Intent to use Constantly (Issue #1558)
- Re: [whatwg/webidl] Intent to use Constantly (Issue #1558)
- Re: [whatwg/webidl] Intent to use Constantly (Issue #1558)
[whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
- Re: [whatwg/url] Malformed URL Normalization in Standard Introduces SSRF Risks (Issue #893)
Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876)
[whatwg/webidl] Fix IsDetachedBuffer check in ArrayBuffer transfer (PR #1557)
Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385)
Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443)
- Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443)
- Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443)
- Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443)
- Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443)
- Re: [whatwg/dom] concept-node-equals definition is not correct (Issue #1443)