Thursday, 23 April 2026
- Re: [w3c/selection-api] Set "has scheduled selectionchange event" to true (PR #356)
- [w3c/selection-api] Set "has scheduled selectionchange event" to true (PR #356)
- Re: [w3c/IndexedDB] Spec mostly doesn't mention blob expectations (Issue #454)
- Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
Wednesday, 22 April 2026
- Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152)
- Re: [whatwg/streams] Export "set up reader/writer" algorithms for other specs (PR #1370)
- Re: [whatwg/streams] Export "set up reader/writer" algorithms for other specs (PR #1370)
- Re: [whatwg/streams] Export "set up reader/writer" algorithms for other specs (PR #1370)
- Re: [whatwg/streams] Export "set up reader/writer" algorithms for other specs (PR #1370)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485)
- Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/streams] Export "set up reader/writer" algorithms for other specs (PR #1370)
- Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485)
- [whatwg/fullscreen] Upstream Document PiP changes to "fullscreen is supported" (PR #259)
- Re: [whatwg/dom] AsyncContext propagation to events (PR #1451)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
Tuesday, 21 April 2026
- Re: [whatwg/streams] Export "set up reader/writer" algorithms for other specs (PR #1370)
- Re: [whatwg/streams] Export "set up reader/writer" algorithms for other specs (PR #1370)
- Re: [whatwg/streams] Export "set up reader/writer" algorithms for other specs (PR #1370)
- Re: [whatwg/streams] Export "set up reader/writer" algorithms for other specs (PR #1370)
- Re: [whatwg/streams] Add `noexport` for abstract operations (PR #1369)
- [whatwg/streams] Export "set up reader/writer" algorithms for other specs (PR #1370)
- Re: [whatwg/fetch] Define ABNF for `origin-or-null. (PR #1924)
- Re: [whatwg/fetch] Add WebDriver BiDi network logging with stable request IDs (PR #1860)
- Re: [whatwg/fetch] Add WebDriver BiDi network logging with stable request IDs (PR #1860)
- Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485)
- Re: [whatwg/fetch] Define ABNF for `origin-or-null. (PR #1924)
- Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485)
- Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485)
- Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485)
- Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485)
- Re: [whatwg/streams] Add `noexport` for abstract operations (PR #1369)
- Re: [whatwg/webidl] Mandate a default value for boolean dictionary members? (Issue #1485)
- Re: [whatwg/streams] Add `noexport` for abstract operations (PR #1369)
- [whatwg/streams] Add no-export for abstract operations (PR #1369)
- Re: [whatwg/fetch] Define ABNF for `origin-or-null. (PR #1924)
- Re: [whatwg/streams] Remove abstract-op (PR #1368)
- Re: [whatwg/streams] Remove abstract-op (PR #1368)
- Re: [whatwg/streams] Remove abstract-op (PR #1368)
- Re: [whatwg/streams] Remove abstract-op (PR #1368)
- Re: [whatwg/streams] Remove abstract-op (PR #1368)
- [whatwg/streams] Remove abstract-op (PR #1368)
- [whatwg/fetch] Define ABNF for `origin-or-null. (PR #1924)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
Monday, 20 April 2026
- Re: [whatwg/fetch] Disallowing `Authorization` in CORS-preflight wildcards is currently not web compatible (Issue #1919)
- Re: [whatwg/fetch] Fetch retry (draft) (PR #1923)
- [whatwg/fetch] Fetch retry (draft) (PR #1923)
Saturday, 18 April 2026
- Re: [whatwg/url] Editorial: Add missing article before "hexadecimal number" (PR #906)
- Re: [whatwg/url] Editorial: Add missing article before "hexadecimal number" (PR #906)
- [whatwg/url] Editorial: Add missing article before "hexadecimal number" (PR #906)
Friday, 17 April 2026
- Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202)
- Re: [whatwg/encoding] Add SECURITY.md for security policy and reporting (PR #363)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- [whatwg/encoding] Add SECURITY.md for security policy and reporting (PR #363)
Thursday, 16 April 2026
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [w3c/manifest] Rename "default display mode" to "applied display mode" (PR #1215)
- [whatwg/dom] Record task-like timing in fire an event (PR #1462)
- Re: [whatwg/storage] ans.1 (Issue #192)
- [whatwg/storage] ans.1 (Issue #192)
Wednesday, 15 April 2026
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- [w3ctag/design-reviews] WG Revision: Selectors 4 (Issue #1221)
- Re: [whatwg/fetch] Only consider pending fetch-later requests for deferred fetch quota (PR #1902)
- Re: [whatwg/fetch] Only consider pending fetch-later requests for deferred fetch quota (PR #1902)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)
- Re: [whatwg/fetch] Define multipart/form-data (PR #1922)
- [w3ctag/design-reviews] [wg/wasm] WebAssembly WG rechartering (Issue #1220)
- Re: [w3c/manifest] Rename "default display mode" to "applied display mode" (PR #1215)
Tuesday, 14 April 2026
- Re: [whatwg/url] Correct a couple minor issues (b11d73b)
- Re: [w3c/manifest] Rename "default display mode" to "applied display mode" (PR #1215)
- Re: [whatwg/fetch] Define multipart/form-data (PR #1922)
- [whatwg/url] Close gap between URL writing and parser sections (PR #905)
- 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)
- [whatwg/fetch] Define multipart/form-data (PR #1922)
- Re: [whatwg/url] Correct a couple minor issues (PR #904)
- Re: [whatwg/url] Correct a couple minor issues (PR #904)
- Re: [whatwg/url] Correct a couple minor issues (PR #904)
- [whatwg/url] Correct a couple minor issues (PR #904)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134)
- Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134)
Monday, 13 April 2026
- Re: [whatwg/dom] AsyncContext propagation to events (PR #1451)
- Re: [whatwg/streams] Use `async iterable` webidl type in ReadableStream.from (PR #1310)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3ctag/design-reviews] [wg/das] Devices and Sensors Working Group 2026 Charter (Issue #1187)
- Re: [whatwg/encoding] Add support for `[AllowResizable]` inputs (PR #362)
- Re: [whatwg/encoding] Add support for `[AllowResizable]` inputs (PR #362)
- Re: [whatwg/encoding] Add support for `[AllowResizable]` inputs (PR #362)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- [w3c/manifest] Add normative algorithm for when to call "fetch a manifest image resource" (Issue #1216)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
Sunday, 12 April 2026
- Re: [whatwg/streams] Editorial: Narrow ReadableStreamBYOBRequest.view to Uint8Array (PR #1367)
- Re: [whatwg/streams] Editorial: Narrow ReadableStreamBYOBRequest.view to Uint8Array (PR #1367)
- [whatwg/streams] Editorial: Narrow ReadableStreamBYOBRequest.view to Uint8Array (PR #1367)
- Re: [whatwg/streams] Specification unclear on type of byobRequest.view (Issue #1366)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- [whatwg/streams] Specification unclear on type of byobRequest.view (Issue #1366)
Saturday, 11 April 2026
- Re: [whatwg/fetch] Empty fetchLater requests are allowed per spec, but WPT expects these to fail (Issue #1920)
- Re: [whatwg/fetch] some edits (PR #1921)
- Re: [whatwg/webidl] Editorial: note that Promise<T> arguments also accept T (e1300e9)
- Re: [w3c/manifest] Rename "default display mode" to "applied display mode" (PR #1215)
- [whatwg/fetch] some edits (PR #1921)
- Re: [w3c/manifest] Rename "default display mode" to "applied display mode" (PR #1215)
- Re: [w3c/gamepad] Require system focus for gamepad user gesture (PR #207)
- Re: [w3c/gamepad] Require system focus for gamepad user gesture (PR #207)
- Re: [w3c/gamepad] Require system focus for gamepad user gesture (PR #207)
- Re: [w3ctag/design-reviews] [wg/das] Devices and Sensors Working Group 2026 Charter (Issue #1187)
Friday, 10 April 2026
- Re: [w3ctag/design-reviews] Question: How to reduce apex domain modifications for IDPs using FedCM (Issue #1217)
- Re: [w3ctag/design-reviews] Question: How to reduce apex domain modifications for IDPs using FedCM (Issue #1217)
- Re: [w3ctag/design-reviews] WG Revision: EPUB 3.4 (Issue #1216)
- Re: [w3ctag/design-reviews] WG Revision: EPUB 3.4 (Issue #1216)
- Re: [w3ctag/design-reviews] Question: Capability Delegation stalled -- specs are implementing local workarounds (Issue #1213)
- Re: [w3ctag/design-reviews] Question: Could the TAG help define "The Web Platform" vs "The Web" or some other useful distinctions? (Issue #1202)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [whatwg/fetch] Only consider pending fetch-later requests for deferred fetch quota (PR #1902)
- [whatwg/fetch] Empty fetchLater requests are allowed per spec, but WPT expects these to fail (Issue #1920)
- Re: [whatwg/fetch] Only consider pending fetch-later requests for deferred fetch quota (PR #1902)
- Re: [whatwg/fetch] Update fetch-later spec according to WPT expectations=0D (PR #1902)
- [w3c/manifest] Rename "default display mode" to "applied display mode" (PR #1215)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
Thursday, 9 April 2026
- Re: [w3ctag/design-reviews] Question: Using Cross-Origin-Resource-Policy to enable compression dictionary support for opaque responses (Issue #1203)
- Re: [w3ctag/design-reviews] Question: Using Cross-Origin-Resource-Policy to enable compression dictionary support for opaque responses (Issue #1203)
- Re: [w3c/gamepad] Require system focus for gamepad user gesture (PR #207)
- Re: [w3c/gamepad] Require system focus for gamepad user gesture (PR #207)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Installation detection from a web app url opened in a browser tab (Issue #1214)
- Re: [w3c/manifest] Installation detection from a web app url opened in a browser tab (Issue #1214)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- [w3c/manifest] Installation detection from a web app url opened in a browser tab (Issue #1214)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/editing] Caret movement based on visual screen position rather than DOM order? (Issue #533)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] "Default display mode" section is super confusing (Issue #1024)
- Re: [w3c/manifest] "Default display mode" section is super confusing (Issue #1024)
- Re: [w3c/manifest] Clarify how images are loaded, and that they don't depend on CSP (#910)
- Re: [w3c/editing] Repro for #531 (PR #532)
- Re: [w3c/editing] Repro for #531 (PR #532)
- Re: [w3c/editing] Safari: `height: 100%` changes layout when the parent height is defined via `aspect-ratio` (Issue #531)
- Re: [w3c/editing] Safari: `height: 100%` changes layout when the parent height is defined via `aspect-ratio` (Issue #531)
- Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784)
- Re: [w3c/manifest] Clarify applying manifest to an existing browsing context (PR #1202)
- Re: [w3c/manifest] Clarify applying manifest to an existing browsing context (PR #1202)
- Re: [w3c/manifest] Clarify applying manifest to an existing browsing context (PR #1202)
- Re: [w3c/manifest] chore: Add retiredDate for Diego González (PR #1213)
- Re: [w3c/manifest] chore: Add retiredDate for Diego González (PR #1213)
- Re: [w3c/manifest] chore: Add retiredDate for Diego González (PR #1213)
- Re: [w3c/manifest] Clarify applying manifest to an existing browsing context (PR #1202)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Clarify how manifest image resources are fetched (PR #1171)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3ctag/design-reviews] Incubation: Web Speech API: On-Device Recognition Quality (Issue #1189)
- [w3c/manifest] chore: Add retiredDate for Diego González (PR #1213)
- Re: [w3c/editing] Spec: Empty addressable content fields with placeholders (Issue #528)
- [w3c/editing] Caret movement based on visual screen position rather than DOM order? (Issue #533)
- Re: [w3c/editing] Charter - open tasks (Issue #527)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Clarify applying manifest to an existing browsing context (PR #1202)
- Re: [w3c/manifest] [Editorial] Fixes "default display mode" terminology (PR #1204)
- Re: [w3c/manifest] [Editorial] Fixes "default display mode" terminology (PR #1204)
- Re: [w3c/manifest] Clarify applying manifest to an existing browsing context (PR #1202)
- Re: [w3c/manifest] Clarify applying manifest to an existing browsing context (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)
- [w3c/permissions] Permission state constraints don't always seem to be ensured (Issue #476)
- Re: [w3c/manifest] Editorial: add a note on out-of-scope manifest linking behavior (PR #1202)
- Re: [w3c/editing] Firefox: event.getTargetRanges() in beforeinput not consistent with window.getSelection() (Issue #493)
- Re: [WICG/webcomponents] HTML Modules (#645)
- Re: [WICG/webcomponents] HTML Modules (#645)
- Re: [WICG/webcomponents] HTML Modules (#645)
- Re: [w3c/FileAPI] readAsDataURL should be more precise about the data URL contents (#104)
- Re: [w3c/ServiceWorker] Request's initiator can't be "fetch" (Issue #1718)
- Re: [w3c/ServiceWorker] Request's initiator can't be "fetch" (Issue #1718)
- Re: [w3c/ServiceWorker] Set request's initiator and destination to empty string in cache.addA… (PR #1822)
Wednesday, 8 April 2026
- [w3c/gamepad] DOM Elements Integration (Issue #227)
- Re: [w3c/FileAPI] readAsDataURL should be more precise about the data URL contents (#104)
- Re: [w3c/FileAPI] readAsDataURL should be more precise about the data URL contents (#104)
- Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098)
- Re: [w3c/FileAPI] Correct handling of resizable ArrayBuffer? (Issue #219)
- Re: [w3c/FileAPI] Correct handling of resizable ArrayBuffer? (Issue #219)
- Re: [whatwg/fetch] Disallowing `Authorization` in CORS-preflight wildcards is currently not web compatible (Issue #1919)
- Re: [w3c/ServiceWorker] Set request's initiator and destination to empty string in cache.addA… (PR #1822)
- [w3c/editing] Repro for #531 (PR #532)
- [w3c/editing] Safari: `height: 100%` changes layout when the parent height is defined via `aspect-ratio` (Issue #531)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/permissions] Add more permissions into the registry (Issue #475)
- Re: [w3c/ServiceWorker] Set request's initiator and destination to empty string in cache.addA… (PR #1822)
- Re: [w3c/ServiceWorker] Set request's initiator and destination to empty string in cache.addA… (PR #1822)
- Re: [w3c/ServiceWorker] Set request's initiator and destination to empty string in cache.addA… (PR #1822)
- [w3c/permissions] Add more permissions into the registry (Issue #475)
- Re: [w3c/ServiceWorker] Set request's initiator and destination to empty string in cache.addA… (PR #1822)
- [w3c/ServiceWorker] Set request's initiator and destination to empty string in cache.addA… (PR #1822)
- Re: [w3ctag/design-reviews] Question: How to reduce apex domain modifications for IDPs using FedCM (Issue #1217)
Tuesday, 7 April 2026
- [w3ctag/design-reviews] Incubation: Platform-provided behaviors for custom elements (Issue #1219)
- [w3ctag/design-reviews] <usermedia> element (part of PEPC) (Issue #1218)
- Re: [w3ctag/design-reviews] Question: How to reduce apex domain modifications for IDPs using FedCM (Issue #1217)
- Re: [w3c/FileAPI] Correct handling of resizable ArrayBuffer? (Issue #219)
- [w3ctag/design-reviews] Question: How to reduce apex domain modifications for IDPs using FedCM (Issue #1217)
- Re: [w3ctag/design-reviews] [wg/das] Devices and Sensors Working Group 2026 Charter (Issue #1187)
- [whatwg/fetch] Disallowing `Authorization` in CORS-preflight wildcards is currently not web compatible (Issue #1919)
- Re: [w3c/FileAPI] Correct handling of resizable ArrayBuffer? (Issue #219)
- [w3c/FileAPI] Correct handling of resizable ArrayBuffer? (Issue #219)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
Monday, 6 April 2026
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
- Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (colors only) (PR #1207)
Saturday, 4 April 2026
- [whatwg/webidl] Intent to use bigint/numeric union (Issue #1588)
- Re: [w3c/IndexedDB] Clarification on what `range` should be in "create-a-request-to-retrieve-multiple-items" when `queryOrOptions` is undefined/null (Issue #493)
- Re: [w3c/IndexedDB] The algorithm "create-a-request-to-retrieve-multiple-items" does not specify what `range` should be when `queryOrOptions` is undefined/null (Issue #493)
- [w3c/IndexedDB] The algorithm "create-a-request-to-retrieve-multiple-items" does not specify what `range` should be when `queryOrOptions` is undefined/null (Issue #493)
Friday, 3 April 2026
- Re: [whatwg/fetch] Add ability to opt-out of back-forward cache (Issue #1917)
- Re: [whatwg/fetch] Use SETTINGS_WT_ENABLED from draft 15 of ietf-webtrans-http3 (PR #1918)
- Re: [w3c/clipboard-apis] Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() (PR #248)
- Re: [w3c/clipboard-apis] Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() (PR #248)
- [whatwg/webidl] DOMException name proposal (Issue #1586)
- Re: [w3c/clipboard-apis] Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() (PR #248)
- Re: [w3c/clipboard-apis] Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() (PR #248)
- Re: [w3c/clipboard-apis] Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() (PR #248)
- Re: [w3c/clipboard-apis] Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() (PR #248)
- Re: [w3c/clipboard-apis] Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() (PR #248)
- Re: [w3c/clipboard-apis] Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() (PR #248)
- Re: [w3c/clipboard-apis] Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() (PR #248)
Thursday, 2 April 2026
- Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198)
- Re: [whatwg/streams] Do not mark abstract operations with `data-export` (Issue #1365)
- [whatwg/streams] Do not mark abstract operations with `data-export` (Issue #1365)
- Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198)
- Re: [WICG/webcomponents] Reference Target: How to handle events fired on the reference target by related elements? (Issue #1098)
- Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198)
- Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198)
- Re: [w3c/ServiceWorker] Request's initiator can't be "fetch" (Issue #1718)
- Re: [w3c/ServiceWorker] Request's initiator can't be "fetch" (Issue #1718)
- Re: [w3c/clipboard-apis] Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() (PR #248)
- Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198)
- Re: [w3ctag/design-reviews] Incubation: speculation rules `form_submission` field for prerendering (Issue #1192)
- Re: [w3ctag/design-reviews] Incubation: speculation rules `form_submission` field for prerendering (Issue #1192)
- Re: [w3c/ServiceWorker] Request's initiator can't be "fetch" (Issue #1718)
- [w3ctag/design-reviews] WG Revision: EPUB 3.4 (Issue #1216)
Wednesday, 1 April 2026
- Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)
- Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198)
- Re: [whatwg/fetch] Use SETTINGS_WT_ENABLED from draft 15 of ietf-webtrans-http3 (PR #1918)
- [whatwg/fetch] Use SETTINGS_WT_ENABLED from draft 15 of ietf-webtrans-http3 (PR #1918)
- Re: [w3ctag/design-reviews] Question: Could the TAG help define "The Web Platform" vs "The Web" or some other useful distinctions? (Issue #1202)
- [whatwg/fetch] Add ability to opt-out of back-forward cache (Issue #1917)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- [w3ctag/design-reviews] [wg/wot] Web of Things Working Group rechartering (Issue #1215)
- [w3ctag/design-reviews] [wg/math] Math Group Charter (Issue #1214)
- Re: [whatwg/fetch] Add "text" destination type, for JavaScript text imports (PR #1898)
- Re: [whatwg/fetch] Add "text" destination type, for JavaScript text imports (PR #1898)
- Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198)
- Re: [w3ctag/design-reviews] Other Spec Review: The revert-rule keyword (Issue #1193)
- Re: [w3ctag/design-reviews] Other Spec Review: The revert-rule keyword (Issue #1193)
- Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134)
- Re: [w3ctag/design-reviews] Incubation: seamless page transition with deferred commit (Issue #1177)
- Re: [w3c/manifest] Standardize when link clicks or navigations enter and/or leave installed PWAs (#989)
- Re: [w3c/manifest] Standardize when link clicks or navigations enter and/or leave installed PWAs (#989)
- Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198)
- Re: [w3c/editing] execCommand commands listed in MDN but not in the spec (Issue #530)
- Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198)
- Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134)