[w3ctag/design-reviews] Mirror design reviews to a private discussion repository (PR #987)
[w3c/manifest] launch handling, and adding a "service-worker" client-mode (Issue #1143)
Re: [w3ctag/design-reviews] Before 6 August 2023 -- Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) - Google Chrome - Daniel (w3.org) (Issue #973)
- Re: [w3ctag/design-reviews] Before 6 August 2023 -- Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) - Google Chrome - Daniel (w3.org) (Issue #973)
- Re: [w3ctag/design-reviews] Before 6 August 2023 -- Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) - Google Chrome - Daniel (w3.org) (Issue #973)
Re: [w3ctag/design-reviews] Requesting review of HTML Ruby Markup Extensions (Issue #959)
Re: [w3ctag/design-reviews] WebAssembly JavaScript Promise Integration API (Issue #809)
Re: [w3ctag/design-reviews] Specification review for CSS Anchor Positioning (Issue #848)
[whatwg/fetch] Anchor permanence for integration with compression dictionary spec? (Issue #1771)
- Re: [whatwg/fetch] Anchor permanence for integration with compression dictionary spec? (Issue #1771)
- Re: [whatwg/fetch] Anchor permanence for integration with compression dictionary spec? (Issue #1771)
- Re: [whatwg/fetch] Anchor permanence for integration with compression dictionary spec? (Issue #1771)
- Re: [whatwg/fetch] Anchor permanence for integration with compression dictionary spec? (Issue #1771)
- Re: [whatwg/fetch] Anchor permanence for integration with compression dictionary spec? (Issue #1771)
Re: [whatwg/webidl] Move to WHATWG (#1016)
- Re: [whatwg/webidl] Move to WHATWG (#1016)
- Re: [whatwg/webidl] Move to WHATWG (#1016)
- Re: [whatwg/webidl] Move to WHATWG (#1016)
- Re: [whatwg/webidl] Move to WHATWG (#1016)
- Re: [whatwg/webidl] Move to WHATWG (#1016)
- Re: [whatwg/webidl] Move to WHATWG (#1016)
[w3ctag/design-reviews] Early Design Review: Lightweight FedCM (Issue #986)
- Re: [w3ctag/design-reviews] Early Design Review: Lightweight FedCM (Issue #986)
- Re: [w3ctag/design-reviews] Early Design Review: Lightweight FedCM (Issue #986)
- Re: [w3ctag/design-reviews] Early Design Review: Lightweight FedCM (Issue #986)
- Re: [w3ctag/design-reviews] Early Design Review: Lightweight FedCM (Issue #986)
[w3c/ServiceWorker] Sandboxing untrusted code offline is currently impossible (Issue #1727)
[w3c/ServiceWorker] Normative references to discontinued specs in Service Workers Nightly (Issue #1726)
[w3c/push-api] Normative references to discontinued specs in Push API (Issue #390)
[w3ctag/design-reviews] Realms Initialization Control (Issue #985)
- Re: [w3ctag/design-reviews] Realms Initialization Control (Issue #985)
- Re: [w3ctag/design-reviews] Realms Initialization Control (Issue #985)
Re: [w3ctag/design-reviews] Element Capture (Issue #954)
Re: [whatwg/webidl] add [[ErrorData]] slot to DOMExceptions (PR #1421)
- Re: [whatwg/webidl] add [[ErrorData]] slot to DOMExceptions (PR #1421)
- Re: [whatwg/webidl] add [[ErrorData]] slot to DOMExceptions (PR #1421)
- Re: [whatwg/webidl] add [[ErrorData]] slot to DOMExceptions (PR #1421)
- Re: [whatwg/webidl] add [[ErrorData]] slot to DOMExceptions (PR #1421)
- Re: [whatwg/webidl] add [[ErrorData]] slot to DOMExceptions (PR #1421)
- Re: [whatwg/webidl] add [[ErrorData]] slot to DOMExceptions (PR #1421)
- Re: [whatwg/webidl] add [[ErrorData]] slot to DOMExceptions (PR #1421)
- Re: [whatwg/webidl] add [[ErrorData]] slot to DOMExceptions (PR #1421)
Re: [whatwg/dom] Should EventInit contain 'timestamp'? (#76)
[whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
[w3c/DOM-Parsing] Serializing outerHTML of an HTML node that got adopted by an XML document (Issue #85)
[w3c/ServiceWorker] expose installed service worker script contents (Issue #1725)
[w3c/DOM-Parsing] Provide an API to serialize with the "require well-formed" parameter set to true (Issue #84)
[whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
Re: [w3ctag/design-reviews] text-wrap: pretty (Issue #864)
- Re: [w3ctag/design-reviews] text-wrap: pretty (Issue #864)
- Re: [w3ctag/design-reviews] text-wrap: pretty (Issue #864)
[w3c/uievents] Remove definitions of MutationEvent and friends (PR #381)
Re: [w3ctag/design-reviews] Private Aggregation API (Issue #846)
[w3c/push-api] Holding "Fire a Functional Event" incorrectly (Issue #389)
[w3c/push-api] Push subscriptions are not associated with service workers (PR #388)
[w3c/push-api] Editorial: clarify Receiving a Push Message (PR #387)
[w3c/push-api] How to compute number of views for the push notifications sent? (Issue #386)
- Re: [w3c/push-api] How to compute number of views for the push notifications sent? (Issue #386)
- Re: [w3c/push-api] How to compute number of views for the push notifications sent? (Issue #386)
- Re: [w3c/push-api] How to compute number of views for the push notifications sent? (Issue #386)
[w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
Re: [whatwg/fetch] Allow request take AsyncIterable body? (#1291)
[w3c/manifest] Clarify case-insensitive parsing for enum values (Issue #1142)
- Re: [w3c/manifest] Clarify case-insensitive parsing for enum values (Issue #1142)
- Re: [w3c/manifest] Clarify case-insensitive parsing for enum values (Issue #1142)
Re: [whatwg/webidl] Named properties object / named property visibility algorithm with property on Window.prototype (#607)
[whatwg/webidl] Intent to use Constants (Issue #1428)
Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
[whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
Re: [whatwg/fetch] Handling Partial Content / 206 (#144)
[whatwg/url] `URLSearchParams.set()` accepts an array as value in Firefox & Chrome but it's nowhere documented (Issue #833)
- Re: [whatwg/url] `URLSearchParams.set()` accepts an array as value in Firefox & Chrome but this is nowhere documented (Issue #833)
- Re: [whatwg/url] `URLSearchParams.set()` accepts an array as value in Firefox & Chrome but this is nowhere documented (Issue #833)
- Re: [whatwg/url] `URLSearchParams.set()` accepts an array as value in Firefox & Chrome but this is nowhere documented (Issue #833)
- Re: [whatwg/url] `URLSearchParams.set()` accepts an array as value in Firefox & Chrome but this is nowhere documented (Issue #833)
[whatwg/webidl] export "is a platform object" (PR #1427)
[WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072)
- Re: [WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072)
- Re: [WICG/webcomponents] Reference Target: Should the `form` and `list` JavaScript attributes return the host element? (Issue #1072)
[WICG/webcomponents] Reference Target: How to handle invalid ID references? (Issue #1071)
[w3c/manifest] Editorial: Trim `dir`, `display`, `orientation`, text and color values (PR #1140)
- Re: [w3c/manifest] Editorial: Trim `dir`, `display`, `orientation`, text and color values (PR #1140)
[w3c/ServiceWorker] "Batch Cache Operations" contains a parable that confuses me (Issue #1724)
Re: [w3c/permissions] Editorial: Fix sentences around permission states (PR #452)
[w3ctag/design-reviews] 88828282882 (Issue #984)
Re: [w3ctag/design-reviews] JS String Builtins for WebAssembly (Issue #940)
Re: [w3c/ServiceWorker] The unnecessary limitations of the Cache.put API leads to users inventing work-arounds (Issue #1643)
Re: [whatwg/url] Should file URLs have opaque hostnames? (#599)
- Re: [whatwg/url] Should file URLs have opaque hostnames? (#599)
- Re: [whatwg/url] Should file URLs have opaque hostnames? (#599)
- Re: [whatwg/url] Should file URLs have opaque hostnames? (#599)
- Re: [whatwg/url] Should file URLs have opaque hostnames? (#599)
Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
[whatwg/dom] Corrected the variable's name from 'element' to 'result'. (PR #1306)
- Re: [whatwg/dom] Corrected the variable's name from 'element' to 'result'. (PR #1306)
- Re: [whatwg/dom] Corrected the variable's name from 'element' to 'result'. (PR #1306)
Re: [whatwg/url] Differentiate from zero-sized fragment and no fragment in url (Issue #779)
Re: [w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169)
- Re: [w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169)
- Re: [w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169)
- Re: [w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169)
Re: [whatwg/webidl] Stop assuming "transfer" is same-agent cluster (PR #1422)
Re: [whatwg/fullscreen] Clarification for Accessibility requested (#197)
- Re: [whatwg/fullscreen] Clarification for Accessibility requested (#197)
- Re: [whatwg/fullscreen] Clarification for Accessibility requested (#197)
Re: [whatwg/dom] AbortSignal.any() assertion failure (Issue #1293)
[w3ctag/design-reviews] WebXR Device API (delta/aiming 2nd CRS) (Issue #983)
Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975)
Re: [w3ctag/design-reviews] Support Video Chapter in MediaMetadata (Issue #952)
Re: [w3ctag/design-reviews] Spec review for Snap Events (Issue #943)
[WICG/webcomponents] event.composedPath()[0] can be very slow: add event.composedTarget? (Issue #1070)
- Re: [WICG/webcomponents] event.composedPath()[0] can be very slow: add event.composedTarget? (Issue #1070)
- Re: [WICG/webcomponents] event.composedPath()[0] can be very slow: add event.composedTarget? (Issue #1070)
[whatwg/streams] Propagate reason argument to resolved promise of cancel algorithm (PR #1324)
- Re: [whatwg/streams] Propagate reason argument to resolved promise of cancel algorithm (PR #1324)
- Re: [whatwg/streams] Propagate reason argument to resolved promise of cancel algorithm (PR #1324)
- Re: [whatwg/streams] Propagate reason argument to resolved promise of cancel algorithm (PR #1324)
[w3c/clipboard-apis] Add link to explainer doc for clipboardchange event (PR #221)
Re: [WICG/webcomponents] declarative-custom-elements: fix error with script export (#887)
Re: [WICG/webcomponents] fix example so that attachShadow does not throw an exception (#632)
Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989)
Re: [w3ctag/design-reviews] Speculation rules: target_hint field (Issue #931)
- Re: [w3ctag/design-reviews] Speculation rules: target_hint field (Issue #931)
- Re: [w3ctag/design-reviews] Speculation rules: target_hint field (Issue #931)
Re: [whatwg/fetch] Block access to ::, ::ffff:0:0, and 0.0.0.0 (PR #1763)
- Re: [whatwg/fetch] Block access to ::, ::ffff:0:0, and 0.0.0.0 (PR #1763)
- Re: [whatwg/fetch] Block access to ::, ::ffff:0:0, and 0.0.0.0 (PR #1763)
- Re: [whatwg/fetch] Block access to ::, ::ffff:0:0, and 0.0.0.0 (PR #1763)
Re: [whatwg/fetch] Block access to :: and 0.0.0.0 (PR #1763)
- Re: [whatwg/fetch] Block access to :: and 0.0.0.0 (PR #1763)
- Re: [whatwg/fetch] Block access to :: and 0.0.0.0 (PR #1763)
- Re: [whatwg/fetch] Block access to :: and 0.0.0.0 (PR #1763)
[whatwg/fetch] Make get, decode, and split handle a trailing comma correctly (PR #1769)
- Re: [whatwg/fetch] Make get, decode, and split handle a trailing comma correctly (PR #1769)
- Re: [whatwg/fetch] Make get, decode, and split handle a trailing comma correctly (PR #1769)
- Re: [whatwg/fetch] Make get, decode, and split handle a trailing comma correctly (PR #1769)
- Re: [whatwg/fetch] Make get, decode, and split handle a trailing comma correctly (PR #1769)
- Re: [whatwg/fetch] Make get, decode, and split handle edge cases correctly (PR #1769)
- Re: [whatwg/fetch] Make get, decode, and split handle edge cases correctly (PR #1769)
- Re: [whatwg/fetch] Make get, decode, and split handle edge cases correctly (PR #1769)
- Re: [whatwg/fetch] Make get, decode, and split handle edge cases correctly (PR #1769)
[whatwg/streams] Handeling backpressure on the Readable side of a transform stream (Issue #1323)
- Re: [whatwg/streams] Handeling backpressure on the Readable side of a transform stream (Issue #1323)
- Re: [whatwg/streams] Handeling backpressure on the Readable side of a transform stream (Issue #1323)
- Re: [whatwg/streams] Handeling backpressure on the Readable side of a transform stream (Issue #1323)
- Re: [whatwg/streams] Handeling backpressure on the Readable side of a transform stream (Issue #1323)
[whatwg/url] Review Draft Publication: August 2024 (PR #832)
[whatwg/streams] Review Draft Publication: August 2024 (PR #1322)
- Re: [whatwg/streams] Review Draft Publication: August 2024 (PR #1322)
- Re: [whatwg/streams] Review Draft Publication: August 2024 (PR #1322)
Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578)
[whatwg/fetch] "get, decode, and split" doesn't return example output (Issue #1768)
- Re: [whatwg/fetch] "get, decode, and split" doesn't return example output (Issue #1768)
- Re: [whatwg/fetch] "get, decode, and split" doesn't return example output (Issue #1768)
- Re: [whatwg/fetch] "get, decode, and split" doesn't return example output (Issue #1768)
Re: [w3c/uievents] Need virtual key codes (Issue #377)
Re: [WICG/webcomponents] Upstreaming Shadow DOM and outstanding v1 work (#661)
Re: [WICG/webcomponents] Close this repository in the future (#652)
Re: [WICG/webcomponents] css-modules: fix typo (#943)
Re: [WICG/webcomponents] CR/LF fix at end of document (#851)
Re: [WICG/webcomponents] update to use import attributes syntax (PR #1039)
Re: [WICG/webcomponents] April 2024 DOM Parts Quarterly Meeting (Issue #1047)
Re: [WICG/webcomponents] Modify :is() and :where() to support selecting derived node types (Issue #1037)
Re: [WICG/webcomponents] TPAC Web Components Community Group Breakout Takeaways (Issue #1026)
Re: [WICG/webcomponents] RFC: Element Handles for Cross-root ARIA (cross-post from wicg/aom) (Issue #1020)
Re: [WICG/webcomponents] 2023 TPAC F2F discussion? (Issue #1018)
Re: [WICG/webcomponents] Spring 2023 Styling and Theming F2F (Issue #1006)
Re: [WICG/webcomponents] Is this still an "incubation"? (Issue #984)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
Re: [WICG/webcomponents] TPAC 2022 Web Components Meeting(s) (Issue #966)
Re: [WICG/webcomponents] TPAC 2021 Web Components Meeting (#944)
Re: [WICG/webcomponents] State of all of the proposals. (#928)
Re: [WICG/webcomponents] RfC: API design for aria delegation mechanism (#917)
Re: [WICG/webcomponents] Add delegatesLabel and a content attribute to specify the label element within a shadow tree (#916)
Re: [WICG/webcomponents] RfC: An alternative approach to accessibility across shadow boundaries (#898)
Re: [WICG/webcomponents] Web Components-related breakouts @ TPAC 2020 (#877)
Re: [WICG/webcomponents] odd custom element placement (#869)
Re: [WICG/webcomponents] Deprecation warning misleading. (#818)
Re: [WICG/webcomponents] Custom pseudo-classes for host elements via shadow roots (:state) (#738)
Re: [WICG/webcomponents] registry: Add an API to retrieve the localName given a custom element constructor (#566)
Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883)
- Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883)
- Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883)
- Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883)
[whatwg/fetch] Add Range to no-cors safelisted headers (Issue #1767)
- Re: [whatwg/fetch] Add Range to no-cors safelisted headers (Issue #1767)
- Re: [whatwg/fetch] Add Range to no-cors safelisted headers (Issue #1767)
[WICG/webcomponents] [templates] A JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
- Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
Re: [WICG/webcomponents] Proposal: Allow custom elements to be in any namespace (#634)
[WICG/webcomponents] Reference Target, level 2 (Issue #1068)
Re: [w3c/IndexedDB] How should IDB connections and outstanding IDB transactions behave when a page enters back/forward cache? (Issue #381)
Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
- Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)
Re: [whatwg/fetch] Allow range header without preflight (#1312)
[w3c/manifest] systray support and web install topics for manifest spec. (Issue #1139)
[w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
- Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)
Re: [w3ctag/design-reviews] Add Skip-Ad media session action (Issue #957)
Re: [w3ctag/design-reviews] Shared Storage API (Issue #747)
[w3ctag/design-reviews] Early design review: Storage Access Headers (Issue #982)
- Re: [w3ctag/design-reviews] Early design review: Storage Access Headers (Issue #982)
- Re: [w3ctag/design-reviews] Early design review: Storage Access Headers (Issue #982)
Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
- Re: [whatwg/dom] Mark dependent abort signals as aborted before firing events (PR #1295)
[whatwg/dom] Correct doAmazingness() example (PR #1305)
- Re: [whatwg/dom] Correct doAmazingness() example (PR #1305)
- Re: [whatwg/dom] Correct doAmazingness() example (PR #1305)
Re: [whatwg/dom] Trusted types attributes (PR #1268)
[whatwg/dom] Correct lookupPrefix() after fourteen years (PR #1304)
- Re: [whatwg/dom] Correct lookupPrefix() after fourteen years (PR #1304)
- Re: [whatwg/dom] Correct lookupPrefix() after fourteen years (PR #1304)
[w3c/manifest] "link capturing" on the web platform into an installed web app (Issue #1138)
Re: [whatwg/dom] Update element.attributes getter steps to be less vague (PR #1297)
- Re: [whatwg/dom] Update element.attributes getter steps to be less vague (PR #1297)
- Re: [whatwg/dom] Update element.attributes getter steps to be less vague (PR #1297)
- Re: [whatwg/dom] Update element.attributes getter steps to be less vague (PR #1297)
- Re: [whatwg/dom] Update element.attributes getter steps to be less vague (PR #1297)
- Re: [whatwg/dom] Update element.attributes getter steps to be less vague (PR #1297)
Re: [whatwg/dom] Revert "Trusted Types integration for "converting nodes into a node"" (PR #1299)
Re: [whatwg/dom] Consider adding localNameFilter to MutationObserver (#398)
Re: [whatwg/fetch] Tighten `application/x-www-form-urlencoded` CORS safe-list carveout? (Issue #1706)
[whatwg/fetch] Spec WWW-Authenticate and Proxy-Authenticate handling in HTTP-network-or-cache fetch (Issue #1766)
[w3ctag/design-reviews] Call stacks in crash reports from unresponsive web pages (Issue #981)
[whatwg/dom] Editorial: Update to use new "report an exception" algorithm in HTML (PR #1303)
- Re: [whatwg/dom] Editorial: Update to use new "report an exception" algorithm in HTML (PR #1303)
- Re: [whatwg/dom] Editorial: Update to use new "report an exception" algorithm in HTML (PR #1303)
- Re: [whatwg/dom] Editorial: Update to use new "report an exception" algorithm in HTML (PR #1303)
- Re: [whatwg/dom] Editorial: Update to use new "report an exception" algorithm in HTML (PR #1303)
- Re: [whatwg/dom] Editorial: Update to use new "report an exception" algorithm in HTML (PR #1303)
- Re: [whatwg/dom] Update to use new "report an exception" algorithm in HTML (PR #1303)
- Re: [whatwg/dom] Update to use new "report an exception" algorithm in HTML (PR #1303)
- Re: [whatwg/dom] Update to use new "report an exception" algorithm in HTML (PR #1303)
- Re: [whatwg/dom] Update to use new "report an exception" algorithm in HTML (PR #1303)
- Re: [whatwg/dom] Update to use new "report an exception" algorithm in HTML (PR #1303)
[WICG/webcomponents] Reference Target: Clarify the Live References section (PR #1067)
- Re: [WICG/webcomponents] Reference Target: Clarify the Live References section (PR #1067)
- Re: [WICG/webcomponents] Reference Target: Clarify the Live References section (PR #1067)
[WICG/webcomponents] Reference Target: Clarify how JS Element attributes work with referenceTarget (PR #1066)
- Re: [WICG/webcomponents] Reference Target: Clarify how JS Element attributes work with referenceTarget (PR #1066)
- Re: [WICG/webcomponents] Reference Target: Clarify how JS Element attributes work with referenceTarget (PR #1066)
- Re: [WICG/webcomponents] Reference Target: Clarify how JS Element attributes work with referenceTarget (PR #1066)
- Re: [WICG/webcomponents] Reference Target: Clarify how JS Element attributes work with referenceTarget (PR #1066)
- Re: [WICG/webcomponents] Reference Target: Clarify how JS Element attributes work with referenceTarget (PR #1066)
- Re: [WICG/webcomponents] Reference Target: Clarify how JS Element attributes work with referenceTarget (PR #1066)
- Re: [WICG/webcomponents] Reference Target: Clarify how JS Element attributes work with referenceTarget (PR #1066)
Re: [w3ctag/design-reviews] View Transitions: list of types (Issue #908)
[WICG/webcomponents] 2024 TPAC planning (Issue #1065)
- Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065)
- Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065)
- Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065)
- Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065)
- Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065)
- Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065)
- Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065)
- Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065)
- Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065)
Re: [w3ctag/design-reviews] Web Install API - Same Origin (Issue #888)
- Re: [w3ctag/design-reviews] Web Install API - Same Origin (Issue #888)
- Re: [w3ctag/design-reviews] Web Install API - Same Origin (Issue #888)
- Re: [w3ctag/design-reviews] Web Install API - Same Origin (Issue #888)
- Re: [w3ctag/design-reviews] Web Install API - Same Origin (Issue #888)
- Re: [w3ctag/design-reviews] Web Install API - Same Origin (Issue #888)
- Re: [w3ctag/design-reviews] Web Install API - Same Origin (Issue #888)
Re: [w3ctag/design-reviews] Web Install API - Cross-Origin (Issue #946)
[whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)
- Re: [whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)
- Re: [whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)
- Re: [whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)
- Re: [whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)
- Re: [whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)
- Re: [whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)
- Re: [whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)
- Re: [whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)
- Re: [whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)
- Re: [whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)
Re: [whatwg/xhr] Update link for fragment serialization algorithm (PR #390)
[whatwg/url] Should parsing take into account state override on port overflow (Issue #831)
- Re: [whatwg/url] Should parsing take into account state override on port overflow (Issue #831)
- Re: [whatwg/url] Should parsing take into account state override on port overflow (Issue #831)
- Re: [whatwg/url] Should parsing take into account state override on port overflow (Issue #831)
Re: [whatwg/encoding] Fast byteLength() (Issue #333)
- Re: [whatwg/encoding] Fast byteLength() (Issue #333)
- Re: [whatwg/encoding] Fast byteLength() (Issue #333)
- Re: [whatwg/encoding] Fast byteLength() (Issue #333)
Re: [w3c/push-api] Expose pushManager on Navigator (PR #368)
- Re: [w3c/push-api] Expose pushManager on Navigator (PR #368)
- Re: [w3c/push-api] Expose pushManager on Navigator (PR #368)
- Re: [w3c/push-api] Expose pushManager on Navigator (PR #368)
- Re: [w3c/push-api] Expose pushManager on Navigator (PR #368)
[whatwg/storage] Create SECURITY.md (PR #175)
[whatwg/dom] Missing arguments for “locate a namespace prefix” in `lookupPrefix` steps (Issue #1302)
- Re: [whatwg/dom] Missing arguments for “locate a namespace prefix” in `lookupPrefix` steps (Issue #1302)
- Re: [whatwg/dom] Missing arguments for “locate a namespace prefix” in `lookupPrefix` steps (Issue #1302)
Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270)
- Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270)
- Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270)
Re: [WICG/webcomponents] Simplified custom element definition (Issue #1064)
Re: [whatwg/fetch] Block access to 0.0.0.0 (PR #1763)
- Re: [whatwg/fetch] Block access to 0.0.0.0 (PR #1763)
- Re: [whatwg/fetch] Block access to 0.0.0.0 (PR #1763)
- Re: [whatwg/fetch] Block access to 0.0.0.0 (PR #1763)
[whatwg/url] Sssodha (Issue #830)
Re: [w3c/uievents] Mouse back/forward buttons: page navigation or JS events? (#277)
[w3ctag/design-reviews] Dynamic import maps (Issue #980)
- Re: [w3ctag/design-reviews] Dynamic import maps (Issue #980)
- Re: [w3ctag/design-reviews] Dynamic import maps (Issue #980)
Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158)
Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201)
Re: [w3c/gamepad] gamepads is not defined in steps for getGamepads (Issue #204)
Re: [w3c/gamepad] Editorial: Add missing steps in getGamepads (PR #205)
Re: [w3c/gamepad] Require system focus for gamepad user gesture (PR #207)
Re: [w3c/gamepad] Chore(README.md): remove link to old features (PR #208)
- Re: [w3c/gamepad] Chore(README.md): remove link to old features (PR #208)
- Re: [w3c/gamepad] Chore(README.md): remove link to old features (PR #208)
[w3c/selection-api] Update PR template (PR #333)
- Re: [w3c/selection-api] Update PR template (PR #333)
- Re: [w3c/selection-api] Update PR template (PR #333)
[w3c/clipboard-apis] Add PR template (PR #220)
- Re: [w3c/clipboard-apis] Update PR template (PR #220)
- Re: [w3c/clipboard-apis] Update PR template (PR #220)
Re: [whatwg/fetch] Define opaque-response blocking (updated) (PR #1755)
[whatwg/webidl] Intent use number / bigint union type (Issue #1426)
- Re: [whatwg/webidl] Intent use number / bigint union type (Issue #1426)
- Re: [whatwg/webidl] Intent use number / bigint union type (Issue #1426)
Re: [WICG/webcomponents] Add referenceTarget to ShadowRootInit argument to attachShadow() (PR #1062)
- Re: [WICG/webcomponents] Add referenceTarget to ShadowRootInit argument to attachShadow() (PR #1062)
- Re: [WICG/webcomponents] Add referenceTarget to ShadowRootInit argument to attachShadow() (PR #1062)
[w3c/editing] [execCommand] Fixed newline Unicode character for insertText action command step 5. (PR #465)
- Re: [w3c/editing] [execCommand] Fixed newline Unicode character for insertText action command step 5. (PR #465)
- Re: [w3c/editing] [execCommand] Fixed newline Unicode character for insertText action command step 5. (PR #465)
- Re: [w3c/editing] [execCommand] Fixed newline Unicode character for insertText action command step 5. (PR #465)
[w3c/editing] [execCommand] 9.22 The 'insertText' command action step 5. incorrectly states (U+00A0) as a newline code point (Issue #464)
[whatwg/encoding] Throw exception when text encode alloc memory fail. (Issue #334)
- Re: [whatwg/encoding] Throw exception when text encode alloc memory fail. (Issue #334)
- Re: [whatwg/encoding] Throw exception when text encode alloc memory fail. (Issue #334)
- Re: [whatwg/encoding] Throw exception when text encode alloc memory fail. (Issue #334)
Re: [whatwg/url] Web compatibility issue with various unknown (external) protocols like ed2k (Issue #815)
- Re: [whatwg/url] Web compatibility issue with various unknown (external) protocols like ed2k (Issue #815)
- Re: [whatwg/url] Web compatibility issue with various unknown (external) protocols like ed2k (Issue #815)
- Re: [whatwg/url] Web compatibility issue with various unknown (external) protocols like ed2k (Issue #815)
Re: [w3c/selection-api] Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary (Issue #176)
Re: [w3ctag/design-reviews] Web Translation API (Issue #948)
[whatwg/streams] Stream read hangs when stream is closed during a BYOD read (Issue #1321)
- Re: [whatwg/streams] Stream read hangs when stream is closed during a BYOB read (Issue #1321)
- Re: [whatwg/streams] Stream read hangs when stream is closed during a BYOB read (Issue #1321)
- Re: [whatwg/streams] Stream read hangs when stream is closed during a BYOB read (Issue #1321)
Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
Re: [w3ctag/design-reviews] Controller Documents v1.0 (Issue #960)
Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
- Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
- Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
- Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
- Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
- Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
- Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
- Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
- Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
- Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
- Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
- Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
[whatwg/xhr] https://onlinebooking.sand.telangana.gov.in/Masters/Home.aspx (Issue #391)
Re: [WICG/webcomponents] CSS Shadow Parts Selector ::part() does not work in combination with :disabled pseudo-class in Chrome (#918)
Re: [whatwg/dom] Proposal: rate limiting event listeners (debounce / throttle) (Issue #1298)
- Re: [whatwg/dom] Proposal: rate limiting event listeners (debounce / throttle) (Issue #1298)
- Re: [whatwg/dom] Proposal: rate limiting event listeners (debounce / throttle) (Issue #1298)
- Re: [whatwg/dom] Proposal: rate limiting event listeners (debounce / throttle) (Issue #1298)
- Re: [whatwg/dom] Proposal: rate limiting event listeners (debounce / throttle) (Issue #1298)
- Re: [whatwg/dom] Proposal: rate limiting event listeners (debounce / throttle) (Issue #1298)
[w3c/selection-api] `selectionchange` fires differently across the browser engines (Issue #332)
- Re: [w3c/selection-api] `selectionchange` fires differently across the browser engines (Issue #332)
- Re: [w3c/selection-api] `selectionchange` fires differently across the browser engines (Issue #332)
- Re: [w3c/selection-api] `selectionchange` fires differently across the browser engines (Issue #332)
[whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
- Re: [whatwg/url] Basic URL parse requires stripping tabs before host state is entered, allowing bad hosts (Issue #829)
[whatwg/streams] Editorial: Update use of WebIDL "invoke a callback function" (PR #1320)
- Re: [whatwg/streams] Editorial: Update use of WebIDL "invoke a callback function" (PR #1320)
- Re: [whatwg/streams] Editorial: Update use of WebIDL "invoke a callback function" (PR #1320)
[whatwg/dom] Editorial: Update use of WebIDL "invoke a callback function" (PR #1301)
- Re: [whatwg/dom] Editorial: Update use of WebIDL "invoke a callback function" (PR #1301)
- Re: [whatwg/dom] Editorial: Update use of WebIDL "invoke a callback function" (PR #1301)
[whatwg/webidl] Specifications which use "invoke the callback function" should be updated to specify their exception handling behavior. (Issue #1425)
Re: [w3ctag/design-reviews] Early TAG review request for Playout Statistics API for WebAudio (Issue #939)
Re: [whatwg/webidl] Handle exceptions when calling callbacks by default (Issue #1423)
- Re: [whatwg/webidl] Handle exceptions when calling callbacks by default (Issue #1423)
- Re: [whatwg/webidl] Handle exceptions when calling callbacks by default (Issue #1423)
Re: [whatwg/webidl] Allow users of "invoke a callback function" to report the exception (PR #1424)
- Re: [whatwg/webidl] Allow users of "invoke a callback function" to report the exception (PR #1424)
- Re: [whatwg/webidl] Allow users of "invoke a callback function" to report the exception (PR #1424)
Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
[w3c/selection-api] Change getComposedRanges to have options as input (PR #331)
- Re: [w3c/selection-api] Change getComposedRanges to have options as input (PR #331)
- Re: [w3c/selection-api] Change getComposedRanges to have options as input (PR #331)
- Re: [w3c/selection-api] Change getComposedRanges to have options as input (PR #331)
- Re: [w3c/selection-api] Change getComposedRanges to have options as input (PR #331)
Re: [whatwg/dom] Composed tree infrastructure (#725)
[w3c/clipboard-apis] Remove issues claiming "clipboard-write" was removed (PR #219)
- Re: [w3c/clipboard-apis] Remove issues claiming "clipboard-write" was removed (PR #219)
- Re: [w3c/clipboard-apis] Remove issues claiming "clipboard-write" was removed (PR #219)
- Re: [w3c/clipboard-apis] Remove issues claiming "clipboard-write" was removed (PR #219)
- Re: [w3c/clipboard-apis] Remove issues claiming "clipboard-write" was removed (PR #219)
[whatwg/dom] Missing "queue a global task" to resolve Promise in abort example (Issue #1300)
- Re: [whatwg/dom] Missing "queue a global task" to resolve Promise in abort example (Issue #1300)
- Re: [whatwg/dom] Missing "queue a global task" to resolve Promise in abort example (Issue #1300)
- Re: [whatwg/dom] Missing "queue a global task" to resolve Promise in abort example (Issue #1300)
Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
Re: [w3c/pointerlock] Section 2.1 should mention the effect of lock on PointerEvents (Issue #97)
Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)
- Re: [whatwg/dom] Define mutation events (#305)