Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849)
[whatwg/webidl] Add self to acks (PR #1110)
Re: [whatwg/dom] Consider specifying document.evaluate and document.createNSResolver (#67)
[whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
[whatwg/webidl] Genius-Tech-1998s (Issue #1109)
Re: [w3ctag/design-reviews] Font Table Access API (#400)
[whatwg/webidl] Video (Issue #1108)
[whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107)
- Re: [whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107)
- Re: [whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107)
- Re: [whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107)
- Re: [whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107)
Re: [w3c/ServiceWorker] The Cache objects do not expire unless authors *or users* delete the entries. (#1276)
[w3c/permissions] "extra permission data" definition should be normative (Issue #369)
Re: [w3c/permissions] Guidance on whether to add an API to the permissions spec (#116)
Re: [w3c/permissions] Safari returns different results for current permission state (#278)
- Re: [w3c/permissions] Safari returns different results for current permission state (#278)
- Re: [w3c/permissions] Safari returns different results for current permission state (#278)
[w3c/clipboard-apis] [meta] Fix broken markup (PR #171)
Re: [w3c/permissions] Specifications should add conformance classes (#283)
Re: [w3c/permissions] Handle non-fully-active documents (#162)
Re: [whatwg/fetch] Should 0.0.0.0 always be a network error? (#1117)
Re: [whatwg/dom] Disconnect single target instead of all (#126)
[whatwg/streams] How to create a transformed WritableStream that waits for close? (Issue #1222)
Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172)
- Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172)
- Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172)
- Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172)
- Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172)
- Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172)
Re: [whatwg/dom] Proposal: Storage Access API (#560)
[whatwg/streams] Editorial Mark high water mark definition as exported (PR #1221)
- Re: [whatwg/streams] Editorial: Mark high water mark definition as exported (PR #1221)
- Re: [whatwg/streams] Editorial: Mark high water mark definition as exported (PR #1221)
- Re: [whatwg/streams] Editorial: Mark high water mark definition as exported (PR #1221)
Re: [whatwg/fetch] Handling Partial Content / 206 (#144)
[w3c/ServiceWorker] Unnecessary Origin Restriction (Issue #1628)
- Re: [w3c/ServiceWorker] Unnecessary Origin Restriction (Issue #1628)
- Re: [w3c/ServiceWorker] Unnecessary Origin Restriction (Issue #1628)
- Re: [w3c/ServiceWorker] Unnecessary Origin Restriction (Issue #1628)
- Re: [w3c/ServiceWorker] Unnecessary Origin Restriction (Issue #1628)
[WICG/webcomponents] Place to chat about Web Components standardization (Issue #956)
[whatwg/storage] Editorial: use string literal for permission name (PR #136)
- Re: [whatwg/storage] Editorial: use string literal for permission name (PR #136)
- Re: [whatwg/storage] Editorial: use string literal for permission name (PR #136)
- Re: [whatwg/storage] Editorial: use string literal for permission name (PR #136)
- Re: [whatwg/storage] Editorial: use string literal for permission name (PR #136)
[w3c/ServiceWorker] when I deploy my app new version, latest version/changes not updated at the first time reload (Issue #1627)
- Re: [w3c/ServiceWorker] when I deploy my app new version, latest version/changes not updated at the first time reload (Issue #1627)
- Re: [w3c/ServiceWorker] when I deploy my app new version, latest version/changes not updated at the first time reload (Issue #1627)
Re: [w3ctag/design-reviews] Web App Launch Handler (Issue #683)
Re: [w3c/manifest] Allow unique start_url for subdomains (#470)
Re: [w3c/ServiceWorker] support efficient offline redirects (#1457)
[w3c/permissions] Editorial: add UA + spec conformance classes (PR #368)
- Re: [w3c/permissions] Editorial: add UA + spec conformance classes (PR #368)
- Re: [w3c/permissions] Editorial: add UA + spec conformance classes (PR #368)
- Re: [w3c/permissions] Editorial: add UA + spec conformance classes (PR #368)
Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813)
[whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106)
- Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106)
- Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106)
- Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106)
- Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106)
- Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106)
- Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106)
[w3c/permissions] Editorial: clarify Permission Policy / Powerful Feature overlap (PR #367)
- Re: [w3c/permissions] Editorial: clarify Permission Policy / Powerful Feature overlap (PR #367)
- Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367)
- Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367)
- Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367)
- Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367)
- Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367)
- Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107)
Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689)
[w3c/permissions] Removal of PermissionName broke downstream standards (Issue #366)
- Re: [w3c/permissions] Removal of PermissionName broke downstream standards (Issue #366)
- Re: [w3c/permissions] Removal of PermissionName broke downstream standards (Issue #366)
- Re: [w3c/permissions] Removal of PermissionName broke downstream standards (Issue #366)
[whatwg/streams] Review Draft Publication: February 2022 (PR #1219)
- Re: [whatwg/streams] Review Draft Publication: February 2022 (PR #1219)
- Re: [whatwg/streams] Review Draft Publication: February 2022 (PR #1219)
[whatwg/xhr] Review Draft Publication: February 2022 (PR #341)
[whatwg/url] Review Draft Publication: February 2022 (PR #687)
[whatwg/storage] Review Draft Publication: February 2022 (PR #135)
- Re: [whatwg/storage] Review Draft Publication: February 2022 (PR #135)
- Re: [whatwg/storage] Review Draft Publication: February 2022 (PR #135)
Re: [w3ctag/design-reviews] Markup based Client Hints delegation for third-party content (Issue #702)
Re: [w3c/permissions] Handle not fully active documents when querying Permissions API (#249)
[w3c/permissions] Handle non-fully-active documents (PR #365)
- Re: [w3c/permissions] Handle non-fully-active documents (PR #365)
- Re: [w3c/permissions] Handle non-fully-active documents (PR #365)
- Re: [w3c/permissions] Handle non-fully-active documents (PR #365)
- Re: [w3c/permissions] Handle non-fully-active documents (PR #365)
- Re: [w3c/permissions] Handle non-fully-active documents (PR #365)
- Re: [w3c/permissions] Handle non-fully-active documents (PR #365)
- Re: [w3c/permissions] Handle non-fully-active documents (PR #365)
- Re: [w3c/permissions] Handle non-fully-active documents (PR #365)
- Re: [w3c/permissions] Handle non-fully-active documents (PR #365)
Re: [w3c/permissions] Editorial: use permission state concept, not enum values (#285)
Re: [w3c/permissions] Permissions states should be concepts (#243)
Re: [w3c/permissions] Add "background-playback" permission type? (#193)
[whatwg/webidl] Issue (Issue #1104)
Re: [whatwg/fetch] HTTP/2 headers (#1316)
Re: [whatwg/fetch] HTTP/2 server push support (#51)
- Re: [whatwg/fetch] HTTP/2 server push support (#51)
- Re: [whatwg/fetch] HTTP/2 server push support (#51)
- Re: [whatwg/fetch] HTTP/2 server push support (#51)
- Re: [whatwg/fetch] HTTP/2 server push support (#51)
Re: [WICG/webcomponents] SVG <use> tag with CSS ::part selector (Issue #955)
Re: [WICG/webcomponents] Adding support for ShadowDOM features in SVG (#942)
Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
- Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
- Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
- Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
Re: [whatwg/streams] WritableStreamDefaultController.abortReason (#1165)
[w3c/editing] clarifications for the pickling design proposal (Issue #393)
[w3c/IndexedDB] Batch get/getAll (Issue #376)
Re: [whatwg/storage] Session storage and changing browsing contexts (#119)
[whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059)
- Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059)
- Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059)
- Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059)
- Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059)
- Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059)
- Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059)
- Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059)
[w3c/ServiceWorker] Service Worker as secure storage and provider for access token and refresh token (Issue #1626)
Re: [w3c/gamepad] Require secure context for gamepad state and events (#120)
[whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
Re: [whatwg/streams] 'Splitter' stream? (#1030)
[w3c/manifest] Tidied up document using tidy-html5 (PR #1032)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1032)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1032)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1032)
Re: [w3c/manifest] Specify how updates work (#446)
[w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170)
- Re: [w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170)
- Re: [w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170)
- Re: [w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170)
Re: [w3c/IndexedDB] Key Paths: Support iteration step operator (#35)
Re: [w3ctag/design-reviews] Gamepad API input events (#662)
[w3c/editing] Add explainer for custom format read/write. (PR #392)
- Re: [w3c/editing] Add explainer for custom format read/write. (PR #392)
- Re: [w3c/editing] Add explainer for custom format read/write. (PR #392)
- Re: [w3c/editing] Add explainer for custom format read/write. (PR #392)
[whatwg/streams] WritableStreamDefaultController [[strategySizeAlgorithm]] called after being set to undefined (Issue #1218)
- Re: [whatwg/streams] WritableStreamDefaultController [[strategySizeAlgorithm]] called after being set to undefined (Issue #1218)
- Re: [whatwg/streams] WritableStreamDefaultController [[strategySizeAlgorithm]] called after being set to undefined (Issue #1218)
Re: [w3ctag/design-reviews] Distributed Tracing WG: Baggage specification (#650)
[w3c/permissions] Editorial: Add linking-text for "specifies a powerful feature" (PR #363)
- Re: [w3c/permissions] Editorial: Add linking-text for "specifies a powerful feature" (PR #363)
- Re: [w3c/permissions] Editorial: Add linking-text for "specifies a powerful feature" (PR #363)
Re: [w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682)
- Re: [w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682)
- Re: [w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682)
Re: [w3c/ServiceWorker] How does ServiceWorker interact with non-"fully active" documents? (#1594)
Re: [w3ctag/design-reviews] Scroll-linked Animations (#521)
Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49)
- Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49)
- Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49)
[whatwg/webidl] Expoes (Issue #1102)
Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
Re: [w3ctag/design-reviews] `prefers-reduced-data` CSS Media Query (Issue #705)
Re: [whatwg/dom] Add declarative Shadow DOM features (#892)
[whatwg/dom] Add Security and privacy considerations section (PR #1058)
[w3ctag/design-reviews] WIP: Web of Things (WoT) Thing Description 1.1 - Security Review (Issue #715)
[whatwg/fetch] Check if fetch record's "fetch" instance needs to be nullable (Issue #1403)
Re: [whatwg/dom] Privacy/Security considerations section (#1013)
Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)
- Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)
- Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)
- Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)
- Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)
- Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)
- Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)
- Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)
- Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)
- Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)
- Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)
[whatwg/fetch] B (Issue #1402)
[w3c/clipboard-apis] `ClipboardItem` constructor should throw when `items` is empty (Issue #169)
- Re: [w3c/clipboard-apis] `ClipboardItem` constructor should throw when `items` are empty (Issue #169)
- Re: [w3c/clipboard-apis] `ClipboardItem` constructor should throw when `items` are empty (Issue #169)
Re: [WICG/webcomponents] [WebDriver] Testability of web components (#771)
Re: [w3c/permissions] Move permissions out to each spec (#263)
Re: [w3c/permissions] Ensure "screen-wake-lock" permission is integrated in Screen Wake Lock API (or just remove it?) (Issue #319)
[w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
- Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362)
[whatwg/webidl] Intent to use Constants (Issue #1101)
[whatwg/webidl] Mismatch between normative and informative text about the Other grammar rule (Issue #1100)
- Re: [whatwg/webidl] Mismatch between normative and informative text about the Other grammar rule (Issue #1100)
- Re: [whatwg/webidl] ExtendedAttributeList can match unbalanced ( ), [ ], and { } (Issue #1100)
- Re: [whatwg/webidl] ExtendedAttributeList can match unbalanced ( ), [ ], and { } (Issue #1100)
- Re: [whatwg/webidl] ExtendedAttributeList can match unbalanced ( ), [ ], and { } (Issue #1100)
- Re: [whatwg/webidl] ExtendedAttributeList can match unbalanced ( ), [ ], and { } (Issue #1100)
[whatwg/fetch] United Stated (Issue #1401)
[whatwg/dom] getComputedStyle should also be a method of the element (Issue #1057)
- Re: [whatwg/dom] getComputedStyle should also be a method of the element (Issue #1057)
- Re: [whatwg/dom] getComputedStyle should also be a method of the element (Issue #1057)
- Re: [whatwg/dom] getComputedStyle should also be a method of the element (Issue #1057)
Re: [w3c/ServiceWorker] How should import() work in service workers? (#1585)
Re: [whatwg/fetch] Streams based uploading with Content-Length (not chunked encoding) (#95)
Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005)
- Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005)
- Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005)
[whatwg/url] Editorial: address some minor nits (PR #686)
- Re: [whatwg/url] Editorial: address some minor nits (PR #686)
- Re: [whatwg/url] Editorial: address some minor nits (PR #686)
- Re: [whatwg/url] Editorial: address some minor nits (PR #686)
Re: [whatwg/fetch] Define the "Preload Cache" (#590)
[whatwg/fetch] Define the "memory cache" (Issue #1400)
- Re: [whatwg/fetch] Define the "memory cache" (Issue #1400)
- Re: [whatwg/fetch] Define the "memory cache" (Issue #1400)
- Re: [whatwg/fetch] Define the "memory cache" (Issue #1400)
Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156)
- Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156)
- Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156)
[w3c/gamepad] Use * as default allowlist (PR #159)
- Re: [w3c/gamepad] Use * as default allowlist (PR #159)
- Re: [w3c/gamepad] Use * as default allowlist (PR #159)
Re: [w3c/gamepad] getGamepad() check if doc is fully active (PR #157)
[whatwg/storage] Add a storage key comparison algorithm (PR #134)
- Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134)
- Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134)
- Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134)
- Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134)
- Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134)
- Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134)
- Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134)
- Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134)
- Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134)
- Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134)
Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389)
Re: [whatwg/fetch] Deprecate fetch (#28)
Re: [w3c/editing] Move to Jitsi for meetings? (Issue #385)
[w3c/editing] Update meeting invite link (PR #391)
- Re: [w3c/editing] Update meeting invite link (PR #391)
- Re: [w3c/editing] Update meeting invite link (PR #391)
- Re: [w3c/editing] Update meeting invite link (PR #391)
[whatwg/storage] Add an algorithm for comparing storage keys (Issue #133)
Re: [whatwg/fetch] CH processing, cross-origin redirects and service workers (#800)
Re: [whatwg/fetch] Client Hints infrastructure (#1072)
[w3c/editing] Add Feb 10 minutes (PR #390)
Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164)
Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359)
- Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359)
- Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359)
- Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359)
- Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359)
- Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359)
[w3c/editing] Updating video conferencing link to Jitsi (PR #389)
- Re: [w3c/editing] Updating video conferencing link to Jitsi (PR #389)
- Re: [w3c/editing] Updating video conferencing link to Jitsi (PR #389)
- Re: [w3c/editing] Updating video conferencing link to Jitsi (PR #389)
- Re: [w3c/editing] Updating video conferencing link to Jitsi (PR #389)
Re: [whatwg/fetch] Integrate early hints https://tools.ietf.org/html/rfc8297 (#1225)
- Re: [whatwg/fetch] Integrate early hints https://tools.ietf.org/html/rfc8297 (#1225)
- Re: [whatwg/fetch] Integrate early hints https://tools.ietf.org/html/rfc8297 (#1225)
- Re: [whatwg/fetch] Integrate early hints https://tools.ietf.org/html/rfc8297 (#1225)
Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696)
- Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696)
- Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696)
- Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696)
- Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696)
- Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696)
- Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696)
- Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696)
Re: [w3c/permissions] Add "popups" permission type (#210)
[whatwg/streams] Returning buffers to the underlying source (Issue #1217)
- Re: [whatwg/streams] Returning buffers to the underlying source (Issue #1217)
- Re: [whatwg/streams] Returning buffers to the underlying source (Issue #1217)
- Re: [whatwg/streams] Returning buffers to the underlying source (Issue #1217)
Re: [WICG/webcomponents] `customElements.upgrade` does not upgrade node subtrees cloned from `template` contents via `cloneNode` (Issue #946)
[w3c/permissions] Provide guidelines or heuristics to prevent fingerprinting in case permission is denied (Issue #361)
- Re: [w3c/permissions] Provide guidelines or heuristics to prevent fingerprinting in case permission is denied (Issue #361)
- Re: [w3c/permissions] Provide guidelines or heuristics to prevent fingerprinting in case permission is denied (Issue #361)
Re: [WICG/webcomponents] RfC: API design for aria delegation mechanism (#917)
Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
- Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)
Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
- Re: [whatwg/fetch] Integration with preload (PR #1342)
Re: [w3c/permissions] Definition of PermissionStatus lifetime (#266)
[w3c/permissions] Simplify CG model (PR #360)
- Re: [w3c/permissions] Simplify CG model (PR #360)
- Re: [w3c/permissions] Simplify CG model (PR #360)
- Re: [w3c/permissions] Simplify GC model (PR #360)
- Re: [w3c/permissions] Simplify GC model (PR #360)
- Re: [w3c/permissions] Simplify GC model (PR #360)
[w3c/permissions] Editorial: generalize statement about PermissionState emum (PR #359)
- Re: [w3c/permissions] Editorial: generalize statement about PermissionState emum (PR #359)
- Re: [w3c/permissions] Editorial: generalize statement about PermissionState emum (PR #359)
[w3c/permissions] Tidied up document using tidy-html5 (PR #358)
- Re: [w3c/permissions] Tidied up document using tidy-html5 (PR #358)
- Re: [w3c/permissions] Tidied up document using tidy-html5 (PR #358)
- Re: [w3c/permissions] Tidied up document using tidy-html5 (PR #358)
Re: [w3c/permissions] Proposals: Drop "Powerful features registry" and PermissionName enum (Issue #314)
[w3c/permissions] Editorial: make 'Creating instances' an algorithm (PR #357)
- Re: [w3c/permissions] Editorial: make 'Creating instances' an algorithm (PR #357)
- Re: [w3c/permissions] Editorial: make 'Creating instances' an algorithm (PR #357)
- Re: [w3c/permissions] Editorial: make 'Creating instances' an algorithm (PR #357)
- Re: [w3c/permissions] Editorial: make 'Creating instances' an algorithm (PR #357)
[whatwg/streams] Add tests for interaction between autoAllocateChunkSize and respondWithNewView (PR #1216)
- Re: [whatwg/streams] Add tests for interaction between autoAllocateChunkSize and respondWithNewView (PR #1216)
- Re: [whatwg/streams] Add tests for interaction between autoAllocateChunkSize and respondWithNewView (PR #1216)
- Re: [whatwg/streams] Add tests for interaction between autoAllocateChunkSize and respondWithNewView (PR #1216)
Re: [whatwg/url] Support IPv6 zone identifiers (#392)
[whatwg/dom] Walace Oliveira Branco (Issue #1056)
Re: [whatwg/streams] ReadableStream.prototype.pipeline(...) (Issue #1184)
Re: [w3c/ServiceWorker] Declarative routing (#1373)
Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756)
[whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
- Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132)
Re: [w3ctag/design-reviews] Compute Pressure API (#621)
- Re: [w3ctag/design-reviews] Compute Pressure API (#621)
- Re: [w3ctag/design-reviews] Compute Pressure API (#621)
Re: [whatwg/xhr] Resource Timing integration (#319)
- Re: [whatwg/xhr] Resource Timing integration (#319)
- Re: [whatwg/xhr] Resource Timing integration (#319)
- Re: [whatwg/xhr] Resource Timing integration (#319)
- Re: [whatwg/xhr] Resource Timing integration (#319)
- Re: [whatwg/xhr] Resource Timing integration (#319)
- Re: [whatwg/xhr] Resource Timing integration (#319)
- Re: [whatwg/xhr] Resource Timing integration (#319)
- Re: [whatwg/xhr] Resource Timing integration (#319)
- Re: [whatwg/xhr] Resource Timing integration (#319)
- Re: [whatwg/xhr] Resource Timing integration (#319)
- Re: [whatwg/xhr] Resource Timing integration (#319)
[whatwg/encoding] Ending (Issue #281)
Re: [whatwg/dom] General DOM effect/Object mutation DOM effect (Issue #1049)
Re: [w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695)
- Re: [w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695)
- Re: [w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695)
- Re: [w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695)
Re: [w3ctag/design-reviews] Region Capture (Issue #710)
Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703)
- Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703)
- Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703)
- Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703)
- Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703)
- Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703)
- Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703)
- Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703)
- Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703)
- Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703)
Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523)
Re: [w3ctag/design-reviews] Modification of selection APIs to account for shadow dom (Issue #694)
Re: [w3ctag/design-reviews] AbortSignal.timeout() (Issue #711)
Re: [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708)
- Re: [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708)
- Re: [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708)
- Re: [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708)
Re: [w3ctag/design-reviews] Review request before CR: CSS `selector()` (Issue #709)
Re: [w3c/editing] Expose keyboard language? (#351)
- Re: [w3c/editing] Expose keyboard language? (#351)
- Re: [w3c/editing] Expose keyboard language? (#351)
Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675)
- Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675)
- Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675)
- Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675)
- Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675)
- Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675)
- Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675)
- Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675)
- Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675)
- Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675)
Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329)
- Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329)
- Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329)
- Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329)
- Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329)
- Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329)
- Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329)
- Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329)
[whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
- Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
- Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
- Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
- Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
[whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097)
- Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097)
- Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097)
- Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097)
- Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097)
- Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097)
- Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097)
- Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097)
- Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097)
- Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097)
- Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097)
Re: [whatwg/fetch] Use case for Headers getAll (#973)
[w3c/permissions] Further alignment with Permissions Policy (Issue #356)
Re: [w3c/permissions] Rename PermissionName enum to PowerfulFeatureName (#286)
Re: [w3c/editing] EditContext: Are the events for `EditContext` propagated in the DOM tree? (#341)
[whatwg/webidl] ไทยพาณิชย์ (Issue #1096)
Re: [WICG/webcomponents] Scoped Custom Element Registries (#716)
- Re: [WICG/webcomponents] Scoped Custom Element Registries (#716)
- Re: [WICG/webcomponents] Scoped Custom Element Registries (#716)
- Re: [WICG/webcomponents] Scoped Custom Element Registries (#716)
Re: [w3c/manifest] BREAKING CHANGE: Replace "badge" with "monochrome" (#833) (2c55d86)
[whatwg/fetch] make Response and Headers serializable (Issue #1399)
Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150)
- Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150)
- Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150)
- Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150)
- Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150)
- Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150)
[whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055)
- Re: [whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055)
- Re: [whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055)
- Re: [whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055)
- Re: [whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055)
- Re: [whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055)
Re: [w3c/permissions] Add a fourth permission state "grantable without a prompt"? (#250)
[w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
Re: [w3c/permissions] Semantic Permission Bundles (#191)
- Re: [w3c/permissions] Semantic Permission Bundles (#191)
- Re: [w3c/permissions] Semantic Permission Bundles (#191)
- Re: [w3c/permissions] Semantic Permission Bundles (#191)
[w3c/permissions] Editorial: cleanup Permissions model (PR #355)
- Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355)
- Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355)
- Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355)
- Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355)
- Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355)
- Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355)
[w3c/permissions] Add concept of Default Permission State (PR #354)
- Re: [w3c/permissions] Add concept of Default Permission State (PR #354)
- Re: [w3c/permissions] Add concept of Default Permission State (PR #354)
- Re: [w3c/permissions] Add concept of Default Permission State (PR #354)
- Re: [w3c/permissions] Add concept of Default Permission State (PR #354)
[w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
- Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353)
[w3c/permissions] Editorial: run 'in parallel', not asynchronously (PR #352)
- Re: [w3c/permissions] Editorial: run 'in parallel', not asynchronously (PR #352)
- Re: [w3c/permissions] Editorial: run 'in parallel', not asynchronously (PR #352)
[w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351)
- Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351)
- Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351)
- Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351)
- Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351)
- Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351)
- Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351)
- Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351)
[w3c/permissions] Editorial: cleanup examples (PR #350)
- Re: [w3c/permissions] Editorial: cleanup examples (PR #350)
- Re: [w3c/permissions] Editorial: cleanup examples (PR #350)
- Re: [w3c/permissions] Editorial: cleanup examples (PR #350)
- Re: [w3c/permissions] Editorial: cleanup examples (PR #350)
- Re: [w3c/permissions] Editorial: cleanup examples (PR #350)
[w3c/permissions] Automation: "Get Permission" (#349)
[w3c/permissions] Automation: "set permission" granularity (#348)
[w3c/permissions] Automation: Need two more steps to handle closed browsing context and user prompts (#347)
[w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346)
- Re: [w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346)
- Re: [w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346)
- Re: [w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346)
- Re: [w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346)
- Re: [w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346)
[w3c/permissions] Editorial: clean up abstract (PR #345)
- Re: [w3c/permissions] Editorial: clean up abstract (PR #345)
- Re: [w3c/permissions] Editorial: clean up abstract (PR #345)
- Re: [w3c/permissions] Editorial: clean up abstract (PR #345)
Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384)
- Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384)
- Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384)
- Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384)
[whatwg/streams] Add WritableStream's signal definition for other specs (PR #1215)
- Re: [whatwg/streams] Add WritableStream's signal definition for other specs (PR #1215)
- Re: [whatwg/streams] Add WritableStream's signal definition for other specs (PR #1215)
- Re: [whatwg/streams] Add WritableStream's signal definition for other specs (PR #1215)
Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026)
[whatwg/dom] Should AbortSignal.timeout only be exposed on (Window, Worker)? (Issue #1054)
- Re: [whatwg/dom] Should AbortSignal.timeout only be exposed on (Window, Worker)? (Issue #1054)
- Re: [whatwg/dom] Should AbortSignal.timeout only be exposed on (Window, Worker)? (Issue #1054)
Re: [w3c/FileAPI] Include file creation time and last access time. (#26)
Re: [w3c/manifest] Why is purpose a "unordered set of unique space-separated tokens"? (#903)
- Re: [w3c/manifest] Why is purpose a "unordered set of unique space-separated tokens"? (#903)
- Re: [w3c/manifest] Why is purpose a "unordered set of unique space-separated tokens"? (#903)
Re: [w3c/manifest] Status report and planning for TPAC 2021 (#999)
Re: [w3c/FileAPI] Consider Blob.fromStream (returns a Promise<Blob>) (#140)
Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
- Re: [whatwg/url] Support relative URLs (#531)
[w3c/clipboard-apis] Should `clipboard.writeText()` replace `\n` characters with `\r\n` on Windows? (Issue #168)
- Re: [w3c/clipboard-apis] Should `clipboard.writeText()` replace `\n` characters with `\r\n` on Windows? (Issue #168)
- Re: [w3c/clipboard-apis] Should `clipboard.writeText()` replace `\n` characters with `\r\n` on Windows? (Issue #168)
[w3c/manifest] Link to manifest-app-info in the README (PR #1030)
- Re: [w3c/manifest] Link to manifest-app-info in the README (PR #1030)
- Re: [w3c/manifest] Link to manifest-app-info in the README (PR #1030)
Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
- Re: [w3c/manifest] Describe manifest update behavior (#1011)
Re: [whatwg/webidl] Introduce "mark as handled" for promises (PR #1090)
- Re: [whatwg/webidl] Introduce "mark as handled" for promises (PR #1090)
- Re: [whatwg/webidl] Introduce "mark as handled" for promises (PR #1090)
Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951)
Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032)
[whatwg/fetch] Merging Client Hints Infrastructure into FETCH (and HTML) Standards (Issue #1398)
- Re: [whatwg/fetch] Merging Client Hints Infrastructure into FETCH (and HTML) Standards (Issue #1398)
Re: [w3ctag/design-reviews] [mediaqueries-4] Range contexts (Issue #707)
Re: [w3ctag/design-reviews] [css-values-4] The Large, Small, and Dynamic Viewport Sizes (Issue #706)
Re: [w3ctag/design-reviews] Priority Hints API (Issue #704)
- Re: [w3ctag/design-reviews] Priority Hints API (Issue #704)
- Re: [w3ctag/design-reviews] Priority Hints API (Issue #704)
- Re: [w3ctag/design-reviews] Priority Hints API (Issue #704)
- Re: [w3ctag/design-reviews] Priority Hints API (Issue #704)
- Re: [w3ctag/design-reviews] Priority Hints API (Issue #704)
- Re: [w3ctag/design-reviews] Priority Hints API (Issue #704)
- Re: [w3ctag/design-reviews] Priority Hints API (Issue #704)
- Re: [w3ctag/design-reviews] Priority Hints API (Issue #704)
[whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131)
- Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131)
- Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131)
- Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131)
- Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131)
- Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131)
- Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131)
- Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131)
Re: [w3c/manifest] Link to manifest-app-info in the README (Issue #1027)
- Re: [w3c/manifest] Link to manifest-app-info in the README (Issue #1027)
- Re: [w3c/manifest] Link to manifest-app-info in the README (Issue #1027)
- Re: [w3c/manifest] Link to manifest-app-info in the README (Issue #1027)
[whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397)
- Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397)
- Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397)
- Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397)
Re: [w3c/clipboard-apis] supported type should include MathML types (#141)
[w3c/clipboard-apis] Clipboard Pickling: should the unsanitized option support a way to ask for all representations to be unsanitized? (Issue #167)
- Re: [w3c/clipboard-apis] Clipboard Pickling: should the unsanitized option support a way to ask for all representations to be unsanitized? (Issue #167)
- Re: [w3c/clipboard-apis] Clipboard Pickling: should the unsanitized option support a way to ask for all representations to be unsanitized? (Issue #167)
- Re: [w3c/clipboard-apis] Clipboard Pickling: should the unsanitized option support a way to ask for all representations to be unsanitized? (Issue #167)
- Re: [w3c/clipboard-apis] Clipboard Pickling: should the unsanitized option support a way to ask for all representations to be unsanitized? (Issue #167)
[w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344)
- Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344)
- Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344)
- Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344)
- Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344)
- Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344)
- Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344)
[w3ctag/design-reviews] Review request for Confirmation of Action API (Issue #713)
Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166)
- Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166)
- Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166)
- Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166)
- Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166)
- Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166)
Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686)
- Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686)
- Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686)
- Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686)
- Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686)
- Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686)
- Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686)
- Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686)
- Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686)
- Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686)
[whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214)
- Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214)
- Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214)
- Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214)
- Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214)
- Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214)
- Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214)
- Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214)
- Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214)
Re: [whatwg/webidl] Force `[NewObject]` for Promise returning functions? (Issue #1084)
Re: [whatwg/fetch] Add `Response.json` static method (PR #1392)
- Re: [whatwg/fetch] Add `Response.json` static method (PR #1392)
- Re: [whatwg/fetch] Add `Response.json` static method (PR #1392)
- Re: [whatwg/fetch] Add `Response.json` static method (PR #1392)
- Re: [whatwg/fetch] Add `Response.json` static method (PR #1392)
- Re: [whatwg/fetch] Add `Response.json` static method (PR #1392)
[whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094)
- Re: [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094)
- Re: [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094)
- Re: [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094)
- Re: [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094)
- Re: [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094)