public-webapps-github@w3.org from January 2024 by author

7ombie

• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Wednesday, 17 January)

Aaron Gustafson

• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Wednesday, 17 January)

Adam Argyle

• Re: [w3ctag/design-reviews] `prefers-reduced-data` CSS Media Query (Issue #705) (Wednesday, 17 January)

Adam Rice

• [whatwg/streams] Editorial: Export definition "writable stream writer" (PR #1304) (Wednesday, 31 January)
• Re: [whatwg/fetch] Option to fetch raw byte as is. (without decompressing) (Issue #1524) (Wednesday, 31 January)
• Re: [whatwg/streams] Editorial: Export byte streams related terms (PR #1303) (Monday, 29 January)
• Re: [whatwg/encoding] Make encodeInto() throw when given a detached buffer (Issue #324) (Thursday, 25 January)
• Re: [whatwg/streams] Meta: update contribution guidelines (PR #1301) (Tuesday, 9 January)

Aetinx

• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 25 January)

Ahmed Abdellahi Abdat

• Re: [w3c/manifest] Manifest: property 'src' ignored, URL is invalid. (Issue #1059) (Sunday, 21 January)

alancutter

• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Thursday, 18 January)
• Re: [w3c/manifest] Procedure for moving manifests and Apps (#850) (Monday, 1 January)

Aleksey Chendemerov

• Re: [w3c/IndexedDB] Add an Observer API (#51) (Wednesday, 10 January)

Alex Rudenko

• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Wednesday, 31 January)
• Re: [w3c/permissions] WebDriver BiDi: support user contexts in setPermission (Issue #439) (Wednesday, 31 January)
• [w3c/permissions] WebDriver BiDi: support user contexts in setPermission (Issue #439) (Wednesday, 31 January)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Wednesday, 31 January)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Wednesday, 31 January)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Wednesday, 31 January)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Tuesday, 30 January)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Tuesday, 30 January)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Tuesday, 30 January)
• [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Tuesday, 30 January)
• [w3c/permissions] WebDriver: Should Set Permission apply to future browsing contexts? (Issue #437) (Tuesday, 16 January)
• Re: [w3c/permissions] WebDriver: Make it possible to pass a different origin to "Set Permission" (Issue #419) (Monday, 15 January)
• Re: [w3c/permissions] Require an explicit origin for WebDriver BiDi automation (PR #436) (Saturday, 13 January)
• Re: [w3c/permissions] Require an explicit origin for WebDriver BiDi automation (PR #436) (Saturday, 13 January)
• Re: [w3c/permissions] Require an explicit origin for WebDriver BiDi automation (PR #436) (Saturday, 13 January)
• [w3c/permissions] Require an explicit origin for WebDriver BiDi automation (PR #436) (Friday, 12 January)
• Re: [w3c/permissions] Editorial: fix tidy errors (PR #434) (Friday, 12 January)
• Re: [w3c/permissions] Editorial: fix tidy errors (PR #434) (Friday, 12 January)
• [w3c/permissions] Editorial: Update link to accelerometer permission (PR #435) (Friday, 12 January)
• Re: [w3c/permissions] Editorial: fix tidy errors (PR #434) (Friday, 12 January)
• Re: [w3c/permissions] Editorial: fix tidy errors (PR #434) (Friday, 12 January)
• Re: [w3c/permissions] Editorial: fix tidy errors (PR #434) (Friday, 12 January)
• [w3c/permissions] Editorial: fix tidy errors (PR #434) (Friday, 12 January)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Tuesday, 2 January)

Alice

• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Friday, 5 January)

Alwin Blok

• Re: [whatwg/url] Differentiate from zero-sized fragment and no fragment in url (Issue #779) (Sunday, 7 January)
• Re: [whatwg/url] Are drive letters always invalid? (#612) (Sunday, 7 January)

Amanda Parker

• Re: [w3c/manifest] Procedure for moving manifests and Apps (#850) (Tuesday, 2 January)

Amy Guy

• Re: [w3ctag/design-reviews] Captured Mouse Events (Issue #872) (Wednesday, 24 January)
• Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838) (Monday, 15 January)
• Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838) (Monday, 15 January)

Andrew

• Re: [WICG/webcomponents] Allow a click on label associated with custom element to focus the custom element (#891) (Thursday, 18 January)

Andrew Sutherland

• Re: [w3c/ServiceWorker] dynamically registered event listeners for extension service worker (Issue #1698) (Tuesday, 9 January)

Anne van Kesteren

• Re: [whatwg/dom] Side effects due to tree insertion or removal (script, iframe) (#808) (Wednesday, 31 January)
• Re: [whatwg/dom] Side effects due to tree insertion or removal (script, iframe) (#808) (Tuesday, 30 January)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Tuesday, 30 January)
• Re: [whatwg/dom] How should `clonable` work in `cloneNode(false)`? (Issue #1249) (Tuesday, 30 January)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Monday, 29 January)
• Re: [whatwg/url] Web compatibility issue with various unknown (external) protocols like ed2k (Issue #815) (Monday, 29 January)
• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Friday, 26 January)
• Re: [w3c/clipboard-apis] `supports` should take a dictionary instead of a DOMString as argument for readability (Issue #211) (Friday, 26 January)
• [whatwg/url] URL path comparison (Issue #814) (Friday, 26 January)
• Re: [whatwg/url] Consider defining "URL path" as a concept (Issue #792) (Friday, 26 January)
• Re: [whatwg/url] Editorial: add a URL path concept (PR #812) (Friday, 26 January)
• Re: [whatwg/url] Editorial: add a URL path concept (PR #812) (Friday, 26 January)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Thursday, 25 January)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Thursday, 25 January)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Thursday, 25 January)
• Re: [whatwg/encoding] Make encodeInto() throw when given a detached buffer (Issue #324) (Thursday, 25 January)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Wednesday, 24 January)
• [whatwg/encoding] Make encodeInto() throw when given a detached buffer (Issue #324) (Wednesday, 24 January)
• Re: [whatwg/url] Editorial: add a URL path concept (PR #812) (Wednesday, 24 January)
• Re: [whatwg/url] Editorial: add a URL path concept (PR #812) (Wednesday, 24 January)
• Re: [whatwg/url] Editorial: add a URL path concept (PR #812) (Wednesday, 24 January)
• Re: [whatwg/webidl] Meta: update repository files (PR #1386) (Wednesday, 24 January)
• [whatwg/webidl] Meta: update repository files (PR #1386) (Wednesday, 24 January)
• Re: [whatwg/url] Meta: update repository files (PR #813) (Wednesday, 24 January)
• Re: [whatwg/encoding] Meta: update repository files (PR #323) (Wednesday, 24 January)
• Re: [whatwg/storage] Meta: update repository files (PR #171) (Wednesday, 24 January)
• Re: [whatwg/fetch] Meta: update repository files (PR #1731) (Wednesday, 24 January)
• Re: [whatwg/dom] Meta: update repository files (PR #1248) (Wednesday, 24 January)
• [whatwg/url] Meta: update repository files (PR #813) (Wednesday, 24 January)
• [whatwg/streams] Meta: update repository files (PR #1302) (Wednesday, 24 January)
• [whatwg/storage] Meta: update repository files (PR #171) (Wednesday, 24 January)
• [whatwg/fetch] Meta: update repository files (PR #1731) (Wednesday, 24 January)
• [whatwg/fullscreen] Meta: update repository files (PR #233) (Wednesday, 24 January)
• [whatwg/dom] Meta: update repository files (PR #1248) (Wednesday, 24 January)
• [whatwg/encoding] Meta: update repository files (PR #323) (Wednesday, 24 January)
• Re: [whatwg/xhr] Meta: update repository files (PR #385) (Wednesday, 24 January)
• Re: [whatwg/xhr] Meta: update repository files (PR #385) (Wednesday, 24 January)
• [whatwg/xhr] Meta: update repository files (PR #385) (Wednesday, 24 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) (Wednesday, 24 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) (Tuesday, 23 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) (Monday, 22 January)
• [whatwg/url] Editorial: add a URL path concept (PR #812) (Monday, 22 January)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Monday, 22 January)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Monday, 22 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable buffers (Issue #1385) (Monday, 22 January)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Friday, 19 January)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Thursday, 18 January)
• Re: [whatwg/dom] Editorial: remove redundant contains check in AbortSignal.any() (PR #1244) (Tuesday, 16 January)
• Re: [whatwg/dom] Prevent AbortSignal.any() from causing duplicates in source signals (PR #1244) (Tuesday, 16 January)
• Re: [whatwg/storage] Update build.yml (PR #170) (Tuesday, 16 January)
• Re: [whatwg/url] API mechanism for reporting validity errors (Issue #811) (Monday, 15 January)
• Re: [whatwg/fetch] Document the problem with cross-origin headers (#1186) (Monday, 15 January)
• Re: [whatwg/dom] Add attribute validate steps. (#809) (Monday, 15 January)
• Re: [whatwg/dom] Add attribute validate steps. (#809) (Monday, 15 January)
• Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353) (Monday, 15 January)
• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Monday, 15 January)
• Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353) (Monday, 15 January)
• Re: [whatwg/webidl] Allow dictionaries and callbacks to be distinguishable (Issue #1191) (Monday, 15 January)
• Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353) (Monday, 15 January)
• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Monday, 15 January)
• Re: [whatwg/dom] Element.attachShadow should set the declarative flag to false of an existing declarative shadow dom. (Issue #1234) (Sunday, 14 January)
• Re: [whatwg/dom] Reset declarative to false when calling attachShadow (PR #1245) (Sunday, 14 January)
• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Thursday, 11 January)
• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Thursday, 11 January)
• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Thursday, 11 January)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Wednesday, 10 January)
• Re: [whatwg/dom] Reset declarative to false when calling attachShadow (PR #1245) (Wednesday, 10 January)
• Re: [whatwg/dom] Prevent AbortSignal.any() from causing duplicates in source signals (PR #1244) (Tuesday, 9 January)
• Re: [whatwg/dom] Prevent AbortSignal.any() from causing duplicates in source signals (PR #1244) (Tuesday, 9 January)
• Re: [whatwg/fetch] Automatic decompression should sanitize `Content-Encoding` and `Content-Length` headers from the response (Issue #1729) (Monday, 8 January)

Anssi Kostiainen

• Re: [w3ctag/design-reviews] Delta review (to CR) of Web Neural Network API (Issue #771) (Friday, 26 January)
• Re: [w3ctag/design-reviews] Fullscreen Popup Windows (Issue #840) (Tuesday, 16 January)
• Re: [w3ctag/design-reviews] Fullscreen Popup Windows (Issue #840) (Tuesday, 9 January)

Anton Maliev

• Re: [w3ctag/design-reviews] TAG spec review of Storage Access Heuristics (Issue #919) (Tuesday, 16 January)

Ari Chivukula

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

Ben Howell

• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Saturday, 6 January)

Ben Kelly

• Re: [w3ctag/design-reviews] TAG spec review of Storage Access Heuristics (Issue #919) (Tuesday, 2 January)

bootmii

• Re: [whatwg/encoding] Adding BRF as "legacy" single-byte encoding for braille (#40) (Thursday, 25 January)

Brandon Jones

• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Wednesday, 17 January)

Brian Kardell

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

Bruce B. Anderson

• [WICG/webcomponents] Observing the Observed Attributes API (Issue #1045) (Monday, 22 January)

Caridy Patiño

• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Thursday, 18 January)

Carlos Lopez

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Sunday, 14 January)

Chris Lilley

• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Wednesday, 31 January)

chrisrob

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

Christian Liebel

• Re: [w3c/manifest] err_invalid_url (Issue #1107) (Saturday, 6 January)

Christophe Garcia

• [WICG/webcomponents] Why is the focus visible when a lightDom element in a web component is clicked? (Issue #1046) (Wednesday, 24 January)

cynthia

• Re: [w3ctag/design-reviews] The `FileSystemObserver` interface (Issue #868) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] The `FileSystemObserver` interface (Issue #868) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] Web Audio API: User-Selectable Render Quantum Size (Issue #895) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] Web Audio API: User-Selectable Render Quantum Size (Issue #895) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] Web Audio API: RenderCapacity API (Issue #843) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] DisplayMediaStreamOptions monitorTypeSurfaces (Issue #892) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Suggest linking to standards positions (PR #898) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Suggest linking to standards positions (PR #898) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Suggest linking to standards positions (PR #898) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Suggest linking to standards positions (PR #898) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Add examples of stakeholders to issue template (PR #844) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Add examples of stakeholders to issue template (PR #844) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] early design review: bfcache/prerendering eviction APIs (Issue #786) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] early design review: bfcache/prerendering eviction APIs (Issue #786) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] early design review: bfcache/prerendering eviction APIs (Issue #786) (Wednesday, 17 January)
• Re: [w3ctag/design-reviews] early design review: bfcache/prerendering eviction APIs (Issue #786) (Wednesday, 17 January)

Daniel Appelquist

• Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] DisplayMediaStreamOptions monitorTypeSurfaces (Issue #892) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] TAG spec review of Storage Access Heuristics (Issue #919) (Tuesday, 16 January)
• Re: [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Monday, 15 January)
• Re: [w3ctag/design-reviews] Navigation Activation Info (Issue #921) (Thursday, 11 January)
• Re: [w3ctag/design-reviews] Navigation Activation Info (Issue #921) (Thursday, 11 January)
• Re: [w3ctag/design-reviews] Permissions Policy Reporting and Report-Only mode (Issue #909) (Tuesday, 9 January)
• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) (Tuesday, 9 January)
• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) (Tuesday, 9 January)
• Re: [w3ctag/design-reviews] Navigation Activation Info (Issue #921) (Tuesday, 9 January)
• Re: [w3ctag/design-reviews] TAG spec review of Storage Access Heuristics (Issue #919) (Monday, 8 January)

Daniel Florey

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

Daniel Meyer

• Re: [w3c/IndexedDB] Add an Observer API (#51) (Monday, 29 January)

David Bokan

• Re: [w3ctag/design-reviews] Cross-document View Transitions API (Issue #851) (Thursday, 11 January)

Diego Gonzalez

• Re: [w3ctag/design-reviews] (Document Subtitle): Early review for adding a new value to the standard list of `name`s for a meta tag (Issue #819) (Wednesday, 24 January)
• Re: [w3ctag/design-reviews] Web Install API (Issue #888) (Thursday, 18 January)

Domenic Denicola

• Re: [whatwg/encoding] Make encodeInto() throw when given a detached buffer (Issue #324) (Thursday, 25 January)
• Re: [whatwg/fullscreen] Meta: update repository files (PR #233) (Wednesday, 24 January)
• Re: [whatwg/fullscreen] Meta: update repository files (PR #233) (Wednesday, 24 January)
• Re: [whatwg/streams] Meta: update repository files (PR #1302) (Wednesday, 24 January)
• Re: [whatwg/streams] Meta: update repository files (PR #1302) (Wednesday, 24 January)
• Re: [whatwg/xhr] Meta: update repository files (PR #385) (Wednesday, 24 January)
• Re: [whatwg/xhr] Meta: update repository files (PR #385) (Wednesday, 24 January)
• Re: [whatwg/dom] Add attribute validate steps. (#809) (Monday, 15 January)
• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Friday, 12 January)
• Re: [whatwg/streams] Editorial: Add missing argument to cancel and abort wrapper algorithms (PR #1275) (Thursday, 11 January)
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) (Wednesday, 10 January)
• Re: [whatwg/streams] Editorial: Add missing argument to cancel and abort wrapper algorithms (PR #1275) (Wednesday, 10 January)
• Re: [whatwg/streams] cancelAlgorithmWrapper does not handle cancellation argument (Issue #1273) (Wednesday, 10 January)
• Re: [whatwg/streams] cancelAlgorithmWrapper in ReadableStream set up does not pass along the reason (Issue #1241) (Wednesday, 10 January)
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) (Wednesday, 10 January)
• Re: [whatwg/streams] Meta: update contribution guidelines (PR #1301) (Tuesday, 9 January)
• Re: [whatwg/streams] Meta: update contribution guidelines (PR #1301) (Tuesday, 9 January)
• [whatwg/streams] Meta: update contribution guidelines (PR #1301) (Tuesday, 9 January)
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) (Tuesday, 9 January)
• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Tuesday, 9 January)

Dominic Farolino

• Re: [whatwg/dom] Side effects due to tree insertion or removal (script, iframe) (#808) (Wednesday, 31 January)
• Re: [whatwg/dom] Side effects due to tree insertion or removal (script, iframe) (#808) (Tuesday, 30 January)
• Re: [whatwg/dom] Side effects due to tree insertion or removal (script, iframe) (#808) (Monday, 29 January)

dontcallmedom-bot

• [w3c/permissions] Broken references in Permissions (Issue #433) (Wednesday, 10 January)

Eemeli Aro

• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Monday, 22 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Tuesday, 16 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Friday, 5 January)

Emilio Cobos Álvarez

• Re: [whatwg/dom] How should `clonable` work in `cloneNode(false)`? (Issue #1249) (Tuesday, 30 January)
• Re: [whatwg/dom] How should `clonable` work in `cloneNode(false)`? (Issue #1249) (Tuesday, 30 January)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Monday, 29 January)
• Re: [whatwg/dom] Reset declarative to false when calling attachShadow (PR #1245) (Tuesday, 9 January)

Evan Stade

• [w3c/clipboard-apis] read(formats) ambiguous (Issue #209) (Friday, 12 January)
• Re: [w3c/clipboard-apis] Read Blob data for the supported formats on-demand during getType. (Issue #191) (Monday, 8 January)

François Beaufort

• Re: [w3ctag/design-reviews] DisplayMediaStreamOptions monitorTypeSurfaces (Issue #892) (Tuesday, 23 January)

Frederik Braun

• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 31 January)

Gabriel Brito

• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Wednesday, 24 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Thursday, 18 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Thursday, 18 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Thursday, 18 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Tuesday, 16 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Tuesday, 16 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Tuesday, 16 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Saturday, 13 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Saturday, 13 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Saturday, 13 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Saturday, 13 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Friday, 12 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Thursday, 11 January)

Garrett Tanzer

• Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838) (Tuesday, 16 January)

Gary Kacmarcik

• [w3c/uievents] UI Event spec modernization task list (Issue #370) (Wednesday, 31 January)
• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Tuesday, 30 January)
• Re: [w3c/uievents] Add an option to set the max number of rows shown in the output table for keyboard event viewer (Issue #364) (Tuesday, 30 January)
• Re: [w3c/uievents] Disable autocomplete on tools/key-event-viewer.html (Issue #363) (Tuesday, 30 January)
• Re: [w3c/uievents] Disable autocomplete on tools/key-event-viewer.html (Issue #363) (Tuesday, 30 January)
• Re: [w3c/uievents] Define inputType "insertFromPasteAsQuotation" (Issue #368) (Tuesday, 30 January)
• Re: [w3c/uievents] Define inputType "insertFromPasteAsQuotation" (Issue #368) (Tuesday, 30 January)
• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Tuesday, 30 January)
• [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Monday, 29 January)
• Re: [w3c/uievents] Require support for legacy events (Issue #366) (Monday, 22 January)
• Re: [w3c/uievents] Define events directly caused by user interaction (#270) (Monday, 22 January)

Greg Bernstein

• Re: [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) (Tuesday, 16 January)

Greggman

• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Thursday, 18 January)

Hadley Beeman

• Re: [w3ctag/design-reviews] VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport (Issue #768) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport (Issue #768) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] Fullscreen Popup Windows (Issue #840) (Wednesday, 17 January)
• Re: [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) (Tuesday, 16 January)
• Re: [w3ctag/design-reviews] Fullscreen Popup Windows (Issue #840) (Monday, 15 January)
• Re: [w3ctag/design-reviews] Fullscreen Popup Windows (Issue #840) (Monday, 8 January)

Hamish Willee

• Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Friday, 5 January)

hober

• Re: [w3ctag/design-reviews] New attribute to control UA-provided writing assistance (Issue #924) (Wednesday, 24 January)
• Re: [w3ctag/design-reviews] New attribute to control UA-provided writing assistance (Issue #924) (Wednesday, 24 January)
• Re: [w3ctag/design-reviews] Captured Mouse Events (Issue #872) (Wednesday, 24 January)
• Re: [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Wednesday, 24 January)
• Re: [w3ctag/design-reviews] Adding a close event to MessagePort API (Issue #923) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Adding a close event to MessagePort API (Issue #923) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Tabbed web apps (Issue #841) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Tabbed web apps (Issue #841) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Tuesday, 23 January)

hybridherbst

• Re: [w3c/manifest] Feature request: access to menu bar and context menus (Issue #1025) (Wednesday, 10 January)

Jackie(Guokai) Han

• [w3c/ServiceWorker] Support import() local code in extension service worker (Issue #1700) (Monday, 8 January)
• Re: [w3c/ServiceWorker] dynamically registered event listeners for extension service worker (Issue #1698) (Monday, 8 January)

Jake Archibald

• Re: [whatwg/webidl] Allow dictionaries and callbacks to be distinguishable (Issue #1191) (Monday, 15 January)

James M Snell

• Re: [whatwg/url] API mechanism for reporting validity errors (Issue #811) (Sunday, 14 January)
• [whatwg/url] API mechanism for reporting validity errors (Issue #811) (Sunday, 14 January)

Jared White

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 12 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 9 January)

Jeffrey Yasskin

• Re: [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) (Tuesday, 16 January)

Jens Tangermann

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

Jeremy Roman

• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) (Tuesday, 9 January)
• Re: [whatwg/streams] Editorial: Plumb reason through abort and cancel algorithm wrappers (PR #1300) (Tuesday, 9 January)

jgraham

• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Thursday, 4 January)
• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Thursday, 4 January)
• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Thursday, 4 January)
• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Thursday, 4 January)

Joe Pea

• Re: [w3c/pointerlock] movementX/Y coordinate space (#42) (Thursday, 11 January)
• Re: [w3c/pointerlock] movementX/Y coordinate space (#42) (Thursday, 11 January)

Joe Puccio

• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Friday, 12 January)

Joey Arhar

• Re: [whatwg/fullscreen] Don't close ancestor popovers when fullscreening (PR #237) (Wednesday, 31 January)
• [whatwg/fullscreen] Don't close ancestor popovers when fullscreening (PR #237) (Wednesday, 31 January)

Jonathan Hao

• Re: [whatwg/fetch] Document the problem with cross-origin headers (#1186) (Monday, 15 January)
• Re: [whatwg/fetch] Document the problem with cross-origin headers (#1186) (Monday, 15 January)

Jordan Brennan

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Friday, 12 January)

Josh Goodall

• Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 14 January)

Joshua Bell

• Re: [whatwg/encoding] Make encodeInto() throw when given a detached buffer (Issue #324) (Wednesday, 24 January)

jub0bs

• Re: [whatwg/fetch] If a resource allows credentials but omits Vary, shouldn't responses to non-CORS requests also contain Access-Control-Allow-Credentials? (Issue #1601) (Saturday, 20 January)

Justin Fagnani

• Re: [whatwg/dom] How should `clonable` work in `cloneNode(false)`? (Issue #1249) (Tuesday, 30 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Tuesday, 23 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Monday, 22 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Monday, 22 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 16 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 12 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 12 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 12 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 9 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 9 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 9 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 9 January)
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Tuesday, 2 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Tuesday, 2 January)

Kagami Sascha Rosylight

• Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Wednesday, 31 January)
• Re: [whatwg/dom] How should `clonable` work in `cloneNode(false)`? (Issue #1249) (Tuesday, 30 January)
• Re: [whatwg/dom] How should `clonable` work in `cloneNode(false)`? (Issue #1249) (Monday, 29 January)
• Re: [whatwg/dom] How should `clonable` work in `cloneNode(false)`? (Issue #1249) (Monday, 29 January)
• Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353) (Monday, 29 January)
• Re: [whatwg/streams] Editorial: Add missing argument to cancel and abort wrapper algorithms (PR #1275) (Wednesday, 10 January)
• Re: [w3c/push-api] Expose pushManager on Navigator (PR #368) (Wednesday, 3 January)
• Re: [w3c/push-api] Expose pushManager on Navigator (PR #368) (Wednesday, 3 January)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Tuesday, 2 January)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Tuesday, 2 January)

Karebear1000

• Re: [whatwg/webidl] `record<>` should allow the keytype to be a typedef that resolves to one of the allowed string types (Issue #1267) (Friday, 12 January)

Karl

• Re: [whatwg/url] Web compatibility issue with various unknown (external) protocols like ed2k (Issue #815) (Monday, 29 January)
• Re: [whatwg/url] API mechanism for reporting validity errors (Issue #811) (Monday, 15 January)
• Re: [whatwg/url] API mechanism for reporting validity errors (Issue #811) (Sunday, 14 January)

Keith Cirkel

• Re: [whatwg/xhr] XMLHttpRequest Standard (Issue #384) (Thursday, 18 January)
• Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353) (Monday, 15 January)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Wednesday, 17 January)

Kevin Gibbons

• [whatwg/fetch] add a method to get a Uint8Array to Body (Issue #1732) (Monday, 29 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) (Tuesday, 23 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) (Monday, 22 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) (Monday, 22 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable buffers (Issue #1385) (Monday, 22 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable buffers (Issue #1385) (Monday, 22 January)
• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable buffers (Issue #1385) (Monday, 22 January)
• [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable buffers (Issue #1385) (Sunday, 21 January)

kleinkk76

• Re: [w3ctag/design-reviews] Mixed content level 2 (#420) (Saturday, 6 January)

Kongpc256

• [whatwg/webidl] KAMPANAT THUMWONG (Issue #1384) (Sunday, 7 January)

Krzysztof Kotowicz

• Re: [whatwg/webidl] Added a definition of {{StringContext}} extended attribute. (#841) (Friday, 26 January)
• Re: [whatwg/webidl] Added a definition of {{StringContext}} extended attribute. (#841) (Friday, 26 January)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Thursday, 25 January)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Thursday, 25 January)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Thursday, 25 January)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Thursday, 25 January)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Thursday, 25 January)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Wednesday, 24 January)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Wednesday, 24 January)
• Re: [whatwg/dom] Add attribute validate steps. (#809) (Tuesday, 23 January)
• [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Tuesday, 23 January)
• Re: [whatwg/dom] Add attribute validate steps. (#809) (Monday, 15 January)

Lea Verou

• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Sunday, 28 January)
• Re: [w3ctag/design-reviews] Side Panel (Issue #903) (Saturday, 27 January)
• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] Side Panel (Issue #903) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Monday, 15 January)
• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Thursday, 11 January)
• Re: [w3ctag/design-reviews] text-wrap: pretty (Issue #864) (Monday, 8 January)
• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Monday, 8 January)
• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Monday, 8 January)

Liam Brady

• Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838) (Friday, 5 January)

liudonghua

• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Tuesday, 16 January)
• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Tuesday, 16 January)

Lu

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

Luis Pato

• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Thursday, 18 January)
• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Thursday, 18 January)

Lukasz Olejnik

• Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723) (Friday, 26 January)
• Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723) (Thursday, 25 January)

Luke Warlow

• Re: [whatwg/dom] Add attribute validate steps. (#809) (Monday, 15 January)
• Re: [whatwg/webidl] Added a definition of {{StringContext}} extended attribute. (#841) (Saturday, 13 January)
• Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353) (Friday, 12 January)
• Re: [whatwg/webidl] Added a definition of {{StringContext}} extended attribute. (#841) (Thursday, 4 January)

Léonie Watson

• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Tuesday, 30 January)

Manish Goregaokar

• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Tuesday, 30 January)

Manu Sporny

• Re: [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) (Tuesday, 16 January)

Marcos Cáceres

• Re: [w3c/pointerlock] [Editorial] Fix `browsing context` links. (PR #88) (Tuesday, 30 January)
• Re: [w3c/pointerlock] [Editorial] Fix `browsing context` links. (PR #88) (Tuesday, 30 January)
• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Monday, 29 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Wednesday, 24 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Wednesday, 24 January)
• Re: [w3c/gamepad] move vibrationActuator to main spec (Issue #173) (Wednesday, 24 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Tuesday, 23 January)
• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Thursday, 18 January)
• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Thursday, 18 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Thursday, 18 January)
• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Thursday, 18 January)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Wednesday, 17 January)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Wednesday, 17 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Wednesday, 17 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Wednesday, 17 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Wednesday, 17 January)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Wednesday, 17 January)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Tuesday, 16 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Tuesday, 16 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Tuesday, 16 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Tuesday, 16 January)
• Re: [w3c/permissions] Broken references in Permissions (Issue #433) (Monday, 15 January)
• Re: [w3c/gamepad] Require secure context for gamepad state and events (#120) (Monday, 15 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 15 January)
• Re: [w3c/permissions] Require an explicit origin for WebDriver BiDi automation (PR #436) (Monday, 15 January)
• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Friday, 12 January)
• Re: [w3c/gamepad] Define user activation and added references in getGamepads and gamepa… (#107) (Friday, 12 January)
• Re: [w3c/gamepad] Define user activation and added references in getGamepads and gamepa… (#107) (Friday, 12 January)
• Re: [w3c/gamepad] spec `gamepadbuttondown` and `gamepadbuttonup` events (issue #4) (#15) (Friday, 12 January)
• Re: [w3c/gamepad] spec `gamepadbuttondown` and `gamepadbuttonup` events (issue #4) (#15) (Friday, 12 January)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Thursday, 11 January)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Thursday, 11 January)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 11 January)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 11 January)
• Re: [w3c/permissions] Umbrella / Meta: Browser Permissions for WebDriver BiDi as an extension module (Issue #424) (Thursday, 11 January)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Thursday, 11 January)
• Re: [w3c/manifest] Reword ‘member’ to ‘field’ (Issue #1108) (Tuesday, 9 January)
• Re: [w3c/manifest] Reword ‘member’ to ‘field’ (Issue #1108) (Tuesday, 9 January)

MarleshiaM

• [w3c/manifest] Adding protocol handlers (PR #1110) (Thursday, 18 January)

Martin Thomson

• Re: [w3ctag/design-reviews] requestStorageAccessFor (Issue #808) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] Update 010-specification-review.md (PR #844) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Compute Pressure API (#621) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Tuesday, 23 January)

Masayuki Nakano

• Re: [w3c/uievents] Specify the textInput event (PR #362) (Wednesday, 31 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Wednesday, 31 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Tuesday, 30 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Tuesday, 30 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Tuesday, 30 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Tuesday, 30 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Tuesday, 30 January)
• Re: [w3c/uievents] Define inputType "insertFromPasteAsQuotation" (Issue #368) (Tuesday, 30 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Monday, 29 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Monday, 29 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Monday, 29 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Monday, 29 January)
• 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) (Monday, 29 January)
• 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) (Monday, 29 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Friday, 19 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Friday, 19 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Friday, 19 January)
• Re: [w3c/uievents] A way to determine what the value of an input will be if `beforeinput` is not prevented (#289) (Friday, 12 January)
• Re: [w3c/uievents] Define groups of events by the interaction that caused them (#311) (Friday, 12 January)

Mason Freed

• Re: [whatwg/dom] How should `clonable` work in `cloneNode(false)`? (Issue #1249) (Tuesday, 30 January)
• Re: [whatwg/dom] How should `clonable` work in `cloneNode(false)`? (Issue #1249) (Tuesday, 30 January)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Monday, 29 January)
• [whatwg/dom] How should `clonable` work in `cloneNode(false)`? (Issue #1249) (Monday, 29 January)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Monday, 29 January)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Monday, 29 January)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Saturday, 27 January)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Saturday, 27 January)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Saturday, 27 January)
• Re: [WICG/webcomponents] Jan 2024 DOM Parts Quarterly Meeting (Issue #1027) (Friday, 26 January)
• Re: [WICG/webcomponents] Jan 2024 DOM Parts Quarterly Meeting (Issue #1027) (Friday, 26 January)
• Re: [WICG/webcomponents] Jan 2024 DOM Parts Quarterly Meeting (Issue #1027) (Thursday, 25 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Tuesday, 23 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Monday, 22 January)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Friday, 19 January)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Thursday, 18 January)
• [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Tuesday, 16 January)
• Re: [whatwg/dom] Reset declarative to false when calling attachShadow (PR #1245) (Friday, 12 January)
• Re: [whatwg/dom] Reset declarative to false when calling attachShadow (PR #1245) (Friday, 12 January)
• Re: [whatwg/dom] Reset declarative to false when calling attachShadow (PR #1245) (Friday, 12 January)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Thursday, 11 January)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Tuesday, 9 January)
• [whatwg/dom] Reset declarative to false when calling attachShadow (PR #1245) (Tuesday, 9 January)

Matt Giuca

• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Friday, 19 January)
• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Thursday, 18 January)
• Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Thursday, 18 January)
• [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109) (Wednesday, 17 January)
• Re: [w3c/manifest] Procedure for moving manifests and Apps (#850) (Friday, 12 January)

Matt Reynolds

• Re: [w3c/gamepad] Add trackpad button support (Issue #191) (Friday, 26 January)
• Re: [w3c/gamepad] Add vibrationActuator to the main spec (PR #190) (Tuesday, 23 January)
• Re: [w3c/gamepad] Add trackpad button support (Issue #191) (Wednesday, 3 January)

Matthew Phillips

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 13 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 13 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 13 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 12 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)

Matthew Tylee Atkinson

• Re: [w3ctag/design-reviews] Captured Mouse Events (Issue #872) (Wednesday, 24 January)
• Re: [w3ctag/design-reviews] HTMLSelectElement showPicker() (Issue #900) (Friday, 12 January)

Mattias Buelens

• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Tuesday, 16 January)

Max Paperno

• Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 14 January)

Mayank

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 16 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 12 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 12 January)

meacer

• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 31 January)

Michael Warren

• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Thursday, 11 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Wednesday, 10 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Monday, 8 January)

Mike Taylor

• Re: [w3ctag/design-reviews] Update 010-specification-review.md (PR #844) (Tuesday, 16 January)
• Re: [w3ctag/design-reviews] Suggest linking to standards positions (PR #898) (Tuesday, 16 January)
• Re: [w3c/permissions] WebDriver: Make it possible to pass a different origin to "Set Permission" (Issue #419) (Tuesday, 16 January)
• Re: [w3c/permissions] Require an explicit origin for WebDriver BiDi automation (PR #436) (Tuesday, 16 January)
• Re: [w3c/permissions] Require an explicit origin for WebDriver BiDi automation (PR #436) (Tuesday, 16 January)
• Re: [w3c/permissions] Require an explicit origin for WebDriver BiDi automation (PR #436) (Sunday, 14 January)
• Re: [w3c/permissions] Require an explicit origin for WebDriver BiDi automation (PR #436) (Sunday, 14 January)
• Re: [w3c/permissions] Require an explicit origin for WebDriver BiDi automation (PR #436) (Sunday, 14 January)
• Re: [w3c/permissions] Require an explicit origin for WebDriver BiDi automation (PR #436) (Friday, 12 January)
• Re: [w3c/permissions] Editorial: fix tidy errors (PR #434) (Friday, 12 January)
• Re: [w3c/permissions] Editorial: fix tidy errors (PR #434) (Friday, 12 January)
• Re: [w3c/permissions] Editorial: fix tidy errors (PR #434) (Friday, 12 January)
• Re: [w3c/permissions] Editorial: Update link to accelerometer permission (PR #435) (Friday, 12 January)
• Re: [w3c/permissions] Editorial: Update link to accelerometer permission (PR #435) (Friday, 12 January)
• Re: [w3c/permissions] Editorial: Update link to accelerometer permission (PR #435) (Friday, 12 January)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Thursday, 11 January)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Tuesday, 2 January)

Mike Wasserman

• [whatwg/fullscreen] WIP: Enable configuration for fullscreen without transient activation (PR #235) (Thursday, 25 January)
• [whatwg/fullscreen] Entering fullscreen without transient activation (Issue #234) (Thursday, 25 January)

Miklos Vajna

• [w3c/clipboard-apis] RTF is not exposed when using navigator.clipboard.read() (Issue #210) (Thursday, 18 January)

Miniontoby

• Re: [w3c/gamepad] Require secure context for gamepad state and events (#120) (Tuesday, 16 January)

Mirko Brodesser

• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Wednesday, 31 January)

Ms2ger

• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Friday, 12 January)
• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Thursday, 11 January)
• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Thursday, 11 January)
• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Thursday, 11 January)

Mustaq Ahmed

• Re: [w3c/pointerlock] [Editorial] Fix `browsing context` links. (PR #88) (Tuesday, 30 January)
• Re: [w3c/pointerlock] [Editorial] Fix `browsing context` links. (PR #88) (Tuesday, 30 January)
• [w3c/pointerlock] [Editorial] Fix `browsing context` links. (PR #88) (Monday, 29 January)
• [w3c/pointerlock] Editorial: Broken HTML and DOM references (Issue #87) (Monday, 29 January)
• Re: [w3c/pointerlock] Make scheib a co-editor. (PR #86) (Monday, 29 January)
• Re: [w3c/pointerlock] Make scheib a co-editor. (PR #86) (Friday, 26 January)
• Re: [w3c/pointerlock] Make scheib a co-editor. (PR #86) (Friday, 26 January)
• [w3c/pointerlock] Make scheib a co-editor. (PR #86) (Friday, 26 January)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 2 January)

Nan Lin

• Re: [w3ctag/design-reviews] Review Request for Attribution Reporting API (Issue #724) (Wednesday, 24 January)

Nathan Knowler

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 9 January)

ngdangtu

• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Wednesday, 24 January)

Nick Coury

• Re: [w3ctag/design-reviews] Navigation Activation Info (Issue #921) (Thursday, 11 January)

Nidhi Jaju

• Re: [whatwg/streams] Editorial: Export byte streams related terms (PR #1303) (Monday, 29 January)
• Re: [whatwg/streams] Editorial: Export byte streams related terms (PR #1303) (Monday, 29 January)
• [whatwg/streams] Editorial: Export byte streams related terms (PR #1303) (Monday, 29 January)

Noam Rosenthal

• Re: [whatwg/fetch] WIP: Public subresource check (PR #1617) (Monday, 15 January)
• Re: [whatwg/fetch] WIP: Public subresource check (PR #1617) (Monday, 15 January)
• Re: [w3ctag/design-reviews] Navigation Activation Info (Issue #921) (Thursday, 11 January)
• Re: [w3ctag/design-reviews] Navigation Activation Info (Issue #921) (Tuesday, 9 January)
• Re: [w3ctag/design-reviews] Long Animation Frame API (LoAF) (Issue #911) (Thursday, 4 January)

Nolan Lawson

• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Wednesday, 10 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 9 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 9 January)

Norren

• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Wednesday, 17 January)

nxthor

• Re: [w3c/push-api] Some things about the PushEncryptionKeys p256dh and auth are not clear enough (#212) (Tuesday, 30 January)

Oliver Dunk

• Re: [w3c/ServiceWorker] dynamically registered event listeners for extension service worker (Issue #1698) (Monday, 8 January)

Pascal Schilp

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 15 January)

pascal vos

• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 9 January)

Patrick H. Lauke

• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Tuesday, 30 January)

patrick kettner

• [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Tuesday, 16 January)

Paul Jensen

• Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723) (Thursday, 25 January)

Paul Norman

• Re: [whatwg/fetch] Consider shifting the "bad port list" to an allowlist. (#1189) (Thursday, 25 January)

Peter Burns

• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Wednesday, 24 January)

Peter Linss

• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Friday, 26 January)

Philip Jägenstedt

• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 10 January)

Pierre-Anthony Lemieux

• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Wednesday, 31 January)

Pierre-Yves Gérardy

• Re: [whatwg/dom] Side effects due to tree insertion or removal (script, iframe) (#808) (Wednesday, 31 January)

pma-90

• Re: [whatwg/url] IdnaTestV2.json "xn--xn--a--gua.pt" test case problem (Issue #803) (Friday, 19 January)
• Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810) (Saturday, 6 January)

Rajeev1011

• Re: [w3c/manifest] err_invalid_url (Issue #1107) (Saturday, 6 January)
• [w3c/manifest] err_invalid_url (Issue #1107) (Saturday, 6 January)

Rin Arakaki

• [w3c/manifest] Reword ‘member’ to ‘field’ (Issue #1108) (Saturday, 6 January)

Rob Eisenberg

• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Monday, 22 January)
• Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 14 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 12 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 9 January)

Robert Knight

• Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Wednesday, 31 January)
• Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Wednesday, 31 January)

Ruben Van de Velde

• Re: [whatwg/webidl] Allow for global objects with a mutable prototype chain (PR #1381) (Friday, 12 January)

Ryosuke Niwa

• Re: [WICG/webcomponents] Jan 2024 DOM Parts Quarterly Meeting (Issue #1027) (Thursday, 25 January)
• Re: [WICG/webcomponents] Jan 2024 DOM Parts Quarterly Meeting (Issue #1027) (Thursday, 25 January)
• Re: [WICG/webcomponents] Jan 2024 DOM Parts Quarterly Meeting (Issue #1027) (Thursday, 25 January)
• Re: [WICG/webcomponents] Jan 2024 DOM Parts Quarterly Meeting (Issue #1027) (Thursday, 25 January)
• Re: [WICG/webcomponents] Jan 2024 DOM Parts Quarterly Meeting (Issue #1027) (Thursday, 25 January)
• Re: [WICG/webcomponents] Jan 2024 DOM Parts Quarterly Meeting (Issue #1027) (Thursday, 25 January)
• [WICG/webcomponents] April 2024 DOM Parts Quarterly Meeting (Issue #1047) (Wednesday, 24 January)
• Re: [whatwg/dom] clone with clone children flag set should append clone before cloning children (Issue #1219) (Wednesday, 24 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Tuesday, 16 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 16 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Sunday, 14 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 13 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 12 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Friday, 12 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Wednesday, 10 January)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Tuesday, 9 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Monday, 8 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Monday, 8 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Friday, 5 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Friday, 5 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Tuesday, 2 January)

Sage

• Re: [w3c/pointerlock] movementX/Y coordinate space (#42) (Friday, 12 January)

Sasha Firsov

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

Scott Haseley

• Re: [whatwg/dom] Prevent AbortSignal.any() from causing duplicates in source signals (PR #1244) (Tuesday, 9 January)

Shawn Blake

• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Tuesday, 16 January)
• [whatwg/storage] Update build.yml (PR #170) (Tuesday, 16 January)

Shivani Sharma

• Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838) (Monday, 15 January)

Shu-yu Guo

• Re: [whatwg/webidl] "byte length of a buffer source type" needs updating for resizable and detached buffers (Issue #1385) (Tuesday, 23 January)

Simon Pieters

• Re: [w3c/uievents] Specify the textInput event (PR #362) (Monday, 29 January)
• [w3c/uievents] Define inputType "insertFromPasteAsQuotation" (Issue #368) (Monday, 29 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Monday, 29 January)
• [w3c/uievents] Define events for drag-and-drop operations (textInput etc) (Issue #367) (Monday, 29 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Monday, 29 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Tuesday, 23 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Tuesday, 23 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Tuesday, 23 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Tuesday, 23 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Monday, 15 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 11 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 11 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 11 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 11 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 11 January)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 11 January)
• Re: [w3c/uievents] Define events directly caused by user interaction (#270) (Thursday, 11 January)
• Re: [w3c/uievents] Browsers do not fire select event with UIEvent (#284) (Thursday, 11 January)
• Re: [w3c/uievents] Redefine when `keypress` event should be fired (#266) (Thursday, 11 January)
• Re: [w3c/uievents] Define groups of events by the interaction that caused them (#311) (Thursday, 11 January)
• [w3c/uievents] Require support for legacy events (Issue #366) (Thursday, 11 January)
• Re: [w3c/uievents] Cancelable/default action for keydown, composition*, beforeinput, textInput, input (Issue #361) (Thursday, 11 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Monday, 8 January)

smaug----

• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Tuesday, 30 January)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Tuesday, 2 January)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Tuesday, 2 January)
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Tuesday, 2 January)
• Re: [WICG/webcomponents] Observing slotchange mutation records: a `SlotChangeObserver` API similar to `MutationObserver` with `childList:true` (Issue #1042) (Tuesday, 2 January)

snianu

• Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Wednesday, 31 January)
• Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Thursday, 25 January)
• [w3c/clipboard-apis] `supports` should take a dictionary instead of a DOMString as argument for readability (Issue #211) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Thursday, 25 January)
• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Tuesday, 23 January)
• Re: [w3c/clipboard-apis] Read Blob data for the supported formats on-demand during getType. (Issue #191) (Thursday, 18 January)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Thursday, 18 January)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Wednesday, 17 January)
• Re: [w3c/clipboard-apis] Read Blob data for the supported formats on-demand during getType. (Issue #191) (Thursday, 4 January)
• [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Wednesday, 3 January)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Tuesday, 2 January)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Tuesday, 2 January)
• Re: [w3c/editing] Delayed clipboard rendering API shape. (Issue #423) (Tuesday, 2 January)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Tuesday, 2 January)

Steve Orvell

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 17 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 15 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 13 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 13 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 13 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Thursday, 11 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 10 January)
• Re: [WICG/webcomponents] Allow customElementRegistry definitions to persist across page loads (Issue #1033) (Tuesday, 9 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 9 January)
• [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without Shadow DOM (Issue #1043) (Monday, 8 January)

Sun Shin

• Re: [w3c/gamepad] Add trackpad button support (Issue #191) (Friday, 26 January)
• Re: [w3c/gamepad] Add trackpad button support (Issue #191) (Friday, 26 January)

Swoorup Joshi

• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Thursday, 18 January)
• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Wednesday, 17 January)

Tab Atkins Jr.

• Re: [whatwg/url] Editorial: add a URL path concept (PR #812) (Thursday, 25 January)

TAMURA, Kent

• Re: [w3ctag/design-reviews] `field-sizing` CSS property (Issue #890) (Tuesday, 9 January)

Tanancha Prawanna

• [w3c/ServiceWorker] Ms. Tanancha prawanna (Issue #1703) (Wednesday, 24 January)
• [w3c/ServiceWorker] Ms. Tanancha prawanna (Issue #1702) (Wednesday, 24 January)

tguild

• Re: [w3ctag/design-reviews] VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport (Issue #768) (Tuesday, 30 January)

Thomas

• Re: [whatwg/storage] Allow all storage types to expire, not just cookies (#11) (Saturday, 13 January)

Thomas Steiner

• Re: [w3ctag/design-reviews] Tabbed web apps (Issue #841) (Tuesday, 23 January)
• Re: [w3c/ServiceWorker] Support import() local code in extension service worker (Issue #1700) (Monday, 8 January)
• Re: [w3c/ServiceWorker] dynamically registered event listeners for extension service worker (Issue #1698) (Monday, 8 January)

Tim Nguyen

• Re: [whatwg/fullscreen] How should UAs hide root element scrollbars? (Issue #236) (Saturday, 27 January)
• Re: [whatwg/fullscreen] How should UAs hide scrollbars? (Issue #236) (Saturday, 27 January)
• Re: [whatwg/fullscreen] How should UAs hide scrollbars? (Issue #236) (Saturday, 27 January)
• Re: [whatwg/fullscreen] How should UAs hide scrollbars? (Issue #236) (Saturday, 27 January)
• [whatwg/fullscreen] How should UAs hide scrollbars? (Issue #236) (Saturday, 27 January)

Tom Schuster

• Re: [whatwg/url] Web compatibility issue with various unknown (external) protocols like ed2k (Issue #815) (Monday, 29 January)
• [whatwg/url] Web compatibility issue with various unknown (external) protocols like ed2k (Issue #815) (Monday, 29 January)

Trishamalone16

• Re: [whatwg/xhr] XMLHttpRequest Standard (Issue #384) (Thursday, 18 January)
• [whatwg/xhr] XMLHttpRequest Standard (Issue #384) (Thursday, 18 January)

Valentin Gosu

• Re: [whatwg/url] Web compatibility issue with various unknown (external) protocols like ed2k (Issue #815) (Monday, 29 January)

Vincent Hilla

• Re: [whatwg/dom] Prevent AbortSignal.any() from causing duplicates in source signals (PR #1244) (Tuesday, 16 January)
• Re: [whatwg/dom] Prevent AbortSignal.any() from causing duplicates in source signals (PR #1244) (Tuesday, 16 January)
• Re: [whatwg/dom] Prevent AbortSignal.any() from causing duplicates in source signals (PR #1244) (Tuesday, 9 January)
• [whatwg/dom] Prevent AbortSignal.any() from causing duplicates in source signals (PR #1244) (Tuesday, 9 January)

Vincent Scheib

• Re: [w3c/pointerlock] Make scheib a co-editor. (PR #86) (Friday, 26 January)
• Re: [w3c/pointerlock] Make scheib a co-editor. (PR #86) (Friday, 26 January)

vmpstr

• Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353) (Monday, 29 January)
• Re: [whatwg/webidl] Add distinguishable state for cb and dictionary-like (PR #1353) (Monday, 29 January)

Westbrook Johnson

• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Thursday, 11 January)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Wednesday, 10 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Wednesday, 10 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Wednesday, 10 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Monday, 8 January)
• Re: [WICG/webcomponents] Observing slotchange mutation records: a `SlotChangeObserver` API similar to `MutationObserver` with `childList:true` (Issue #1042) (Sunday, 7 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Saturday, 6 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Friday, 5 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Friday, 5 January)
• Re: [WICG/webcomponents] DOM Parts Quarterly Meeting (Issue #1027) (Friday, 5 January)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Wednesday, 3 January)

woody-li

• [WICG/webcomponents] What's the right target of anchor link inside shadowDom (Issue #1048) (Monday, 29 January)

Xiaobin Cui

• Re: [w3ctag/design-reviews] Side Panel (Issue #903) (Friday, 26 January)

Xiaoqian Wu

• Re: [w3c/DOM-Parsing] DOM Parsing from stream (Issue #77) (Tuesday, 2 January)

Xidorn Quan

• Re: [whatwg/fullscreen] How should UAs hide root element scrollbars? (Issue #236) (Saturday, 27 January)
• Re: [whatwg/fullscreen] How should UAs hide scrollbars? (Issue #236) (Saturday, 27 January)
• Re: [whatwg/fullscreen] Removing `:fullscreen-ancestor` pseudo-class causes webcompat issue (#103) (Saturday, 27 January)
• Re: [whatwg/fullscreen] Removing `:fullscreen-ancestor` pseudo-class causes webcompat issue (#103) (Saturday, 27 January)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 25 January)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 24 January)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 18 January)
• [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Monday, 15 January)

Yves Lafon

• Re: [w3ctag/design-reviews] deliveryType (Resource Timing) (Issue #858) (Monday, 8 January)
• Re: [w3ctag/design-reviews] deliveryType (Resource Timing) (Issue #858) (Monday, 8 January)

一丝

• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 9 January)

华

• Re: [whatwg/fetch] Extend Cross-Origin-Resource-Policy to take origin values (#760) (Thursday, 18 January)

Last message date: Wednesday, 31 January 2024 22:50:49 UTC