Saturday, 30 November 2024
- Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975)
- Re: [whatwg/streams] Meta: improve test coverage (PR #1334)
Friday, 29 November 2024
- Re: [whatwg/streams] Meta: improve test coverage (PR #1334)
- [whatwg/streams] Meta: improve test coverage (PR #1334)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/url] invalid-reverse-solidus error definition has character mixed up. (Issue #772)
- Re: [whatwg/url] HISTORY & SECURITY: URL Parsing Differences Between Implementations Security Issues (Issue #766)
- Re: [whatwg/url] HISTORY & SECURITY: URL Parsing Differences Between Implementations Security Issues (Issue #766)
- Re: [whatwg/url] Proposal for new version of parsing spec (Issue #778)
- Re: [whatwg/url] Proposal for new version of parsing spec (Issue #778)
- Re: [whatwg/url] Enforce UTF-8 when url is given to the basic URL parser (Issue #783)
- Re: [whatwg/url] "valid domain" does not match validation errors in the host parser (Issue #797)
- Re: [whatwg/url] Should we escape \ in non-special non-opaque paths? (Issue #675)
- Re: [whatwg/url] Should we escape \ in non-special non-opaque paths? (Issue #675)
- Re: [whatwg/url] Request for review: URLPattern (#635)
- Re: [whatwg/url] Request for review: URLPattern (#635)
- Re: [whatwg/url] Issues with UTS #46 tests (#341)
- Re: [whatwg/url] Issues with UTS #46 tests (#341)
- Re: [whatwg/url] Hoist "forbidden domain code point" check into "domain to ASCII" (Issue #818)
- Re: [whatwg/url] Editorial: check forbidden domain code points in domain to ASCII (PR #841)
- Re: [whatwg/url] Editorial: check forbidden domain code points in domain to ASCII (PR #841)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [whatwg/url] Set IDNA's IgnoreInvalidPunycode to false (PR #843)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [whatwg/url] Set IDNA's IgnoreInvalidPunycode to false (PR #843)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [whatwg/url] More IDNA roundtrippability issues (Issue #760)
- Re: [whatwg/url] More IDNA roundtrippability issues (Issue #760)
- Re: [whatwg/url] IdnaTestV2.json "xn--xn--a--gua.pt" test case problem (Issue #803)
- Re: [whatwg/url] IdnaTestV2.json "xn--xn--a--gua.pt" test case problem (Issue #803)
- [whatwg/url] Set IDNA's IgnoreInvalidPunycode to false (PR #843)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [whatwg/url] Encourage denoting character-attributable errors by the REPLACEMENT CHARACTER (Issue #819)
- Re: [whatwg/url] CheckHyphens isn't set to beStrict (Issue #820)
- Re: [whatwg/url] CheckHyphens isn't set to beStrict (Issue #820)
- Re: [whatwg/url] Set IDNA's CheckHyphens to the value of beStrict (PR #842)
- Re: [whatwg/url] Encourage denoting character-attributable errors by the REPLACEMENT CHARACTER (Issue #819)
- Re: [whatwg/url] Encourage denoting character-attributable errors by the REPLACEMENT CHARACTER (Issue #819)
- Re: [whatwg/url] Set IDNA's CheckHyphens to the value of beStrict (PR #842)
- Re: [whatwg/url] Explain why valid domain needs to run ToUnicode (Issue #817)
- Re: [whatwg/url] Explain why valid domain needs to run ToUnicode (Issue #817)
- Re: [whatwg/url] Explain why valid domain needs to run ToUnicode (Issue #817)
- Re: [whatwg/url] Remove redundant domain to Unicode call from valid domain (PR #840)
- [whatwg/url] Set IDNA's CheckHyphens to the value of beStrict (PR #842)
- Re: [whatwg/url] Remove redundant domain to Unicode call from valid domain (PR #840)
- Re: [whatwg/url] Encourage denoting character-attributable errors by the REPLACEMENT CHARACTER (Issue #819)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/url] Hoist "forbidden domain code point" check into "domain to ASCII" (Issue #818)
- Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326)
- [whatwg/url] Editorial: check forbidden domain code points in domain to ASCII (PR #841)
- Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326)
- Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326)
- Re: [whatwg/url] Explain why valid domain needs to run ToUnicode (Issue #817)
- [whatwg/url] Remove redundant domain to Unicode call from valid domain (PR #840)
- Re: [whatwg/url] Update to Unicode 16.0.0 (Issue #836)
- Re: [whatwg/url] Clearly mark conformance checking-only aspects of the IDNA section (Issue #816)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- [w3c/uievents] Mandate a minimum dispatch frequency for continuous UI input events (Issue #389)
Thursday, 28 November 2024
- [w3c/pointerlock] Allow applications to access higher-precision mouse movement data (Issue #102)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- [w3c/ServiceWorker] Feedback on the ServiceWorker feature in the web-platform-dx/web-features project (Issue #1738)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [WICG/webcomponents] Reference Target naming (Issue #1087)
- Re: [WICG/webcomponents] Reference Target naming (Issue #1087)
- Re: [WICG/webcomponents] Reference Target Tracking Issue (Issue #1086)
- Re: [WICG/webcomponents] Reference Target naming (Issue #1087)
- Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326)
- [WICG/webcomponents] Reference Target naming (Issue #1087)
Wednesday, 27 November 2024
- Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975)
- Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326)
- Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326)
- Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Should a Range object be able to update a Selection object (#772)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [w3ctag/design-reviews] DOM state-preserving move (Issue #976)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [w3ctag/design-reviews] [Handwriting] Add Handwriting CSS Value (Issue #1018)
- [w3c/editing] Add mechanism to control enablement of handwriting (Issue #472)
- [w3c/clipboard-apis] Add privacy considerations for the clipboardchange event (Issue #230)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975)
- Re: [whatwg/dom] Use the principal realm to initialize Event.timeStamp (PR #1329)
- Re: [WICG/webcomponents] Reference Target: How to handle invalid ID references? (Issue #1071)
- [whatwg/dom] Use the principal realm to initialize Event.timeStamp (PR #1329)
- Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/streams] `.throw()`ing an async iterator (Issue #1284)
- Re: [whatwg/streams] `.throw()`ing an async iterator (Issue #1284)
- Re: [whatwg/streams] Commit pull-into descriptors after filling from queue (PR #1326)
- Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331)
- Re: [whatwg/streams] Fix attempting to get the chunk size after strategy is cleared (PR #1333)
- Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975)
- Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975)
- Re: [WICG/webcomponents] Reference Target Tracking Issue (Issue #1086)
- Re: [WICG/webcomponents] Reference Target Tracking Issue (Issue #1086)
- Re: [WICG/webcomponents] Reference Target: How to handle invalid ID references? (Issue #1071)
- [WICG/webcomponents] Reference Target Tracking Issue (Issue #1086)
Tuesday, 26 November 2024
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)
- Re: [whatwg/fetch] Define HSTS as "internal" redirect (Issue #1426)
- [whatwg/fetch] HTTPS-RR upgrades are in the wrong place (Issue #1789)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015)
- Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- [w3ctag/design-reviews] CSP report-hash directive (Issue #1020)
- Re: [whatwg/url] Proposal: Functional chaining on URLSearchParams (Issue #756)
- Re: [whatwg/url] Proposal: Functional chaining on URLSearchParams (Issue #756)
- Re: [whatwg/streams] Fix attempting to get the chunk size after strategy is cleared (PR #1333)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/url] "IPv6 serializer" does not define an algorithm for longest sequence of IPv6 pieces that are 0 (#321)
- Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
- [whatwg/url] Formal IPv6 address definition (Issue #839)
- [whatwg/streams] Fix attempting to get the chunk size after strategy is cleared (PR #1333)
- Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331)
- Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
- [w3ctag/design-reviews] Normative Changes of the Input Events Level 2 (Issue #1019)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/webidl] 0327482776 (Issue #1453)
- Re: [whatwg/url] Update to Unicode 16.0.0 (Issue #836)
- Re: [w3ctag/design-reviews] [Handwriting] Add Handwriting CSS Value (Issue #1018)
Monday, 25 November 2024
- Re: [whatwg/webidl] 0327482776 (Issue #1453)
- Re: [whatwg/webidl] 0327482776 (Issue #1453)
- Re: [whatwg/webidl] 0327482776 (Issue #1453)
- Re: [whatwg/webidl] 0327482776 (Issue #1453)
- Re: [whatwg/webidl] 0327482776 (Issue #1453)
- [whatwg/webidl] 0327482776 (Issue #1453)
- Re: [w3ctag/design-reviews] [Handwriting] Add Handwriting CSS Value (Issue #1018)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [w3ctag/design-reviews] [Handwriting] Add Handwriting CSS Value (Issue #1018)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/url] Update to Unicode 16.0.0 (Issue #836)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Missing machinery for associated Event data (Issue #1328)
- [whatwg/dom] Missing machinery for associated Event data (Issue #1328)
- Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
- [w3ctag/design-reviews] [Handwriting] Add Handwriting CSS Value (Issue #1018)
- Re: [w3ctag/design-reviews] Accessibility conformance Testing (ACT) Rules Format 1.1 (Issue #977)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- Re: [whatwg/dom] Should a Range object be able to update a Selection object (#772)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [w3c/push-api] Meta: address xref issue (PR #394)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [w3c/push-api] Meta: address xref issue (PR #394)
- Re: [w3c/push-api] Meta: address xref issue (PR #394)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
Sunday, 24 November 2024
- Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
Saturday, 23 November 2024
- Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224)
- Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
- Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
Friday, 22 November 2024
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [w3ctag/design-reviews] Vision for W3C: request horizontal architectural review and wide TAG review (Issue #1008)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/streams] Shouldn't WritableStreamDefaultWriter.write() reject if underlyingSink.write calls controller.error()? (Issue #1332)
- Re: [whatwg/streams] Shouldn't WritableStreamDefaultWriter.write() reject if underlyingSink.write calls controller.error()? (Issue #1332)
- Re: [w3c/editing] Should we propose "::caret" pseudo-element to CSS WG? (#158)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [w3c/FileAPI] Update auto-publish.yml (PR #204)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- [w3c/FileAPI] Update auto-publish.yml (PR #204)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [whatwg/dom] Trusted types attributes (PR #1268)
- Re: [WICG/webcomponents] Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements (Issue #1073)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [w3c/manifest] Link incubations (PR #1153)
- Re: [w3c/manifest] Link incubations (PR #1153)
- Re: [whatwg/dom] Selecting Events with Style (Issue #1233)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/streams] Shouldn't WritableStreamDefaultWriter.write() reject if underlyingSink.write calls controller.error()? (Issue #1332)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
- Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- Re: [w3ctag/design-reviews] Early Design Review: Partitioned Popins (Issue #956)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- [w3ctag/design-reviews] ClipboardChange event API (Issue #1017)
Thursday, 21 November 2024
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338)
- Re: [w3c/manifest] Link incubations (PR #1153)
- Re: [w3c/manifest] Link incubations (PR #1153)
- Re: [w3c/manifest] Link incubations (PR #1153)
- Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- [whatwg/streams] Shouldn't WritableStreamDefaultWriter.write() reject if underlyingSink.write calls controller.error()? (Issue #1332)
- Re: [w3ctag/design-reviews] DOM state-preserving move (Issue #976)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [WICG/webcomponents] Update reference-target-explainer supported attributes (PR #1084)
- Re: [whatwg/dom] Should a Range object be able to update a Selection object (#772)
- Re: [WICG/webcomponents] Update reference-target-explainer supported attributes (PR #1084)
- [WICG/webcomponents] Update reference-target-explainer supported attributes (PR #1084)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3ctag/design-reviews] Review for Protected Audiences Bidding and Auction Services API (Issue #1009)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [w3ctag/design-reviews] CSS reading-flow property (Issue #978)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- [WICG/webcomponents] 2025 Q1 Face-to-face (Issue #1083)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
- Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287)
- Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003)
- Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331)
- Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [w3c/uievents-key] The link to [WEB4CE] is unavailable (Issue #69)
- Re: [w3c/uievents-key] The link to [WEB4CE] is unavailable (Issue #69)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [scoped-registries] CustomElementRegistry to support SDLC of generic browser entities (Issue #976)
- Re: [WICG/webcomponents] [scoped-registries] CustomElementRegistry to support SDLC of generic browser entities (Issue #976)
- Re: [WICG/webcomponents] [scoped-registries] Moving elements with shadow roots between documents (#907)
- Re: [WICG/webcomponents] [scoped-registries] Moving elements with shadow roots between documents (#907)
- Re: [WICG/webcomponents] [scoped-registries] How does customElements.upgrade() work? (Issue #1001)
- Re: [WICG/webcomponents] [scoped-registries] How does customElements.upgrade() work? (Issue #1001)
- Re: [WICG/webcomponents] Idea: Alternative Ways to Control Registry Scoping (Issue #1058)
- Re: [WICG/webcomponents] Idea: Alternative Ways to Control Registry Scoping (Issue #1058)
- Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040)
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
Wednesday, 20 November 2024
- Re: [w3ctag/design-reviews] Web Install API - Cross-Origin (Issue #946)
- Re: [w3ctag/design-reviews] Web Install API - Cross-Origin (Issue #946)
- Re: [w3ctag/design-reviews] Review for Protected Audiences Bidding and Auction Services API (Issue #1009)
- Re: [w3ctag/design-reviews] Review for Protected Audiences Bidding and Auction Services API (Issue #1009)
- Re: [w3ctag/design-reviews] Customizable select element (Issue #1007)
- Re: [w3ctag/design-reviews] Customizable select element (Issue #1007)
- Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003)
- Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003)
- Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/fetch] Safelist Last-Event-ID (#568)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [w3ctag/design-reviews] CSS reading-flow property (Issue #978)
- Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- [w3ctag/design-reviews] FYI - Web Authentication API: PublicKeyCredential’s getClientCapabilities() method (Issue #1016)
- Re: [whatwg/dom] Browsers don't throw when using replaceChild() to replace existing doctype (Issue #1327)
- Re: [whatwg/dom] Browsers don't throw when using replaceChild() to replace existing doctype (Issue #1327)
- [whatwg/dom] Browsers don't throw when using replaceChild() to replace existing doctype (Issue #1327)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Safelist Last-Event-ID (#568)
- Re: [whatwg/webidl] Editorial: define boolean and integer types in terms of Infra (PR #1452)
- Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight for navigations (PR #1785)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785)
- Re: [w3c/selection-api] Throw correct exceptions from collapse/selectAllChildren on detached doctypes (#86)
- Re: [w3c/selection-api] Throw correct exceptions from collapse/selectAllChildren on detached doctypes (#86)
- Re: [w3c/selection-api] Tidied up document using tidy-html5 (PR #340)
- Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342)
- Re: [w3c/selection-api] Throw InvalidNodeTypeError on DocumentType nodes (#118)
- Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342)
- Re: [whatwg/fetch] Safelist Last-Event-ID (#568)
- Re: [whatwg/webidl] Editorial: define boolean and integer types in terms of Infra (PR #1452)
- Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
Tuesday, 19 November 2024
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [whatwg/fetch] Safelist Last-Event-ID (#568)
- Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785)
- Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785)
- Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
- Re: [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788)
- Re: [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- [whatwg/webidl] Editorial: define boolean and integer types in terms of Infra (PR #1452)
- Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551)
- Re: [w3c/push-api] Expose pushManager on Window (PR #393)
- Re: [w3c/push-api] Meta: address xref issue (PR #394)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Meta: address xref issue (PR #394)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342)
- [w3c/push-api] Meta: address xref issue (PR #394)
- Re: [w3c/push-api] Expose pushManager on Window (PR #393)
- [w3c/push-api] Expose pushManager on Window (PR #393)
- Re: [w3c/push-api] Expose pushManager on Navigator (PR #368)
- Re: [w3c/push-api] Expose pushManager on Navigator (PR #368)
- Re: [w3ctag/design-reviews] Element Capture (Issue #954)
- Re: [w3ctag/design-reviews] Element Capture (Issue #954)
- Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
- Re: [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
- Re: [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788)
- Re: [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788)
- Re: [whatwg/dom] Improve readability. maybe.. (PR #1326)
- Re: [whatwg/dom] Improve readability. maybe.. (PR #1326)
- Re: [whatwg/dom] Improve readability. maybe.. (PR #1326)
- Re: [whatwg/fetch] Editorial: make JSON parsing wording match Infra spec (PR #1787)
- Re: [whatwg/fetch] Editorial: make JSON parsing wording match Infra spec (PR #1787)
- Re: [whatwg/dom] Improve readability. maybe.. (PR #1326)
- Re: [whatwg/dom] Improve readability. maybe.. (PR #1326)
- Re: [whatwg/dom] Improve readability. maybe.. (PR #1326)
- Re: [whatwg/fetch] Editorial: make JSON parsing wording match Infra spec (PR #1787)
- Re: [whatwg/dom] Improve readability. maybe.. (PR #1326)
- Re: [whatwg/dom] Editorial: break from the inner invoke loop rather than returning (PR #1325)
- [whatwg/fetch] Add `Last-Event-ID` to CORS-safelisted request headers (PR #1788)
- [whatwg/fetch] Editorial: make JSON parsing wording match Infra spec (PR #1787)
- Re: [whatwg/dom] Editorial: break from the inner invoke loop rather than returning (PR #1325)
- [whatwg/dom] Improve readability. maybe.. (PR #1326)
Monday, 18 November 2024
- Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)
- Re: [w3c/push-api] Expose pushManager on Navigator (PR #368)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- [whatwg/url] Editorial: adopt Infra number definitions (and redo IPv6 pieces) (PR #838)
- [whatwg/dom] Editorial: break from the inner invoke loop rather than returning (PR #1325)
- Re: [whatwg/dom] "inner invoke" of event listener with "once" doesn't mark listener as "removed" (Issue #1323)
- Re: [whatwg/dom] Correct once handling for "nested" events (PR #1324)
- Re: [whatwg/dom] Correct once handling for "nested" events (PR #1324)
- Re: [whatwg/dom] Correct once handling for "nested" events (PR #1324)
- Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342)
- [whatwg/dom] Correct once handling for "nested" events (PR #1324)
- Re: [whatwg/dom] "inner invoke" of event listener with "once" doesn't mark listener as "removed" (Issue #1323)
- Re: [whatwg/dom] "inner invoke" of event listener with "once" doesn't mark listener as "removed" (Issue #1323)
- Re: [whatwg/fetch] Safelist Last-Event-ID (#568)
- Re: [whatwg/dom] "inner invoke" of event listener with "once" doesn't mark listener as "removed" (Issue #1323)
- Re: [w3c/uievents] Replace Window with WindowProxy in IDL throughout? (Issue #388)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
Sunday, 17 November 2024
- [w3c/uievents] Replace Window with WindowProxy in IDL throughout? (Issue #388)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [w3c/ServiceWorker] No idea. I think we should remove that restriction. (Issue #1737)
- Re: [w3c/ServiceWorker] No idea. I think we should remove that restriction. (Issue #1737)
- [w3c/ServiceWorker] No idea. I think we should remove that restriction. (Issue #1737)
- [whatwg/dom] "inner invoke" of event listener with "once" doesn't mark listener as "removed" (Issue #1323)
Saturday, 16 November 2024
- Re: [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342)
- Re: [w3ctag/design-reviews] Controller Documents v1.0 (Issue #960)
- [w3c/selection-api] Throw InvalidNodeTypeError for doctype more eagerly (PR #342)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [whatwg/fetch] Safelist Last-Event-ID (#568)
Friday, 15 November 2024
- Re: [whatwg/webidl] Update to HTML changes for ShadowRealms (PR #1437)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- [w3ctag/design-reviews] Payment link type in HTML (Issue #1015)
Thursday, 14 November 2024
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198)
- Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468)
- Re: [whatwg/fetch] HTTP/2 and Content-Length (Issue #1786)
- Re: [w3ctag/design-reviews] CSS advanced attr() function (#513)
- Re: [w3ctag/design-reviews] CSS advanced attr() function (#513)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [w3c/ServiceWorker] > Wanted to start adding the changed/added guidelines, SC and sections to a list here to help the AG WG know what sections are ready to review. This will be a draft PR until we are ready to send the document to the AG WG for their first review. See [Issue #65]. (Issue #1736)
- [w3c/ServiceWorker] > Wanted to start adding the changed/added guidelines, SC and sections to a list here to help the AG WG know what sections are ready to review. This will be a draft PR until we are ready to send the document to the AG WG for their first review. See [Issue #65]. (Issue #1736)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- [whatwg/fetch] HTTP/2 and Content-Length (Issue #1786)
- [w3c/uievents-key] The link to [WEB4CE] is unavailable (Issue #69)
- Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338)
- Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994)
- Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994)
- Re: [w3ctag/design-reviews] Element Capture (Issue #954)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)
- Re: [w3c/manifest] Clarification needed for document URL (Issue #1147)
- Re: [w3c/manifest] Clarification needed for document URL (Issue #1147)
- [w3ctag/design-reviews] Document-Policy: expect-no-linked-resources (Issue #1014)
- Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338)
Wednesday, 13 November 2024
- Re: [whatwg/fetch] Can the set of safelisted methods be extended? (Issue #1774)
- Re: [w3ctag/design-reviews] Web Authentication's PublicKeyCredential signal methods (Issue #996)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
- Re: [w3c/push-api] Declarative Web Push (Issue #360)
- Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
- Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784)
- Re: [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331)
- [w3c/manifest] Link incubations (PR #1153)
- Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784)
- Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338)
- Re: [w3ctag/design-reviews] Web Authentication's PublicKeyCredential signal methods (Issue #996)
- Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338)
- Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338)
- Re: [w3ctag/design-reviews] Early review request for "Explicit JavaScript Compile Hints" (Issue #947)
- Re: [w3ctag/design-reviews] Early review request for "Explicit JavaScript Compile Hints" (Issue #947)
- Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)
- Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338)
- Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785)
- Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785)
- Re: [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338)
- [whatwg/encoding] 0xA3 0xA0 in GB 18030 (Issue #338)
- Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994)
- Re: [w3ctag/design-reviews] CSS :open pseudo-class (Issue #1010)
- Re: [w3ctag/design-reviews] CSS :open pseudo-class (Issue #1010)
Tuesday, 12 November 2024
- Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994)
- Re: [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011)
- Re: [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
- Re: [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785)
- Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [w3c/push-api] "a service worker registration has at most one push subscription" seems wrong (Issue #392)
- [w3c/push-api] "a service worker registration has at most one push subscription" seems wrong (Issue #392)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- [w3ctag/design-reviews] Paint/presentation timestamps in performance APIs (Issue #1013)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [whatwg/webidl] Enumeration Emulator (Issue #1450)
- [whatwg/webidl] Enumeration Emulator (Issue #1450)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [WICG/webcomponents] Why can't the registry enumerate the custom elements? (#775)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
Monday, 11 November 2024
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [w3ctag/design-reviews] Early Design Review: Partitioned Popins (Issue #956)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- [whatwg/fetch] Allow HTTP scheme fetches to make CORS preflight (PR #1785)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
Sunday, 10 November 2024
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [WICG/webcomponents] Clonning shadowroot , example : element.cloneNode({ deep: true, includeShadowDOM: true }); (Issue #1082)
- Re: [WICG/webcomponents] Clonning shadowroot , example : element.cloneNode({ deep: true, includeShadowDOM: true }); (Issue #1082)
Saturday, 9 November 2024
- [WICG/webcomponents] Clonning shadowroot , example : element.cloneNode({ deep: true, includeShadowDOM: true }); (Issue #1082)
- Re: [whatwg/fetch] SSTTATUS (Issue #1784)
- Re: [whatwg/url] metro (Issue #837)
- Re: [whatwg/webidl] MP4Box (Issue #1449)
- Re: [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011)
- [whatwg/fetch] SSTTATUS (Issue #1784)
- [whatwg/url] metro (Issue #837)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- [whatwg/streams] Abort followed by write on WritableStream may invoke a null strategy algorithm (Issue #1331)
- [whatwg/webidl] MP4Box (Issue #1449)
- Re: [w3c/manifest] Clarification needed for document URL (Issue #1147)
Friday, 8 November 2024
- Re: [w3c/IndexedDB] Return explicit failure from object store retrieval operations (Issue #432)
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
- Re: [w3c/manifest] Manifest processing should not be a function of document URL (#668)
- Re: [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011)
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
- Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734)
- Re: [whatwg/streams] define semantics of {source,sink}.finally() (#636)
- Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734)
Thursday, 7 November 2024
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- [w3c/IndexedDB] Return explicit failure from object store retrieval operations (Issue #432)
- Re: [whatwg/webidl] https://code.google.com (Issue #1448)
- [whatwg/webidl] https://code.google.com (Issue #1448)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784)
- Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784)
- Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784)
- Re: [w3c/manifest] Require document to be in scope to be styled by the manifest (#791)
- Re: [w3c/manifest] Require document to be in scope to be styled by the manifest (#791)
- Re: [w3c/manifest] First pass as adding a Client Hint for Display Mode (#977)
- Re: [w3c/manifest] First pass as adding a Client Hint for Display Mode (#977)
- Re: [w3c/manifest] Add protocol handlers to the explainer and spec (#863)
- Re: [w3c/manifest] Add protocol handlers to the explainer and spec (#863)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] What theme color should be used when a PWA window is out of scope? (#755)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
- Re: [w3c/manifest] Clarify case-insensitive parsing for enum values (Issue #1142)
- Re: [w3c/manifest] Make enums case-insensitive (PR #1149)
- Re: [w3c/manifest] Make enums case-insensitive (PR #1149)
- Re: [w3c/manifest] related_applications is single engine feature (#956)
- Re: [w3c/manifest] prefer_related_applications is single engine feature (#957)
- Re: [w3c/manifest] Move `prefer_related_applications` and `related_applications` to manifest incubation (PR #1152)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3c/manifest] Move `prefer_related_applications` and `related_applications` to manifest incubation (PR #1152)
- Re: [w3c/manifest] Make enums case-insensitive (PR #1149)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203)
Wednesday, 6 November 2024
- Re: [w3ctag/design-reviews] CSS reading-flow property (Issue #978)
- Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203)
- Re: [w3ctag/design-reviews] CSS reading-flow property (Issue #978)
- Re: [w3ctag/design-reviews] CSS reading-flow property (Issue #978)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- [w3ctag/design-reviews] User-defined script "entry points" for performance timing (Issue #1012)
- [whatwg/dom] Define iteration order of inclusive ancestors in "remove" (Issue #1322)
- Re: [whatwg/dom] Integration with trusted types inside of node conversion (PR #1258)
Tuesday, 5 November 2024
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320)
- Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321)
- Re: [w3c/manifest] Clarification needed for document URL (Issue #1147)
- Re: [w3c/selection-api] Selection.toString is under specified (#7)
- Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3c/push-api] Add Declarative Web Push (PR #385)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011)
- Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320)
- Re: [w3c/uievents-key] CFC to publish UI Events KeyboardEvent key Values as a Proposed Recommendation in the WebApps WG (Issue #68)
- Re: [w3c/uievents-key] CFC to publish UI Events KeyboardEvent key Values as a Proposed Recommendation in the WebApps WG (Issue #68)
- Re: [w3c/uievents-code] CFC to publish UI Events KeyboardEvent code Values as a Proposed Recommendation in the WebApps WG (Issue #43)
- Re: [w3c/uievents-code] CFC to publish UI Events KeyboardEvent code Values as a Proposed Recommendation in the WebApps WG (Issue #43)
- Re: [whatwg/fetch] Exclude localhost from HTTPS upgrades (Issue #1780)
- Re: [whatwg/fetch] Exclude localhost from HTTPS upgrades (Issue #1780)
- Re: [whatwg/fetch] Skip localhost when evaluating HSTS upgrades (PR #1781)
- Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003)
- Re: [w3c/ServiceWorker] Expose the Fetch Metadata Request Headers (#1513)
- Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206)
- Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206)
Monday, 4 November 2024
- Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206)
- Re: [w3c/ServiceWorker] active service worker should be reset for same-origin redirects during navigation (Issue #1735)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- [w3c/ServiceWorker] active service worker should be reset for same-origin redirects during navigation (Issue #1735)
- Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
- Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)
- Re: [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734)
- Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607)
- Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
- [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734)
- Re: [whatwg/storage] StorageEstimate.quota + Storage Pressure (#73)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321)
- Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203)
- Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321)
- Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
- Re: [w3ctag/design-reviews] Review for Protected Audiences Bidding and Auction Services API (Issue #1009)
- Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412)
Sunday, 3 November 2024
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)
- Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321)
- Re: [whatwg/xhr] `FormData` `has()` should include a second param for matching the value like `URLSearchParams` (Issue #392)
Saturday, 2 November 2024
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- [whatwg/xhr] `FormData` `has()` should include a second param for matching the value like `URLSearchParams` (Issue #392)
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
Friday, 1 November 2024
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
- Re: [w3c/manifest] related_applications is single engine feature (#956)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3c/manifest] related_applications is single engine feature (#956)
- [w3c/manifest] Move `prefer_related_applications` and `related_applications` to manifest incubation (PR #1152)
- Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000)
- Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)