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

Sunday, 31 December 2023

• Re: [w3c/gamepad] Require secure context for gamepad state and events (#120) BlobTheKat
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) Hawk Ticehurst
• Re: [whatwg/webidl] Suggestion: forbid ECMA-262/402-defined global names for some named constructs (Issue #1331) ExE Boss

Saturday, 30 December 2023

• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) Federico Brigante

Friday, 29 December 2023

• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) Karl
• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) 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) stefanbeigel
• Re: [whatwg/fetch] When there is an issue with the URL parameter, fetch does not have any errors (Issue #1730) Anne van Kesteren
• Re: [whatwg/fetch] When there is an issue with the URL parameter, fetch does not have any errors (Issue #1730) Worst One
• [whatwg/fetch] When there is an issue with the URL parameter, fetch does not have any errors (Issue #1730) Worst One
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) Alex Rudenko

Thursday, 28 December 2023

• Re: [whatwg/webidl] Editorial: align with HTML on calling ECMAScript JavaScript (#863) Anne van Kesteren
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) 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) 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) Anne van Kesteren

Wednesday, 27 December 2023

• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) Randall Leeds
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) Kagami Sascha Rosylight
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) Edgar Chen
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) Edgar Chen
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Rob Eisenberg
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) Randall Leeds
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) Edgar Chen
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Brian Kardell
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Matthew Phillips
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Jeremy Roman
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Jeremy Roman
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Jeremy Roman
• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) stefanbeigel
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) Kagami Sascha Rosylight
• [whatwg/webidl] Tanancha prawanna (Issue #1383) Tanancha Prawanna
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) Randall Leeds

