public-webapps-github@w3.org from June 2022 by author

Aaron Gustafson

• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Monday, 27 June)
• Re: [w3c/push-api] Mention or enforce userVisibleOnly check in PushManager.subscribe? (#339) (Wednesday, 15 June)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Monday, 13 June)

Abin K Paul

• Re: [whatwg/fetch] Add render-blocking boolean to fetch timing info (PR #1449) (Monday, 27 June)
• Re: [whatwg/fetch] Pass in render blocking status via finalize and report timing (PR #1449) (Saturday, 18 June)
• [whatwg/fetch] Pass in render blocking status via finalize and report timing (PR #1449) (Thursday, 2 June)

Adam Argyle

• Re: [w3ctag/design-reviews] `prefers-reduced-data` CSS Media Query (Issue #705) (Monday, 13 June)

Adam Rice

• Re: [whatwg/streams] Fix invalid high water mark for tee branches (PR #1234) (Wednesday, 1 June)

Addison Phillips

• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Friday, 17 June)

Aditya Todkar

• Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Sunday, 26 June)

Amaziest

• Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090) (Tuesday, 28 June)

Amy Guy

• Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718) (Monday, 27 June)
• Re: [w3ctag/design-reviews] Web of Things (WoT) Discovery (Issue #733) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture 1.1 (Issue #736) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735) (Tuesday, 14 June)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Wednesday, 8 June)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Wednesday, 8 June)

Anne van Kesteren

• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Thursday, 30 June)
• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Tuesday, 28 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Tuesday, 28 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Tuesday, 28 June)
• Re: [whatwg/fetch] Editorial: Fix ending tag for dfn (PR #1455) (Tuesday, 28 June)
• Re: [whatwg/fetch] Editorial: Fix ending tag for dfn (PR #1455) (Tuesday, 28 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Tuesday, 28 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 28 June)
• Re: [whatwg/encoding] 7-bit ASCII encoding (Issue #287) (Sunday, 26 June)
• Re: [whatwg/encoding] 7-bit ASCII encoding (Issue #287) (Sunday, 26 June)
• Re: [whatwg/fetch] Editorial: Remove the nonexistent controller variable in the fetch algorithm. (PR #1462) (Saturday, 25 June)
• Re: [whatwg/fetch] Editorial: Remove the nonexistent controller variable in the fetch algorithm. (PR #1462) (Friday, 24 June)
• Re: [whatwg/fetch] Editorial: Remove the nonexistent controller variable in the fetch algorithm. (PR #1462) (Friday, 24 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/encoding] Review Draft Publication: June 2022 (PR #288) (Monday, 20 June)
• Re: [whatwg/fetch] Review Draft Publication: June 2022 (PR #1458) (Monday, 20 June)
• Re: [whatwg/dom] Review Draft Publication: June 2022 (PR #1089) (Monday, 20 June)
• [whatwg/encoding] Review Draft Publication: June 2022 (PR #288) (Monday, 20 June)
• [whatwg/dom] Review Draft Publication: June 2022 (PR #1089) (Monday, 20 June)
• [whatwg/fetch] Review Draft Publication: June 2022 (PR #1458) (Monday, 20 June)
• Re: [whatwg/fetch] When response comes from a worker, some of the timing-info should pass through (#1208) (Friday, 17 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Friday, 17 June)
• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Friday, 17 June)
• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Friday, 17 June)
• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Friday, 17 June)
• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Friday, 17 June)
• Re: [whatwg/fetch] Allow more flexibility in how 401s/407s are handled? (#1132) (Thursday, 16 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Thursday, 16 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Thursday, 16 June)
• Re: [whatwg/fetch] Request body streams should use chunked encoding (#966) (Thursday, 16 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Thursday, 16 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Thursday, 16 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Thursday, 16 June)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Thursday, 16 June)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Thursday, 16 June)
• Re: [whatwg/webidl] Meta: downstream issues (Issue #1147) (Wednesday, 15 June)
• Re: [whatwg/webidl] Meta: list webidl2.js and widlparser in PR template (PR #1156) (Wednesday, 15 June)
• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Wednesday, 15 June)
• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Wednesday, 15 June)
• Re: [whatwg/fetch] processResponseConsumeBody and opaque responses (Issue #1446) (Wednesday, 15 June)
• Re: [whatwg/webidl] Meta: list webidl2.js and widlparser in PR template (PR #1156) (Wednesday, 15 June)
• Re: [whatwg/webidl] Meta: list webidl2.js and widlparser in PR template (PR #1156) (Wednesday, 15 June)
• Re: [whatwg/xhr] Refactor for auto-reporting timing from fetch (PR #347) (Wednesday, 15 June)
• Re: [whatwg/webidl] Meta: list webidl2.js and widlparser in PR template (PR #1156) (Wednesday, 15 June)
• Re: [whatwg/webidl] Meta: downstream issues (Issue #1147) (Wednesday, 15 June)
• [whatwg/webidl] Meta: list webidl2.js and widlparser in PR template (PR #1156) (Wednesday, 15 June)
• Re: [whatwg/xhr] Refactor for auto-reporting timing from fetch (PR #347) (Wednesday, 15 June)
• Re: [whatwg/fetch] Pass in render blocking status via finalize and report timing (PR #1449) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/url] Proposal: URL.parseIPv4() URL.parseIPv6() (Issue #696) (Tuesday, 14 June)
• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/xhr] Refactor for auto-reporting timing from fetch (PR #347) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/url] Proposal: URL.parseIPv4() URL.parseIPv6() (Issue #696) (Tuesday, 14 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 13 June)
• Re: [whatwg/fetch] Fetch body streams are not full duplex (#1254) (Monday, 13 June)
• Re: [whatwg/fetch] Fetch body streams are not full duplex (#1254) (Monday, 13 June)
• Re: [whatwg/dom] Add a fully active check for EventTarget in event listener inner invoke (PR #1085) (Monday, 13 June)
• Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920) (Monday, 13 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Monday, 13 June)
• Re: [whatwg/fetch] Streams based uploading with Content-Length (not chunked encoding) (#95) (Monday, 13 June)
• Re: [whatwg/fetch] Streams based uploading with Content-Length (not chunked encoding) (#95) (Monday, 13 June)
• Re: [whatwg/dom] Missing dot for `concept-node-remove`s first step. (PR #1086) (Thursday, 9 June)
• Re: [whatwg/dom] Missing dot for `concept-node-remove`s first step. (PR #1086) (Thursday, 9 June)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Thursday, 9 June)
• Re: [w3c/clipboard-apis] The MIME type checking should ignore the "web " prefix (Issue #178) (Wednesday, 8 June)
• Re: [whatwg/fetch] Editorial: Update severals biblio refs to HTTP-SEMANTICS (PR #1451) (Wednesday, 8 June)
• Re: [whatwg/fetch] Editorial: Update severals biblio refs to HTTP-SEMANTICS (PR #1451) (Wednesday, 8 June)
• Re: [whatwg/fetch] Editorial: Update severals biblio refs to HTTP-SEMANTICS (PR #1451) (Wednesday, 8 June)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Wednesday, 8 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Wednesday, 8 June)
• Re: [whatwg/webidl] Add [Exposed=*] to expose on all globals (#526) (Wednesday, 8 June)
• Re: [whatwg/encoding] 7-bit ASCII encoding (Issue #287) (Wednesday, 8 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 7 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 7 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 7 June)
• Re: [whatwg/dom] Should event dispatch check that the event target is in a fully active realm? (Issue #1084) (Tuesday, 7 June)
• Re: [whatwg/webidl] Promises: resolve algorithm should accept a promise (#957) (Tuesday, 7 June)
• Re: [whatwg/webidl] Allow dictionary values to default to undefined (#983) (Tuesday, 7 June)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Friday, 3 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Friday, 3 June)
• Re: [whatwg/fetch] Define opaque-response blocking (PR #1442) (Wednesday, 1 June)
• Re: [whatwg/fetch] Define opaque-response blocking (PR #1442) (Wednesday, 1 June)
• Re: [whatwg/fetch] Add algorithm to extract an encoding from a MIME type (PR #1447) (Wednesday, 1 June)
• Re: [whatwg/fetch] Add algorithm to extract an encoding from a MIME type (PR #1447) (Wednesday, 1 June)
• Re: [w3c/FileAPI] Blob URL store partitioning (#153) (Wednesday, 1 June)
• [whatwg/fetch] Add algorithm to extract an encoding from a MIME type (PR #1447) (Wednesday, 1 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Wednesday, 1 June)

Anthony Ramine

• Re: [whatwg/url] Parser generates invalid URLs (#379) (Saturday, 18 June)

Ari Chivukula

• Re: [whatwg/fetch] Prevent cross-origin sensitive header probing (PR #1434) (Wednesday, 29 June)
• Re: [whatwg/fetch] Prevent cross-origin sensitive header probing (PR #1434) (Tuesday, 28 June)
• Re: [w3ctag/design-reviews] Markup based Client Hints delegation for third-party content (Issue #702) (Tuesday, 14 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Tuesday, 7 June)
• Re: [w3ctag/design-reviews] Markup based Client Hints delegation for third-party content (Issue #702) (Tuesday, 7 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Sunday, 5 June)
• Re: [whatwg/fetch] Prevent cross-origin sensitive header probing (PR #1434) (Friday, 3 June)
• Re: [whatwg/fetch] Prevent cross-origin sensitive header probing (PR #1434) (Friday, 3 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Thursday, 2 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Thursday, 2 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Thursday, 2 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Thursday, 2 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Thursday, 2 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Thursday, 2 June)
• [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Thursday, 2 June)
• Re: [whatwg/fetch] Prevent cross-origin sensitive header probing (PR #1434) (Thursday, 2 June)
• Re: [whatwg/fetch] Prevent cross-origin sensitive header probing (PR #1434) (Thursday, 2 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (Issue #382) (Wednesday, 1 June)
• Re: [w3ctag/design-reviews] Markup based Client Hints delegation for third-party content (Issue #702) (Wednesday, 1 June)
• Re: [w3ctag/design-reviews] Markup based Client Hints delegation for third-party content (Issue #702) (Wednesday, 1 June)

Arthur Sonzogni

• Re: [w3ctag/design-reviews] COEP reflection (Issue #742) (Monday, 20 June)

Austin Sullivan

• [w3ctag/design-reviews] FYI review of Writable directory prompts for the File System Access API (Issue #749) (Friday, 24 June)

Ayu Ishii

• Re: [w3c/IndexedDB] Bikeshed: Enable 'Assume Explicit For' and make links explicit (PR #385) (Wednesday, 8 June)

Barry Pollard

• Re: [w3ctag/design-reviews] `prefers-reduced-data` CSS Media Query (Issue #705) (Monday, 13 June)

Ben Bucksch

• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Wednesday, 22 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 20 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 20 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 20 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 20 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 20 June)
• Re: [whatwg/fetch] Fetch body streams are not full duplex (#1254) (Monday, 13 June)
• Re: [whatwg/fetch] Fetch body streams are not full duplex (#1254) (Monday, 13 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 13 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 13 June)
• Re: [whatwg/fetch] Fetch body streams are not full duplex (#1254) (Monday, 13 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Thursday, 9 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Thursday, 9 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Wednesday, 8 June)

Ben Kelly

• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Wednesday, 8 June)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Wednesday, 8 June)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Wednesday, 8 June)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Friday, 3 June)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Friday, 3 June)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Friday, 3 June)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Friday, 3 June)
• [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Thursday, 2 June)

Benjamin Gruenbaum

• Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235) (Thursday, 23 June)

Bo Cupp

• Re: [w3c/editing] Update meeting invite link (PR #391) (Thursday, 30 June)
• Re: [w3c/clipboard-apis] Add Web Custom format (PR #175) (Friday, 3 June)

Brett Zamir

• Re: [w3c/IndexedDB] Editorial: Add event definition for 'close' (PR #384) (Friday, 3 June)
• Re: [w3c/IndexedDB] Editorial: Add event definition for 'close' (PR #384) (Friday, 3 June)

Camillia Smith Barnes

• [w3ctag/design-reviews] Shared Storage API (Issue #747) (Monday, 6 June)

campersau

• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Wednesday, 8 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Wednesday, 8 June)

Chris Harrelson

• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Wednesday, 29 June)

Chris Holt

• Re: [w3ctag/design-reviews] Early design review: Focusgroup (Issue #732) (Monday, 20 June)

Chris Needham

• [w3c/uievents] Fixed typos (PR #327) (Wednesday, 1 June)

Chris Odom

• Re: [WICG/webcomponents] The way to access current script or current root, from Shadow DOM (#717) (Tuesday, 21 June)

Claudia Pelchat

• [whatwg/fetch] Api-Bitbucket (Issue #1459) (Tuesday, 21 June)

craigfarra023

• [whatwg/webidl] "identifier_of_inherited_interface " (Issue #1161) (Saturday, 25 June)

cynthia

• Re: [w3ctag/design-reviews] Navigation API (formerly app history API) (Issue #717) (Tuesday, 28 June)

Dan Ehrlich

• Re: [whatwg/fetch] Cannot get next URL for redirect="manual" (#763) (Thursday, 2 June)

Dan Robertson

• Re: [whatwg/fetch] blob: fetch of slice() without valid content type yields unexpected results (Issue #1464) (Tuesday, 28 June)
• Re: [whatwg/fetch] blob: fetch of slice() without valid content type yields unexpected results (Issue #1464) (Monday, 27 June)
• [whatwg/fetch] blob: fetch of slice() without valid content type yields unexpected results (Issue #1464) (Monday, 27 June)
• Re: [w3c/FileAPI] blob: slice() without valid content type yields unexpected results (Issue #177) (Monday, 27 June)
• Re: [w3c/FileAPI] blob: slice() without valid content type yields unexpected results (Issue #177) (Monday, 27 June)
• [w3c/FileAPI] blob: slice() without valid content type yields unexpected results (Issue #177) (Monday, 27 June)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Friday, 24 June)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Friday, 24 June)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Monday, 20 June)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Thursday, 16 June)
• [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Thursday, 16 June)
• Re: [whatwg/fetch] simple range header value parser does not allow for suffix-byte-range-spec (Issue #1450) (Thursday, 9 June)
• [whatwg/fetch] simple range header value parser does not allow for suffix-byte-range-spec (Issue #1450) (Sunday, 5 June)
• Re: [whatwg/fetch] blob: URLs and range requests (#1070) (Saturday, 4 June)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Review Request for adding video- prefixed media features (Issue #697) (Tuesday, 28 June)
• Re: [w3ctag/design-reviews] Review Request for adding video- prefixed media features (Issue #697) (Tuesday, 28 June)
• Re: [w3ctag/design-reviews] Conditional Focus (When Display-Capture Starts) (#679) (Tuesday, 28 June)
• Re: [w3ctag/design-reviews] Conditional Focus (When Display-Capture Starts) (#679) (Tuesday, 28 June)
• Re: [w3ctag/design-reviews] Navigation API (formerly app history API) (Issue #717) (Wednesday, 22 June)
• Re: [w3ctag/design-reviews] COEP reflection (Issue #742) (Wednesday, 22 June)
• Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Wednesday, 22 June)
• Re: [w3ctag/design-reviews] Cookies Having Independent Partitioned State (CHIPS) (#654) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Cookies Having Independent Partitioned State (CHIPS) (#654) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Early design review: CSS Toggles (Issue #730) (Monday, 20 June)
• Re: [w3ctag/design-reviews] Early design review of the **updated** Multi-Screen Window Placement API (#602) (Monday, 13 June)
• Re: [w3ctag/design-reviews] `prefers-reduced-data` CSS Media Query (Issue #705) (Wednesday, 8 June)
• Re: [w3ctag/design-reviews] Review Request for Attribution Reporting API (Issue #724) (Tuesday, 7 June)
• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Monday, 6 June)
• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Monday, 6 June)

Daniel Ehrenberg

• Re: [whatwg/webidl] Add [Exposed=*] to expose on all globals (#526) (Tuesday, 7 June)

Daniel Murphy

• Re: [w3c/manifest] Feature request: access to menu bar and context menus (Issue #1025) (Tuesday, 7 June)

Dapeng(Max) Liu

• Re: [w3ctag/design-reviews] Site-initiated mirroring (Issue #745) (Thursday, 30 June)
• Re: [w3ctag/design-reviews] Collection of Screensharing-related UX Hints (Issue #744) (Tuesday, 28 June)

Dave Tapuska

• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Friday, 17 June)

Domenic Denicola

• Re: [w3ctag/design-reviews] Navigation API (formerly app history API) (Issue #717) (Tuesday, 28 June)
• Re: [whatwg/dom] Add onabort definition and add onslotchange (#785) (Thursday, 23 June)
• Re: [whatwg/dom] Add onabort definition and add onslotchange (#785) (Thursday, 23 June)
• Re: [w3ctag/design-reviews] Navigation API (formerly app history API) (Issue #717) (Wednesday, 22 June)
• Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235) (Tuesday, 21 June)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 21 June)
• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Friday, 17 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Friday, 17 June)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 16 June)
• Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735) (Thursday, 16 June)
• Re: [whatwg/webidl] Meta: list webidl2.js and widlparser in PR template (PR #1156) (Wednesday, 15 June)
• Re: [w3ctag/design-reviews] Navigation API (formerly app history API) (Issue #717) (Monday, 13 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Wednesday, 8 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Wednesday, 8 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Wednesday, 8 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 7 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 7 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 7 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 7 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 7 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 7 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 7 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 7 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Tuesday, 7 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Monday, 6 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Monday, 6 June)
• [w3ctag/design-reviews] import.meta.resolve() (Issue #746) (Monday, 6 June)
• Re: [whatwg/dom] Should event dispatch check that the event target is in a fully active realm? (Issue #1084) (Friday, 3 June)
• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Friday, 3 June)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Friday, 3 June)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Friday, 3 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Thursday, 2 June)
• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Wednesday, 1 June)
• Re: [w3ctag/design-reviews] Markup based Client Hints delegation for third-party content (Issue #702) (Wednesday, 1 June)
• Re: [whatwg/fetch] Add algorithm to extract an encoding from a MIME type (PR #1447) (Wednesday, 1 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Wednesday, 1 June)

Dominique Hazael-Massieux

• Re: [w3c/IndexedDB] Associate event definitions with the interfaces they fire at (PR #387) (Wednesday, 29 June)
• [w3c/IndexedDB] Associate event definitions with the interfaces they fire at (PR #387) (Wednesday, 29 June)
• [w3c/selection-api] Align description of events with DOM suggested phrasing (PR #148) (Friday, 3 June)
• [w3c/touch-events] Improve markup for event summary table (PR #122) (Friday, 3 June)

dram2040

• Re: [w3c/IndexedDB] Editorial: Add event definition for 'close' (PR #384) (Friday, 3 June)

Edgar Chen

• Re: [w3c/clipboard-apis] Should ClipboardItem be marked as [SecureContext]? (#103) (Friday, 10 June)
• Re: [w3c/clipboard-apis] Add Web Custom format (PR #175) (Tuesday, 7 June)

Ege Korkan

• Re: [w3ctag/design-reviews] Web of Things (WoT) Thing Description 1.1: TAG and Security Review (Issue #715) (Tuesday, 14 June)

Elad Alon

• Re: [w3ctag/design-reviews] Conditional Focus (When Display-Capture Starts) (#679) (Thursday, 30 June)
• Re: [w3ctag/design-reviews] Collection of Screensharing-related UX Hints (Issue #744) (Thursday, 16 June)
• [w3ctag/design-reviews] Collection of Screensharing-related UX Hints (Issue #744) (Thursday, 2 June)

fergald

• Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Tuesday, 28 June)

francescoterrell

• [w3c/ServiceWorker] Loading service worker behind authentication (Issue #1648) (Sunday, 19 June)

Frank Lemanschik

• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Wednesday, 1 June)

Frederik Braun

• [whatwg/dom] Missing dot for `concept-node-remove`s first step. (PR #1086) (Thursday, 9 June)

Gary Kacmarcik

• Re: [w3c/uievents] Specify non-cancelable wheel events when there are no non-passive listeners (PR #330) (Wednesday, 29 June)
• Re: [w3c/uievents] Document the cancelability of wheel events (#282) (Wednesday, 29 June)
• Re: [w3c/uievents] Specify non-cancelable wheel events when there are no non-passive listeners (PR #330) (Wednesday, 29 June)
• Re: [w3c/uievents] Specify non-cancelable wheel events when there are no non-passive listeners (PR #330) (Wednesday, 29 June)
• Re: [w3c/uievents] Specify non-cancelable wheel/mousewheel events when there are no non-passive listeners (PR #330) (Wednesday, 29 June)
• [w3c/uievents] Add mousewheel to the "Legacy Event Types" section (Issue #331) (Wednesday, 29 June)
• Re: [w3c/uievents] Fixed typos (PR #327) (Wednesday, 1 June)
• Re: [w3c/uievents] Fixed typos (PR #327) (Wednesday, 1 June)

github-actions[bot]

• [w3c/push-api] chore(tidy): tidy up document (PR #351) (Thursday, 2 June)

Hadley Beeman

• Re: [w3ctag/design-reviews] Cookies Having Independent Partitioned State (CHIPS) (#654) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Web of Things (WoT) Thing Description 1.1: TAG and Security Review (Issue #715) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Web of Things (WoT) Thing Description 1.1: TAG and Security Review (Issue #715) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Web of Things (WoT) Thing Description 1.1: TAG and Security Review (Issue #715) (Tuesday, 14 June)
• Re: [w3ctag/design-reviews] I18N String-Meta and WebIDL (Issue #716) (Tuesday, 7 June)

Henri Sivonen

• Re: [whatwg/dom] document.createEvent() should maybe not be conditional upon exposure (#952) (Monday, 20 June)

Ian Vollick

• Re: [w3ctag/design-reviews] Shared Element Transitions - Early Review (#631) (Thursday, 16 June)

Irene Knapp

• [w3c/gamepad] Make note of the fact that the standard gamepad layout is privacy-relevant (Issue #161) (Thursday, 2 June)

Jake Archibald

• Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940) (Sunday, 26 June)
• Re: [whatwg/fetch] simple range header value parser does not allow for suffix-byte-range-spec (Issue #1450) (Thursday, 9 June)

James M Snell

• Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235) (Wednesday, 22 June)
• Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235) (Tuesday, 21 June)
• Re: [whatwg/url] Proposal: URL.parseIPv4() URL.parseIPv6() (Issue #696) (Tuesday, 14 June)
• Re: [whatwg/streams] Performance optimization: `ReadableStreamDefaultReader.prototype.readMany` (Issue #1236) (Tuesday, 14 June)
• Re: [whatwg/url] Proposal: URL.parseIPv4() URL.parseIPv6() (Issue #696) (Tuesday, 14 June)
• [whatwg/url] Proposal: URL.parseIPv4() URL.parseIPv6() (Issue #696) (Monday, 13 June)
• Re: [whatwg/streams] Handling stream errors in a TransformStream transformer (Issue #1212) (Monday, 13 June)
• Re: [whatwg/streams] Returning buffers to the underlying source (Issue #1217) (Monday, 13 June)
• [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235) (Monday, 13 June)

Jan Schejbal

• Re: [whatwg/encoding] 7-bit ASCII encoding (Issue #287) (Sunday, 26 June)
• [whatwg/encoding] 7-bit ASCII encoding (Issue #287) (Wednesday, 8 June)

jarhar

• Re: [w3ctag/design-reviews] Element.isVisible review (Issue #734) (Thursday, 9 June)

Jarred Sumner

• Re: [whatwg/streams] Performance optimization: `ReadableStreamDefaultReader.prototype.readMany` (Issue #1236) (Wednesday, 15 June)
• [whatwg/streams] Performance optimization: `ReadableStreamDefaultReader.prototype.readMany` (Issue #1236) (Tuesday, 14 June)

Jeremy Roman

• Re: [whatwg/fetch] Editorial: Remove the nonexistent controller variable in the fetch algorithm. (PR #1462) (Friday, 24 June)
• Re: [whatwg/fetch] Editorial: Remove the nonexistent controller variable in the fetch algorithm. (PR #1462) (Friday, 24 June)
• Re: [whatwg/fetch] Editorial: Remove the nonexistent controller variable in the fetch algorithm. (PR #1462) (Friday, 24 June)
• [whatwg/fetch] Editorial: Remove the nonexistent controller variable in the fetch algorithm. (PR #1462) (Friday, 24 June)

Jimmy Wärting

• Re: [w3c/push-api] userVisibleOnly should be standardized to match browser behaviour (#313) (Sunday, 26 June)

Joey Arhar

• Re: [whatwg/dom] DOM Comments don't align with HTML comments (#1023) (Tuesday, 21 June)
• Re: [whatwg/dom] DOM Comments don't align with HTML comments (#1023) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Element.isVisible review (Issue #734) (Tuesday, 21 June)

Johannes Wilm

• Re: [w3c/editing] Update meeting invite link (PR #391) (Thursday, 30 June)
• Re: [w3c/editing] Update meeting invite link (PR #391) (Thursday, 30 June)
• Re: [w3c/editing] Update meeting invite link (PR #391) (Thursday, 30 June)
• Re: [w3c/editing] Add June 9, 2022 minutes (PR #401) (Thursday, 30 June)
• Re: [w3c/editing] Add June 9, 2022 minutes (PR #401) (Thursday, 30 June)

Joshua Bell

• Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Wednesday, 29 June)
• Re: [w3c/IndexedDB] Normalize negative zero (PR #386) (Wednesday, 29 June)
• Re: [w3c/IndexedDB] Associate event definitions with the interfaces they fire at (PR #387) (Wednesday, 29 June)
• Re: [w3c/IndexedDB] Associate event definitions with the interfaces they fire at (PR #387) (Wednesday, 29 June)
• Re: [whatwg/fetch] blob: fetch of slice() without valid content type yields unexpected results (Issue #1464) (Tuesday, 28 June)
• Re: [w3c/FileAPI] blob: slice() without valid content type yields unexpected results (Issue #177) (Monday, 27 June)
• Re: [w3c/IndexedDB] Clarify the handling of +0 and -0 in keys (Issue #375) (Saturday, 11 June)
• [w3c/IndexedDB] Normalize negative zero (PR #386) (Saturday, 11 June)
• Re: [w3c/IndexedDB] Clarify the handling of +0 and -0 in keys (Issue #375) (Saturday, 11 June)
• Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Initial sketch of manual commit flag for transactions (#331) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Sketch out IDBCursor.close() (#302) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Bikeshed: Enable 'Assume Explicit For' and make links explicit (PR #385) (Wednesday, 8 June)
• [w3c/IndexedDB] Bikeshed: Enable 'Assume Explicit For' and make links explicit (PR #385) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (Issue #382) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Editorial: Add event definition for 'close' (PR #384) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Editorial: Add event definition for 'close' (PR #384) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Monday, 6 June)
• Re: [w3c/IndexedDB] Editorial: Add event definition for 'close' (PR #384) (Monday, 6 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Saturday, 4 June)
• Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Saturday, 4 June)
• Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Saturday, 4 June)
• Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Saturday, 4 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Friday, 3 June)
• Re: [w3c/IndexedDB] Editorial: Add event definition for 'close' (PR #384) (Friday, 3 June)
• Re: [w3c/IndexedDB] Editorial: Add event definition for 'close' (PR #384) (Friday, 3 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Friday, 3 June)
• Re: [w3c/IndexedDB] Editorial: Add event definition for 'close' (PR #384) (Friday, 3 June)
• [w3c/IndexedDB] Editorial: Add event definition for 'close' (PR #384) (Friday, 3 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Thursday, 2 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Thursday, 2 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (PR #383) (Thursday, 2 June)
• Re: [w3c/IndexedDB] Support Storage Partitioning (Issue #382) (Wednesday, 1 June)

Kagami Sascha Rosylight

• Re: [whatwg/webidl] Meta: list webidl2.js and widlparser in PR template (PR #1156) (Wednesday, 15 June)
• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Thursday, 2 June)
• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Thursday, 2 June)

Keith Cirkel

• Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920) (Saturday, 11 June)
• Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920) (Thursday, 9 June)

Kershaw

• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Thursday, 16 June)

Khushal Sagar

• [w3ctag/design-reviews] CSS Overflow for replaced elements (Issue #750) (Friday, 24 June)
• Re: [w3ctag/design-reviews] Shared Element Transitions - Early Review (#631) (Thursday, 16 June)
• [w3ctag/design-reviews] Shared Element Transitions API (Issue #748) (Thursday, 16 June)

krgovind

• Re: [w3ctag/design-reviews] Cookies Having Independent Partitioned State (CHIPS) (#654) (Tuesday, 21 June)

Lea Verou

• Re: [w3ctag/design-reviews] renderPriority element attribute (#676) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Early design review: Focusgroup (Issue #732) (Monday, 20 June)
• Re: [w3ctag/design-reviews] Early design review: Focusgroup (Issue #732) (Monday, 20 June)
• Re: [w3ctag/design-reviews] `prefers-reduced-data` CSS Media Query (Issue #705) (Monday, 13 June)
• Re: [w3ctag/design-reviews] Modification of selection APIs to account for shadow dom (Issue #694) (Monday, 6 June)
• Re: [w3ctag/design-reviews] Modification of selection APIs to account for shadow dom (Issue #694) (Monday, 6 June)
• Re: [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708) (Monday, 6 June)
• Re: [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708) (Monday, 6 June)

Leo Balter

• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Wednesday, 29 June)

Lewis Pham

• Re: [w3c/ServiceWorker] Service worker catches requests from different ports (Issue #1646) (Wednesday, 1 June)
• Re: [w3c/ServiceWorker] Service worker catches requests from different ports (Issue #1646) (Wednesday, 1 June)
• [w3c/ServiceWorker] Service worker catches requests from different ports (Issue #1646) (Wednesday, 1 June)

Liam DeBeasi

• [w3c/manifest] Feature request: add option to disable built-in navigation gestures (Issue #1041) (Wednesday, 8 June)

Livia Medeiros

• [whatwg/fetch] Editorial: Add 103 to note about null body Response (PR #1465) (Thursday, 30 June)
• [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090) (Monday, 27 June)

LONCHHAIHONG

• [whatwg/xhr] 001645559 (Issue #350) (Wednesday, 15 June)

Luca Casonato

• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 20 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 20 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 20 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 20 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Friday, 17 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Friday, 17 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Friday, 17 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Friday, 17 June)
• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Thursday, 16 June)
• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Wednesday, 15 June)
• Re: [whatwg/fetch] blob url fetch with no mime type set is undefined (Issue #1436) (Wednesday, 15 June)
• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Wednesday, 15 June)
• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Wednesday, 15 June)
• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Wednesday, 15 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Tuesday, 14 June)
• [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Tuesday, 14 June)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Tuesday, 14 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 13 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 13 June)

Lukasz Olejnik

• Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735) (Wednesday, 29 June)
• Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735) (Wednesday, 29 June)

Luo Yifan（罗一凡）

• [w3ctag/design-reviews] Private Network Access (aka CORS-RFC1918) permission to relax mixed content (Issue #751) (Tuesday, 28 June)

Madhur Jain

• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Wednesday, 22 June)

Marcos Cáceres

• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Thursday, 30 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Thursday, 30 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Thursday, 30 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Tuesday, 28 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Tuesday, 28 June)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Tuesday, 28 June)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Friday, 24 June)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 23 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 23 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 23 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 23 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 23 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 23 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 23 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 23 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 23 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Tuesday, 21 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Tuesday, 21 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Tuesday, 21 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Tuesday, 21 June)
• Re: [w3c/gamepad] Fold extensions.html into main spec (Issue #165) (Tuesday, 14 June)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Friday, 10 June)
• Re: [w3c/push-api] Mention or enforce userVisibleOnly check in PushManager.subscribe? (#339) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• [w3c/gamepad] Fold extensions.html into main spec (Issue #165) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Wednesday, 8 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Wednesday, 8 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Wednesday, 8 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Wednesday, 8 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Wednesday, 8 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Wednesday, 8 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Wednesday, 8 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Wednesday, 8 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Wednesday, 8 June)
• Re: [w3c/IndexedDB] Editorial: Add event definition for 'close' (PR #384) (Wednesday, 8 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Tuesday, 7 June)
• [w3c/gamepad] chore: tidy extensions.html (PR #164) (Tuesday, 7 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Tuesday, 7 June)
• Re: [w3c/gamepad] Suggest Standard Gamepad as a fingerprinting mitigation (PR #162) (Tuesday, 7 June)
• Re: [w3c/gamepad] Add gamepad input events (#152) (Tuesday, 7 June)
• Re: [w3c/gamepad] Suggest Standard Gamepad as a fingerprinting mitigation (PR #162) (Tuesday, 7 June)
• Re: [w3c/gamepad] Suggest Standard Gamepad as a fingerprinting mitigation (PR #162) (Tuesday, 7 June)
• Re: [w3c/gamepad] Suggest Standard Gamepad as a fingerprinting mitigation (PR #162) (Tuesday, 7 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Friday, 3 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Friday, 3 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Friday, 3 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Friday, 3 June)
• Re: [w3c/push-api] chore(tidy): tidy up document (PR #351) (Thursday, 2 June)
• Re: [w3c/push-api] chore(tidy): tidy up document (PR #351) (Thursday, 2 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Thursday, 2 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Thursday, 2 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Thursday, 2 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Thursday, 2 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Thursday, 2 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Thursday, 2 June)
• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Thursday, 2 June)
• Re: [w3c/push-api] Remove redudant secure context check (PR #349) (Thursday, 2 June)
• [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Thursday, 2 June)
• [w3c/push-api] Remove redudant secure context check (PR #349) (Wednesday, 1 June)
• Re: [w3c/push-api] check and consume user activation (PR #348) (Wednesday, 1 June)
• [w3c/push-api] check and consume user activation (PR #348) (Wednesday, 1 June)
• Re: [w3c/push-api] PushManager subscribe method probably needs a transient activation check (Issue #346) (Wednesday, 1 June)

Markus Unterwaditzer

• [w3c/selection-api] interop: Trailing whitespace in h1/h2 is selectable in firefox, not selectable in chrome (Issue #149) (Monday, 13 June)

Martin Thomson

• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Monday, 6 June)
• Re: [w3c/push-api] Remove redudant secure context check (PR #349) (Wednesday, 1 June)
• Re: [w3c/push-api] check and consume user activation (PR #348) (Wednesday, 1 June)

Martin Traverse

• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 6 June)

maryfranharper

• [whatwg/dom] infected text (Issue #1091) (Monday, 27 June)

Mason Freed

• Re: [w3ctag/design-reviews] Modification of selection APIs to account for shadow dom (Issue #694) (Friday, 17 June)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Friday, 17 June)
• Re: [w3c/uievents] Introduce contextmenuclose or similar event. (#309) (Thursday, 9 June)
• [w3ctag/design-reviews] The Popup API (Issue #743) (Wednesday, 1 June)

Mathias Bynens

• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Wednesday, 8 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Wednesday, 8 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Wednesday, 8 June)

Matt Reynolds

• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• Re: [w3c/gamepad] Fold extensions.html into main spec (Issue #165) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Thursday, 9 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Wednesday, 8 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Tuesday, 7 June)
• Re: [w3c/gamepad] Make note of the fact that the standard gamepad layout is privacy-relevant (Issue #161) (Tuesday, 7 June)
• Re: [w3c/gamepad] Suggest Standard Gamepad as a fingerprinting mitigation (PR #162) (Tuesday, 7 June)
• Re: [w3c/gamepad] Suggest Standard Gamepad as a fingerprinting mitigation (PR #162) (Tuesday, 7 June)
• Re: [w3c/gamepad] chore: tidy extensions.html (PR #164) (Tuesday, 7 June)
• Re: [w3c/gamepad] chore: tidy extensions.html (PR #164) (Tuesday, 7 June)
• Re: [w3c/gamepad] Suggest Standard Gamepad as a fingerprinting mitigation (PR #162) (Tuesday, 7 June)
• Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68) (Monday, 6 June)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Monday, 6 June)
• [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Monday, 6 June)
• [w3c/gamepad] Suggest Standard Gamepad as a fingerprinting mitigation (PR #162) (Thursday, 2 June)

Matteo Collina

• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Thursday, 30 June)

Matthew Gaudet

• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Monday, 6 June)
• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Friday, 3 June)

Mattias Buelens

• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Monday, 27 June)
• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Monday, 6 June)
• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Monday, 6 June)
• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Thursday, 2 June)

Maufas

• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Monday, 6 June)

Michael Wasserman

• Re: [w3ctag/design-reviews] Early design review of the **updated** Multi-Screen Window Placement API (#602) (Monday, 13 June)

Mike Taylor

• Re: [w3c/permissions] "Changes to this document may be tracked at" points to incorrect repo ? (#198) (Friday, 10 June)
• Re: [w3c/permissions] "Changes to this document may be tracked at" points to incorrect repo ? (#198) (Friday, 10 June)

Mustaq Ahmed

• Re: [w3c/uievents] Remove text selection from the dblclick default action - #328 (PR #329) (Friday, 24 June)
• Re: [w3c/uievents] Remove text selection from the dblclick default action - #328 (PR #329) (Friday, 24 June)

Nick Williams

• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 21 June)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Tuesday, 21 June)

Noam Rosenthal

• Re: [whatwg/xhr] Editorial: Refactor for auto-reporting timing from fetch (PR #347) (Tuesday, 28 June)
• Re: [whatwg/xhr] Editorial: Refactor for auto-reporting timing from fetch (PR #347) (Tuesday, 28 June)
• Re: [whatwg/xhr] Editorial: Refactor for auto-reporting timing from fetch (PR #347) (Tuesday, 28 June)
• Re: [whatwg/xhr] Editorial: Refactor for auto-reporting timing from fetch (PR #347) (Tuesday, 28 June)
• Re: [whatwg/xhr] Editorial: Refactor for auto-reporting timing from fetch (PR #347) (Tuesday, 28 June)
• Re: [whatwg/fetch] Editorial: Remove the nonexistent controller variable in the fetch algorithm. (PR #1462) (Friday, 24 June)
• Re: [whatwg/fetch] Editorial: Fix ending tag for dfn (PR #1455) (Thursday, 23 June)
• Re: [whatwg/fetch] Expose decoded/encoded size for constructed responses (PR #1456) (Sunday, 19 June)
• Re: [whatwg/fetch] Expose decoded/encoded size for constructed responses (PR #1456) (Sunday, 19 June)
• [whatwg/fetch] Expose decoded/encoded size for constructed responses (PR #1456) (Sunday, 19 June)
• [whatwg/fetch] Editorial: Fix ending tag for dfn (PR #1455) (Friday, 17 June)
• Re: [whatwg/xhr] Editorial: Refactor for auto-reporting timing from fetch (PR #347) (Friday, 17 June)
• Re: [whatwg/xhr] Editorial: Refactor for auto-reporting timing from fetch (PR #347) (Friday, 17 June)
• Re: [whatwg/xhr] Refactor for auto-reporting timing from fetch (PR #347) (Wednesday, 15 June)
• Re: [whatwg/xhr] Refactor for auto-reporting timing from fetch (PR #347) (Wednesday, 15 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Wednesday, 15 June)
• Re: [whatwg/xhr] Refactor for auto-reporting timing from fetch (PR #347) (Wednesday, 15 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Wednesday, 15 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Wednesday, 15 June)
• Re: [whatwg/xhr] Refactor for auto-reporting timing from fetch (PR #347) (Wednesday, 15 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/xhr] Refactor for auto-reporting timing from fetch (PR #347) (Tuesday, 14 June)
• Re: [whatwg/xhr] Refactor for auto-reporting timing from fetch (PR #347) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• [whatwg/fetch] Add `initiatorType` values to CSP/destination table (Issue #1452) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 14 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Thursday, 9 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Wednesday, 8 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Wednesday, 8 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Wednesday, 8 June)
• Re: [whatwg/fetch] Editorial: Update severals biblio refs to HTTP-SEMANTICS (PR #1451) (Wednesday, 8 June)
• [whatwg/fetch] Editorial: Update severals biblio refs to HTTP-SEMANTICS (PR #1451) (Wednesday, 8 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Wednesday, 8 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Wednesday, 8 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 7 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 7 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 7 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Tuesday, 7 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Wednesday, 1 June)

Patrick H. Lauke

• Re: [w3c/touch-events] Remove outdated "Issues" section (PR #132) (Wednesday, 29 June)
• [w3c/touch-events] Remove outdated "Issues" section (PR #132) (Wednesday, 29 June)
• Re: [w3c/touch-events] Change `may` to `should` for non-cancelable events (PR #131) (Wednesday, 29 June)
• Re: [w3c/touch-events] Require non-cancelable events with "should" or "must" when there are only passive listeners (Issue #130) (Wednesday, 29 June)
• [w3c/touch-events] Change `may` to `should` for non-cancelable events (PR #131) (Wednesday, 29 June)
• Re: [w3c/touch-events] Require non-cancelable events with "should" or "must" when there are only passive listeners (Issue #130) (Wednesday, 29 June)
• Re: [w3c/touch-events] Update changelog (PR #129) (Friday, 3 June)
• [w3c/touch-events] Update changelog (PR #129) (Friday, 3 June)
• Re: [w3c/touch-events] Change a `should` to `MUST` (PR #128) (Friday, 3 June)
• [w3c/touch-events] Change a `should` to `MUST` (PR #128) (Friday, 3 June)
• Re: [w3c/touch-events] Add standard CoC (PR #127) (Friday, 3 June)
• [w3c/touch-events] Add standard CoC (PR #127) (Friday, 3 June)
• Re: [w3c/touch-events] Add correct respec reference (PR #126) (Friday, 3 June)
• [w3c/touch-events] Add correct respec reference (PR #126) (Friday, 3 June)
• Re: [w3c/touch-events] Reword altitudeAngle/azimuthAngle descriptions in line with PE, add illustrations (PR #125) (Friday, 3 June)
• [w3c/touch-events] Reword altitudeAngle/azimuthAngle descriptions in line with PE, add illustrations (PR #125) (Friday, 3 June)
• Re: [w3c/touch-events] Add pr-preview (PR #124) (Friday, 3 June)
• [w3c/touch-events] Add pr-preview (PR #124) (Friday, 3 June)
• Re: [w3c/touch-events] Add `defer` to respec script (PR #123) (Friday, 3 June)
• [w3c/touch-events] Add `defer` to respec script (PR #123) (Friday, 3 June)
• Re: [w3c/touch-events] Improve markup for event summary table (PR #122) (Friday, 3 June)
• Re: [w3c/touch-events] Improve markup for event summary table (PR #122) (Friday, 3 June)
• Re: [w3c/touch-events] Improve markup for event summary table (PR #122) (Friday, 3 June)

Paul Grenier

• Re: [w3ctag/design-reviews] Early design review: Focusgroup (Issue #732) (Sunday, 19 June)

Peter Beverloo

• Re: [w3c/push-api] Rewrite .subscribe() to fix various bugs (PR #350) (Friday, 24 June)
• Re: [w3c/push-api] check and consume user activation (PR #348) (Friday, 24 June)

Peter Linss

• Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718) (Monday, 27 June)
• Re: [w3ctag/design-reviews] Element.isVisible review (Issue #734) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Element.isVisible review (Issue #734) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735) (Thursday, 16 June)

Peter Van der Beken

• Re: [whatwg/webidl] Allow dictionary values to default to undefined (#983) (Friday, 3 June)
• Re: [whatwg/webidl] Allow dictionary values to default to undefined (#983) (Friday, 3 June)

Philip Jägenstedt

• Re: [whatwg/dom] Add onabort definition and add onslotchange (#785) (Thursday, 23 June)
• Re: [whatwg/dom] Add onabort definition and add onslotchange (#785) (Thursday, 23 June)

Rakina Zata Amni

• Re: [w3c/gamepad] gamepadconnected/disconnected events & non-"fully active" documents (#149) (Thursday, 16 June)

Recep

• [whatwg/webidl] Optional (Issue #1155) (Friday, 10 June)
• [whatwg/webidl] Null (Issue #1154) (Friday, 10 June)

Rick Byers

• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Friday, 17 June)
• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Friday, 17 June)

Robert Flack

• Re: [w3c/uievents] Remove text selection from the dblclick default action - #328 (PR #329) (Friday, 24 June)
• Re: [w3c/uievents] Remove text selection from the dblclick default action - #328 (PR #329) (Friday, 24 June)
• [w3c/uievents] Remove text selection from the dblclick default action - #328 (PR #329) (Friday, 24 June)
• [w3c/uievents] Remove dblclick text selection default action to match browsers (Issue #328) (Friday, 24 June)
• Re: [w3c/uievents] Introduce contextmenuclose or similar event. (#309) (Tuesday, 7 June)

Rossen Atanassov

• Re: [w3ctag/design-reviews] Element.isVisible review (Issue #734) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Early design review of the **updated** Multi-Screen Window Placement API (#602) (Monday, 13 June)
• Re: [w3ctag/design-reviews] [css-values-4] The Large, Small, and Dynamic Viewport Sizes (Issue #706) (Wednesday, 8 June)
• Re: [w3ctag/design-reviews] [css-values-4] The Large, Small, and Dynamic Viewport Sizes (Issue #706) (Wednesday, 8 June)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Monday, 6 June)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Monday, 6 June)

Russell Beswick

• Re: [WICG/webcomponents] The way to access current script or current root, from Shadow DOM (#717) (Thursday, 23 June)

SabineWren

• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Sunday, 12 June)

said

• [whatwg/encoding] encoding/resources/utf-32-big-endian-nobom.html (Issue #289) (Tuesday, 21 June)

sam goto

• Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718) (Thursday, 30 June)
• Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718) (Thursday, 30 June)
• Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718) (Thursday, 30 June)

Sam Sneddon

• Re: [whatwg/dom] document.createEvent() should maybe not be conditional upon exposure (#952) (Monday, 6 June)

Samuel Williams

• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Friday, 17 June)
• Re: [whatwg/fetch] Fetch body streams are not full duplex (#1254) (Monday, 13 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Thursday, 9 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Wednesday, 1 June)

Scott Haseley

• Re: [whatwg/dom] Add a fully active check for EventTarget in event listener inner invoke (PR #1085) (Monday, 13 June)
• Re: [whatwg/dom] Add a fully active check for EventTarget in event listener inner invoke (PR #1085) (Monday, 13 June)
• [whatwg/dom] Add a fully active check for EventTarget in event listener inner invoke (PR #1085) (Wednesday, 8 June)
• Re: [whatwg/dom] Should event dispatch check that the event target is in a fully active realm? (Issue #1084) (Saturday, 4 June)
• Re: [whatwg/dom] Should event dispatch check that the event target is in a fully active realm? (Issue #1084) (Friday, 3 June)
• [whatwg/dom] Should event dispatch check that the event target is in a fully active realm? (Issue #1084) (Friday, 3 June)

Shivani Sharma

• Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735) (Friday, 17 June)
• Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735) (Tuesday, 14 June)
• Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735) (Monday, 13 June)

Simon Chan

• Re: [whatwg/streams] Returning buffers to the underlying source (Issue #1217) (Saturday, 11 June)

Simon Fraser

• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 16 June)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 16 June)

Simon Pieters

• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Thursday, 30 June)
• Re: [w3c/uievents] Add mousewheel to the "Legacy Event Types" section (Issue #331) (Thursday, 30 June)
• Re: [w3c/uievents] Add mousewheel to the "Legacy Event Types" section (Issue #331) (Thursday, 30 June)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 30 June)
• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Thursday, 30 June)
• [w3c/touch-events] Expected behavior of non-cancelable events intervention is unclear (Issue #133) (Wednesday, 29 June)
• Re: [w3c/uievents] Specify non-cancelable wheel/mousewheel events when there are no non-passive listeners (PR #330) (Wednesday, 29 June)
• Re: [w3c/uievents] Specify non-cancelable wheel/mousewheel events when there are no non-passive listeners (PR #330) (Wednesday, 29 June)
• [w3c/uievents] Specify non-cancelable wheel/mousewheel events when there are no non-passive listeners (PR #330) (Wednesday, 29 June)
• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Tuesday, 28 June)
• Re: [w3c/uievents] Document the cancelability of wheel events (#282) (Tuesday, 28 June)
• Re: [w3c/uievents] Document the cancelability of wheel events (#282) (Tuesday, 28 June)
• [w3c/touch-events] Require non-cancelable events with "should" or "must" when there are only passive listeners (Issue #130) (Tuesday, 28 June)
• Re: [w3c/uievents] Add WheelEvent#wheelDelta/wheelDeltaX/wheelDeltaY (#138) (Monday, 20 June)
• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Monday, 20 June)
• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Monday, 20 June)
• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Friday, 17 June)
• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Friday, 17 June)
• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Friday, 17 June)
• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Friday, 17 June)
• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Friday, 17 June)
• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Friday, 17 June)
• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Friday, 17 June)
• Re: [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Friday, 17 June)
• [whatwg/dom] Specify addEventListener default passive hack for smoothscroll.js (Issue #1088) (Friday, 17 June)
• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Friday, 17 June)
• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Friday, 17 June)
• Re: [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Thursday, 16 June)
• [whatwg/dom] Specify default passive for document-level wheel/mousewheel/touchstart/touchmove events (PR #1087) (Thursday, 16 June)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 16 June)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 16 June)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 16 June)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 16 June)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 16 June)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Thursday, 16 June)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Wednesday, 15 June)
• Re: [whatwg/dom] Allow more characters in element/attribute names and prefixes (PR #1079) (Wednesday, 8 June)
• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Wednesday, 8 June)
• Re: [whatwg/dom] document.createEvent() should maybe not be conditional upon exposure (#952) (Tuesday, 7 June)

sinner13ozan

• [whatwg/webidl] h (Issue #1153) (Monday, 6 June)

smaug----

• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 30 June)
• Re: [whatwg/fetch] blob: fetch of slice() without valid content type yields unexpected results (Issue #1464) (Tuesday, 28 June)
• Re: [whatwg/dom] Add a fully active check for EventTarget in event listener inner invoke (PR #1085) (Monday, 20 June)

snianu

• [w3c/clipboard-apis] Async clipboard read and race conditions. (Issue #180) (Friday, 24 June)
• Re: [w3c/clipboard-apis] What are the mandatory data types for Asynchronous Clipboard API? (Issue #177) (Friday, 10 June)
• Re: [w3c/clipboard-apis] Should ClipboardItem be marked as [SecureContext]? (#103) (Friday, 10 June)
• Re: [w3c/clipboard-apis] Should ClipboardItem be marked as [SecureContext]? (#103) (Friday, 10 June)
• [w3c/clipboard-apis] Should reading the clipboard throw DataError or empty clipboard items? (Issue #179) (Friday, 10 June)
• Re: [w3c/clipboard-apis] The MIME type checking should ignore the "web " prefix (Issue #178) (Wednesday, 8 June)
• Re: [w3c/clipboard-apis] Add Web Custom format (PR #175) (Tuesday, 7 June)
• Re: [w3c/clipboard-apis] Add Web Custom format (PR #175) (Monday, 6 June)
• Re: [w3c/clipboard-apis] Add Web Custom format (PR #175) (Saturday, 4 June)

Syndace

• Re: [w3c/ServiceWorker] Registering service workers for unique origins? (#1437) (Friday, 24 June)

Tab Atkins Jr.

• Re: [whatwg/webidl] Promises: resolve algorithm should accept a promise (#957) (Monday, 6 June)
• Re: [whatwg/webidl] Meta: downstream issues (Issue #1147) (Monday, 6 June)

Takumi Fujimoto

• Re: [w3ctag/design-reviews] Site-initiated mirroring (Issue #745) (Thursday, 30 June)
• [w3ctag/design-reviews] Site-initiated mirroring (Issue #745) (Monday, 6 June)

Tom Schuster

• [whatwg/fetch] Always send Origin header for (non HEAD/GET) CORS requests (PR #1463) (Friday, 24 June)
• Re: [whatwg/fetch] Referrer policy of "no-referrer" sets Origin to null on same-origin "cors" requests (#1022) (Wednesday, 22 June)
• Re: [whatwg/fetch] Referrer policy of "no-referrer" sets Origin to null on same-origin "cors" requests (#1022) (Wednesday, 22 June)
• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Monday, 6 June)

Travis Leithead

• Re: [w3ctag/design-reviews] Early design review: Focusgroup (Issue #732) (Wednesday, 22 June)
• [w3c/editing] Add June 9, 2022 minutes (PR #401) (Thursday, 9 June)

Vitaliy Potapov

• Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920) (Sunday, 12 June)
• Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920) (Saturday, 11 June)
• Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920) (Thursday, 9 June)

vmpstr

• Re: [w3ctag/design-reviews] renderPriority element attribute (#676) (Tuesday, 28 June)
• Re: [w3ctag/design-reviews] Element.isVisible review (Issue #734) (Tuesday, 21 June)
• Re: [w3ctag/design-reviews] Element.isVisible review (Issue #734) (Thursday, 9 June)
• Re: [w3ctag/design-reviews] Shared Element Transitions - Early Review (#631) (Thursday, 9 June)

W3C Bot

• Re: [w3c/push-api] chore(tidy): tidy up document (PR #351) (Thursday, 2 June)
• Re: [w3c/uievents] Fixed typos (PR #327) (Wednesday, 1 June)

wayne glicco

• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Wednesday, 8 June)

Will Hawkins

• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 27 June)

Xiaocheng Hu

• Re: [whatwg/fetch] Pass in render blocking status via finalize and report timing (PR #1449) (Tuesday, 14 June)

Yajing Tang

• [w3c/manifest] Use ordered map JSON in id processing (PR #1040) (Thursday, 2 June)

Yoav Weiss

• Re: [whatwg/fetch] Prevent cross-origin sensitive header probing (PR #1434) (Tuesday, 28 June)
• Re: [whatwg/fetch] Expose decoded/encoded size for constructed responses (PR #1456) (Sunday, 19 June)
• Re: [whatwg/fetch] Pass in render blocking status via finalize and report timing (PR #1449) (Tuesday, 14 June)
• Re: [whatwg/fetch] Prevent cross-origin sensitive header probing (PR #1434) (Friday, 3 June)
• Re: [w3ctag/design-reviews] Markup based Client Hints delegation for third-party content (Issue #702) (Thursday, 2 June)

Yoichi Osato

• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Thursday, 16 June)

Yonathan Randolph

• Re: [whatwg/streams] Fix invalid high water mark for tee branches (PR #1234) (Wednesday, 1 June)
• Re: [whatwg/streams] Fix invalid high water mark for tee branches (PR #1234) (Wednesday, 1 June)
• Re: [whatwg/streams] Fix invalid high water mark for tee branches (PR #1234) (Wednesday, 1 June)
• [whatwg/streams] Fix invalid high water mark for tee branches (PR #1234) (Wednesday, 1 June)

youennf

• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Tuesday, 14 June)
• Re: [whatwg/fetch] Define the "memory cache" (Issue #1400) (Sunday, 5 June)

Yutaka Hirano

• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Tuesday, 28 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Tuesday, 28 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Tuesday, 28 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Tuesday, 28 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Tuesday, 28 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Tuesday, 28 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Wednesday, 22 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Wednesday, 22 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Wednesday, 22 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 21 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 20 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 20 June)
• [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Monday, 20 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Friday, 17 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Friday, 17 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Thursday, 16 June)
• Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Thursday, 16 June)
• Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413) (Wednesday, 15 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Monday, 13 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Monday, 13 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Thursday, 9 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Thursday, 9 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Thursday, 9 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Wednesday, 8 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Wednesday, 8 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Wednesday, 1 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Wednesday, 1 June)
• Re: [whatwg/fetch] Disallow streaming upload on HTTP/1.1 connections (PR #1444) (Wednesday, 1 June)
• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Wednesday, 1 June)

Yves Lafon

• [w3c/ServiceWorker] align default metadata used for both ED and CRD (PR #1647) (Thursday, 16 June)

ziyunfei

• [w3c/clipboard-apis] The MIME type checking should ignore the "web" prefix (Issue #178) (Wednesday, 8 June)

zizifn

• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Thursday, 23 June)

Last message date: Thursday, 30 June 2022 22:50:18 UTC