Friday, 31 March 2023
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161)
- Re: [WICG/webcomponents] FACE + invalidState + delegatesFocus throws "An invalid form control with name='{name}' is not focusable." on form submit (Issue #995)
- Re: [WICG/webcomponents] FACE + invalidState + delegatesFocus throws "An invalid form control with name='{name}' is not focusable." on form submit (Issue #995)
- [WICG/webcomponents] FACE + invalidState + delegatesFocus throws "An invalid form control with name='{name}' is not focusable." on form submit (Issue #995)
- Re: [whatwg/url] Public Suffix API (#528)
- Re: [whatwg/dom] Disconnect single target instead of all (#126)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [whatwg/fullscreen] ::backdrop and :fullscreen now defined in CSS specs (Issue #221)
- Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760)
- [whatwg/fullscreen] ::backdrop and :fullscreen now defined in CSS specs (Issue #221)
- [whatwg/dom] HTTPS (Issue #1180)
- Re: [whatwg/dom] Disconnect single target instead of all (#126)
- Re: [whatwg/dom] Documents never have their node document set? (Issue #1178)
- Re: [whatwg/dom] Fix #1178: Define a document's node document. (PR #1179)
- Re: [whatwg/dom] Fix #1178: Define a document's node document. (PR #1179)
- Re: [whatwg/streams] Can pipeTo() be synchronous? (Issue #1243)
- Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263)
- Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263)
- Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263)
- Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263)
- Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263)
- Re: [whatwg/dom] Disconnect single target instead of all (#126)
- Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823)
- Re: [whatwg/streams] Specify realm for object creation (Issue #1213)
Thursday, 30 March 2023
- Re: [whatwg/dom] Disconnect single target instead of all (#126)
- [whatwg/fetch] Resumable File Uploads (Issue #1626)
- [whatwg/storage] Editorial: Export storage keys, their origins, and storage sheds. (PR #162)
- Re: [whatwg/streams] Specify realm for object creation (Issue #1213)
- [whatwg/dom] Fix #1178: Define a document's node document. (PR #1179)
- Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263)
- Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263)
- [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263)
- Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [w3ctag/design-reviews] Background Blur API (Issue #826)
- [w3ctag/design-reviews] Web Bluetooth exclusionFilters option in requestDevice() (Issue #830)
- Re: [whatwg/dom] Documents never have their node document set? (Issue #1178)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- [w3c/ServiceWorker] Servet WEB (Issue #1675)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
Wednesday, 29 March 2023
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Don't recommend extensions use vendor prefixing (Issue #1072)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073)
- Re: [w3ctag/design-reviews] Display and content-visibility animations (Issue #824)
- Re: [w3ctag/design-reviews] Transitions on specified discrete properties (Issue #825)
- Re: [w3ctag/design-reviews] Transitions on specified discrete properties (Issue #825)
- Re: [w3ctag/design-reviews] Display and content-visibility animations (Issue #824)
- [w3ctag/design-reviews] Entry and Exit Animations (Issue #829)
- [whatwg/dom] Documents never have their node document set? (Issue #1178)
- Re: [w3c/editing] Additional documents for unsanitized HTML read/write (PR #422)
- Re: [w3c/editing] Additional documents for unsanitized HTML read/write (PR #422)
- Re: [w3c/editing] Additional documents for unsanitized HTML read/write (PR #422)
- Re: [w3c/editing] Additional documents for unsanitized HTML read/write (PR #422)
- Re: [w3c/editing] Additional documents for unsanitized HTML read/write (PR #422)
- Re: [w3c/editing] Additional documents for unsanitized HTML read/write (PR #422)
- Re: [w3ctag/design-reviews] Transitions on specified discrete properties (Issue #825)
- Re: [w3c/editing] Additional documents for unsanitized HTML read/write (PR #422)
- [w3c/editing] Additional documents for unsanitized HTML read/write (PR #422)
- Re: [w3c/gamepad] Please don't restrict to a secure context (#145)
- Re: [w3ctag/design-reviews] Transitions on specified discrete properties (Issue #825)
- Re: [w3ctag/design-reviews] Background Blur API (Issue #826)
- Re: [w3ctag/design-reviews] Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 (Issue #811)
- Re: [w3ctag/design-reviews] Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 (Issue #811)
- Re: [w3c/manifest] Personal note (Issue #1074)
- Re: [w3ctag/design-reviews] CR Snapshot Review for EPUB 3.3 (Issue #816)
- Re: [w3c/uievents] Wheel event groups are not defined (Issue #338)
- [w3c/manifest] Personal note (Issue #1074)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [whatwg/webidl] Clarify #named-properties-object (PR #1285)
- Re: [whatwg/webidl] Clarify #named-properties-object (PR #1285)
- Re: [whatwg/webidl] Clarify #named-properties-object (PR #1285)
- Re: [whatwg/webidl] Clarify #named-properties-object (PR #1285)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [whatwg/dom] Don't store is value when it won't be useful (#661)
- Re: [whatwg/dom] Don't store is value when it won't be useful (#661)
- Re: [whatwg/webidl] Clarify #named-properties-object (PR #1285)
- 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: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/webidl] Clarify #named-properties-object (PR #1285)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/webidl] Clarify #named-properties-object (PR #1285)
Tuesday, 28 March 2023
- Re: [whatwg/fetch] add step for upgrades, still missing fallback (ec498bd)
- Re: [whatwg/fetch] add step for upgrades, still missing fallback (ec498bd)
- Re: [whatwg/dom] [Range] Should the DOM range spec include an i18n warning? (Issue #1177)
- Re: [whatwg/dom] [Range] Should the DOM range spec include an i18n warning? (Issue #1177)
- Re: [whatwg/url] HISTORY & SECURITY: URL Parsing Differences Between Implementations Security Issues (Issue #766)
- [whatwg/url] HISTORY: URL Parsing Differences Between Implementations Security Issues (Issue #766)
- [whatwg/webidl] Clarify #named-properties-object (PR #1285)
- Re: [w3c/uievents-code] Unicode terminology (Issue #36)
- Re: [w3c/uievents-code] update unicode terminology (PR #38)
- Re: [w3c/uievents-key] Use of uppercase hex for code points (editorial) (Issue #60)
- Re: [w3c/uievents-key] use uppercase hex for code points (PR #61)
- Re: [w3c/uievents-key] Definition of 'string' (Issue #58)
- [whatwg/xhr] c (Issue #372)
- Re: [whatwg/fetch] Correct blob: URL range requests (e1f8129)
- Re: [whatwg/fetch] Correct blob: URL range requests (e1f8129)
- Re: [w3c/uievents-code] update unicode terminology (PR #38)
- Re: [w3c/uievents-code] update unicode terminology (PR #38)
- Re: [w3c/uievents-code] update unicode terminology (PR #38)
- Re: [w3c/uievents-code] update unicode terminology (PR #38)
- Re: [w3ctag/design-reviews] Background Blur API (Issue #826)
- Re: [w3ctag/design-reviews] CR Snapshot Review for EPUB 3.3 (Issue #816)
- Re: [w3ctag/design-reviews] CR Snapshot Review for EPUB 3.3 (Issue #816)
- Re: [whatwg/dom] [Range] Should the DOM range spec include an i18n warning? (Issue #1177)
- Re: [whatwg/fetch] add step for upgrades, still missing fallback (ec498bd)
- Re: [w3c/uievents-key] update the reference to UAX15 (PR #62)
- Re: [w3c/uievents-key] use uppercase hex for code points (PR #61)
- Re: [w3c/uievents-code] update unicode terminology (PR #38)
- Re: [w3c/uievents-key] update the reference to UAX15 (PR #62)
- Re: [w3c/uievents-key] use uppercase hex for code points (PR #61)
- Re: [WICG/webcomponents] Editor support for WebComponents (#776)
- [w3c/uievents-code] update unicode terminology (PR #38)
- Re: [whatwg/dom] [Range] Should the DOM range spec include an i18n warning? (Issue #1177)
Monday, 27 March 2023
- Re: [w3ctag/design-reviews] Spec review for Scroll-driven Animations (Issue #828)
- [w3ctag/design-reviews] Spec review for Scroll-driven Animations (Issue #828)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- [whatwg/fetch] What destination should my feature use (Issue #1625)
- [whatwg/fetch] Apple Day (Issue #1624)
- [whatwg/dom] [Range] Should the DOM range spec include an i18n warning? (Issue #1177)
- [whatwg/fetch] issues (Issue #1623)
- [w3c/uievents-key] update the reference to UAX15 (PR #62)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- [w3c/uievents-key] use uppercase hex for code points (PR #61)
- Re: [WICG/webcomponents] HTML Modules (#645)
- Re: [whatwg/streams] Could a byte stream read directly into and out of a SAB (w/o transfer)? (#757)
- Re: [whatwg/streams] Could a byte stream read directly into and out of a SAB (w/o transfer)? (#757)
Sunday, 26 March 2023
- Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578)
- 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)
Saturday, 25 March 2023
- 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/fullscreen] Hide pop-ups when making an element fullscreen (PR #204)
- Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204)
- [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
Friday, 24 March 2023
- Re: [w3c/editing] Mark the old EditContext spec as archived (PR #421)
- Re: [w3c/editing] Mark the old EditContext spec as archived (PR #421)
- [w3c/editing] Mark the old EditContext spec as archived (PR #421)
- Re: [WICG/webcomponents] HTML Modules as a leaf node in the module graph or not? (#805)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- [whatwg/fetch] How to send ‘OPTIONS * HTTP/1.1’ requests (asterisk form) with fetch()? (Issue #1622)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3ctag/design-reviews] Review request for TURTLEDOVE (Issue #723)
- Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453)
- Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453)
- Re: [w3ctag/design-reviews] Shared Storage API (Issue #747)
- Re: [whatwg/fetch] Response static methods use null this value to specify the realm (Issue #1603)
- Re: [whatwg/fetch] Response static methods use null this value to specify the realm (Issue #1603)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- [whatwg/dom] <span id="line939"></span> url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEgAAABIAQMAAABvIyEEAAAABlBMVEUAAABTU1OoaSf/AAAAAXRSTlMAQObYZgAAADtJREFUKM9jYBgFRIP///8/wM16wGAhg5fF3ICbVYCfZf8fD4uBgXlAWPx/8LEKmJvxsCiwFxji/3GyANQXWAZOSFkcAAAAAElFTkSuQmCC) 1x, (Issue #1175)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618)
- [WICG/webcomponents] Templates are currently half a solution to web component HTML (Issue #994)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [whatwg/fetch] Make response body streams readable byte streams (#1246)
- Re: [whatwg/fetch] Make response body streams readable byte streams (#1246)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618)
- Re: [whatwg/streams] "If flushPromise was rejected with reason r, the..." (Issue #1262)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
Thursday, 23 March 2023
- Re: [w3c/push-api] A javascript api for sending push notifications to others (#303)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [whatwg/dom] Allow 'lower-boundary' scoping argument in querySelector() (Issue #1172)
- Re: [w3ctag/design-reviews] Multi-Screen Window Placement on the Web - Initiating Multi-Screen Experiences (Issue #767)
- Re: [w3ctag/design-reviews] Multi-Screen Window Placement on the Web - Initiating Multi-Screen Experiences (Issue #767)
- Re: [w3c/push-api] A javascript api for sending push notifications to others (#303)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [whatwg/fullscreen] Create SECURITY.md (PR #220)
- [whatwg/fullscreen] Create SECURITY.md (PR #220)
- [whatwg/fullscreen] BARCLAYS BANK (Issue #219)
- Re: [whatwg/fetch] Correct blob: URL range requests (PR #1621)
- Re: [whatwg/fetch] Correct blob: URL range requests (PR #1621)
- Re: [whatwg/fetch] Add `<div algorithm>` wrappers around algorithms (Issue #1526)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619)
- Re: [whatwg/storage] Meta: update repository files (PR #161)
- Re: [whatwg/storage] Meta: update repository files (PR #161)
- [whatwg/storage] Meta: update repository files (PR #161)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619)
- [whatwg/streams] "If flushPromise was rejected with reason r, the..." (Issue #1262)
- Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760)
- Re: [w3ctag/design-reviews] Review request for TURTLEDOVE (Issue #723)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
Wednesday, 22 March 2023
- Re: [w3c/IndexedDB] Specifying "indexedDB" storage bottle deletion when data is evicted by quota (Issue #400)
- Re: [w3c/IndexedDB] Specifying "indexedDB" storage bottle deletion when data is evicted by quota (Issue #400)
- Re: [w3c/IndexedDB] Main (PR #399)
- [w3ctag/design-reviews] Early design review: scheduler.yield() (Issue #827)
- Re: [w3c/IndexedDB] Specifying "indexedDB" storage bottle deletion when data is evicted by quota (Issue #400)
- [w3c/IndexedDB] Specifying "indexedDB" storage bottle deletion when data is evicted by quota (Issue #400)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- [whatwg/encoding] 20s (Issue #308)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- Re: [w3c/ServiceWorker] Skip service worker no-op fetch handler (Issue #1671)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674)
- Re: [whatwg/dom] Export event listener callback (PR #1174)
- Re: [whatwg/dom] Export event listener callback (PR #1174)
- Re: [whatwg/dom] Export event listener callback (PR #1174)
- [whatwg/dom] Export event listener callback (PR #1174)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- Re: [whatwg/fetch] Correct blob: URL range requests (PR #1621)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- Re: [whatwg/dom] Editorial: an HTMLCollection (PR #1173)
- Re: [whatwg/dom] Editorial: an HTMLCollection (PR #1173)
- Re: [whatwg/dom] Editorial: an HTMLCollection (PR #1173)
- Re: [whatwg/dom] Editorial: an HTMLCollection (PR #1173)
- [whatwg/dom] Editorial: an HTMLCollection (PR #1173)
- Re: [whatwg/dom] Allow 'lower-boundary' scoping argument in querySelector() (Issue #1172)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765)
- Re: [whatwg/fetch] Don't append controls for upstream caches. (#788)
- Re: [whatwg/fetch] add step for upgrades, still missing fallback (ec498bd)
Tuesday, 21 March 2023
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420)
- Re: [whatwg/fetch] add fallback to http algorithm (ce88a76)
- Re: [whatwg/fetch] add fallback to http algorithm (ce88a76)
- Re: [whatwg/fetch] add step for upgrades, still missing fallback (ec498bd)
- Re: [whatwg/fetch] add step for upgrades, still missing fallback (ec498bd)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420)
- Re: [WICG/webcomponents] [dom-parts] Remove `.value` and `.commit()`, add `replaceChildren` (Issue #991)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990)
- Re: [WICG/webcomponents] [dom-parts] Remove `.value` and `.commit()`, add `replaceChildren` (Issue #991)
- [w3c/editing] Add unsanitized html read/write doc. (PR #420)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990)
- Re: [WICG/webcomponents] [dom-parts] Remove `.value` and `.commit()`, add `replaceChildren` (Issue #991)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161)
- Re: [WICG/webcomponents] [dom-parts] Remove `.value` and `.commit()`, add `replaceChildren` (Issue #991)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990)
- [WICG/webcomponents] [dom-parts] Browser updating parts list from `getParts()` (Issue #993)
- [WICG/webcomponents] [dom-parts] Tree structure of parts in the DOM (Issue #992)
- [WICG/webcomponents] [dom-parts] Remove `.value` and `.commit()`, add `replaceChildren` (Issue #991)
- [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990)
- Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186)
- [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186)
- Re: [whatwg/fetch] Correct blob: URL range requests (PR #1621)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- [whatwg/fetch] Correct blob: URL range requests (PR #1621)
- Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760)
- Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523)
- Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
Monday, 20 March 2023
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158)
- Re: [whatwg/url] URLSearchParams append/set: variadic values argument? (Issue #762)
- Re: [whatwg/url] URLSearchParams append/set: variadic values argument? (Issue #762)
- Re: [w3ctag/design-reviews] requestStorageAccessFor (Issue #808)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [w3ctag/design-reviews] text-wrap: balance (Issue #822)
- Re: [w3ctag/design-reviews] text-wrap: balance (Issue #822)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743)
- [whatwg/dom] Allow 'lower-boundary' scoping argument in querySelector() (Issue #1172)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [w3c/editing] JS API to invoke native desktop emoji picker (#350)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- Re: [w3c/editing] JS API to invoke native desktop emoji picker (#350)
- Re: [whatwg/webidl] Purpose of call-a-user-object’s-operation’s opName parameter (Issue #1282)
- Re: [whatwg/dom] What exactly does reflect touch target list entity? (Issue #1171)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- Re: [whatwg/fetch] CI test (PR #1605)
- Re: [w3c/editing] JS API to invoke native desktop emoji picker (#350)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170)
- [w3ctag/design-reviews] Background Blur API (Issue #826)
- Re: [whatwg/dom] What exactly does reflect touch target list entity? (Issue #1171)
- [whatwg/dom] What exactly does reflect touch target list entity? (Issue #1171)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674)
- [whatwg/dom] Export terms needed for ServiceWorker/1671 (PR #1170)
- Re: [w3c/gamepad] Please don't restrict to a secure context (#145)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [whatwg/url] URL.canParse() (Issue #713)
- Re: [whatwg/url] Add URL.canParse() (PR #763)
- Re: [whatwg/webidl] Review Draft Publication: March 2023 (PR #1284)
- [whatwg/webidl] Review Draft Publication: March 2023 (PR #1284)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
Sunday, 19 March 2023
- Re: [whatwg/dom] Export "event listener/type". (PR #1169)
- Re: [whatwg/dom] Export "event listener/type". (PR #1169)
- Re: [whatwg/webidl] Purpose of call-a-user-object’s-operation’s opName parameter (Issue #1282)
Saturday, 18 March 2023
- Re: [whatwg/xhr] Need Discussion of 'why' Behind Deprecation of sync xhr (Issue #371)
- Re: [whatwg/url] URLSearchParams append/set: variadic values argument? (Issue #762)
- Re: [whatwg/url] URLSearchParams append/set: variadic values argument? (Issue #762)
Friday, 17 March 2023
- [whatwg/webidl] Purpose of call-a-user-object’s-operation’s opName parameter (Issue #1282)
- Re: [w3ctag/design-reviews] requestStorageAccessFor (Issue #808)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743)
- Re: [whatwg/xhr] Need Discussion of 'why' Behind Deprecation of sync xhr (Issue #371)
- Re: [whatwg/xhr] Need Discussion of 'why' Behind Deprecation of sync xhr (Issue #371)
- [whatwg/xhr] Need Discussion of 'why' Behind Deprecation of sync xhr (Issue #371)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618)
- Re: [whatwg/dom] Export "event listener/type". (PR #1169)
- Re: [whatwg/dom] Export "event listener/type". (PR #1169)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [whatwg/url] Add URL.canParse() (PR #763)
- Re: [whatwg/webidl] Should a read–write maplike/setlike interface be allowed having static operations with same name as set methods, e.g. clear, delete ... (Issue #1280)
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281)
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281)
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281)
- Re: [whatwg/dom] Export "event listener/type". (PR #1169)
- [whatwg/dom] Export "event listener/type". (PR #1169)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3c/uievents] Specify wheel event groups (PR #344)
- Re: [w3c/permissions] add accessibility considerations (PR #412)
- Re: [w3c/permissions] add accessibility considerations (PR #412)
Thursday, 16 March 2023
- Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [w3ctag/design-reviews] FileSystemHandle Unique ID (Issue #764)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281)
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281)
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [whatwg/url] Add URL.canParse() (PR #763)
- Re: [whatwg/url] URL.canParse() (Issue #713)
- [whatwg/url] Add URL.canParse() (PR #763)
- [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281)
- Re: [w3ctag/design-reviews] CR Snapshot Review for EPUB 3.3 (Issue #816)
- Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823)
- Re: [whatwg/streams] Can pipeTo() be synchronous? (Issue #1243)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [whatwg/url] URLSearchParams append/set: variadic values argument? (Issue #762)
- Re: [whatwg/webidl] Should a read–write maplike/setlike interface be allowed having static operations with same name as set methods, e.g. clear, delete ... (Issue #1280)
- Re: [whatwg/streams] Can pipeTo() be synchronous? (Issue #1243)
- Re: [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161)
- Re: [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161)
- Re: [whatwg/webidl] Should a read–write maplike/setlike interface be allowed having static operations with same name as set methods, e.g. clear, delete ... (Issue #1280)
- [whatwg/webidl] Should a read–write maplike/setlike interface be allowed having static operations with same name as set methods, e.g. clear, delete ... (Issue #1280)
- 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/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161)
- Re: [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- 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)
- [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: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
Wednesday, 15 March 2023
- Re: [w3c/selection-api] getComposedRange() review (Issue #161)
- 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] Spring 2023 "F2F" (Issue #978)
- Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823)
- [w3ctag/design-reviews] Display and content-visibility animations (Issue #824)
- [w3ctag/design-reviews] Transitions on specified discrete properties (Issue #825)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161)
- Re: [w3ctag/design-reviews] Native File System API (#390)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
- Re: [w3ctag/design-reviews] Native File System API (#390)
- Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823)
- Re: [w3ctag/design-reviews] Native File System API (#390)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823)
- Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354)
- Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354)
- Re: [whatwg/url] javascript: URL parsing (#307)
- Re: [w3ctag/design-reviews] text-wrap: balance (Issue #822)
- 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: add <div algorithm> wrappers to data URLs (PR #1619)
- [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619)
Tuesday, 14 March 2023
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/webidl] Annotations for what may throw (#603)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [w3ctag/design-reviews] Wildcards in Permissions Policy Origins (Issue #765)
- Re: [whatwg/dom] Do not dispatch a trusted event when target and reletedTarget are identical (#336)
- Re: [whatwg/url] URLSearchParams append/set: variadic values argument? (Issue #762)
- Re: [whatwg/url] URLSearchParams.appendAll(iterable) (#461)
- [whatwg/url] URLSearchParams append/set: variadic values argument? (Issue #762)
- Re: [whatwg/dom] Do not dispatch a trusted event when target and reletedTarget are identical (#336)
- Re: [whatwg/encoding] Static methods for TextEncoder and TextDecoder (PR #284)
- Re: [whatwg/url] URLSearchParams.appendAll(iterable) (#461)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161)
- Re: [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
- Re: [w3ctag/design-reviews] Gamepad Extensions API touch input (Issue #799)
- Re: [w3ctag/design-reviews] Gamepad Extensions API touch input (Issue #799)
- 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] Do not dispatch a trusted event when target and reletedTarget are identical (#336)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [whatwg/fullscreen] Consider removing the containing block adjustment for popovers (Issue #218)
- Re: [whatwg/fullscreen] Consider removing the containing block adjustment for popovers (Issue #218)
- Re: [whatwg/fullscreen] Consider removing the containing block adjustment for popovers (Issue #218)
Monday, 13 March 2023
- [whatwg/streams] S.g. (Issue #1261)
- Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760)
- Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808)
- Re: [w3ctag/design-reviews] FedCM Auto Re-authentication API (Issue #813)
- Re: [w3ctag/design-reviews] Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 (Issue #811)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [w3ctag/design-reviews] text-wrap: balance (Issue #822)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- Re: [whatwg/dom] Do not dispatch a trusted event when target and reletedTarget are identical (#336)
- Re: [whatwg/url] IPv4 parser "invents" a valid ip from doi prefix; is this / should this be correct behaviour? (Issue #761)
- Re: [whatwg/url] IPv4 parser "invents" a valid ip from doi prefix; is this / should this be correct behaviour? (Issue #761)
- Re: [whatwg/url] IPv4 parser "invents" a valid ip from doi prefix; is this / should this be correct behaviour? (Issue #761)
- Re: [whatwg/url] IPv4 parser "invents" a valid ip from doi prefix; is this / should this be correct behaviour? (Issue #761)
- [whatwg/url] IPv4 parser "invents" a valid ip from doi prefix; is this / should this be correct behaviour? (Issue #761)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)
Sunday, 12 March 2023
- [whatwg/encoding] Preface punctuation (Issue #304)
- Re: [whatwg/fetch] Rename "extract-value flag" to "extract-value" and define it as a boolean (Issue #1567)
Saturday, 11 March 2023
- [w3c/IndexedDB] Main (PR #399)
- Re: [whatwg/url] URLSearchParams delete all vs delete one (#335)
- Re: [whatwg/url] javascript: URL parsing (#307)
Friday, 10 March 2023
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819)
- Re: [whatwg/url] More IDNA roundtrippability issues (Issue #760)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [whatwg/url] More IDNA roundtrippability issues (Issue #760)
- Re: [whatwg/url] javascript: URL parsing (#307)
- 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: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- 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: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- [w3c/editing] Behavior of insert* commands for contenteditable=plaintext-only (Issue #419)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [whatwg/url] javascript: URL parsing (#307)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [w3c/gamepad] Move James Hollyer to former editors (PR #185)
- Re: [w3c/gamepad] Move James Hollyer to former editors (PR #185)
Thursday, 9 March 2023
- [w3c/gamepad] Move James Hollyer to former editors (PR #185)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [whatwg/url] More IDNA roundtrippability issues (Issue #760)
- [whatwg/url] More IDNA roundtrippability issues (Issue #760)
- Re: [whatwg/webidl] Seeking clarification on whether unioning promises and callbacks is allowed (Issue #1278)
- Re: [whatwg/webidl] Seeking clarification on whether unioning promises and callbacks is allowed (Issue #1278)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [whatwg/dom] Declarative Shadow DOM (#831)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808)
- Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808)
- Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808)
- Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808)
- Re: [whatwg/url] Double-encoded IDNA labels don't roundtrip (#603)
- [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989)
- Re: [whatwg/url] Double-encoded IDNA labels don't roundtrip (#603)
- [WICG/webcomponents] [custom-elements] Proposal for definition-time validation of dependencies (Issue #988)
- [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [whatwg/webidl] Seeking clarification on whether unioning promises and callbacks is allowed (Issue #1278)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- [whatwg/webidl] Seeking clarification on whether unioning promises and callbacks is allowed (Issue #1278)
- Re: [w3ctag/design-reviews] FileSystemHandle.remove() for the File System Access API (Issue #773)
- Re: [w3ctag/design-reviews] FileSystemHandle.remove() for the File System Access API (Issue #773)
- Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- 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/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
Wednesday, 8 March 2023
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [w3ctag/design-reviews] Spec review for CSS Nesting (Issue #791)
- Re: [whatwg/fullscreen] Consider removing the containing block adjustment for popovers (Issue #218)
- Re: [whatwg/fullscreen] Consider removing the containing block adjustment for popovers (Issue #218)
- Re: [whatwg/fullscreen] Consider removing the containing block adjustment for popovers (Issue #218)
- [whatwg/fullscreen] Consider removing the containing block adjustment for popovers (Issue #218)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- 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: [w3c/editing] Define `contenteditable=plaintext-only` (PR #407)
- Re: [w3c/editing] Define `contenteditable=plaintext-only` (PR #407)
- Re: [w3c/editing] Define `contenteditable=plaintext-only` (PR #407)
- [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618)
- 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: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- 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: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
Tuesday, 7 March 2023
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- 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: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- 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] [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] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969)
- Re: [whatwg/url] Allow queries in relative references when the baseURL has an opaque path (Issue #668)
- Re: [whatwg/url] javascript: URL parsing (#307)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969)
- Re: [whatwg/fullscreen] How :fullscreen CSS pseudo class works in shadow dom? (#149)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969)
- Re: [whatwg/fetch] More informative error types (#526)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [whatwg/fetch] Allow pre-allocating array buffer for .arrayBuffer(), to allow zero-copy loads (Issue #1615)
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)
- Re: [whatwg/url] Allow queries in relative references when the baseURL has an opaque path (Issue #668)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- [whatwg/fetch] WIP: Public subresource check (PR #1617)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- 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: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
Monday, 6 March 2023
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to section 5. (PR #1616)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to section 5. (PR #1616)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969)
- 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)
- [whatwg/fetch] Editorial: add <div algorithm> wrappers to section 5. (PR #1616)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- 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)
- [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- 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: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- 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/url] Allow queries in relative references when the baseURL has an opaque path (Issue #668)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- 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: [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: [w3c/gamepad] Restrict getGamepads() to [SecureContext] (#113)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [whatwg/url] Allow queries in relative references when the baseURL has an opaque path (Issue #668)
- Re: [whatwg/url] Allow queries in relative references when the baseURL has an opaque path (Issue #668)
- Re: [whatwg/fetch] Allow pre-allocating array buffer for .arrayBuffer(), to allow zero-copy loads (Issue #1615)
- [whatwg/fetch] Allow pre-allocating array buffer for .arrayBuffer(), for WebAssembly based parsing with zero copy. (Issue #1615)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [whatwg/url] Allow queries in relative references when the baseURL has an opaque path (Issue #668)
- Re: [whatwg/url] Allow queries in relative references when the baseURL has an opaque path (Issue #668)
- Re: [whatwg/url] URL.canParse() (Issue #713)
- 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/url] [proposal] Enhanced the ability for multiple same-name-parameters to the URLSearchParams: .has() and .delete() (Issue #680)
- Re: [whatwg/url] [proposal] Enhanced the ability for multiple same-name-parameters to the URLSearchParams: .has() and .delete() (Issue #680)
- Re: [whatwg/url] [proposal] Enhanced the ability for multiple same-name-parameters to the URLSearchParams: .has() and .delete() (Issue #680)
- Re: [whatwg/url] Broken references in URL Standard (Issue #759)
- Re: [whatwg/url] Broken references in URL Standard (Issue #759)
- Re: [whatwg/url] URL.canParse() (Issue #713)
- Re: [whatwg/url] Expose a URLHost class to JavaScript (#288)
- Re: [whatwg/url] Allow queries in relative references when the baseURL has an opaque path (Issue #668)
- Re: [whatwg/url] Proposal: file: URL separator deduplication (#552)
- Re: [whatwg/url] URLSearchParams.appendAll(iterable) (#461)
Sunday, 5 March 2023
- Re: [whatwg/url] javascript: URL parsing (#307)
- 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)
- [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614)
- Re: [whatwg/webidl] Reachxdxdxd (Issue #1276)
- [whatwg/webidl] Reachxdxdxd (Issue #1276)
Saturday, 4 March 2023
- [whatwg/fetch] 拿來 (Issue #1613)
- Re: [w3c/editing] JS API to invoke native desktop emoji picker (#350)
Friday, 3 March 2023
- Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343)
- Re: [w3c/IndexedDB] Normalize negative zero (PR #386)
- Re: [w3c/IndexedDB] Initial sketch of manual commit flag for transactions (#331)
- Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280)
- Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334)
- Re: [w3c/IndexedDB] Sketch out IDBCursor.close() (#302)
- Re: [w3c/IndexedDB] Rename 'array key' to 'composite key'. For #360 (PR #392)
- Re: [w3c/IndexedDB] Editorial: Remove redundant ticks from <dfn event> text (PR #398)
- Re: [w3c/IndexedDB] Editorial: Remove redundant ticks from <dfn event> text (PR #398)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [w3c/IndexedDB] Editorial: Remove redundant ticks from <dfn event> text (PR #398)
- [w3c/IndexedDB] Editorial: Remove redundant ticks from <dfn event> text (PR #398)
- Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343)
- Re: [w3c/IndexedDB] Normalize negative zero (PR #386)
- Re: [w3c/IndexedDB] Initial sketch of manual commit flag for transactions (#331)
- Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280)
- Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334)
- Re: [w3c/IndexedDB] Sketch out IDBCursor.close() (#302)
- Re: [w3c/IndexedDB] Rename 'array key' to 'composite key'. For #360 (PR #392)
- Re: [w3c/IndexedDB] Editorial: Replace markup <a type for> syntax with markdown {{...!!type}} (PR #397)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161)
- Re: [w3c/IndexedDB] Editorial: Replace markup <a type for> syntax with markdown {{...!!type}} (PR #397)
- Re: [w3c/IndexedDB] Editorial: Replace markup <a type for> syntax with markdown {{...!!type}} (PR #397)
- [w3c/IndexedDB] Editorial: Replace markup <a type for> syntax with markdown {{...!!type}} (PR #397)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Request class (PR #1612)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Request class (PR #1612)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [w3ctag/design-reviews] Skip no-op service worker fetch handler (Issue #815)
- Re: [w3ctag/design-reviews] Skip no-op service worker fetch handler (Issue #815)
- Re: [whatwg/dom] Dead key symbols not included in KeyboardEvent (#900)
- Re: [whatwg/dom] Dead key symbols not included in KeyboardEvent (#900)
- [w3c/uievents] Dead key symbols not included in KeyboardEvent (Issue #343)
- Re: [whatwg/dom] Dead key symbols not included in KeyboardEvent (#900)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [w3c/uievents] TPAC 2022 status reports (Issue #333)
- Re: [w3c/uievents] Status report and planning for TPAC 2021 (#308)
- Re: [whatwg/dom] Dead key symbols not included in KeyboardEvent (#900)
- Re: [whatwg/dom] Dead key symbols not included in KeyboardEvent (#900)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Request class (PR #1612)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Request class (PR #1612)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- [w3ctag/design-reviews] Early design review request: IPA (Issue #823)
- Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
Thursday, 2 March 2023
- Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [w3c/IndexedDB] Rename 'array key' to 'composite key'. For #360 (PR #392)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161)
- Re: [w3ctag/design-reviews] Multi-Screen Window Placement on the Web - Initiating Multi-Screen Experiences (Issue #767)
- Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79)
- Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [whatwg/webidl] Power (Issue #1274)
- [whatwg/webidl] Power (Issue #1274)
- Re: [w3ctag/design-reviews] Private Network Access (aka CORS-RFC1918) (#572)
- Re: [whatwg/fetch] Give guidance on when flags should be set, for other spec authors (#186)
- Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585)
- Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585)
- Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585)
- Re: [w3c/manifest] Don't recommend extensions use vendor prefixing (Issue #1072)
- Re: [w3c/manifest] Don't recommend extensions use vendor prefixing (Issue #1072)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Request class (PR #1612)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
- Re: [whatwg/url] Parsing square brackets ([]) in path, query, and fragment (#595)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
Wednesday, 1 March 2023
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [whatwg/url] Broken references in URL Standard (Issue #759)
- Re: [w3c/gamepad] Restrict getGamepads() to [SecureContext] (#113)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- [whatwg/url] Broken references in URL Standard (Issue #759)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3c/manifest] Don't recommend extensions use vendor prefixing (Issue #1072)
- Re: [w3c/manifest] Don't recommend extensions use vendor prefixing (Issue #1072)
- [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073)
- Re: [w3c/manifest] Don't recommend extensions use vendor prefixing (Issue #1072)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- Re: [w3c/manifest] Don't recommend extensions use vendor prefixing (Issue #1072)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672)
- [w3c/manifest] Don't recommend extensions use vendor prefixing (Issue #1072)
- Re: [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217)