[whatwg/webidl] DOMException needs Exposed=* (Issue #1136)
Re: [whatwg/fetch] Should credentialed, same-site, cross-origin requests be easier to enable? (#1226)
[whatwg/webidl] Make it clearer that static and namespace attrs don't get to have state. Fixes #1133 (PR #1135)
[w3ctag/design-reviews] Review request for Fenced Frames (Issue #735)
[whatwg/webidl] Namespaces disallow ObservableArray attributes, but allow other interfaces (Issue #1134)
[whatwg/webidl] "attribute getter" steps skip security checks on namespaces (Issue #1133)
Re: [whatwg/webidl] ObservableArray types in namespace (#1000)
- Re: [whatwg/webidl] ObservableArray types in namespace (#1000)
- Re: [whatwg/webidl] ObservableArray types in namespace (#1000)
- Re: [whatwg/webidl] ObservableArray types in namespace (#1000)
- Re: [whatwg/webidl] ObservableArray types in namespace (#1000)
- Re: [whatwg/webidl] ObservableArray types in namespace (#1000)
- Re: [whatwg/webidl] ObservableArray types in namespace (#1000)
Re: [whatwg/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254)
- Re: [whatwg/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254)
- Re: [whatwg/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254)
[whatwg/url] Can a registrable domain or public suffix have a trailing dot? (Issue #693)
- Re: [whatwg/url] Can a registrable domain or public suffix have a trailing dot? (Issue #693)
- Re: [whatwg/url] Can a registrable domain or public suffix have a trailing dot? (Issue #693)
- Re: [whatwg/url] Can a registrable domain or public suffix have a trailing dot? (Issue #693)
- Re: [whatwg/url] Can a registrable domain or public suffix have a trailing dot? (Issue #693)
- Re: [whatwg/url] Can a registrable domain or public suffix have a trailing dot? (Issue #693)
[whatwg/url] PSL references broken (Issue #692)
[whatwg/fetch] Proposal: Expose `initiator` to JavaScript (Issue #1430)
Re: [whatwg/webidl] What is "type name" used for? (#835)
- Re: [whatwg/webidl] What is "type name" used for? (#835)
- Re: [whatwg/webidl] What is "type name" used for? (#835)
[whatwg/webidl] Remove the concept of 'type name'. Closes #835 (PR #1132)
- Re: [whatwg/webidl] Remove the concept of 'type name'. Closes #835 (PR #1132)
- Re: [whatwg/webidl] Remove the concept of 'type name'. Closes #835 (PR #1132)
Re: [whatwg/webidl] make hooking into maplike and setlike methods easier (#824)
Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { min }) (#1145)
- Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { min }) (#1145)
- Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { min }) (#1145)
Re: [WICG/webcomponents] Allowing CSS combinators postfixed to the ::slotted() or :host selectors (#889)
Re: [w3c/ServiceWorker] [Feature request] Expose parent client ID for iframe navigations (#1556)
Re: [whatwg/encoding] Expose APIs everywhere (f09648a)
Re: [w3c/ServiceWorker] Service Workers with Self Signed Certificates over SSL (#1514)
[w3ctag/design-reviews] Element.isVisible review (Issue #734)
[w3ctag/design-reviews] WIP: Web of Things (WoT) Discovery (Issue #733)
Re: [w3c/gamepad] gamepadconnected/disconnected events & non-"fully active" documents (#149)
Re: [w3ctag/design-reviews] WebGPU and WGSL (#626)
[w3c/touch-events] Change company for Patrick H. Lauke (PR #117)
Re: [w3c/ServiceWorker] Partition clients API by storage key. (#1606) (PR #1632)
[w3c/touch-events] Fix respec definition errors (PR #116)
Re: [w3c/touch-events] Clarify cancelability during scroll (#79)
Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91)
[w3c/touch-events] Use `data-export` attribute for exporting terms (PR #115)
- Re: [w3c/touch-events] Use `data-export` attribute for exporting terms (PR #115)
- Re: [w3c/touch-events] Use `data-export` attribute for exporting terms (PR #115)
- Re: [w3c/touch-events] Use `data-export` attribute for exporting terms (PR #115)
Re: [whatwg/fetch] Fetch body streams are not full duplex (#1254)
[w3ctag/design-reviews] Early design review: Focusgroup (Issue #732)
- Re: [w3ctag/design-reviews] Early design review: Focusgroup (Issue #732)
- Re: [w3ctag/design-reviews] Early design review: Focusgroup (Issue #732)
[whatwg/streams] Do the abort steps of ReadableStreamPipeTo really guarantee the abort callback to be called before cancel? (Issue #1229)
- Re: [whatwg/streams] Do the abort steps of ReadableStreamPipeTo really guarantee the abort callback to be called before cancel? (Issue #1229)
- Re: [whatwg/streams] Do the abort steps of ReadableStreamPipeTo really guarantee the abort callback to be called before cancel? (Issue #1229)
- Re: [whatwg/streams] Do the abort steps of ReadableStreamPipeTo really guarantee the abort callback to be called before cancel? (Issue #1229)
- Re: [whatwg/streams] Do the abort steps of ReadableStreamPipeTo really guarantee the abort callback to be called before cancel? (Issue #1229)
- Re: [whatwg/streams] Do the abort steps of ReadableStreamPipeTo really guarantee the abort callback to be called before cancel? (Issue #1229)
[whatwg/webidl] Remove obsolete "type name" concept (Issue #1131)
- Re: [whatwg/webidl] Remove obsolete "type name" concept (Issue #1131)
- Re: [whatwg/webidl] Remove obsolete "type name" concept (Issue #1131)
[whatwg/webidl] Export getter/setter steps, and note the tools you have access to when defining them. (PR #1130)
- Re: [whatwg/webidl] Export getter/setter steps, and note the tools you have access to when defining them. (PR #1130)
- Re: [whatwg/webidl] Export getter/setter steps, and note the tools you have access to when defining them. (PR #1130)
- Re: [whatwg/webidl] Export getter/setter steps, and note the tools you have access to when defining them. (PR #1130)
- Re: [whatwg/webidl] Export getter/setter steps, and note the tools you have access to when defining them. (PR #1130)
- Re: [whatwg/webidl] Export getter/setter steps, and note the tools you have access to when defining them. (PR #1130)
- Re: [whatwg/webidl] Export getter/setter steps, and note the tools you have access to when defining them. (PR #1130)
Re: [whatwg/fetch] How should the ReadableStream from response.body work when it's multipart? (#1021)
[whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
Re: [w3c/manifest] i18n: Multiple manifest links with different hreflang? (#892)
Re: [w3c/manifest] Add a manifest option for the declaration of the web application running pattern (Issue #1019)
[whatwg/streams] explain better what the pull method should do in the underlying source API (Issue #1228)
- Re: [whatwg/streams] explain better what the pull method should do in the underlying source API (Issue #1228)
- Re: [whatwg/streams] explain better what the pull method should do in the underlying source API (Issue #1228)
- Re: [whatwg/streams] explain better what the pull method should do in the underlying source API (Issue #1228)
- Re: [whatwg/streams] explain better what the pull method should do in the underlying source API (Issue #1228)
Re: [w3ctag/design-reviews] EditContext API (#416)
[whatwg/url] Add more examples of opaque hosts (PR #691)
- Re: [whatwg/url] Add more examples of opaque hosts (PR #691)
- Re: [whatwg/url] Add more examples of opaque hosts (PR #691)
- Re: [whatwg/url] Add more examples of opaque hosts (PR #691)
Re: [w3c/uievents] no way to distinguish printable key values from non-printable (#264)
[whatwg/dom] treejson.org/wg (Issue #1076)
Re: [whatwg/storage] Support obtaining a storage key from an environment (afbf6bd)
- Re: [whatwg/storage] Support obtaining a storage key from an environment (afbf6bd)
- Re: [whatwg/storage] Support obtaining a storage key from an environment (afbf6bd)
- Re: [whatwg/storage] Support obtaining a storage key from an environment (afbf6bd)
Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
[whatwg/encoding] Static methods for TextEncoder and TextDecoder (PR #284)
Re: [w3ctag/design-reviews] Early design review: Subresource loading with Web Bundles (#616)
[w3ctag/design-reviews] Review request for CSS Variables (Issue #731)
- Re: [w3ctag/design-reviews] Review request for CSS Variables (Issue #731)
- Re: [w3ctag/design-reviews] Review request for CSS Variables (Issue #731)
Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
- Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
- Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
- Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
- Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
- Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
- Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098)
Re: [w3c/ServiceWorker] A WindowClient close or terminate method perhaps? (#1567)
[whatwg/fetch] Rgegeh (Issue #1427)
[whatwg/dom] Unspecified behavior when NodeFilter#acceptNode returns null (Issue #1075)
- Re: [whatwg/dom] Unspecified behavior when NodeFilter#acceptNode returns null (Issue #1075)
- Re: [whatwg/dom] Unspecified behavior when NodeFilter#acceptNode returns null (Issue #1075)
- Re: [whatwg/dom] Unspecified behavior when NodeFilter#acceptNode returns null (Issue #1075)
- Re: [whatwg/dom] Unspecified behavior when NodeFilter#acceptNode returns null (Issue #1075)
- Re: [whatwg/dom] Unspecified behavior when NodeFilter#acceptNode returns null (Issue #1075)
- Re: [whatwg/dom] Unspecified behavior when NodeFilter#acceptNode returns null (Issue #1075)
- Re: [whatwg/dom] Unspecified behavior when NodeFilter#acceptNode returns null (Issue #1075)
- Re: [whatwg/dom] Unspecified behavior when NodeFilter#acceptNode returns null (Issue #1075)
Re: [whatwg/fetch] Perform TAO check for nested navigations (PR #1422)
- Re: [whatwg/fetch] Perform TAO check for nested navigations (PR #1422)
- Re: [whatwg/fetch] Perform TAO check for nested navigations (PR #1422)
- Re: [whatwg/fetch] Perform TAO check for nested navigations (PR #1422)
- Re: [whatwg/fetch] Perform TAO check for nested navigations (PR #1422)
- Re: [whatwg/fetch] Perform TAO check for nested navigations (PR #1422)
- Re: [whatwg/fetch] Perform TAO check for nested navigations (PR #1422)
- Re: [whatwg/fetch] Perform TAO check for nested navigations (PR #1422)
- Re: [whatwg/fetch] Perform TAO check for nested navigations (PR #1422)
Re: [w3c/pointerlock] feature request : Allow to set pointer position upon release (#61)
Re: [w3c/editing] Each specification in its own repository (Issue #374)
Re: [w3ctag/design-reviews] AbortSignal.timeout() (Issue #711)
[w3c/editing] Recognize Edit-context new repo and issues (PR #398)
- Re: [w3c/editing] Recognize Edit-context new repo and issues (PR #398)
- Re: [w3c/editing] Recognize Edit-context new repo and issues (PR #398)
Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920)
- Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920)
- Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920)
[whatwg/url] Opaque hosts: realistic examples and origins? (Issue #690)
- Re: [whatwg/url] Opaque hosts: realistic examples and origins? (Issue #690)
- Re: [whatwg/url] Opaque hosts: realistic examples and origins? (Issue #690)
- Re: [whatwg/url] Opaque hosts: realistic examples and origins? (Issue #690)
- Re: [whatwg/url] Opaque hosts: realistic examples and origins? (Issue #690)
- Re: [whatwg/url] Opaque hosts: realistic examples and origins? (Issue #690)
- Re: [whatwg/url] Opaque hosts: realistic examples and origins? (Issue #690)
- Re: [whatwg/url] Opaque hosts: realistic examples and origins? (Issue #690)
- Re: [whatwg/url] Opaque hosts: realistic examples and origins? (Issue #690)
- Re: [whatwg/url] Opaque hosts: realistic examples and origins? (Issue #690)
Re: [w3c/manifest] Add a "tabbed application" mode (#737)
- Re: [w3c/manifest] Add a "tabbed application" mode (#737)
- Re: [w3c/manifest] Add a "tabbed application" mode (#737)
[whatwg/webidl] Export observable array attribute/backing list (PR #1124)
- Re: [whatwg/webidl] Export observable array attribute/backing list (PR #1124)
- Re: [whatwg/webidl] Export observable array attribute/backing list (PR #1124)
Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1315)
[whatwg/fetch] Define HSTS as "internal" redirect (Issue #1426)
[w3c/manifest] Add a manifest option for the declaration the "version" of the web application (Issue #1036)
- Re: [w3c/manifest] Add a manifest option for the declaration the "version" of the web application (Issue #1036)
- Re: [w3c/manifest] Add a manifest option for the declaration the "version" of the web application (Issue #1036)
- Re: [w3c/manifest] Add a manifest option for the declaration the "version" of the web application (Issue #1036)
- Re: [w3c/manifest] Add a manifest option for the declaration the "version" of the web application (Issue #1036)
- Re: [w3c/manifest] Add a manifest option for the declaration the "version" of the web application (Issue #1036)
- Re: [w3c/manifest] Add a manifest option for the declaration the "version" of the web application (Issue #1036)
- Re: [w3c/manifest] Add a manifest option for the declaration the "version" of the web application (Issue #1036)
Re: [w3ctag/design-reviews] FYI - MediaCapabilities API for WebRTC (Issue #720)
Re: [w3ctag/design-reviews] Web of Things (WoT) Thing Description 1.1: TAG and Security Review (Issue #715)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Thing Description 1.1: TAG and Security Review (Issue #715)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Thing Description 1.1: TAG and Security Review (Issue #715)
[whatwg/fetch] the body.getReader() size/length (Issue #1425)
- Re: [whatwg/fetch] the body.getReader() size/length (Issue #1425)
- Re: [whatwg/fetch] the body.getReader() size/length (Issue #1425)
Re: [w3ctag/design-reviews] Early design review for Range API improvements (Issue #725)
Re: [w3ctag/design-reviews] Review request for TURTLEDOVE (Issue #723)
Re: [whatwg/streams] Specify realm for object creation (Issue #1213)
Re: [w3ctag/design-reviews] File Handling (#371)
Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
- Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891)
Re: [WICG/webcomponents] Upstreaming Shadow DOM and outstanding v1 work (#661)
Re: [WICG/webcomponents] Allow customizing base URL of a shadow root (#581)
Re: [WICG/webcomponents] update repo type (PR #949)
[whatwg/fetch] Export main fetch (PR #1424)
- Re: [whatwg/fetch] Export main fetch (PR #1424)
- Re: [whatwg/fetch] Export main fetch (PR #1424)
- Re: [whatwg/fetch] Export main fetch (PR #1424)
[w3ctag/design-reviews] Early design review: CSS Toggles (Issue #730)
Re: [w3c/gamepad] Xbox One impulse trigger effects (#138)
Re: [w3ctag/design-reviews] FYI Review of CSS Fonts 4 `font-palette`and `@font-palette-values` (Issue #719)
- Re: [w3ctag/design-reviews] FYI Review of CSS Fonts 4 `font-palette`and `@font-palette-values` (Issue #719)
- Re: [w3ctag/design-reviews] FYI Review of CSS Fonts 4 `font-palette`and `@font-palette-values` (Issue #719)
- Re: [w3ctag/design-reviews] FYI Review of CSS Fonts 4 `font-palette`and `@font-palette-values` (Issue #719)
- Re: [w3ctag/design-reviews] FYI Review of CSS Fonts 4 `font-palette`and `@font-palette-values` (Issue #719)
- Re: [w3ctag/design-reviews] FYI Review of CSS Fonts 4 `font-palette`and `@font-palette-values` (Issue #719)
Re: [w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170)
[w3c/editing] Add editing minutes 2022-04-14 (PR #397)
- Re: [w3c/editing] Add editing minutes 2022-04-14 (PR #397)
- Re: [w3c/editing] Add editing minutes 2022-04-14 (PR #397)
[w3c/editing] Interop 2022 and `execCommand` (Issue #396)
- Re: [w3c/editing] Interop 2022 and `execCommand` (Issue #396)
- Re: [w3c/editing] Interop 2022 and `execCommand` (Issue #396)
- Re: [w3c/editing] Interop 2022 and `execCommand` (Issue #396)
- Re: [w3c/editing] Interop 2022 and `execCommand` (Issue #396)
Re: [w3c/editing] clarifications for the pickling design proposal (Issue #393)
- Re: [w3c/editing] clarifications for the pickling design proposal (Issue #393)
- Re: [w3c/editing] clarifications for the pickling design proposal (Issue #393)
- Re: [w3c/editing] clarifications for the pickling design proposal (Issue #393)
Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359)
Re: [w3ctag/design-reviews] Font Table Access API (#400)
Re: [w3c/touch-events] Consider defaulting to use passive listener on window/document/document.body (#74)
Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365)
[whatwg/dom] Tanayout Chanmee (Issue #1074)
[w3c/touch-events] Switch to the right profile of ReSpec (PR #114)
- Re: [w3c/touch-events] Switch to the right profile of ReSpec (PR #114)
- Re: [w3c/touch-events] Switch to the right profile of ReSpec (PR #114)
- Re: [w3c/touch-events] Switch to the right profile of ReSpec (PR #114)
Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718)
Re: [w3ctag/design-reviews] Navigation API (formerly app history API) (Issue #717)
Re: [whatwg/webidl] ExtendedAttributeList can match unbalanced ( ), [ ], and { } (Issue #1100)
Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { atLeast }) (#1145)
- Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { atLeast }) (#1145)
- Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { atLeast }) (#1145)
- Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { atLeast }) (#1145)
Re: [whatwg/dom] Editorial: correct extracting reference (0bf93ba)
[whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
- Re: [whatwg/streams] Remove ReadableStreamBYOBReadResult (PR #1227)
[w3c/touch-events] Export 'expose legacy touch event APIs' (PR #113)
- Re: [w3c/touch-events] Export 'expose legacy touch event APIs' (PR #113)
- Re: [w3c/touch-events] Export 'expose legacy touch event APIs' (PR #113)
Re: [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094)
Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714)
Re: [w3c/ServiceWorker] How should import() work in service workers? (#1585)
Re: [w3c/editing] Update meeting invite link (PR #391)
Re: [w3c/editing] Add 3/10/22 minutes (PR #395)
[w3c/ServiceWorker] [question]: how do CacheStorage save encoded responses? (Issue #1641)
- Re: [w3c/ServiceWorker] [question]: how do CacheStorage save encoded responses? (Issue #1641)
- Re: [w3c/ServiceWorker] [question]: how do CacheStorage save encoded responses? (Issue #1641)
- Re: [w3c/ServiceWorker] [question]: how do CacheStorage save encoded responses? (Issue #1641)
- Re: [w3c/ServiceWorker] [question]: how do CacheStorage save encoded responses? (Issue #1641)
- Re: [w3c/ServiceWorker] [question]: how do CacheStorage save encoded responses? (Issue #1641)
- Re: [w3c/ServiceWorker] [question]: how do CacheStorage save encoded responses? (Issue #1641)
- Re: [w3c/ServiceWorker] [question]: how do CacheStorage save encoded responses? (Issue #1641)
- Re: [w3c/ServiceWorker] [question]: how do CacheStorage save encoded responses? (Issue #1641)
- Re: [w3c/ServiceWorker] [question]: how do CacheStorage save encoded responses? (Issue #1641)
[whatwg/dom] `event.target` not cleared if event is not fired on `ShadowRoot` (Issue #1072)
Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
Re: [whatwg/url] Support IPv6 zone identifiers (#392)
Re: [w3c/gamepad] Please don't restrict to a secure context (#145)
Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
[w3c/permissions] Gaps in the current permissions model (Issue #377)
Re: [w3c/permissions] previousResult not really stored anywhere (#234)
- Re: [w3c/permissions] previousResult not really stored anywhere (#234)
- Re: [w3c/permissions] previousResult not really stored anywhere (#234)
- Re: [w3c/permissions] previousResult not really stored anywhere (#234)
Re: [w3c/permissions] Add "popups" permission type (#210)
[w3c/permissions] Allow "prompt the user to choose" apply to one or more options. (PR #376)
[w3c/touch-events] Fix typos, add Simon Pieters to acks, update list of changes (PR #112)
- Re: [w3c/touch-events] Fix typos, add Simon Pieters to acks, update list of changes (PR #112)
- Re: [w3c/touch-events] Fix typos, add Simon Pieters to acks, update list of changes (PR #112)
- Re: [w3c/touch-events] Fix typos, add Simon Pieters to acks, update list of changes (PR #112)
- Re: [w3c/touch-events] Fix typos, add Simon Pieters to acks, update list of changes (PR #112)
Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135)
- Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135)
- Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135)
[whatwg/dom] Maybe throw NotSupportedError for createEvent('touchevent') (PR #1071)
- Re: [whatwg/dom] Maybe throw NotSupportedError for createEvent('touchevent') (PR #1071)
- Re: [whatwg/dom] Maybe throw NotSupportedError for createEvent('touchevent') (PR #1071)
- Re: [whatwg/dom] Maybe throw NotSupportedError for createEvent('touchevent') (PR #1071)
- Re: [whatwg/dom] Maybe throw NotSupportedError for createEvent('touchevent') (PR #1071)
- Re: [whatwg/dom] Maybe throw NotSupportedError for createEvent('touchevent') (PR #1071)
- Re: [whatwg/dom] Maybe throw NotSupportedError for createEvent('touchevent') (PR #1071)
- Re: [whatwg/dom] Maybe throw NotSupportedError for createEvent('touchevent') (PR #1071)
[w3c/touch-events] Conditionally expose legacy touch event APIs (PR #111)
- Re: [w3c/touch-events] Conditionally expose legacy touch event APIs (PR #111)
- Re: [w3c/touch-events] Conditionally expose legacy touch event APIs (PR #111)
- Re: [w3c/touch-events] Conditionally expose legacy touch event APIs (PR #111)
Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64)
- Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64)
- Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64)
Re: [w3ctag/design-reviews] Markup based Client Hints delegation for third-party content (Issue #702)
Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
- Re: [whatwg/fetch] Process subresource link headers (PR #1409)
Re: [w3c/manifest] Shortcut_items uses manifest_url when it should use start_url (#1003)
Re: [w3c/manifest] Clarify shortcut_items should be within scope of scope (PR #1033)
Re: [WICG/webcomponents] Proposal: Allow custom elements to be in any namespace (#634)
[w3c/ServiceWorker] Fixing some spec linking issues (PR #1640)
- Re: [w3c/ServiceWorker] Fixing some spec linking issues (PR #1640)
- Re: [w3c/ServiceWorker] Fixing some spec linking issues (PR #1640)
[w3ctag/design-reviews] Cookie Expires/Max-Age attribute upper limit (Issue #729)
- Re: [w3ctag/design-reviews] Cookie Expires/Max-Age attribute upper limit (Issue #729)
- Re: [w3ctag/design-reviews] Cookie Expires/Max-Age attribute upper limit (Issue #729)
Re: [w3ctag/design-reviews] Require markdown for explainers, and some more (#381)
[w3ctag/design-reviews] Account Ownership Marques Ware (Issue #728)
Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849)
- Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849)
- Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849)
- Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849)
- Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849)
Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
- Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)
Re: [whatwg/fetch] Specify connection timing for HTTP/3 (PR #1417)
- Re: [whatwg/fetch] Specify connection timing for HTTP/3 (PR #1417)
- Re: [whatwg/fetch] Specify connection timing for HTTP/3 (PR #1417)
- Re: [whatwg/fetch] Specify connection timing for HTTP/3 (PR #1417)
- Re: [whatwg/fetch] Specify connection timing for HTTP/3 (PR #1417)
- Re: [whatwg/fetch] Specify connection timing for HTTP/3 (PR #1417)
- Re: [whatwg/fetch] Specify connection timing for HTTP/3 (PR #1417)
- Re: [whatwg/fetch] Specify connection timing for HTTP/3 (PR #1417)
[w3ctag/design-reviews] Review request on `blocking=render` attribute for scripts, stylesheets and link resources (Issue #727)
- Re: [w3ctag/design-reviews] Review request on `blocking=render` attribute for scripts, stylesheets and link resources (Issue #727)
- Re: [w3ctag/design-reviews] Review request on `blocking=render` attribute for scripts, stylesheets and link resources (Issue #727)
- Re: [w3ctag/design-reviews] Review request on `blocking=render` attribute for scripts, stylesheets and link resources (Issue #727)
- Re: [w3ctag/design-reviews] Review request on `blocking=render` attribute for scripts, stylesheets and link resources (Issue #727)
- Re: [w3ctag/design-reviews] Review request on `blocking=render` attribute for scripts, stylesheets and link resources (Issue #727)
- Re: [w3ctag/design-reviews] Review request on `blocking=render` attribute for scripts, stylesheets and link resources (Issue #727)
Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
- Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
- Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
- Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
- Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
- Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
- Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
- Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
- Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)
[whatwg/fetch] Editorial: Rename 'fetch finale' to 'fetch response handover' (PR #1423)
- Re: [whatwg/fetch] Editorial: Rename 'fetch finale' to 'fetch response handover' (PR #1423)
- Re: [whatwg/fetch] Editorial: Rename 'fetch finale' to 'fetch response handover' (PR #1423)
Re: [whatwg/fetch] Editorial suggestion: rename "fetch finale" (Issue #1419)
- Re: [whatwg/fetch] Editorial suggestion: rename "fetch finale" (Issue #1419)
- Re: [whatwg/fetch] Editorial suggestion: rename "fetch finale" (Issue #1419)
Re: [whatwg/fetch] Perform TAO check when reporting, using global's origin (PR #1422)
- Re: [whatwg/fetch] Perform TAO check when reporting, using global's origin (PR #1422)
- Re: [whatwg/fetch] Perform TAO check when reporting, using global's origin (PR #1422)
- Re: [whatwg/fetch] Perform TAO check when reporting, using global's origin (PR #1422)
- Re: [whatwg/fetch] Perform TAO check when reporting, using global's origin (PR #1422)
- Re: [whatwg/fetch] Perform TAO check when reporting, using global's origin (PR #1422)
- Re: [whatwg/fetch] Perform TAO check when reporting, using global's origin (PR #1422)
- Re: [whatwg/fetch] Perform TAO check when reporting, using global's origin (PR #1422)
- Re: [whatwg/fetch] Perform TAO check when reporting, using global's origin (PR #1422)
- Re: [whatwg/fetch] Perform TAO check when reporting, using global's origin (PR #1422)
Re: [whatwg/fetch] Editorial: using serialized origin in TAO check and "null" (Issue #1421)
- Re: [whatwg/fetch] Editorial: using serialized origin in TAO check and "null" (Issue #1421)
- Re: [whatwg/fetch] Editorial: using serialized origin in TAO check and "null" (Issue #1421)
- Re: [whatwg/fetch] Editorial: using serialized origin in TAO check and "null" (Issue #1421)
- Re: [whatwg/fetch] Editorial: using serialized origin in TAO check and "null" (Issue #1421)
Re: [w3ctag/design-reviews] EPUB 3.3 (Issue #684)
- Re: [w3ctag/design-reviews] EPUB 3.3 (Issue #684)
- Re: [w3ctag/design-reviews] EPUB 3.3 (Issue #684)
- Re: [w3ctag/design-reviews] EPUB 3.3 (Issue #684)
- Re: [w3ctag/design-reviews] EPUB 3.3 (Issue #684)
Re: [w3ctag/design-reviews] Web App Launch Handler (Issue #683)
Re: [w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682)
Re: [w3ctag/design-reviews] Conditional Focus (When Display-Capture Starts) (#679)
Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523)
- Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523)
- Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523)
- Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523)
Re: [w3ctag/design-reviews] Direct Sockets API (#548)
Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688)
Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696)
Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
- Re: [whatwg/fetch] Move `finalize and report timing` to controller (PR #1413)
Re: [w3ctag/design-reviews] Same-origin prerendering triggered by speculationrules (#667)
Re: [w3ctag/design-reviews] Digital Goods API (#571)
- Re: [w3ctag/design-reviews] Digital Goods API (#571)
- Re: [w3ctag/design-reviews] Digital Goods API (#571)
- Re: [w3ctag/design-reviews] Digital Goods API (#571)
Re: [whatwg/dom] Add declarative Shadow DOM features (#892)
- Re: [whatwg/dom] Add declarative Shadow DOM features (#892)
- Re: [whatwg/dom] Add declarative Shadow DOM features (#892)
Re: [whatwg/fetch] Range header 'helper' produces incorrect header value (#1265)
[whatwg/dom] Add EventListener Sub Flags [Suggestion] [Feature Request] (Issue #1070)
Re: [WICG/webcomponents] How can a custom element detect when it is distributed, and what its composed parent is? (#941)
[whatwg/storage] Wouldn't the origin extracted from the creation URL be wrong in for example sandboxed iframes, as well as in some other opaque origin situations (i.e. a dedicated worker created by a sandboxed iframe should have the same opaque origin as its creator, for BroadcastChannel to work between them). (Issue #141)
Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156)
[w3c/clipboard-apis] Replacing no-break spaces when converting HTML to plain text upon clipboard export (Issue #173)
Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
- Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)
Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412)
- Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412)
- Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412)
- Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412)
- Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412)
- Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412)
- Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412)
- Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412)
Re: [whatwg/streams] Editorial: update use of, or stop using, completion values? (Issue #1224)
Re: [w3c/clipboard-apis] Don't recommend user gesture in clipboard API (#75)
- Re: [w3c/clipboard-apis] Don't recommend user gesture in clipboard API (#75)
- Re: [w3c/clipboard-apis] Don't recommend user gesture in clipboard API (#75)
- Re: [w3c/clipboard-apis] Don't recommend user gesture in clipboard API (#75)
- Re: [w3c/clipboard-apis] Don't recommend user gesture in clipboard API (#75)
- Re: [w3c/clipboard-apis] Don't recommend user gesture in clipboard API (#75)
Re: [whatwg/url] Expose a URLHost class to JavaScript (#288)
Re: [WICG/webcomponents] CSS selector to style slots with slotted elements (#936)
- Re: [WICG/webcomponents] CSS selector to style slots with slotted elements (#936)
- Re: [WICG/webcomponents] CSS selector to style slots with slotted elements (#936)
- Re: [WICG/webcomponents] CSS selector to style slots with slotted elements (#936)
- Re: [WICG/webcomponents] CSS selector to style slots with slotted elements (#936)
Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)