[w3ctag/design-reviews] Incubation: (Issue #1252)
[w3c/ServiceWorker] Editorial: queue a task to reject promise in InstallEvent.addRoutes (PR #1839)
Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764)
[w3c/editing] Actually return true from indent command (PR #547)
Re: [w3c/clipboard-apis] Remove clipboardchange event (and replace it possibly with a promise returning method) (Issue #228)
Re: [w3c/clipboard-apis] ClipboardChange even spec: Callout details for cross-origin iframes and fencedframes (Issue #226)
Re: [w3c/ServiceWorker] w3c/ServiceWorker (Issue #1826)
[whatwg/fetch] Make `Response.redirect()` headers mutable (PR #1944)
Re: [w3c/uievents] Use `USVString` for input and composition events (Issue #352)
[w3ctag/design-reviews] Other Spec Review: JS Self-Profiling Markers (ProfilerSample.marker) (Issue #1251)
Re: [whatwg/dom] Add reference target to shadow root (PR #1353)
Re: [w3ctag/design-reviews] WG New Spec: Web Sustainability Guidelines (Issue #1181)
Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203)
Re: [w3ctag/design-reviews] Media Capture Capability Elements (part of PEPC) (Issue #1218)
[w3ctag/design-reviews] Incubation: WebRTC Diagnostic Logging (Issue #1250)
[whatwg/webidl] Intent to use Constants (Issue #1623)
[w3ctag/design-reviews] WG New Spec: Recognized Entities v1.0 (Issue #1249)
Re: [w3ctag/design-reviews] WG Revision: WebTransport (Issue #1212)
Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136)
[w3c/manifest] Should `display-mode` be gated for cross-origin iframes? (Issue #1239)
[w3c/manifest] editorial: add missing assertion to chosen-display-mode algorithm (PR #1238)
Re: [w3c/ServiceWorker] Request's origin needs to be set for [[Update]] algorithm (#1447)
Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273)
Re: [w3c/ServiceWorker] Add a WPT test for credentialed requests in register()/update (#1435)
Re: [w3c/ServiceWorker] Should update() always reject if there is an installing worker? (#1429)
Re: [w3c/ServiceWorker] Should we restore the registration record removing step in Clear Registration? (#1433)
Re: [w3c/ServiceWorker] What happens to the request body if the fetch isn't handled? (#1191)
Re: [w3c/manifest] user initiated 'uninstall' event (#1201)
[w3c/manifest] Editorial: don't reference WebIDL identifier (PR #1237)
[w3c/manifest] Tidied up document using tidy-html5 (PR #1236)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1236)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1236)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1236)
[w3c/manifest] Format U+002F character references using W3C I18N template (PR #1235)
- Re: [w3c/manifest] Format U+002F character references using W3C I18N template (PR #1235)
- Re: [w3c/manifest] Format U+002F character references using W3C I18N template (PR #1235)
[w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234)
- Re: [w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234)
- Re: [w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234)
- Re: [w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234)
- Re: [w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234)
- Re: [w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234)
[w3c/manifest] editorial: fix typos, grammar, and a stray definition (PR #1233)
- Re: [w3c/manifest] editorial: fix typos, grammar, and a stray definition (PR #1233)
- Re: [w3c/manifest] editorial: fix typos, grammar, and a stray definition (PR #1233)
- Re: [w3c/manifest] editorial: fix typos, grammar, and a stray definition (PR #1233)
[w3c/editing] When should metadata-content elements like <style> be editable? (Issue #546)
Re: [w3ctag/design-reviews] Incubation: Platform-provided behaviors for custom elements (Issue #1219)
[whatwg/webidl] DOMException name proposal (Issue #1622)
[w3c/manifest] Have an "Internationalization Considerations" section? (Issue #1232)
[w3c/manifest] Use template for character references (Issue #1231)
[w3c/manifest] Are `*_localized` items clearly allowed in shortcut items? (Issue #1230)
[w3c/manifest] Provide examples of non-ASCII in the path and host parts of `id` (Issue #1229)
Re: [w3c/screen-orientation] Fix iframe promise rejection in unloading document cleanup (PR #268)
[whatwg/webidl] Bocil smp (Issue #1621)
[w3c/screen-orientation] Editorial: add Léonie Watson as co-editor (PR #280)
Re: [w3c/screen-orientation] Should pending promise be abort if document isn't top-level? (Issue #257)
[w3c/screen-orientation] Square (1:1) screens fall outside both screen orientation values lists (Issue #279)
[w3c/screen-orientation] Editorial: clarify the natural screen orientation (PR #278)
- Re: [w3c/screen-orientation] Editorial: clarify the natural screen orientation (PR #278)
- Re: [w3c/screen-orientation] Editorial: clarify the natural screen orientation (PR #278)
[w3ctag/design-reviews] Other Spec Review: CSS scroll-axis-lock (Issue #1248)
- Re: [w3ctag/design-reviews] Other Spec Review: CSS scroll-axis-lock (Issue #1248)
- Re: [w3ctag/design-reviews] Other Spec Review: CSS scroll-axis-lock (Issue #1248)
[w3ctag/design-reviews] Question: can we better define the intention of the "disable scripting" user preference (Issue #1247)
[whatwg/dom] Scope-match a selectors string including a pseudo-element selector (Issue #1497)
[whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943)
- Re: [whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943)
- Re: [whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943)
- Re: [whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943)
- Re: [whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943)
- Re: [whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943)
Re: [w3ctag/design-reviews] Incubation: Proofreader API (Issue #1146)
[w3c/editing] IOS Safari: Ability to opt-out of Form assistant bar (which is useless for single-field editors and takes up a lot of space) (Issue #545)
Re: [w3ctag/design-reviews] Incubation: Autofill Event (Issue #1197)
[w3c/editing] Actually return true from forwarddelete (PR #544)
[whatwg/webidl] Intent to use Constants (Issue #1620)
[whatwg/dom] Order shadow root concepts consistently (PR #1496)
[whatwg/dom] Editorial: lean on early return in attach a shadow root (PR #1495)
[whatwg/webidl] Check for detached buffer source when checking if transferable is inverted (Issue #1619)
Re: [w3c/ServiceWorker] Build spec using travis (#1099)
Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267)
[whatwg/fullscreen] Review Draft Publication: July 2026 (PR #263)
- Re: [whatwg/fullscreen] Review Draft Publication: July 2026 (PR #263)
- Re: [whatwg/fullscreen] Review Draft Publication: July 2026 (PR #263)
[whatwg/dom] Restore active custom element constructor map entries after construction (PR #1494)
- Re: [whatwg/dom] Restore active custom element constructor map entries after construction (PR #1494)
- Re: [whatwg/dom] Restore active custom element constructor map entries after construction (PR #1494)
- Re: [whatwg/dom] Restore active custom element constructor map entries after construction (PR #1494)
- Re: [whatwg/dom] Restore active custom element constructor map entries after construction (PR #1494)
Re: [whatwg/streams] Use `async iterable` webidl type in ReadableStream.from (PR #1310)
[w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222)
- Re: [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222)
- Re: [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222)
- Re: [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222)
- Re: [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222)
- Re: [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222)
Re: [w3c/ServiceWorker] Should register() trigger an update if only updateViaCache changes? (#1414)
Re: [w3c/ServiceWorker] Consider exposing Page Lifecycle state to service-worker (#1345)
Re: [w3c/ServiceWorker] Is respondWith(fetch(event.request)) always the same as not calling respondWith()? (#1395)
Re: [w3c/ServiceWorker] spec should document Cache API HEIST mitigations (#1396)
Re: [w3c/ServiceWorker] Fully inline (.js + json manifest) service worker (#1392)
- Re: [w3c/ServiceWorker] Fully inline (.js + json manifest) service worker (#1392)
- Re: [w3c/ServiceWorker] Fully inline (.js + json manifest) service worker (#1392)
Re: [w3c/ServiceWorker] Add WPT for an in-scope iframe inside a data URL iframe. (#1393)
- Re: [w3c/ServiceWorker] Add WPT for an in-scope iframe inside a data URL iframe. (#1393)
- Re: [w3c/ServiceWorker] Add WPT for an in-scope iframe inside a data URL iframe. (#1393)
[w3c/ServiceWorker] Editorial: serialize CacheStorage access on a dedicated parallel queue (PR #1838)
[w3c/ServiceWorker] Editorial: queue a task in Cache API (PR #1837)
[w3c/ServiceWorker] Editorial: queue a task in Client / Clients API (PR #1836)
- Re: [w3c/ServiceWorker] Editorial: queue a task in Client / Clients API (PR #1836)
- Re: [w3c/ServiceWorker] Editorial: queue a task in Client / Clients API (PR #1836)
[w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerGlobalScope.skipWaiting (PR #1835)
- Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerGlobalScope.skipWaiting (PR #1835)
- Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerGlobalScope.skipWaiting (PR #1835)
[w3c/ServiceWorker] Editorial: queue a task in NavigationPreloadManager (PR #1834)
- Re: [w3c/ServiceWorker] Editorial: queue a task in NavigationPreloadManager (PR #1834)
- Re: [w3c/ServiceWorker] Editorial: queue a task in NavigationPreloadManager (PR #1834)
[w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerContainer.getRegistration (PR #1833)
- Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerContainer.getRegistration (PR #1833)
- Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerContainer.getRegistration (PR #1833)
- Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerContainer.getRegistration (PR #1833)
- Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerContainer.getRegistration (PR #1833)
Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198)
[w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246)
- Re: [w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246)
- Re: [w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246)
- Re: [w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246)
- Re: [w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246)
- Re: [w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246)
[w3c/editing] Spec for InsertImage command is (no longer) 'correct'. (Issue #543)
Re: [w3ctag/design-reviews] Other Spec Review: Single-Axis Scroll Containers (Issue #1222)
Re: [w3ctag/design-reviews] Other Spec Review: overscroll-behavior: chain (Issue #1228)
Re: [w3ctag/design-reviews] [wg/atag] Authoring Tools Accessibility Guidelines Group Charter (Issue #1241)
Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511)
Re: [whatwg/dom] Clarify create an element assertion (Issue #1338)
Re: [w3ctag/design-reviews] WG Revision: CSSPseudoElement (Issue #1233)
Re: [w3ctag/design-reviews] Other Spec Review: Responsively-sized iframes (Issue #1223)
[w3ctag/design-reviews] Question: Review manifest-first Web Install API (Issue #1245)
- Re: [w3ctag/design-reviews] Question: Review manifest-first Web Install API (Issue #1245)
- Re: [w3ctag/design-reviews] Question: Review manifest-first Web Install API (Issue #1245)
- Re: [w3ctag/design-reviews] Question: Review manifest-first Web Install API (Issue #1245)
- Re: [w3ctag/design-reviews] Question: Review manifest-first Web Install API (Issue #1245)
[w3c/manifest] Manifest name: USVString or not? (Issue #1228)
- Re: [w3c/manifest] Manifest name: USVString or not? (Issue #1228)
- Re: [w3c/manifest] Manifest name: USVString or not? (Issue #1228)
- Re: [w3c/manifest] Manifest name: USVString or not? (Issue #1228)
- Re: [w3c/manifest] Manifest name: USVString or not? (Issue #1228)
Re: [w3c/gamepad] Add device orientation support (Issue #211)
- Re: [w3c/gamepad] Add device orientation support (Issue #211)
- Re: [w3c/gamepad] Add device orientation support (Issue #211)
Re: [w3c/gamepad] DOM Elements Integration (Issue #227)
Re: [w3ctag/design-reviews] (brand new ✨) Web Install API (Issue #1051)
[whatwg/webidl] Intent to use Constants (Issue #1618)
- Re: [whatwg/webidl] Intent to use Constants (Issue #1618)
- Re: [whatwg/webidl] Intent to use Constants (Issue #1618)
[w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
- Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832)
[whatwg/streams] Revisiting ReadableStream.from(syncIter) and ReadableStream.from(str) (Issue #1376)
- Re: [whatwg/streams] Revisiting ReadableStream.from(syncIter) and ReadableStream.from(str) (Issue #1376)
- Re: [whatwg/streams] Revisiting ReadableStream.from(syncIter) and ReadableStream.from(str) (Issue #1376)
Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144)
[whatwg/dom] Factor out find a named element and rename a collection's nodes (PR #1493)
Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
- Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)
Re: [whatwg/dom] Define a mapping to a Selectors Element Tree (#542)
- Re: [whatwg/dom] Define a mapping to a Selectors Element Tree (#542)
- Re: [whatwg/dom] Define a mapping to a Selectors Element Tree (#542)
Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578)
[whatwg/fetch] Add onInformation interim response support (PR #1942)
[whatwg/fetch] Sending trailers (PR #1941)
Re: [whatwg/fetch] Trailer support in the API (#981)
[whatwg/fetch] Add .trailers to Response/Request (PR #1940)
- Re: [whatwg/fetch] Add .trailers to Response/Request (PR #1940)
- Re: [whatwg/fetch] Add .trailers to Response/Request (PR #1940)
[whatwg/dom] Copy a document's base URL when cloning (PR #1492)
Re: [whatwg/dom] `event.target` not cleared if event is not fired on `ShadowRoot` (Issue #1072)
[w3c/clipboard-apis] [Security Proposal] Allow ClipboardItem to accept a BufferSource such as Uint8Array to harmonize with memory sanitizations (Issue #251)
Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
- Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
- Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
- Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
- Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
- Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)
[whatwg/url] Ab (Issue #927)
Re: [w3c/pointerlock] Should not release pointer lock when pressing esc while fullscreen keyboard lock is active (Issue #110)
[w3c/gamepad] Trigger HTML activation (PR #230)
[w3c/clipboard-apis] "allowed to show a popup" definition link goes nowhere (Issue #250)
Re: [whatwg/dom] Define the realm of nodes (#977)
[whatwg/dom] Create nodes in the realm of the document they are created for (PR #1491)
- Re: [whatwg/dom] Create nodes in the realm of the document they are created for (PR #1491)
- Re: [whatwg/dom] Create nodes in the realm of the document they are created for (PR #1491)
- Re: [whatwg/dom] Create nodes in the realm of the document they are created for (PR #1491)
- Re: [whatwg/dom] Create nodes in the realm of the document they are created for (PR #1491)
Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292)
Re: [w3c/ServiceWorker] A description mistake in spec document (#1391)
Re: [w3c/ServiceWorker] clients.get() should not resolve before sandboxing determines the origin of the client (#1385)
- Re: [w3c/ServiceWorker] clients.get() should not resolve before sandboxing determines the origin of the client (#1385)
- Re: [w3c/ServiceWorker] clients.get() should not resolve before sandboxing determines the origin of the client (#1385)
Re: [w3c/gamepad] Should fire events instead of using passive model (#4)
[w3c/ServiceWorker] cache and cache-storage algos forgets to queue a task to resolve promise. (Issue #1831)
- Re: [w3c/ServiceWorker] cache and cache-storage algos forgets to queue a task to resolve promise. (Issue #1831)
- Re: [w3c/ServiceWorker] cache and cache-storage algos forgets to queue a task to resolve promise. (Issue #1831)
Re: [w3c/editing] Chrome: Selection barrier at details element when contenteditable=true (Issue #538)
Re: [whatwg/dom] Adopting children of an intentional null shadow root goes wrong (Issue #1429)
[w3c/uievents] Add normative note to spec regarding "modifier keys on mobile platforms" (Issue #417)
[w3c/manifest] "cannot be used together" editing woes (Issue #1227)
Re: [w3c/editing] forming of community editing group (Issue #541)
[w3c/editing] Inconsistent `KeyboardEvent.shiftKey` behavior for virtual keyboard autocapitalization (Issue #542)
- Re: [w3c/editing] Inconsistent `KeyboardEvent.shiftKey` behavior for virtual keyboard autocapitalization (Issue #542)
- Re: [w3c/editing] Inconsistent `KeyboardEvent.shiftKey` behavior for virtual keyboard autocapitalization (Issue #542)
Re: [whatwg/dom] What does adoptNode() return for DocumentFragment? (#813)
Re: [w3ctag/design-reviews] WG Revision: CSS Anchor Positioning Level 1 (Issue #1182)
Re: [whatwg/webidl] Is a function signature with a parameter type `(DOMString or Interface)` a footgun? (Issue #1604)
- Re: [whatwg/webidl] Is a function signature with a parameter type `(DOMString or Interface)` a footgun? (Issue #1604)
- Re: [whatwg/webidl] Is a function signature with a parameter type `(DOMString or Interface)` a footgun? (Issue #1604)
- Re: [whatwg/webidl] Is a function signature with a parameter type `(DOMString or Interface)` a footgun? (Issue #1604)
- Re: [whatwg/webidl] Is a function signature with a parameter type `(DOMString or Interface)` a footgun? (Issue #1604)
[whatwg/dom] Editorial: type arguments in event dispatch algorithms (PR #1490)
Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
Re: [w3c/screen-orientation] "natural" is ambiguous (Issue #275)
[whatwg/dom] Editorial: name event path items and clarify target selection (PR #1489)
[w3c/permissions] Rename document (Issue #478)
- Re: [w3c/permissions] Rename document (Issue #478)
- Re: [w3c/permissions] Rename document (Issue #478)
- Re: [w3c/permissions] Rename document (Issue #478)
- Re: [w3c/permissions] Rename document (Issue #478)
- Re: [w3c/permissions] Rename document (Issue #478)
- Re: [w3c/permissions] Rename document (Issue #478)
- Re: [w3c/permissions] Rename document (Issue #478)
- Re: [w3c/permissions] Rename document (Issue #478)
- Re: [w3c/permissions] Rename document (Issue #478)
- Re: [w3c/permissions] Rename document (Issue #478)
Re: [whatwg/dom] Element.matches and pseudo-elements (#185)
- Re: [whatwg/dom] Element.matches and pseudo-elements (#185)
- Re: [whatwg/dom] Element.matches and pseudo-elements (#185)
- Re: [whatwg/dom] Element.matches and pseudo-elements (#185)
- Re: [whatwg/dom] Element.matches and pseudo-elements (#185)
- Re: [whatwg/dom] Element.matches and pseudo-elements (#185)
Re: [whatwg/dom] replaceChild() has odd mutation observer behavior after #754 (#814)
Re: [w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172)
[whatwg/dom] Adopt node before removing child in replace (PR #1488)
- Re: [whatwg/dom] Adopt node before removing child in replace (PR #1488)
- Re: [whatwg/dom] Adopt node before removing child in replace (PR #1488)
- Re: [whatwg/dom] Adopt node before removing child in replace (PR #1488)
- Re: [whatwg/dom] Adopt node before removing child in replace (PR #1488)
Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
[whatwg/dom] Let replaceChildren() replace a document's children (PR #1487)
- Re: [whatwg/dom] Let replaceChildren() replace a document's children (PR #1487)
- Re: [whatwg/dom] Let replaceChildren() replace a document's children (PR #1487)
- Re: [whatwg/dom] Let replaceChildren() replace a document's children (PR #1487)
Re: [whatwg/dom] Trouble understanding a parable of specification, under the "ensure pre-insertion validity" list of steps (#870)
[whatwg/dom] Adopt a DocumentFragment with a host like any other node (PR #1486)
- Re: [whatwg/dom] Adopt a DocumentFragment with a host like any other node (PR #1486)
- Re: [whatwg/dom] Adopt a DocumentFragment with a host like any other node (PR #1486)
- Re: [whatwg/dom] Adopt a DocumentFragment with a host like any other node (PR #1486)
Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819)
Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412)
Re: [whatwg/dom] Define "has event listener" operation (#453)
Re: [whatwg/dom] Improving "find slottables" (Issue #1063)
Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564)
- Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564)
- Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564)
Re: [whatwg/dom] Which target could we expose in Event Timing? (#838)
Re: [whatwg/dom] Increase the ability to query whether the host environment supports a specific event (#968)
Re: [whatwg/dom] replaceChildren can not replace a Document's documentElement (Issue #1045)
[whatwg/dom] Clarify create an element assertion (PR #1485)
- Re: [whatwg/dom] Clarify create an element assertion (PR #1485)
- Re: [whatwg/dom] Clarify create an element assertion (PR #1485)
- Re: [whatwg/dom] Clarify create an element assertion (PR #1485)
Re: [whatwg/dom] Proposal: Allow WebIDL bindings to expose method parameters' types (Issue #1182)
Re: [whatwg/dom] Proposal: A new way to do feature detection for members (Issue #1181)
Re: [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183)
Re: [whatwg/dom] Variable strength aborting (Issue #1215)
Re: [whatwg/dom] Make it possible to wrap [parts of] the contents of a <textarea> or <input> in a Range (Issue #1375)
[whatwg/dom] Editorial: improve ensure pre-insert validity (PR #1484)
- Re: [whatwg/dom] Editorial: improve ensure pre-insert validity (PR #1484)
- Re: [whatwg/dom] Editorial: improve ensure pre-insert validity (PR #1484)
- Re: [whatwg/dom] Editorial: improve ensure pre-insert validity (PR #1484)
- Re: [whatwg/dom] Editorial: improve ensure pre-insert validity (PR #1484)
Re: [whatwg/dom] Please add the links to the old versions? (Issue #1067)
[whatwg/webidl] Intent to use bigint/numeric union (Issue #1617)
Re: [w3ctag/design-reviews] Other Spec Review: `textStream()` for `Blob` and `Body` (Issue #1236)
- Re: [w3ctag/design-reviews] Other Spec Review: `textStream()` for `Blob` and `Body` (Issue #1236)
- Re: [w3ctag/design-reviews] Other Spec Review: `textStream()` for `Blob` and `Body` (Issue #1236)
- Re: [w3ctag/design-reviews] Other Spec Review: `textStream()` for `Blob` and `Body` (Issue #1236)
Re: [whatwg/dom] Blame stopped working (Issue #1367)
Re: [whatwg/dom] Expose document fragment serialization algorithm (#965)
Re: [whatwg/dom] Strange behavior with `insertBefore` vs `appendChild` and transitions (#880)
Re: [whatwg/dom] Element.replaceChild should allow for `old, new` argument ordering if `new` is a new element and `old` is a child of Element (#847)
Re: [whatwg/dom] classes are compared without Unicode normalization (#793)
Re: [whatwg/dom] Why is `createProcessingInstruction(…)` allowed in HTML, but `createCDATASection(…)` isn’t? (#798)
Re: [whatwg/dom] Address feedback from Travis and Sangwhan (#702)
[whatwg/dom] Editorial: address assorted feedback (PR #1483)
Re: [whatwg/dom] Refactor toggle attribute (#663)
Re: [whatwg/dom] Abstract common logic in toggleAttribute() and setAttribute()? (#657)
Re: [whatwg/dom] "To validate and extract a namespace and qualifiedName" could use clarification about case-insensitivity (#680)
Re: [whatwg/dom] Allow <menu>, <ul>, <ol>, <li> to attach shadow (#676)
Re: [whatwg/dom] Make "inner invoke" use "remove an event listener" (#758)
Re: [whatwg/dom] Make "inner invoke" use "remove an event listener" (#651)
Re: [whatwg/dom] document.open()'s mutation event suppression (#640)
Re: [whatwg/dom] Editorial: consider linking "present" consistently (#574)
[whatwg/dom] Editorial: remove remaining dictionary "is present" usage (PR #1482)
Re: [whatwg/dom] Node Tree section should probably include Attr (#457)
Re: [whatwg/dom] Ranges and Attr nodes (#607)
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] 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: [whatwg/dom] Use `commonAncestorContainer` in concept-range-clone (#56)
[whatwg/dom] Editorial: abstract getting the common ancestor (PR #1481)
- Re: [whatwg/dom] Editorial: abstract getting the common ancestor (PR #1481)
- Re: [whatwg/dom] Editorial: abstract getting the common ancestor (PR #1481)
[w3c/manifest] Create SECURITY.md (PR #1226)
[w3c/manifest] Prepare the Manifest spec for CR (Issue #1225)
Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154)
[whatwg/webidl] Intent to use Constants (Issue #1616)
[whatwg/dom] Restore deep cloning of shadow root contents. (PR #1480)
- Re: [whatwg/dom] Restore deep cloning of shadow root contents. (PR #1480)
- Re: [whatwg/dom] Restore deep cloning of shadow root contents. (PR #1480)
Re: [whatwg/streams] Use `async_sequence` in `ReadableStream.from` (PR #1372)
- Re: [whatwg/streams] Use `async_sequence` in `ReadableStream.from` (PR #1372)
- Re: [whatwg/streams] Use `async_sequence` in `ReadableStream.from` (PR #1372)
[w3ctag/design-reviews] [wg/webappsec] Web Application Security Working Group Charter (Issue #1244)
- Re: [w3ctag/design-reviews] [wg/webappsec] Web Application Security Working Group Charter (Issue #1244)
- Re: [w3ctag/design-reviews] [wg/webappsec] Web Application Security Working Group Charter (Issue #1244)
[whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926)
- Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926)
- Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926)
- Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926)
- Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926)
- Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926)
- Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926)
- Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926)
- Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926)
- Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926)
- Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926)
Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551)
- Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551)
- Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551)
Re: [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173)
Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437)
Re: [whatwg/dom] Editorial: make adopt traverse the tree less (PR #1427)
Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400)
[w3c/ServiceWorker] Redesign Service-Worker-Allowed header extraction (PR #1830)
- Re: [w3c/ServiceWorker] Redesign Service-Worker-Allowed header extraction (PR #1830)
- Re: [w3c/ServiceWorker] Redesign Service-Worker-Allowed header extraction (PR #1830)
- Re: [w3c/ServiceWorker] Redesign Service-Worker-Allowed header extraction (PR #1830)
[w3c/manifest] Split privacy and security considerations into separate sections (PR #1224)
- Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224)
- Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224)
- Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224)
- Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224)
- Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224)
- Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224)
Re: [w3c/ServiceWorker] ready promise is kind of weird after you call unregister() (#1279)
Re: [w3c/ServiceWorker] Cache's put() says it clones the response (#1382)
Re: [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367)
Re: [w3c/ServiceWorker] ready promise doesn't work right when controlling registration is resurrected (#1198)
Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206)
Re: [w3c/ServiceWorker] Should a service worker be allowed to register new service workers? (#1117)
- Re: [w3c/ServiceWorker] Should a service worker be allowed to register new service workers? (#1117)
- Re: [w3c/ServiceWorker] Should a service worker be allowed to register new service workers? (#1117)
- Re: [w3c/ServiceWorker] Should a service worker be allowed to register new service workers? (#1117)
Re: [w3c/ServiceWorker] Web Authentication API access in service worker (#1369)
Re: [whatwg/webidl] Update PropertyDescriptor [[Get]]/[[Set]] to [[Getter]]/[[Setter]] (PR #1613)
- Re: [whatwg/webidl] Update PropertyDescriptor [[Get]]/[[Set]] to [[Getter]]/[[Setter]] (PR #1613)
- Re: [whatwg/webidl] Update PropertyDescriptor [[Get]]/[[Set]] to [[Getter]]/[[Setter]] (PR #1613)
[w3c/manifest] [DRAFT] Check against i18n Review Checklist (Issue #1223)
Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413)
- Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413)
- Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413)
- Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413)
- Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413)
[w3c/manifest] Tidied up document using tidy-html5 (PR #1222)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1222)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1222)
- Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1222)
Re: [WICG/webcomponents] Reference Target "phase 2": seeking feedback and use cases (Issue #1111)
Re: [whatwg/fetch] Anchor permanence for https://fetch.spec.whatwg.org/#methods (Issue #1932)
[whatwg/fetch] Meta: make methods a required ID (PR #1939)
Re: [w3c/ServiceWorker] Redesign of "extract header list values" expected (#1360)
Re: [whatwg/url] Meta: UTS46 feedback (Issue #744)
[w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221)
- Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221)
- Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221)
- Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221)
- Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221)
- Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221)
- Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221)
[w3c/manifest] chore: update SchemaStore URLs to www.schemastore.org (PR #1220)
- Re: [w3c/manifest] chore: update SchemaStore URLs to www.schemastore.org (PR #1220)
- Re: [w3c/manifest] chore: update SchemaStore URLs to www.schemastore.org (PR #1220)
- Re: [w3c/manifest] chore: update SchemaStore URLs to www.schemastore.org (PR #1220)
- Re: [w3c/manifest] chore: fix SchemaStore links and drop the embedded schema view (PR #1220)
- Re: [w3c/manifest] chore: fix SchemaStore links and drop the embedded schema view (PR #1220)
- Re: [w3c/manifest] chore: fix SchemaStore links and drop the embedded schema view (PR #1220)
- Re: [w3c/manifest] chore: fix SchemaStore links and drop the embedded schema view (PR #1220)
Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
- Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)
Re: [w3c/manifest] Redefine application context on top-level traversable (PR #1219)
- Re: [w3c/manifest] Redefine application context on top-level traversable (PR #1219)
- Re: [w3c/manifest] Redefine application context on top-level traversable (PR #1219)
- Re: [w3c/manifest] Redefine application context on top-level traversable (PR #1219)
- Re: [w3c/manifest] Redefine application context on top-level traversable (PR #1219)
Re: [whatwg/dom] Add and export get an element by ID (PR #1476)
Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (PR #1205)
[whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479)
- Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479)
- Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479)
- Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479)
- Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479)
- Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479)
- Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479)
Re: [whatwg/dom] NodeIterator's pre-removing steps does not match browsers (#907)
Re: [whatwg/dom] Fix NodeIterator pre-remove steps for ancestors of root (PR #1477)
- Re: [whatwg/dom] Fix NodeIterator pre-remove steps for ancestors of root (PR #1477)
- Re: [whatwg/dom] Fix NodeIterator pre-remove steps for ancestors of root (PR #1477)
- Re: [whatwg/dom] Fix NodeIterator pre-remove steps for ancestors of root (PR #1477)
[whatwg/url] Report a validation error for IPv4 addresses from non-ASCII input (PR #925)
- Re: [whatwg/url] Report a validation error for IPv4 addresses from non-ASCII input (PR #925)
- Re: [whatwg/url] Report a validation error for IPv4 addresses from non-ASCII input (PR #925)
[w3ctag/design-reviews] Service discovery (Issue #1243)
[w3ctag/design-reviews] Other Spec Review: HTML menu elements (Issue #1242)
- Re: [w3ctag/design-reviews] Other Spec Review: HTML menu elements (Issue #1242)
- Re: [w3ctag/design-reviews] Other Spec Review: HTML menu elements (Issue #1242)
- Re: [w3ctag/design-reviews] Other Spec Review: HTML menu elements (Issue #1242)
Re: [w3ctag/design-reviews] Other Spec Review: CRA web browser standard (Issue #1239)
- Re: [w3ctag/design-reviews] Other Spec Review: CRA web browser standard (Issue #1239)
- Re: [w3ctag/design-reviews] Other Spec Review: CRA web browser standard (Issue #1239)
- Re: [w3ctag/design-reviews] Other Spec Review: CRA web browser standard (Issue #1239)
[whatwg/dom] Remove "allow declarative shadow roots" (PR #1478)
- Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478)
- Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478)
- Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478)
- Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478)
- Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478)
- Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478)
- Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478)
[whatwg/url] Close more gaps between URL writing and parser sections (PR #924)
- Re: [whatwg/url] Close more gaps between URL writing and parser sections (PR #924)
- Re: [whatwg/url] Close more gaps between URL writing and parser sections (PR #924)
- Re: [whatwg/url] Close more gaps between URL writing and parser sections (PR #924)
[whatwg/url] Enumerate differences with URI & IRI in an appendix (PR #923)
- Re: [whatwg/url] Enumerate differences with URI & IRI in an appendix (PR #923)
- Re: [whatwg/url] Enumerate differences with URI & IRI in an appendix (PR #923)
- Re: [whatwg/url] Enumerate differences with URI & IRI in an appendix (PR #923)
- Re: [whatwg/url] Enumerate differences with URI & IRI in an appendix (PR #923)
Re: [w3ctag/design-reviews] Incubation: Prerendering cross-origin iframes (Issue #1207)
Re: [whatwg/url] It is unlikely that the spec's two definitions of valid URL strings are equal (Issue #704)
- Re: [whatwg/url] It is unlikely that the spec's two definitions of valid URL strings are equal (Issue #704)
- Re: [whatwg/url] It is unlikely that the spec's two definitions of valid URL strings are equal (Issue #704)
Re: [whatwg/fetch] Integrating the HTTP QUERY method (RFC 10008): method normalization, CORS, and caching (Issue #1938)
Re: [whatwg/url] RFC 4291 is not really sufficient to define "valid IPv6-address string" (Issue #916)
Re: [whatwg/url] What is an opaque path? (Issue #922)
- Re: [whatwg/url] What is an opaque path? (Issue #922)
- Re: [whatwg/url] What is an opaque path? (Issue #922)
- Re: [whatwg/url] What is an opaque path? (Issue #922)
Re: [whatwg/url] A branch of the "ends in a number checker" cannot be hit (Issue #865)
Re: [whatwg/url] Define valid IPv6-address string inline (PR #917)
- Re: [whatwg/url] Define valid IPv6-address string inline (PR #917)
- Re: [whatwg/url] Define valid IPv6-address string inline (PR #917)
Re: [whatwg/url] Valid domain needs to account for ending with a number (PR #918)
- Re: [whatwg/url] Valid domain needs to account for ending with a number (PR #918)
- Re: [whatwg/url] Valid domain needs to account for ending with a number (PR #918)
- Re: [whatwg/url] Valid domain needs to account for ending with a number (PR #918)