Wednesday, 31 May 2023
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [whatwg/dom] Add before removing steps (PR #1185)
- Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546)
- Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546)
- Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546)
- Re: [w3c/FileAPI] Proposal: Add a capability to create a Blob URL with a unique (non-opaque) origin (Issue #192)
- Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829)
- Re: [w3c/uievents] Specify wheel event groups (PR #344)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [w3c/gamepad] Please don't restrict to a secure context (#145)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [whatwg/dom] Add before removing steps (PR #1185)
- Re: [whatwg/dom] Add before removing steps (PR #1185)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [whatwg/dom] Add before removing steps (PR #1185)
- Re: [w3c/ServiceWorker] Use an AbortController instead of signaling abort on AbortSignal (PR #1683)
- Re: [w3c/ServiceWorker] Use an AbortController instead of signaling abort on AbortSignal (PR #1683)
- Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546)
- Re: [whatwg/url] Add file as allowed scheme for blob origin (PR #775)
- Re: [whatwg/url] Add file as allowed scheme for blob origin (PR #775)
- Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546)
- Re: [whatwg/dom] Undefined variable in the "add an event listener" algorithm (Issue #1203)
- Re: [whatwg/dom] Correct undefined variable in add an event listener (PR #1204)
- Re: [whatwg/dom] Correct undefined variable in add an event listener (PR #1204)
- Re: [w3c/uievents] Specify wheel event groups (PR #344)
- Re: [w3c/uievents] Specify wheel event groups (PR #344)
- Re: [whatwg/webidl] Give SharedArrayBuffer a dedicated type (PR #1311)
- Re: [whatwg/webidl] Give SharedArrayBuffer a dedicated type (PR #1311)
- Re: [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
- Re: [whatwg/webidl] Give SharedArrayBuffer a dedicated type (PR #1311)
- Re: [w3c/ServiceWorker] Declarative routing (#1373)
- Re: [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
Tuesday, 30 May 2023
- Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [w3c/ServiceWorker] Use an AbortController instead of signaling abort on AbortSignal (PR #1683)
- [w3c/ServiceWorker] Use an AbortController instead of signaling abort on AbortSignal (PR #1683)
- Re: [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
- Re: [whatwg/url] Add file as allowed scheme for blob origin (PR #775)
- [whatwg/url] Add file as allowed scheme for blob origin (PR #775)
- Re: [w3ctag/design-reviews] Cross-document View Transitions API (Issue #851)
- Re: [whatwg/webidl] Give SharedArrayBuffer a dedicated type (PR #1311)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [whatwg/webidl] Give SharedArrayBuffer a dedicated type (PR #1311)
- [whatwg/webidl] Give SharedArrayBuffer a dedicated type (PR #1311)
- Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [WICG/webcomponents] [a11y]: permit aria-hidden=true on focusable shadow elements in FACE (Issue #1014)
- Re: [whatwg/dom] Undefined variable in the "add an event listener" algorithm (Issue #1203)
- [whatwg/dom] Correct undefined variable in add an event listener (PR #1204)
- [whatwg/webidl] Float16Array integration (Issue #1310)
- Re: [whatwg/dom] Add before removing steps (PR #1185)
- Re: [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
- Re: [whatwg/fetch] Should `processResponse` also receive the internal response, similar to `processResponseConsumeBody`? (Issue #1664)
- Re: [whatwg/fetch] Should `processResponse` also receive the internal response, similar to `processResponseConsumeBody`? (Issue #1664)
- [w3ctag/design-reviews] Cross-document View Transitions API (Issue #851)
Monday, 29 May 2023
- Re: [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183)
- Re: [whatwg/fetch] Should `processResponse` also receive the internal response, similar to `processResponseConsumeBody`? (Issue #1664)
- Re: [w3c/uievents-key] Definition of 'string' (Issue #58)
- Re: [whatwg/fetch] Proposal to block 4190 (sieve) and 6679 (osaut, irc+tls alternate) (Issue #1663)
- Re: [whatwg/fetch] Proposal to block 4190 (sieve) and 6679 (osaut, irc+tls alternate) (Issue #1663)
- Re: [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [w3c/manifest] Themed/colored icons for web apps (Issue #1091)
- Re: [w3c/manifest] Themed/colored icons for web apps (Issue #1091)
Sunday, 28 May 2023
- [w3ctag/design-reviews] Specification review request for Verifiable Credential Data Integrity (Issue #850)
- Re: [w3c/uievents] Missing "Insert" and "Delete" keys from the Event Key Location table (Issue #347)
- Re: [whatwg/fetch] Be more selective with handing out the internal response (PR #1661)
- Re: [w3c/manifest] Themed/colored icons for web apps (Issue #1091)
- Re: [whatwg/fetch] Be more selective with handing out the internal response (PR #1661)
- Re: [whatwg/fetch] Be more selective with handing out the internal response (PR #1661)
- Re: [w3c/manifest] Themed/colored icons for web apps (Issue #1091)
Saturday, 27 May 2023
- [whatwg/url] 9388414819 (Issue #774)
- [whatwg/url] IP (Issue #773)
- [whatwg/dom] Undefined variable in the "add an event listener" algorithm (Issue #1203)
- Re: [whatwg/fetch] Review Draft Publication: December 2022 (3b6fcf6)
- [whatwg/webidl] Null (Issue #1309)
- Re: [whatwg/dom] Event.composedPath() inconsistency between implementors. (Issue #1201)
- Re: [whatwg/fetch] Should `processResponse` also receive the internal response, similar to `processResponseConsumeBody`? (Issue #1664)
- Re: [w3c/uievents] Added Insert and Delete to the Location table (PR #348)
Friday, 26 May 2023
- Re: [whatwg/dom] Editorial: Split attachShadow element list into separate definition (PR #1200)
- [w3c/uievents] Added Insert and Delete to the Location table (PR #348)
- [w3c/uievents] Missing "Insert" and "Delete" keys from the Event Key Location table (Issue #347)
- Re: [whatwg/fetch] Should `processResponse` also receive the internal response, similar to `processResponseConsumeBody`? (Issue #1664)
- Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229)
- Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229)
- Re: [w3c/ServiceWorker] @MMMMCCCCBOT (Issue #1682)
- [w3c/ServiceWorker] @MMMMCCCCBOT (Issue #1682)
- [w3c/ServiceWorker] السلام عليكم (Issue #1681)
- Re: [WICG/webcomponents] [dom-parts] Creation API (Issue #1010)
- Re: [WICG/webcomponents] [dom-parts] Attribute Grouping (Issue #1011)
- Re: [WICG/webcomponents] [dom-parts] cloneWithParts / cloneTree (Issue #1012)
- [w3c/IndexedDB] Consider adding a simple(ish) query engine (Issue #403)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/streams] Recoverable error from failed parameter validation? (Issue #1280)
- Re: [whatwg/streams] Recoverable error from failed parameter validation? (Issue #1280)
- Re: [whatwg/fetch] Should `processResponse` also receive the internal response, similar to `processResponseConsumeBody`? (Issue #1664)
- [whatwg/fetch] Should `processResponse` also receive the internal response, similar to `processResponseConsumeBody`? (Issue #1664)
- [w3ctag/design-reviews] Incremental Font Transfer: Patch Subset (Issue #849)
- Re: [whatwg/fetch] Proposal to block 4190 (sieve) and 6679 (osaut, irc+tls alternate) (Issue #1663)
- [whatwg/fetch] Proposal to block 4190 (sieve) and 6679 (osaut, irc+tls alternate) (Issue #1663)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/streams] Recoverable error from failed parameter validation? (Issue #1280)
- Re: [whatwg/streams] Recoverable error from failed parameter validation? (Issue #1280)
- Re: [whatwg/dom] Event.composedPath() inconsistency between implementors. (Issue #1201)
- Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235)
- Re: [whatwg/fetch] [Question] What is the expected behavior for reusing the Request body in a HTTP redirect fetch (status code 307 / 308)? (Issue #1662)
- Re: [whatwg/fetch] [Question] What is the expected behavior for reusing the Request body in a HTTP redirect fetch (status code 307 / 308)? (Issue #1662)
- Re: [whatwg/fetch] [Question] What is the expected behavior for reusing the Request body in a HTTP redirect fetch (status code 307 / 308)? (Issue #1662)
- Re: [whatwg/fetch] [Question] What is the expected behavior for reusing the Request body in a HTTP redirect fetch (status code 307 / 308)? (Issue #1662)
- [whatwg/fetch] [Question] What is the expected behavior for reusing the Request body in a HTTP redirect fetch (status code 307 / 308)? (Issue #1662)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/dom] Export AbortController's signal (PR #1202)
- Re: [whatwg/dom] Export AbortController's signal (PR #1202)
- Re: [whatwg/url] invalid-reverse-solidus error definition has character mixed up. (Issue #772)
- [whatwg/url] invalid-reverse-solidus error definition has character mixed up. (Issue #772)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [w3c/uievents-key] Key mapping specification for Mac JIS Kana / Eisu, Windows ImeOn / ImeOff, Android KANA (virtual) keys (Issue #55)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
Thursday, 25 May 2023
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
- Re: [w3ctag/design-reviews] Design review: AbortSignal.any() (Issue #737)
- Re: [whatwg/dom] Export AbortController's signal (PR #1202)
- [whatwg/dom] Export AbortController's signal (PR #1202)
- Re: [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
- Re: [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
- [whatwg/fetch] Be more selective with handing out the internal response (PR #1661)
- [whatwg/streams] Recoverable error from failed parameter validation? (Issue #1280)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- [w3c/FileAPI] Specify actual byte reading algorithm for Blob.stream() (Issue #194)
- Re: [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
- Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
- Re: [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
Wednesday, 24 May 2023
- [w3c/manifest] Themed/colored icons for web apps (Issue #1091)
- Re: [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
- [whatwg/streams] Use an AbortController instead of signaling abort on AbortSignal (PR #1279)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [w3ctag/design-reviews] WebAssembly Garbage Collection extensions (Issue #814)
- Re: [w3ctag/design-reviews] Background Blur API (Issue #826)
- Re: [w3ctag/design-reviews] WebAssembly Garbage Collection extensions (Issue #814)
- Re: [w3ctag/design-reviews] requestStorageAccessFor (Issue #808)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner non-"http(s):" URL (PR #771)
- Re: [whatwg/url] The origin of "blob:" URL containing inner "blob:" URL (Issue #770)
- Re: [whatwg/streams] Editorial: update WPT (PR #1264)
- Re: [w3ctag/design-reviews] Element.checkVisibility review (Issue #734)
- Re: [w3ctag/design-reviews] Element.checkVisibility review (Issue #734)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner non-"http(s):" URL (PR #771)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [WICG/webcomponents] Document "layers" for single-use components (#806)
- Re: [whatwg/fullscreen] Editorial: align @namespace declaration with HTML (PR #225)
- Re: [whatwg/fullscreen] Editorial: align @namespace declaration with HTML (PR #225)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [whatwg/fullscreen] Editorial: align @namespace declaration with HTML (PR #225)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [whatwg/fullscreen] Editorial: align @namespace declaration with HTML (PR #225)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- [w3ctag/design-reviews] Specification review for CSS Anchor Positioning (Issue #848)
- Re: [w3c/editing] Mark the copy of the EditContext explainer in this repo as archived (PR #431)
- Re: [w3c/editing] Mark the copy of the EditContext explainer in this repo as archived (PR #431)
Tuesday, 23 May 2023
- [w3c/editing] Mark the copy of the EditContext explainer in this repo as archived (PR #431)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [w3c/gamepad] Please don't restrict to a secure context (#145)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [w3c/gamepad] Please don't restrict to a secure context (#145)
- Re: [w3c/gamepad] Please don't restrict to a secure context (#145)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [w3c/editing] [Delayed Clipboard Rendering] Does macOS support setting the data for the requested pasteboard item asynchronously? (Issue #425)
- [whatwg/fullscreen] Editorial: align @namespace declaration with HTML (PR #225)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [w3c/uievents-key] Key mapping specification for Mac JIS Kana / Eisu, Windows ImeOn / ImeOff, Android KANA (virtual) keys (Issue #55)
- Re: [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [w3c/uievents-code] CFC to publish UI Events KeyboardEvent code Values as a CR in the WebApps WG (Issue #40)
- Re: [w3c/uievents-code] CFC to publish UI Events KeyboardEvent code Values as a CR in the WebApps WG (Issue #40)
- Re: [w3c/uievents-key] CFC to publish UI Events KeyboardEvent key Values as a CR in the WebApps WG (Issue #64)
- Re: [w3c/uievents-key] CFC to publish UI Events KeyboardEvent key Values as a CR in the WebApps WG (Issue #64)
Monday, 22 May 2023
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- [whatwg/url] Return null origin of "blob:" URL containing inner "blob:" URL (PR #771)
- Re: [w3ctag/design-reviews] Element.checkVisibility review (Issue #734)
- Re: [w3ctag/design-reviews] Element.checkVisibility review (Issue #734)
- Re: [w3ctag/design-reviews] Sync Methods for FileSystemSyncAccessHandle in File System Access API (Issue #772)
- [w3ctag/design-reviews] I have reviewed the TAG's Web Platform Design Principles (Issue #847)
- Re: [w3ctag/design-reviews] WebRTC Codec selection API (Issue #836)
- Re: [w3ctag/design-reviews] Sync Methods for FileSystemSyncAccessHandle in File System Access API (Issue #772)
- Re: [w3ctag/design-reviews] Spec review for Scroll-driven Animations (Issue #828)
- Re: [w3ctag/design-reviews] Spec review for Scroll-driven Animations (Issue #828)
- Re: [w3ctag/design-reviews] Element.checkVisibility review (Issue #734)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
- Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
- Re: [whatwg/dom] Event.composedPath() inconsistency between implementors. (Issue #1201)
- Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
- Re: [whatwg/dom] Event.composedPath() inconsistency between implementors. (Issue #1201)
- Re: [whatwg/dom] Event.composedPath() inconsistency between implementors. (Issue #1201)
- [whatwg/dom] Event.composedPath() inconsistency between implementors. (Issue #1201)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
- Re: [whatwg/fetch] The end of fetch response handover needs to operate on the internal response (Issue #1512)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/dom] Editorial: Split attachShadow element list into separate definition (PR #1200)
- Re: [whatwg/dom] Editorial: Split attachShadow element list into separate definition (PR #1200)
- Re: [whatwg/dom] Editorial: Split attachShadow element list into separate definition (PR #1200)
- Re: [whatwg/fetch] Header list "get" return type is unclear (Issue #1659)
- Re: [whatwg/fetch] Editorial: define return types of most header list algorithms (PR #1660)
- Re: [whatwg/fetch] Editorial: define return types of most header list algorithms (PR #1660)
- Re: [whatwg/fetch] Editorial: define return types of most header list algorithms (PR #1660)
- Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204)
- Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204)
- Re: [whatwg/fetch] Editorial: define return types of most header list algorithms (PR #1660)
- [whatwg/fetch] Editorial: define return types of most header list algorithms (PR #1660)
- [whatwg/fetch] Header list "get" return type is unclear (Issue #1659)
Sunday, 21 May 2023
- Re: [w3c/editing] Define behavior of pressing enter in inline editing host (Issue #430)
- Re: [whatwg/fetch] Account for removal of AbortSignal's follow (086e35f)
- [whatwg/fetch] correction en tete (Issue #1658)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Profile - Review Requested (Issue #818)
Saturday, 20 May 2023
Friday, 19 May 2023
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- [w3ctag/design-reviews] Private Aggregation API (Issue #846)
- Re: [w3ctag/design-reviews] Shared Storage API (Issue #747)
- Re: [whatwg/dom] Editorial: Split attachShadow element list into separate definition (PR #1200)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [w3c/editing] Define behavior of pressing enter in inline editing host (Issue #430)
- [w3c/push-api] Best practices to dismiss web push notifications cross devices (Issue #359)
- Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
- Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/dom] Editorial: Split attachShadow element list into separate definition (PR #1200)
- [whatwg/webidl] Hh (Issue #1308)
- Re: [w3c/editing] Define behavior of pressing enter in inline editing host (Issue #430)
Thursday, 18 May 2023
- Re: [w3c/ServiceWorker] Preventing server-forced updates (#822)
- [w3c/ServiceWorker] Support subresource integrity for service workers (Issue #1680)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- [w3ctag/design-reviews] Multiple Readers and Writers in File System Access API (Issue #845)
- Re: [whatwg/dom] Editorial: Split attachShadow element list into separate definition (PR #1200)
- Re: [whatwg/dom] Editorial: Split attachShadow element list into separate definition (PR #1200)
- Re: [w3c/pointerlock] Can we drop the spec version? (Issue #83)
- Re: [whatwg/fetch] Pause readable stream reader (Issue #1651)
- [whatwg/fetch] Editorial: clarify how to get MIME type for request and response (PR #1657)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/dom] Editorial: Split attachShadow element list into separate definition (PR #1200)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [w3c/IndexedDB] Could we drop the spec versioning? (Issue #402)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- [w3c/pointerlock] Can we drop the spec version? (Issue #83)
- [whatwg/webidl] The new rules would require a special permit (Issue #1307)
- [w3c/IndexedDB] Could we drop the spec versioning? (Issue #402)
- Re: [w3c/IndexedDB] TPAC 2022 status report (Issue #389)
- Re: [w3c/IndexedDB] TPAC 2022 status report (Issue #389)
- Re: [whatwg/dom] Editorial: Split attachShadow element list into separate definition (PR #1200)
- [whatwg/dom] Editorial: Split attachShadow element list into separate definition (PR #1200)
Wednesday, 17 May 2023
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [whatwg/dom] Userland AbortSignal (Issue #1195)
- Re: [whatwg/dom] Userland AbortSignal (Issue #1195)
- Re: [w3c/editing] Define behavior of pressing enter in inline editing host (Issue #430)
- [w3c/editing] Define behavior of pressing enter in inline editing host (Issue #430)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- [w3ctag/design-reviews] Update 010-specification-review.md (PR #844)
- Re: [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110)
- Re: [w3ctag/design-reviews] Review of DPUB-ARIA 1.1 and DPUB-AAM 1.1 (Issue #821)
- Re: [w3c/ServiceWorker] Editorial: pass signal to Request/create (PR #1678)
- Re: [whatwg/fetch] Editorial: account for removal of AbortSignal's follow (PR #1646)
- Re: [whatwg/fetch] Editorial: account for removal of AbortSignal's follow (PR #1646)
- Re: [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Proposal: AbortSignal.wrap (Issue #1147)
- Re: [whatwg/dom] Requirement for AbortSignal argument to be named 'signal' can be confusing for some APIs. (Issue #1112)
- Re: [whatwg/dom] Requirement for AbortSignal argument to be named 'signal' can be confusing for some APIs. (Issue #1112)
- Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059)
- Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059)
- Re: [whatwg/dom] Userland AbortSignal (Issue #1195)
- Re: [whatwg/fetch] Pause readable stream reader (Issue #1651)
- Re: [whatwg/fetch] Pause readable stream reader (Issue #1651)
- Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735)
- Re: [whatwg/fetch] Pause readable stream reader (Issue #1651)
- Re: [whatwg/dom] Userland AbortSignal (Issue #1195)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fetch] Pause readable stream reader (Issue #1651)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [w3c/ServiceWorker] FetchEvent: Add origin check before setting replacesClientId (Issue #1679)
- [w3c/ServiceWorker] FetchEvent: Add origin check before setting replacesClientId (Issue #1679)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
Tuesday, 16 May 2023
- Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [WICG/webcomponents] Move imperative parts of DOM-Parts.md to DOM-Parts-Imperative.md (f35141f)
- Re: [WICG/webcomponents] Move imperative parts of DOM-Parts.md to DOM-Parts-Imperative.md (f35141f)
- Re: [WICG/webcomponents] Move imperative parts of DOM-Parts.md to DOM-Parts-Imperative.md (f35141f)
- Re: [WICG/webcomponents] Move imperative parts of DOM-Parts.md to DOM-Parts-Imperative.md (f35141f)
- Re: [WICG/webcomponents] Move imperative parts of DOM-Parts.md to DOM-Parts-Imperative.md (f35141f)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Profile - Review Requested (Issue #818)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [w3ctag/design-reviews] requestStorageAccessFor (Issue #808)
- Re: [w3ctag/design-reviews] requestStorageAccessFor (Issue #808)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
- Re: [w3c/manifest] No way to localize icons? (Issue #1077)
- Re: [w3c/manifest] Application name section might need localization support (Issue #1088)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [WICG/webcomponents] Move imperative parts of DOM-Parts.md to DOM-Parts-Imperative.md (f35141f)
- Re: [WICG/webcomponents] Move imperative parts of DOM-Parts.md to DOM-Parts-Imperative.md (f35141f)
Monday, 15 May 2023
- Re: [WICG/webcomponents] Move imperative parts of DOM-Parts.md to DOM-Parts-Imperative.md (f35141f)
- Re: [WICG/webcomponents] Move imperative parts of DOM-Parts.md to DOM-Parts-Imperative.md (f35141f)
- Re: [whatwg/dom] Define XPath's lang() as ASCII case-insensitive (Issue #1199)
- Re: [WICG/webcomponents] Move imperative parts of DOM-Parts.md to DOM-Parts-Imperative.md (f35141f)
- Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Profile - Review Requested (Issue #818)
- Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586)
- Re: [w3ctag/design-reviews] VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport (Issue #768)
- Re: [w3ctag/design-reviews] Review of IMSC-HRM (Issue #788)
- Re: [w3ctag/design-reviews] Review of IMSC-HRM (Issue #788)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [w3c/uievents-key] CFC to publish UI Events KeyboardEvent key Values as a CR in the WebApps WG (Issue #64)
- Re: [whatwg/fetch] Clarify priority between blob.type and Content-Type in headers for request/response.blob() (Issue #1630)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- [w3c/uievents-key] CFC to publish UI Events KeyboardEvent key Values as a CR in the WebApps WG (Issue #64)
- [w3c/uievents-code] CFC to publish UI Events KeyboardEvent code Values as a CR in the WebApps WG (Issue #40)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fetch] Clarify priority between blob.type and Content-Type in headers for request/response.blob() (Issue #1630)
- Re: [whatwg/fetch] Clarify priority between blob.type and Content-Type in headers for request/response.blob() (Issue #1630)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [w3c/manifest] Application name section might need localization support (Issue #1088)
- Re: [WICG/webcomponents] [custom-elements] Proposal for definition-time validation of dependencies (Issue #988)
- Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
- Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- [whatwg/dom] Define XPath's lang() as ASCII case-insensitive (Issue #1199)
- [whatwg/dom] Import HTML's XPath and XSLT monkey patches (Issue #1198)
- Re: [w3c/manifest] No way to localize icons? (Issue #1077)
- Re: [w3c/manifest] No language/direction metadata for shortcuts? (Issue #1078)
- [w3c/manifest] "internationalization" section (Issue #1090)
- [w3c/manifest] JSON "commonly" encoded in Unicode (Issue #1089)
- [w3c/manifest] Application name section might need localization support (Issue #1088)
- [w3c/manifest] shortcuts and localizability (Issue #1087)
- [w3c/manifest] "security sensitive" items interaction with localization (Issue #1086)
- [w3c/manifest] `name` and `short_name` relationship to localization and accessibility (Issue #1085)
- [w3c/manifest] Use of `CanonicalizeUnicodeLocaleId` (Issue #1084)
- [w3c/manifest] Description of language tags incorrect (Issue #1083)
- [w3c/manifest] Description of `lang` incorrect (Issue #1082)
- [w3c/manifest] Reference to BIDI should probably use SpecRef reference to UAX9 (editorial) (Issue #1081)
- [w3c/manifest] "localizable members" should be defined separately? (Issue #1080)
- Re: [w3c/manifest] No language/direction metadata for shortcuts? (Issue #1078)
- Re: [w3c/manifest] No language/direction metadata for shortcuts? (Issue #1078)
- [w3c/manifest] Value `auto` for `dir` probably shouldn't say "no explicit directionality" (Issue #1079)
- Re: [w3c/manifest] No language/direction metadata for shortcuts? (Issue #1078)
- Re: [w3c/manifest] No language/direction metadata for shortcuts? (Issue #1078)
- [w3c/manifest] No language/direction metadata for shortcuts? (Issue #1078)
- Re: [w3c/manifest] We should add a character limit to `name` and `short_name` (Issue #1070)
- [w3c/manifest] No way to localize icons? (Issue #1077)
- Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
Sunday, 14 May 2023
- [whatwg/xhr] xhr (Issue #375)
- Re: [w3c/FileAPI] Add method to read file into user given Uint8Array (#83)
- Re: [w3c/FileAPI] Add method to read file into user given Uint8Array (#83)
- Re: [whatwg/fetch] Provide opt-in for Expect = "100-continue" (#41)
- Re: [WICG/webcomponents] Why do we really need hyphens? (#658)
Saturday, 13 May 2023
- Re: [WICG/webcomponents] Why do we really need hyphens? (#658)
- Re: [WICG/webcomponents] Why do we really need hyphens? (#658)
- Re: [w3c/FileAPI] Return a byte stream from "get stream" algorithm (PR #188)
- Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
- Re: [WICG/webcomponents] Template Instantiation Support for Microdata (Issue #1013)
- Re: [whatwg/fetch] "consume body" step disagrees with "fully read" on whether the error callback accepts an argument (Issue #1636)
- Re: [whatwg/fetch] Fully read's processBodyError argument needs to take an exception (PR #1650)
- Re: [whatwg/fetch] Fully read's processBodyError argument needs to take an exception (PR #1650)
Friday, 12 May 2023
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fetch] HTTPS Upgrades (Issue #1654)
- 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/uievents] Introduce contextmenuclose or similar event. (#309)
Thursday, 11 May 2023
- [whatwg/webidl] Probar WebIDL (Issue #1305)
- Re: [whatwg/dom] Undeprecate document.all (Issue #1196)
- Re: [whatwg/dom] Undeprecate document.all (Issue #1196)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- [whatwg/webidl] luy$ (Issue #1304)
- Re: [whatwg/dom] Undeprecate document.all (Issue #1196)
- [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164)
- Re: [whatwg/fetch] HTTPS Upgrades (Issue #1654)
- [whatwg/fetch] HTTPS Upgrades (Issue #1654)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- [whatwg/dom] Undeprecate document.all (Issue #1196)
- Re: [w3c/editing] [Delayed Clipboard Rendering] Does macOS support setting the data for the requested pasteboard item asynchronously? (Issue #425)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- [WICG/webcomponents] [a11y]: permit aria-hidden=true on focusable shadow elements in FACE (Issue #1014)
- Re: [w3c/clipboard-apis] Mark up definition of events following bikeshed conventions (PR #181)
- Re: [w3c/clipboard-apis] Mark up definition of events following bikeshed conventions (PR #181)
- Re: [w3c/editing] Update meeting invite link (PR #391)
- Re: [w3c/editing] Update meeting invite link (PR #391)
- Re: [w3c/screen-orientation] Consume user activation (PR #218)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [w3c/editing] [EditContext] Issues for May 11 meeting (Issue #426)
- Re: [w3c/editing] [EditContext] Issues for May 11 meeting (Issue #426)
- Re: [w3c/editing] TPAC 2023 participation (Issue #429)
- Re: [w3c/editing] TPAC 2023 participation (Issue #428)
- [w3c/editing] TPAC 2023 participation (Issue #429)
- [w3c/editing] TPAC 2023 participation (Issue #428)
- [w3c/editing] TPAC 2023 participation (Issue #427)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [w3ctag/design-reviews] FedCM Auto Re-authentication API (Issue #813)
- Re: [w3c/screen-orientation] Promise for unlock()? (#104)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
Wednesday, 10 May 2023
- Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- [w3ctag/design-reviews] Web Audio API: RenderCapacity API (Issue #843)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [w3c/uievents] Specify wheel event groups (PR #344)
- Re: [w3c/uievents] Specify wheel event groups (PR #344)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [w3c/uievents] Introduce contextmenuclose or similar event. (#309)
- Re: [w3c/uievents] Added a new event to communicate context menu dismissal. (PR #322)
- Re: [WICG/webcomponents] Should shadow host have `display: block` by default? (#426)
- Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
- [WICG/webcomponents] Template Instantiation Support for Microdata (Issue #1013)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- [whatwg/xhr] Failed to load (Issue #374)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/webidl] what? (Issue #1303)
- [whatwg/webidl] what? (Issue #1303)
- Re: [w3c/screen-orientation] Add can-lock-orientation media feature to detect if locking is possible (Issue #206)
- Re: [w3c/screen-orientation] Promise for unlock()? (#104)
Tuesday, 9 May 2023
- [w3c/editing] [EditContext] Issues for May 11 meeting (Issue #426)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [w3c/screen-orientation] Require a gesture? (Issue #210)
- Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88)
- Re: [w3c/uievents] Reflect the reality for the focus event order (#290)
- Re: [w3c/uievents] Reflect the reality for the focus event order (#290)
- Re: [w3c/uievents] Reflect the reality for the focus event order (#290)
- Re: [w3c/uievents] Remove dblclick text selection default action to match browsers (Issue #328)
- Re: [w3c/uievents] Remove text selection from the dblclick default action - #328 (PR #329)
- Re: [w3c/uievents] Remove text selection from the dblclick default action - #328 (PR #329)
- Re: [w3c/screen-orientation] Consume user activation (PR #218)
- Re: [w3c/uievents] Remove text selection from the dblclick default action - #328 (PR #329)
- Re: [w3c/uievents] Remove text selection from the dblclick default action - #328 (PR #329)
- Re: [w3c/uievents] Specify wheel event groups (PR #344)
- [w3c/editing] [Delayed Clipboard Rendering] Does macOS support setting the data for the requested pasteboard item asynchronously? (Issue #425)
- Re: [w3c/uievents-code] Needs clearer definition of virtual keyboard's KeyboardEvent.code value if it doesn't emulate physical key event completely (#2)
- Re: [w3c/uievents-code] Get horizontal review for UIEvents KeyboardEvent Code (Issue #32)
- Re: [w3c/uievents-code] Get horizontal review for UIEvents KeyboardEvent Code (Issue #32)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [w3c/uievents-code] Possible error: "Backspace" is listed in the Writing System Keys instead of Functional Keys table (Issue #34)
- Re: [w3c/uievents-code] Possible error: "Backspace" is listed in the Writing System Keys instead of Functional Keys table (Issue #34)
- Re: [w3c/uievents-code] Possible typo: "Page Down" listed as key name for "End" (Issue #33)
- Re: [w3c/uievents-code] Possible typo: "Page Down" listed as key name for "End" (Issue #33)
- Re: [whatwg/dom] Userland AbortSignal (Issue #1195)
- Re: [w3c/uievents-code] Broken references in UI Events KeyboardEvent code Values (Issue #37)
- Re: [w3c/uievents-code] Link implementation report from spec (#31)
- Re: [w3c/uievents-key] Link implementation report from spec (#54)
- Re: [w3c/uievents-key] Definition of 'string' (Issue #58)
- Re: [w3c/uievents-key] Definition of 'string' (Issue #58)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [w3c/uievents-key] Updating Travis Leithead affiliation (PR #63)
- Re: [w3c/uievents-key] Updating Travis Leithead affiliation (PR #63)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [w3c/pointerlock] Should movementX/Y move to UI Events? (Issue #82)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
Monday, 8 May 2023
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [whatwg/fetch] Keep track of errors so they can be exposed (if desired) in UX (and maybe API at some point) (#352)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079)
- Re: [whatwg/url] The origin of "blob:" URL containing inner "blob:" URL (Issue #770)
- [whatwg/url] The origin of "blob:" URL containing inner "blob:" URL (Issue #770)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/dom] Userland AbortSignal (Issue #1195)
- 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] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Pause readable stream reader (Issue #1651)
- Re: [whatwg/streams] Update terminology and example of the streams-for-raw-video explainer according proposed spec PR (PR #1278)
- Re: [whatwg/streams] Update terminology and example of the streams-for-raw-video explainer according proposed spec PR (PR #1278)
- Re: [whatwg/fetch] Pause readable stream reader (Issue #1651)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: share a conditional in fetch response handover (PR #1653)
- Re: [whatwg/fetch] Editorial: share a conditional in fetch response handover (PR #1653)
- [whatwg/fetch] Editorial: share a conditional in fetch response handover (PR #1653)
- Re: [whatwg/fetch] Editorial: name variable internalResponse consistently (PR #1652)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [whatwg/fetch] Editorial: name variable internalResponse consistently (PR #1652)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/webidl] It is unclear if [AllowShared] BufferSource is valid (#961)
- [whatwg/fetch] Editorial: name variable internalResponse consistently (PR #1652)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/fetch] Response static methods use null this value to specify the realm (Issue #1603)
- Re: [whatwg/fetch] Use the current realm for Response's static methods (PR #1649)
- Re: [whatwg/fetch] Use the current realm for Response's static methods (PR #1649)
- Re: [whatwg/fetch] Use the current realm for Response's static methods (PR #1649)
- Re: [whatwg/url] URLSearchParams delete all vs delete one (#335)
- Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735)
- Re: [whatwg/streams] Editorial: account for removal of AbortSignal's follow (PR #1277)
- Re: [whatwg/streams] Editorial: account for removal of AbortSignal's follow (PR #1277)
- Re: [whatwg/fetch] Use the current realm for Response's static methods (PR #1649)
- Re: [whatwg/fetch] Use the current realm for Response's static methods (PR #1649)
- Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735)
- Re: [whatwg/dom] Userland AbortSignal (Issue #1195)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
Sunday, 7 May 2023
- [whatwg/url] Jdp (Issue #769)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/webidl] It is unclear if [AllowShared] BufferSource is valid (#961)
- Re: [whatwg/webidl] It is unclear if [AllowShared] BufferSource is valid (#961)
- 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] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/fetch] Editorial: account for removal of AbortSignal's follow (PR #1646)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
Saturday, 6 May 2023
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [whatwg/streams] Update terminology and example of the streams-for-raw-video explainer according proposed spec PR (PR #1278)
- Re: [whatwg/fetch] Pause readable stream reader (Issue #1651)
- Re: [whatwg/fetch] Pause readable stream reader (Issue #1651)
- Re: [whatwg/fetch] Rename "extract-value flag" to "extract-value" and define it as a boolean (Issue #1567)
- Re: [whatwg/fetch] Editorial: update args for collect an HTTP quoted string (PR #1641)
- Re: [WICG/webcomponents] [dom-parts] Attribute Grouping (Issue #1011)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- [w3ctag/design-reviews] Isolated Web Apps (Issue #842)
Friday, 5 May 2023
- Re: [w3c/pointerlock] Should movementX/Y move to UI Events? (Issue #82)
- Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [whatwg/fetch] Editorial: update args for collect an HTTP quoted string (PR #1641)
- Re: [whatwg/fetch] Editorial: update args for collect an HTTP quoted string (PR #1641)
- Re: [whatwg/fetch] Editorial: update args for collect an HTTP quoted string (PR #1641)
- Re: [whatwg/fetch] Editorial: update args for collect an HTTP quoted string (PR #1641)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079)
- Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735)
- Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735)
- Re: [whatwg/streams] Update terminology and example of the streams-for-raw-video explainer according proposed spec PR (PR #1278)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- [whatwg/fetch] Pause readable stream reader (Issue #1651)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/dom] Filtering only trusted events in addEventListener (#1016)
- [whatwg/dom] Userland AbortSignal (Issue #1195)
- [whatwg/streams] Update terminology and example of the streams-for-raw-video explainer according proposed spec PR (PR #1278)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/dom] Filtering only trusted events in addEventListener (#1016)
- Re: [whatwg/dom] Robust events (#1016)
- Re: [whatwg/dom] Robust events (#1016)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [whatwg/dom] Robust events (#1016)
- Re: [w3c/ServiceWorker] Editorial: pass signal to Request/create (PR #1678)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [whatwg/dom] Robust events (#1016)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- [whatwg/dom] Stop exporting AbortSignal's signal abort (Issue #1194)
- [w3ctag/design-reviews] Tabbed web apps (Issue #841)
Thursday, 4 May 2023
- Re: [w3c/ServiceWorker] Editorial: pass signal to Request/create (PR #1678)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/url] Skipping an item while iterating is undefined (Issue #768)
- Re: [w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [WICG/webcomponents] Scoped Custom Element Registries (#716)
- Re: [WICG/webcomponents] Scoped Custom Element Registries (#716)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/dom] Allow other specs to add event listeners ergonomically (#878)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)
- Re: [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/fetch] "consume body" step disagrees with "fully read" on whether the error callback accepts an argument (Issue #1636)
- Re: [whatwg/fetch] Add a way to have cookie origin and CORS origin be different (Issue #1637)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- [whatwg/fetch] Fully read's processBodyError argument needs to take an exception (PR #1650)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- [whatwg/fetch] Use the current realm for Response's static methods (PR #1649)
- Re: [whatwg/dom] Allow other specs to add event listeners ergonomically (#878)
- Re: [whatwg/dom] Allow other specs to add event listeners ergonomically (#878)
- Re: [whatwg/dom] Allow other specs to add event listeners ergonomically (#878)
- Re: [whatwg/dom] Allow other specs to add event listeners ergonomically (#878)
- Re: [w3c/uievents-key] Definition of 'string' (Issue #58)
- Re: [whatwg/dom] Allow other specs to add event listeners ergonomically (#878)
- Re: [whatwg/fetch] Editorial: account for removal of AbortSignal's follow (PR #1646)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
- Re: [whatwg/webidl] Throwing DOMExceptions in the context of a promise returning operation (Issue #1301)
- Re: [whatwg/dom] Allow other specs to add event listeners ergonomically (#878)
- Re: [whatwg/webidl] Throwing DOMExceptions in the context of a promise returning operation (Issue #1301)
- Re: [whatwg/dom] Allow other specs to add event listeners ergonomically (#878)
- [whatwg/webidl] Throwing DOMExceptions in the context of a promise returning operation (Issue #1301)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Allow other specs to add event listeners ergonomically (#878)
- [whatwg/fetch] Hola (Issue #1648)
- Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
- Re: [w3c/screen-orientation] Split out the safety checks into a shared algorithm (Issue #237)
- Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
- [w3c/screen-orientation] Use "user attention" of top-level traversable (Issue #252)
- Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
- Re: [whatwg/fullscreen] Flatten requestFullscreen() error conditions (PR #224)
- [whatwg/dom] const paragraphs = document.querySelectorAll("p"); // paragraphs[0] is the first <p> element // paragraphs[1] is the second <p> element, etc. alert(paragraphs[0].nodeName); (Issue #1193)
- Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
- Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
- Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
- Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
- Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
Wednesday, 3 May 2023
- Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607)
- [w3c/ServiceWorker] Editorial: pass signal to Request/create (PR #1678)
- Re: [whatwg/fetch] Editorial: account for removal of AbortSignal's follow (PR #1646)
- Re: [whatwg/fetch] Editorial: account for removal of AbortSignal's follow (PR #1646)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/streams] Editorial: account for removal of AbortSignal's follow (PR #1277)
- Re: [whatwg/streams] Editorial: account for removal of AbortSignal's follow (PR #1277)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/storage] Sandboxed application file system (Issue #164)
- [whatwg/storage] Application file system (Issue #164)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/fetch] Editorial: account for removal of AbortSignal's follow (PR #1646)
- Re: [whatwg/fetch] Editorial: account for removal of AbortSignal's follow (PR #1646)
- Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
- [whatwg/url] Skipping an item while iterating is undefined (Issue #768)
- Re: [whatwg/streams] Editorial: account for removal of AbortSignal's follow (PR #1277)
- Re: [whatwg/streams] Editorial: account for removal of AbortSignal's follow (PR #1277)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- [whatwg/fullscreen] Flatten requestFullscreen() error conditions (PR #224)
- Re: [whatwg/fullscreen] Consume user gestures in requestFullscreen (#152)
- Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153)
- Re: [whatwg/streams] Editorial: account for removal of AbortSignal's follow (PR #1277)
- Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153)
- Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153)
- Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153)
- Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153)
- Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153)
- Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153)
- Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [WICG/webcomponents] [dom-parts] Creation API (Issue #1010)
Tuesday, 2 May 2023
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
- [whatwg/streams] Editorial: account for removal of AbortSignal's follow (PR #1277)
- Re: [whatwg/fetch] Editorial: account for removal of AbortSignal's follow (PR #1646)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- [w3ctag/design-reviews] Fullscreen Popup Windows (Issue #840)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- [WICG/webcomponents] [dom-parts] cloneWithParts / cloneTree (Issue #1012)
- [WICG/webcomponents] [dom-parts] Attribute Grouping (Issue #1011)
- [WICG/webcomponents] [dom-parts] Creation API (Issue #1010)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- [whatwg/fetch] Editorial: account for removal of AbortSignal's follow (PR #1646)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (Issue #1068)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250)
- Re: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250)
- Re: [w3c/screen-orientation] Screen orientation change need to queue a task to fire an event properly (Issue #244)
Monday, 1 May 2023
- [w3c/uievents] Create jekyll-docker.yml (PR #345)
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add before removing steps (PR #1185)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [whatwg/dom] Attribute change steps should run after setting the value, not before (Issue #1190)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [whatwg/fetch] Why does the Fetch standard forbid GET Body when it's not against REST? (Issue #1644)
- Re: [whatwg/fetch] Why does the Fetch standard forbid GET Body when it's not against REST? (Issue #1644)
- Re: [w3c/uievents-code] Updating Travis Leithead affiliation (PR #39)
- Re: [w3c/uievents-code] Updating Travis Leithead affiliation (PR #39)
- [w3c/uievents-code] Updating Travis Leithead affiliation (PR #39)
- [w3c/uievents-key] Updating Travis Leithead affiliation (PR #63)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204)
- Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204)
- Re: [whatwg/fetch] Consider shifting the "bad port list" to an allowlist. (#1189)
- [w3c/pointerlock] Should movementX/Y move to UI Events? (Issue #82)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483)
- Re: [w3c/screen-orientation] Should we standardize window.orientation? (Issue #249)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)