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

Aaron Gustafson

• Re: [w3c/manifest] Web Manifest Overrides (Issue #1045) (Friday, 3 May)

Adam Rice

• Re: [whatwg/fetch] Question about stream handling around fetch requests with integrity metadata (Issue #1754) (Friday, 24 May)
• Re: [whatwg/streams] read all bytes usage/signature may be hard to understand (Issue #1315) (Thursday, 23 May)
• Re: [whatwg/streams] read all bytes usage/signature may be hard to understand (Issue #1315) (Thursday, 23 May)

Addison Phillips

• Re: [w3c/manifest] fix: dir's auto definition (PR #1118) (Friday, 3 May)

Alex Russell

• Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723) (Wednesday, 8 May)

Alexandra Borovova

• [w3c/permissions] Add an optional `topLevelOrigin` argument to `permissions.setPermission` WebDriver BiDi command (Issue #450) (Tuesday, 7 May)

Alvin Ji

• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 28 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 28 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 28 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 28 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 28 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 28 May)
• [w3c/pointerlock] lock requests queue processing is incomplete (Issue #96) (Tuesday, 28 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 23 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 16 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 16 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 9 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 9 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Thursday, 9 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 8 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 8 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 8 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 8 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 8 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 8 May)
• [w3c/pointerlock] When a subsequent requestPointerLock is rejected, should an already locked target exit lock state? (Issue #91) (Monday, 6 May)
• [w3c/pointerlock] Propose to add a static field to indicate whether `unadjustedMovement` is supported. (Issue #90) (Monday, 6 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Monday, 6 May)

Amy Guy

• Re: [w3ctag/design-reviews] Tidy up; add Focus labels by default (PR #953) (Monday, 6 May)
• [w3ctag/design-reviews] Tidy up; add Focus labels by default (PR #953) (Monday, 6 May)

Andrea Canciani

• Re: [w3c/ServiceWorker] Registering service workers for unique origins? (#1437) (Saturday, 4 May)
• Re: [w3c/ServiceWorker] Registering service workers for unique origins? (#1437) (Saturday, 4 May)

Andrea Giammarchi

• Re: [whatwg/storage] Expose IndexedDB IDBObjectStore.purge() method (Issue #174) (Friday, 31 May)
• Re: [whatwg/storage] Expose IndexedDB IDBObjectStore.purge() method (Issue #174) (Friday, 31 May)
• [w3c/IndexedDB] Expose IndexedDB IDBObjectStore.purge() method (Issue #420) (Friday, 31 May)
• Re: [whatwg/storage] Expose IndexedDB IDBObjectStore.purge() method (Issue #174) (Friday, 31 May)
• Re: [whatwg/storage] Expose IndexedDB IDBObjectStore.purge() method (Issue #174) (Friday, 31 May)
• Re: [whatwg/storage] Expose IndexedDB IDBObjectStore.purge() method (Issue #174) (Friday, 31 May)
• Re: [whatwg/storage] Expose IndexedDB IDBObjectStore.purge() method (Issue #174) (Friday, 31 May)
• [whatwg/storage] Expose IndexedDB IDBObjectStore.purge() method (Issue #174) (Friday, 31 May)
• [whatwg/streams] Symbol.clone to ease-out structuredClone implicit conversion (Issue #1314) (Tuesday, 14 May)
• Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287) (Thursday, 9 May)
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Thursday, 2 May)

Anne van Kesteren

• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/storage] Expose IndexedDB IDBObjectStore.purge() method (Issue #174) (Friday, 31 May)
• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/dom] Closed Shadow DOM blocks accessibility testing (Issue #1290) (Wednesday, 29 May)
• Re: [whatwg/dom] Closed Shadow DOM blocks accessibility testing (Issue #1290) (Wednesday, 29 May)
• Re: [w3c/selection-api] Selection.direction spec issue, what should happen on multiple click? (Issue #177) (Tuesday, 28 May)
• Re: [w3c/FileAPI] Modernize Blob constructor a tiny bit (#125) (Sunday, 26 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #198) (Friday, 24 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #198) (Friday, 24 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Friday, 24 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Friday, 24 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Thursday, 23 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Thursday, 23 May)
• Re: [whatwg/url] Proposal: URL.setSearchParams() (Issue #828) (Thursday, 23 May)
• Re: [whatwg/fetch] Question about stream handling around fetch requests with integrity metadata (Issue #1754) (Wednesday, 22 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Friday, 17 May)
• Re: [whatwg/dom] Request for mechanism to determine if children changed steps are called as a result of script or parser (Issue #1288) (Thursday, 16 May)
• Re: [whatwg/fetch] add a method to get a Uint8Array to Body (Issue #1732) (Tuesday, 14 May)
• Re: [whatwg/fetch] Add bytes() method to Body mixin (PR #1753) (Tuesday, 14 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Monday, 13 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Monday, 13 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Monday, 13 May)
• Re: [whatwg/fetch] Add bytes() method to Body mixin (PR #1753) (Monday, 13 May)
• [w3c/ServiceWorker] No examples around addRoutes() API (Issue #1717) (Tuesday, 7 May)
• [w3c/ServiceWorker] Editorial: "mutual exclusive" (Issue #1716) (Tuesday, 7 May)
• Re: [whatwg/fetch] “Realmless” ArrayBuffer creation in Body’s arrayBuffer() steps (Issue #1675) (Tuesday, 7 May)
• Re: [whatwg/fetch] Editorial: Fix realmless ArrayBuffer creation (PR #1751) (Tuesday, 7 May)
• Re: [whatwg/fetch] Editorial: Fix realmless ArrayBuffer creation (PR #1751) (Tuesday, 7 May)
• Re: [whatwg/fetch] Editorial: Fix realmless ArrayBuffer creation (PR #1751) (Tuesday, 7 May)
• Re: [whatwg/fetch] Editorial: Fix realmless ArrayBuffer creation (PR #1751) (Monday, 6 May)
• Re: [whatwg/fetch] Editorial: Add missing comma after "json" (PR #1750) (Monday, 6 May)
• Re: [whatwg/fetch] Editorial: Add missing comma after "json" (PR #1750) (Monday, 6 May)
• Re: [whatwg/fetch] Editorial: Add missing comma after "json" (PR #1750) (Monday, 6 May)
• Re: [whatwg/fetch] Editorial: Fix realmless ArrayBuffer creation (PR #1751) (Monday, 6 May)
• Re: [whatwg/fetch] Editorial: link "a new promise" (PR #1752) (Monday, 6 May)
• Re: [whatwg/dom] Proposal: elementsFromRect() (Issue #1286) (Friday, 3 May)
• Re: [whatwg/fetch] fetch does not allow caching requests with a null client (Issue #1749) (Thursday, 2 May)
• Re: [whatwg/fetch] Consider renaming or replacing http3only? (Issue #1744) (Thursday, 2 May)
• Re: [whatwg/fetch] Rename http3Only to requireUnreliable (PR #1745) (Thursday, 2 May)
• Re: [w3c/clipboard-apis] The permission request stuff is no longer in contention (PR #214) (Thursday, 2 May)

Anssi Kostiainen

• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Friday, 31 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #369) (Thursday, 30 May)
• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Monday, 20 May)

Aral Roca Gomez

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Wednesday, 15 May)

Ari Chivukula

• Re: [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Monday, 20 May)
• [w3ctag/design-reviews] Early Design Review: Partitioned Popins (Issue #956) (Tuesday, 14 May)

BlobTheKat

• Re: [w3c/gamepad] Drop SecureContext extended attrs from interfaces (PR #194) (Thursday, 30 May)
• Re: [w3c/pointerlock] movementX/Y coordinate space (#42) (Friday, 10 May)
• Re: [w3c/gamepad] Re-enable Gamepad Access from HTTP (aka insecure) Context (Issue #203) (Wednesday, 8 May)
• Re: [w3c/gamepad] Require secure context for gamepad state and events (#120) (Wednesday, 8 May)

Bruce B. Anderson

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

bryanalia

• Re: [whatwg/dom] Editorial: explain the possible primary interfaces for nodes (abaa3fb) (Thursday, 23 May)

Chris Lilley

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

Christian Biesinger

• [whatwg/fetch] fetch does not allow caching requests with a null client (Issue #1749) (Wednesday, 1 May)

Christian Liebel

• Re: [w3c/manifest] Wammi123 (Issue #1129) (Tuesday, 28 May)
• Re: [w3c/manifest] Wammi123 (Issue #1127) (Saturday, 18 May)
• Re: [w3c/manifest] Wammi123 (Issue #1126) (Saturday, 18 May)
• Re: [w3c/manifest] Spec Metadata Lists Incorrect Values for Chrome (#939) (Friday, 17 May)
• Re: [w3c/manifest] Spec Metadata Lists Incorrect Values for Chrome (#939) (Friday, 17 May)
• [w3c/manifest] Add Christian as editor (PR #1125) (Friday, 17 May)

Christian Stewart

• Re: [whatwg/fetch] what should fetch() do if request's window has been destroyed or stopped? (#153) (Tuesday, 7 May)
• Re: [w3c/ServiceWorker] should FetchEvent.request.signal reflect abort status of outer request? (#1544) (Tuesday, 7 May)

Ciprian Amariei

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

CSS Meeting Bot

• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Thursday, 9 May)
• Re: [w3c/editing] normative spec changes do not always end up as issues filed with browsers (Issue #463) (Thursday, 9 May)
• Re: [w3c/editing] TPAC 2024 participation (Issue #462) (Thursday, 9 May)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Speculation rules: target_hint field (Issue #931) (Wednesday, 22 May)
• Re: [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Monday, 20 May)
• Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838) (Wednesday, 15 May)
• Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Wednesday, 15 May)
• Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Wednesday, 1 May)
• Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Wednesday, 1 May)

Daniel Ehrenberg

• Re: [WICG/webcomponents] Idea: A tree-aware task scheduler (Issue #1055) (Saturday, 4 May)

Daniel Murphy

• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Thursday, 23 May)
• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Tuesday, 21 May)
• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Monday, 20 May)
• Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092) (Thursday, 16 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Monday, 6 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Thursday, 2 May)
• Re: [w3c/manifest] Web Manifest Overrides (Issue #1045) (Thursday, 2 May)

Daniel Vogelheim

• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Wednesday, 22 May)

David Alsh

• Re: [whatwg/storage] Allow all storage types to expire, not just cookies (#11) (Monday, 6 May)

David Benjamin

• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Tuesday, 28 May)

Diego Gonzalez

• Re: [w3c/manifest] Chore: add Diego as editor, retire Aaron (PR #1124) (Monday, 13 May)

Domenic Denicola

• Re: [whatwg/url] Proposal: URL.setSearchParams() (Issue #828) (Friday, 24 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Thursday, 16 May)
• Re: [whatwg/streams] Symbol.clone to ease-out structuredClone implicit conversion (Issue #1314) (Wednesday, 15 May)
• Re: [whatwg/streams] Symbol.clone to ease-out structuredClone implicit conversion (Issue #1314) (Wednesday, 15 May)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Thursday, 9 May)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Wednesday, 8 May)
• Re: [whatwg/fullscreen] Don't close ancestor popovers when fullscreening (PR #237) (Tuesday, 7 May)
• Re: [whatwg/fullscreen] Don't close ancestor popovers when fullscreening (PR #237) (Tuesday, 7 May)
• Re: [whatwg/fullscreen] Don't close ancestor popovers when fullscreening (PR #237) (Tuesday, 7 May)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Tuesday, 7 May)

Dominic Farolino

• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• [whatwg/dom] Should post-connected steps be able to run multiple times during insertion? (Issue #1291) (Friday, 31 May)
• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/dom] Introduce DOM post-connection steps (PR #1261) (Friday, 31 May)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Thursday, 16 May)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Wednesday, 15 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Monday, 13 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Monday, 13 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Wednesday, 8 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Wednesday, 8 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Sunday, 5 May)
• Re: [w3c/IndexedDB] Clarify interaction of IndexedDB lifecycles with relation to document and worker lifecycle mechanics (Issue #416) (Saturday, 4 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Wednesday, 1 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Wednesday, 1 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Wednesday, 1 May)

Edgar Chen

• Re: [w3c/clipboard-apis] Make it possible to read image/svg+xml from the clipboard (#92) (Thursday, 30 May)
• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Wednesday, 8 May)

Elad Alon

• [w3ctag/design-reviews] Element Capture (Issue #954) (Friday, 10 May)

Erik96922@gmail.com

• [w3c/manifest] Wammi123 (Issue #1129) (Tuesday, 28 May)
• [w3c/manifest] IHeyReally-85d32 (Issue #1128) (Monday, 27 May)
• [w3c/manifest] Wammi123 (Issue #1127) (Saturday, 18 May)
• [w3c/manifest] Wammi123 (Issue #1126) (Saturday, 18 May)
• Re: [w3c/manifest] IHeyReally (Issue #1123) (Friday, 10 May)
• [w3c/manifest] IHeyReally (Issue #1123) (Friday, 10 May)

Eugene Zemtsov

• [w3ctag/design-reviews] Conversion to RGB in VideoFrame.copyTo() (Issue #951) (Wednesday, 1 May)

fantasai

• Re: [w3ctag/design-reviews] Specification review for CSS Anchor Positioning (Issue #848) (Monday, 13 May)

Florian Rivoal

• [w3ctag/design-reviews] Requesting review of HTML Ruby Markup Extensions (Issue #959) (Friday, 31 May)

Frank Lemanschik

• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Thursday, 16 May)

François Beaufort

• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Monday, 13 May)

Frederik Braun

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

Fredrik Hernqvist

• Re: [w3ctag/design-reviews] Early TAG review request for Playout Statistics API for WebAudio (Issue #939) (Wednesday, 15 May)

github-actions[bot]

• [w3c/pointerlock] Tidied up document using tidy-html5 (PR #95) (Wednesday, 8 May)

Grant Forrest

• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Tuesday, 21 May)
• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Monday, 20 May)
• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Friday, 17 May)

Greg Horvath

• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Friday, 17 May)
• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Wednesday, 15 May)

Gregory Terzian

• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Tuesday, 21 May)
• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Monday, 20 May)

Guillaume Brunerie

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Thursday, 16 May)
• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Wednesday, 15 May)

Han Seoul-Oh

• [w3c/uievents] Need virtual key codes (Issue #377) (Thursday, 16 May)
• Re: [w3c/uievents] Proposal: Way to determine if any modifier key is pressed (#151) (Wednesday, 15 May)
• Re: [w3c/uievents] How do web apps distinguish if a keydown event causes text input? (#18) (Wednesday, 15 May)
• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)
• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)
• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)
• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)
• Re: [w3c/uievents] no way to distinguish printable key values from non-printable (#264) (Wednesday, 15 May)
• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)

Henri Sivonen

• [w3c/DOM-Parsing] No-namespace element serialized in a namespace if DOM Level 1 xmlns attribute set (Issue #83) (Thursday, 30 May)

Henrik Skupin

• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Thursday, 23 May)
• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Wednesday, 8 May)

hober

• Re: [w3ctag/design-reviews] Support Video Chapter in MediaMetadata (Issue #952) (Monday, 20 May)
• Re: [w3ctag/design-reviews] Support Video Chapter in MediaMetadata (Issue #952) (Monday, 20 May)
• Re: [w3ctag/design-reviews] Importmap integrity (Issue #944) (Friday, 3 May)

i18n-now

• Re: [w3c/ServiceWorker] Promise on navigator.serviceWorker that resolves when page is controlled (#799) (Sunday, 26 May)

Ian Clelland

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

Jake Archibald

• Re: [whatwg/storage] Expose IndexedDB IDBObjectStore.purge() method (Issue #174) (Friday, 31 May)

Jakub T. Jankiewicz

• Re: [w3c/ServiceWorker] Support modifying cookies on an intercepted fetch (#837) (Thursday, 16 May)

James Browning

• [whatwg/dom] Add a method like .addTeardown to AbortSignal (Issue #1289) (Saturday, 18 May)
• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Saturday, 11 May)

James Howard

• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Friday, 10 May)

James M Snell

• Re: [whatwg/url] Proposal: URL.setSearchParams() (Issue #828) (Thursday, 23 May)
• Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 9 May)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Tuesday, 7 May)
• Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Saturday, 4 May)

Jamie

• Re: [whatwg/fetch] Editorial: Add missing comma after "json" (PR #1750) (Monday, 6 May)
• Re: [whatwg/fetch] Editorial: Add missing comma after "json" (PR #1750) (Monday, 6 May)
• Re: [whatwg/fetch] Editorial: Add missing comma after "json" (PR #1750) (Friday, 3 May)
• [whatwg/fetch] Editorial: Add missing comma after "json" (PR #1750) (Friday, 3 May)

Jared White

• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Wednesday, 8 May)

jarhar

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Wednesday, 8 May)

Jeremy Nguyen

• [whatwg/url] Proposal: URL.setSearchParams() (Issue #828) (Thursday, 23 May)

jgraham

• [whatwg/fetch] Webdriver cache mode (PR #1756) (Wednesday, 29 May)

jiamingc

• Re: [w3ctag/design-reviews] Support Video Chapter in MediaMetadata (Issue #952) (Monday, 20 May)
• [w3ctag/design-reviews] Add Skip-Ad media session action (Issue #957) (Wednesday, 15 May)
• [w3ctag/design-reviews] Support Video Chapter in MediaMetadata (Issue #952) (Saturday, 4 May)

Joe Pea

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Thursday, 16 May)
• Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287) (Wednesday, 15 May)
• Re: [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287) (Wednesday, 15 May)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Wednesday, 15 May)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Wednesday, 15 May)

Joe Puccio

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

Joey Arhar

• Re: [whatwg/fullscreen] Don't close ancestor popovers when fullscreening (PR #237) (Friday, 3 May)

Johannes Wilm

• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Friday, 24 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Friday, 24 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Thursday, 23 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Wednesday, 22 May)
• [w3c/editing] normative spec changes do not always end up as issues filed with browsers (Issue #463) (Thursday, 9 May)
• [w3c/editing] TPAC 2024 participation (Issue #462) (Thursday, 9 May)
• Re: [w3c/editing] Upstream changes from Trusted Types (PR #460) (Thursday, 9 May)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Thursday, 2 May)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Thursday, 2 May)

Joshua Bell

• Re: [whatwg/webidl] Float16Array integration (Issue #1310) (Friday, 17 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Friday, 10 May)

Joshua Chen

• Re: [whatwg/webidl] Float16Array integration (Issue #1310) (Friday, 17 May)
• Re: [whatwg/webidl] Float16Array integration (Issue #1310) (Friday, 17 May)

Julia Remus

• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Monday, 20 May)

Justin Fagnani

• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Friday, 10 May)
• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Friday, 3 May)
• [whatwg/dom] Proposal: elementsFromRect() (Issue #1286) (Thursday, 2 May)

Kagami Sascha Rosylight

• Re: [w3c/FileAPI] Modernize Blob constructor a tiny bit (#125) (Sunday, 26 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Saturday, 25 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Saturday, 25 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Friday, 24 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #198) (Friday, 24 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #198) (Friday, 24 May)
• Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 24 May)
• [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Wednesday, 22 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Wednesday, 22 May)
• Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Wednesday, 15 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Wednesday, 15 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Monday, 13 May)
• Re: [w3c/uievents] mousemove and preventDefault() (#278) (Wednesday, 8 May)

Keita Suzuki

• [w3ctag/design-reviews] Timing Info for ServiceWorker static routing API (Issue #958) (Tuesday, 28 May)

Kevin Gibbons

• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #369) (Thursday, 30 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Wednesday, 29 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Friday, 24 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Tuesday, 21 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Tuesday, 21 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #369) (Tuesday, 21 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #369) (Tuesday, 21 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #369) (Monday, 20 May)
• Re: [whatwg/webidl] Float16Array integration (Issue #1310) (Friday, 17 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Monday, 13 May)
• Re: [whatwg/fetch] Add bytes() method to Body mixin (PR #1753) (Monday, 13 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Monday, 13 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #369) (Monday, 13 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Friday, 10 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Friday, 10 May)
• [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #369) (Friday, 10 May)
• [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Friday, 10 May)
• [whatwg/fetch] Add bytes() method to Body mixin (PR #1753) (Friday, 10 May)
• Re: [whatwg/fetch] Editorial: Fix realmless ArrayBuffer creation (PR #1751) (Monday, 6 May)
• Re: [whatwg/fetch] Editorial: Fix realmless ArrayBuffer creation (PR #1751) (Monday, 6 May)
• [whatwg/fetch] Editorial: link "a new promise" (PR #1752) (Saturday, 4 May)
• [whatwg/fetch] Editorial: Fix realmless ArrayBuffer creation (PR #1751) (Saturday, 4 May)

kirav

• Re: [w3ctag/design-reviews] Review request before CR: CSS `selector()` (Issue #709) (Monday, 20 May)

Knud

• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Wednesday, 29 May)
• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Wednesday, 8 May)

L. David Baron

• Re: [w3ctag/design-reviews] CSS calc-size() function (Issue #955) (Tuesday, 21 May)
• [w3ctag/design-reviews] CSS calc-size() function (Issue #955) (Tuesday, 14 May)

Lea Verou

• Re: [w3ctag/design-reviews] Specification review for CSS Anchor Positioning (Issue #848) (Friday, 24 May)
• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Monday, 13 May)
• [whatwg/dom] `MutationObserver` flag to observe mutations in (open) shadow trees to facilitate polyfills of HTML syntax (Issue #1287) (Wednesday, 8 May)
• Re: [w3ctag/design-reviews] Web Audio API: Add error reporting via AudioContext.onerror (Issue #950) (Monday, 6 May)

Luca Casonato

• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Tuesday, 7 May)
• Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397) (Tuesday, 7 May)

Luke Warlow

• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Thursday, 16 May)
• Re: [whatwg/dom] Request for mechanism to determine if children changed steps are called as a result of script or parser (Issue #1288) (Thursday, 16 May)
• [whatwg/dom] Request for mechanism to determine if children changed steps are called as a result of script or parser (Issue #1288) (Thursday, 16 May)
• Re: [w3c/editing] Upstream changes from trusted types (Issue #461) (Tuesday, 14 May)
• Re: [w3c/editing] Upstream changes from Trusted Types (PR #460) (Tuesday, 14 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Monday, 13 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Tuesday, 7 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Tuesday, 7 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Tuesday, 7 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Tuesday, 7 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Tuesday, 7 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Tuesday, 7 May)
• Re: [whatwg/dom] Trusted types attributes (PR #1268) (Tuesday, 7 May)

Maks Orlovich

• Re: [whatwg/streams] read all bytes usage/signature may be hard to understand (Issue #1315) (Thursday, 23 May)
• Re: [whatwg/streams] read all bytes usage/signature may be hard to understand (Issue #1315) (Thursday, 23 May)
• [whatwg/streams] read all bytes usage/signature may be hard to understand (Issue #1315) (Monday, 20 May)

Marcos Cáceres

• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Thursday, 30 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Thursday, 30 May)
• Re: [w3c/manifest] IHeyReally-85d32 (Issue #1128) (Tuesday, 28 May)
• Re: [w3c/FileAPI] Modernize Blob constructor a tiny bit (#125) (Sunday, 26 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Saturday, 25 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Thursday, 23 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Thursday, 23 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Tuesday, 21 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Tuesday, 21 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #369) (Tuesday, 21 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Tuesday, 21 May)
• [w3c/FileAPI] Add bytes() method for reading bytes into a Uint8Array (PR #198) (Tuesday, 21 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #369) (Tuesday, 21 May)
• [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Tuesday, 21 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Tuesday, 21 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Tuesday, 21 May)
• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Tuesday, 21 May)
• Re: [w3c/gamepad] Allow initializing the gamepad index to a specific value (PR #193) (Tuesday, 21 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Monday, 20 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Monday, 20 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #369) (Monday, 20 May)
• Re: [w3c/gamepad] Specify length of array when controllers are connected/disconnected. (#104) (Monday, 20 May)
• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Monday, 20 May)
• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Monday, 20 May)
• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Monday, 20 May)
• [w3c/gamepad] Chore(README.md): remove link to old features (PR #208) (Monday, 20 May)
• Re: [w3c/gamepad] Require system focus for gamepad user gesture (PR #207) (Monday, 20 May)
• Re: [w3c/manifest] Add Christian as editor (PR #1125) (Friday, 17 May)
• Re: [w3c/manifest] Add Christian as editor (PR #1125) (Friday, 17 May)
• Re: [w3c/pointerlock] Tidied up document using tidy-html5 (PR #95) (Thursday, 16 May)
• Re: [w3c/pointerlock] Tidied up document using tidy-html5 (PR #95) (Thursday, 16 May)
• Re: [w3c/manifest] Chore: add Diego as editor, retire Aaron (PR #1124) (Thursday, 16 May)
• Re: [w3c/gamepad] Add missing steps in getGamepads (PR #205) (Thursday, 16 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Thursday, 16 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Sunday, 12 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Sunday, 12 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Sunday, 12 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Sunday, 12 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Sunday, 12 May)
• Re: [w3c/manifest] Chore: add Diego as editor, retire Aaron (PR #1124) (Sunday, 12 May)
• Re: [w3c/manifest] Chore: add Diego as editor, retire Aaron (PR #1124) (Sunday, 12 May)
• Re: [w3c/manifest] Chore: add Diego as editor, retire Aaron (PR #1124) (Sunday, 12 May)
• Re: [w3c/manifest] Chore: add Diego as editor, retire Aaron (PR #1124) (Sunday, 12 May)
• [w3c/manifest] Chore: add Diego as editor, retire Aaron (PR #1124) (Sunday, 12 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Sunday, 12 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Sunday, 12 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Saturday, 11 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Saturday, 11 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Friday, 10 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Friday, 10 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Friday, 10 May)
• Re: [w3c/manifest] IHeyReally (Issue #1123) (Friday, 10 May)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 10 May)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 10 May)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 10 May)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 10 May)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 10 May)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 10 May)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 10 May)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 10 May)
• Re: [w3c/gamepad] Fold touchEvents from extensions.html into index.html (PR #198) (Friday, 10 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Friday, 10 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Thursday, 9 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Thursday, 9 May)
• Re: [w3c/gamepad] Editorial: add a Model section (#136) (Thursday, 9 May)
• Re: [w3c/gamepad] Re-enable Gamepad Access from HTTP (aka insecure) Context (Issue #203) (Thursday, 9 May)
• Re: [w3c/pointerlock] Editorial: Fix ReSpec error with ancestor browsing context (PR #89) (Wednesday, 8 May)
• Re: [w3c/pointerlock] Editorial: Broken HTML and DOM references (Issue #87) (Wednesday, 8 May)
• Re: [w3c/pointerlock] Editorial: Fix ReSpec error with ancestor browsing context (PR #89) (Wednesday, 8 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 8 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Tuesday, 7 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Tuesday, 7 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Tuesday, 7 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 7 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 7 May)
• [w3c/pointerlock] Visibility state checks (Issue #93) (Tuesday, 7 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 7 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 7 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 7 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 7 May)
• [w3c/pointerlock] Clarification on interaction with shadow-roots (Issue #92) (Tuesday, 7 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 7 May)
• Re: [w3c/manifest] fix: dir's auto definition (PR #1118) (Friday, 3 May)
• Re: [w3c/manifest] fix: dir's auto definition (PR #1118) (Thursday, 2 May)
• Re: [w3c/manifest] fix: dir's auto definition (PR #1118) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Thursday, 2 May)
• Re: [w3c/manifest] fix: dir's auto definition (PR #1118) (Thursday, 2 May)
• Re: [w3c/manifest] fix: dir's auto definition (PR #1118) (Thursday, 2 May)
• Re: [w3c/manifest] chore: tidy (PR #1119) (Thursday, 2 May)
• [w3c/manifest] chore: tidy (PR #1119) (Thursday, 2 May)
• Re: [w3c/manifest] fix: dir's auto definition (PR #1118) (Thursday, 2 May)
• Re: [w3c/manifest] fix: dir's auto definition (PR #1118) (Thursday, 2 May)
• [w3c/manifest] fix: dir's auto definition (PR #1118) (Thursday, 2 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Thursday, 2 May)
• Re: [w3c/manifest] Privacy consideration specifies an unenforceable "MUST NOT" condition on developers (Issue #1113) (Thursday, 2 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Thursday, 2 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Thursday, 2 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039) (Wednesday, 1 May)
• Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039) (Wednesday, 1 May)

Marijn Kruisselbrink

• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #198) (Friday, 24 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Monday, 13 May)
• Re: [w3c/FileAPI] Add bytes() method to Blob for reading bytes into a Uint8Array (PR #197) (Friday, 10 May)

Martin Thomson

• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Tuesday, 21 May)
• Re: [w3ctag/design-reviews] CSS calc-size() function (Issue #955) (Tuesday, 21 May)
• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #369) (Monday, 20 May)
• Re: [w3ctag/design-reviews] document.caretPositionFromPoint API in shadow DOM scenario (Issue #949) (Tuesday, 7 May)
• Re: [w3ctag/design-reviews] Web Audio API: Add error reporting via AudioContext.onerror (Issue #950) (Monday, 6 May)
• Re: [w3ctag/design-reviews] Web Audio API: Add error reporting via AudioContext.onerror (Issue #950) (Monday, 6 May)
• [w3c/clipboard-apis] The permission request stuff is no longer in contention (PR #214) (Wednesday, 1 May)

Mason Freed

• Re: [w3c/selection-api] Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary (Issue #176) (Monday, 20 May)
• Re: [w3c/selection-api] Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary (Issue #176) (Friday, 17 May)
• Re: [w3ctag/design-reviews] Specification review for CSS Anchor Positioning (Issue #848) (Monday, 13 May)

Matt Giuca

• Re: [w3c/manifest] Add a "tabbed application" mode (#737) (Monday, 27 May)
• Re: [w3ctag/design-reviews] Tabbed web apps (Issue #841) (Friday, 24 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Wednesday, 22 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Wednesday, 22 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Wednesday, 22 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Wednesday, 22 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Wednesday, 22 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Wednesday, 22 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Friday, 10 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Friday, 10 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Friday, 10 May)
• Re: [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Wednesday, 8 May)
• [w3c/manifest] Processing steps for id now removes the fragment (PR #1122) (Monday, 6 May)
• Re: [w3c/manifest] Manifest id should strip fragment at parse time (Issue #1121) (Monday, 6 May)
• [w3c/manifest] Manifest id should strip fragment at parse time (Issue #1121) (Monday, 6 May)
• Re: [w3c/manifest] fix: dir's auto definition (PR #1118) (Monday, 6 May)
• Re: [w3c/manifest] Remove problematic icon matching algorithm (PR #1120) (Friday, 3 May)
• Re: [w3c/manifest] fix: dir's auto definition (PR #1118) (Friday, 3 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)
• Re: [w3c/manifest] Rewrite privacy considerations on fingerprinting in start_url (PR #1114) (Wednesday, 1 May)

Matt Menke

• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Tuesday, 28 May)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Tuesday, 28 May)

Matt Reynolds

• Re: [w3c/gamepad] Require system focus for gamepad user gesture (PR #207) (Saturday, 25 May)
• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Saturday, 25 May)
• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Saturday, 25 May)
• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Saturday, 25 May)
• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Saturday, 25 May)
• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Saturday, 25 May)
• Re: [w3c/gamepad] Add sequenceId slot and fix effect promises (PR #201) (Saturday, 25 May)
• Re: [w3c/gamepad] Allow initializing the gamepad index to a specific value (PR #193) (Saturday, 25 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Wednesday, 22 May)
• Re: [w3c/gamepad] Length of getGamepads() array (#82) (Wednesday, 22 May)
• Re: [w3c/gamepad] Length of getGamepads() array (#82) (Wednesday, 22 May)
• Re: [w3c/gamepad] Specify length of array when controllers are connected/disconnected. (#104) (Wednesday, 22 May)
• Re: [w3c/gamepad] Specify length of array when controllers are connected/disconnected. (#104) (Wednesday, 22 May)
• Re: [w3c/gamepad] Allow initializing the gamepad index to a specific value (PR #193) (Tuesday, 21 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Saturday, 18 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Wednesday, 15 May)
• Re: [w3c/gamepad] Add missing steps in getGamepads (PR #205) (Tuesday, 14 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Friday, 10 May)
• [w3c/gamepad] Require system focus for gamepad user gesture (PR #207) (Friday, 10 May)
• Re: [w3c/gamepad] Re-enable Gamepad Access from HTTP (aka insecure) Context (Issue #203) (Friday, 10 May)
• [w3c/gamepad] Require focus for initial gamepad user gesture (Issue #206) (Friday, 10 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Friday, 10 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Friday, 10 May)
• Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202) (Friday, 10 May)
• Re: [w3c/gamepad] Add missing steps in getGamepads (PR #205) (Friday, 10 May)
• Re: [w3c/gamepad] Add missing steps in getGamepads (PR #205) (Friday, 10 May)
• [w3c/gamepad] Add missing steps in getGamepads (PR #205) (Friday, 10 May)
• [w3c/gamepad] gamepads is not defined in steps for getGamepads (Issue #204) (Friday, 10 May)
• Re: [w3c/gamepad] Re-enable Gamepad Access from HTTP (aka insecure) Context (Issue #203) (Thursday, 9 May)

Matthew Tylee Atkinson

• Re: [w3ctag/design-reviews] Updated review of WebNN API (Issue #933) (Thursday, 23 May)
• Re: [w3ctag/design-reviews] Speculation rules: target_hint field (Issue #931) (Wednesday, 22 May)
• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Wednesday, 22 May)
• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Monday, 20 May)

Mattias Buelens

• Re: [whatwg/streams] read all bytes usage/signature may be hard to understand (Issue #1315) (Thursday, 23 May)
• Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 9 May)
• Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Thursday, 9 May)
• Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 3 May)
• Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 3 May)

Michael Warren

• Re: [WICG/webcomponents] [open-stylable] Collection of user stories (Issue #1052) (Wednesday, 1 May)
• Re: [WICG/webcomponents] [open-stylable] Collection of user stories (Issue #1052) (Wednesday, 1 May)

Michiel De Backker

• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Monday, 20 May)

Mike Wasserman

• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Friday, 17 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Thursday, 16 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Thursday, 16 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Wednesday, 15 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Tuesday, 14 May)
• Re: [whatwg/fullscreen] WIP: Enable configuration for fullscreen without transient activation (PR #235) (Thursday, 9 May)

Mikko Rantalainen

• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Thursday, 2 May)

Mozes Stumpf

• Re: [w3c/selection-api] Selection.direction spec issue, what should happen on multiple click? (Issue #177) (Wednesday, 29 May)
• [w3c/selection-api] Selection.direction spec issue, what should happen on multiple click? (Issue #177) (Monday, 27 May)

Mustaq Ahmed

• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 28 May)
• [w3c/pointerlock] Section 2.1 should mention the effect of lock on PointerEvents (Issue #97) (Tuesday, 28 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 28 May)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Tuesday, 21 May)
• Re: [w3c/uievents] UI Event spec modernization task list (Issue #370) (Tuesday, 14 May)
• Re: [w3c/uievents] mousemove and preventDefault() (#278) (Thursday, 9 May)
• Re: [w3c/uievents] mousemove and preventDefault() (#278) (Thursday, 9 May)
• Re: [w3c/pointerlock] Editorial: Fix ReSpec error with ancestor browsing context (PR #89) (Monday, 6 May)
• Re: [w3c/pointerlock] Fix ReSpec error with ancestor browsing context. (PR #89) (Monday, 6 May)
• [w3c/pointerlock] Fix ReSpec error with ancestor browsing context. (PR #89) (Monday, 6 May)

Nathan Knowler

• [WICG/webcomponents] Allows slots to ignore surrounding whitespace (Issue #1056) (Friday, 3 May)

Nick Coury

• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Thursday, 2 May)
• Re: [whatwg/dom] MutationObserver node complete identifier (Issue #1116) (Wednesday, 1 May)
• Re: [whatwg/dom] MutationObserver node complete identifier (Issue #1116) (Wednesday, 1 May)
• Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Wednesday, 1 May)

Noam Rosenthal

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Wednesday, 8 May)

NullVoxPopuli

• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Saturday, 11 May)

Oliver Williams

• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Sunday, 12 May)
• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Wednesday, 8 May)

ollop

• [w3c/pointerlock] Provide more information about movementX/Y for unadjusted movements (Issue #98) (Wednesday, 29 May)

Pascal Schilp

• Re: [WICG/webcomponents] [open-stylable] Collection of user stories (Issue #1052) (Wednesday, 1 May)

Peter Beverloo

• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Thursday, 30 May)

Peter Linss

• Re: [w3ctag/design-reviews] Specification review for CSS Anchor Positioning (Issue #848) (Thursday, 23 May)
• Re: [w3ctag/design-reviews] Importmap integrity (Issue #944) (Monday, 6 May)
• Re: [w3ctag/design-reviews] Importmap integrity (Issue #944) (Monday, 6 May)

Philip Jägenstedt

• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Friday, 17 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Friday, 17 May)
• Re: [whatwg/fullscreen] Flatten requestFullscreen() error conditions (PR #224) (Friday, 17 May)
• Re: [whatwg/fullscreen] Flatten requestFullscreen() error conditions (PR #224) (Friday, 17 May)
• Re: [whatwg/fullscreen] Broken references in Fullscreen API Standard (Issue #215) (Friday, 17 May)
• Re: [whatwg/fullscreen] Pre-apply orientation lock via FullscreenOptions (PR #207) (Friday, 17 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Friday, 17 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Friday, 17 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Friday, 17 May)
• Re: [whatwg/fullscreen] How should UAs hide root element scrollbars? (Issue #236) (Friday, 17 May)
• Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235) (Thursday, 16 May)

Pieterjan

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

Piotr

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

polywock

• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)
• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)
• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)
• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)
• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)
• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)
• Re: [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Wednesday, 15 May)

Rafael Cintron

• Re: [w3ctag/design-reviews] Updated review of WebNN API (Issue #933) (Sunday, 26 May)

Rick Byers

• Re: [w3c/uievents] Mouse coordinates represented in CSS pixels do not account for retina displays with window.devicePixelRatio > 1 (#40) (Sunday, 12 May)

Rob Eisenberg

• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Friday, 10 May)
• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Wednesday, 8 May)
• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Wednesday, 8 May)
• Re: [WICG/webcomponents] April Face-to-face Scheduling/Agenda (Issue #1050) (Friday, 3 May)
• [WICG/webcomponents] Idea: HTML Module Imports and Exports (Issue #1059) (Friday, 3 May)
• [WICG/webcomponents] Idea: Alternative Ways to Control Registry Scoping (Issue #1058) (Friday, 3 May)
• [WICG/webcomponents] Use Cases: Iterating and Combining Custom Element Registries (Issue #1057) (Friday, 3 May)

Robbie Clutton

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

Ryosuke Niwa

• Re: [w3c/selection-api] Fixes https://github.com/w3c/selection-api/issues/170. (PR #172) (Wednesday, 22 May)
• Re: [w3c/selection-api] Fixes https://github.com/w3c/selection-api/issues/170. (4397d66) (Wednesday, 22 May)

Sanket Joshi

• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Thursday, 23 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Thursday, 23 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Wednesday, 22 May)
• Re: [w3c/editing] normative spec changes do not always end up as issues filed with browsers (Issue #463) (Friday, 10 May)

Sasha Firsov

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Wednesday, 15 May)
• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Friday, 10 May)

schwering

• Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Thursday, 23 May)

Sean Feng

• [whatwg/fetch] Define opaque-response blocking (updated) (PR #1755) (Monday, 27 May)
• Re: [w3c/selection-api] Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary (Issue #176) (Tuesday, 21 May)

Serhii Pustovit

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

Shunya Shishido

• Re: [w3c/ServiceWorker] Ensure "race-network-and-fetch-handler" is used with a fetch handler (PR #1719) (Friday, 31 May)

Simon Pieters

• Re: [whatwg/fetch] Define opaque-response blocking (updated) (PR #1755) (Monday, 27 May)
• [w3c/ServiceWorker] Request's initiator can't be "fetch" (Issue #1718) (Thursday, 16 May)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Wednesday, 15 May)
• Re: [w3ctag/design-reviews] document.caretPositionFromPoint API in shadow DOM scenario (Issue #949) (Tuesday, 7 May)

simoneonofri

• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Tuesday, 21 May)

Siye Liu

• Re: [w3c/selection-api] Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary (Issue #176) (Friday, 17 May)
• [w3c/selection-api] Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary (Issue #176) (Friday, 17 May)
• Re: [w3ctag/design-reviews] document.caretPositionFromPoint API in shadow DOM scenario (Issue #949) (Tuesday, 7 May)

smaug----

• Re: [w3c/selection-api] Fixes https://github.com/w3c/selection-api/issues/170. (PR #172) (Wednesday, 22 May)
• Re: [w3c/selection-api] Fixes https://github.com/w3c/selection-api/issues/170. (4397d66) (Wednesday, 22 May)
• Re: [w3c/selection-api] Fixes https://github.com/w3c/selection-api/issues/170. (4397d66) (Wednesday, 22 May)
• Re: [w3c/selection-api] Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary (Issue #176) (Monday, 20 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Wednesday, 8 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Wednesday, 8 May)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Thursday, 2 May)

snianu

• Re: [w3c/clipboard-apis] Make it possible to read image/svg+xml from the clipboard (#92) (Thursday, 30 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Wednesday, 22 May)
• Re: [w3c/clipboard-apis] Split implementor interest and implementation bugs from PR template (PR #215) (Wednesday, 22 May)

Sobhanysiamak

• Re: [whatwg/url] Note that there are no plans to support <zone_id>. Fixes https://www.w3.org/Bugs/Public/show_bug.cgi?id=27234 (ca97ec8) (Wednesday, 15 May)

steimelchrome

• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Monday, 6 May)

Steve Orvell

• Re: [WICG/webcomponents] Idea: Alternative Ways to Control Registry Scoping (Issue #1058) (Friday, 10 May)
• Re: [WICG/webcomponents] April Face-to-face Scheduling/Agenda (Issue #1050) (Friday, 3 May)
• Re: [WICG/webcomponents] [scoped-registries] Finding a definition for disconnected elements (Issue #1040) (Friday, 3 May)
• Re: [WICG/webcomponents] Idea: Alternative Ways to Control Registry Scoping (Issue #1058) (Friday, 3 May)
• Re: [WICG/webcomponents] April Face-to-face Scheduling/Agenda (Issue #1050) (Thursday, 2 May)
• Re: [WICG/webcomponents] Idea: A tree-aware task scheduler (Issue #1055) (Thursday, 2 May)

Sun Shin

• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Friday, 17 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Saturday, 11 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Saturday, 11 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Friday, 10 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Friday, 10 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Friday, 10 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Friday, 10 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Friday, 10 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Friday, 10 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Friday, 10 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Friday, 10 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Friday, 10 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Thursday, 9 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Thursday, 9 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Thursday, 9 May)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Thursday, 9 May)

Tab Atkins Jr.

• Re: [w3ctag/design-reviews] Specification review for CSS Anchor Positioning (Issue #848) (Friday, 24 May)
• Re: [w3ctag/design-reviews] Specification review for CSS Anchor Positioning (Issue #848) (Thursday, 23 May)

Takumi Fujimoto

• [w3c/pointerlock] Proposal to integrate pointer lock with the permissions API (Issue #94) (Wednesday, 8 May)

Thomas Steiner

• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Friday, 3 May)

Thomas Wisniewski

• Re: [w3c/FileAPI] Modernize Blob constructor a tiny bit (#125) (Sunday, 26 May)

Tim Flynn

• Re: [whatwg/fetch] Question about stream handling around fetch requests with integrity metadata (Issue #1754) (Friday, 24 May)
• [whatwg/fetch] Question about stream handling around fetch requests with integrity metadata (Issue #1754) (Wednesday, 22 May)

Tom Grushka

• [whatwg/dom] Closed Shadow DOM blocks accessibility testing (Issue #1290) (Tuesday, 28 May)

Tom Schuster

• Re: [w3c/push-api] Add bytes() method for reading bytes into a Uint8Array (PR #370) (Friday, 24 May)

Vidar Eldøy

• Re: [WICG/webcomponents] Why do we really need hyphens? (#658) (Sunday, 19 May)

Vincent Scheib

• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Friday, 17 May)
• Re: [w3c/pointerlock] When a subsequent requestPointerLock is rejected, should an already locked target exit lock state? (Issue #91) (Friday, 17 May)

W3C Bot

• Re: [w3c/pointerlock] Tidied up document using tidy-html5 (PR #95) (Wednesday, 8 May)

Wei Wang

• Re: [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Tuesday, 21 May)

weizman

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Wednesday, 8 May)

Westbrook Johnson

• Re: [WICG/webcomponents] April Face-to-face Scheduling/Agenda (Issue #1050) (Friday, 3 May)
• Re: [WICG/webcomponents] April Face-to-face Scheduling/Agenda (Issue #1050) (Friday, 3 May)
• Re: [WICG/webcomponents] April Face-to-face Scheduling/Agenda (Issue #1050) (Wednesday, 1 May)

Yoav Weiss

• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 27 May)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Friday, 31 May)
• Re: [w3c/ServiceWorker] Ensure "race-network-and-fetch-handler" is used with a fetch handler (PR #1719) (Friday, 31 May)
• [w3c/ServiceWorker] Ensure "race-network-and-fetch-handler" is used with a fetch handler (PR #1719) (Friday, 31 May)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Monday, 13 May)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Thursday, 9 May)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Thursday, 9 May)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Thursday, 9 May)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Thursday, 9 May)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Thursday, 9 May)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Wednesday, 8 May)
• Re: [w3c/ServiceWorker] Editorial: fixed the bikeshed errors (PR #1715) (Wednesday, 8 May)
• Re: [w3c/ServiceWorker] Editorial: Add notice on the _or condition depth. (PR #1714) (Wednesday, 1 May)

youennf

• Re: [whatwg/streams] Add support for ReadableStream "owning" type (PR #1271) (Friday, 24 May)

Yuxuan Zhang

• Re: [w3c/gamepad] Re-enable Gamepad Access from HTTP (aka insecure) Context (Issue #203) (Sunday, 12 May)
• Re: [w3c/gamepad] Re-enable Gamepad Access from HTTP (aka insecure) Context (Issue #203) (Sunday, 12 May)
• Re: [w3c/gamepad] Re-enable Gamepad Access from HTTP (aka insecure) Context (Issue #203) (Friday, 10 May)
• Re: [w3c/gamepad] Re-enable Gamepad Access from HTTP (aka insecure) Context (Issue #203) (Thursday, 9 May)
• Re: [w3c/gamepad] Require secure context for gamepad state and events (#120) (Wednesday, 8 May)
• [w3c/gamepad] Re-enable Gamepad Access from HTTP (aka insecure) Context (Issue #203) (Wednesday, 8 May)
• Re: [w3c/gamepad] Require secure context for gamepad state and events (#120) (Wednesday, 8 May)

Last message date: Friday, 31 May 2024 16:40:15 UTC