Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041)
[w3c/gamepad] haptic test on android/ios does not detect ps5 haptic triggers (Issue #188)
- Re: [w3c/gamepad] haptic test on android/ios does not detect ps5 haptic triggers (Issue #188)
- Re: [w3c/gamepad] haptic test on android/ios does not detect ps5 haptic triggers (Issue #188)
[whatwg/webidl] Meta: use XXX as issue class (PR #1355)
Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038)
- Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038)
- Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038)
[w3ctag/design-reviews] Allow transferring ArrayBuffer into WebCodecs object constructors (Issue #889)
[w3c/IndexedDB] TPAC 2023 status report (Issue #413)
[w3c/editing] Update explainer to add the new write algorithm. (PR #436)
Re: [w3ctag/design-reviews] content-visibility: auto forces contain-intrinsic-size: auto (Issue #876)
[whatwg/fetch] Consider restricting 103 Early Hints to HTTP/2 or later (Issue #1698)
- Re: [whatwg/fetch] Consider restricting 103 Early Hints to HTTP/2 or later (Issue #1698)
- Re: [whatwg/fetch] Consider restricting 103 Early Hints to HTTP/2 or later (Issue #1698)
Re: [w3ctag/design-reviews] ServiceWorker static routing API (Issue #863)
- Re: [w3ctag/design-reviews] ServiceWorker static routing API (Issue #863)
- Re: [w3ctag/design-reviews] ServiceWorker static routing API (Issue #863)
Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939)
[whatwg/webidl] https://support.google.com/chrome/thread/232038101?hl=en (Issue #1354)
[whatwg/dom] Server-side "template instantiation" (Issue #1222)
- Re: [whatwg/dom] Server-side "template instantiation" (Issue #1222)
- Re: [whatwg/dom] Server-side "template instantiation" (Issue #1222)
- Re: [whatwg/dom] Server-side "template instantiation" (Issue #1222)
[w3ctag/design-reviews] Web Install API (Issue #888)
Re: [whatwg/url] Consider adding a constructor to make a URL from parts (#354)
Re: [w3ctag/design-reviews] HTML Modules (#334)
[whatwg/url] Add `URL.from(object)` constructor? (Issue #782)
- Re: [whatwg/url] Add `URL.from(object)` constructor? (Issue #782)
- Re: [whatwg/url] Add `URL.from(object)` constructor? (Issue #782)
- Re: [whatwg/url] Add `URL.from(object)` constructor? (Issue #782)
- Re: [whatwg/url] Add `URL.from(object)` constructor? (Issue #782)
- Re: [whatwg/url] Add `URL.from(object)` constructor? (Issue #782)
- Re: [whatwg/url] Add `URL.from(object)` constructor? (Issue #782)
- Re: [whatwg/url] Add `URL.from(object)` constructor? (Issue #782)
- Re: [whatwg/url] Add `URL.from(object)` constructor? (Issue #782)
[w3ctag/design-reviews] Specification Review: FetchLater API (Issue #887)
[w3ctag/design-reviews] Document Render-Blocking (Issue #886)
- Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886)
- Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886)
- Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886)
Re: [w3ctag/design-reviews] EditContext API (#416)
Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523)
Re: [w3ctag/design-reviews] HTTPS Upgrades (Issue #853)
- Re: [w3ctag/design-reviews] HTTPS Upgrades (Issue #853)
- Re: [w3ctag/design-reviews] HTTPS Upgrades (Issue #853)
- Re: [w3ctag/design-reviews] HTTPS Upgrades (Issue #853)
- Re: [w3ctag/design-reviews] HTTPS Upgrades (Issue #853)
Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674)
- Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674)
- Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674)
[whatwg/dom] Explicitly update the child's parent (Issue #1221)
- Re: [whatwg/dom] Explicitly update the child's parent (Issue #1221)
- Re: [whatwg/dom] Explicitly update the child's parent (Issue #1221)
- Re: [whatwg/dom] Explicitly update the child's parent (Issue #1221)
Re: [w3c/uievents] Define behavior for wheel event group when the scroll is handed off (Issue #342)
Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
Re: [whatwg/fetch] Add `"json"` destination, for JSON modules (PR #1691)
Re: [whatwg/dom] Disconnect single target instead of all (#126)
Re: [whatwg/fetch] Move Content-Range header builder to separate algorithm (Issue #1552)
Re: [w3c/uievents] "keyCode" is the only way to work with KeyboardEvents now (#267)
Re: [whatwg/dom] Allow custom "get the parent" algorithms for EventTargets (#583)
Re: [w3c/uievents] `beforeinput` and `compositionupdate` event order (Issue #354)
Re: [w3c/uievents] Keyboard Event Types: possible text missing. (Issue #324)
Re: [w3c/uievents] Specify the `textInput` event (Issue #353)
Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723)
- Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723)
- Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723)
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: [w3ctag/design-reviews] Shared Storage API (Issue #747)
Re: [w3ctag/design-reviews] Private Aggregation API (Issue #846)
[w3ctag/design-reviews] CSS State Container Queries (Issue #885)
[whatwg/fetch] shenal123409@outlook.com (Issue #1697)
Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144)
Re: [w3c/FileAPI] Proposal: Add a capability to create a Blob URL with a unique (non-opaque) origin (Issue #192)
[whatwg/fetch] Editorial: Create the build a content range algorithm (PR #1696)
- Re: [whatwg/fetch] Editorial: Create the build a content range algorithm (PR #1696)
- Re: [whatwg/fetch] Editorial: Create the build a content range algorithm (PR #1696)
- Re: [whatwg/fetch] Editorial: Create the build a content range algorithm (PR #1696)
- Re: [whatwg/fetch] Editorial: Create the build a content range algorithm (PR #1696)
- Re: [whatwg/fetch] Editorial: Create the build a content range algorithm (PR #1696)
- Re: [whatwg/fetch] Editorial: Create the build a content range algorithm (PR #1696)
Re: [whatwg/fetch] Create Range header section in HTTP extensions section (Issue #1553)
Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
Re: [WICG/webcomponents] Proposal: Allow custom elements to be in any namespace (#634)
[w3c/clipboard-apis] Async Clipboard API take more time compared to DataTransfer API to read/write data in System Clipboard (Issue #190)
- Re: [w3c/clipboard-apis] Async Clipboard API take more time compared to DataTransfer API to read/write data in System Clipboard (Issue #190)
- Re: [w3c/clipboard-apis] Async Clipboard API take more time compared to DataTransfer API to read/write data in System Clipboard (Issue #190)
Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795)
- Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795)
- Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795)
Re: [w3c/uievents] key-event-viewer does not work in Internet Explorer (#188)
Re: [w3c/uievents] Missing keycap on Section 4.6.4.1. - keydown ? (#214)
Re: [w3c/uievents] Restore key/char/glyph styles (#312)
[w3c/ServiceWorker] Don't require Cache API to have a secure context (Issue #1691)
[whatwg/url] Review Draft Publication: August 2023 (PR #781)
[whatwg/streams] Review Draft Publication: August 2023 (PR #1293)
- Re: [whatwg/streams] Review Draft Publication: August 2023 (PR #1293)
- Re: [whatwg/streams] Review Draft Publication: August 2023 (PR #1293)
Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
[whatwg/dom] Provide a "deep clone" shorthand (Issue #1220)
[w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690)
- Re: [w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690)
- Re: [w3c/ServiceWorker] Add a Service-Worker-Exclude Header (Issue #1690)
[w3c/uievents-code] Control Pad images labeled "Numpad" (Issue #41)
- Re: [w3c/uievents-code] Control Pad images labeled "Numpad" (Issue #41)
- Re: [w3c/uievents-code] Control Pad images labeled "Numpad" (Issue #41)
[whatwg/encoding] Api payout (Issue #315)
[WICG/webcomponents] Does form association need to be per-class, or could it be per-instance? (Issue #1025)
Re: [WICG/webcomponents] Editor support for WebComponents (#776)
- Re: [WICG/webcomponents] Editor support for WebComponents (#776)
- Re: [WICG/webcomponents] Editor support for WebComponents (#776)
- Re: [WICG/webcomponents] Editor support for WebComponents (#776)
- Re: [WICG/webcomponents] Editor support for WebComponents (#776)
[w3c/IndexedDB] Specify behavior when document is not fully active (Issue #412)
- Re: [w3c/IndexedDB] Specify behavior when document is not fully active (Issue #412)
- Re: [w3c/IndexedDB] Specify behavior when document is not fully active (Issue #412)
- Re: [w3c/IndexedDB] Specify behavior when document is not fully active (Issue #412)
- Re: [w3c/IndexedDB] Specify behavior when document is not fully active (Issue #412)
- Re: [w3c/IndexedDB] Specify behavior when document is not fully active (Issue #412)
Re: [whatwg/webidl] Allow dictionaries and callbacks to be distinguishable (Issue #1191)
[whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
- Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353)
Re: [w3ctag/design-reviews] WebRTC Codec selection API (Issue #836)
Re: [WICG/webcomponents] Alternative to customized built-in - Element custom enhancements (Issue #1000)
Re: [w3c/editing] [charter] execCommand spec should be in scope (Issue #432)
Re: [w3c/uievents] Insert Key is not part of the spec as a modifier key (#273)
Re: [w3c/uievents] TPAC planning and specification status report (#268)
Re: [w3c/uievents] Status report and planning for TPAC 2021 (#308)
[w3ctag/design-reviews] TAG review request for the IDP signin status API (Issue #884)
[w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)
- Re: [w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)
- Re: [w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)
- Re: [w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)
- Re: [w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)
- Re: [w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)
- Re: [w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)
- Re: [w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)
- Re: [w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)
- Re: [w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)
Re: [w3c/ServiceWorker] Add a static routing API support. (PR #1686)
- Re: [w3c/ServiceWorker] Add a static routing API support. (PR #1686)
- Re: [w3c/ServiceWorker] Add a static routing API support. (PR #1686)
[whatwg/webidl] gkggf (Issue #1352)
Re: [w3c/screen-orientation] Promise for unlock()? (#104)
Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989)
[whatwg/webidl] Remove extra }'s from some TypeError references (PR #1351)
- Re: [whatwg/webidl] Remove extra }'s from some TypeError references (PR #1351)
- Re: [whatwg/webidl] Remove extra }'s from some TypeError references (PR #1351)
[w3c/permissions] One time permissions: exposing and specifying grant type (Issue #418)
Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414)
- Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414)
- Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414)
- Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414)
- Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414)
- Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414)
[w3c/uievents-key] Typo fixes. (PR #67)
[w3c/manifest] Create Medwin (PR #1095)
Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
[WICG/webcomponents] Provide a means of identifying Constructable StyleSheet instances from browser dev tools. (Issue #1024)
- Re: [WICG/webcomponents] Provide a means of identifying Constructable StyleSheet instances from browser dev tools. (Issue #1024)
- Re: [WICG/webcomponents] Provide a means of identifying Constructable StyleSheet instances from browser dev tools. (Issue #1024)
- Re: [WICG/webcomponents] Provide a means of identifying Constructable StyleSheet instances from browser dev tools. (Issue #1024)
- Re: [WICG/webcomponents] Provide a means of identifying Constructable StyleSheet instances from browser dev tools. (Issue #1024)
- Re: [WICG/webcomponents] Provide a means of identifying Constructable StyleSheet instances from browser dev tools. (Issue #1024)
[whatwg/webidl] Intent to use Constants (Issue #1350)
[whatwg/fetch] w3c/webappsec-permissions-policy issue #207 (Issue #1695)
- Re: [whatwg/fetch] w3c/webappsec-permissions-policy issue #207 (Issue #1695)
- Re: [whatwg/fetch] w3c/webappsec-permissions-policy issue #207 (Issue #1695)
- Re: [whatwg/fetch] w3c/webappsec-permissions-policy issue #207 (Issue #1695)
- Re: [whatwg/fetch] w3c/webappsec-permissions-policy issue #207 (Issue #1695)
Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)
- Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)
- Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)
- Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)
[whatwg/fetch] Piotr (Issue #1694)
Re: [w3c/IndexedDB] Could we drop the spec versioning? (Issue #402)
Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
- Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
- Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
- Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
- Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
[w3ctag/design-reviews] `inverted-colors` CSS Media Query (Issue #883)
[w3c/selection-api] Define `Selection.rangeCount` when an input field is focused (Issue #166)
Re: [w3c/IndexedDB] Editorial: Move Ali to Former Editor, note affiliation (PR #407)
[whatwg/fetch] interop: content-type for blob fetch with invalid type (Issue #1693)
- Re: [whatwg/fetch] interop: content-type for blob fetch with invalid type (Issue #1693)
- Re: [whatwg/fetch] interop: content-type for blob fetch with invalid type (Issue #1693)
Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)
Re: [w3c/ServiceWorker] Declarative routing (#1373)
- Re: [w3c/ServiceWorker] Declarative routing (#1373)
- Re: [w3c/ServiceWorker] Declarative routing (#1373)
- Re: [w3c/ServiceWorker] Declarative routing (#1373)
- Re: [w3c/ServiceWorker] Declarative routing (#1373)
- Re: [w3c/ServiceWorker] Declarative routing (#1373)
- Re: [w3c/ServiceWorker] Declarative routing (#1373)
- Re: [w3c/ServiceWorker] Declarative routing (#1373)
- Re: [w3c/ServiceWorker] Declarative routing (#1373)
[w3ctag/design-reviews] DOM merging engine/API (Discussion #882)
[whatwg/streams] I'm going to be at work (Issue #1292)
- Re: [whatwg/streams] I'm going to be at work (Issue #1292)
- Re: [whatwg/streams] I'm going to be at work (Issue #1292)
Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465)
Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334)
Re: [w3c/IndexedDB] Normalize negative zero (PR #386)
Re: [w3c/IndexedDB] Editorial: Update note markup/markdown and styling (PR #404)
- Re: [w3c/IndexedDB] Editorial: Update note markup/markdown and styling (PR #404)
- Re: [w3c/IndexedDB] Editorial: Update note markup/markdown and styling (PR #404)
- Re: [w3c/IndexedDB] Editorial: Update note markup/markdown and styling (PR #404)
- Re: [w3c/IndexedDB] Editorial: Update note markup/markdown and styling (PR #404)
Re: [w3c/IndexedDB] Transaction lifetime verbiage, "running" (Issue #408)
[whatwg/webidl] Pay api (Issue #1349)
Re: [whatwg/fetch] Trailer support in the API (#981)
Re: [w3ctag/design-reviews] Specification review request for Verifiable Credential Data Integrity (Issue #850)
Re: [w3ctag/design-reviews] RDF Canonicalization (Issue #855)
- Re: [w3ctag/design-reviews] RDF Canonicalization (Issue #855)
- Re: [w3ctag/design-reviews] RDF Canonicalization (Issue #855)
Re: [w3ctag/design-reviews] [FYI] Clear Client Hints via Clear-Site-Data header (Issue #871)
Re: [w3ctag/design-reviews] Disabling UA transitions for same-document navigations (Issue #835)
Re: [w3ctag/design-reviews] Tabbed web apps (Issue #841)
Re: [w3ctag/design-reviews] Borderless mode (Issue #852)
Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
Re: [w3c/gamepad] Request: support for analog keyboards (Issue #187)
Re: [w3ctag/design-reviews] Captured Mouse Events (Issue #872)
Re: [w3ctag/design-reviews] Web Audio API: RenderCapacity API (Issue #843)
Re: [w3ctag/design-reviews] Cross-document View Transitions API (Issue #851)
[w3c/IndexedDB] Rename "open a database" algorithm to "open a database connection" (PR #411)
- Re: [w3c/IndexedDB] Rename "open a database" algorithm to "open a database connection" (PR #411)
- Re: [w3c/IndexedDB] Rename "open a database" algorithm to "open a database connection" (PR #411)
- Re: [w3c/IndexedDB] Rename "open a database" algorithm to "open a database connection" (PR #411)
- Re: [w3c/IndexedDB] Rename "open a database" algorithm to "open a database connection" (PR #411)
- Re: [w3c/IndexedDB] Rename "open a database" algorithm to "open a database connection" (PR #411)
- Re: [w3c/IndexedDB] Rename "open a database" algorithm to "open a database connection" (PR #411)
- Re: [w3c/IndexedDB] Rename "open a database" algorithm to "open a database connection" (PR #411)
[w3c/IndexedDB] "opening/closing a database" (Issue #410)
- Re: [w3c/IndexedDB] "opening/closing a database" (Issue #410)
- Re: [w3c/IndexedDB] "opening/closing a database" (Issue #410)
Re: [w3c/IndexedDB] Disambiguate "running" for transactions (PR #409)
- Re: [w3c/IndexedDB] Disambiguate "running" for transactions (PR #409)
- Re: [w3c/IndexedDB] Disambiguate "running" for transactions (PR #409)
- Re: [w3c/IndexedDB] Disambiguate "running" for transactions (PR #409)
- Re: [w3c/IndexedDB] Disambiguate "running" for transactions (PR #409)
- Re: [w3c/IndexedDB] Disambiguate "running" for transactions (PR #409)
- Re: [w3c/IndexedDB] Disambiguate "running" for transactions (PR #409)
- Re: [w3c/IndexedDB] Disambiguate "running" for transactions (PR #409)
- Re: [w3c/IndexedDB] Disambiguate "running" for transactions (PR #409)
- Re: [w3c/IndexedDB] Disambiguate "running" for transactions (PR #409)
[whatwg/dom] clone with clone children flag set should append clone before cloning children (Issue #1219)
[whatwg/webidl] Intent to use Constants (Issue #1348)
- Re: [whatwg/webidl] Intent to use Constants (Issue #1348)
- Re: [whatwg/webidl] Intent to use Constants (Issue #1348)
Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
Re: [w3ctag/design-reviews] Review Request for Attribution Reporting API (Issue #724)
- Re: [w3ctag/design-reviews] Review Request for Attribution Reporting API (Issue #724)
- Re: [w3ctag/design-reviews] Review Request for Attribution Reporting API (Issue #724)
Re: [w3ctag/design-reviews] Review request for TURTLEDOVE (Issue #723)
Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838)
- Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838)
- Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838)
Re: [whatwg/url] Proposal for new version of parsing spec (Issue #778)
Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
Re: [w3ctag/design-reviews] First-Party Sets (#342)
Re: [w3ctag/design-reviews] TAG spec review of Bounce Tracking Mitigations (Issue #862)
- Re: [w3ctag/design-reviews] TAG spec review of Bounce Tracking Mitigations (Issue #862)
- Re: [w3ctag/design-reviews] TAG spec review of Bounce Tracking Mitigations (Issue #862)
- Re: [w3ctag/design-reviews] TAG spec review of Bounce Tracking Mitigations (Issue #862)
- Re: [w3ctag/design-reviews] TAG spec review of Bounce Tracking Mitigations (Issue #862)
Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760)
[w3ctag/design-reviews] `prefers-reduced-transparency` CSS Media Query (Issue #881)
Re: [w3ctag/design-reviews] Exclusive accordion (<details name="">) (Issue #866)
- Re: [w3ctag/design-reviews] Exclusive accordion (<details name="">) (Issue #866)
- Re: [w3ctag/design-reviews] Exclusive accordion (<details name="">) (Issue #866)
- Re: [w3ctag/design-reviews] Exclusive accordion (<details name="">) (Issue #866)
Re: [w3ctag/design-reviews] Portable Network Graphics (PNG), Third Edition. (Issue #873)
Re: [w3ctag/design-reviews] Early design review: scheduler.yield() (Issue #827)
- Re: [w3ctag/design-reviews] Early design review: scheduler.yield() (Issue #827)
- Re: [w3ctag/design-reviews] Early design review: scheduler.yield() (Issue #827)
Re: [w3ctag/design-reviews] deliveryType (Resource Timing) (Issue #858)
- Re: [w3ctag/design-reviews] deliveryType (Resource Timing) (Issue #858)
- Re: [w3ctag/design-reviews] deliveryType (Resource Timing) (Issue #858)
Re: [w3ctag/design-reviews] Early design review: Subresource loading with Web Bundles (#616)
Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
- Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)
Re: [w3ctag/design-reviews] WebDriver BiDi (Issue #869)
- Re: [w3ctag/design-reviews] WebDriver BiDi (Issue #869)
- Re: [w3ctag/design-reviews] WebDriver BiDi (Issue #869)
Re: [w3ctag/design-reviews] Web of Things (WoT) Profile - Review Requested (Issue #818)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Profile - Review Requested (Issue #818)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Profile - Review Requested (Issue #818)
Re: [WICG/webcomponents] 2023 TPAC F2F discussion? (Issue #1018)
- Re: [WICG/webcomponents] 2023 TPAC F2F discussion? (Issue #1018)
- Re: [WICG/webcomponents] 2023 TPAC F2F discussion? (Issue #1018)
- Re: [WICG/webcomponents] 2023 TPAC F2F discussion? (Issue #1018)
Re: [w3ctag/design-reviews] WebUSB exclusionFilters option in requestDevice() (Issue #865)
Re: [w3ctag/design-reviews] API for capturing all screens (Issue #856)
[whatwg/dom] heyits_me (Issue #1218)
Re: [w3ctag/design-reviews] Bluetooth RFCOMM in Web Serial API (Issue #854)
- Re: [w3ctag/design-reviews] Bluetooth RFCOMM in Web Serial API (Issue #854)
- Re: [w3ctag/design-reviews] Bluetooth RFCOMM in Web Serial API (Issue #854)
- Re: [w3ctag/design-reviews] Bluetooth RFCOMM in Web Serial API (Issue #854)
- Re: [w3ctag/design-reviews] Bluetooth RFCOMM in Web Serial API (Issue #854)
Re: [w3ctag/design-reviews] Multiple Readers and Writers in File System Access API (Issue #845)
- Re: [w3ctag/design-reviews] Multiple Readers and Writers in File System Access API (Issue #845)
- Re: [w3ctag/design-reviews] Multiple Readers and Writers in File System Access API (Issue #845)
Re: [w3ctag/design-reviews] Web Authentication: Large Blob extension (Issue #820)
- Re: [w3ctag/design-reviews] Web Authentication: Large Blob extension (Issue #820)
- Re: [w3ctag/design-reviews] Web Authentication: Large Blob extension (Issue #820)
- Re: [w3ctag/design-reviews] Web Authentication: Large Blob extension (Issue #820)
- Re: [w3ctag/design-reviews] Web Authentication: Large Blob extension (Issue #820)
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)
- 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)
[whatwg/xhr] Ambiguous definition/initial values of network error (Issue #379)
- Re: [whatwg/xhr] Ambiguous definition/initial values of network error (Issue #379)
- Re: [whatwg/xhr] Ambiguous definition/initial values of network error (Issue #379)
- Re: [whatwg/xhr] Ambiguous definition/initial values of network error (Issue #379)
Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
- Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)