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

7ombie

• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Saturday, 9 December)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Friday, 8 December)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Sunday, 3 December)

alancutter

• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) (Friday, 1 December)

Alex Rudenko

• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Friday, 29 December)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Friday, 8 December)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Monday, 4 December)

Aljbore1

• Re: [w3c/clipboard-apis] Aljbore (Issue #204) (Tuesday, 12 December)
• [w3c/clipboard-apis] Aljbore (Issue #204) (Tuesday, 12 December)

Alphabet

• Re: [w3c/manifest] Procedure for moving manifests and Apps (#850) (Monday, 18 December)

Alvin Ji

• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Monday, 18 December)

Amy Guy

• Re: [w3ctag/design-reviews] `field-sizing` CSS property (Issue #890) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] The CSS `word-break: auto-phrase` property (Issue #891) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] Verifiable Credentials Data Model v2.0 (Issue #860) (Thursday, 14 December)

Anne van Kesteren

• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) (Friday, 29 December)
• Re: [whatwg/fetch] When there is an issue with the URL parameter, fetch does not have any errors (Issue #1730) (Friday, 29 December)
• Re: [whatwg/webidl] Editorial: align with HTML on calling ECMAScript JavaScript (#863) (Thursday, 28 December)
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Thursday, 28 December)
• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) (Thursday, 28 December)
• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) (Thursday, 28 December)
• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) (Friday, 22 December)
• Re: [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) (Thursday, 21 December)
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Thursday, 21 December)
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Thursday, 21 December)
• Re: [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) (Thursday, 21 December)
• Re: [whatwg/fetch] Review Draft Publication: December 2023 (PR #1728) (Monday, 18 December)
• Re: [whatwg/dom] Review Draft Publication: December 2023 (PR #1242) (Monday, 18 December)
• [whatwg/fetch] Review Draft Publication: December 2023 (PR #1728) (Monday, 18 December)
• [whatwg/dom] Review Draft Publication: December 2023 (PR #1242) (Monday, 18 December)
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Friday, 15 December)
• Re: [w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169) (Friday, 15 December)
• Re: [w3c/clipboard-apis] Merge a PR only with explicit implementor consensus (followup) (Issue #207) (Thursday, 14 December)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 14 December)
• Re: [whatwg/dom] Editorial: mark up algorithms about Events (PR #1240) (Thursday, 14 December)
• Re: [whatwg/dom] Editorial: mark up algorithms about Events (PR #1240) (Thursday, 14 December)
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) (Wednesday, 13 December)
• Re: [whatwg/dom] Corresponding attribute for clonable of ShadowRootInit? (Issue #1236) (Wednesday, 13 December)
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) (Wednesday, 13 December)
• Re: [whatwg/webidl] non-readonly [FrozenArray] attributes are footguns as currently specced (#810) (Monday, 11 December)
• Re: [whatwg/url] Properly escape the & (PR #808) (Friday, 8 December)
• Re: [whatwg/url] Properly escape the & (PR #808) (Friday, 8 December)
• Re: [whatwg/url] An opaque-host parser and percent encoding (Issue #806) (Wednesday, 6 December)
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) (Tuesday, 5 December)
• Re: [whatwg/url] A '@' character in the host part of file URLs (Issue #805) (Tuesday, 5 December)
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) (Monday, 4 December)
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) (Monday, 4 December)

Ari Chivukula

• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) (Tuesday, 19 December)

Aric Monary

• Re: [w3c/uievents] Add max number of rows option for keyboard event viewer (PR #365) (Friday, 15 December)
• Re: [w3c/uievents] Add max number of rows option for keyboard event viewer (PR #365) (Friday, 15 December)
• [w3c/uievents] Add max number of rows option for keyboard event viewer (PR #365) (Friday, 15 December)
• [w3c/uievents] Add an option to set the max number of rows shown in the output table for keyboard event viewer (Issue #364) (Friday, 15 December)

Arutiunian Artem

• Re: [w3ctag/design-reviews] Observable API design review (Issue #902) (Saturday, 23 December)

Austin Sullivan

• Re: [w3ctag/design-reviews] The `FileSystemObserver` interface (Issue #868) (Monday, 18 December)
• Re: [w3c/IndexedDB] Editorial: Update a variable with set, not let (PR #415) (Tuesday, 12 December)

ayalatech

• Re: [w3c/FileAPI] Support using AbortController with FileAPI (#159) (Friday, 1 December)

Azarattum

• Re: [w3c/uievents] Expose 'inertial scrolling state' in wheel events (#58) (Saturday, 16 December)

Ben Lesh

• Re: [w3ctag/design-reviews] Observable API design review (Issue #902) (Tuesday, 26 December)

Benoit Charbonnier

• Re: [w3c/uievents] Clearify whether `mouseover`, `mouseout`, `mouseenter` and `mouseleave` are fired or not fired when the target is removed by `mousedown` or `mouseup` (Issue #359) (Wednesday, 13 December)

BlobTheKat

• Re: [w3c/gamepad] Require secure context for gamepad state and events (#120) (Sunday, 31 December)

Brian Kardell

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 27 December)

Bruce B. Anderson

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Tuesday, 26 December)
• [WICG/webcomponents] [Proposal] Stylesheet Observer (Issue #1041) (Thursday, 21 December)

Caleb Williams

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Sunday, 24 December)

caraitto

• Re: [whatwg/webidl] Export "an exception was thrown" (PR #1293) (Wednesday, 13 December)

Chris Cawley

• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Friday, 8 December)

Chris Harrelson

• Re: [w3c/uievents] `beforeinput` and `compositionupdate` event order (Issue #354) (Friday, 8 December)

Chris Lilley

• Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894) (Tuesday, 19 December)

CobraFighter

• [whatwg/dom] Double.sink../admissibleadd|.-symmetrical door-.left true*dot_R (Issue #1241) (Saturday, 16 December)

Dan Clark

• [w3c/editing] Don't enable execCommand commands in EditContext (PR #457) (Monday, 18 December)

Dan Robertson

• Re: [w3c/uievents] Specify wheel event groups (PR #344) (Monday, 4 December)
• Re: [w3c/uievents] Specify wheel event groups (PR #344) (Monday, 4 December)
• Re: [w3c/uievents] Specify wheel event groups (PR #344) (Monday, 4 December)

Daniel Appelquist

• Re: [w3ctag/design-reviews] navigateEvent.sourceElement (Issue #867) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] navigateEvent.sourceElement (Issue #867) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) (Tuesday, 19 December)
• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) (Tuesday, 19 December)
• Re: [w3ctag/design-reviews] Permissions Policy Reporting and Report-Only mode (Issue #909) (Tuesday, 19 December)
• Re: [w3ctag/design-reviews] TAG spec review of Storage Access Heuristics (Issue #919) (Tuesday, 19 December)
• Re: [w3ctag/design-reviews] Web Install API (Issue #888) (Monday, 18 December)
• Re: [w3ctag/design-reviews] The `FileSystemObserver` interface (Issue #868) (Monday, 18 December)

Daniel Ehrenberg

• Re: [whatwg/webidl] Add support for AsyncContext (PR #1369) (Tuesday, 12 December)

Daniel Enrique Aecherli

• [whatwg/dom] Source Code Tool (Issue #1238) (Monday, 11 December)

Danielle Church

• [w3c/ServiceWorker] Unable to insert conditional-request headers in Service Worker? (Issue #1699) (Sunday, 24 December)

Dave Seidman

• Re: [w3c/uievents] Expose 'inertial scrolling state' in wheel events (#58) (Saturday, 16 December)

DavidMulder0

• Re: [w3c/clipboard-apis] Feature detection of web custom format support (Issue #201) (Friday, 8 December)
• Re: [w3c/clipboard-apis] Feature detection of web custom format support (Issue #201) (Friday, 8 December)
• [w3c/clipboard-apis] Feature detection of web custom format support (Issue #201) (Friday, 8 December)

Domenic Denicola

• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) (Wednesday, 20 December)
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) (Wednesday, 20 December)
• Re: [whatwg/webidl] Fix rotated column headers on Distinguishable table (PR #1380) (Wednesday, 20 December)
• Re: [whatwg/webidl] Fix rotated column headers on Distinguishable table (PR #1380) (Wednesday, 20 December)
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) (Wednesday, 13 December)
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) (Wednesday, 13 December)
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) (Wednesday, 13 December)
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) (Wednesday, 13 December)
• Re: [whatwg/streams] Define generic operation for GetDesiredSize? (#745) (Wednesday, 13 December)
• Re: [whatwg/streams] Define generic operation for GetDesiredSize? (#745) (Wednesday, 13 December)
• Re: [whatwg/streams] Put test results in margins of the spec (#216) (Wednesday, 13 December)
• Re: [whatwg/streams] Put test results in margins of the spec (#216) (Wednesday, 13 December)
• Re: [whatwg/streams] Export the "error the stream" concept? (#679) (Wednesday, 13 December)
• Re: [whatwg/streams] Export the "error the stream" concept? (#679) (Wednesday, 13 December)

Dominique Hazael-Massieux

• Re: [w3c/clipboard-apis] Aljbore (Issue #204) (Tuesday, 12 December)

Edgar Chen

• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Wednesday, 27 December)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Wednesday, 27 December)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Wednesday, 27 December)

Eduardo Pinho

• Re: [whatwg/fetch] Option to fetch raw byte as is. (without decompressing) (Issue #1524) (Tuesday, 12 December)

Eemeli Aro

• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Monday, 11 December)

Elad Alon

• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) (Friday, 1 December)

Ethan Resnick

• Re: [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) (Thursday, 21 December)
• [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) (Thursday, 21 December)

Evan Stade

• Re: [w3c/clipboard-apis] Read Blob data for the supported formats on-demand during getType. (Issue #191) (Tuesday, 12 December)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Tuesday, 12 December)
• [w3c/clipboard-apis] References to permissions (Issue #205) (Tuesday, 12 December)
• Re: [w3c/clipboard-apis] Parallelism and task sources (Issue #202) (Tuesday, 12 December)
• [w3c/clipboard-apis] algorithms don't enforce focus requirement (Issue #203) (Tuesday, 12 December)
• [w3c/clipboard-apis] Parallelism and task sources (Issue #202) (Tuesday, 12 December)

ExE Boss

• Re: [whatwg/webidl] Suggestion: forbid ECMA-262/402-defined global names for some named constructs (Issue #1331) (Sunday, 31 December)

Federico Brigante

• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) (Saturday, 30 December)

Gabriel Brito

• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Saturday, 16 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Thursday, 14 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Thursday, 14 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Friday, 8 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Friday, 8 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Friday, 8 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Friday, 8 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Thursday, 7 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Thursday, 7 December)

Gabriel Corona

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Monday, 11 December)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Sunday, 10 December)

Gary Kacmarcik

• Re: [w3c/uievents] Add an option to set the max number of rows shown in the output table for keyboard event viewer (Issue #364) (Friday, 15 December)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Monday, 4 December)
• Re: [w3c/uievents] Added a new event to communicate context menu dismissal. (PR #322) (Monday, 4 December)
• Re: [w3c/uievents] Use `USVString` for input and composition events (PR #351) (Monday, 4 December)
• Re: [w3c/uievents] Use `USVString` for input and composition events (Issue #352) (Monday, 4 December)
• Re: [w3c/uievents] Use `USVString` for input and composition events (PR #351) (Monday, 4 December)
• Re: [w3c/uievents] Use `USVString` for input and composition events (PR #351) (Monday, 4 December)
• Re: [w3c/uievents] Wheel event groups are not defined (Issue #338) (Monday, 4 December)
• Re: [w3c/uievents] Specify wheel event groups (PR #344) (Monday, 4 December)

Greg Bernstein

• [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) (Friday, 15 December)

Hadley Beeman

• Re: [w3ctag/design-reviews] systemEntropy addition to PerformanceNavigationTiming (Issue #878) (Monday, 18 December)

Hawk Ticehurst

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Sunday, 31 December)

Hayato Ito

• Re: [whatwg/url] An opaque-host parser and percent encoding (Issue #806) (Wednesday, 6 December)
• Re: [whatwg/url] An opaque-host parser and percent encoding (Issue #806) (Wednesday, 6 December)
• [whatwg/url] An opaque-host parser and percent encoding (Issue #806) (Wednesday, 6 December)
• [whatwg/url] A '@' character in the host part of file URLs (Issue #805) (Tuesday, 5 December)

Ian Clelland

• Re: [w3ctag/design-reviews] Permissions Policy Reporting and Report-Only mode (Issue #909) (Tuesday, 19 December)

ijesneo611

• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Saturday, 23 December)
• [whatwg/webidl] check 6 (Issue #1382) (Saturday, 23 December)

iteriani

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Monday, 11 December)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 8 December)

Jackie(Guokai) Han

• Re: [w3c/ServiceWorker] How can I control and manage socket events in Service Workers? (Issue #1697) (Friday, 22 December)
• [w3c/ServiceWorker] dynamically registered event listeners for extension service worker (Issue #1698) (Friday, 22 December)

James

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Tuesday, 12 December)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Tuesday, 12 December)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Monday, 11 December)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Sunday, 10 December)

James Addison

• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) (Friday, 22 December)
• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) (Friday, 22 December)
• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) (Friday, 22 December)

James Howard

• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 14 December)

jamiewalch

• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Tuesday, 19 December)
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Wednesday, 6 December)

Jefri Reynaldi

• Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204) (Saturday, 16 December)

Jeremy Roman

• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Wednesday, 27 December)
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Wednesday, 27 December)
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Wednesday, 27 December)
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Wednesday, 20 December)
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) (Wednesday, 20 December)
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Tuesday, 19 December)
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Tuesday, 19 December)
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Tuesday, 19 December)
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Tuesday, 19 December)
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Tuesday, 19 December)
• [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) (Tuesday, 19 December)
• Re: [whatwg/webidl] Editorial: align with HTML on calling ECMAScript JavaScript (#863) (Tuesday, 19 December)
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) (Tuesday, 19 December)
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) (Tuesday, 19 December)
• [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) (Tuesday, 19 December)

Joe Pea

• Re: [whatwg/dom] `childList` records across multiple `MutationObserver`s are observed in fundamentally incorrect order (Issue #1111) (Friday, 22 December)
• [WICG/webcomponents] making a SlotChangeObserver similar to MutationObserver childList (Issue #1042) (Friday, 22 December)
• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) (Tuesday, 19 December)

Joey Arhar

• Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) (Monday, 18 December)

Johannes Wilm

• Re: [w3c/editing] Don't enable execCommand commands in EditContext (PR #457) (Tuesday, 19 December)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Tuesday, 12 December)

Joshua Bell

• Re: [w3c/IndexedDB] 53db883f495fc71bb5168f0e7e91561af1005b9 (Issue #414) (Tuesday, 19 December)
• Re: [w3c/IndexedDB] IDL interface for the intersection of IDBObjectStore and IDBIndex? (#367) (Tuesday, 19 December)
• Re: [w3c/IndexedDB] TPAC 2023 status report (Issue #413) (Tuesday, 19 December)
• Re: [w3c/IndexedDB] Editorial: Update a variable with set, not let (PR #415) (Tuesday, 12 December)
• Re: [w3c/IndexedDB] Editorial: Update a variable with set, not let (PR #415) (Monday, 11 December)
• Re: [w3c/IndexedDB] Editorial: Update a variable with set, not let (PR #415) (Monday, 11 December)
• [w3c/IndexedDB] Editorial: Update a variable with set, not let (PR #415) (Monday, 11 December)
• Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343) (Thursday, 7 December)

juj

• Re: [w3c/gamepad] Please don't restrict to a secure context (#145) (Monday, 11 December)

Justin Fagnani

• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Friday, 8 December)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Thursday, 7 December)

Kagami Sascha Rosylight

• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Wednesday, 27 December)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Wednesday, 27 December)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Friday, 15 December)
• [w3c/clipboard-apis] Merge a PR only with explicit implementor consensus (followup) (Issue #207) (Thursday, 14 December)
• Re: [w3c/clipboard-apis] Parallelism and task sources (Issue #202) (Tuesday, 12 December)
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) (Monday, 11 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Tuesday, 5 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Tuesday, 5 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Monday, 4 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Monday, 4 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Monday, 4 December)
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) (Monday, 4 December)
• [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) (Saturday, 2 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 2 December)
• [whatwg/fetch] RequestInit::priority lacks corresponding Request::priority attribute (Issue #1726) (Saturday, 2 December)
• Re: [whatwg/dom] Corresponding attribute for clonable of ShadowRootInit? (Issue #1236) (Friday, 1 December)

Karl

• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) (Friday, 29 December)
• Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784) (Wednesday, 6 December)
• Re: [whatwg/url] A '@' character in the host part of file URLs (Issue #805) (Tuesday, 5 December)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Saturday, 2 December)

Keith Cirkel

• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Friday, 15 December)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Wednesday, 13 December)
• Re: [whatwg/dom] Source Code Tool (Issue #1238) (Monday, 11 December)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Sunday, 10 December)
• [w3ctag/design-reviews] Invokers API (Issue #920) (Friday, 8 December)

Kevin Cox

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Monday, 11 December)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Monday, 11 December)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Monday, 11 December)

Klaus Frank

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Thursday, 14 December)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Saturday, 2 December)

Kyra Seevers

• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) (Wednesday, 13 December)

Lea Verou

• Re: [w3ctag/design-reviews] Extending the PointerEvent with Unique DeviceId Attribute (Issue #880) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] Extending the PointerEvent with Unique DeviceId Attribute (Issue #880) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) (Monday, 18 December)
• Re: [w3ctag/design-reviews] Spec review for CSS Nesting (Issue #791) (Monday, 18 December)
• Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) (Monday, 18 December)
• Re: [w3ctag/design-reviews] Extending the PointerEvent with Unique DeviceId Attribute (Issue #880) (Monday, 18 December)

Leo Kettmeir

• Re: [whatwg/streams] add TrasformStream finally callback (PR #1231) (Thursday, 21 December)
• Re: [whatwg/streams] add TrasformStream finally callback (PR #1231) (Thursday, 21 December)

Luca Casonato

• [whatwg/fetch] Automatic decompression should sanitize `Content-Encoding` and `Content-Length` headers from the response (Issue #1729) (Thursday, 21 December)

mangelozzi

• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Friday, 15 December)

Manu Sporny

• Re: [w3ctag/design-reviews] Verifiable Credentials Data Model v2.0 (Issue #860) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) (Monday, 18 December)

Marcos Cáceres

• Re: [w3c/IndexedDB] Could we drop the spec versioning? (Issue #402) (Thursday, 21 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 20 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 19 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)
• [w3c/gamepad] Add trackpad button support (Issue #191) (Tuesday, 19 December)
• Re: [w3c/push-api] check and consume user activation (PR #348) (Friday, 15 December)
• Re: [w3c/push-api] Expose pushManager on Navigator (PR #368) (Friday, 15 December)
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Friday, 15 December)
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Friday, 15 December)
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Friday, 15 December)
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Friday, 15 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Friday, 15 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Friday, 15 December)
• Re: [w3c/push-api] check and consume user activation (PR #348) (Thursday, 14 December)
• Re: [w3c/push-api] Editorial: Introduce 'push subscription owner' concept (PR #367) (Thursday, 14 December)
• Re: [w3c/push-api] Editorial: Introduce 'push subscription owner' concept (PR #367) (Thursday, 14 December)
• Re: [w3c/push-api] Expose pushManager on Navigator (PR #368) (Thursday, 14 December)
• [w3c/push-api] Navigator.push manager (PR #368) (Thursday, 14 December)
• Re: [w3c/push-api] Editorial: Introduce 'push subscription owner' concept (PR #367) (Thursday, 14 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 14 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 14 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 14 December)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 14 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• [w3c/push-api] Editorial: Introduce 'push subscription owner' concept (PR #367) (Monday, 11 December)
• [w3c/push-api] Editorial: fix references to Fetch and Web Sockets (PR #366) (Monday, 11 December)
• Re: [w3c/push-api] WPT testability (Issue #365) (Friday, 8 December)
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Friday, 8 December)
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Friday, 8 December)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Friday, 8 December)
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Wednesday, 6 December)
• [whatwg/fullscreen] Add keyboard locking option (PR #232) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Wednesday, 6 December)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Monday, 4 December)
• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) (Friday, 1 December)
• [w3c/permissions] Editorial: add example of prompt timing out (PR #432) (Friday, 1 December)
• Re: [w3c/permissions] Can 'prompt the user to choose' return deny after some implementation specific timeout? (Issue #430) (Friday, 1 December)
• Re: [w3c/permissions] Can 'prompt the user to choose' return deny after some implementation specific timeout? (Issue #430) (Friday, 1 December)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Friday, 1 December)

Mario Hamann

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 20 December)

Mark Nottingham

• Re: [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) (Friday, 22 December)
• Re: [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) (Thursday, 21 December)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 20 December)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Tuesday, 12 December)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Monday, 11 December)

Martin Thomson

• Re: [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) (Monday, 18 December)
• Re: [w3c/push-api] Expose pushManager on Navigator (PR #368) (Thursday, 14 December)
• Re: [w3c/push-api] Editorial: fix references to Fetch and Web Sockets (PR #366) (Monday, 11 December)
• Re: [w3c/push-api] Editorial: Introduce 'push subscription owner' concept (PR #367) (Monday, 11 December)
• Re: [w3c/push-api] Editorial: fix references to Fetch and Web Sockets (PR #366) (Monday, 11 December)
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Monday, 4 December)

Mason Freed

• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Friday, 15 December)
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Friday, 15 December)

Matt Reynolds

• Re: [w3c/gamepad] Make permissions policy allow list "all" (Issue #155) (Friday, 15 December)
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Friday, 15 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Thursday, 14 December)

Matthew Phillips

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 27 December)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 20 December)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Monday, 11 December)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 8 December)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 8 December)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 7 December)

Matthieu Sieben

• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Thursday, 21 December)

meacer

• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 14 December)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 14 December)
• [whatwg/fetch] Referrer determination should be done on updated URLs in main fetch (Issue #1727) (Thursday, 14 December)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 14 December)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Friday, 1 December)

Mike Jackson

• Re: [w3ctag/design-reviews] systemEntropy addition to PerformanceNavigationTiming (Issue #878) (Tuesday, 12 December)

Mike Taylor

• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Friday, 8 December)
• Re: [w3c/permissions] Can 'prompt the user to choose' return deny after some implementation specific timeout? (Issue #430) (Friday, 1 December)
• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) (Friday, 1 December)
• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) (Friday, 1 December)
• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) (Friday, 1 December)
• Re: [w3c/permissions] Can 'prompt the user to choose' return deny after some implementation specific timeout? (Issue #430) (Friday, 1 December)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Friday, 1 December)

mithumiah231

• Re: [whatwg/webidl] Web idl standard (Issue #1376) (Saturday, 2 December)
• [whatwg/webidl] Web idl standard (Issue #1376) (Saturday, 2 December)

mitzos87

• Re: [w3ctag/design-reviews] Update 010-specification-review.md (PR #844) (Monday, 4 December)

Ms2ger

• [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Wednesday, 20 December)
• [whatwg/dom] Editorial: mark up algorithms about Events (PR #1240) (Wednesday, 13 December)
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) (Wednesday, 13 December)
• [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) (Wednesday, 13 December)
• [whatwg/dom] Add support for AsyncContext in dispatching Events (PR #1239) (Tuesday, 12 December)
• Re: [whatwg/webidl] Add support for AsyncContext (PR #1369) (Tuesday, 12 December)
• [whatwg/webidl] Truncation in "convert a Web IDL arguments list to an ECMAScript arguments list" seems (potentially) incorrect (Issue #1377) (Tuesday, 12 December)

Nate Moore

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 19 December)

Noam Rosenthal

• Re: [w3ctag/design-reviews] Long Animation Frame API (LoAF) (Issue #911) (Wednesday, 20 December)
• [w3ctag/design-reviews] Navigation Activation Info (Issue #921) (Wednesday, 13 December)

Nolan Lawson

• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Wednesday, 13 December)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Thursday, 7 December)

nolimit042

• Re: [whatwg/dom] CONTACTLOEI (Issue #1243) (Tuesday, 19 December)
• [whatwg/dom] CONTACTLOEI (Issue #1243) (Tuesday, 19 December)

nononokam

• [w3ctag/design-reviews] Adding a close event to MessagePort API (Issue #923) (Tuesday, 19 December)

Oliver Terbu

• Re: [w3ctag/design-reviews] Verifiable Credentials Data Model v2.0 (Issue #860) (Thursday, 14 December)

otabek-git

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Thursday, 21 December)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 20 December)

Oxford Harrison

• Re: [whatwg/dom] `childList` records across multiple `MutationObserver`s are observed in fundamentally incorrect order (Issue #1111) (Tuesday, 19 December)

Patrick Nelson

• Re: [whatwg/dom] Custom element callback/promise for "connected and parsed" (#662) (Saturday, 9 December)

Peter Linss

• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Monday, 18 December)
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Monday, 18 December)
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) (Monday, 11 December)
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Friday, 1 December)

Philipp Hancke

• Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912) (Tuesday, 5 December)
• Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912) (Tuesday, 5 December)

Randall Leeds

• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Wednesday, 27 December)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Wednesday, 27 December)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Wednesday, 27 December)

rclaretianafm105

• [whatwg/url] RADIO (Issue #807) (Thursday, 7 December)

Rein Petersen

• [w3c/DOM-Parsing] DOM Parsing from stream (Issue #77) (Thursday, 21 December)

Rik Cabanier

• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 12 December)

Rob Eisenberg

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 27 December)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Wednesday, 13 December)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 8 December)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 7 December)

Rossen Atanassov

• Re: [w3ctag/design-reviews] Long Animation Frame API (LoAF) (Issue #911) (Wednesday, 20 December)
• Re: [w3ctag/design-reviews] Intersection Observer Scroll Margin (Issue #905) (Monday, 11 December)
• Re: [w3ctag/design-reviews] Intersection Observer Scroll Margin (Issue #905) (Monday, 11 December)
• Re: [w3ctag/design-reviews] @page margin boxes (Issue #918) (Monday, 11 December)
• Re: [w3ctag/design-reviews] @page margin boxes (Issue #918) (Monday, 11 December)

Ryosuke Niwa

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 19 December)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Monday, 18 December)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Monday, 18 December)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Wednesday, 13 December)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Monday, 11 December)

Sahir Vellani

• Re: [w3ctag/design-reviews] Extending the PointerEvent with Unique DeviceId Attribute (Issue #880) (Tuesday, 19 December)

Sanket Joshi

• [w3ctag/design-reviews] New attribute to control UA-provided writing assistance (Issue #924) (Saturday, 23 December)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Friday, 22 December)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Friday, 22 December)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Friday, 22 December)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Friday, 22 December)

Sasha Firsov

• Re: [WICG/webcomponents] [idea] HTML Modules: Allow exporting without a script (#863) (Thursday, 7 December)

Sean Feng

• [w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169) (Thursday, 14 December)

Sergio

• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 19 December)

Shahriar Nasseri

• Re: [whatwg/webidl] Meta: improve "distinguishable" table column header rotation (8e9affa) (Thursday, 21 December)

Simon Pieters

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Thursday, 21 December)
• Re: [w3c/clipboard-apis] Merge a PR only with explicit implementor consensus (followup) (Issue #207) (Monday, 18 December)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Tuesday, 5 December)
• Re: [w3c/uievents] Specify wheel event groups (PR #344) (Monday, 4 December)

smaug----

• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Friday, 15 December)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Thursday, 14 December)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Wednesday, 13 December)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Friday, 1 December)

snianu

• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Friday, 22 December)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Friday, 22 December)
• Re: [w3c/editing] Don't enable execCommand commands in EditContext (PR #457) (Tuesday, 19 December)
• Re: [w3c/editing] Don't enable execCommand commands in EditContext (PR #457) (Tuesday, 19 December)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Friday, 15 December)
• [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Friday, 15 December)
• Re: [w3c/clipboard-apis] Merge a PR only with explicit implementor consensus (followup) (Issue #207) (Friday, 15 December)
• Re: [w3c/clipboard-apis] Merge a PR only with explicit implementor consensus (followup) (Issue #207) (Friday, 15 December)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Friday, 15 December)
• Re: [w3c/clipboard-apis] Topic: ‘unsanitized’ option to allow developers to opt-out of UA-provided sanitization (Issue #206) (Friday, 15 December)
• Re: [w3c/clipboard-apis] Read Blob data for the supported formats on-demand during getType. (Issue #191) (Wednesday, 13 December)
• [w3c/clipboard-apis] Topic: ‘unsanitized’ option to allow developers to opt-out of UA-provided sanitization (Issue #206) (Wednesday, 13 December)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Tuesday, 12 December)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Tuesday, 12 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Tuesday, 5 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Tuesday, 5 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Monday, 4 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Monday, 4 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Monday, 4 December)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Monday, 4 December)

stefanbeigel

• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) (Friday, 29 December)
• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) (Wednesday, 27 December)
• [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) (Friday, 22 December)

Steve Orvell

• [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Friday, 8 December)

Sun Shin

• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Tuesday, 19 December)
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Tuesday, 19 December)
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Wednesday, 6 December)
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Friday, 1 December)

Tab Atkins Jr.

• [whatwg/webidl] Fix rotated column headers on Distinguishable table (PR #1380) (Tuesday, 19 December)
• [whatwg/url] Properly escape the & (PR #808) (Thursday, 7 December)

Tanancha Prawanna

• [whatwg/webidl] Tanancha prawanna (Issue #1383) (Wednesday, 27 December)

tcaptan-cr

• Re: [w3ctag/design-reviews] Intersection Observer Scroll Margin (Issue #905) (Wednesday, 13 December)

Tim Nguyen

• Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) (Monday, 18 December)
• Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) (Monday, 18 December)

Tom Schuster

• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) (Wednesday, 13 December)
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) (Wednesday, 13 December)

Tom Wilkinson

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 7 December)

Val Packett

• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) (Friday, 22 December)

vmpstr

• Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886) (Friday, 15 December)

wattroll

• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Friday, 22 December)

Westbrook Johnson

• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Friday, 22 December)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Monday, 18 December)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Friday, 15 December)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Monday, 11 December)

William Faircloth

• Re: [w3c/gamepad] Add gamepad light indicator extension (#143) (Saturday, 23 December)

Worst One

• Re: [whatwg/fetch] When there is an issue with the URL parameter, fetch does not have any errors (Issue #1730) (Friday, 29 December)
• [whatwg/fetch] When there is an issue with the URL parameter, fetch does not have any errors (Issue #1730) (Friday, 29 December)

Yoav Weiss

• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Monday, 4 December)
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Friday, 1 December)

youennf

• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) (Friday, 1 December)

Zamralik

• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Monday, 18 December)

Last message date: Sunday, 31 December 2023 14:23:28 UTC