Sunday, 30 April 2023
- Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- Re: [whatwg/webidl] Detect whether a dictionary member was set by default or not (Issue #1300)
- Re: [whatwg/url] Add URL.canParse() (ae3c28b)
- [whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645)
Friday, 28 April 2023
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [whatwg/dom] Attribute change steps should run after setting the value, not before (Issue #1190)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- [whatwg/fetch] Why does the Fetch standard forbid GET Body when it's not against REST? (Issue #1644)
- 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: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250)
- Re: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250)
- Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
- Re: [whatwg/dom] Proposal: A new way to do feature detection for members (Issue #1181)
- Re: [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183)
- Re: [whatwg/dom] Proposal: A new way to do feature detection for members (Issue #1181)
- Re: [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183)
- 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/fetch] Editorial: use "pull from bytes" algorithm (4502481)
- Re: [whatwg/fetch] Editorial: use "pull from bytes" algorithm (4502481)
- Re: [whatwg/fetch] Proposal: `Viewport` header for early hints (Issue #1640)
- Re: [whatwg/fetch] Proposal: `Viewport` header for early hints (Issue #1640)
- Re: [whatwg/fetch] Specify how/if response status code & content type are exposed for cross-origin navigations (Issue #1602)
- Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628)
- Re: [whatwg/fetch] The fetch pull algorithm does not pass proper bytesWritten to ReadableByteStreamControllerRespond (Issue #1610)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add before removing steps (PR #1185)
- Re: [whatwg/dom] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #1189)
- Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184)
- Re: [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183)
- Re: [whatwg/dom] Proposal: A new way to do feature detection for members (Issue #1181)
- Re: [whatwg/webidl] Detect whether a dictionary member was set by default or not (Issue #1300)
- [whatwg/webidl] Detect whether a dictionary member was set by default or not (Issue #1300)
- Re: [whatwg/webidl] Editorial: Fix typo in the overload resolution algorithm (PR #1299)
- Re: [whatwg/webidl] Editorial: Fix typo in the overload resolution algorithm (PR #1299)
- [whatwg/webidl] Editorial: Fix typo in the overload resolution algorithm (PR #1299)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
Thursday, 27 April 2023
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- Re: [whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [w3ctag/design-reviews] Review of IMSC-HRM (Issue #788)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [w3ctag/design-reviews] WebRTC-SVC (Scalable Video Coding) (Issue #837)
- Re: [whatwg/fetch] Access-Control-Max-Age not effective in preflight request caching when Authorization header is programatically defined (#1278)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- [whatwg/fetch] A (Issue #1643)
- Re: [whatwg/fetch] R (Issue #1642)
- [whatwg/fetch] R (Issue #1642)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] [meta] Don't require merge queue for PRs (Issue #1075)
- Re: [w3c/manifest] [meta] Don't require merge queue for PRs (Issue #1075)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [whatwg/webidl] ByteString text should not talk about UTF-8 (Issue #1295)
- Re: [whatwg/webidl] ByteString text should not talk about UTF-8 (Issue #1295)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
Wednesday, 26 April 2023
- Re: [w3c/manifest] Ran tidy. (PR #1076)
- Re: [whatwg/fetch] Access-Control-Max-Age not effective in preflight request caching when Authorization header is programatically defined (#1278)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [w3ctag/design-reviews] WebRTC-SVC (Scalable Video Coding) (Issue #837)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [w3ctag/design-reviews] WebRTC-SVC (Scalable Video Coding) (Issue #837)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [w3c/manifest] Ran tidy. (PR #1076)
- Re: [w3c/manifest] Ran tidy. (PR #1076)
- Re: [w3c/manifest] Ran tidy. (PR #1076)
- [w3ctag/design-reviews] FedCM: LoginHint, UserInfo, and RPContext (Issue #839)
- Re: [w3c/manifest] Ran tidy. (PR #1076)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [whatwg/fetch] Consider shifting the "bad port list" to an allowlist. (#1189)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [w3ctag/design-reviews] WebRTC-SVC (Scalable Video Coding) (Issue #837)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [whatwg/webidl] Editorial: remove remaining UTF-8 and UTF-16 references (PR #1298)
- Re: [whatwg/webidl] Editorial: remove remaining UTF-8 and UTF-16 references (PR #1298)
- [whatwg/webidl] Editorial: remove remaining UTF-8 and UTF-16 references (PR #1298)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Ran tidy. (PR #1076)
- Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [w3c/screen-orientation] Should we standardize window.orientation? (Issue #249)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [w3c/manifest] [meta] Don't require merge queue for PRs (Issue #1075)
- Re: [w3c/manifest] Ran tidy. (PR #1076)
- Re: [w3c/manifest] Ran tidy. (PR #1076)
- Re: [whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191)
- Re: [w3c/manifest] Ran tidy. (PR #1076)
- Re: [w3c/manifest] Ran tidy. (PR #1076)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Ran tidy. (PR #1076)
- Re: [whatwg/webidl] Intent to use Constants (Issue #1297)
- Re: [whatwg/webidl] Intent to use Constants (Issue #1297)
- [whatwg/webidl] Intent to use Constants (Issue #1297)
- Re: [whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191)
- [w3c/manifest] Ran tidy. (PR #1076)
Tuesday, 25 April 2023
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- [whatwg/dom] Introducing Direct Navigation to Client-Side JavaScript-Generated HTML Documents (Issue #1192)
- [WICG/webcomponents] [declarate-custom-elements] Capabilities needed and open questions (Issue #1009)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- [w3ctag/design-reviews] Specification review for fenced frames (Issue #838)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- [w3ctag/design-reviews] WebRTC-SVC (Scalable Video Coding) (Issue #837)
- Re: [whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191)
- Re: [whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191)
- [whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191)
- [WICG/webcomponents] Introducing Direct Navigation to Client-Side JavaScript-Generated HTML Documents (Issue #1008)
- Re: [whatwg/fetch] Editorial: update args for collect an HTTP quoted string (PR #1641)
- [whatwg/fetch] Editorial: update args for collect an HTTP quoted string (PR #1641)
Monday, 24 April 2023
- Re: [whatwg/fetch] Authorization-removal change was compatibility-breaking (Issue #1631)
- Re: [whatwg/dom] Add before removing steps (PR #1185)
- Re: [w3ctag/design-reviews] WebAssembly Garbage Collection extensions (Issue #814)
- Re: [w3c/manifest] Manifest: property 'src' ignored, URL is invalid. (Issue #1059)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915)
- [w3ctag/design-reviews] WebRTC Codec selection API (Issue #836)
- Re: [w3ctag/design-reviews] Two changes to Secure Payment Confirmation prior to CR (Issue #802)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [whatwg/dom] Attribute change steps should run after setting the value, not before (Issue #1190)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [whatwg/dom] Add before removing steps (PR #1185)
- Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248)
- Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795)
- Re: [whatwg/dom] Disconnect single target instead of all (#126)
- Re: [whatwg/dom] Disconnect single target instead of all (#126)
- [whatwg/dom] Attribute change steps should run after setting the value, not before (Issue #1190)
- Re: [whatwg/webidl] Normative: Match ECMA‑262 function property enumeration order (#914)
- Re: [WICG/webcomponents] Cascading Style Sheet module scripts (#759)
- Re: [whatwg/webidl] Normative: Match ECMA‑262 function property enumeration order (#914)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] HTTP-redirect does not call processResponse and breaks navigation expectations (Issue #1629)
- Re: [whatwg/fetch] Pass recursive=false to manual navigation redirect (PR #1638)
- Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638)
- Re: [whatwg/fetch] Authorization-removal change was compatibility-breaking (Issue #1631)
- Re: [whatwg/fetch] Proposal: `Viewport` header for early hints (Issue #1640)
- [whatwg/fetch] Proposal: `Viewport` header for early hints (Issue #1640)
- Re: [whatwg/fetch] Authorization-removal change was compatibility-breaking (Issue #1631)
- Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638)
- Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638)
- Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620)
- Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638)
- Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638)
- Re: [whatwg/dom] Disconnect single target instead of all (#126)
- Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638)
- Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] [meta] Don't require merge queue for PRs (Issue #1075)
- [w3c/manifest] [meta] Don't require merge queue for PRs (Issue #1075)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
Sunday, 23 April 2023
- Re: [whatwg/streams] Synchronous WritableStream Writer to avoid heap allocations from Promises returned by WritableStreamDefaultWriter's write (Issue #1276)
- Re: [whatwg/dom] Disconnect single target instead of all (#126)
- [whatwg/webidl] Improperly pluralized verb in "The [LegacyNamespace] extended attribute take an identifier" (Issue #1296)
- Re: [WICG/webcomponents] Cascading Style Sheet module scripts (#759)
- [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638)
- Re: [w3ctag/design-reviews] Shared Storage API (Issue #747)
Saturday, 22 April 2023
- [whatwg/dom] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #1189)
- Re: [whatwg/webidl] Normative: Match ECMA‑262 function property enumeration order (#914)
- Re: [whatwg/webidl] Normative: Match ECMA‑262 function property enumeration order (#914)
- Re: [whatwg/webidl] Revamp ByteString, DOMString, and USVString (#335)
- Re: [whatwg/webidl] Revamp ByteString, DOMString, and USVString (#335)
- Re: [whatwg/webidl] تم ايقاف الخط للاتصالات والمكالمات والرسائل النصية القصيرة SMS01128336635 ارجو المساعده (Issue #1294)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- Re: [w3c/selection-api] toString should return the selected text in input / textarea element (Issue #165)
- [w3c/selection-api] toString should return the selected text in input / textarea element (Issue #165)
Friday, 21 April 2023
- [w3ctag/design-reviews] Disabling UA transitions for same-document navigations (Issue #835)
- Re: [w3c/selection-api] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #164)
- Re: [w3c/selection-api] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #164)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- [w3ctag/design-reviews] Detect UA Transitions on Same-Document Navigations (Issue #834)
- Re: [WICG/webcomponents] [scoped-registries] Should WC be usable as "views"? (Issue #998)
- Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [WICG/webcomponents] [scoped-registries] What does `new` mean for elements in multiple registries? (Issue #1007)
- Re: [WICG/webcomponents] [scoped-registries] What does `new` mean for elements in multiple registries? (Issue #1007)
- Re: [WICG/webcomponents] [scoped-registries] What does `new` mean for elements in multiple registries? (Issue #1007)
- Re: [WICG/webcomponents] [scoped-registries] What does `new` mean for elements in multiple registries? (Issue #1007)
- Re: [w3ctag/design-reviews] WebAssembly Garbage Collection extensions (Issue #814)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- [whatwg/webidl] ByteString text should not talk about UTF-8 (Issue #1295)
- Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- Re: [WICG/webcomponents] SVG use element can't reference an element within the same shadow tree (#772)
- [WICG/webcomponents] [scoped-registries] What does `new` mean for elements in multiple registries? (Issue #1007)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [WICG/webcomponents] registry: Add an API to retrieve the localName given a custom element constructor (#566)
- Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [WICG/webcomponents] CSS selector to style slots with slotted elements (#936)
- Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)
- Re: [WICG/webcomponents] Theming options for shadow roots (#864)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)
- Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)
- Re: [WICG/webcomponents] Add delegatesLabel and a content attribute to specify the label element within a shadow tree (#916)
- Re: [WICG/webcomponents] There is no way to navigate to a fragment inside a shadow tree (#924)
- Re: [WICG/webcomponents] Supporting `<noscript>` when FACE is in play (Issue #1004)
- Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939)
- Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [WICG/webcomponents] [declarative-custom-elements] how would SSR work? (#886)
- Re: [WICG/webcomponents] [declarative-custom-elements] shorter syntax (#885)
- Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
- Re: [WICG/webcomponents] [dom-parts] Browser updating parts list from `getParts()` (Issue #993)
- Re: [WICG/webcomponents] [dom-parts] Tree structure of parts in the DOM (Issue #992)
- 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] Template/part proposals - Naming for DOM Parts API (#902)
- Re: [WICG/webcomponents] Template/part proposals should explain how and why they improve performance (#901)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161)
- [w3c/selection-api] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #164)
- [w3c/selection-api] Serialization of the current selection, when that selection crosses shadow roots (Issue #163)
- Re: [WICG/webcomponents] Interaction between imperative slotting and declarative shadow DOM (Issue #967)
- Re: [w3c/uievents] Need property which gives the (base) unmodified key (#247)
- Re: [whatwg/fetch] Clarify priority between blob.type and Content-Type in headers for request/response.blob() (Issue #1630)
- Re: [whatwg/streams] Synchronous WritableStream Writer to avoid heap allocations from Promises returned by WritableStreamDefaultWriter's write (Issue #1276)
- Re: [w3ctag/design-reviews] Shared Storage API (Issue #747)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3ctag/design-reviews] Shared Storage API (Issue #747)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069)
- Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039)
- [whatwg/streams] writeSync function on WritableStreamDefaultWriter to avoid unnecessary heap allocations from Promises returned by write (Issue #1276)
- 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: [w3ctag/design-reviews] Early design review request: IPA (Issue #823)
Thursday, 20 April 2023
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- [WICG/webcomponents] Spring 2023 Styling and Theming F2F (Issue #1006)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [WICG/webcomponents] "The problematic position" when Custom Elements throw errors? (#547)
- Re: [WICG/webcomponents] "The problematic position" when Custom Elements throw errors? (#547)
- Re: [WICG/webcomponents] components v1 native implementation - inner components problem (#615)
- Re: [WICG/webcomponents] components v1 native implementation - inner components problem (#615)
- Re: [WICG/webcomponents] HTML parser: align custom elements with the template element (#630)
- Re: [WICG/webcomponents] HTML parser: align custom elements with the template element (#630)
- Re: [WICG/webcomponents] [idea] Lifecycle method: beforeDisconnectedCallback (#825)
- Re: [WICG/webcomponents] [idea] Lifecycle method: beforeDisconnectedCallback (#825)
- Re: [WICG/webcomponents] JavaScript bundlers, HMR and customElements.define() (#829)
- Re: [WICG/webcomponents] JavaScript bundlers, HMR and customElements.define() (#829)
- Re: [WICG/webcomponents] observedAttributes should be converted to ASCII lowercase (#838)
- Re: [WICG/webcomponents] observedAttributes should be converted to ASCII lowercase (#838)
- Re: [WICG/webcomponents] `customElements.upgrade` does not upgrade node subtrees cloned from `template` contents via `cloneNode` (Issue #946)
- Re: [WICG/webcomponents] `customElements.upgrade` does not upgrade node subtrees cloned from `template` contents via `cloneNode` (Issue #946)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)
- Re: [WICG/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [WICG/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [WICG/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [WICG/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614)
- Re: [WICG/webcomponents] elementsFromPoint behavior is unclear (#735)
- Re: [WICG/webcomponents] elementsFromPoint behavior is unclear (#735)
- Re: [WICG/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773)
- Re: [WICG/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788)
- Re: [WICG/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788)
- Re: [WICG/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788)
- Re: [WICG/webcomponents] Document "layers" for single-use components (#806)
- Re: [WICG/webcomponents] [idea] shadowattach event (#893)
- Re: [WICG/webcomponents] [idea] shadowattach event (#893)
- Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005)
- [WICG/webcomponents] Supporting `<noscript>` when FACE is in play (Issue #1004)
- Re: [whatwg/streams] Editorial: Add missing argument to cancel and abort wrapper algorithms (PR #1275)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990)
- [whatwg/fetch] Add a way to have cookie origin and CORS origin be different (Issue #1637)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
- Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [w3ctag/design-reviews] FedCM Auto Re-authentication API (Issue #813)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188)
- Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188)
- Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188)
- Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188)
- Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/fetch] HTTP-redirect does not call processResponse and breaks navigation expectations (Issue #1629)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- Re: [whatwg/fetch] HTTP-redirect does not call processResponse and breaks navigation expectations (Issue #1629)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- Re: [w3ctag/design-reviews] early design review: bfcache/prerendering eviction APIs (Issue #786)
- Re: [w3ctag/design-reviews] FedCM Auto Re-authentication API (Issue #813)
- Re: [w3ctag/design-reviews] Wildcards in Permissions Policy Origins (Issue #765)
- Re: [w3ctag/design-reviews] Wildcards in Permissions Policy Origins (Issue #765)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [w3ctag/design-reviews] Web Authentication: Large Blob extension (Issue #820)
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721)
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)
- Re: [w3ctag/design-reviews] Web Bluetooth exclusionFilters option in requestDevice() (Issue #830)
- Re: [w3ctag/design-reviews] Web Bluetooth exclusionFilters option in requestDevice() (Issue #830)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)
- Re: [w3ctag/design-reviews] (Document Subtitle): Early review for adding a new value to the standard list of `name`s for a meta tag (Issue #819)
- Re: [w3ctag/design-reviews] (Document Subtitle): Early review for adding a new value to the standard list of `name`s for a meta tag (Issue #819)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188)
- Re: [whatwg/streams] Editorial: Add missing argument to cancel and abort wrapper algorithms (PR #1275)
- Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795)
- Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795)
- Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
- Re: [w3ctag/design-reviews] WebAssembly Garbage Collection extensions (Issue #814)
- Re: [WICG/webcomponents] Isolated web components (Issue #1002)
- [whatwg/streams] Editorial: Add missing argument to cancel and abort wrapper algorithms (PR #1275)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
Wednesday, 19 April 2023
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [WICG/webcomponents] Isolated web components (Issue #1002)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- [WICG/webcomponents] Isolated web components (Issue #1002)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- [whatwg/fetch] "consume body" step disagrees with "fully read" on whether the error callback accepts an argument (Issue #1636)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- [whatwg/streams] Add support for TransformStream "owning" writable/readable types (PR #1274)
- Re: [w3ctag/design-reviews] Shared Storage API (Issue #747)
- Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184)
- Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184)
- Re: [w3ctag/design-reviews] TAG review of the proposal to use the RegExp `v` flag instead of `u` for the HTML `pattern` attribute (Issue #832)
- Re: [w3ctag/design-reviews] TAG review of the proposal to use the RegExp `v` flag instead of `u` for the HTML `pattern` attribute (Issue #832)
- Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624)
- Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184)
- Re: [whatwg/streams] cancelAlgorithmWrapper does not handle cancellation argument (Issue #1273)
- [whatwg/dom] Clarification for <link> behavior in Declarative Shadow DOM (Issue #1187)
- [whatwg/streams] cancelAlgorithmWrapper does not handle cancellation argument (Issue #1273)
- [whatwg/dom] Yoshua is King (Issue #1186)
- Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795)
- Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
- Re: [w3ctag/design-reviews] Pre-CR review: HTML Review Draft — Published 18 January 2021 (#657)
- Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760)
- Re: [w3ctag/design-reviews] Early design review: scheduler.yield() (Issue #827)
- Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
Tuesday, 18 April 2023
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- [WICG/webcomponents] [scoped-registries] How does customElements.upgrade() work? (Issue #1001)
- Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- [WICG/webcomponents] Alternative to customized built-in - Element custom enhancements (Issue #1000)
- Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184)
- Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624)
- Re: [w3c/uievents] "keyCode" is the only way to work with KeyboardEvents now (#267)
- [whatwg/fetch] `fetch` should have definition for server side stuff, like `dnsLookup` and `socketPath` (Issue #1635)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240)
- Re: [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240)
- Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184)
- Re: [whatwg/fetch] Authorization-removal change was compatibility-breaking (Issue #1631)
- Re: [whatwg/fetch] What is meant by "It is initially « »" (Issue #1634)
- Re: [whatwg/fetch] What is meant by "It is initially « »" (Issue #1634)
- Re: [whatwg/fetch] What is meant by "It is initially « »" (Issue #1634)
- Re: [whatwg/fetch] What is meant by "It is initially « »" (Issue #1634)
- [whatwg/fetch] What is meant by "It is initially « »" (Issue #1634)
Monday, 17 April 2023
- Re: [whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222)
- Re: [whatwg/dom] Add before removing steps (PR #1185)
- Re: [whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)
- Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939)
- [w3c/ServiceWorker] Batch Cache Operations can't return an empty list (Issue #1677)
- [whatwg/dom] Add before removing steps (PR #1185)
- Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for writablestream owning type (PR #1272)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/fetch] Add http method to fetch timing info (PR #1632)
- [whatwg/streams] Add support for writablestream owning type (PR #1272)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [whatwg/fetch] Add http method to fetch timing info (PR #1632)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [whatwg/fetch] Add http method to fetch timing info (PR #1632)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- [whatwg/fetch] fix: Add http method to fetch timing info (PR #1632)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [w3ctag/design-reviews] text-wrap: balance (Issue #822)
- Re: [whatwg/webidl] Purpose of call-a-user-object’s-operation’s opName parameter (Issue #1282)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
Sunday, 16 April 2023
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884)
- Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884)
- Re: [WICG/webcomponents] [declarative-custom-elements] how would SSR work? (#886)
- [whatwg/fetch] Authorization-removal change was compatibility-breaking (Issue #1631)
Saturday, 15 April 2023
- Re: [WICG/webcomponents] [scoped-registries] Should WC be usable as "views"? (Issue #998)
- Re: [WICG/webcomponents] [scoped-registries] Should WC be usable as "views"? (Issue #998)
- Re: [WICG/webcomponents] [scoped-registries] Should WC be usable as "views"? (Issue #998)
- Re: [WICG/webcomponents] custom pseudo elements like ::before ::after, but using custom elements (Issue #983)
- Re: [WICG/webcomponents] custom pseudo elements like ::before ::after, but using custom elements (Issue #983)
- [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184)
- [WICG/webcomponents] [scoped-registries] Should WC be usable as "views"? (Issue #998)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
Friday, 14 April 2023
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [whatwg/streams] Efficient mapping to Unix-style APIs with pollable readers and writers (Issue #1265)
- Re: [whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222)
- Re: [whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222)
- Re: [whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [w3ctag/design-reviews] Review request for TURTLEDOVE (Issue #723)
- Re: [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110)
- Re: [whatwg/webidl] Export "an exception was thrown" (PR #1293)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989)
- Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [WICG/webcomponents] Interaction between ElementInternals (e.g. default ARIA) and declarative shadow DOM (Issue #972)
- Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186)
- Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [w3c/screen-orientation] Angle not consistently implemented (Issue #247)
- Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248)
- Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248)
- Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989)
- Re: [whatwg/webidl] Export "an exception was thrown" (PR #1293)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
Thursday, 13 April 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/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186)
- Re: [w3c/gamepad] GamepadHapticActuator.playEffect() algorithm seems wrong with regards to `[[playingEffectPromise]]` (Issue #179)
- Re: [w3c/gamepad] Update playingEffectPromise synchronously (PR #182)
- Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186)
- Re: [whatwg/webidl] Export "an exception was thrown" (PR #1293)
- Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280)
- Re: [w3c/IndexedDB] Sketch out IDBCursor.close() (#302)
- Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334)
- Re: [w3c/IndexedDB] Rename 'array key' to 'composite key'. For #360 (PR #392)
- Re: [w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401)
- Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343)
- Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343)
- Re: [w3c/IndexedDB] Initial sketch of manual commit flag for transactions (#331)
- Re: [w3c/IndexedDB] Sketch out IDBCursor.close() (#302)
- Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334)
- Re: [w3c/IndexedDB] Normalize negative zero (PR #386)
- Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186)
- Re: [w3c/IndexedDB] Rename 'array key' to 'composite key'. For #360 (PR #392)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- [whatwg/webidl] Export "an exception was thrown" (PR #1293)
- Re: [whatwg/webidl] Does [NewObject] do anything? (Issue #1289)
- Re: [whatwg/webidl] Does [NewObject] do anything? (Issue #1289)
- [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)
- Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989)
- Re: [w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401)
- Re: [w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401)
- Re: [w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401)
- Re: [w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401)
- Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989)
- Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989)
- Re: [w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- [w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250)
- Re: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250)
- Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
- [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251)
- Re: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250)
- [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250)
- Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248)
- Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248)
- [w3c/screen-orientation] Should we standardize window.orientation? (Issue #249)
- Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186)
- Re: [w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424)
Wednesday, 12 April 2023
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)
- Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [whatwg/fetch] Rename "extract-value flag" to "extract-value" and define it as a boolean (Issue #1567)
- Re: [w3ctag/design-reviews] [FYI] Report Critical-CH caused restart in NavigationTiming (Issue #833)
- Re: [w3ctag/design-reviews] requestStorageAccessFor (Issue #808)
- Re: [WICG/webcomponents] [declarative-custom-elements] how would SSR work? (#886)
- Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628)
- Re: [WICG/webcomponents] [declarative-custom-elements] how would SSR work? (#886)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- [whatwg/fetch] Clarify priority between blob.type and Content-Type in headers for request/response.blob() (Issue #1630)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248)
- Re: [w3c/screen-orientation] Angle not consistently implemented (Issue #247)
- [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248)
- Re: [w3c/screen-orientation] Angle not consistently implemented (Issue #247)
Tuesday, 11 April 2023
- Re: [w3c/screen-orientation] Angle not consistently implemented (Issue #247)
- [w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424)
- Re: [whatwg/webidl] ym962529@gmail.com (Issue #1292)
- [whatwg/webidl] ym962529@gmail.com (Issue #1292)
- Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914)
- Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884)
- [w3c/editing] Delayed clipboard rendering API shape. (Issue #423)
- Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884)
- Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884)
- Re: [WICG/webcomponents] How should autofill work for inputs generated inside shadow roots (#572)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- [w3c/screen-orientation] Angle not consistently implemented (Issue #247)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [w3ctag/design-reviews] First-Party Sets (#342)
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
Monday, 10 April 2023
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)
- Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204)
- Re: [w3ctag/design-reviews] Shared Storage API (Issue #747)
- Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204)
- Re: [w3ctag/design-reviews] Background Blur API (Issue #826)
- Re: [w3ctag/design-reviews] Background Blur API (Issue #826)
- Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726)
- Re: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185)
- Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- [whatwg/webidl] “Define the (static|unforgeable regular) attributes” algs say namespace is a possible argument (Issue #1291)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
Sunday, 9 April 2023
- [whatwg/fetch] HTTP-redirect does not call processResponse and breaks navigation expectations (Issue #1629)
- Re: [w3c/IndexedDB] Track ES BigInt work (#230)
- 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: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185)
- [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271)
- 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)
Friday, 7 April 2023
- Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)
- [whatwg/streams] Latency-bounded reads (Issue #1270)
- Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- Re: [whatwg/storage] Add "fileSystem" as a registered storage endpoint (PR #163)
- Re: [whatwg/storage] Add "fileSystem" as a registered storage endpoint (PR #163)
- Re: [w3c/uievents-key] Update UAX #15 to the latest version (Issue #59)
- Re: [whatwg/storage] Ensure storage endpoints are defined as storage endpoints (#90)
- [whatwg/storage] Add "fileSystem" as a registered storage endpoint (PR #163)
Thursday, 6 April 2023
- Re: [whatwg/webidl] Does [NewObject] do anything? (Issue #1289)
- [whatwg/webidl] Does [NewObject] do anything? (Issue #1289)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- Re: [w3ctag/design-reviews] Shared Storage API (Issue #747)
- 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 popovers when making an element fullscreen (PR #204)
- 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 popovers when making an element fullscreen (PR #204)
- 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 popovers when making an element fullscreen (PR #204)
- 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 popovers when making an element fullscreen (PR #204)
- 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: [WICG/webcomponents] <iframe> and the History API (#184)
- Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083)
Wednesday, 5 April 2023
- [whatwg/streams] @albasha96 (Issue #1267)
- Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628)
- Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628)
- [w3ctag/design-reviews] [FYI] Report Critical-CH caused restart in NavigationTiming (Issue #833)
- Re: [w3ctag/design-reviews] TAG review of the proposal to use the RegExp `v` flag instead of `u` for the HTML `pattern` attribute (Issue #832)
- Re: [w3ctag/design-reviews] TAG review of the proposal to use the RegExp `v` flag instead of `u` for the HTML `pattern` attribute (Issue #832)
- Re: [w3ctag/design-reviews] TAG review of the proposal to use the RegExp `v` flag instead of `u` for the HTML `pattern` attribute (Issue #832)
- [w3ctag/design-reviews] TAG review of the proposal to use the RegExp `v` flag instead of `u` for the HTML `pattern` attribute (Issue #832)
- Re: [w3ctag/design-reviews] First-Party Sets (#342)
- Re: [whatwg/streams] async iteration over a ReadableStream containing a rejected Promise will not clean up (Issue #1266)
- Re: [whatwg/fetch] add step for upgrades, still missing fallback (ec498bd)
- Re: [whatwg/fetch] add missing bracket (315cbb7)
- Re: [whatwg/encoding] Editorial: use leading and pending surrogate (PR #309)
- Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628)
- Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628)
- Re: [whatwg/streams] async iteration over a ReadableStream containing a rejected Promise will not clean up (Issue #1266)
- Re: [whatwg/streams] Efficient mapping to Unix-style APIs with pollable readers and writers (Issue #1265)
- Re: [whatwg/encoding] Editorial: use leading and pending surrogate (PR #309)
- [whatwg/encoding] Editorial: use leading and pending surrogate (PR #309)
- Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628)
- [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628)
- Re: [whatwg/streams] Editorial: update WPT (PR #1264)
- Re: [whatwg/streams] async iteration over a ReadableStream containing a rejected Promise will not clean up (Issue #1266)
- Re: [WICG/webcomponents] Templates are currently half a solution to web component HTML (Issue #994)
- [whatwg/streams] async iteration over a ReadableStream containing a rejected Promise will not clean up (Issue #1266)
- Re: [whatwg/webidl] async iteration can produce promises, which the ES spec generally avoids (Issue #1288)
- Re: [whatwg/webidl] async iteration can produce promises, which the ES spec generally avoids (Issue #1288)
- Re: [whatwg/webidl] async iteration can produce promises, which the ES spec generally avoids (Issue #1288)
- Re: [WICG/webcomponents] Empty innerHTML/textContent in connectedCallback, but the actual content is rendered (#903)
- Re: [WICG/webcomponents] Empty innerHTML/textContent in connectedCallback, but the actual content is rendered (#903)
- Re: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- 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)
- [whatwg/webidl] async iteration can produce promises, which the ES spec generally avoids (Issue #1288)
- [whatwg/streams] Efficient mapping to Unix-style APIs with pollable readers and writers (Issue #1265)
Tuesday, 4 April 2023
- [w3ctag/design-reviews] Eligibility for autofill (Issue #831)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- [whatwg/streams] Editorial: update WPT (PR #1264)
- Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083)
- Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083)
- Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- Re: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185)
- Re: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185)
- Re: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- Re: [w3c/uievents-key] Update UAX #15 to the latest version (Issue #59)
- Re: [w3c/uievents-key] update the reference to UAX15 (PR #62)
- Re: [w3c/uievents-key] update the reference to UAX15 (PR #62)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)
- [WICG/webcomponents] Functionally complete declarative templating (Issue #997)
- Re: [whatwg/streams] Specify realm for object creation (Issue #1213)
- Re: [whatwg/streams] Specify realm for object creation (Issue #1213)
- Re: [w3c/selection-api] collapse() and extend() should not exit early when called with a node within a shadow tree (Issue #162)
- Re: [WICG/webcomponents] Templates are currently half a solution to web component HTML (Issue #994)
- Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- Re: [w3c/selection-api] collapse() and extend() should not exit early when called with a node within a shadow tree (Issue #162)
- [w3c/selection-api] collapse() and extend() should not exit early when called with a node within a shadow tree (Issue #162)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805)
Monday, 3 April 2023
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- [whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222)
- Re: [whatwg/webidl] Revamp ByteString, DOMString, and USVString (#335)
- Re: [whatwg/streams] Specify realm for object creation (Issue #1213)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161)
- Re: [whatwg/dom] Specify that AbortController#abort() be bound to AbortController instance (#981)
- Re: [whatwg/dom] Specify that AbortController#abort() be bound to AbortController instance (#981)
- [WICG/webcomponents] [a11y]: An exhaustive look at support for using HTMLInputElement with Web Components (Issue #996)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- Re: [whatwg/streams] Can pipeTo() be synchronous? (Issue #1243)
- Re: [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183)
- Re: [whatwg/dom] Proposal: Allow WebIDL bindings to expose method parameters' types (Issue #1182)
- Re: [whatwg/dom] Proposal: Allow WebIDL bindings to expose method parameters' types (Issue #1182)
- Re: [whatwg/dom] Proposal: Allow WebIDL bindings to expose method parameters' types (Issue #1182)
- [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183)
- [whatwg/dom] Proposal: Allow WebIDL bindings to expose method parameters' types (Issue #1182)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [whatwg/dom] Disconnect single target instead of all (#126)
- Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- [whatwg/dom] Proposal: A new way to do feature detection for members (Issue #1181)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)
- [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676)
- 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: [w3c/screen-orientation] Example of usage is incorrect (Issue #245)
- Re: [w3c/screen-orientation] Fix error in example usage (PR #246)
- Re: [w3c/screen-orientation] Fix error in example usage (PR #246)
Sunday, 2 April 2023
- [w3c/screen-orientation] Fix error in example usage (PR #246)
- [w3c/screen-orientation] Example of usage is incorrect (Issue #245)
- [whatwg/url] Consider defining a primitive for a host-and-port parser (Issue #767)