Tuesday, 26 December 2023

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) Bruce B. Anderson
• Re: [w3ctag/design-reviews] Observable API design review (Issue #902) Ben Lesh

Sunday, 24 December 2023

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Caleb Williams
• [w3c/ServiceWorker] Unable to insert conditional-request headers in Service Worker? (Issue #1699) Danielle Church

Saturday, 23 December 2023

• Re: [w3c/gamepad] Add gamepad light indicator extension (#143) William Faircloth
• Re: [w3ctag/design-reviews] Observable API design review (Issue #902) Arutiunian Artem
• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) ijesneo611
• [whatwg/webidl] check 6 (Issue #1382) ijesneo611
• [w3ctag/design-reviews] New attribute to control UA-provided writing assistance (Issue #924) Sanket Joshi

Friday, 22 December 2023

• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) James Addison
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) Sanket Joshi
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) Sanket Joshi
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) Sanket Joshi
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) snianu
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) Sanket Joshi
• Re: [whatwg/dom] `childList` records across multiple `MutationObserver`s are observed in fundamentally incorrect order (Issue #1111) Joe Pea
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) snianu
• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) Val Packett
• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) Anne van Kesteren
• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) James Addison
• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) James Addison
• [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) stefanbeigel
• Re: [w3c/ServiceWorker] How can I control and manage socket events in Service Workers? (Issue #1697) Jackie(Guokai) Han
• [w3c/ServiceWorker] dynamically registered event listeners for extension service worker (Issue #1698) Jackie(Guokai) Han
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) wattroll
• [WICG/webcomponents] making a SlotChangeObserver similar to MutationObserver childList (Issue #1042) Joe Pea
• Re: [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) Mark Nottingham
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Westbrook Johnson

Thursday, 21 December 2023

• [whatwg/fetch] Automatic decompression should sanitize `Content-Encoding` and `Content-Length` headers from the response (Issue #1729) Luca Casonato
• Re: [whatwg/webidl] Meta: improve "distinguishable" table column header rotation (8e9affa) Shahriar Nasseri
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) Simon Pieters
• [w3c/DOM-Parsing] DOM Parsing from stream (Issue #77) Rein Petersen
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) Matthieu Sieben
• [WICG/webcomponents] [Proposal] Stylesheet Observer (Issue #1041) Bruce B. Anderson
• Re: [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) Ethan Resnick
• Re: [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) Anne van Kesteren
• Re: [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) Mark Nottingham
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Anne van Kesteren
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Anne van Kesteren
• Re: [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) Anne van Kesteren
• [whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809) Ethan Resnick
• Re: [w3c/IndexedDB] Could we drop the spec versioning? (Issue #402) Marcos Cáceres
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) otabek-git
• Re: [whatwg/streams] add TrasformStream finally callback (PR #1231) Leo Kettmeir
• Re: [whatwg/streams] add TrasformStream finally callback (PR #1231) Leo Kettmeir

Wednesday, 20 December 2023

• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3ctag/design-reviews] Verifiable Credentials Data Model v2.0 (Issue #860) Manu Sporny
• Re: [w3ctag/design-reviews] `field-sizing` CSS property (Issue #890) Amy Guy
• Re: [w3ctag/design-reviews] Extending the PointerEvent with Unique DeviceId Attribute (Issue #880) Lea Verou
• Re: [w3ctag/design-reviews] Extending the PointerEvent with Unique DeviceId Attribute (Issue #880) Lea Verou
• Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894) Amy Guy
• Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894) Amy Guy
• Re: [w3ctag/design-reviews] navigateEvent.sourceElement (Issue #867) Daniel Appelquist
• Re: [w3ctag/design-reviews] navigateEvent.sourceElement (Issue #867) Daniel Appelquist
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Mario Hamann
• Re: [w3ctag/design-reviews] The CSS `word-break: auto-phrase` property (Issue #891) Amy Guy
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) Peter Linss
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) Peter Linss
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Jeremy Roman
• [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) Ms2ger
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) Jeremy Roman
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) otabek-git
• Re: [w3ctag/design-reviews] Long Animation Frame API (LoAF) (Issue #911) Noam Rosenthal
• Re: [w3ctag/design-reviews] Long Animation Frame API (LoAF) (Issue #911) Rossen Atanassov
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Matthew Phillips
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) Domenic Denicola
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) Domenic Denicola
• Re: [whatwg/webidl] Fix rotated column headers on Distinguishable table (PR #1380) Domenic Denicola
• Re: [whatwg/webidl] Fix rotated column headers on Distinguishable table (PR #1380) Domenic Denicola
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) Mark Nottingham
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji

Tuesday, 19 December 2023

• [whatwg/webidl] Fix rotated column headers on Distinguishable table (PR #1380) Tab Atkins Jr.
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Ryosuke Niwa
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) Nate Moore
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Jeremy Roman
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Jeremy Roman
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Jeremy Roman
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Jeremy Roman
• Re: [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Jeremy Roman
• [whatwg/webidl] Editorial: Refer to ECMA-262 as JavaScript rather than ECMAScript (PR #1379) Jeremy Roman
• Re: [whatwg/webidl] Editorial: align with HTML on calling ECMAScript JavaScript (#863) Jeremy Roman
• Re: [w3ctag/design-reviews] Relative Color Syntax (RCS) (Issue #894) Chris Lilley
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) Jeremy Roman
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) Jeremy Roman
• [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) Jeremy Roman
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) Sun Shin
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) jamiewalch
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) Sun Shin
• Re: [w3ctag/design-reviews] Extending the PointerEvent with Unique DeviceId Attribute (Issue #880) Sahir Vellani
• Re: [whatwg/dom] `childList` records across multiple `MutationObserver`s are observed in fundamentally incorrect order (Issue #1111) Oxford Harrison
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Sergio
• Re: [w3ctag/design-reviews] Permissions Policy Reporting and Report-Only mode (Issue #909) Ian Clelland
• Re: [whatwg/dom] CONTACTLOEI (Issue #1243) nolimit042
• [whatwg/dom] CONTACTLOEI (Issue #1243) nolimit042
• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) Ari Chivukula
• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) Daniel Appelquist
• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) Daniel Appelquist
• Re: [w3ctag/design-reviews] Permissions Policy Reporting and Report-Only mode (Issue #909) Daniel Appelquist
• Re: [w3ctag/design-reviews] TAG spec review of Storage Access Heuristics (Issue #919) Daniel Appelquist
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/editing] Don't enable execCommand commands in EditContext (PR #457) Johannes Wilm
• [w3ctag/design-reviews] Adding a close event to MessagePort API (Issue #923) nononokam
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito
• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) Joe Pea
• [w3c/gamepad] Add trackpad button support (Issue #191) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/IndexedDB] 53db883f495fc71bb5168f0e7e91561af1005b9 (Issue #414) Joshua Bell
• Re: [w3c/IndexedDB] IDL interface for the intersection of IDBObjectStore and IDBIndex? (#367) Joshua Bell
• Re: [w3c/IndexedDB] TPAC 2023 status report (Issue #413) Joshua Bell
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• Re: [w3c/editing] Don't enable execCommand commands in EditContext (PR #457) snianu
• Re: [w3c/editing] Don't enable execCommand commands in EditContext (PR #457) snianu

Monday, 18 December 2023

• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Alvin Ji
• [w3c/editing] Don't enable execCommand commands in EditContext (PR #457) Dan Clark
• Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) Joey Arhar
• Re: [w3c/manifest] Procedure for moving manifests and Apps (#850) Alphabet
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Ryosuke Niwa
• Re: [w3ctag/design-reviews] The `FileSystemObserver` interface (Issue #868) Austin Sullivan
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Westbrook Johnson
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Ryosuke Niwa
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) Peter Linss
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) Peter Linss
• Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) Tim Nguyen
• Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) Lea Verou
• Re: [w3ctag/design-reviews] Spec review for CSS Nesting (Issue #791) Lea Verou
• Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) Tim Nguyen
• Re: [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) Lea Verou
• Re: [w3ctag/design-reviews] Web Install API (Issue #888) Daniel Appelquist
• Re: [w3ctag/design-reviews] Extending the PointerEvent with Unique DeviceId Attribute (Issue #880) Lea Verou
• Re: [w3ctag/design-reviews] The `FileSystemObserver` interface (Issue #868) Daniel Appelquist
• Re: [w3ctag/design-reviews] systemEntropy addition to PerformanceNavigationTiming (Issue #878) Hadley Beeman
• Re: [w3c/clipboard-apis] Merge a PR only with explicit implementor consensus (followup) (Issue #207) Simon Pieters
• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) Zamralik
• Re: [whatwg/fetch] Review Draft Publication: December 2023 (PR #1728) Anne van Kesteren
• Re: [whatwg/dom] Review Draft Publication: December 2023 (PR #1242) Anne van Kesteren
• [whatwg/fetch] Review Draft Publication: December 2023 (PR #1728) Anne van Kesteren
• [whatwg/dom] Review Draft Publication: December 2023 (PR #1242) Anne van Kesteren
• Re: [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) Manu Sporny
• Re: [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) Martin Thomson

Saturday, 16 December 2023

• Re: [w3c/uievents] Expose 'inertial scrolling state' in wheel events (#58) Dave Seidman
• Re: [w3c/uievents] Expose 'inertial scrolling state' in wheel events (#58) Azarattum
• Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204) Jefri Reynaldi
• [whatwg/dom] Double.sink../admissibleadd|.-symmetrical door-.left true*dot_R (Issue #1241) CobraFighter
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito

Friday, 15 December 2023

• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) snianu
• [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) snianu
• Re: [w3c/uievents] Add an option to set the max number of rows shown in the output table for keyboard event viewer (Issue #364) Gary Kacmarcik
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Westbrook Johnson
• Re: [w3c/gamepad] Make permissions policy allow list "all" (Issue #155) Matt Reynolds
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) Matt Reynolds
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) Kagami Sascha Rosylight
• Re: [w3c/clipboard-apis] Merge a PR only with explicit implementor consensus (followup) (Issue #207) snianu
• Re: [w3c/clipboard-apis] Merge a PR only with explicit implementor consensus (followup) (Issue #207) snianu
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) snianu
• Re: [w3c/clipboard-apis] Topic: ‘unsanitized’ option to allow developers to opt-out of UA-provided sanitization (Issue #206) snianu
• [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) Greg Bernstein
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) Keith Cirkel
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) Mason Freed
• Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886) vmpstr
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) mangelozzi
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) Anne van Kesteren
• Re: [w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169) Anne van Kesteren
• Re: [w3c/uievents] Add max number of rows option for keyboard event viewer (PR #365) Aric Monary
• Re: [w3c/uievents] Add max number of rows option for keyboard event viewer (PR #365) Aric Monary
• [w3c/uievents] Add max number of rows option for keyboard event viewer (PR #365) Aric Monary
• [w3c/uievents] Add an option to set the max number of rows shown in the output table for keyboard event viewer (Issue #364) Aric Monary
• Re: [w3c/push-api] check and consume user activation (PR #348) Marcos Cáceres
• Re: [w3c/push-api] Expose pushManager on Navigator (PR #368) Marcos Cáceres
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) Marcos Cáceres
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) Marcos Cáceres
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) Marcos Cáceres
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) Mason Freed
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) smaug----
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres

Thursday, 14 December 2023

• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Matt Reynolds
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito
• Re: [w3c/push-api] Expose pushManager on Navigator (PR #368) Martin Thomson
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) smaug----
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) meacer
• [w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169) Sean Feng
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) meacer
• [whatwg/fetch] Referrer determination should be done on updated URLs in main fetch (Issue #1727) meacer
• Re: [w3ctag/design-reviews] Verifiable Credentials Data Model v2.0 (Issue #860) Oliver Terbu
• Re: [w3ctag/design-reviews] Verifiable Credentials Data Model v2.0 (Issue #860) Amy Guy
• Re: [w3c/clipboard-apis] Merge a PR only with explicit implementor consensus (followup) (Issue #207) Anne van Kesteren
• [w3c/clipboard-apis] Merge a PR only with explicit implementor consensus (followup) (Issue #207) Kagami Sascha Rosylight
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) Anne van Kesteren
• Re: [whatwg/dom] Editorial: mark up algorithms about Events (PR #1240) Anne van Kesteren
• Re: [whatwg/dom] Editorial: mark up algorithms about Events (PR #1240) Anne van Kesteren
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) Klaus Frank
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) James Howard
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) meacer
• Re: [w3c/push-api] check and consume user activation (PR #348) Marcos Cáceres
• Re: [w3c/push-api] Editorial: Introduce 'push subscription owner' concept (PR #367) Marcos Cáceres
• Re: [w3c/push-api] Editorial: Introduce 'push subscription owner' concept (PR #367) Marcos Cáceres
• Re: [w3c/push-api] Expose pushManager on Navigator (PR #368) Marcos Cáceres
• [w3c/push-api] Navigator.push manager (PR #368) Marcos Cáceres
• Re: [w3c/push-api] Editorial: Introduce 'push subscription owner' concept (PR #367) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) Marcos Cáceres

Wednesday, 13 December 2023

• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Nolan Lawson
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Rob Eisenberg
• Re: [whatwg/webidl] Export "an exception was thrown" (PR #1293) caraitto
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) smaug----
• Re: [w3c/clipboard-apis] Read Blob data for the supported formats on-demand during getType. (Issue #191) snianu
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Keith Cirkel
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) Kyra Seevers
• [whatwg/dom] Editorial: mark up algorithms about Events (PR #1240) Ms2ger
• 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) Benoit Charbonnier
• [w3ctag/design-reviews] Navigation Activation Info (Issue #921) Noam Rosenthal
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) Ms2ger
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) Domenic Denicola
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) Domenic Denicola
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) Domenic Denicola
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) Domenic Denicola
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) Tom Schuster
• Re: [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) Tom Schuster
• [whatwg/webidl] Dictionary with required members as optional argument (Issue #1378) Ms2ger
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) Anne van Kesteren
• Re: [whatwg/dom] Corresponding attribute for clonable of ShadowRootInit? (Issue #1236) Anne van Kesteren
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) Anne van Kesteren
• Re: [whatwg/streams] Define generic operation for GetDesiredSize? (#745) Domenic Denicola
• Re: [whatwg/streams] Define generic operation for GetDesiredSize? (#745) Domenic Denicola
• Re: [whatwg/streams] Put test results in margins of the spec (#216) Domenic Denicola
• Re: [whatwg/streams] Put test results in margins of the spec (#216) Domenic Denicola
• Re: [whatwg/streams] Export the "error the stream" concept? (#679) Domenic Denicola
• Re: [whatwg/streams] Export the "error the stream" concept? (#679) Domenic Denicola
• Re: [w3ctag/design-reviews] Intersection Observer Scroll Margin (Issue #905) tcaptan-cr
• [w3c/clipboard-apis] Topic: ‘unsanitized’ option to allow developers to opt-out of UA-provided sanitization (Issue #206) snianu
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Ryosuke Niwa

Tuesday, 12 December 2023

• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) snianu
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) snianu
• Re: [whatwg/webidl] Add support for AsyncContext (PR #1369) Daniel Ehrenberg
• Re: [w3c/IndexedDB] Editorial: Update a variable with set, not let (PR #415) Joshua Bell
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) Johannes Wilm
• Re: [w3c/clipboard-apis] Read Blob data for the supported formats on-demand during getType. (Issue #191) Evan Stade
• Re: [w3c/IndexedDB] Editorial: Update a variable with set, not let (PR #415) Austin Sullivan
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) Evan Stade
• Re: [w3ctag/design-reviews] systemEntropy addition to PerformanceNavigationTiming (Issue #878) Mike Jackson
• [w3c/clipboard-apis] References to permissions (Issue #205) Evan Stade
• Re: [w3c/clipboard-apis] Parallelism and task sources (Issue #202) Evan Stade
• Re: [whatwg/fetch] Option to fetch raw byte as is. (without decompressing) (Issue #1524) Eduardo Pinho
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) James
• [whatwg/dom] Add support for AsyncContext in dispatching Events (PR #1239) Ms2ger
• Re: [whatwg/webidl] Add support for AsyncContext (PR #1369) Ms2ger
• Re: [w3c/clipboard-apis] Parallelism and task sources (Issue #202) Kagami Sascha Rosylight
• [whatwg/webidl] Truncation in "convert a Web IDL arguments list to an ECMAScript arguments list" seems (potentially) incorrect (Issue #1377) Ms2ger
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) Mark Nottingham
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Rik Cabanier
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Rik Cabanier
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) James
• Re: [w3c/clipboard-apis] Aljbore (Issue #204) Dominique Hazael-Massieux
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Marcos Cáceres
• Re: [w3c/clipboard-apis] Aljbore (Issue #204) Aljbore1
• [w3c/clipboard-apis] Aljbore (Issue #204) Aljbore1
• [w3c/clipboard-apis] algorithms don't enforce focus requirement (Issue #203) Evan Stade
• [w3c/clipboard-apis] Parallelism and task sources (Issue #202) Evan Stade

Monday, 11 December 2023

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) Mark Nottingham
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) James
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) Eemeli Aro
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) Ryosuke Niwa
• Re: [w3c/IndexedDB] Editorial: Update a variable with set, not let (PR #415) Joshua Bell
• Re: [w3c/IndexedDB] Editorial: Update a variable with set, not let (PR #415) Joshua Bell
• [w3c/IndexedDB] Editorial: Update a variable with set, not let (PR #415) Joshua Bell
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Westbrook Johnson
• Re: [w3ctag/design-reviews] Intersection Observer Scroll Margin (Issue #905) Rossen Atanassov
• Re: [w3ctag/design-reviews] Intersection Observer Scroll Margin (Issue #905) Rossen Atanassov
• Re: [w3ctag/design-reviews] @page margin boxes (Issue #918) Rossen Atanassov
• Re: [w3ctag/design-reviews] @page margin boxes (Issue #918) Rossen Atanassov
• Re: [whatwg/dom] Source Code Tool (Issue #1238) Keith Cirkel
• Re: [w3ctag/design-reviews] Partitioning :visited links history (Issue #896) Peter Linss
• [whatwg/dom] Source Code Tool (Issue #1238) Daniel Enrique Aecherli
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) Kagami Sascha Rosylight
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) Matthew Phillips
• Re: [w3c/gamepad] Please don't restrict to a secure context (#145) juj
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) Kevin Cox
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) Gabriel Corona
• Re: [whatwg/webidl] non-readonly [FrozenArray] attributes are footguns as currently specced (#810) Anne van Kesteren
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) iteriani
• Re: [w3c/push-api] Editorial: fix references to Fetch and Web Sockets (PR #366) Martin Thomson
• Re: [w3c/push-api] Editorial: Introduce 'push subscription owner' concept (PR #367) Martin Thomson
• Re: [w3c/push-api] Editorial: fix references to Fetch and Web Sockets (PR #366) Martin Thomson
• [w3c/push-api] Editorial: Introduce 'push subscription owner' concept (PR #367) Marcos Cáceres
• [w3c/push-api] Editorial: fix references to Fetch and Web Sockets (PR #366) Marcos Cáceres
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) Kevin Cox
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) Kevin Cox

Sunday, 10 December 2023

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) Gabriel Corona
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) James
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) Keith Cirkel

Saturday, 9 December 2023

• Re: [whatwg/dom] Custom element callback/promise for "connected and parsed" (#662) Patrick Nelson
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) 7ombie

Friday, 8 December 2023

• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) 7ombie
• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) Chris Cawley
• Re: [w3c/uievents] `beforeinput` and `compositionupdate` event order (Issue #354) Chris Harrelson
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) Justin Fagnani
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) Matthew Phillips
• [w3ctag/design-reviews] Invokers API (Issue #920) Keith Cirkel
• [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) Steve Orvell
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) Mike Taylor
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) Alex Rudenko
• Re: [w3c/clipboard-apis] Feature detection of web custom format support (Issue #201) DavidMulder0
• Re: [w3c/clipboard-apis] Feature detection of web custom format support (Issue #201) DavidMulder0
• [w3c/clipboard-apis] Feature detection of web custom format support (Issue #201) DavidMulder0
• Re: [whatwg/url] Properly escape the & (PR #808) Anne van Kesteren
• Re: [whatwg/url] Properly escape the & (PR #808) Anne van Kesteren
• Re: [w3c/push-api] WPT testability (Issue #365) Marcos Cáceres
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Marcos Cáceres
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Marcos Cáceres
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) Marcos Cáceres
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) iteriani
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) Rob Eisenberg
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) Matthew Phillips

Thursday, 7 December 2023

• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito
• Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343) Joshua Bell
• [whatwg/url] Properly escape the & (PR #808) Tab Atkins Jr.
• Re: [WICG/webcomponents] [idea] HTML Modules: Allow exporting without a script (#863) Sasha Firsov
• [whatwg/url] RADIO (Issue #807) rclaretianafm105
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) Rob Eisenberg
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Nolan Lawson
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) Justin Fagnani
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) Tom Wilkinson
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) Matthew Phillips
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) Gabriel Brito

Wednesday, 6 December 2023

• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) Martin Thomson
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Martin Thomson
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) Martin Thomson
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) Sun Shin
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) jamiewalch
• 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) Karl
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Marcos Cáceres
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Marcos Cáceres
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Marcos Cáceres
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Marcos Cáceres
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Marcos Cáceres
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Marcos Cáceres
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) Marcos Cáceres
• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) Marcos Cáceres
• Re: [whatwg/url] An opaque-host parser and percent encoding (Issue #806) Hayato Ito
• Re: [whatwg/url] An opaque-host parser and percent encoding (Issue #806) Hayato Ito
• [whatwg/fullscreen] Add keyboard locking option (PR #232) Marcos Cáceres
• Re: [whatwg/url] An opaque-host parser and percent encoding (Issue #806) Anne van Kesteren
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) Martin Thomson
• [whatwg/url] An opaque-host parser and percent encoding (Issue #806) Hayato Ito
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) Marcos Cáceres

Tuesday, 5 December 2023

• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) snianu
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) Kagami Sascha Rosylight
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) snianu
• Re: [whatwg/url] A '@' character in the host part of file URLs (Issue #805) Karl
• Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912) Philipp Hancke
• Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912) Philipp Hancke
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) Kagami Sascha Rosylight
• Re: [w3c/uievents] Specify the textInput event (PR #362) Simon Pieters
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) Anne van Kesteren
• Re: [whatwg/url] A '@' character in the host part of file URLs (Issue #805) Anne van Kesteren
• [whatwg/url] A '@' character in the host part of file URLs (Issue #805) Hayato Ito

Monday, 4 December 2023

• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) snianu
• Re: [w3c/uievents] Specify the textInput event (PR #362) Gary Kacmarcik
• Re: [w3c/uievents] Added a new event to communicate context menu dismissal. (PR #322) Gary Kacmarcik
• Re: [w3c/uievents] Use `USVString` for input and composition events (PR #351) Gary Kacmarcik
• Re: [w3c/uievents] Use `USVString` for input and composition events (Issue #352) Gary Kacmarcik
• Re: [w3c/uievents] Specify wheel event groups (PR #344) Dan Robertson
• Re: [w3c/uievents] Use `USVString` for input and composition events (PR #351) Gary Kacmarcik
• Re: [w3c/uievents] Use `USVString` for input and composition events (PR #351) Gary Kacmarcik
• Re: [w3c/uievents] Wheel event groups are not defined (Issue #338) Gary Kacmarcik
• Re: [w3c/uievents] Specify wheel event groups (PR #344) Gary Kacmarcik
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) Kagami Sascha Rosylight
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) snianu
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) Kagami Sascha Rosylight
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) snianu
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) Kagami Sascha Rosylight
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) Kagami Sascha Rosylight
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) snianu
• Re: [w3c/uievents] Specify wheel event groups (PR #344) Dan Robertson
• Re: [w3c/uievents] Specify wheel event groups (PR #344) Dan Robertson
• Re: [w3c/uievents] Specify wheel event groups (PR #344) Simon Pieters
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) Alex Rudenko
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) Yoav Weiss
• Re: [w3ctag/design-reviews] Update 010-specification-review.md (PR #844) mitzos87
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) Anne van Kesteren
• Re: [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) Anne van Kesteren
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) Martin Thomson
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) Marcos Cáceres

Sunday, 3 December 2023

• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) 7ombie

Saturday, 2 December 2023

• [whatwg/dom] Add ShadowRoot clonable attribute (PR #1237) Kagami Sascha Rosylight
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) Kagami Sascha Rosylight
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) Karl
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) Klaus Frank
• [whatwg/fetch] RequestInit::priority lacks corresponding Request::priority attribute (Issue #1726) Kagami Sascha Rosylight
• Re: [whatwg/webidl] Web idl standard (Issue #1376) mithumiah231
• [whatwg/webidl] Web idl standard (Issue #1376) mithumiah231

Friday, 1 December 2023

• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) Peter Linss
• Re: [w3c/permissions] Can 'prompt the user to choose' return deny after some implementation specific timeout? (Issue #430) Mike Taylor
• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) Mike Taylor
• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) Mike Taylor
• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) Mike Taylor
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) Sun Shin
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) Yoav Weiss
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) smaug----
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) meacer
• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) Elad Alon
• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) youennf
• Re: [w3c/FileAPI] Support using AbortController with FileAPI (#159) ayalatech
• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) alancutter
• Re: [whatwg/dom] Corresponding attribute for clonable of ShadowRootInit? (Issue #1236) Kagami Sascha Rosylight
• Re: [w3c/permissions] Editorial: add example of prompt timing out (PR #432) Marcos Cáceres
• [w3c/permissions] Editorial: add example of prompt timing out (PR #432) Marcos Cáceres
• Re: [w3c/permissions] Can 'prompt the user to choose' return deny after some implementation specific timeout? (Issue #430) Marcos Cáceres
• Re: [w3c/permissions] Can 'prompt the user to choose' return deny after some implementation specific timeout? (Issue #430) Mike Taylor
• Re: [w3c/permissions] Can 'prompt the user to choose' return deny after some implementation specific timeout? (Issue #430) Marcos Cáceres
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) Marcos Cáceres
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) Mike Taylor

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