public-webapps-github@w3.org from April 2023 by author

Aaron Gustafson

Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Wednesday, 26 April)
Re: [w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)
Re: [w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Friday, 21 April)

Abin K Paul

Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Friday, 7 April)

Adam Klein

Re: [w3ctag/design-reviews] WebAssembly Garbage Collection extensions (Issue #814) (Monday, 24 April)

Adam Rice

Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Monday, 24 April)
Re: [whatwg/streams] Synchronous WritableStream Writer to avoid heap allocations from Promises returned by WritableStreamDefaultWriter's write (Issue #1276) (Friday, 21 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Wednesday, 19 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Tuesday, 18 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Monday, 17 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 14 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185) (Monday, 10 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Monday, 10 April)
Re: [whatwg/streams] Efficient mapping to Unix-style APIs with pollable readers and writers (Issue #1265) (Wednesday, 5 April)
Re: [whatwg/encoding] Editorial: use leading and pending surrogate (PR #309) (Wednesday, 5 April)
Re: [whatwg/streams] Editorial: update WPT (PR #1264) (Wednesday, 5 April)
Re: [whatwg/streams] async iteration over a ReadableStream containing a rejected Promise will not clean up (Issue #1266) (Wednesday, 5 April)
Re: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185) (Wednesday, 5 April)
Re: [whatwg/streams] Specify realm for object creation (Issue #1213) (Tuesday, 4 April)
Re: [whatwg/streams] Can pipeTo() be synchronous? (Issue #1243) (Monday, 3 April)

adixon-adobe

Re: [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110) (Friday, 14 April)

Alex Russell

Re: [w3ctag/design-reviews] [FYI] Report Critical-CH caused restart in NavigationTiming (Issue #833) (Wednesday, 12 April)
Re: [w3ctag/design-reviews] requestStorageAccessFor (Issue #808) (Wednesday, 12 April)
Re: [w3ctag/design-reviews] First-Party Sets (#342) (Wednesday, 5 April)

Alexander Kalenik

[whatwg/fetch] HTTP-redirect does not call processResponse and breaks navigation expectations (Issue #1629) (Sunday, 9 April)

Alexander Spirgel

Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Wednesday, 12 April)
Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Sunday, 9 April)
Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Sunday, 9 April)

Andrea Giammarchi

Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 10 April)

Andreas Rossberg

Re: [w3ctag/design-reviews] WebAssembly Garbage Collection extensions (Issue #814) (Friday, 21 April)

Andreu Botella

Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Thursday, 6 April)

Anne van Kesteren

Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Friday, 28 April)
Re: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250) (Friday, 28 April)
Re: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250) (Friday, 28 April)
Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251) (Friday, 28 April)
Re: [whatwg/dom] Proposal: A new way to do feature detection for members (Issue #1181) (Friday, 28 April)
Re: [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183) (Friday, 28 April)
Re: [whatwg/fetch] Specify how/if response status code & content type are exposed for cross-origin navigations (Issue #1602) (Friday, 28 April)
Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628) (Friday, 28 April)
Re: [whatwg/fetch] The fetch pull algorithm does not pass proper bytesWritten to ReadableByteStreamControllerRespond (Issue #1610) (Friday, 28 April)
Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Friday, 28 April)
Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Friday, 28 April)
Re: [whatwg/dom] Add before removing steps (PR #1185) (Friday, 28 April)
Re: [whatwg/dom] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #1189) (Friday, 28 April)
Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184) (Friday, 28 April)
Re: [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183) (Friday, 28 April)
Re: [whatwg/dom] Proposal: A new way to do feature detection for members (Issue #1181) (Friday, 28 April)
Re: [whatwg/webidl] Detect whether a dictionary member was set by default or not (Issue #1300) (Friday, 28 April)
Re: [whatwg/webidl] Editorial: Fix typo in the overload resolution algorithm (PR #1299) (Friday, 28 April)
Re: [whatwg/webidl] Editorial: Fix typo in the overload resolution algorithm (PR #1299) (Friday, 28 April)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Thursday, 27 April)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Thursday, 27 April)
Re: [whatwg/fetch] Access-Control-Max-Age not effective in preflight request caching when Authorization header is programatically defined (#1278) (Thursday, 27 April)
Re: [whatwg/webidl] Editorial: remove remaining UTF-8 and UTF-16 references (PR #1298) (Wednesday, 26 April)
[whatwg/webidl] Editorial: remove remaining UTF-8 and UTF-16 references (PR #1298) (Wednesday, 26 April)
Re: [w3c/screen-orientation] Should we standardize window.orientation? (Issue #249) (Wednesday, 26 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Wednesday, 26 April)
Re: [whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191) (Wednesday, 26 April)
Re: [whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191) (Tuesday, 25 April)
Re: [whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191) (Tuesday, 25 April)
Re: [whatwg/fetch] Editorial: update args for collect an HTTP quoted string (PR #1641) (Tuesday, 25 April)
Re: [whatwg/dom] Attribute change steps should run after setting the value, not before (Issue #1190) (Monday, 24 April)
Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176) (Monday, 24 April)
Re: [whatwg/dom] Add before removing steps (PR #1185) (Monday, 24 April)
Re: [whatwg/webidl] Normative: Match ECMA‑262 function property enumeration order (#914) (Monday, 24 April)
Re: [whatwg/fetch] HTTP-redirect does not call processResponse and breaks navigation expectations (Issue #1629) (Monday, 24 April)
Re: [whatwg/fetch] Pass recursive=false to manual navigation redirect (PR #1638) (Monday, 24 April)
Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638) (Monday, 24 April)
Re: [whatwg/fetch] Authorization-removal change was compatibility-breaking (Issue #1631) (Monday, 24 April)
Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638) (Monday, 24 April)
Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638) (Monday, 24 April)
Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620) (Monday, 24 April)
Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638) (Monday, 24 April)
Re: [whatwg/webidl] Revamp ByteString, DOMString, and USVString (#335) (Saturday, 22 April)
Re: [whatwg/webidl] Revamp ByteString, DOMString, and USVString (#335) (Saturday, 22 April)
Re: [whatwg/webidl] تم ايقاف الخط للاتصالات والمكالمات والرسائل النصية القصيرة SMS01128336635 ارجو المساعده (Issue #1294) (Saturday, 22 April)
Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Saturday, 22 April)
Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Friday, 21 April)
[whatwg/webidl] ByteString text should not talk about UTF-8 (Issue #1295) (Friday, 21 April)
Re: [whatwg/fetch] Clarify priority between blob.type and Content-Type in headers for request/response.blob() (Issue #1630) (Friday, 21 April)
Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Friday, 21 April)
Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188) (Thursday, 20 April)
Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188) (Thursday, 20 April)
Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188) (Thursday, 20 April)
Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Thursday, 20 April)
Re: [whatwg/fetch] HTTP-redirect does not call processResponse and breaks navigation expectations (Issue #1629) (Thursday, 20 April)
Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184) (Wednesday, 19 April)
Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184) (Tuesday, 18 April)
Re: [whatwg/fetch] Authorization-removal change was compatibility-breaking (Issue #1631) (Tuesday, 18 April)
Re: [whatwg/fetch] What is meant by "It is initially « »" (Issue #1634) (Tuesday, 18 April)
Re: [whatwg/fetch] Add http method to fetch timing info (PR #1632) (Monday, 17 April)
Re: [whatwg/webidl] Does [NewObject] do anything? (Issue #1289) (Thursday, 13 April)
Re: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250) (Thursday, 13 April)
Re: [whatwg/encoding] Editorial: use leading and pending surrogate (PR #309) (Wednesday, 5 April)
[whatwg/encoding] Editorial: use leading and pending surrogate (PR #309) (Wednesday, 5 April)
[whatwg/url] Consider defining a primitive for a host-and-port parser (Issue #767) (Sunday, 2 April)

Anssi Kostiainen

Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795) (Monday, 24 April)

Antonio Sartori

Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Friday, 14 April)

Anup Singh

Re: [whatwg/fetch] Rename "extract-value flag" to "extract-value" and define it as a boolean (Issue #1567) (Wednesday, 12 April)

Ari Chivukula

[w3ctag/design-reviews] [FYI] Report Critical-CH caused restart in NavigationTiming (Issue #833) (Wednesday, 5 April)

Austin Sullivan

Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805) (Thursday, 20 April)
Re: [whatwg/storage] Add "fileSystem" as a registered storage endpoint (PR #163) (Friday, 7 April)
Re: [whatwg/storage] Add "fileSystem" as a registered storage endpoint (PR #163) (Friday, 7 April)
Re: [whatwg/storage] Ensure storage endpoints are defined as storage endpoints (#90) (Friday, 7 April)
[whatwg/storage] Add "fileSystem" as a registered storage endpoint (PR #163) (Friday, 7 April)
Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805) (Tuesday, 4 April)

Ben Mathwig

Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Friday, 21 April)

benjaminsavage

Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823) (Friday, 21 April)

Benny Powers

Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005) (Friday, 21 April)
[WICG/webcomponents] Supporting `<noscript>` when FACE is in play (Issue #1004) (Thursday, 20 April)

Bernard Aboba

Re: [w3ctag/design-reviews] WebRTC-SVC (Scalable Video Coding) (Issue #837) (Wednesday, 26 April)

Brian Takita

Bruce B. Anderson

Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Friday, 28 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Friday, 28 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Thursday, 27 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Thursday, 27 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Thursday, 27 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Thursday, 27 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Thursday, 27 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Wednesday, 26 April)
Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Friday, 21 April)
Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Thursday, 20 April)
Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Thursday, 20 April)
Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Thursday, 20 April)
Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Thursday, 20 April)
Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Wednesday, 19 April)
Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Wednesday, 19 April)
Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Tuesday, 18 April)
[WICG/webcomponents] Alternative to customized built-in - Element custom enhancements (Issue #1000) (Tuesday, 18 April)
Re: [WICG/webcomponents] [declarative-custom-elements] how would SSR work? (#886) (Wednesday, 12 April)
Re: [WICG/webcomponents] [declarative-custom-elements] how would SSR work? (#886) (Wednesday, 12 April)
Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884) (Tuesday, 11 April)
Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884) (Tuesday, 11 April)
Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884) (Tuesday, 11 April)
Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Thursday, 6 April)
Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Tuesday, 4 April)

caraitto

[whatwg/webidl] Export "an exception was thrown" (PR #1293) (Thursday, 13 April)

Carlos Lopez

[WICG/webcomponents] [a11y]: An exhaustive look at support for using HTMLInputElement with Web Components (Issue #996) (Monday, 3 April)

Chervya

Re: [whatwg/storage] Meta: update repository files (d5dbe0b) (Saturday, 1 April)

Cory LaViska

Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)

cybai (Haku)

[whatwg/fetch] Clarify priority between blob.type and Content-Type in headers for request/response.blob() (Issue #1630) (Wednesday, 12 April)

cynthia

Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795) (Wednesday, 19 April)
Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Wednesday, 19 April)

Dale Curtis

Re: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185) (Tuesday, 4 April)
Re: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185) (Tuesday, 4 April)

Dan Robertson

[whatwg/fetch] Editorial: update args for collect an HTTP quoted string (PR #1641) (Tuesday, 25 April)

Daniel Appelquist

Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Friday, 21 April)
Re: [w3ctag/design-reviews] Wildcards in Permissions Policy Origins (Issue #765) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Wildcards in Permissions Policy Origins (Issue #765) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Wednesday, 19 April)
Re: [w3ctag/design-reviews] First-Party Sets (#342) (Tuesday, 11 April)
Re: [w3ctag/design-reviews] Background Blur API (Issue #826) (Monday, 10 April)
Re: [w3ctag/design-reviews] Background Blur API (Issue #826) (Monday, 10 April)

Daniel Murphy

Re: [w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)
Re: [w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)
Re: [w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)

Darien Maillet Valentine

Re: [whatwg/webidl] Detect whether a dictionary member was set by default or not (Issue #1300) (Sunday, 30 April)
Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184) (Wednesday, 19 April)
Re: [whatwg/webidl] Purpose of call-a-user-object’s-operation’s opName parameter (Issue #1282) (Monday, 17 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Friday, 14 April)
[whatwg/webidl] “Define the (static|unforgeable regular) attributes” algs say namespace is a possible argument (Issue #1291) (Monday, 10 April)

David Benjamin

Re: [whatwg/fetch] Consider shifting the "bad port list" to an allowlist. (#1189) (Wednesday, 26 April)

David Callanan

Re: [w3c/IndexedDB] Track ES BigInt work (#230) (Sunday, 9 April)

Domenic Denicola

Re: [whatwg/webidl] ByteString text should not talk about UTF-8 (Issue #1295) (Thursday, 27 April)
Re: [whatwg/webidl] ByteString text should not talk about UTF-8 (Issue #1295) (Thursday, 27 April)
Re: [whatwg/webidl] Export "an exception was thrown" (PR #1293) (Friday, 14 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Friday, 7 April)
Re: [whatwg/webidl] Does [NewObject] do anything? (Issue #1289) (Thursday, 6 April)
Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628) (Wednesday, 5 April)
Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263) (Wednesday, 5 April)
Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263) (Wednesday, 5 April)
Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263) (Wednesday, 5 April)
Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Tuesday, 4 April)
Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Monday, 3 April)
Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263) (Monday, 3 April)
Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263) (Monday, 3 April)

Dominic Farolino

[w3ctag/design-reviews] Specification review for fenced frames (Issue #838) (Tuesday, 25 April)
[whatwg/webidl] Does [NewObject] do anything? (Issue #1289) (Thursday, 6 April)
Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Tuesday, 4 April)
Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Tuesday, 4 April)

Dominique Hazael-Massieux

Re: [w3ctag/design-reviews] WebRTC-SVC (Scalable Video Coding) (Issue #837) (Thursday, 27 April)
[w3ctag/design-reviews] WebRTC-SVC (Scalable Video Coding) (Issue #837) (Tuesday, 25 April)

Don Marti

Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Tuesday, 11 April)

donatocayurin

Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263) (Friday, 28 April)
Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263) (Friday, 28 April)
Re: [whatwg/fetch] Editorial: use "pull from bytes" algorithm (4502481) (Friday, 28 April)
Re: [whatwg/fetch] Editorial: use "pull from bytes" algorithm (4502481) (Friday, 28 April)
Re: [whatwg/fetch] Proposal: `Viewport` header for early hints (Issue #1640) (Friday, 28 April)
Re: [whatwg/fetch] Proposal: `Viewport` header for early hints (Issue #1640) (Friday, 28 April)

dSalieri

Re: [whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191) (Wednesday, 26 April)
[whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191) (Tuesday, 25 April)
Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184) (Wednesday, 19 April)
Re: [whatwg/dom] Second chance to find respectively type of event handler (Issue #1184) (Tuesday, 18 April)
[whatwg/dom] Second chance to find respectively type of event handler (Issue #1184) (Saturday, 15 April)

Elad Alon

Re: [whatwg/dom] Proposal: A new way to do feature detection for members (Issue #1181) (Friday, 28 April)
Re: [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183) (Friday, 28 April)
Re: [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183) (Monday, 3 April)
Re: [whatwg/dom] Proposal: Allow WebIDL bindings to expose method parameters' types (Issue #1182) (Monday, 3 April)
Re: [whatwg/dom] Proposal: Allow WebIDL bindings to expose method parameters' types (Issue #1182) (Monday, 3 April)
Re: [whatwg/dom] Proposal: Allow WebIDL bindings to expose method parameters' types (Issue #1182) (Monday, 3 April)
[whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183) (Monday, 3 April)
[whatwg/dom] Proposal: Allow WebIDL bindings to expose method parameters' types (Issue #1182) (Monday, 3 April)

Emilio Cobos Álvarez

Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176) (Monday, 24 April)
[whatwg/dom] Attribute change steps should run after setting the value, not before (Issue #1190) (Monday, 24 April)

Ethan Arrowood

Re: [whatwg/fetch] What is meant by "It is initially « »" (Issue #1634) (Tuesday, 18 April)
[whatwg/fetch] What is meant by "It is initially « »" (Issue #1634) (Tuesday, 18 April)

ExE Boss

Re: [whatwg/webidl] Normative: Match ECMA‑262 function property enumeration order (#914) (Saturday, 22 April)
Re: [whatwg/webidl] Normative: Match ECMA‑262 function property enumeration order (#914) (Saturday, 22 April)

fergald

Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Friday, 28 April)
Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Thursday, 20 April)
Re: [w3ctag/design-reviews] early design review: bfcache/prerendering eviction APIs (Issue #786) (Thursday, 20 April)

Florent Castelli

Re: [w3ctag/design-reviews] WebRTC-SVC (Scalable Video Coding) (Issue #837) (Wednesday, 26 April)
[w3ctag/design-reviews] WebRTC Codec selection API (Issue #836) (Monday, 24 April)

Frank

Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Thursday, 20 April)

Frank Topel

Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Sunday, 9 April)

François Beaufort

[whatwg/webidl] Detect whether a dictionary member was set by default or not (Issue #1300) (Friday, 28 April)
[whatwg/dom] Proposal: A new way to do feature detection for members (Issue #1181) (Monday, 3 April)

François Daoust

Re: [w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401) (Thursday, 13 April)
[w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401) (Thursday, 13 April)

Fuqiao Xue

Re: [w3c/uievents-key] Update UAX #15 to the latest version (Issue #59) (Friday, 7 April)

github-merge-queue[bot]

Re: [w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)
Re: [w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)

HBS

Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188) (Thursday, 20 April)
Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188) (Thursday, 20 April)
Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188) (Thursday, 20 April)
Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188) (Thursday, 20 April)
Re: [whatwg/dom] Clarification on document tree and DOM tree (Issue #1188) (Thursday, 20 April)
[whatwg/dom] Clarification on document tree and DOM tree (Issue #1188) (Thursday, 20 April)

hemanth.hm

Re: [whatwg/url] Add URL.canParse() (ae3c28b) (Sunday, 30 April)

hober

Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Thursday, 27 April)
Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Friday, 21 April)
Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Thursday, 20 April)
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) (Thursday, 20 April)
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) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Pre-CR review: HTML Review Draft — Published 18 January 2021 (#657) (Wednesday, 19 April)
Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Wednesday, 19 April)
Re: [w3ctag/design-reviews] Early design review: scheduler.yield() (Issue #827) (Wednesday, 19 April)

ianbjacobs

Re: [w3ctag/design-reviews] Two changes to Secure Payment Confirmation prior to CR (Issue #802) (Monday, 24 April)

Jake Archibald

Re: [whatwg/fetch] What is meant by "It is initially « »" (Issue #1634) (Tuesday, 18 April)
Re: [whatwg/fetch] What is meant by "It is initially « »" (Issue #1634) (Tuesday, 18 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Tuesday, 11 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Tuesday, 11 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Monday, 3 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Monday, 3 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Monday, 3 April)

James Babcock

Re: [whatwg/fetch] Authorization-removal change was compatibility-breaking (Issue #1631) (Monday, 24 April)
Re: [whatwg/fetch] Authorization-removal change was compatibility-breaking (Issue #1631) (Monday, 24 April)
[whatwg/fetch] Authorization-removal change was compatibility-breaking (Issue #1631) (Sunday, 16 April)

James Garbutt

Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Sunday, 9 April)

Javier G. Visiedo

Re: [whatwg/fetch] Access-Control-Max-Age not effective in preflight request caching when Authorization header is programatically defined (#1278) (Wednesday, 26 April)

Jeffrey Yasskin

Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Friday, 21 April)
Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Thursday, 20 April)
Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Thursday, 20 April)
Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Thursday, 20 April)
Re: [whatwg/webidl] Export "an exception was thrown" (PR #1293) (Friday, 14 April)
Re: [whatwg/webidl] Export "an exception was thrown" (PR #1293) (Thursday, 13 April)
Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Tuesday, 4 April)
Re: [whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Tuesday, 4 April)
[whatwg/webidl] Editorial: Define the WebIDL string types in terms of Infra types. (PR #1287) (Tuesday, 4 April)
Re: [whatwg/webidl] Revamp ByteString, DOMString, and USVString (#335) (Monday, 3 April)

Jeremy Roman

Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721) (Monday, 24 April)

Joey Arhar

Re: [whatwg/dom] Add before removing steps (PR #1185) (Monday, 24 April)
Re: [whatwg/dom] Add before removing steps (PR #1185) (Monday, 17 April)
Re: [whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222) (Monday, 17 April)
[whatwg/dom] Add before removing steps (PR #1185) (Monday, 17 April)
Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176) (Tuesday, 11 April)
Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176) (Tuesday, 11 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Monday, 10 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Monday, 10 April)

Jonathan Hao

Re: [w3ctag/design-reviews] WebRTC-SVC (Scalable Video Coding) (Issue #837) (Wednesday, 26 April)

Josh Karlin

Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Wednesday, 19 April)
Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Monday, 10 April)
Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Thursday, 6 April)

Joshua Bell

Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343) (Thursday, 13 April)
Re: [w3c/IndexedDB] Normalize negative zero (PR #386) (Thursday, 13 April)
Re: [w3c/IndexedDB] Initial sketch of manual commit flag for transactions (#331) (Thursday, 13 April)
Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280) (Thursday, 13 April)
Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Thursday, 13 April)
Re: [w3c/IndexedDB] Sketch out IDBCursor.close() (#302) (Thursday, 13 April)
Re: [w3c/IndexedDB] Rename 'array key' to 'composite key'. For #360 (PR #392) (Thursday, 13 April)
Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280) (Thursday, 13 April)
Re: [w3c/IndexedDB] Sketch out IDBCursor.close() (#302) (Thursday, 13 April)
Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Thursday, 13 April)
Re: [w3c/IndexedDB] Rename 'array key' to 'composite key'. For #360 (PR #392) (Thursday, 13 April)
Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343) (Thursday, 13 April)
Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280) (Thursday, 13 April)
Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343) (Thursday, 13 April)
Re: [w3c/IndexedDB] Initial sketch of manual commit flag for transactions (#331) (Thursday, 13 April)
Re: [w3c/IndexedDB] Sketch out IDBCursor.close() (#302) (Thursday, 13 April)
Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Thursday, 13 April)
Re: [w3c/IndexedDB] Normalize negative zero (PR #386) (Thursday, 13 April)
Re: [w3c/IndexedDB] Rename 'array key' to 'composite key'. For #360 (PR #392) (Thursday, 13 April)
Re: [w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401) (Thursday, 13 April)
Re: [w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401) (Thursday, 13 April)
Re: [w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401) (Thursday, 13 April)
Re: [w3c/IndexedDB] Adjust links to ECMAScript specifications (PR #401) (Thursday, 13 April)
Re: [w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424) (Thursday, 13 April)

Justin Fagnani

Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Friday, 28 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Thursday, 27 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Thursday, 27 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Thursday, 27 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Thursday, 27 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Thursday, 27 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Wednesday, 26 April)
[WICG/webcomponents] [declarate-custom-elements] Capabilities needed and open questions (Issue #1009) (Tuesday, 25 April)
Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Monday, 24 April)
Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Monday, 24 April)
Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Monday, 24 April)
Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Monday, 24 April)
Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Monday, 24 April)
Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Monday, 24 April)
Re: [WICG/webcomponents] [scoped-registries] What does `new` mean for elements in multiple registries? (Issue #1007) (Friday, 21 April)
Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Friday, 21 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Thursday, 20 April)
[WICG/webcomponents] Spring 2023 Styling and Theming F2F (Issue #1006) (Thursday, 20 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Thursday, 20 April)
Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005) (Thursday, 20 April)
Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Thursday, 20 April)
Re: [WICG/webcomponents] Isolated web components (Issue #1002) (Thursday, 20 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Wednesday, 19 April)
[WICG/webcomponents] Isolated web components (Issue #1002) (Wednesday, 19 April)
[WICG/webcomponents] [scoped-registries] How does customElements.upgrade() work? (Issue #1001) (Tuesday, 18 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Monday, 17 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Saturday, 15 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Friday, 14 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Friday, 14 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Friday, 14 April)
Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989) (Friday, 14 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Friday, 14 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Friday, 14 April)
Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989) (Thursday, 13 April)
Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914) (Tuesday, 11 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 11 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 11 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 11 April)

Kagami Sascha Rosylight

Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Monday, 24 April)
Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628) (Wednesday, 12 April)
Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628) (Wednesday, 5 April)
Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628) (Wednesday, 5 April)
Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628) (Wednesday, 5 April)
Re: [whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628) (Wednesday, 5 April)
[whatwg/fetch] Editorial: Use "pull from bytes" algorithm (PR #1628) (Wednesday, 5 April)
Re: [whatwg/streams] Specify realm for object creation (Issue #1213) (Tuesday, 4 April)
Re: [whatwg/streams] Specify realm for object creation (Issue #1213) (Monday, 3 April)
Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263) (Monday, 3 April)

Keith Cirkel

Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Thursday, 27 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Thursday, 27 April)
[whatwg/dom] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #1189) (Saturday, 22 April)
Re: [WICG/webcomponents] [scoped-registries] What does `new` mean for elements in multiple registries? (Issue #1007) (Friday, 21 April)
Re: [WICG/webcomponents] [scoped-registries] What does `new` mean for elements in multiple registries? (Issue #1007) (Friday, 21 April)
[WICG/webcomponents] [scoped-registries] What does `new` mean for elements in multiple registries? (Issue #1007) (Friday, 21 April)
Re: [WICG/webcomponents] registry: Add an API to retrieve the localName given a custom element constructor (#566) (Friday, 21 April)
Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Friday, 21 April)
Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Friday, 21 April)
Re: [WICG/webcomponents] CSS selector to style slots with slotted elements (#936) (Friday, 21 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Friday, 21 April)
Re: [WICG/webcomponents] Theming options for shadow roots (#864) (Friday, 21 April)
Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Friday, 21 April)
Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 21 April)
Re: [WICG/webcomponents] Add delegatesLabel and a content attribute to specify the label element within a shadow tree (#916) (Friday, 21 April)
Re: [WICG/webcomponents] There is no way to navigate to a fragment inside a shadow tree (#924) (Friday, 21 April)
Re: [WICG/webcomponents] Supporting `<noscript>` when FACE is in play (Issue #1004) (Friday, 21 April)
Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Friday, 21 April)
Re: [WICG/webcomponents] [scoped-registries] Element upgrade ordering (#923) (Friday, 21 April)
Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914) (Friday, 21 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Friday, 21 April)
Re: [WICG/webcomponents] [declarative-custom-elements] how would SSR work? (#886) (Friday, 21 April)
Re: [WICG/webcomponents] [declarative-custom-elements] shorter syntax (#885) (Friday, 21 April)
Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884) (Friday, 21 April)
Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Friday, 21 April)
Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003) (Friday, 21 April)
Re: [WICG/webcomponents] [dom-parts] Browser updating parts list from `getParts()` (Issue #993) (Friday, 21 April)
Re: [WICG/webcomponents] [dom-parts] Tree structure of parts in the DOM (Issue #992) (Friday, 21 April)
Re: [WICG/webcomponents] [dom-parts] Remove `.value` and `.commit()`, add `replaceChildren` (Issue #991) (Friday, 21 April)
Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Friday, 21 April)
Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902) (Friday, 21 April)
Re: [WICG/webcomponents] Template/part proposals should explain how and why they improve performance (#901) (Friday, 21 April)
Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Friday, 21 April)
[w3c/selection-api] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #164) (Friday, 21 April)
[w3c/selection-api] Serialization of the current selection, when that selection crosses shadow roots (Issue #163) (Friday, 21 April)
Re: [WICG/webcomponents] Interaction between imperative slotting and declarative shadow DOM (Issue #967) (Friday, 21 April)
Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Thursday, 20 April)
Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Tuesday, 4 April)

Kenneth Rohde Christiansen

Re: [w3ctag/design-reviews] Compute Pressure Specification Review (Issue #795) (Wednesday, 19 April)

Kevin Gibbons

Re: [whatwg/streams] async iteration over a ReadableStream containing a rejected Promise will not clean up (Issue #1266) (Wednesday, 5 April)
[whatwg/streams] async iteration over a ReadableStream containing a rejected Promise will not clean up (Issue #1266) (Wednesday, 5 April)
Re: [whatwg/webidl] async iteration can produce promises, which the ES spec generally avoids (Issue #1288) (Wednesday, 5 April)
Re: [whatwg/webidl] async iteration can produce promises, which the ES spec generally avoids (Issue #1288) (Wednesday, 5 April)
[whatwg/webidl] async iteration can produce promises, which the ES spec generally avoids (Issue #1288) (Wednesday, 5 April)

Khafra

[w3c/ServiceWorker] Batch Cache Operations can't return an empty list (Issue #1677) (Monday, 17 April)

Khushal Sagar

[w3ctag/design-reviews] Disabling UA transitions for same-document navigations (Issue #835) (Friday, 21 April)
[w3ctag/design-reviews] Detect UA Transitions on Same-Document Navigations (Issue #834) (Friday, 21 April)

Koji Ishii

Re: [w3ctag/design-reviews] text-wrap: balance (Issue #822) (Monday, 17 April)

Lea Verou

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) (Wednesday, 19 April)
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) (Wednesday, 19 April)
Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) (Wednesday, 19 April)
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) (Wednesday, 5 April)
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) (Wednesday, 5 April)

Lexvato

Re: [whatwg/webidl] Does [NewObject] do anything? (Issue #1289) (Thursday, 13 April)

liudonghua

Re: [WICG/webcomponents] Empty innerHTML/textContent in connectedCallback, but the actual content is rendered (#903) (Wednesday, 5 April)
Re: [WICG/webcomponents] Empty innerHTML/textContent in connectedCallback, but the actual content is rendered (#903) (Wednesday, 5 April)

Lonnie Best

[whatwg/dom] Introducing Direct Navigation to Client-Side JavaScript-Generated HTML Documents (Issue #1192) (Tuesday, 25 April)
[WICG/webcomponents] Introducing Direct Navigation to Client-Side JavaScript-Generated HTML Documents (Issue #1008) (Tuesday, 25 April)

loynoir

[whatwg/fetch] `fetch` should have definition for server side stuff, like `dnsLookup` and `socketPath` (Issue #1635) (Tuesday, 18 April)

M. Pont

[w3c/screen-orientation] Example of usage is incorrect (Issue #245) (Sunday, 2 April)

Makoto Kato

Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248) (Monday, 24 April)
Re: [w3c/screen-orientation] Angle not consistently implemented (Issue #247) (Tuesday, 11 April)

mangelozzi

Re: [WICG/webcomponents] Cascading Style Sheet module scripts (#759) (Sunday, 23 April)

Manuel Rego Casasnovas

Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005) (Monday, 24 April)

Marcos Cáceres

Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/screen-orientation] Angle not consistently implemented (Issue #247) (Friday, 14 April)
Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248) (Friday, 14 April)
Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248) (Friday, 14 April)
Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Friday, 14 April)
Re: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250) (Thursday, 13 April)
Re: [w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250) (Thursday, 13 April)
Re: [w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251) (Thursday, 13 April)
[w3c/screen-orientation] Editorial: combine safety check steps into new section (PR #251) (Thursday, 13 April)
[w3c/screen-orientation] Editorial: fix queue a task to fire change an event (PR #250) (Thursday, 13 April)
Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248) (Thursday, 13 April)
Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248) (Thursday, 13 April)
[w3c/screen-orientation] Should we standardize window.orientation? (Issue #249) (Thursday, 13 April)
Re: [w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248) (Wednesday, 12 April)
Re: [w3c/screen-orientation] Angle not consistently implemented (Issue #247) (Wednesday, 12 April)
[w3c/screen-orientation] Standardize angle orientations counter-clockwise (PR #248) (Wednesday, 12 April)
Re: [w3c/screen-orientation] Angle not consistently implemented (Issue #247) (Wednesday, 12 April)
[w3c/screen-orientation] Angle not consistently implemented (Issue #247) (Tuesday, 11 April)
Re: [w3c/screen-orientation] Example of usage is incorrect (Issue #245) (Monday, 3 April)
Re: [w3c/screen-orientation] Fix error in example usage (PR #246) (Monday, 3 April)
Re: [w3c/screen-orientation] Fix error in example usage (PR #246) (Monday, 3 April)

Martin Thomson

Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Tuesday, 11 April)
Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823) (Saturday, 1 April)

Mason Freed

Re: [whatwg/dom] Attribute change steps should run after setting the value, not before (Issue #1190) (Friday, 28 April)
Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Monday, 24 April)
Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Monday, 24 April)
Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Monday, 24 April)
Re: [WICG/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788) (Thursday, 20 April)
Re: [WICG/webcomponents] Document "layers" for single-use components (#806) (Thursday, 20 April)
Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Thursday, 20 April)
Re: [whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222) (Monday, 17 April)
Re: [whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222) (Friday, 14 April)
Re: [whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222) (Friday, 14 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Wednesday, 12 April)

Mathias Bynens

Matt Giuca

Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Thursday, 27 April)
Re: [w3c/manifest] [meta] Don't require merge queue for PRs (Issue #1075) (Thursday, 27 April)
Re: [w3c/manifest] [meta] Don't require merge queue for PRs (Issue #1075) (Thursday, 27 April)
Re: [w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)
Re: [w3c/manifest] [meta] Don't require merge queue for PRs (Issue #1075) (Wednesday, 26 April)
Re: [w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)
Re: [w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)
Re: [w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Wednesday, 26 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Wednesday, 26 April)
[w3c/manifest] Ran tidy. (PR #1076) (Wednesday, 26 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Monday, 24 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Monday, 24 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Monday, 24 April)
Re: [w3c/manifest] [meta] Don't require merge queue for PRs (Issue #1075) (Monday, 24 April)
[w3c/manifest] [meta] Don't require merge queue for PRs (Issue #1075) (Monday, 24 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Friday, 21 April)
Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Friday, 21 April)
Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039) (Friday, 21 April)

Matt Reynolds

Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Thursday, 13 April)
Re: [w3c/gamepad] GamepadHapticActuator.playEffect() algorithm seems wrong with regards to `[[playingEffectPromise]]` (Issue #179) (Thursday, 13 April)
Re: [w3c/gamepad] Update playingEffectPromise synchronously (PR #182) (Thursday, 13 April)
Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Thursday, 13 April)
Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Wednesday, 12 April)

Matthew

[whatwg/dom] Yoshua is King (Issue #1186) (Wednesday, 19 April)

Matthew Olsson

Re: [whatwg/streams] Editorial: Add missing argument to cancel and abort wrapper algorithms (PR #1275) (Thursday, 20 April)
[whatwg/streams] Editorial: Add missing argument to cancel and abort wrapper algorithms (PR #1275) (Thursday, 20 April)
[whatwg/streams] cancelAlgorithmWrapper does not handle cancellation argument (Issue #1273) (Wednesday, 19 April)

Matthew Phillips

Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Friday, 28 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Thursday, 27 April)

Mattias Buelens

Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Tuesday, 11 April)
Re: [whatwg/streams] async iteration over a ReadableStream containing a rejected Promise will not clean up (Issue #1266) (Wednesday, 5 April)
[whatwg/streams] Editorial: update WPT (PR #1264) (Tuesday, 4 April)
Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Tuesday, 4 April)
Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Tuesday, 4 April)
Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Tuesday, 4 April)

Michael Kleber

Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Friday, 14 April)
Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Tuesday, 11 April)

Michael Warren

Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Monday, 10 April)

Michaël Gallego

[whatwg/dom] Clarification for <link> behavior in Declarative Shadow DOM (Issue #1187) (Wednesday, 19 April)

Mike Taylor

Re: [whatwg/dom] Does the currentEvent variable make a sense in Inner Invoke? (Issue #1191) (Thursday, 27 April)
Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Monday, 3 April)

Ming-Ying Chung

Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Tuesday, 4 April)
Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Monday, 3 April)

mohamed1rashad

[whatwg/streams] @albasha96 (Issue #1267) (Wednesday, 5 April)

Ms2ger

[whatwg/webidl] Editorial: Fix typo in the overload resolution algorithm (PR #1299) (Friday, 28 April)
Re: [whatwg/webidl] Editorial: remove remaining UTF-8 and UTF-16 references (PR #1298) (Wednesday, 26 April)
Re: [whatwg/webidl] Normative: Match ECMA‑262 function property enumeration order (#914) (Monday, 24 April)

Muhammad Salem

Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Sunday, 16 April)

Nick Doty

Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Thursday, 27 April)

nickwelp

[whatwg/fetch] Why does the Fetch standard forbid GET Body when it's not against REST? (Issue #1644) (Friday, 28 April)

Nicolas Gilbert

Re: [WICG/webcomponents] [scoped-registries] Should WC be usable as "views"? (Issue #998) (Friday, 21 April)
Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989) (Friday, 21 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Friday, 21 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Wednesday, 19 April)
Re: [WICG/webcomponents] [scoped-registries] Should WC be usable as "views"? (Issue #998) (Saturday, 15 April)
[WICG/webcomponents] [scoped-registries] Should WC be usable as "views"? (Issue #998) (Saturday, 15 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Friday, 14 April)
Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989) (Friday, 14 April)
Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989) (Friday, 14 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Friday, 14 April)
Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989) (Thursday, 13 April)
Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989) (Thursday, 13 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Wednesday, 12 April)

Nidhi Jaju

Re: [whatwg/streams] Editorial: Add missing argument to cancel and abort wrapper algorithms (PR #1275) (Thursday, 20 April)
Re: [whatwg/streams] cancelAlgorithmWrapper does not handle cancellation argument (Issue #1273) (Wednesday, 19 April)
[whatwg/streams] Latency-bounded reads (Issue #1270) (Friday, 7 April)

Nigel Megitt

Re: [w3ctag/design-reviews] Review of IMSC-HRM (Issue #788) (Thursday, 27 April)

Nikola Pavlovic

Re: [WICG/webcomponents] <iframe> and the History API (#184) (Thursday, 6 April)

Noam Rosenthal

[whatwg/fetch] Use internalResponse at end of fetch handover (PR #1645) (Sunday, 30 April)
Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620) (Monday, 24 April)
Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620) (Monday, 24 April)
Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620) (Monday, 24 April)
Re: [whatwg/fetch] Proposal: `Viewport` header for early hints (Issue #1640) (Monday, 24 April)
[whatwg/fetch] Proposal: `Viewport` header for early hints (Issue #1640) (Monday, 24 April)
Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638) (Monday, 24 April)
Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638) (Monday, 24 April)
Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620) (Monday, 24 April)
Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620) (Monday, 24 April)
Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620) (Monday, 24 April)
Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620) (Monday, 24 April)
Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638) (Monday, 24 April)
Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638) (Monday, 24 April)
Re: [whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638) (Monday, 24 April)
Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483) (Monday, 24 April)
[whatwg/fetch] Editorial: Pass recursive=false to manual navigation redirect (PR #1638) (Sunday, 23 April)
Re: [whatwg/fetch] HTTP-redirect does not call processResponse and breaks navigation expectations (Issue #1629) (Thursday, 20 April)
Re: [whatwg/fetch] Separate DNS timing info from proxy resolution (PR #1429) (Tuesday, 11 April)

Nolan Lawson

Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Thursday, 20 April)
[WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005) (Thursday, 20 April)
Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Monday, 17 April)
Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Monday, 17 April)

npm1

[w3ctag/design-reviews] FedCM: LoginHint, UserInfo, and RPContext (Issue #839) (Wednesday, 26 April)
[whatwg/fetch] Add a way to have cookie origin and CORS origin be different (Issue #1637) (Thursday, 20 April)

Paul Jensen

Re: [w3ctag/design-reviews] Review request for TURTLEDOVE (Issue #723) (Friday, 14 April)

Peter Burns

Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 11 April)

Peter Ferenczy

Re: [w3c/uievents] Need property which gives the (base) unmodified key (#247) (Friday, 21 April)
Re: [w3c/uievents] "keyCode" is the only way to work with KeyboardEvents now (#267) (Tuesday, 18 April)

Peter Linss

Re: [w3ctag/design-reviews] FedCM Auto Re-authentication API (Issue #813) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Web Authentication: Large Blob extension (Issue #820) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Web Bluetooth exclusionFilters option in requestDevice() (Issue #830) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Web Bluetooth exclusionFilters option in requestDevice() (Issue #830) (Thursday, 20 April)
Re: [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240) (Tuesday, 18 April)
Re: [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240) (Tuesday, 18 April)

Philip Jägenstedt

Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Friday, 28 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Wednesday, 26 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Tuesday, 25 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Tuesday, 25 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Tuesday, 25 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Tuesday, 25 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Wednesday, 19 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Wednesday, 19 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Wednesday, 19 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)
Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Thursday, 6 April)

piscopancer

Re: [w3c/manifest] Manifest: property 'src' ignored, URL is invalid. (Issue #1059) (Monday, 24 April)

Piyaphart samutkang

Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Sunday, 23 April)

PoolloverNathan

[whatwg/webidl] Improperly pluralized verb in "The [LegacyNamespace] extended attribute take an identifier" (Issue #1296) (Sunday, 23 April)

Reilly Grant

Re: [whatwg/streams] Efficient mapping to Unix-style APIs with pollable readers and writers (Issue #1265) (Friday, 14 April)
[whatwg/streams] Efficient mapping to Unix-style APIs with pollable readers and writers (Issue #1265) (Wednesday, 5 April)

Renoir Boulanger

Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Monday, 24 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Monday, 24 April)

Rick Byers

Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Tuesday, 25 April)

Rik Cabanier

Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Friday, 14 April)
Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Friday, 14 April)
Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Thursday, 13 April)
Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Thursday, 13 April)

Rob Eisenberg

Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Friday, 28 April)
Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009) (Friday, 28 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Thursday, 27 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Thursday, 27 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Thursday, 27 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Monday, 17 April)

Robert Kieffer

Re: [whatwg/dom] Specify that AbortController#abort() be bound to AbortController instance (#981) (Monday, 3 April)
Re: [whatwg/dom] Specify that AbortController#abort() be bound to AbortController instance (#981) (Monday, 3 April)

RockIn

Re: [whatwg/dom] Disconnect single target instead of all (#126) (Monday, 24 April)
Re: [whatwg/dom] Disconnect single target instead of all (#126) (Monday, 24 April)

Ronald Zielaznicki

Re: [whatwg/dom] Disconnect single target instead of all (#126) (Sunday, 23 April)

Rossen Atanassov

Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Monday, 10 April)

Russell Bicknell

Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)

Ryosuke Niwa

Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Monday, 24 April)
Re: [WICG/webcomponents] [scoped-registries] Describe interaction with declarative shadow DOM (#915) (Monday, 24 April)
Re: [w3c/selection-api] toString should return the selected text in input / textarea element (Issue #165) (Saturday, 22 April)
[w3c/selection-api] toString should return the selected text in input / textarea element (Issue #165) (Saturday, 22 April)
Re: [w3c/selection-api] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #164) (Friday, 21 April)
Re: [w3c/selection-api] Should TreeWalker be expanded to support shadow roots in support of the selection API? (Issue #164) (Friday, 21 April)
Re: [WICG/webcomponents] Spring 2023 Cross-Root ARIA F2F (Issue #1005) (Friday, 21 April)
Re: [WICG/webcomponents] "The problematic position" when Custom Elements throw errors? (#547) (Thursday, 20 April)
Re: [WICG/webcomponents] "The problematic position" when Custom Elements throw errors? (#547) (Thursday, 20 April)
Re: [WICG/webcomponents] components v1 native implementation - inner components problem (#615) (Thursday, 20 April)
Re: [WICG/webcomponents] components v1 native implementation - inner components problem (#615) (Thursday, 20 April)
Re: [WICG/webcomponents] HTML parser: align custom elements with the template element (#630) (Thursday, 20 April)
Re: [WICG/webcomponents] HTML parser: align custom elements with the template element (#630) (Thursday, 20 April)
Re: [WICG/webcomponents] [idea] Lifecycle method: beforeDisconnectedCallback (#825) (Thursday, 20 April)
Re: [WICG/webcomponents] [idea] Lifecycle method: beforeDisconnectedCallback (#825) (Thursday, 20 April)
Re: [WICG/webcomponents] JavaScript bundlers, HMR and customElements.define() (#829) (Thursday, 20 April)
Re: [WICG/webcomponents] JavaScript bundlers, HMR and customElements.define() (#829) (Thursday, 20 April)
Re: [WICG/webcomponents] observedAttributes should be converted to ASCII lowercase (#838) (Thursday, 20 April)
Re: [WICG/webcomponents] observedAttributes should be converted to ASCII lowercase (#838) (Thursday, 20 April)
Re: [WICG/webcomponents] `customElements.upgrade` does not upgrade node subtrees cloned from `template` contents via `cloneNode` (Issue #946) (Thursday, 20 April)
Re: [WICG/webcomponents] `customElements.upgrade` does not upgrade node subtrees cloned from `template` contents via `cloneNode` (Issue #946) (Thursday, 20 April)
Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962) (Thursday, 20 April)
Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962) (Thursday, 20 April)
Re: [WICG/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Thursday, 20 April)
Re: [WICG/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Thursday, 20 April)
Re: [WICG/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 20 April)
Re: [WICG/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Thursday, 20 April)
Re: [WICG/webcomponents] elementsFromPoint behavior is unclear (#735) (Thursday, 20 April)
Re: [WICG/webcomponents] elementsFromPoint behavior is unclear (#735) (Thursday, 20 April)
Re: [WICG/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) (Thursday, 20 April)
Re: [WICG/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788) (Thursday, 20 April)
Re: [WICG/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788) (Thursday, 20 April)
Re: [WICG/webcomponents] [idea] shadowattach event (#893) (Thursday, 20 April)
Re: [WICG/webcomponents] [idea] shadowattach event (#893) (Thursday, 20 April)
Re: [WICG/webcomponents] Isolated web components (Issue #1002) (Wednesday, 19 April)
Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Wednesday, 19 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Monday, 17 April)
[WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Monday, 17 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Friday, 14 April)
Re: [w3c/selection-api] collapse() and extend() should not exit early when called with a node within a shadow tree (Issue #162) (Tuesday, 4 April)
Re: [w3c/selection-api] collapse() and extend() should not exit early when called with a node within a shadow tree (Issue #162) (Tuesday, 4 April)
[w3c/selection-api] collapse() and extend() should not exit early when called with a node within a shadow tree (Issue #162) (Tuesday, 4 April)
Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Monday, 3 April)

RZ7272

[whatwg/fetch] A (Issue #1643) (Thursday, 27 April)
Re: [whatwg/fetch] R (Issue #1642) (Thursday, 27 April)
[whatwg/fetch] R (Issue #1642) (Thursday, 27 April)

S.A.N

Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 26 April)

Safwa Islam

Re: [whatwg/webidl] Intent to use Constants (Issue #1297) (Wednesday, 26 April)
Re: [whatwg/webidl] Intent to use Constants (Issue #1297) (Wednesday, 26 April)
[whatwg/webidl] Intent to use Constants (Issue #1297) (Wednesday, 26 April)

Sam Atkins

[whatwg/fetch] "consume body" step disagrees with "fully read" on whether the error callback accepts an argument (Issue #1636) (Wednesday, 19 April)

Sasha Firsov

Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Sunday, 30 April)
Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782) (Monday, 24 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Thursday, 20 April)
Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003) (Thursday, 20 April)
Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Wednesday, 19 April)
Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884) (Sunday, 16 April)
Re: [WICG/webcomponents] [declarative-custom-elements] how does the class get associated with the definition (#884) (Sunday, 16 April)
Re: [WICG/webcomponents] [declarative-custom-elements] how would SSR work? (#886) (Sunday, 16 April)
Re: [WICG/webcomponents] [scoped-registries] Should WC be usable as "views"? (Issue #998) (Saturday, 15 April)
Re: [WICG/webcomponents] [scoped-registries] Should WC be usable as "views"? (Issue #998) (Saturday, 15 April)
Re: [WICG/webcomponents] custom pseudo elements like ::before ::after, but using custom elements (Issue #983) (Saturday, 15 April)
Re: [WICG/webcomponents] custom pseudo elements like ::before ::after, but using custom elements (Issue #983) (Saturday, 15 April)
Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Friday, 7 April)
Re: [WICG/webcomponents] Templates are currently half a solution to web component HTML (Issue #994) (Wednesday, 5 April)
Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Wednesday, 5 April)
Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Wednesday, 5 April)
Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Wednesday, 5 April)
Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Wednesday, 5 April)
Re: [WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Wednesday, 5 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 4 April)
[WICG/webcomponents] Functionally complete declarative templating (Issue #997) (Tuesday, 4 April)
Re: [WICG/webcomponents] Templates are currently half a solution to web component HTML (Issue #994) (Tuesday, 4 April)

schwering

Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Thursday, 20 April)
[w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Tuesday, 4 April)

Scott Haseley

Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Wednesday, 12 April)
Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Tuesday, 4 April)
Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Tuesday, 4 April)
Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Monday, 3 April)
Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Monday, 3 April)

Serhii Kulykov

Re: [WICG/webcomponents] Cascading Style Sheet module scripts (#759) (Monday, 24 April)

Shivan Kaul Sahib

Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823) (Sunday, 30 April)

Simon Pieters

Re: [WICG/webcomponents] Interaction between ElementInternals (e.g. default ARIA) and declarative shadow DOM (Issue #972) (Friday, 14 April)

smaug----

Re: [whatwg/dom] Disconnect single target instead of all (#126) (Monday, 24 April)
Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Thursday, 13 April)
Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Wednesday, 12 April)
Re: [whatwg/dom] Disconnect single target instead of all (#126) (Monday, 3 April)

snianu

Re: [w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424) (Thursday, 13 April)
[w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424) (Tuesday, 11 April)
Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Tuesday, 11 April)
[w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Tuesday, 11 April)

Sohom Datta

Re: [whatwg/fetch] Add http method to fetch timing info (PR #1632) (Monday, 17 April)
[whatwg/fetch] fix: Add http method to fetch timing info (PR #1632) (Monday, 17 April)

Tab Atkins Jr.

Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Friday, 28 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Friday, 28 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Tuesday, 25 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Thursday, 20 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Thursday, 20 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Thursday, 20 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Thursday, 20 April)
Re: [whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222) (Friday, 14 April)
Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Friday, 14 April)
[whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223) (Thursday, 13 April)
[whatwg/fullscreen] Unfullscreening unconditionally removes from top layer, ignoring other qualities (Issue #222) (Monday, 3 April)

Thomas Di Grégorio

Re: [WICG/webcomponents] SVG use element can't reference an element within the same shadow tree (#772) (Friday, 21 April)

Thomas Steiner

Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Thursday, 20 April)

Tiger Oakes

[w3c/screen-orientation] Fix error in example usage (PR #246) (Sunday, 2 April)

Tim Nguyen

Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Friday, 28 April)

Timothy Gu

Re: [whatwg/webidl] async iteration can produce promises, which the ES spec generally avoids (Issue #1288) (Wednesday, 5 April)

Titouan Rigoudy

Re: [whatwg/fetch] add step for upgrades, still missing fallback (ec498bd) (Wednesday, 5 April)
Re: [whatwg/fetch] add missing bracket (315cbb7) (Wednesday, 5 April)

Tom Wilkinson

Re: [WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003) (Thursday, 20 April)
Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Thursday, 20 April)
[WICG/webcomponents] [dom-parts] Declarative syntax for creating DOM Parts (Issue #1003) (Thursday, 20 April)
Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Thursday, 20 April)
Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999) (Tuesday, 18 April)

turboborsuk

Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Tuesday, 18 April)

Westbrook Johnson

Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 11 April)
Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 4 April)

xgqfrms

Re: [WICG/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 11 April)

Xiaocheng Hu

Re: [WICG/webcomponents] [scoped-registries] What does `new` mean for elements in multiple registries? (Issue #1007) (Friday, 21 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Tuesday, 18 April)
Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914) (Monday, 17 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Monday, 17 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Friday, 14 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Wednesday, 12 April)
Re: [WICG/webcomponents] [scoped-registries] Proposal for registry extension (Issue #989) (Wednesday, 12 April)
Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987) (Wednesday, 12 April)
Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914) (Tuesday, 11 April)

Xiaoqian Wu

Re: [w3c/uievents-key] Update UAX #15 to the latest version (Issue #59) (Tuesday, 4 April)
Re: [w3c/uievents-key] update the reference to UAX15 (PR #62) (Tuesday, 4 April)
Re: [w3c/uievents-key] update the reference to UAX15 (PR #62) (Tuesday, 4 April)
Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Tuesday, 4 April)

Yehia Mohamed Yehia

Re: [whatwg/webidl] ym962529@gmail.com (Issue #1292) (Tuesday, 11 April)
[whatwg/webidl] ym962529@gmail.com (Issue #1292) (Tuesday, 11 April)

yi-gu

Re: [w3ctag/design-reviews] FedCM Auto Re-authentication API (Issue #813) (Thursday, 20 April)

Yoav Weiss

Re: [whatwg/fetch] Add http method to fetch timing info (PR #1632) (Monday, 17 April)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Tuesday, 11 April)

Yoshisato Yanagisawa

Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Tuesday, 11 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Monday, 3 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Monday, 3 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Monday, 3 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Monday, 3 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Monday, 3 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Monday, 3 April)
Re: [w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Monday, 3 April)
[w3c/ServiceWorker] Avoid executing the code in the All Fetch Listeners Are Empty algorithm. (PR #1676) (Monday, 3 April)

youennf

Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 21 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 20 April)
[whatwg/streams] Add support for TransformStream "owning" writable/readable types (PR #1274) (Wednesday, 19 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Tuesday, 18 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Monday, 17 April)
Re: [whatwg/streams] Add support for writablestream owning type (PR #1272) (Monday, 17 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Monday, 17 April)
[whatwg/streams] Add support for writablestream owning type (PR #1272) (Monday, 17 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Monday, 17 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 14 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 14 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 14 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 14 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 14 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 14 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 14 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Thursday, 13 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Wednesday, 12 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Tuesday, 11 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Tuesday, 11 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Tuesday, 11 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Tuesday, 11 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Tuesday, 11 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Tuesday, 11 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Tuesday, 11 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Tuesday, 11 April)
Re: [whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Tuesday, 11 April)
Re: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185) (Sunday, 9 April)
[whatwg/streams] Add support for ReadableStream "transfer" type (PR #1271) (Sunday, 9 April)
Re: [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185) (Tuesday, 4 April)

Yves Lafon

Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Thursday, 20 April)
Re: [w3ctag/design-reviews] WebAssembly Garbage Collection extensions (Issue #814) (Thursday, 20 April)
Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Monday, 3 April)

Last message date: Sunday, 30 April 2023 23:25:47 UTC