Re: [whatwg/dom] DOM Events introduction: clarify how listeners are invoked (12beda2)
Re: [whatwg/dom] Trusted Types integration (#789)
[w3c/manifest] chore: Add retiredDate for Kenneth Rohde Christiansen (PR #1192)
Re: [w3c/ServiceWorker] should an window.open() about:blank document be controlled by opener's controller? (#1163)
Re: [w3c/ServiceWorker] Dynamic Event Handler Registration (#1156)
Re: [w3c/ServiceWorker] Register HTTP header fields with IANA (#1134)
Re: [w3c/ServiceWorker] Make object equality of service workers clearer (#1140)
Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122)
- Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122)
- Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122)
- Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122)
Re: [w3c/ServiceWorker] respondWith uses the wrong targetRealm (#1055)
Re: [w3c/ServiceWorker] consider how clients.claim() should work with srcdoc iframes (#1093)
Re: [w3c/ServiceWorker] Lifetime of service workers in relation to dedicated and shared workers (#1119)
Re: [w3c/ServiceWorker] What does it mean to wait "for a task to be executed (including its asynchronous steps)"? (#1109)
Re: [w3c/ServiceWorker] Write tests for MIX behaviour (#1105)
Re: [w3c/ServiceWorker] Spec uses incorrect settings object when fetching a module worker (#849)
[w3c/ServiceWorker] E (Issue #1800)
[w3ctag/design-reviews] Incubation: PWA (same-site) Origin Migration (Issue #1164)
[whatwg/dom] setAttributeNS incorrect context for validation (Issue #1417)
Re: [w3ctag/design-reviews] Incubation: Proofreader API (Issue #1146)
Re: [w3ctag/design-reviews] Signature-Based Integrity. (Issue #1041)
[w3c/IndexedDB] treat writes to the DB that have no success handler as having called commit (Issue #482)
- Re: [w3c/IndexedDB] treat writes to the DB that have no success handler as having called commit (Issue #482)
- Re: [w3c/IndexedDB] treat writes to the DB that have no success handler as having called commit (Issue #482)
Re: [w3c/uievents] Event order of onKeyDown, onKeyPress, onKeyUp, and onPaste when using pasting (CMD + v) in Mac OS X (#261)
[w3c/IndexedDB] Clarify cursor iteration predicates some more (PR #481)
Re: [w3ctag/design-reviews] Other Spec Review: Extend CSP script-src hashes (Issue #1128)
Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)
Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390)
[whatwg/fetch] Add "webtransport" request mode (integration) (PR #1873)
Re: [w3c/manifest] TPAC 2025 status report (Issue #1181)
[w3c/IndexedDB] `retrieve multiple items from an index` index out of bounds error (Issue #480)
[whatwg/dom] Autofill Event Needed (Issue #1416)
- Re: [whatwg/dom] Autofill Event Needed (Issue #1416)
- Re: [whatwg/dom] Autofill Event Needed (Issue #1416)
[w3ctag/design-reviews] Reconsider W3C Recommendation status of XSLT 2.0 and XSLT 3.0 (Issue #1163)
[w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)
- Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)
- Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)
- Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)
- Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)
- Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)
- Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)
- Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)
- Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)
- Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)
[w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
- Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479)
Re: [WICG/webcomponents] Reference Target "phase 2": seeking feedback and use cases (Issue #1111)
Re: [w3ctag/design-reviews] `<geolocation>` element (part of PEPC) (Issue #1140)
- Re: [w3ctag/design-reviews] `<geolocation>` element (part of PEPC) (Issue #1140)
- Re: [w3ctag/design-reviews] `<geolocation>` element (part of PEPC) (Issue #1140)
[w3ctag/design-reviews] Incubation: template (Issue #1162)
Re: [w3c/ServiceWorker] TPAC 2025 status report (Issue #1787)
Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962)
Re: [w3c/ServiceWorker] Recovering from fetch failures (#939)
[w3c/permissions] Can permissions.setPermission not use context? (Issue #471)
- Re: [w3c/permissions] Can permissions.setPermission not use context? (Issue #471)
- Re: [w3c/permissions] Can permissions.setPermission not use context? (Issue #471)
- Re: [w3c/permissions] Can permissions.setPermission not use context? (Issue #471)
- Re: [w3c/permissions] Can permissions.setPermission not use context? (Issue #471)
- Re: [w3c/permissions] Can permissions.setPermission not use context? (Issue #471)
- Re: [w3c/permissions] Can permissions.setPermission not use context? (Issue #471)
Re: [w3ctag/design-reviews] WG Revision: Dubbing and Audio description Profiles of TTML2 (for 2nd CRS) (Issue #1139)
Re: [w3c/clipboard-apis] Remove clipboardchange event (and replace it possibly with a promise returning method) (Issue #228)
[whatwg/webidl] Intent to use Constants (Issue #1535)
Re: [whatwg/fetch] New Proposal: Fetch retry (Issue #1838)
Re: [w3c/pointerlock] TPAC 2025 status report (Issue #103)
[whatwg/fetch] docs: add example for X-Content-Type-Options header (PR #1872)
[whatwg/fetch] Clarify handling of request body streams during redirects (Issue #1871)
- Re: [whatwg/fetch] Clarify handling of request body streams during redirects (Issue #1871)
- Re: [whatwg/fetch] Clarify handling of request body streams during redirects (Issue #1871)
[whatwg/fetch] Fix memory leak in Fetch with large stream responses (Issue #1870)
- Re: [whatwg/fetch] Fix memory leak in Fetch with large stream responses (Issue #1870)
- Re: [whatwg/fetch] Fix memory leak in Fetch with large stream responses (Issue #1870)
[whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
- Re: [whatwg/fetch] Override "Accept-Language" header if WebDriver BiDi emulated language is present. (PR #1869)
[whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889)
- Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889)
- Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889)
- Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889)
- Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889)
- Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889)
- Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889)
- Re: [whatwg/url] URLSearchParams inconsistent behavior with multiple same-name parameters leads to data loss on backend (Issue #889)
Re: [w3ctag/design-reviews] Prompt API (Issue #1093)
- Re: [w3ctag/design-reviews] Prompt API (Issue #1093)
- Re: [w3ctag/design-reviews] Prompt API (Issue #1093)
- Re: [w3ctag/design-reviews] Prompt API (Issue #1093)
- Re: [w3ctag/design-reviews] Prompt API (Issue #1093)
Re: [whatwg/storage] Add a nonce (ephemeral token) to the Storage Key (Issue #183)
[w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799)
- Re: [w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799)
- Re: [w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799)
- Re: [w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799)
- Re: [w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799)
- Re: [w3c/ServiceWorker] Requests from <object> elements are not intercepted (Issue #1799)
[w3ctag/design-reviews] WG New Spec: RDF 1.2 N-Triples (Issue #1161)
[w3ctag/design-reviews] WG New Spec: RDF 1.2 Semantics (Issue #1160)
[w3ctag/design-reviews] WG New Spec: RDF 1.2 Concepts and Abstract Data Model (Issue #1159)
[w3c/uievents] Initial 'source' defn (PR #405)
- Re: [w3c/uievents] Initial 'source' defn (PR #405)
- Re: [w3c/uievents] Initial 'source' defn (PR #405)
[whatwg/dom] Allow `MutationObserver` to observe across `<slot>`s (Issue #1415)
Re: [whatwg/dom] Define XSLTProcessor (#181)
[w3c/ServiceWorker] Proposal: Support No-Vary-Search header in Cache API (Issue #1798)
- Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798)
- Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798)
- Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798)
- Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798)
- Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798)
- Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798)
- Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798)
- Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798)
- Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798)
[w3c/screen-orientation] chore: tidy up document (PR #274)
Re: [w3c/screen-orientation] Allow unlock() to return a promise (PR #231)
[w3c/ServiceWorker] Feature Request: Support CacheStorage.match() options in SW Static Routing API cache source (Issue #1797)
- Re: [w3c/ServiceWorker] Feature Request: Support CacheStorage.match() options in SW Static Routing API cache source (Issue #1797)
- Re: [w3c/ServiceWorker] Support CacheStorage.match() options in SW Static Routing API cache source (Issue #1797)
- Re: [w3c/ServiceWorker] Support CacheStorage.match() options in SW Static Routing API cache source (Issue #1797)
Re: [w3c/screen-orientation] Use "user attention" of top-level traversable (Issue #252)
Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384)
[w3ctag/design-reviews] ViewTransitions: waitUntil() method (Issue #1158)
- Re: [w3ctag/design-reviews] ViewTransitions: waitUntil() method (Issue #1158)
- Re: [w3ctag/design-reviews] ViewTransitions: waitUntil() method (Issue #1158)
Re: [w3ctag/design-reviews] [wg/webextensions] Web Extensions Working Group (Issue #1138)
[whatwg/url] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888)
- Re: [whatwg/url] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888)
- Re: [whatwg/url] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888)
- Re: [whatwg/url] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888)
- Re: [whatwg/url] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888)
- Re: [whatwg/url] URL.toJSON() returns a string, not an object — misleading name, consider toJSONObject (Issue #888)
[whatwg/webidl] Help (Issue #1534)
[whatwg/webidl] Help (Issue #1533)
[whatwg/webidl] Hacker in my old account (Issue #1532)
[whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
- Re: [whatwg/url] Simplify the public suffix and registrable domain definitions (PR #887)
[whatwg/fetch] `Response.error` / `Response.redirect` should return object whose headers are mutable, as well as `Response.json` (Issue #1868)
- Re: [whatwg/fetch] `Response.error` / `Response.redirect` should return object whose headers are mutable, as well as `Response.json` (Issue #1868)
- Re: [whatwg/fetch] `Response.redirect` should return object whose headers are mutable, as well as `Response.json` (Issue #1868)
- Re: [whatwg/fetch] `Response.redirect` should return object whose headers are mutable, as well as `Response.json` (Issue #1868)
Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
Re: [w3c/manifest] Use URLPattern for scope member (#1002)
Re: [w3c/IndexedDB] TPAC 2025 status report (Issue #469)
Re: [w3c/IndexedDB] TPAC 2024: Discussion Topics (Issue #422)
[WICG/webcomponents] Manual slot assignment and slot elements in consuming components (Issue #1115)
Re: [w3ctag/design-reviews] Reduce Accept-Language (Issue #1078)
[w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
- Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
- Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
- Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
- Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
- Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
- Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
- Re: [w3c/screen-orientation] Add can-lock-orientation CSS media feature (PR #273)
Re: [w3c/screen-orientation] TPAC 2025 status report (Issue #258)
[w3c/screen-orientation] Add hidden document monitoring in parallel orientation lock steps (PR #272)
- Re: [w3c/screen-orientation] Add hidden document monitoring in parallel orientation lock steps (PR #272)
- Re: [w3c/screen-orientation] Add hidden document monitoring in parallel orientation lock steps (PR #272)
[w3c/screen-orientation] Standardize window.orientation API (PR #271)
[w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270)
- Re: [w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270)
- Re: [w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270)
- Re: [w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270)
- Re: [w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270)
- Re: [w3c/screen-orientation] Add continuous monitoring for pre-lock conditions (PR #270)
Re: [w3c/screen-orientation] Missing tasks in parallel steps in Screen Orientation (Issue #253)
[whatwg/fullscreen] Add pending fullscreen request flag and promise to document state (PR #251)
[w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269)
- Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269)
- Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269)
- Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269)
- Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269)
- Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269)
- Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269)
- Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269)
- Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269)
- Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269)
- Re: [w3c/screen-orientation] Refactor fullscreen rejection handling to use WebIDL react pattern (PR #269)
Re: [w3c/gamepad] TPAC 2025 status report (Issue #226)
- Re: [w3c/gamepad] TPAC 2025 status report (Issue #226)
- Re: [w3c/gamepad] TPAC 2025 status report (Issue #226)
[w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404)
- Re: [w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404)
- Re: [w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404)
- Re: [w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404)
- Re: [w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404)
- Re: [w3c/uievents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (Issue #404)
[w3c/manifest] PWA Migration (Issue #1189)
Re: [w3c/screen-orientation] Complete self-reviews (#201)
[w3c/screen-orientation] Fix iframe promise rejection in unloading document cleanup (PR #268)
- Re: [w3c/screen-orientation] Fix iframe promise rejection in unloading document cleanup (PR #268)
- Re: [w3c/screen-orientation] Fix iframe promise rejection in unloading document cleanup (PR #268)
Re: [w3c/screen-orientation] Must natural orientation be detectable? (Issue #259)
Re: [w3c/screen-orientation] Fingerprinting risk: users that configure their device to not permit screen locking (Issue #260)
- Re: [w3c/screen-orientation] Fingerprinting risk: users that configure their device to not permit screen locking (Issue #260)
- Re: [w3c/screen-orientation] Fingerprinting risk: users that configure their device to not permit screen locking (Issue #260)
Re: [w3c/screen-orientation] Editorial: pre-lock conditions definition placement (Issue #261)
[w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
- Re: [w3c/screen-orientation] Editorial: Fix pre-lock conditions algorithm structure (PR #267)
Re: [w3c/screen-orientation] Are ScreenOrientation change events scoped as tightly as possible (Issue #262)
- Re: [w3c/screen-orientation] Are ScreenOrientation change events scoped as tightly as possible (Issue #262)
- Re: [w3c/screen-orientation] Are ScreenOrientation change events scoped as tightly as possible (Issue #262)
- Re: [w3c/screen-orientation] Are ScreenOrientation change events scoped as tightly as possible (Issue #262)
- Re: [w3c/screen-orientation] Are ScreenOrientation change events scoped as tightly as possible (Issue #262)
[w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Switch to using fully active descendant of a top-level traversable with user attention (PR #266)
- Re: [w3c/screen-orientation] Address privacy review feedback (PR #266)
- Re: [w3c/screen-orientation] Address privacy review feedback (PR #266)
- Re: [w3c/screen-orientation] Address privacy review feedback (PR #266)
- Re: [w3c/screen-orientation] Address privacy review feedback (PR #266)
- Re: [w3c/screen-orientation] Address privacy review feedback (PR #266)
- Re: [w3c/screen-orientation] Address privacy review feedback (PR #266)
- Re: [w3c/screen-orientation] Address privacy review feedback (PR #266)
- Re: [w3c/screen-orientation] Address privacy review feedback (PR #266)
- Re: [w3c/screen-orientation] Address privacy review feedback (PR #266)
- Re: [w3c/screen-orientation] Address privacy review feedback (PR #266)
- Re: [w3c/screen-orientation] Address privacy review feedback (PR #266)
[whatwg/xhr] `ProgressEvent.loaded` references decompressed length, but `total` references the Content-Length header (Issue #403)
[w3c/screen-orientation] Editorial: change clicking to selecting (PR #265)
- Re: [w3c/screen-orientation] Editorial: change clicking to selecting (PR #265)
- Re: [w3c/screen-orientation] Editorial: change clicking to selecting (PR #265)
Re: [w3ctag/design-reviews] [ig/me] Media & Entertainment Interest Group Charter (Issue #1154)
Re: [w3ctag/design-reviews] WG New Spec: Direction feature for `scroll-state()` query (Issue #1153)
Re: [w3ctag/design-reviews] The `interesttarget` attribute (Issue #1058)
[w3c/ServiceWorker] Synthetic Response via Static Routing API (Issue #1796)
Re: [w3ctag/design-reviews] WG Revision: Screen Orientation (Issue #1155)
[w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478)
- Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478)
- Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478)
- Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478)
- Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478)
- Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478)
- Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478)
- Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478)
- Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478)
Re: [w3ctag/design-reviews] Other Spec Review: TCP Socket Pool Limit Randomization (Issue #1151)
[whatwg/webidl] Pls. We are the right family (Issue #1531)
- Re: [whatwg/webidl] Pls. We are the right family (Issue #1531)
- Re: [whatwg/webidl] Pls. We are the right family (Issue #1531)
- Re: [whatwg/webidl] Pls. We are the right family (Issue #1531)
Re: [w3c/uievents] Need virtual key codes (Issue #377)
Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152)
[w3c/screen-orientation] Some Code Samples have code references in orange/light blue color combination which has 2.9:1 contrast (should be 4.5:1) (Issue #264)
- Re: [w3c/screen-orientation] Some Code Samples have code references in orange/light blue color combination which has 2.9:1 contrast (should be 4.5:1) (Issue #264)
- Re: [w3c/screen-orientation] Some Code Samples have code references in orange/light blue color combination which has 2.9:1 contrast (should be 4.5:1) (Issue #264)
[w3c/screen-orientation] Wording change; adjust term "clicking" to "Select" to reflect multiple ways to activate Lock/Unlock (Issue #263)
- Re: [w3c/screen-orientation] Wording change; adjust term "clicking" to "Select" to reflect multiple ways to activate Lock/Unlock (Issue #263)
- Re: [w3c/screen-orientation] Wording change; adjust term "clicking" to "Select" to reflect multiple ways to activate Lock/Unlock (Issue #263)
- Re: [w3c/screen-orientation] Wording change; adjust term "clicking" to "Select" to reflect multiple ways to activate Lock/Unlock (Issue #263)
[whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
- Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
- Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
- Re: [whatwg/fetch] Handle `Unencoded-Digest` assertions. (PR #1867)
Re: [w3ctag/design-reviews] Other Spec Review: TCP Socket Pool per-Top-Level-Site (Issue #1151)
[w3c/IndexedDB] In "object store storage operation", be more explicit about how to handle ConstraintError from an index (Issue #477)
Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support Structured JSON Responses from IdPs (Issue #1147)
- Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support Structured JSON Responses from IdPs (Issue #1147)
- Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support Structured JSON Responses from IdPs (Issue #1147)
- Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support Structured JSON Responses from IdPs (Issue #1147)
Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136)
- Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136)
- Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136)
- Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136)
- Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136)
- Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136)
- Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136)
- Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136)
[w3c/uievents] Add new property to `InputEvent` to determine whether (Issue #403)
- Re: [w3c/uievents] Add new property to `InputEvent` to determine whether the text being input by IME has just been confirmed without help of `compositionend` (Issue #403)
- Re: [w3c/uievents] Add new property to `InputEvent` to determine whether the text being input by IME has just been confirmed without help of `compositionend` (Issue #403)
Re: [w3c/permissions] Add an optional `topLevelOrigin` argument to `permissions.setPermission` WebDriver BiDi command (Issue #450)
[whatwg/webidl] Intent to use constructor steps (Issue #1530)
[whatwg/url] URL (Issue #886)
[w3c/IndexedDB] Transactions should be marked as inactive during key serialization (Issue #476)
- Re: [w3c/IndexedDB] Transactions should be marked as inactive during key serialization (Issue #476)
- Re: [w3c/IndexedDB] Transactions should be marked as inactive during key serialization (Issue #476)
- Re: [w3c/IndexedDB] Transactions should be marked as inactive during key serialization (Issue #476)
- Re: [w3c/IndexedDB] Transactions should be marked as inactive during key serialization (Issue #476)
Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
Re: [whatwg/webidl] Add disposer and async_disposer (PR #1488)
Re: [WICG/webcomponents] Proposal: Allow custom elements to be in any namespace (#634)
[w3c/uievents] Proposal: use `relatedTarget` for click events originated from labels (Issue #402)
- Re: [w3c/uievents] Proposal: use `relatedTarget` for click events originated from labels (Issue #402)
- Re: [w3c/uievents] Proposal: use `relatedTarget` for click events originated from labels (Issue #402)
Re: [w3c/ServiceWorker] API to tell developers why the SW was killed (#1101)
Re: [whatwg/dom] Add reference target to shadow root (PR #1353)
Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400)
- Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400)
- Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400)
- Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400)
- Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400)
Re: [w3c/ServiceWorker] Add ServiceWorker.prototype.registration (#798)
Re: [w3c/ServiceWorker] consider exposing self.clients on window and other worker globals (#955)
[whatwg/url] 50337978316 (Issue #885)
[whatwg/url] 9930017996@Upi (Issue #884)
- Re: [whatwg/url] 9930017996@Upi (Issue #884)
- Re: [whatwg/url] 9930017996@Upi (Issue #884)
- Re: [whatwg/url] 9930017996@Upi (Issue #884)
[whatwg/dom] custom element registry mutability in an element (Issue #1414)
- Re: [whatwg/dom] custom element registry mutability in an element (Issue #1414)
- Re: [whatwg/dom] custom element registry mutability in an element (Issue #1414)
- Re: [whatwg/dom] custom element registry mutability in an element (Issue #1414)
- Re: [whatwg/dom] custom element registry mutability in an element (Issue #1414)
- Re: [whatwg/dom] custom element registry mutability in an element (Issue #1414)
Re: [w3c/ServiceWorker] Meta: move the specification to the top-level directory (#1009)
Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224)
[w3ctag/design-reviews] WG New Spec: DID Resolution (Issue #1157)
- Re: [w3ctag/design-reviews] WG New Spec: DID Resolution (Issue #1157)
- Re: [w3ctag/design-reviews] WG New Spec: DID Resolution (Issue #1157)
Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015)
[whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413)
- Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413)
Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843)
- Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843)
- Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843)
- Re: [whatwg/fetch] WIP: Add a mechanism to fetch to track progress (PR #1843)
Re: [w3ctag/design-reviews] Incubation: Preventing User Dictionary Leaks via ::spelling-error and ::grammar-error CSS Pseudo-Elements (Issue #1148)
- Re: [w3ctag/design-reviews] Incubation: Preventing User Dictionary Leaks via ::spelling-error and ::grammar-error CSS Pseudo-Elements (Issue #1148)
- Re: [w3ctag/design-reviews] Incubation: Preventing User Dictionary Leaks via ::spelling-error and ::grammar-error CSS Pseudo-Elements (Issue #1148)
Re: [w3c/editing] July 2025 meeting cancelled due to summer holidays (Issue #489)
Re: [w3c/editing] Nested editing hosts do not need to be wrapped in insertParagraph (Issue #490)
- Re: [w3c/editing] Nested editing hosts do not need to be wrapped in insertParagraph (Issue #490)
- Re: [w3c/editing] Nested editing hosts do not need to be wrapped in insertParagraph (Issue #490)
- Re: [w3c/editing] Nested editing hosts do not need to be wrapped in insertParagraph (Issue #490)
Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240)
Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support showing third-party iframe origins in the UI (Issue #1145)
- Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support showing third-party iframe origins in the UI (Issue #1145)
- Re: [w3ctag/design-reviews] WG New Spec: FedCM—Support showing third-party iframe origins in the UI (Issue #1145)
Re: [w3ctag/design-reviews] WG Revision: Geolocation (Issue #1144)
Re: [w3c/ServiceWorker] Service worker client URL discrepancy (#1515)
- Re: [w3c/ServiceWorker] Service worker client URL discrepancy (#1515)
- Re: [w3c/ServiceWorker] Service worker client URL discrepancy (#1515)
[whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)
[whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412)
- Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412)
- Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412)
- Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412)
- Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412)
- Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412)
- Re: [whatwg/dom] Custom element registry handling on insert after adopt (Issue #1412)
Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
- Re: [whatwg/fetch] [WebDriver BiDi] emulated network offline (PR #1852)
[whatwg/dom] tetooo (Issue #1411)
- Re: [whatwg/dom] tetooo (Issue #1411)
- Re: [whatwg/dom] tetooo (Issue #1411)
- Re: [whatwg/dom] tetooo (Issue #1411)
[whatwg/dom] https://github.com/Teto-07/Mini-Inventory-and-Sales-Management-System/issues/new/choose (Issue #1410)
- Re: [whatwg/dom] https://github.com/Teto-07/Mini-Inventory-and-Sales-Management-System/issues/new/choose (Issue #1410)
- Re: [whatwg/dom] https://github.com/Teto-07/Mini-Inventory-and-Sales-Management-System/issues/new/choose (Issue #1410)
- Re: [whatwg/dom] https://github.com/Teto-07/Mini-Inventory-and-Sales-Management-System/issues/new/choose (Issue #1410)
- Re: [whatwg/dom] https://github.com/Teto-07/Mini-Inventory-and-Sales-Management-System/issues/new/choose (Issue #1410)
[whatwg/fetch] Http parsing Carlyluminatti (Issue #1866)
- Re: [whatwg/fetch] Http parsing Carlyluminatti (Issue #1866)
- Re: [whatwg/fetch] Http parsing Carlyluminatti (Issue #1866)
Re: [WICG/webcomponents] Observe ShadowRoot attachment (#204)
- Re: [WICG/webcomponents] Observe ShadowRoot attachment (#204)
- Re: [WICG/webcomponents] Observe ShadowRoot attachment (#204)
Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287)
Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
- Re: [whatwg/dom] Integrate Trusted Types enforcement into attribute handling (PR #1268)
[whatwg/streams] Allow error to be provided to reader.releaseLock() (Issue #1358)
Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135)
- Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135)
- Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135)
- Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135)
- Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135)
- Re: [w3ctag/design-reviews] Incubation: Inline Integrity (Issue #1135)
[w3c/permissions] chore(tidy): tidy up document (PR #470)
[w3ctag/design-reviews] WG Revision: CSS Color Adjust Level 1 (Issue #1156)
- Re: [w3ctag/design-reviews] WG Revision: CSS Color Adjust Level 1 (Issue #1156)
- Re: [w3ctag/design-reviews] WG Revision: CSS Color Adjust Level 1 (Issue #1156)
[w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188)
- Re: [w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188)
- Re: [w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188)
- Re: [w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188)
- Re: [w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188)
- Re: [w3c/manifest] rdlmNdl mjd jy jrud (Issue #1188)
[whatwg/fetch] static method: `Response.html`? (Issue #1865)
- Re: [whatwg/fetch] static method: `Response.html`? (Issue #1865)
- Re: [whatwg/fetch] static method: `Response.html`? (Issue #1865)
- Re: [whatwg/fetch] static method: `Response.html`? (Issue #1865)
- Re: [whatwg/fetch] static method: `Response.html`? (Issue #1865)
- Re: [whatwg/fetch] static method: `Response.html`? (Issue #1865)
Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406)
- Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406)
- Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406)
- Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406)
- Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406)
- Re: [whatwg/dom] Proposal: moveOrInsertBefore() (Issue #1406)
Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
- Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)
Re: [whatwg/xhr] Clarify if `ProgressEvent.loaded` should indicate the size of compress, or uncompressed, data (Issue #388)
- Re: [whatwg/xhr] Clarify if `ProgressEvent.loaded` should indicate the size of compress, or uncompressed, data (Issue #388)
- Re: [whatwg/xhr] Clarify if `ProgressEvent.loaded` should indicate the size of compress, or uncompressed, data (Issue #388)
- Re: [whatwg/xhr] Clarify if `ProgressEvent.loaded` should indicate the size of compress, or uncompressed, data (Issue #388)
[w3c/IndexedDB] Explicitly define how to handle `queryOrOptions` being omitted in `getAll`/`getAllKeys` (Issue #475)
[whatwg/dom] Make attachShadow() use the global registry by default (PR #1409)
- Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409)
- Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409)
- Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409)
- Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409)
- Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409)
- Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409)
- Re: [whatwg/dom] Make attachShadow() use the global registry by default (PR #1409)
[whatwg/fetch] Susant edit (PR #1864)
[whatwg/fetch] done (PR #1863)
Re: [w3c/ServiceWorker] Allow the service worker to work in the background without stopping for installed PWA (Issue #1728)
- Re: [w3c/ServiceWorker] Allow the service worker to work in the background without stopping for installed PWA (Issue #1728)
- Re: [w3c/ServiceWorker] Allow the service worker to work in the background without stopping for installed PWA (Issue #1728)
Re: [w3c/uievents] Click event is not fired when the node is removed and then added back (#141)
Re: [w3c/ServiceWorker] Auto-cache imported scripts (#908)
- Re: [w3c/ServiceWorker] Auto-cache imported scripts (#908)
- Re: [w3c/ServiceWorker] Auto-cache imported scripts (#908)
- Re: [w3c/ServiceWorker] Auto-cache imported scripts (#908)
Re: [w3c/ServiceWorker] Expose fragments cross-origin for subresources (#910)
- Re: [w3c/ServiceWorker] Expose fragments cross-origin for subresources (#910)
- Re: [w3c/ServiceWorker] Expose fragments cross-origin for subresources (#910)
Re: [w3c/ServiceWorker] Handle Fetch "shift+reload" (#952)
Re: [w3c/ServiceWorker] Handle the quota exceeded error globally (#971)
Re: [w3c/ServiceWorker] Get Cache Size (#1059)
[w3c/ServiceWorker] Move spec files to root directory and remove unused files (PR #1794)
- Re: [w3c/ServiceWorker] Move spec files to root directory and remove unused files (PR #1794)
- Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794)
- Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794)
- Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794)
- Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794)
- Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794)
- Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794)
- Re: [w3c/ServiceWorker] [Editorial] Move spec files to root directory and remove unused files (PR #1794)
[whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
- Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)
[whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408)
- Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408)
- Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408)
- Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408)
- Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408)
- Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408)
- Re: [whatwg/dom] customElementRegistry.initialize should provoke custom elements to upgrade (Issue #1408)
[whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862)
- Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862)
- Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862)
- Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862)
- Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862)
- Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862)
- Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862)
- Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862)
- Re: [whatwg/fetch] Add a textStream() method to the Body mixin (PR #1862)
[whatwg/fetch] Convenience method to stream a response as text (Issue #1861)
- Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861)
- Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861)
- Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861)
- Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861)
- Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861)
- Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861)
- Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861)
- Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861)
- Re: [whatwg/fetch] Convenience method to stream a response as text (Issue #1861)
Re: [w3ctag/design-reviews] Incubation: An `Origin` Object (Issue #1130)
- Re: [w3ctag/design-reviews] Incubation: An `Origin` Object (Issue #1130)
- Re: [w3ctag/design-reviews] Incubation: An `Origin` Object (Issue #1130)
- Re: [w3ctag/design-reviews] Incubation: An `Origin` Object (Issue #1130)
[WICG/webcomponents] Reference Target: Rethinking attribute reflection for invalid reference targets (Issue #1114)
- Re: [WICG/webcomponents] Reference Target: Rethinking attribute reflection for invalid reference targets (Issue #1114)
- Re: [WICG/webcomponents] Reference Target: Rethinking attribute reflection for invalid reference targets (Issue #1114)
- Re: [WICG/webcomponents] Reference Target: Rethinking attribute reflection for invalid reference targets (Issue #1114)
Re: [w3ctag/design-reviews] Incubation: FormControlRange - Live ranges for <input> and <textarea> (Issue #1142)
Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140)
- Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140)
- Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140)
- Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140)
- Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140)
- Re: [w3ctag/design-reviews] Incubation: `<geolocation>` element (part of PEPC) (Issue #1140)
Re: [whatwg/fetch] Throw `SecurityError` on non-trustworthy URLs in `fetchLater` (PR #1858)
[whatwg/encoding] Text(De|En)coder in WorkletGlobalScope (Issue #356)
- Re: [whatwg/encoding] Text(De|En)coder in WorkletGlobalScope (Issue #356)
- Re: [whatwg/encoding] Text(De|En)coder in WorkletGlobalScope (Issue #356)
[w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243)
- Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243)
- Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243)
- Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243)
- Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243)
- Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243)
- Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243)
Re: [whatwg/dom] Add FormControlRange interface (PR #1404)
- Re: [whatwg/dom] Add FormControlRange interface (PR #1404)
- Re: [whatwg/dom] Add FormControlRange interface (PR #1404)
Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134)
- Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134)
- Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134)
- Re: [w3ctag/design-reviews] Incubation: patching (interleaved out-of-order streaming) (Issue #1134)
Re: [w3ctag/design-reviews] [wg/json-ld] JSON-LD Working Group Charter (Issue #1150)
- Re: [w3ctag/design-reviews] [wg/json-ld] JSON-LD Working Group Charter (Issue #1150)
- Re: [w3ctag/design-reviews] [wg/json-ld] JSON-LD Working Group Charter (Issue #1150)
- Re: [w3ctag/design-reviews] [wg/json-ld] JSON-LD Working Group Charter (Issue #1150)
- Re: [w3ctag/design-reviews] [wg/json-ld] JSON-LD Working Group Charter (Issue #1150)
Re: [whatwg/dom] Proposal to improve the DOM creation api (#150)
[w3c/permissions] Use embeddedOrigin instead of topLevelOrigin in setPermission (PR #469)
- Re: [w3c/permissions] Use embeddedOrigin instead of topLevelOrigin in setPermission (PR #469)
- Re: [w3c/permissions] Use embeddedOrigin instead of topLevelOrigin in setPermission (PR #469)
[whatwg/fetch] Call webdriver bidi hooks to clone request and response bodies (PR #1860)
Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239)
- Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239)
- Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event specification with ClipboardChangeEventInit dictionary (PR #239)
Re: [w3c/ServiceWorker] A way to specify a pattern of destination URLs to hit/skip SW (#1454)
[w3c/ServiceWorker] Need for a mechanism to detect supported conditions and sources in the SW Static Routing API (Issue #1793)
Re: [whatwg/dom] attachShadow default custom element registry (Issue #1407)
- Re: [whatwg/dom] attachShadow default custom element registry (Issue #1407)
- Re: [whatwg/dom] attachShadow default custom element registry (Issue #1407)
- Re: [whatwg/dom] attachShadow default custom element registry (Issue #1407)
Re: [w3c/ServiceWorker] Broken references in Service Workers Nightly (Issue #1669)
- Re: [w3c/ServiceWorker] Broken references in Service Workers Nightly (Issue #1669)
- Re: [w3c/ServiceWorker] Broken references in Service Workers Nightly (Issue #1669)