[WICG/webcomponents] [custom-elements] Why is `attributeChangedCallback` synchronous? (Issue #963)
[w3c/permissions] Tidied up document using tidy-html5 (PR #382)
- Re: [w3c/permissions] Tidied up document using tidy-html5 (PR #382)
- Re: [w3c/permissions] Tidied up document using tidy-html5 (PR #382)
- Re: [w3c/permissions] Chore: Tidied up document using tidy-html5 (PR #382)
[w3c/manifest] related_applications needs more settings (Issue #1047)
Re: [whatwg/fetch] Why doesn't `fetch` reject if 400 ≤ status < 600? (#18)
Re: [WICG/webcomponents] `customElements.upgrade` does not upgrade node subtrees cloned from `template` contents via `cloneNode` (Issue #946)
Re: [WICG/webcomponents] `distributionchange` events, and `distributedNodes()` / `distributedElements()` APIs? (#940)
Re: [WICG/webcomponents] CSS selector to style slots with slotted elements (#936)
Re: [WICG/webcomponents] Allowing CSS combinators postfixed to the ::slotted() or :host selectors (#889)
[whatwg/fetch] How to parse BigInt using Response.json() function ? (Issue #1473)
- Re: [whatwg/fetch] How to parse BigInt using Response.json() function ? (Issue #1473)
- Re: [whatwg/fetch] How to parse BigInt using Response.json() function ? (Issue #1473)
Re: [WICG/webcomponents] HTML Modules: JavaScript Scoping of ShadowDom Children (Issue #959)
Re: [whatwg/fetch] blob: fetch of slice() without valid content type yields unexpected results (Issue #1464)
Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454)
- Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454)
- Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454)
Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346)
Re: [whatwg/fetch] Add render-blocking boolean to fetch timing info (PR #1449)
- Re: [whatwg/fetch] Add render-blocking boolean to fetch timing info (PR #1449)
- Re: [whatwg/fetch] Add render-blocking boolean to fetch timing info (PR #1449)
Re: [w3c/push-api] A javascript api for sending push notifications to others (#303)
Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
Re: [w3ctag/design-reviews] HTMLMediaElement controlsList (#643)
Re: [whatwg/fetch] Editorial: Add 103 to note about null body Response (PR #1465)
- Re: [whatwg/fetch] Editorial: Add 103 to note about null body Response (PR #1465)
- Re: [whatwg/fetch] Editorial: Add 103 to note about null body Response (PR #1465)
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: [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: [whatwg/fetch] Always send Origin header for (non HEAD/GET) CORS requests (PR #1463)
[w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760)
[whatwg/webidl] 'this' and nested steps (Issue #1175)
[w3c/ServiceWorker] Can HTTPS traffic without origin header be intercepted by Service Worker (Issue #1654)
- Re: [w3c/ServiceWorker] Can HTTPS traffic without origin header be intercepted by Service Worker (Issue #1654)
- Re: [w3c/ServiceWorker] Can HTTPS traffic without origin header be intercepted by Service Worker (Issue #1654)
Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
Re: [w3ctag/design-reviews] Review the HTML spec's treatment of focus (#468)
Re: [w3ctag/design-reviews] review HTML event loop and how things fit into it (#489)
[w3c/selection-api] `selectstart` event handler needs to be exposed on `Text` (Issue #159)
- Re: [w3c/selection-api] `selectstart` event handler needs to be exposed on `Text` (Issue #159)
- Re: [w3c/selection-api] `selectstart` event handler needs to be exposed on `Text` (Issue #159)
- Re: [w3c/selection-api] `selectstart` event handler needs to be exposed on `Text` (Issue #159)
Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033)
[w3c/push-api] Documentation: It's not clear how to specify the push service (Issue #355)
Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
Re: [w3ctag/design-reviews] SameParty cookie attribute (#595)
Re: [w3ctag/design-reviews] Early design review of the **updated** Multi-Screen Window Placement API (#602)
Re: [w3ctag/design-reviews] File Handling (#371)
Re: [w3ctag/design-reviews] Collection of Screensharing-related UX Hints (Issue #744)
- Re: [w3ctag/design-reviews] Collection of Screensharing-related UX Hints (Issue #744)
- Re: [w3ctag/design-reviews] Collection of Screensharing-related UX Hints (Issue #744)
Re: [w3ctag/design-reviews] Private Network Access (aka CORS-RFC1918) permission to relax mixed content (Issue #751)
[w3c/ServiceWorker] HTTPS request without origin header are not intercepted by Service Worker (Issue #1653)
- Re: [w3c/ServiceWorker] HTTPS request without origin header are not intercepted by Service Worker (Issue #1653)
- Re: [w3c/ServiceWorker] HTTPS request without origin header are not intercepted by Service Worker (Issue #1653)
[WICG/webcomponents] [element-internals] (Issue #962)
- Re: [WICG/webcomponents] [element-internals] (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
[whatwg/dom] Abood (Issue #1099)
Re: [WICG/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704)
- Re: [WICG/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704)
- Re: [WICG/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704)
- Re: [WICG/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704)
- Re: [WICG/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704)
Re: [WICG/webcomponents] [Template Instantiation] Layering and additional use cases (#747)
Re: [w3c/manifest] Add optional `translations` member (#676)
[w3c/ServiceWorker] TPAC 2022 (Issue #1652)
Re: [w3ctag/design-reviews] Web of Things (WoT) Discovery (Issue #733)
Re: [whatwg/webidl] 2.9. Enumerations - Incorrect wording (#972)
[w3c/manifest] TPAC 2022 status report (Issue #1046)
[w3c/uievents] TPAC 2022 status reports (Issue #333)
[w3c/screen-orientation] TPAC 2022 status report (Issue #208)
[w3c/push-api] TPAC 2022 status report (Issue #354)
[w3c/pointerlock] TPAC 2022 status report (Issue #80)
[w3c/IndexedDB] TPAC 2022 status report (Issue #389)
[w3c/gamepad] TPAC 2022 status report (Issue #169)
[w3c/FileAPI] TPAC 2022 status report (Issue #178)
Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41)
[whatwg/xhr] réouverture transit (Issue #352)
[whatwg/webidl] Fix incorrect wording in `2.9. Enumerations` (PR #1173)
- Re: [whatwg/webidl] Fix incorrect wording in `2.9. Enumerations` (PR #1173)
- Re: [whatwg/webidl] Fix incorrect wording in `2.9. Enumerations` (PR #1173)
- Re: [whatwg/webidl] Fix incorrect wording in `2.9. Enumerations` (PR #1173)
[whatwg/dom] MediaElement and SyntheticMediaElement (Issue #1098)
[w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381)
Re: [whatwg/fetch] Expose decoded/encoded size for constructed responses (PR #1456)
[whatwg/dom] Which interfaces should have event handler attributes? (Issue #1097)
Re: [whatwg/dom] Add a fully active check for EventTarget in event listener inner invoke (PR #1085)
- Re: [whatwg/dom] Add a fully active check for EventTarget in event listener inner invoke (PR #1085)
- Re: [whatwg/dom] Add a fully active check for EventTarget in event listener inner invoke (PR #1085)
Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090)
Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343)
Re: [w3c/ServiceWorker] Remove foreign fetch (#1188)
Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005)
Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
Re: [w3c/manifest] Use ordered map JSON in id processing (PR #1040)
Re: [w3ctag/design-reviews] Element.isVisible review (Issue #734)
Re: [w3ctag/design-reviews] FYI review of Writable directory prompts for the File System Access API (Issue #749)
Re: [w3ctag/design-reviews] Review Request for CSS Subgrid (Issue #712)
Re: [w3ctag/design-reviews] Design review: AbortSignal.any() (Issue #737)
- Re: [w3ctag/design-reviews] Design review: AbortSignal.any() (Issue #737)
- Re: [w3ctag/design-reviews] Design review: AbortSignal.any() (Issue #737)
[w3ctag/design-reviews] Web Machine Learning Model Loader API (Issue #759)
- Re: [w3ctag/design-reviews] Web Machine Learning Model Loader API (Issue #759)
- Re: [w3ctag/design-reviews] Web Machine Learning Model Loader API (Issue #759)
[w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
Re: [WICG/webcomponents] Observable Properties (Issue #951)
- Re: [WICG/webcomponents] Observable Properties (Issue #951)
- Re: [WICG/webcomponents] Observable Properties (Issue #951)
- Re: [WICG/webcomponents] Observable Properties (Issue #951)
[whatwg/xhr] Allow to send body within GET http requests (Issue #351)
- Re: [whatwg/xhr] Allow to send body within GET http requests (Issue #351)
- Re: [whatwg/xhr] Allow to send body within GET http requests (Issue #351)
- Re: [whatwg/xhr] Allow to send body within GET http requests (Issue #351)
[w3c/selection-api] Editorial: fix the issues reported by HTML Tidy (PR #158)
- Re: [w3c/selection-api] Editorial: fix the issues reported by HTML Tidy (PR #158)
- Re: [w3c/selection-api] Editorial: fix the issues reported by HTML Tidy (PR #158)
Re: [w3c/selection-api] Associate repo with Web Editing WG (#145)
Re: [w3ctag/design-reviews] Early design review: Back/forward cache NotRestoredReasons API (Issue #739)
Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738)
- Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738)
- Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738)
- Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738)
- Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738)
Re: [w3c/uievents] Expose 'direction-inversion' in wheel events (#57)
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] EditContext API (#416)
- Re: [w3ctag/design-reviews] EditContext API (#416)
- Re: [w3ctag/design-reviews] EditContext API (#416)
Re: [w3ctag/design-reviews] Early design review: CSS Toggles (Issue #730)
Re: [w3ctag/design-reviews] Response.json() (Issue #741)
- Re: [w3ctag/design-reviews] Response.json() (Issue #741)
- Re: [w3ctag/design-reviews] Response.json() (Issue #741)
- Re: [w3ctag/design-reviews] Response.json() (Issue #741)
Re: [w3ctag/design-reviews] import.meta.resolve() (Issue #746)
Re: [w3ctag/design-reviews] CSS property object-view-box review (Issue #740)
Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture 1.1 (Issue #736)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture 1.1 (Issue #736)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture 1.1 (Issue #736)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture 1.1 (Issue #736)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture 1.1 (Issue #736)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture 1.1 (Issue #736)
[whatwg/dom] 192.168.1.1 (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: [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-registries] Interaction with declarative shadow DOM (#914)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914)
Re: [w3c/manifest] Clarify shortcut_items should be within scope of scope (PR #1033)
[whatwg/url] aasasas (Issue #698)
Re: [whatwg/webidl] Mark DOMException as serializable (#732)
Re: [w3c/ServiceWorker] Create Service Worker from Blob/String that does not persist and auto claims for testing (Issue #1642)
Re: [whatwg/dom] Run adopt as part of insert (c825cea)
[w3c/ServiceWorker] The Service Worker spec should specify how to compute the site for cookies. (Issue #1651)
- Re: [w3c/ServiceWorker] The Service Worker spec should specify how to compute the site for cookies. (Issue #1651)
- Re: [w3c/ServiceWorker] The Service Worker spec should specify how to compute the site for cookies. (Issue #1651)
- Re: [w3c/ServiceWorker] The Service Worker spec should specify how to compute the site for cookies. (Issue #1651)
Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735)
[w3c/gamepad] Update subsections "Receiving inputs" and "Constructing a Gamepad" of Gamepad Interface for touch inputs. (Issue #167)
Re: [w3c/gamepad] Please don't restrict to a secure context (#145)
Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
[w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
Re: [whatwg/url] Goal: Getting a fixed document release (#222)
Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
[whatwg/webidl] .. (Issue #1171)
[whatwg/webidl] Vv (Issue #1170)
[w3c/editing] Add July Minutes (PR #404)
[w3ctag/design-reviews] TAG review of Data Catalog Vocabulary (DCAT) - Version 3 (Issue #758)
Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939)
Re: [w3c/clipboard-apis] Should reading the clipboard throw DataError or empty clipboard items? (Issue #179)
Re: [w3c/clipboard-apis] Async clipboard read and race conditions. (Issue #180)
- Re: [w3c/clipboard-apis] Async clipboard read and race conditions. (Issue #180)
- Re: [w3c/clipboard-apis] Async clipboard read and race conditions. (Issue #180)
[w3c/ServiceWorker] cache.add will block the main thread, such as network bandwidth? (Issue #1650)
- Re: [w3c/ServiceWorker] cache.add will block the main thread, such as network bandwidth? (Issue #1650)
- Re: [w3c/ServiceWorker] cache.add will block the main thread, such as network bandwidth? (Issue #1650)
- Re: [w3c/ServiceWorker] cache.add will block the main thread, such as network bandwidth? (Issue #1650)
Re: [w3ctag/design-reviews] Navigation API (formerly app history API) (Issue #717)
Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
Re: [whatwg/dom] Document.defaultCharset (#58)
[whatwg/webidl] 醒 (Issue #1169)
[whatwg/webidl] New error name: OptOutError (Issue #1168)
- Re: [whatwg/webidl] New error name: OptOutError (Issue #1168)
- Re: [whatwg/webidl] New error name: OptOutError (Issue #1168)
- Re: [whatwg/webidl] New error name: OptOutError (Issue #1168)
- Re: [whatwg/webidl] New error name: OptOutError (Issue #1168)
- Re: [whatwg/webidl] New error name: OptOutError (Issue #1168)
Re: [w3ctag/design-reviews] Deprecating `document.domain` setter. (#564)
[w3ctag/design-reviews] Review request for HTTP Status Code in Resource Timing (Issue #757)
- Re: [w3ctag/design-reviews] Review request for HTTP Status Code in Resource Timing (Issue #757)
- Re: [w3ctag/design-reviews] Review request for HTTP Status Code in Resource Timing (Issue #757)
- Re: [w3ctag/design-reviews] Review request for HTTP Status Code in Resource Timing (Issue #757)
- Re: [w3ctag/design-reviews] Review request for HTTP Status Code in Resource Timing (Issue #757)
- Re: [w3ctag/design-reviews] Review request for HTTP Status Code in Resource Timing (Issue #757)
Re: [w3c/push-api] Push notifications for logged In user (#297)
[whatwg/webidl] webidl (Issue #1167)
Re: [w3c/selection-api] Specify Selection.modify()? (#37)
[w3c/selection-api] Define Selection.prototype.modify (PR #157)
Re: [w3c/manifest] Feature request: add option to disable built-in navigation gestures (Issue #1041)
Re: [w3c/selection-api] Specify the selection behavior when selecting text in textarea or input (#78)
[w3c/selection-api] Remove the stray sentence that editing hosts outside a document cannot have a selection (PR #156)
Re: [w3c/selection-api] Define "editing hosts cannot have a selection" (#1)
- Re: [w3c/selection-api] Define "editing hosts cannot have a selection" (#1)
- Re: [w3c/selection-api] Define "editing hosts cannot have a selection" (#1)
Re: [w3c/selection-api] Selection should detach associated Range when Range move to another root. (#79)
Re: [w3c/selection-api] Add getComposedRange to Selection (#98)
Re: [w3c/selection-api] What task source do we queue events on? (#117)
Re: [w3c/selection-api] Define getSelection on DocumentOrShadowRoot instead of Document (#114)
Re: [w3c/selection-api] Include information about where the selection is ending (#93)
Re: [w3c/selection-api] Specification status report for TPAC 2019 (#111)
[w3c/selection-api] Clarify that the user interaction task source is used for selectionchange event (PR #155)
[w3c/selection-api] Add security and privacy considerations. (PR #154)
Re: [w3c/selection-api] add privacy considerations section (#133)
Re: [w3c/selection-api] add security considerations section (#132)
[w3c/selection-api] Clarify that the direction of selection is preserved when scripts mutates its range. (PR #153)
[whatwg/webidl] Make setlike/maplike generated properties enumerable (PR #1166)
Re: [whatwg/webidl] Inconsistent enumerability on keys/values/entries and friends (#738)
- Re: [whatwg/webidl] Inconsistent enumerability on keys/values/entries and friends (#738)
- Re: [whatwg/webidl] Inconsistent enumerability on keys/values/entries and friends (#738)
- Re: [whatwg/webidl] Inconsistent enumerability on keys/values/entries and friends (#738)
- Re: [whatwg/webidl] Inconsistent enumerability on keys/values/entries and friends (#738)
Re: [w3c/selection-api] What happens to direction when the range associated with the selection is modified? (#127)
- Re: [w3c/selection-api] What happens to direction when the range associated with the selection is modified? (#127)
- Re: [w3c/selection-api] What happens to direction when the range associated with the selection is modified? (#127)
- Re: [w3c/selection-api] What happens to direction when the range associated with the selection is modified? (#127)
Re: [w3c/selection-api] Align description of events with DOM suggested phrasing (PR #148)
- Re: [w3c/selection-api] Align description of events with DOM suggested phrasing (PR #148)
- Re: [w3c/selection-api] Align description of events with DOM suggested phrasing (PR #148)
Re: [w3c/selection-api] Why does getRangeAt must return a reference to (not a copy of) the range? (#40)
Re: [w3c/selection-api] Bahavior without browsing context (#82)
[w3c/selection-api] Fix the definition of containsNode() method when allowPartialContainment is true. (PR #152)
Re: [w3c/selection-api] containsNode could return true for a node that doesn't intersect the selection at all (#116)
Re: [w3c/selection-api] Text says "below" when talking about text that is "above" (#126)
[w3c/selection-api] Closes the issue 126. (PR #151)
Re: [w3c/selection-api] Remove outdated note about getSelection() (#128)
[w3c/selection-api] Remove the outdated note to address the issue #128. (PR #150)
Re: [w3c/selection-api] edge 中selection.focusOffset计算错误 (#97)
Re: [w3c/selection-api] Changing the selection creates a Range object (#103)
[whatwg/fetch] Feature detecting streaming requests (Issue #1470)
- Re: [whatwg/fetch] Feature detecting streaming requests (Issue #1470)
- Re: [whatwg/fetch] Feature detecting streaming requests (Issue #1470)
- Re: [whatwg/fetch] Feature detecting streaming requests (Issue #1470)
- Re: [whatwg/fetch] Feature detecting streaming requests (Issue #1470)
- Re: [whatwg/fetch] Feature detecting streaming requests (Issue #1470)
Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
Re: [w3ctag/design-reviews] Review Request for Attribution Reporting API (Issue #724)
Re: [w3ctag/design-reviews] Site-initiated mirroring (Issue #745)
- Re: [w3ctag/design-reviews] Site-initiated mirroring (Issue #745)
- Re: [w3ctag/design-reviews] Site-initiated mirroring (Issue #745)
- Re: [w3ctag/design-reviews] Site-initiated mirroring (Issue #745)
Re: [w3ctag/design-reviews] WebXR Raw Camera Access API (#652)
- Re: [w3ctag/design-reviews] WebXR Raw Camera Access API (#652)
- Re: [w3ctag/design-reviews] WebXR Raw Camera Access API (#652)
Re: [w3ctag/design-reviews] I18N String-Meta and WebIDL (Issue #716)
- Re: [w3ctag/design-reviews] I18N String-Meta and WebIDL (Issue #716)
- Re: [w3ctag/design-reviews] I18N String-Meta and WebIDL (Issue #716)
- Re: [w3ctag/design-reviews] I18N String-Meta and WebIDL (Issue #716)
- Re: [w3ctag/design-reviews] I18N String-Meta and WebIDL (Issue #716)
- Re: [w3ctag/design-reviews] I18N String-Meta and WebIDL (Issue #716)
Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79)
[w3c/editing] Track: Selection API for Shadow DOM (Issue #403)
- Re: [w3c/editing] Track: Selection API for Shadow DOM (Issue #403)
- Re: [w3c/editing] Track: Selection API for Shadow DOM (Issue #403)
- Re: [w3c/editing] Track: Selection API for Shadow DOM (Issue #403)
Re: [w3c/clipboard-apis] The MIME type checking should ignore the "web " prefix (Issue #178)
Re: [w3ctag/design-reviews] COEP reflection (Issue #742)
- Re: [w3ctag/design-reviews] COEP reflection (Issue #742)
- Re: [w3ctag/design-reviews] COEP reflection (Issue #742)
- Re: [w3ctag/design-reviews] COEP reflection (Issue #742)
- Re: [w3ctag/design-reviews] COEP reflection (Issue #742)
- Re: [w3ctag/design-reviews] COEP reflection (Issue #742)
- Re: [w3ctag/design-reviews] COEP reflection (Issue #742)
- Re: [w3ctag/design-reviews] COEP reflection (Issue #742)
- Re: [w3ctag/design-reviews] COEP reflection (Issue #742)
[w3ctag/design-reviews] ContentVisibilityAutoStateChanged event (Issue #756)
- Re: [w3ctag/design-reviews] ContentVisibilityAutoStateChanged event (Issue #756)
- Re: [w3ctag/design-reviews] ContentVisibilityAutoStateChanged event (Issue #756)
Re: [w3ctag/design-reviews] AbortSignal.timeout() (Issue #711)
- Re: [w3ctag/design-reviews] AbortSignal.timeout() (Issue #711)
- Re: [w3ctag/design-reviews] AbortSignal.timeout() (Issue #711)
Re: [w3ctag/design-reviews] Font Table Access API (#400)
Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718)
- Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718)
- Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718)
- Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718)
- Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718)
[whatwg/fetch] Editorial: Use controller for redirect navigation (PR #1469)
- Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469)
- Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469)
- Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469)
- Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469)
- Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469)
Re: [whatwg/dom] document.createEvent() should maybe not be conditional upon exposure (#952)
Re: [whatwg/fetch] Proposal: CORS means TAO by default (Issue #1414)
Re: [whatwg/dom] Add onabort definition and add onslotchange (#785)
- Re: [whatwg/dom] Add onabort definition and add onslotchange (#785)
- Re: [whatwg/dom] Add onabort definition and add onslotchange (#785)
Re: [w3ctag/design-reviews] Review request for TURTLEDOVE (Issue #723)
- Re: [w3ctag/design-reviews] Review request for TURTLEDOVE (Issue #723)
- Re: [w3ctag/design-reviews] Review request for TURTLEDOVE (Issue #723)
Re: [whatwg/streams] ReadableStream should be an async iterable (#778)
[whatwg/url] Unofficial draft (Issue #697)
[whatwg/dom] Does `attributeFilter` accept itorators? (Issue #1092)
- Re: [whatwg/dom] Does `MutationObserver` `attributeFilter` accept itorators? (Issue #1092)
- Re: [whatwg/dom] Does `MutationObserver` `attributeFilter` accept itorators? (Issue #1092)
[whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468)
- Re: [whatwg/fetch] Pass in response status to mark resource timing (PR #1468)
[whatwg/fetch] Editorial: Move initiator type to other side of note (PR #1467)
- Re: [whatwg/fetch] Editorial: Move initiator type to other side of note (PR #1467)
- Re: [whatwg/fetch] Editorial: Move initiator type to other side of note (PR #1467)
[whatwg/webidl] Editorial: fix uses of `?` with `IfAbruptRejectPromise` (PR #1165)
- Re: [whatwg/webidl] Editorial: fix uses of `?` with `IfAbruptRejectPromise` (PR #1165)
- Re: [whatwg/webidl] Editorial: fix uses of `?` with `IfAbruptRejectPromise` (PR #1165)
- Re: [whatwg/webidl] Editorial: fix uses of `?` with `IfAbruptRejectPromise` (PR #1165)
Re: [w3c/pointerlock] Tidied up document using tidy-html5 (PR #77)
[w3c/clipboard-apis] Mark up definition of events following bikeshed conventions (PR #181)
Re: [w3c/clipboard-apis] Missing event handler IDL attributes (#74)
Re: [w3c/IndexedDB] Normalize negative zero (PR #386)
Re: [w3c/IndexedDB] Initial sketch of manual commit flag for transactions (#331)
Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334)
Re: [w3c/editing] clarifications for the pickling design proposal (Issue #393)
Re: [w3c/editing] TPAC 2022 (Issue #400)
- Re: [w3c/editing] TPAC 2022 (Issue #400)
- Re: [w3c/editing] TPAC 2022 (Issue #400)
- Re: [w3c/editing] TPAC 2022 (Issue #400)
[w3c/editing] Detecting if a virtual keyboard will open if an element gets focus (Issue #402)
Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902)
- Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902)
- Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902)
- Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902)
- Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902)
[whatwg/fetch] Update Note on Request Destination / CSP directive (Issue #1466)
Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954)
[w3c/pointerlock] Use respec conventions for event definitions (PR #79)
- Re: [w3c/pointerlock] Use respec conventions for event definitions (PR #79)
- Re: [w3c/pointerlock] Use respec conventions for event definitions (PR #79)
- Re: [w3c/pointerlock] Use respec conventions for event definitions (PR #79)
- Re: [w3c/pointerlock] Use respec conventions for event definitions (PR #79)
Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
[w3c/DOM-Parsing] "XML serialization of the attributes" appears to be missing "If" at the start of step 3.5.2.4 (Issue #72)
[whatwg/streams] Proposal: ReadableStreamBodyReader (Issue #1238)
- Re: [whatwg/streams] Proposal: ReadableStreamBodyReader (Issue #1238)
- Re: [whatwg/streams] Proposal: ReadableStreamBodyReader (Issue #1238)
- Re: [whatwg/streams] Proposal: ReadableStreamBodyReader (Issue #1238)
- Re: [whatwg/streams] Proposal: ReadableStreamBodyReader (Issue #1238)
- Re: [whatwg/streams] Proposal: ReadableStreamBodyReader (Issue #1238)
- Re: [whatwg/streams] Proposal: ReadableStreamBodyReader (Issue #1238)
- Re: [whatwg/streams] Proposal: ReadableStreamBodyReader (Issue #1238)
- Re: [whatwg/streams] Proposal: ReadableStreamBodyReader (Issue #1238)
Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235)
- Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235)
- Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235)
- Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235)
- Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235)
[WICG/webcomponents] Selector for children of the named slot (Issue #961)
- Re: [WICG/webcomponents] Selector for children of the named slot (Issue #961)
- Re: [WICG/webcomponents] Selector for children of the named slot (Issue #961)
[w3c/IndexedDB] Fix internal links to events (PR #388)
- Re: [w3c/IndexedDB] Fix internal links to events (PR #388)
- Re: [w3c/IndexedDB] Fix internal links to events (PR #388)
- Re: [w3c/IndexedDB] Fix internal links to events (PR #388)
[w3ctag/design-reviews] Fetch streaming upload (Issue #754)
- Re: [w3ctag/design-reviews] Fetch streaming upload (Issue #754)
- Re: [w3ctag/design-reviews] Fetch streaming upload (Issue #754)
- Re: [w3ctag/design-reviews] Fetch streaming upload (Issue #754)
- Re: [w3ctag/design-reviews] Fetch streaming upload (Issue #754)
[w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166)
[w3c/push-api] Question: what about shared device (Issue #353)
[whatwg/streams] Request review MDN readable byte streams docs (Issue #1237)
Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
[w3c/manifest] Rename .pr-preview.json to -preview.json (PR #1044)
[whatwg/webidl] Porfavor me ajude (Issue #1163)
Re: [whatwg/url] URLSearchParams delete all vs delete one (#335)
[WICG/webcomponents] Please, PLEASE, do not allow custom elements to be upgraded in scoped `ShadowRoot` registries. (Issue #960)
- Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960)
- Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960)
- Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960)
- Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960)
- Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960)
- Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960)
Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819)
- Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819)
- Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819)
Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083)
[w3ctag/design-reviews] Review request on Render Blocking Status in Resource Timing (Issue #753)
- Re: [w3ctag/design-reviews] Review request on Render Blocking Status in Resource Timing (Issue #753)
- Re: [w3ctag/design-reviews] Review request on Render Blocking Status in Resource Timing (Issue #753)
- Re: [w3ctag/design-reviews] Review request on Render Blocking Status in Resource Timing (Issue #753)
Re: [whatwg/url] Proposal: URL.parseIPv4() URL.parseIPv6() (Issue #696)
[w3c/ServiceWorker] Is there a security issue justifying no `Set-Cookie` setting in SW? (Issue #1649)
- Re: [w3c/ServiceWorker] Is there a security issue justifying no `Set-Cookie` setting in SW? (Issue #1649)
- Re: [w3c/ServiceWorker] Is there a security issue justifying no `Set-Cookie` setting in SW? (Issue #1649)
Re: [whatwg/url] size (or length) for URLSearchParams (#163)
Re: [w3c/permissions] Add an introduction section? (#274)
Re: [whatwg/dom] Timeout AbortSignal (or AbortController) that gets input from the operation (Issue #1082)
[w3c/uievents] Use <thead> for table headers (PR #332)
- Re: [w3c/uievents] Use <thead> for table headers (PR #332)
- Re: [w3c/uievents] Use <thead> for table headers (PR #332)