Re: [whatwg/streams] Handling stream errors in a TransformStream transformer (Issue #1212)
[w3ctag/design-reviews] Intersection Observer Scroll Margin (Issue #905)
[whatwg/fetch] "should X be blocked" is a bad pattern (Issue #1714)
[whatwg/webidl] Add support for AsyncContext (PR #1369)
- Re: [whatwg/webidl] Add support for AsyncContext (PR #1369)
- Re: [whatwg/webidl] Add support for AsyncContext (PR #1369)
Re: [w3c/uievents] Specification Should Link to Its Own Definition of “Cancelable” (#165)
[whatwg/fetch] Verify request's window usage for preloads (Issue #1713)
[whatwg/fetch] Correct request's window check (PR #1712)
- Re: [whatwg/fetch] Correct request's window check (PR #1712)
- Re: [whatwg/fetch] Correct request's window check (PR #1712)
[whatwg/fetch] 301/302/303 Redirect does not preserve headers (Issue #1711)
- Re: [whatwg/fetch] 301/302/303 Redirect does not preserve headers (Issue #1711)
- Re: [whatwg/fetch] 301/302/303 Redirect does not preserve headers (Issue #1711)
- Re: [whatwg/fetch] 301/302/303 Redirect does not preserve headers (Issue #1711)
- Re: [whatwg/fetch] 301/302/303 Redirect does not preserve headers (Issue #1711)
- Re: [whatwg/fetch] 301/302/303 Redirect does not preserve headers (Issue #1711)
Re: [w3ctag/design-reviews] Exclusive accordion (<details name="">) (Issue #866)
Re: [w3ctag/design-reviews] Cross-document View Transitions API (Issue #851)
Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
[w3ctag/design-reviews] Standardizing Security Semantics of Cross-Site Cookies (Issue #904)
[whatwg/fetch] For which 1xx responses should Set-Cookie work? (Issue #1710)
[whatwg/xhr] Meta: update repository files (PR #383)
[whatwg/webidl] Meta: update repository files (PR #1368)
- Re: [whatwg/webidl] Meta: update repository files (PR #1368)
- Re: [whatwg/webidl] Meta: update repository files (PR #1368)
[whatwg/streams] Meta: update repository files (PR #1295)
- Re: [whatwg/streams] Meta: update repository files (PR #1295)
- Re: [whatwg/streams] Meta: update repository files (PR #1295)
[whatwg/storage] Meta: update repository files (PR #168)
[whatwg/fetch] Meta: update repository files (PR #1709)
[whatwg/fullscreen] Meta: update repository files (PR #230)
[whatwg/encoding] Meta: update repository files (PR #320)
[whatwg/url] Meta: update repository files (PR #795)
[whatwg/dom] Meta: update repository files (PR #1229)
[whatwg/fetch] Meta: update repository files (PR #1708)
- Re: [whatwg/fetch] Meta: update repository files (PR #1708)
- Re: [whatwg/fetch] Meta: update repository files (PR #1708)
[whatwg/fullscreen] Meta: update repository files (PR #229)
- Re: [whatwg/fullscreen] Meta: update repository files (PR #229)
- Re: [whatwg/fullscreen] Meta: update repository files (PR #229)
- Re: [whatwg/fullscreen] Meta: update repository files (PR #229)
[whatwg/dom] Meta: update repository files (PR #1228)
[whatwg/encoding] Meta: update repository files (PR #319)
- Re: [whatwg/encoding] Meta: update repository files (PR #319)
- Re: [whatwg/encoding] Meta: update repository files (PR #319)
[whatwg/url] Meta: update repository files (PR #794)
- Re: [whatwg/url] Meta: update repository files (PR #794)
- Re: [whatwg/url] Meta: update repository files (PR #794)
[whatwg/dom] MutationOvserver and DOMNodeInsertedIntoDocument (Issue #1227)
Re: [whatwg/dom] Stop exporting AbortSignal's signal abort (Issue #1194)
[w3c/push-api] Fix #361. Improving the readability (PR #363)
[whatwg/webidl] Intent to use Constants (Issue #1367)
[whatwg/fetch] [Cookie Layering] WIP Requests (PR #1707)
[whatwg/webidl] jbylc888.com (Issue #1366)
[whatwg/fetch] Tighten `application/x-www-form-urlencoded` CORS safe-list carveout? (Issue #1706)
- Re: [whatwg/fetch] Tighten `application/x-www-form-urlencoded` CORS safe-list carveout? (Issue #1706)
- Re: [whatwg/fetch] Tighten `application/x-www-form-urlencoded` CORS safe-list carveout? (Issue #1706)
[whatwg/dom] Stop exporting AbortSignal's signal abort (PR #1226)
- Re: [whatwg/dom] Stop exporting AbortSignal's signal abort (PR #1226)
- Re: [whatwg/dom] Stop exporting AbortSignal's signal abort (PR #1226)
[whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
- Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)
Re: [whatwg/fetch] More informative error types (#526)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533)
- Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533)
- Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533)
- Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533)
Re: [whatwg/webidl] Fix `indent_size` in `.editorconfig` for Bikeshes files (#1040)
[w3c/push-api] Adds Safari Implementation (Issue #362)
[whatwg/url] Fix validation error when a URL has credentials but no host (PR #793)
- Re: [whatwg/url] Fix validation error when a URL has credentials but no host (PR #793)
- Re: [whatwg/url] Fix validation error when a URL has credentials but no host (PR #793)
- Re: [whatwg/url] Fix validation error when a URL has credentials but no host (PR #793)
- Re: [whatwg/url] Fix validation error when a URL has credentials but no host (PR #793)
- Re: [whatwg/url] Fix validation error when a URL has credentials but no host (PR #793)
- Re: [whatwg/url] Fix validation error when a URL has credentials but no host (PR #793)
- Re: [whatwg/url] Fix validation error when a URL has credentials but no host (PR #793)
- Re: [whatwg/url] Fix validation error when a URL has credentials but no host (PR #793)
- Re: [whatwg/url] Fix validation error when a URL has credentials but no host (PR #793)
[w3c/push-api] Permission Revocation - English language clarification (Issue #361)
Re: [w3c/push-api] pushregistrationlost isn't documented (#149)
[w3ctag/design-reviews] Side Panel (Issue #903)
Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723)
Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
Re: [w3ctag/design-reviews] Tag review for Compression Dictionary Transport (Issue #877)
- Re: [w3ctag/design-reviews] Tag review for Compression Dictionary Transport (Issue #877)
- Re: [w3ctag/design-reviews] Tag review for Compression Dictionary Transport (Issue #877)
- Re: [w3ctag/design-reviews] Tag review for Compression Dictionary Transport (Issue #877)
[whatwg/url] Consider defining "URL path" as a concept (Issue #792)
[whatwg/url] Editorial: remove duplicate "is" (PR #791)
Re: [whatwg/fetch] Access-Control-Max-Age not effective in preflight request caching when Authorization header is programatically defined (#1278)
Re: [w3c/manifest] JSON "commonly" encoded in Unicode (Issue #1089)
Re: [w3c/manifest] Call of topics for TPAC (Issue #1093)
[w3c/manifest] Editorial: remove “commonly” to reflect actual JSON encoding (PR #1100)
[w3c/manifest] Consistent manifest naming (PR #1099)
[whatwg/url] Minor typo (Issue #790)
[whatwg/fetch] fetct commit (Issue #1704)
[w3c/manifest] Editorial: Remove “at risk” warning for monochrome (PR #1098)
[whatwg/fetch] https://fetch.spec.whatwg.org/commit-snapshots/9ca4bda8f67d80b5bd7061be6468c45ccb34d3c7/ (Issue #1703)
[whatwg/fetch] aa (Issue #1702)
Re: [whatwg/webidl] Review Draft Publication: September 2023 (644dd7d)
[w3ctag/design-reviews] Observable API design review (Issue #902)
[w3c/editing] Outdent immediately after indent should restore pre-indent DOM (like popular editors do) (Issue #443)
[w3c/editing] Outdent behavior with respect to list items is not aligned with popular editors (Issue #442)
Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465)
Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989)
[w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901)
Re: [whatwg/streams] ReadableStream.prototype.arrayBuffer() (#1019)
Re: [w3ctag/design-reviews] VC-JWT (Issue #857)
[w3ctag/design-reviews] HTMLSelectElement showPicker() (Issue #900)
- Re: [w3ctag/design-reviews] HTMLSelectElement showPicker() (Issue #900)
- Re: [w3ctag/design-reviews] HTMLSelectElement showPicker() (Issue #900)
- Re: [w3ctag/design-reviews] HTMLSelectElement showPicker() (Issue #900)
[whatwg/url] Editorial: rename host parser's isNotSpecial to isOpaque (PR #789)
- Re: [whatwg/url] Editorial: rename host parser's isNotSpecial to isOpaque (PR #789)
- Re: [whatwg/url] Editorial: rename host parser's isNotSpecial to isOpaque (PR #789)
- Re: [whatwg/url] Editorial: rename host parser's isNotSpecial to isOpaque (PR #789)
- Re: [whatwg/url] Editorial: rename host parser's isNotSpecial to isOpaque (PR #789)
Re: [WICG/webcomponents] SVG <use> tag with CSS ::part selector (Issue #955)
[whatwg/fetch] XCTO affects more than script-like and "style" (Issue #1701)
[whatwg/fetch] Clarify relation to HTTP RFCs and similar (Issue #1700)
Re: [whatwg/fetch] Recommend that servers follow the steps of CORS preflight for easier troubleshooting (Issue #1588)
- Re: [whatwg/fetch] Recommend that servers follow the steps of CORS preflight for easier troubleshooting (Issue #1588)
- Re: [whatwg/fetch] Recommend that servers follow the steps of CORS preflight for easier troubleshooting (Issue #1588)
- Re: [whatwg/fetch] Recommend that servers follow the steps of CORS preflight for easier troubleshooting (Issue #1588)
- Re: [whatwg/fetch] Recommend that servers follow the steps of CORS preflight for easier troubleshooting (Issue #1588)
[w3ctag/design-reviews] Securing Verifiable Credentials using JOSE and COSE (Issue #899)
[whatwg/webidl] Named properties object [[GetOwnProperty]] conflicts with class string (Issue #1365)
- Re: [whatwg/webidl] Named properties object [[GetOwnProperty]] conflicts with class string (Issue #1365)
- Re: [whatwg/webidl] Named properties object [[GetOwnProperty]] conflicts with class string (Issue #1365)
[w3c/permissions] PermissionStatus update steps touch DOM objects in parallel (Issue #421)
- Re: [w3c/permissions] PermissionStatus update steps touch DOM objects in parallel (Issue #421)
- Re: [w3c/permissions] PermissionStatus update steps touch DOM objects in parallel (Issue #421)
Re: [whatwg/dom] Add EventListener Sub Flags [Suggestion] [Feature Request] (Issue #1070)
Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
- Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
- Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
- Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
- Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
- Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
- Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
- Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
Re: [w3ctag/design-reviews] HTML Modules (#334)
[w3c/ServiceWorker] Editorial: remove API URL character encoding (PR #1693)
- Re: [w3c/ServiceWorker] Editorial: remove API URL character encoding (PR #1693)
- Re: [w3c/ServiceWorker] Editorial: remove API URL character encoding (PR #1693)
- Re: [w3c/ServiceWorker] Editorial: remove API URL character encoding (PR #1693)
Re: [w3ctag/design-reviews] Web Authentication: Large Blob extension (Issue #820)
[whatwg/xhr] Editorial: use HTML's encoding-parse a URL (PR #382)
- Re: [whatwg/xhr] Editorial: use HTML's encoding-parse a URL (PR #382)
- Re: [whatwg/xhr] Editorial: use HTML's encoding-parse a URL (PR #382)
- Re: [whatwg/xhr] Editorial: use HTML's encoding-parse a URL (PR #382)
- Re: [whatwg/xhr] Editorial: use HTML's encoding-parse a URL (PR #382)
Re: [w3c/ServiceWorker] [Feature request] Allow keeping service worker alive (#1558)
[w3c/clipboard-apis] Scope events to GlobalEventHandlers (PR #196)
- Re: [w3c/clipboard-apis] Scope events to GlobalEventHandlers (PR #196)
- Re: [w3c/clipboard-apis] Scope events to GlobalEventHandlers (PR #196)
Re: [whatwg/fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179)
[w3c/clipboard-apis] Add 'starts with' to web custom format prefix. (PR #195)
[w3c/clipboard-apis] Update custom types on Mac. (PR #194)
- Re: [w3c/clipboard-apis] Update custom types on Mac. (PR #194)
- Re: [w3c/clipboard-apis] Update custom types on Mac. (PR #194)
- Re: [w3c/clipboard-apis] Update custom types on Mac. (PR #194)
[whatwg/streams] Should `ReadableStreamClose(stream)` also close pending read requests in case of ReadableStreamBYOBReader (Issue #1294)
- Re: [whatwg/streams] Should `ReadableStreamClose(stream)` also close pending read requests in case of ReadableStreamBYOBReader (Issue #1294)
- Re: [whatwg/streams] Should `ReadableStreamClose(stream)` also close pending read requests in case of ReadableStreamBYOBReader (Issue #1294)
- Re: [whatwg/streams] Should `ReadableStreamClose(stream)` also close pending read requests in case of ReadableStreamBYOBReader (Issue #1294)
Re: [w3c/clipboard-apis] Add Web Custom format (PR #175)
- Re: [w3c/clipboard-apis] Add Web Custom format (PR #175)
- Re: [w3c/clipboard-apis] Add Web Custom format (PR #175)
- Re: [w3c/clipboard-apis] Add Web Custom format (PR #175)
- Re: [w3c/clipboard-apis] Add Web Custom format (PR #175)
- Re: [w3c/clipboard-apis] Add Web Custom format (PR #175)
- Re: [w3c/clipboard-apis] Add Web Custom format (PR #175)
- Re: [w3c/clipboard-apis] Add Web Custom format (PR #175)
- Re: [w3c/clipboard-apis] Add Web Custom format (PR #175)
- Re: [w3c/clipboard-apis] Add Web Custom format (PR #175)
[whatwg/encoding] Video Mehmet (Issue #318)
[w3c/clipboard-apis] Start and End fragment tags in text/html format on Windows (Issue #193)
[WICG/webcomponents] Update DOM-Parts (Imperative) to clarify definitions and use cases (PR #1032)
Re: [w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170)
- Re: [w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170)
- Re: [w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170)
Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
[whatwg/url] , (Issue #788)
[whatwg/webidl] Review Draft Publication: September 2023 (PR #1364)
[whatwg/webidl] M Ehsan Hashmi Forsage Eagle Team Admin (Issue #1363)
Re: [whatwg/fetch] Image Accept: headers in the spec prevent conneg (#877)
[whatwg/url] Editorial: correct URL path serializer markup (PR #787)
[w3ctag/design-reviews] Suggest linking to standards positions (PR #898)
Re: [whatwg/fullscreen] Document fullscreening vs. modal dialog (Issue #227)
[whatwg/url] The *URL path serializer* steps use bullets instead of being numbered (Issue #786)
- Re: [whatwg/url] URL path serializer steps use bullets instead of being numbered (Issue #786)
- Re: [whatwg/url] URL path serializer steps use bullets instead of being numbered (Issue #786)
Re: [w3c/permissions] Allow returning "prompt" rather than "denied" (Issue #388)
Re: [whatwg/dom] Declarative Shadow DOM (#831)
[WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031)
- Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031)
- Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031)
- Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031)
Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
- Re: [whatwg/streams] TransformStream cleanup using "Transformer.cancel" (PR #1283)
Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414)
- Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414)
- Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414)
- Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414)
- Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414)
Re: [whatwg/fetch] Add a way to have cookie origin and CORS origin be different (Issue #1637)
- Re: [whatwg/fetch] Add a way to have cookie origin and CORS origin be different (Issue #1637)
- Re: [whatwg/fetch] Add a way to have cookie origin and CORS origin be different (Issue #1637)
- Re: [whatwg/fetch] Add a way to have cookie origin and CORS origin be different (Issue #1637)
Re: [w3c/permissions] One time permissions: exposing and specifying grant type (Issue #418)
[whatwg/xhr] FormData & submitter[formaction] (Issue #381)
- Re: [whatwg/xhr] FormData & submitter[formaction] (Issue #381)
- Re: [whatwg/xhr] FormData & submitter[formaction] (Issue #381)
- Re: [whatwg/xhr] FormData & submitter[formaction] (Issue #381)
- Re: [whatwg/xhr] FormData & submitter[formaction] (Issue #381)
- Re: [whatwg/xhr] FormData & submitter[formaction] (Issue #381)
- Re: [whatwg/xhr] FormData & submitter[formaction] (Issue #381)
- Re: [whatwg/xhr] FormData & submitter[formaction] (Issue #381)
- Re: [whatwg/xhr] FormData & submitter[formaction] (Issue #381)
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: [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: [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: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { min }) (#1145)
- Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { min }) (#1145)
[WICG/webcomponents] Should browsers do bookkeeping on DOM parts after initial parse? (Issue #1030)
- Re: [WICG/webcomponents] Should browsers do bookkeeping on DOM parts after initial parse? (Issue #1030)
- Re: [WICG/webcomponents] Should browsers do bookkeeping on DOM parts after initial parse? (Issue #1030)
- Re: [WICG/webcomponents] Should browsers do bookkeeping on DOM parts after initial parse? (Issue #1030)
- Re: [WICG/webcomponents] Should browsers do bookkeeping on DOM parts after initial parse? (Issue #1030)
- Re: [WICG/webcomponents] Should browsers do bookkeeping on DOM parts after initial parse? (Issue #1030)
- Re: [WICG/webcomponents] Should browsers do bookkeeping on DOM parts after initial parse? (Issue #1030)
- Re: [WICG/webcomponents] Should browsers do bookkeeping on DOM parts after initial parse? (Issue #1030)
- Re: [WICG/webcomponents] Should browsers do bookkeeping on DOM parts after initial parse? (Issue #1030)
Re: [w3ctag/design-reviews] Borderless mode (Issue #852)
[w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
- Re: [w3c/clipboard-apis] Add supports API for async clipboard. (PR #192)
Re: [w3c/clipboard-apis] Async clipboard api - write api example: resolved error (PR #189)
Re: [WICG/webcomponents] RFC: Element Handles for Cross-root ARIA (cross-post from wicg/aom) (Issue #1020)
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)
- Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135)
[w3c/editing] add 'all known' to the Success Criteria section of the proposed charter (PR #441)
- Re: [w3c/editing] add 'all known' to the Success Criteria section of the proposed charter (PR #441)
- Re: [w3c/editing] add 'all known' to the Success Criteria section of the proposed charter (PR #441)
- Re: [w3c/editing] add 'all known' to the Success Criteria section of the proposed charter (PR #441)
- Re: [w3c/editing] add 'all known' to the Success Criteria section of the proposed charter (PR #441)
Re: [w3c/manifest] Create Medwin (PR #1095)
Re: [w3c/uievents] `beforeinput` and `compositionupdate` event order (Issue #354)
- Re: [w3c/uievents] `beforeinput` and `compositionupdate` event order (Issue #354)
- Re: [w3c/uievents] `beforeinput` and `compositionupdate` event order (Issue #354)
- Re: [w3c/uievents] `beforeinput` and `compositionupdate` event order (Issue #354)
[w3c/uievents] Find def for "active text passage" (Issue #358)
[w3c/uievents] Define "composition session" (Issue #357)
[w3c/uievents] Export composition events from spec (Issue #356)
Re: [w3c/editing] Define behavior of pressing enter in inline editing host (Issue #430)
Re: [w3c/gamepad] Update getGamepads to include steps for copying gamepads (PR #172)
[w3c/permissions] Inform users when a UA administrator overrides their permission choices. (PR #420)
- Re: [w3c/permissions] Inform users when a UA administrator overrides their permission choices. (PR #420)
- Re: [w3c/permissions] Inform users when a UA administrator overrides their permission choices. (PR #420)
- Re: [w3c/permissions] Inform users when a UA administrator overrides their permission choices. (PR #420)
- Re: [w3c/permissions] Inform users when a UA administrator overrides their permission choices. (PR #420)
- Re: [w3c/permissions] Inform users when a UA administrator overrides their permission choices. (PR #420)
[w3c/editing] be more precise about out of scope (PR #440)
- Re: [w3c/editing] be more precise about out of scope (PR #440)
- Re: [w3c/editing] be more precise about out of scope (PR #440)
- Re: [w3c/editing] be more precise about out of scope (PR #440)
[w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168)
- Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168)
- Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168)
- Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168)
- Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168)
[w3c/selection-api] getSelection().addRange should allow range with both boundary points in shadow tree (Issue #167)
Re: [w3c/editing] Update explainer to add the new write algorithm. (PR #436)
- Re: [w3c/editing] Update explainer to add the new write algorithm. (PR #436)
- Re: [w3c/editing] Update explainer to add the new write algorithm. (PR #436)
Re: [w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424)
- Re: [w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424)
- Re: [w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424)
- Re: [w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424)
[w3ctag/design-reviews] Tag review request for the "Dubbing and Audio description Profiles of TTML2" (Issue #897)
[WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
Re: [w3ctag/design-reviews] TAG spec review of Bounce Tracking Mitigations (Issue #862)
Re: [WICG/webcomponents] Alternative to customized built-in - Element custom enhancements (Issue #1000)
- Re: [WICG/webcomponents] Alternative to customized built-in - Element custom enhancements (Issue #1000)
- Re: [WICG/webcomponents] Alternative to customized built-in - Element custom enhancements (Issue #1000)
- Re: [WICG/webcomponents] Alternative to customized built-in - Element custom enhancements (Issue #1000)
- Re: [WICG/webcomponents] Alternative to customized built-in - Element custom enhancements (Issue #1000)
- Re: [WICG/webcomponents] Alternative to customized built-in - Element custom enhancements (Issue #1000)
- Re: [WICG/webcomponents] Alternative to customized built-in - Element custom enhancements (Issue #1000)
[WICG/webcomponents] Explain the relationship of DOM Parts to XHTML (Issue #1028)
- Re: [WICG/webcomponents] Explain the relationship of DOM Parts to XHTML (Issue #1028)
- Re: [WICG/webcomponents] Explain the relationship of DOM Parts to XHTML (Issue #1028)
- Re: [WICG/webcomponents] Explain the relationship of DOM Parts to XHTML (Issue #1028)
- Re: [WICG/webcomponents] Explain the relationship of DOM Parts to XHTML (Issue #1028)
- Re: [WICG/webcomponents] Explain the relationship of DOM Parts to XHTML (Issue #1028)
- Re: [WICG/webcomponents] Explain the relationship of DOM Parts to XHTML (Issue #1028)
[WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027)
Re: [WICG/webcomponents] [scoped-registries] How does customElements.upgrade() work? (Issue #1001)
Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
[WICG/webcomponents] TPAC Web Components Community Group Breakout Takeaways (Issue #1026)
Re: [WICG/webcomponents] Scoped Custom Element Registries (#716)
- Re: [WICG/webcomponents] Scoped Custom Element Registries (#716)
- Re: [WICG/webcomponents] Scoped Custom Element Registries (#716)
Re: [w3ctag/design-reviews] Fullscreen Popup Windows (Issue #840)
[w3c/ServiceWorker] Editorial: correct rendering of nested algo steps (PR #1692)
- Re: [w3c/ServiceWorker] Editorial: correct rendering of nested algo steps (PR #1692)
- Re: [w3c/ServiceWorker] Editorial: correct rendering of nested algo steps (PR #1692)
- Re: [w3c/ServiceWorker] Editorial: correct rendering of nested algo steps (PR #1692)
- Re: [w3c/ServiceWorker] Editorial: correct rendering of nested algo steps (PR #1692)
Re: [w3c/push-api] check and consume user activation (PR #348)
Re: [w3c/manifest] badge purpose "monochrome" is only supported by Firefox (#905)
- Re: [w3c/manifest] badge purpose "monochrome" is only supported by Firefox (#905)
- Re: [w3c/manifest] badge purpose "monochrome" is only supported by Firefox (#905)
- Re: [w3c/manifest] badge purpose "monochrome" is only supported by Firefox (#905)
- Re: [w3c/manifest] badge purpose "monochrome" is only supported by Firefox (#905)
Re: [w3c/push-api] TPAC 2022 status report (Issue #354)
Re: [whatwg/url] Expose a URLHost class to JavaScript (#288)
Re: [w3c/ServiceWorker] should FetchEvent.request.signal reflect abort status of outer request? (#1544)
Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
Re: [w3c/manifest] should we standardize navigator.standalone ? (Issue #1092)
Re: [w3c/selection-api] Define `Selection.rangeCount` when an input field is focused (Issue #166)
[w3ctag/design-reviews] Partitioning :visited links history (Issue #896)
Re: [w3ctag/design-reviews] Background Blur API (Issue #826)
[w3c/permissions] WebDriver: Make it possible to pass a different origin to "Set Permission" (Issue #419)
- Re: [w3c/permissions] WebDriver: Make it possible to pass a different origin to "Set Permission" (Issue #419)
- Re: [w3c/permissions] WebDriver: Make it possible to pass a different origin to "Set Permission" (Issue #419)
- Re: [w3c/permissions] WebDriver: Make it possible to pass a different origin to "Set Permission" (Issue #419)
- Re: [w3c/permissions] WebDriver: Make it possible to pass a different origin to "Set Permission" (Issue #419)
[w3c/clipboard-apis] Read Blob data for the supported formats on-demand during getType. (Issue #191)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43)
Re: [whatwg/fetch] Streaming upload (Issue #1438)
[w3c/push-api] Declarative Web Push (Issue #360)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
Re: [w3c/clipboard-apis] Make it possible to read image/svg+xml from the clipboard (#92)
[w3ctag/design-reviews] Web Audio API: User-Selectable Render Quantum Size (Issue #895)
Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
[whatwg/webidl] rxt (Issue #1362)
Re: [w3c/screen-orientation] HTML integration (Issue #219)
[whatwg/webidl] Editorial: Remove the note on `@@unscopables` and `[Global]` interfaces (PR #1361)
- Re: [whatwg/webidl] Editorial: Remove the note on `@@unscopables` and `[Global]` interfaces (PR #1361)
- Re: [whatwg/webidl] Editorial: Remove the note on `@@unscopables` and `[Global]` interfaces (PR #1361)
[whatwg/webidl] Throw TypeError if `[Replaceable]` setter fails to reconfigure the property (PR #1360)
[whatwg/webidl] Editorial: Use CreateDataPropertyOrThrow abstract op in more places (PR #1359)
- Re: [whatwg/webidl] Editorial: Use CreateDataPropertyOrThrow abstract op in more places (PR #1359)
- Re: [whatwg/webidl] Editorial: Use CreateDataPropertyOrThrow abstract op in more places (PR #1359)
- Re: [whatwg/webidl] Editorial: Use CreateDataPropertyOrThrow abstract op in more places (PR #1359)
- Re: [whatwg/webidl] Editorial: Use CreateDataPropertyOrThrow abstract op in more places (PR #1359)
Re: [w3ctag/design-reviews] Isolated Web Apps (Issue #842)
[whatwg/dom] matchMedia-like API for element matches (Issue #1225)
Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703)
- Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703)
- Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703)
- Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703)
- Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703)
- Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703)
- Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703)
Re: [whatwg/fetch] Resumable File Uploads (Issue #1626)
Re: [whatwg/fetch] Option to fetch raw byte as is. (without decompressing) (Issue #1524)
[w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439)
- Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439)
- Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439)
- Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439)
[whatwg/url] Escape trailing spaces in opaque paths (PR #785)
Re: [w3ctag/design-reviews] Verifiable Credential Status List 2021 (Issue #874)
Re: [w3ctag/design-reviews] Specification Review: FetchLater API (Issue #887)
- Re: [w3ctag/design-reviews] Specification Review: FetchLater API (Issue #887)
- Re: [w3ctag/design-reviews] Specification Review: FetchLater API (Issue #887)
- Re: [w3ctag/design-reviews] Specification Review: FetchLater API (Issue #887)
- Re: [w3ctag/design-reviews] Specification Review: FetchLater API (Issue #887)
Re: [w3ctag/design-reviews] systemEntropy addition to PerformanceNavigationTiming (Issue #878)
Re: [w3ctag/design-reviews] Web Audio API: RenderCapacity API (Issue #843)
[w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
- Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894)
Re: [whatwg/dom] Provide a "deep clone" shorthand (Issue #1220)
Re: [whatwg/streams] Consider making writer.abort() automatically generate an "AbortError" DOMException? (Issue #1290)
[whatwg/fetch] Editorial: clarify response's URL list (PR #1699)
- Re: [whatwg/fetch] Editorial: clarify response's URL list (PR #1699)
- Re: [whatwg/fetch] Editorial: clarify response's URL list (PR #1699)
Re: [whatwg/url] IDNA: avoid defining valid domain string in terms of the parser (#245)
[whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
- Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)
[whatwg/webidl] DOMException name proposal (Issue #1358)
[w3ctag/design-reviews] FedCM API extension: Error API, AccountAutoSelectedFlag, HostedDomain and Revocation API (Issue #893)
Re: [w3ctag/design-reviews] Web Install API (Issue #888)
- Re: [w3ctag/design-reviews] Web Install API (Issue #888)
- Re: [w3ctag/design-reviews] Web Install API (Issue #888)
Re: [w3ctag/design-reviews] Bluetooth RFCOMM in Web Serial API (Issue #854)
Re: [w3ctag/design-reviews] WebRTC Codec selection API (Issue #836)
Re: [w3ctag/design-reviews] ServiceWorker static routing API (Issue #863)
- Re: [w3ctag/design-reviews] ServiceWorker static routing API (Issue #863)
- Re: [w3ctag/design-reviews] ServiceWorker static routing API (Issue #863)
- Re: [w3ctag/design-reviews] ServiceWorker static routing API (Issue #863)
Re: [w3ctag/design-reviews] Soft Navigations (Issue #879)
- Re: [w3ctag/design-reviews] Soft Navigations (Issue #879)
- Re: [w3ctag/design-reviews] Soft Navigations (Issue #879)
Re: [w3ctag/design-reviews] TAG review request for the IDP signin status API (Issue #884)
- Re: [w3ctag/design-reviews] TAG review request for the IDP signin status API (Issue #884)
- Re: [w3ctag/design-reviews] TAG review request for the IDP signin status API (Issue #884)
Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)
[whatwg/encoding] N'abdiqua pas le temps pour les choses à venir ZTF Phases 9.8.007.64.31?!¿! (Issue #316)
[whatwg/dom] Add flat tree parent definition (PR #1223)
- Re: [whatwg/dom] Add flat tree parent definition (PR #1223)
- Re: [whatwg/dom] Add flat tree parent definition (PR #1223)
- Re: [whatwg/dom] Add flat tree parent definition (PR #1223)
- Re: [whatwg/dom] Add flat tree parent definition (PR #1223)
Re: [w3c/IndexedDB] Add an Observer API (#51)
Re: [w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)
[w3c/manifest] Define "web application" (Issue #1097)
- Re: [w3c/manifest] Define "web application" (Issue #1097)
- Re: [w3c/manifest] Define "web application" (Issue #1097)
- Re: [w3c/manifest] Define "web application" (Issue #1097)
- Re: [w3c/manifest] Define "web application" (Issue #1097)
- Re: [w3c/manifest] Define "web application" (Issue #1097)
- Re: [w3c/manifest] Define "web application" (Issue #1097)
- Re: [w3c/manifest] Define "web application" (Issue #1097)
- Re: [w3c/manifest] Define "web application" (Issue #1097)
- Re: [w3c/manifest] Define "web application" (Issue #1097)
[whatwg/url] Enforce UTF-8 when url is given to the basic URL parser (Issue #783)
[whatwg/xhr] Use HTML's parse a URL (Issue #380)
- Re: [whatwg/xhr] Use HTML's parse a URL (Issue #380)
- Re: [whatwg/xhr] Use HTML's parse a URL (Issue #380)
- Re: [whatwg/xhr] Use HTML's parse a URL (Issue #380)
[whatwg/webidl] <div id="divA">This is <span>some</span> text!</div> (Issue #1357)
Re: [whatwg/dom] Support for HTML/XML stream parsing/rewriting. (Issue #1222)
Re: [whatwg/fetch] Missing interface for uncompressed Content-Length when compression is used (Issue #1358)
Re: [w3c/clipboard-apis] supported type should include MathML types (#141)
Re: [whatwg/fetch] Explicitly ignore 1xx responses (#366)
Re: [whatwg/fetch] Consider restricting 103 Early Hints to HTTP/2 or later (Issue #1698)
- Re: [whatwg/fetch] Consider restricting 103 Early Hints to HTTP/2 or later (Issue #1698)
- Re: [whatwg/fetch] Consider restricting 103 Early Hints to HTTP/2 or later (Issue #1698)
- Re: [whatwg/fetch] Consider restricting 103 Early Hints to HTTP/2 or later (Issue #1698)
Re: [WICG/webcomponents] define behavior of `@import` in Cascading Style Sheet (CSS) modules (#870)
Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
- Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
- Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
- Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
[w3c/editing] TPAC 2023 agenda (Issue #438)
Re: [w3c/editing] TPAC 2023 participation - Call for topics (Issue #427)
[w3ctag/design-reviews] DisplayMediaStreamOptions monitorTypeSurfaces (Issue #892)
[w3c/editing] RFC: Contenteditable "indent" implementations are not aligned with popular editors (Issue #437)
- Re: [w3c/editing] RFC: Contenteditable "indent" implementations are not aligned with popular editors (Issue #437)
- Re: [w3c/editing] RFC: Contenteditable "indent" implementations are not aligned with popular editors (Issue #437)
- Re: [w3c/editing] RFC: Contenteditable "indent" implementations are not aligned with popular editors (Issue #437)
- Re: [w3c/editing] RFC: Contenteditable "indent"/"outdent" implementations are not aligned with popular editors (Issue #437)
- Re: [w3c/editing] RFC: Contenteditable "indent"/"outdent" implementations are not aligned with popular editors (Issue #437)
- Re: [w3c/editing] RFC: Contenteditable "indent"/"outdent" implementations are not aligned with popular editors (Issue #437)
- Re: [w3c/editing] RFC: Contenteditable "indent"/"outdent" implementations are not aligned with popular editors (Issue #437)
- Re: [w3c/editing] RFC: Contenteditable "indent"/"outdent" implementations are not aligned with popular editors (Issue #437)
- Re: [w3c/editing] RFC: Contenteditable "indent"/"outdent" implementations are not aligned with popular editors (Issue #437)
Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674)
- Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674)
- Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674)
- Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674)
- Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674)
[w3ctag/design-reviews] The CSS `word-break: auto-phrase` property (Issue #891)
Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)