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

=JeffH

• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Thursday, 10 February)

Aaron Gustafson

• Re: [w3c/manifest] Why is purpose a "unordered set of unique space-separated tokens"? (#903) (Friday, 4 February)
• Re: [w3c/manifest] Why is purpose a "unordered set of unique space-separated tokens"? (#903) (Thursday, 3 February)
• Re: [w3c/manifest] Status report and planning for TPAC 2021 (#999) (Thursday, 3 February)
• Re: [w3c/manifest] Link to manifest-app-info in the README (Issue #1027) (Thursday, 3 February)
• Re: [w3c/manifest] Link to manifest-app-info in the README (PR #1030) (Thursday, 3 February)
• Re: [w3c/manifest] Link to manifest-app-info in the README (PR #1030) (Thursday, 3 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 3 February)
• Re: [w3c/manifest] Link to manifest-app-info in the README (Issue #1027) (Wednesday, 2 February)

Adam Klein

• Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172) (Thursday, 24 February)

Adam Langley

• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Thursday, 10 February)
• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Wednesday, 2 February)
• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Tuesday, 1 February)

Adam Rice

• Re: [whatwg/streams] WritableStreamDefaultController [[strategySizeAlgorithm]] called after being set to undefined (Issue #1218) (Tuesday, 15 February)
• [whatwg/streams] WritableStreamDefaultController [[strategySizeAlgorithm]] called after being set to undefined (Issue #1218) (Tuesday, 15 February)
• Re: [whatwg/fetch] Integrate early hints https://tools.ietf.org/html/rfc8297 (#1225) (Thursday, 10 February)
• Re: [whatwg/streams] Add tests for interaction between autoAllocateChunkSize and respondWithNewView (PR #1216) (Wednesday, 9 February)
• Re: [whatwg/streams] Add WritableStream's signal definition for other specs (PR #1215) (Monday, 7 February)
• Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214) (Wednesday, 2 February)
• Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214) (Wednesday, 2 February)

Alex Crichton

• Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097) (Tuesday, 8 February)

Alex Keng

• Re: [w3c/editing] Expose keyboard language? (#351) (Monday, 7 February)
• Re: [w3c/editing] Expose keyboard language? (#351) (Monday, 7 February)

Alwin Blok

• Re: [whatwg/url] Support relative URLs (#531) (Saturday, 12 February)
• Re: [whatwg/url] Support relative URLs (#531) (Saturday, 12 February)
• Re: [whatwg/url] Support relative URLs (#531) (Wednesday, 9 February)
• Re: [whatwg/url] Support relative URLs (#531) (Wednesday, 9 February)
• Re: [whatwg/url] Support relative URLs (#531) (Tuesday, 8 February)
• Re: [whatwg/url] Support relative URLs (#531) (Tuesday, 8 February)
• Re: [whatwg/url] Support relative URLs (#531) (Saturday, 5 February)

Anders Rundgren

• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Friday, 18 February)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Friday, 11 February)

Andreu Botella

• Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172) (Friday, 25 February)
• Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098) (Monday, 7 February)

Andrew Williams

• Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134) (Friday, 11 February)
• Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134) (Friday, 11 February)
• Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134) (Friday, 11 February)
• Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134) (Friday, 11 February)
• [whatwg/storage] Add a storage key comparison algorithm (PR #134) (Thursday, 10 February)
• [whatwg/storage] Add an algorithm for comparing storage keys (Issue #133) (Thursday, 10 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Wednesday, 9 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Wednesday, 9 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Tuesday, 8 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Tuesday, 8 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Tuesday, 8 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Tuesday, 8 February)
• [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Tuesday, 8 February)
• Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131) (Tuesday, 8 February)
• Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131) (Wednesday, 2 February)
• [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131) (Wednesday, 2 February)

andrewfstratton

• Re: [w3c/gamepad] Require secure context for gamepad state and events (#120) (Thursday, 17 February)

Anne van Kesteren

• Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404) (Monday, 28 February)
• Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406) (Monday, 28 February)
• Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406) (Monday, 28 February)
• Re: [whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107) (Friday, 25 February)
• Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172) (Thursday, 24 February)
• Re: [whatwg/storage] Review Draft Publication: February 2022 (PR #135) (Wednesday, 23 February)
• Re: [whatwg/storage] Review Draft Publication: February 2022 (PR #135) (Wednesday, 23 February)
• Re: [whatwg/storage] Editorial: use string literal for permission name (PR #136) (Wednesday, 23 February)
• Re: [whatwg/storage] Editorial: use string literal for permission name (PR #136) (Wednesday, 23 February)
• Re: [whatwg/storage] Editorial: use string literal for permission name (PR #136) (Wednesday, 23 February)
• Re: [whatwg/storage] Editorial: use string literal for permission name (PR #136) (Wednesday, 23 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 23 February)
• [WICG/webcomponents] Place to chat about Web Components standardization (Issue #956) (Wednesday, 23 February)
• Re: [w3c/permissions] Removal of PermissionName broke downstream standards (Issue #366) (Tuesday, 22 February)
• Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813) (Tuesday, 22 February)
• Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813) (Tuesday, 22 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Monday, 21 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Monday, 21 February)
• Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325) (Monday, 21 February)
• [w3c/permissions] Removal of PermissionName broke downstream standards (Issue #366) (Monday, 21 February)
• Re: [whatwg/url] Review Draft Publication: February 2022 (PR #687) (Monday, 21 February)
• Re: [whatwg/xhr] Review Draft Publication: February 2022 (PR #341) (Monday, 21 February)
• [whatwg/streams] Review Draft Publication: February 2022 (PR #1219) (Monday, 21 February)
• [whatwg/xhr] Review Draft Publication: February 2022 (PR #341) (Monday, 21 February)
• [whatwg/url] Review Draft Publication: February 2022 (PR #687) (Monday, 21 February)
• [whatwg/storage] Review Draft Publication: February 2022 (PR #135) (Monday, 21 February)
• Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059) (Friday, 18 February)
• Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059) (Friday, 18 February)
• Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059) (Friday, 18 February)
• Re: [w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170) (Wednesday, 16 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 16 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 16 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Tuesday, 15 February)
• [whatwg/dom] Add Security and privacy considerations section (PR #1058) (Monday, 14 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Monday, 14 February)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 14 February)
• Re: [whatwg/dom] Privacy/Security considerations section (#1013) (Monday, 14 February)
• Re: [whatwg/dom] getComputedStyle should also be a method of the element (Issue #1057) (Monday, 14 February)
• Re: [whatwg/dom] getComputedStyle should also be a method of the element (Issue #1057) (Monday, 14 February)
• Re: [whatwg/fetch] Add `Response.json` static method (PR #1392) (Monday, 14 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Monday, 14 February)
• Re: [whatwg/url] Editorial: address some minor nits (PR #686) (Friday, 11 February)
• Re: [whatwg/url] Editorial: address some minor nits (PR #686) (Friday, 11 February)
• Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134) (Friday, 11 February)
• [whatwg/url] Editorial: address some minor nits (PR #686) (Friday, 11 February)
• Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134) (Friday, 11 February)
• Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134) (Friday, 11 February)
• Re: [whatwg/storage] Add an algorithm for comparing storage keys (Issue #133) (Friday, 11 February)
• Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134) (Friday, 11 February)
• Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134) (Friday, 11 February)
• Re: [whatwg/storage] Add a storage key comparison algorithm (PR #134) (Friday, 11 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Friday, 11 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 11 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 11 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 11 February)
• Re: [whatwg/fetch] Define the "Preload Cache" (#590) (Friday, 11 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 11 February)
• [whatwg/fetch] Define the "memory cache" (Issue #1400) (Friday, 11 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 11 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 11 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 11 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Friday, 11 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Friday, 11 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Friday, 11 February)
• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Friday, 11 February)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Thursday, 10 February)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Thursday, 10 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Thursday, 10 February)
• Re: [whatwg/fetch] Merging Client Hints Infrastructure into FETCH (and HTML) Standards (Issue #1398) (Thursday, 10 February)
• Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131) (Thursday, 10 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Thursday, 10 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Thursday, 10 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Thursday, 10 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Thursday, 10 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Thursday, 10 February)
• Re: [w3c/permissions] Add "popups" permission type (#210) (Thursday, 10 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 9 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Tuesday, 8 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Tuesday, 8 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Tuesday, 8 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Tuesday, 8 February)
• Re: [whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055) (Tuesday, 8 February)
• Re: [whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055) (Tuesday, 8 February)
• Re: [whatwg/dom] Should AbortSignal.timeout only be exposed on (Window, Worker)? (Issue #1054) (Tuesday, 8 February)
• Re: [whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055) (Tuesday, 8 February)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Tuesday, 8 February)
• Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Tuesday, 8 February)
• Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097) (Tuesday, 8 February)
• Re: [w3c/clipboard-apis] Clipboard Pickling: should the unsanitized option support a way to ask for all representations to be unsanitized? (Issue #167) (Tuesday, 8 February)
• Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131) (Tuesday, 8 February)
• Re: [w3c/clipboard-apis] Clipboard Pickling: should the unsanitized option support a way to ask for all representations to be unsanitized? (Issue #167) (Monday, 7 February)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Monday, 7 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Monday, 7 February)
• Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097) (Monday, 7 February)
• Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131) (Monday, 7 February)
• Re: [whatwg/webidl] Introduce "mark as handled" for promises (PR #1090) (Monday, 7 February)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Monday, 7 February)
• Re: [whatwg/fetch] Add `Response.json` static method (PR #1392) (Monday, 7 February)
• Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Monday, 7 February)
• Re: [whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055) (Sunday, 6 February)

arenevier

• [whatwg/fetch] make Response and Headers serializable (Issue #1399) (Friday, 4 February)

Ari Chivukula

• [whatwg/fetch] Merging Client Hints Infrastructure into FETCH (and HTML) Standards (Issue #1398) (Wednesday, 2 February)

Arnaud (Arno) Mandy

• Re: [w3ctag/design-reviews] Compute Pressure API (#621) (Tuesday, 8 February)

Arslan Chaudhry

• [whatwg/encoding] Ending (Issue #281) (Tuesday, 8 February)

bashi

• Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404) (Monday, 28 February)
• Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404) (Monday, 21 February)
• Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404) (Monday, 21 February)
• Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404) (Thursday, 17 February)
• Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404) (Thursday, 17 February)
• [whatwg/fetch] Process 103 Early Hints response (PR #1404) (Thursday, 17 February)
• Re: [whatwg/fetch] Integrate early hints https://tools.ietf.org/html/rfc8297 (#1225) (Monday, 14 February)

basketofsoftkittens

• Re: [whatwg/fetch] Streams based uploading with Content-Length (not chunked encoding) (#95) (Saturday, 12 February)

Ben Kelly

• Re: [w3c/ServiceWorker] Unnecessary Origin Restriction (Issue #1628) (Wednesday, 23 February)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 February)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 8 February)
• Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131) (Monday, 7 February)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Thursday, 3 February)

Ben Olden-Cooligan

• [w3c/IndexedDB] Batch get/getAll (Issue #376) (Friday, 18 February)

Bo Cupp

• Re: [w3c/editing] Add explainer for custom format read/write. (PR #392) (Wednesday, 16 February)
• [w3c/editing] Updating video conferencing link to Jitsi (PR #389) (Thursday, 10 February)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Wednesday, 9 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 9 February)
• [w3c/clipboard-apis] Clipboard Pickling: should the unsanitized option support a way to ask for all representations to be unsanitized? (Issue #167) (Wednesday, 2 February)
• Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166) (Wednesday, 2 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Tuesday, 1 February)
• Re: [w3ctag/design-reviews] Pen Events API (#553) (Tuesday, 1 February)

Brian E Carpenter

• Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Tuesday, 8 February)

cinolt

• Re: [w3c/ServiceWorker] Unnecessary Origin Restriction (Issue #1628) (Wednesday, 23 February)
• [w3c/ServiceWorker] Unnecessary Origin Restriction (Issue #1628) (Wednesday, 23 February)

cnpsc

• Re: [w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682) (Thursday, 17 February)

CSS Meeting Bot

• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Thursday, 10 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Thursday, 10 February)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Thursday, 10 February)
• Re: [w3c/editing] Updating video conferencing link to Jitsi (PR #389) (Thursday, 10 February)

cynthia

• Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703) (Tuesday, 15 February)
• Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703) (Tuesday, 15 February)
• Re: [w3ctag/design-reviews] Priority Hints API (Issue #704) (Tuesday, 15 February)
• Re: [w3ctag/design-reviews] Priority Hints API (Issue #704) (Tuesday, 15 February)
• Re: [w3ctag/design-reviews] Priority Hints API (Issue #704) (Tuesday, 15 February)
• Re: [w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695) (Monday, 14 February)
• Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696) (Saturday, 12 February)
• Re: [w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] Region Capture (Issue #710) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] Pen Events API (#553) (Tuesday, 1 February)
• Re: [w3ctag/design-reviews] Pen Events API (#553) (Tuesday, 1 February)

Daniel

• Re: [w3ctag/design-reviews] Deprecating `document.domain` setter. (#564) (Tuesday, 1 February)

Daniel Appelquist

• Re: [w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695) (Tuesday, 22 February)
• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Monday, 21 February)
• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Monday, 21 February)
• Re: [w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682) (Thursday, 17 February)
• Re: [w3ctag/design-reviews] Review request for Confirmation of Action API (Issue #713) (Tuesday, 15 February)
• Re: [w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682) (Tuesday, 15 February)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Monday, 14 February)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Monday, 14 February)
• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Monday, 14 February)
• Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696) (Thursday, 10 February)
• Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Monday, 7 February)
• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Monday, 7 February)
• Re: [w3ctag/design-reviews] [mediaqueries-4] Range contexts (Issue #707) (Wednesday, 2 February)
• Re: [w3ctag/design-reviews] [css-values-4] The Large, Small, and Dynamic Viewport Sizes (Issue #706) (Wednesday, 2 February)
• Re: [w3ctag/design-reviews] Priority Hints API (Issue #704) (Wednesday, 2 February)
• Re: [w3ctag/design-reviews] Credential Management: Conditional Mediation (Issue #692) (Tuesday, 1 February)
• Re: [w3ctag/design-reviews] Credential Management: Conditional Mediation (Issue #692) (Tuesday, 1 February)
• Re: [w3ctag/design-reviews] Conditional Focus (When Display-Capture Starts) (#679) (Tuesday, 1 February)

Dapeng(Max) Liu

• Re: [w3ctag/design-reviews] Web App Launch Handler (Issue #683) (Wednesday, 23 February)
• Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703) (Tuesday, 8 February)

Darien Maillet Valentine

• [whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107) (Friday, 25 February)
• Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106) (Tuesday, 22 February)
• Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106) (Tuesday, 22 February)
• Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106) (Tuesday, 22 February)
• [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106) (Tuesday, 22 February)
• Re: [whatwg/webidl] ExtendedAttributeList can match unbalanced ( ), [ ], and { } (Issue #1100) (Friday, 18 February)
• Re: [whatwg/webidl] ExtendedAttributeList can match unbalanced ( ), [ ], and { } (Issue #1100) (Tuesday, 15 February)
• Re: [whatwg/webidl] Mismatch between normative and informative text about the Other grammar rule (Issue #1100) (Sunday, 13 February)
• Re: [whatwg/dom] getComputedStyle should also be a method of the element (Issue #1057) (Sunday, 13 February)

Dasein.

• Re: [w3ctag/design-reviews] <search> HTML element (Issue #714) (Saturday, 26 February)

dmvol81

• [whatwg/fetch] United Stated (Issue #1401) (Saturday, 12 February)

Domenic Denicola

• Re: [whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107) (Friday, 25 February)
• Re: [whatwg/streams] Editorial: Mark high water mark definition as exported (PR #1221) (Thursday, 24 February)
• Re: [whatwg/streams] Editorial: Mark high water mark definition as exported (PR #1221) (Thursday, 24 February)
• Re: [whatwg/streams] Editorial: Mark high water mark definition as exported (PR #1221) (Thursday, 24 February)
• Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106) (Tuesday, 22 February)
• Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106) (Tuesday, 22 February)
• Re: [whatwg/webidl] CreateBuiltinFunction’s signature has changed (Issue #1106) (Tuesday, 22 February)
• Re: [whatwg/streams] WritableStreamDefaultController [[strategySizeAlgorithm]] called after being set to undefined (Issue #1218) (Tuesday, 15 February)
• Re: [whatwg/url] Editorial: address some minor nits (PR #686) (Friday, 11 February)
• Re: [whatwg/fetch] Define the "memory cache" (Issue #1400) (Friday, 11 February)
• Re: [whatwg/streams] Returning buffers to the underlying source (Issue #1217) (Friday, 11 February)
• Re: [whatwg/streams] Add tests for interaction between autoAllocateChunkSize and respondWithNewView (PR #1216) (Wednesday, 9 February)
• Re: [w3ctag/design-reviews] AbortSignal.timeout() (Issue #711) (Tuesday, 8 February)
• Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097) (Tuesday, 8 February)
• Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097) (Monday, 7 February)
• Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098) (Monday, 7 February)
• Re: [whatwg/streams] Add WritableStream's signal definition for other specs (PR #1215) (Monday, 7 February)
• [w3ctag/design-reviews] <search> HTML element (Issue #714) (Friday, 4 February)
• [whatwg/streams] Add WritableStream's signal definition for other specs (PR #1215) (Thursday, 3 February)
• Re: [whatwg/dom] Should AbortSignal.timeout only be exposed on (Window, Worker)? (Issue #1054) (Thursday, 3 February)
• Re: [whatwg/webidl] Introduce "mark as handled" for promises (PR #1090) (Wednesday, 2 February)
• Re: [whatwg/webidl] Introduce "mark as handled" for promises (PR #1090) (Wednesday, 2 February)
• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Wednesday, 2 February)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Wednesday, 2 February)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Wednesday, 2 February)
• Re: [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094) (Tuesday, 1 February)
• Re: [whatwg/fetch] Add `Response.json` static method (PR #1392) (Tuesday, 1 February)

Dominique Hazael-Massieux

• [w3c/permissions] "extra permission data" definition should be normative (Issue #369) (Friday, 25 February)
• [whatwg/streams] Editorial Mark high water mark definition as exported (PR #1221) (Wednesday, 23 February)

Elad Alon

• Re: [w3ctag/design-reviews] Conditional Focus (When Display-Capture Starts) (#679) (Tuesday, 22 February)
• Re: [w3ctag/design-reviews] Region Capture (Issue #710) (Tuesday, 8 February)

Eric Portis

• Re: [w3ctag/design-reviews] Markup based Client Hints delegation for third-party content (Issue #702) (Tuesday, 22 February)

ericorth

• Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325) (Tuesday, 22 February)
• Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325) (Friday, 18 February)
• Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325) (Friday, 18 February)

Ethan Jimenez

• [w3ctag/design-reviews] Review Request for CSS Subgrid (Issue #712) (Tuesday, 1 February)

Evan Stade

• Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005) (Friday, 11 February)
• Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005) (Friday, 11 February)
• Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005) (Friday, 11 February)

fdinburgh

• Re: [w3c/IndexedDB] Key Paths: Support iteration step operator (#35) (Wednesday, 16 February)

Fivepillars

• [whatwg/webidl] Genius-Tech-1998s (Issue #1109) (Sunday, 27 February)

François Beaufort

• Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703) (Wednesday, 23 February)
• Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703) (Friday, 11 February)
• Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703) (Thursday, 10 February)
• Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] HIDDevice forget() (Issue #703) (Tuesday, 8 February)

Fuqiao Xue

• [w3c/manifest] Link to manifest-app-info in the README (PR #1030) (Thursday, 3 February)

Gabriel Garrett

• Re: [w3c/ServiceWorker] How should import() work in service workers? (#1585) (Saturday, 12 February)

github-actions[bot]

• [w3c/manifest] Tidied up document using tidy-html5 (PR #1032) (Thursday, 17 February)
• [w3c/permissions] Tidied up document using tidy-html5 (PR #358) (Wednesday, 9 February)

Grimrepe7

• [whatwg/webidl] Intent to use Constants (Issue #1101) (Sunday, 13 February)

Hadley Beeman

• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Monday, 14 February)
• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Monday, 14 February)
• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Monday, 7 February)
• Re: [w3ctag/design-reviews] EPUB 3.3 (Issue #684) (Tuesday, 1 February)

Hamish Willee

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

Henri Sivonen

• Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172) (Friday, 25 February)

hiroshige-g

• Re: [whatwg/storage] Session storage and changing browsing contexts (#119) (Friday, 18 February)

hober

• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Tuesday, 22 February)
• Re: [whatwg/dom] Add Security and privacy considerations section (PR #1058) (Thursday, 17 February)
• Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696) (Monday, 14 February)

ianbjacobs

• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Monday, 14 February)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Monday, 14 February)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Thursday, 10 February)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Monday, 7 February)

Ivan Herman

• Re: [w3ctag/design-reviews] EPUB 3.3 (Issue #684) (Friday, 18 February)

J. Kalyana Sundaram

• Re: [w3ctag/design-reviews] Distributed Tracing WG: Baggage specification (#650) (Thursday, 24 February)
• Re: [w3ctag/design-reviews] Distributed Tracing WG: Baggage specification (#650) (Tuesday, 15 February)

Jahajohn

• [whatwg/webidl] Issue (Issue #1104) (Sunday, 20 February)

Jake Archibald

• Re: [w3c/ServiceWorker] Unnecessary Origin Restriction (Issue #1628) (Wednesday, 23 February)
• Re: [w3c/ServiceWorker] Unnecessary Origin Restriction (Issue #1628) (Wednesday, 23 February)
• Re: [w3c/ServiceWorker] when I deploy my app new version, latest version/changes not updated at the first time reload (Issue #1627) (Wednesday, 23 February)
• Re: [w3c/ServiceWorker] when I deploy my app new version, latest version/changes not updated at the first time reload (Issue #1627) (Wednesday, 23 February)
• Re: [whatwg/fetch] HTTP/2 server push support (#51) (Tuesday, 22 February)
• Re: [whatwg/fetch] HTTP/2 server push support (#51) (Tuesday, 22 February)

James Browning

• Re: [WICG/webcomponents] `customElements.upgrade` does not upgrade node subtrees cloned from `template` contents via `cloneNode` (Issue #946) (Thursday, 10 February)

James Cobban

• [whatwg/dom] getComputedStyle should also be a method of the element (Issue #1057) (Saturday, 12 February)

James M Snell

• Re: [whatwg/streams] ReadableStream.prototype.pipeline(...) (Issue #1184) (Tuesday, 8 February)
• Re: [whatwg/url] Support relative URLs (#531) (Thursday, 3 February)

Jan-Ivar Bruaroey

• Re: [w3c/permissions] Semantic Permission Bundles (#191) (Thursday, 10 February)
• Re: [w3c/permissions] Semantic Permission Bundles (#191) (Friday, 4 February)

Jeffrey Yasskin

• Re: [w3c/permissions] Safari returns different results for current permission state (#278) (Monday, 28 February)
• Re: [w3c/permissions] Provide guidelines or heuristics to prevent fingerprinting in case permission is denied (Issue #361) (Wednesday, 9 February)

Jeremy Davis

• Re: [whatwg/webidl] ExtendedAttributeList can match unbalanced ( ), [ ], and { } (Issue #1100) (Wednesday, 16 February)
• Re: [whatwg/webidl] ExtendedAttributeList can match unbalanced ( ), [ ], and { } (Issue #1100) (Tuesday, 15 February)
• [whatwg/webidl] Mismatch between normative and informative text about the Other grammar rule (Issue #1100) (Sunday, 13 February)

Jimmy Wärting

• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Thursday, 10 February)
• Re: [whatwg/fetch] Deprecate fetch (#28) (Thursday, 10 February)
• Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384) (Thursday, 3 February)
• Re: [w3c/FileAPI] Include file creation time and last access time. (#26) (Thursday, 3 February)
• Re: [w3c/FileAPI] Consider Blob.fromStream (returns a Promise<Blob>) (#140) (Thursday, 3 February)

jmayes41

• Re: [whatwg/dom] Proposal: Storage Access API (#560) (Wednesday, 23 February)

Jo (51D) Rabin

• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Saturday, 19 February)
• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Friday, 18 February)
• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Tuesday, 15 February)
• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Monday, 14 February)

Joe Pea

• Re: [WICG/webcomponents] SVG <use> tag with CSS ::part selector (Issue #955) (Saturday, 19 February)
• Re: [WICG/webcomponents] Adding support for ShadowDOM features in SVG (#942) (Saturday, 19 February)
• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 8 February)

Johannes Wilm

• Re: [w3c/editing] Update meeting invite link (PR #391) (Friday, 11 February)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Thursday, 10 February)
• Re: [w3c/editing] Move to Jitsi for meetings? (Issue #385) (Thursday, 10 February)
• Re: [w3c/editing] Move to Jitsi for meetings? (Issue #385) (Thursday, 10 February)
• Re: [w3c/editing] Add Feb 10 minutes (PR #390) (Thursday, 10 February)
• Re: [w3c/editing] Add Feb 10 minutes (PR #390) (Thursday, 10 February)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Thursday, 10 February)
• [w3c/editing] Update meeting invite link (PR #391) (Thursday, 10 February)
• Re: [w3c/editing] Updating video conferencing link to Jitsi (PR #389) (Thursday, 10 February)

JohnWatson2936

• Re: [w3c/manifest] BREAKING CHANGE: Replace "badge" with "monochrome" (#833) (2c55d86) (Saturday, 5 February)

Joshua Bell

• Re: [w3ctag/design-reviews] Font Table Access API (#400) (Friday, 25 February)
• Re: [w3c/ServiceWorker] The Cache objects do not expire unless authors *or users* delete the entries. (#1276) (Friday, 25 February)

jugglinmike

• [w3c/permissions] Automation: "Get Permission" (#349) (Friday, 4 February)

juj

• Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172) (Thursday, 24 February)
• Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172) (Thursday, 24 February)

Justin Fagnani

• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Wednesday, 23 February)
• Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147) (Monday, 14 February)

Justin Grant

• Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384) (Friday, 18 February)
• Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384) (Thursday, 3 February)

Kagami Sascha Rosylight

• Re: [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094) (Wednesday, 2 February)
• Re: [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094) (Wednesday, 2 February)
• Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214) (Tuesday, 1 February)
• Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214) (Tuesday, 1 February)
• [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214) (Tuesday, 1 February)
• Re: [whatwg/webidl] Force `[NewObject]` for Promise returning functions? (Issue #1084) (Tuesday, 1 February)
• Re: [whatwg/webidl] Force `[NewObject]` for Promise returning functions? (Issue #1084) (Tuesday, 1 February)
• Re: [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094) (Tuesday, 1 February)
• [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094) (Tuesday, 1 February)

Kaleidea

• Re: [w3ctag/design-reviews] <search> HTML element (Issue #714) (Thursday, 10 February)
• Re: [w3ctag/design-reviews] <search> HTML element (Issue #714) (Thursday, 10 February)
• Re: [w3ctag/design-reviews] <search> HTML element (Issue #714) (Wednesday, 9 February)
• Re: [w3ctag/design-reviews] <search> HTML element (Issue #714) (Wednesday, 9 February)
• Re: [w3ctag/design-reviews] <search> HTML element (Issue #714) (Wednesday, 9 February)
• Re: [w3ctag/design-reviews] <search> HTML element (Issue #714) (Wednesday, 9 February)
• Re: [w3ctag/design-reviews] <search> HTML element (Issue #714) (Wednesday, 9 February)
• Re: [w3ctag/design-reviews] <search> HTML element (Issue #714) (Wednesday, 9 February)

Karl

• Re: [whatwg/url] Support relative URLs (#531) (Wednesday, 9 February)
• Re: [whatwg/url] Support relative URLs (#531) (Wednesday, 9 February)
• Re: [whatwg/url] Support relative URLs (#531) (Tuesday, 8 February)
• Re: [whatwg/url] Support relative URLs (#531) (Tuesday, 8 February)
• Re: [whatwg/url] Support relative URLs (#531) (Friday, 4 February)

Kenneth Rohde Christiansen

• Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367) (Thursday, 24 February)
• Re: [w3c/permissions] Editorial: add UA + spec conformance classes (PR #368) (Thursday, 24 February)
• Re: [w3c/permissions] Handle non-fully-active documents (PR #365) (Thursday, 24 February)

KOLANICH

• Re: [w3c/permissions] Provide guidelines or heuristics to prevent fingerprinting in case permission is denied (Issue #361) (Wednesday, 9 February)

Konstantin V. Salikhov

• Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059) (Friday, 18 February)

Kyle Simpson

• Re: [whatwg/streams] WritableStreamDefaultController.abortReason (#1165) (Friday, 18 February)
• Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059) (Friday, 18 February)
• Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059) (Friday, 18 February)
• Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059) (Friday, 18 February)
• [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059) (Thursday, 17 February)

Larry Masinter

• Re: [whatwg/url] Support relative URLs (#531) (Thursday, 3 February)

Lea Verou

• Re: [w3ctag/design-reviews] `prefers-reduced-data` CSS Media Query (Issue #705) (Monday, 14 February)
• Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696) (Monday, 14 February)
• Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696) (Monday, 14 February)
• Re: [w3ctag/design-reviews] Compute Pressure API (#621) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] Compute Pressure API (#621) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] AbortSignal.timeout() (Issue #711) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] Review request before CR: CSS `selector()` (Issue #709) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] Review request before CR: CSS `selector()` (Issue #709) (Tuesday, 8 February)

liuchengwei555

• Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404) (Sunday, 20 February)

Louise Brett

• Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696) (Monday, 14 February)
• Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696) (Monday, 14 February)

Lu

• Re: [w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695) (Monday, 28 February)

Luca Casonato

• Re: [whatwg/fetch] Add `Response.json` static method (PR #1392) (Friday, 11 February)
• Re: [whatwg/fetch] Add `Response.json` static method (PR #1392) (Friday, 11 February)
• Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097) (Tuesday, 8 February)
• Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098) (Tuesday, 8 February)
• Re: [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098) (Monday, 7 February)
• [whatwg/webidl] Allow same identifier in static and regular ops (PR #1098) (Monday, 7 February)
• [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097) (Monday, 7 February)
• Re: [whatwg/fetch] Add `Response.json` static method (PR #1392) (Tuesday, 1 February)

mangelozzi

• Re: [w3c/ServiceWorker] support efficient offline redirects (#1457) (Tuesday, 22 February)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Thursday, 3 February)

Marcber1

• [whatwg/fetch] B (Issue #1402) (Monday, 14 February)

Marcos Cáceres

• Re: [w3c/permissions] Guidance on whether to add an API to the permissions spec (#116) (Friday, 25 February)
• Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367) (Friday, 25 February)
• Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367) (Friday, 25 February)
• Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367) (Friday, 25 February)
• Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367) (Friday, 25 February)
• Re: [w3c/permissions] Removal of PermissionName broke downstream standards (Issue #366) (Wednesday, 23 February)
• [whatwg/storage] Editorial: use string literal for permission name (PR #136) (Wednesday, 23 February)
• [w3c/permissions] Editorial: add UA + spec conformance classes (PR #368) (Tuesday, 22 February)
• Re: [w3c/permissions] Removal of PermissionName broke downstream standards (Issue #366) (Tuesday, 22 February)
• [w3c/permissions] Editorial: clarify Permission Policy / Powerful Feature overlap (PR #367) (Tuesday, 22 February)
• Re: [w3c/permissions] Editorial: clarify Permission Policy / Powerful Feature overlap (PR #367) (Tuesday, 22 February)
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Tuesday, 22 February)
• Re: [w3c/gamepad] Require secure context for gamepad state and events (#120) (Monday, 21 February)
• Re: [w3c/permissions] Handle non-fully-active documents (PR #365) (Monday, 21 February)
• Re: [w3c/permissions] Handle non-fully-active documents (PR #365) (Monday, 21 February)
• Re: [w3c/permissions] Handle non-fully-active documents (PR #365) (Monday, 21 February)
• Re: [w3c/permissions] Handle non-fully-active documents (PR #365) (Monday, 21 February)
• Re: [w3c/permissions] Handle not fully active documents when querying Permissions API (#249) (Monday, 21 February)
• Re: [w3c/permissions] Handle not fully active documents when querying Permissions API (#249) (Monday, 21 February)
• Re: [w3c/permissions] Handle non-fully-active documents (PR #365) (Monday, 21 February)
• [w3c/permissions] Handle non-fully-active documents (PR #365) (Monday, 21 February)
• Re: [w3c/permissions] Editorial: use permission state concept, not enum values (#285) (Monday, 21 February)
• Re: [w3c/permissions] Permissions states should be concepts (#243) (Monday, 21 February)
• Re: [w3c/permissions] Permissions states should be concepts (#243) (Monday, 21 February)
• Re: [w3c/permissions] Add "background-playback" permission type? (#193) (Monday, 21 February)
• Re: [w3c/permissions] Add "background-playback" permission type? (#193) (Monday, 21 February)
• Re: [whatwg/dom] Consider support for ES2015 iterator protocol for NodeIterator (#147) (Sunday, 20 February)
• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1032) (Thursday, 17 February)
• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1032) (Thursday, 17 February)
• Re: [w3c/manifest] Specify how updates work (#446) (Thursday, 17 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 17 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 17 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 17 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 17 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Wednesday, 16 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Wednesday, 16 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Wednesday, 16 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Wednesday, 16 February)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 16 February)
• Re: [w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346) (Tuesday, 15 February)
• Re: [w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346) (Tuesday, 15 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/permissions] Move permissions out to each spec (#263) (Monday, 14 February)
• Re: [w3c/permissions] Ensure "screen-wake-lock" permission is integrated in Screen Wake Lock API (or just remove it?) (Issue #319) (Monday, 14 February)
• Re: [w3c/permissions] Proposals: Drop "Powerful features registry" and PermissionName enum (Issue #314) (Monday, 14 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Monday, 14 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Monday, 14 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Monday, 14 February)
• [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Friday, 11 February)
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Friday, 11 February)
• Re: [w3c/gamepad] Use * as default allowlist (PR #159) (Friday, 11 February)
• Re: [w3c/gamepad] Use * as default allowlist (PR #159) (Friday, 11 February)
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Friday, 11 February)
• [w3c/gamepad] Use * as default allowlist (PR #159) (Friday, 11 February)
• Re: [w3c/permissions] Add "popups" permission type (#210) (Thursday, 10 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Thursday, 10 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Thursday, 10 February)
• Re: [w3c/permissions] Simplify GC model (PR #360) (Wednesday, 9 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Wednesday, 9 February)
• Re: [w3c/permissions] Simplify CG model (PR #360) (Wednesday, 9 February)
• Re: [w3c/permissions] Simplify CG model (PR #360) (Wednesday, 9 February)
• Re: [w3c/permissions] Definition of PermissionStatus lifetime (#266) (Wednesday, 9 February)
• [w3c/permissions] Simplify CG model (PR #360) (Wednesday, 9 February)
• [w3c/permissions] Editorial: generalize statement about PermissionState emum (PR #359) (Wednesday, 9 February)
• Re: [w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346) (Wednesday, 9 February)
• Re: [w3c/permissions] Tidied up document using tidy-html5 (PR #358) (Wednesday, 9 February)
• Re: [w3c/permissions] Tidied up document using tidy-html5 (PR #358) (Wednesday, 9 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Wednesday, 9 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Wednesday, 9 February)
• Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351) (Wednesday, 9 February)
• Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351) (Wednesday, 9 February)
• Re: [w3c/permissions] Proposals: Drop "Powerful features registry" and PermissionName enum (Issue #314) (Wednesday, 9 February)
• Re: [w3c/permissions] Editorial: make 'Creating instances' an algorithm (PR #357) (Wednesday, 9 February)
• Re: [w3c/permissions] Editorial: make 'Creating instances' an algorithm (PR #357) (Wednesday, 9 February)
• [w3c/permissions] Editorial: make 'Creating instances' an algorithm (PR #357) (Wednesday, 9 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Monday, 7 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Monday, 7 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Monday, 7 February)
• [w3c/permissions] Further alignment with Permissions Policy (Issue #356) (Monday, 7 February)
• Re: [w3c/permissions] Rename PermissionName enum to PowerfulFeatureName (#286) (Monday, 7 February)
• Re: [w3c/permissions] Rename PermissionName enum to PowerfulFeatureName (#286) (Monday, 7 February)
• Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355) (Monday, 7 February)
• Re: [w3c/permissions] Editorial: clean up abstract (PR #345) (Monday, 7 February)
• Re: [w3c/permissions] Editorial: clean up abstract (PR #345) (Monday, 7 February)
• Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351) (Monday, 7 February)
• Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351) (Monday, 7 February)
• Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351) (Monday, 7 February)
• Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355) (Saturday, 5 February)
• Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355) (Saturday, 5 February)
• [w3c/permissions] Editorial: cleanup Permissions model (PR #355) (Friday, 4 February)
• Re: [w3c/permissions] Add concept of Default Permission State (PR #354) (Friday, 4 February)
• Re: [w3c/permissions] Add concept of Default Permission State (PR #354) (Friday, 4 February)
• [w3c/permissions] Add concept of Default Permission State (PR #354) (Friday, 4 February)
• [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Friday, 4 February)
• [w3c/permissions] Editorial: run 'in parallel', not asynchronously (PR #352) (Friday, 4 February)
• [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351) (Friday, 4 February)
• [w3c/permissions] Editorial: cleanup examples (PR #350) (Friday, 4 February)
• [w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346) (Friday, 4 February)
• [w3c/permissions] Editorial: clean up abstract (PR #345) (Friday, 4 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 3 February)
• Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344) (Wednesday, 2 February)
• Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344) (Wednesday, 2 February)
• Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344) (Wednesday, 2 February)
• Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344) (Wednesday, 2 February)
• Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344) (Wednesday, 2 February)
• [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344) (Wednesday, 2 February)

Marijn Kruisselbrink

• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Tuesday, 8 February)
• Re: [whatwg/storage] Add 'obtain a storage key for non-storage purposes' (PR #132) (Tuesday, 8 February)
• Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131) (Tuesday, 8 February)

Masayuki Nakano

• Re: [w3c/editing] EditContext: Are the events for `EditContext` propagated in the DOM tree? (#341) (Monday, 7 February)

Mason Freed

• Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849) (Monday, 28 February)

Matt Reynolds

• Re: [w3ctag/design-reviews] Gamepad API input events (#662) (Wednesday, 16 February)
• Re: [w3c/gamepad] getGamepad() check if doc is fully active (PR #157) (Friday, 11 February)
• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Tuesday, 1 February)

Mattias Buelens

• Re: [whatwg/streams] Returning buffers to the underlying source (Issue #1217) (Thursday, 10 February)
• Re: [whatwg/streams] Add tests for interaction between autoAllocateChunkSize and respondWithNewView (PR #1216) (Wednesday, 9 February)
• [whatwg/streams] Add tests for interaction between autoAllocateChunkSize and respondWithNewView (PR #1216) (Tuesday, 8 February)
• Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214) (Wednesday, 2 February)
• Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214) (Tuesday, 1 February)
• Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214) (Tuesday, 1 February)
• Re: [whatwg/streams] Use `(ArrayBufferView or undefined)` for ReadableStreamBYOBReadResult (PR #1214) (Tuesday, 1 February)
• Re: [whatwg/webidl] An undefined dictionary member in IDL->JS conversion: exist or not? (Issue #1094) (Tuesday, 1 February)

Max Waterman

• Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813) (Tuesday, 22 February)
• Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813) (Tuesday, 22 February)
• Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813) (Tuesday, 22 February)

mbrodesser

• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 21 February)
• Re: [w3c/clipboard-apis] `ClipboardItem` constructor should throw when `items` are empty (Issue #169) (Tuesday, 15 February)
• [w3c/clipboard-apis] `ClipboardItem` constructor should throw when `items` is empty (Issue #169) (Monday, 14 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 7 February)
• Re: [w3c/clipboard-apis] Should `clipboard.writeText()` replace `\n` characters with `\r\n` on Windows? (Issue #168) (Friday, 4 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 4 February)
• Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166) (Thursday, 3 February)
• [w3c/clipboard-apis] Should `clipboard.writeText()` replace `\n` characters with `\r\n` on Windows? (Issue #168) (Thursday, 3 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 2 February)
• Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166) (Wednesday, 2 February)
• Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166) (Wednesday, 2 February)

MD ABUL HOSSAIN

• Re: [w3c/manifest] Link to manifest-app-info in the README (Issue #1027) (Wednesday, 2 February)
• Re: [w3c/manifest] Link to manifest-app-info in the README (Issue #1027) (Wednesday, 2 February)

Michael McCool

• [w3ctag/design-reviews] WIP: Web of Things (WoT) Thing Description 1.1 - Security Review (Issue #715) (Monday, 14 February)

Michael[tm] Smith

• Re: [whatwg/streams] Review Draft Publication: February 2022 (PR #1219) (Tuesday, 22 February)
• Re: [whatwg/streams] Review Draft Publication: February 2022 (PR #1219) (Tuesday, 22 February)

Mike Taylor

• Re: [w3c/permissions] Safari returns different results for current permission state (#278) (Monday, 28 February)
• Re: [w3c/permissions] Safari returns different results for current permission state (#278) (Friday, 25 February)
• Re: [w3c/permissions] Editorial: clarify Permissions Policy / Powerful Feature overlap (PR #367) (Thursday, 24 February)
• Re: [w3c/permissions] Specifications should add conformance classes (#283) (Thursday, 24 February)
• Re: [w3c/permissions] Editorial: add UA + spec conformance classes (PR #368) (Thursday, 24 February)
• Re: [w3c/permissions] Editorial: add UA + spec conformance classes (PR #368) (Thursday, 24 February)
• Re: [w3c/permissions] Handle non-fully-active documents (PR #365) (Thursday, 24 February)
• Re: [w3c/permissions] Handle non-fully-active documents (#162) (Thursday, 24 February)
• Re: [w3c/permissions] Handle non-fully-active documents (PR #365) (Thursday, 24 February)
• Re: [w3c/permissions] Handle non-fully-active documents (PR #365) (Thursday, 24 February)
• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Friday, 18 February)
• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Wednesday, 16 February)
• Re: [w3c/permissions] Editorial: Add linking-text for "specifies a powerful feature" (PR #363) (Tuesday, 15 February)
• Re: [w3c/permissions] Editorial: Add linking-text for "specifies a powerful feature" (PR #363) (Tuesday, 15 February)
• [w3c/permissions] Editorial: Add linking-text for "specifies a powerful feature" (PR #363) (Tuesday, 15 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Monday, 14 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/permissions] Add requirements for specifying Powerful Features (PR #362) (Monday, 14 February)
• Re: [w3c/permissions] Simplify GC model (PR #360) (Wednesday, 9 February)
• Re: [w3c/permissions] Definition of PermissionStatus lifetime (#266) (Wednesday, 9 February)
• Re: [w3c/permissions] Simplify GC model (PR #360) (Wednesday, 9 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Wednesday, 9 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Wednesday, 9 February)
• Re: [w3c/permissions] Editorial: generalize statement about PermissionState emum (PR #359) (Wednesday, 9 February)
• Re: [w3c/permissions] Editorial: generalize statement about PermissionState emum (PR #359) (Wednesday, 9 February)
• Re: [w3c/permissions] Editorial: make 'Creating instances' an algorithm (PR #357) (Wednesday, 9 February)
• Re: [w3c/permissions] Editorial: make 'Creating instances' an algorithm (PR #357) (Wednesday, 9 February)
• Re: [w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346) (Wednesday, 9 February)
• Re: [w3c/permissions] Editorial: bring back Automated Testing into spec (PR #346) (Wednesday, 9 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Monday, 7 February)
• Re: [w3c/permissions] Add a fourth permission state "grantable without a prompt"? (#250) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: cleanup Permissions model (PR #355) (Friday, 4 February)
• Re: [w3c/permissions] Add concept of Default Permission State (PR #354) (Friday, 4 February)
• Re: [w3c/permissions] Add concept of Default Permission State (PR #354) (Friday, 4 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Friday, 4 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Friday, 4 February)
• Re: [w3c/permissions] Switch PermissionName to DOMString (PR #353) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: run 'in parallel', not asynchronously (PR #352) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: run 'in parallel', not asynchronously (PR #352) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: clean up Relationship to Permissions Policy (PR #351) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: cleanup examples (PR #350) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: cleanup examples (PR #350) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: cleanup examples (PR #350) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: cleanup examples (PR #350) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: cleanup examples (PR #350) (Friday, 4 February)
• Re: [w3c/permissions] Editorial: clean up abstract (PR #345) (Friday, 4 February)
• Re: [w3c/permissions] Split Pri/Sec considerations + give user control over features (PR #344) (Wednesday, 2 February)

Mitar

• Re: [whatwg/fetch] HTTP/2 server push support (#51) (Tuesday, 22 February)
• Re: [whatwg/fetch] HTTP/2 server push support (#51) (Tuesday, 22 February)

Monday David S.

• Re: [w3c/manifest] Allow unique start_url for subdomains (#470) (Tuesday, 22 February)

Ms2ger

• Re: [whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055) (Monday, 7 February)

Nat McCully

• Re: [w3c/editing] Expose keyboard language? (#351) (Monday, 7 February)

Nick Williams

• Re: [WICG/webcomponents] RfC: API design for aria delegation mechanism (#917) (Wednesday, 9 February)

Nikolay Latyshev

• [w3c/ServiceWorker] Service Worker as secure storage and provider for access token and refresh token (Issue #1626) (Thursday, 17 February)

Noam Rosenthal

• Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406) (Monday, 28 February)
• Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406) (Monday, 28 February)
• Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406) (Monday, 28 February)
• Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406) (Monday, 28 February)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 28 February)
• Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406) (Monday, 28 February)
• [whatwg/fetch] Add server-timing to timing info struct (PR #1406) (Sunday, 27 February)
• Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Wednesday, 23 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Monday, 14 February)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 14 February)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 14 February)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 14 February)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 14 February)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 14 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Monday, 14 February)
• [whatwg/fetch] Check if fetch record's "fetch" instance needs to be nullable (Issue #1403) (Monday, 14 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Monday, 14 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Monday, 14 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Monday, 14 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Sunday, 13 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Sunday, 13 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Sunday, 13 February)
• Re: [whatwg/fetch] Define the "memory cache" (Issue #1400) (Friday, 11 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 11 February)
• Re: [whatwg/fetch] Define the "memory cache" (Issue #1400) (Friday, 11 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 11 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 11 February)
• Re: [whatwg/fetch] Integrate early hints https://tools.ietf.org/html/rfc8297 (#1225) (Thursday, 10 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Thursday, 10 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Thursday, 10 February)
• Re: [whatwg/fetch] Integrate early hints https://tools.ietf.org/html/rfc8297 (#1225) (Thursday, 10 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Wednesday, 9 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Wednesday, 9 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Wednesday, 9 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Wednesday, 9 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Wednesday, 9 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Wednesday, 9 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Wednesday, 9 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Tuesday, 8 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Tuesday, 8 February)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 7 February)

Patrick Meenan

• Re: [w3ctag/design-reviews] Priority Hints API (Issue #704) (Monday, 28 February)
• Re: [w3ctag/design-reviews] Priority Hints API (Issue #704) (Tuesday, 15 February)
• Re: [w3ctag/design-reviews] Priority Hints API (Issue #704) (Tuesday, 15 February)
• Re: [w3ctag/design-reviews] Priority Hints API (Issue #704) (Wednesday, 2 February)
• Re: [w3ctag/design-reviews] Priority Hints API (Issue #704) (Wednesday, 2 February)

Paul Hawxby

• Re: [whatwg/url] Support relative URLs (#531) (Thursday, 3 February)

Paul Libbrecht

• [w3c/editing] clarifications for the pickling design proposal (Issue #393) (Friday, 18 February)
• Re: [w3c/clipboard-apis] supported type should include MathML types (#141) (Wednesday, 2 February)

Peter Linss

• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Monday, 21 February)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Thursday, 10 February)
• Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696) (Thursday, 10 February)
• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Thursday, 10 February)
• Re: [w3ctag/design-reviews] Modification of selection APIs to account for shadow dom (Issue #694) (Tuesday, 8 February)
• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Wednesday, 2 February)

Qing An

• Re: [w3ctag/design-reviews] Web App Launch Handler (Issue #683) (Wednesday, 23 February)
• Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523) (Tuesday, 8 February)

Rakina Zata Amni

• Re: [w3c/ServiceWorker] How does ServiceWorker interact with non-"fully active" documents? (#1594) (Tuesday, 15 February)

Razielrelinquish

• [whatwg/webidl] Expoes (Issue #1102) (Monday, 14 February)

Razvan Grigore

• Re: [w3c/gamepad] Vibrate feature for Gamepad (#19) (Tuesday, 1 February)

Reilly Grant

• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 16 February)
• Re: [whatwg/streams] Returning buffers to the underlying source (Issue #1217) (Thursday, 10 February)
• [whatwg/streams] Returning buffers to the underlying source (Issue #1217) (Thursday, 10 February)
• Re: [whatwg/streams] Add WritableStream's signal definition for other specs (PR #1215) (Thursday, 3 February)

rektide

• Re: [whatwg/fetch] HTTP/2 headers (#1316) (Sunday, 20 February)
• Re: [whatwg/fetch] HTTP/2 server push support (#51) (Sunday, 20 February)

Rossen Atanassov

• Re: [w3ctag/design-reviews] Scroll-linked Animations (#521) (Tuesday, 15 February)
• Re: [w3ctag/design-reviews] Scroll-linked Animations (#521) (Tuesday, 15 February)

Ryan Powell

• Re: [w3c/ServiceWorker] The Cache objects do not expire unless authors *or users* delete the entries. (#1276) (Friday, 25 February)

Sam Boylett

• Re: [whatwg/dom] Disconnect single target instead of all (#126) (Thursday, 24 February)

Samuel Bronson

• Re: [whatwg/dom] Consider specifying document.evaluate and document.createNSResolver (#67) (Sunday, 27 February)

sartang

• [w3ctag/design-reviews] Review request for Confirmation of Action API (Issue #713) (Wednesday, 2 February)

Scott Haseley

• [whatwg/dom] Limit AbortSignal.timeout to Window and Worker (PR #1055) (Friday, 4 February)
• [whatwg/dom] Should AbortSignal.timeout only be exposed on (Window, Worker)? (Issue #1054) (Thursday, 3 February)

scottaohara

• Re: [w3ctag/design-reviews] <search> HTML element (Issue #714) (Wednesday, 9 February)

Seokho Song

• Re: [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708) (Tuesday, 8 February)

Sharidan Lenued

• Re: [whatwg/dom] Model -> View (DOM el) reactivity (Issue #1049) (Tuesday, 1 February)

Shiino Yuki

• Re: [whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107) (Monday, 28 February)
• Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097) (Tuesday, 8 February)
• Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097) (Tuesday, 8 February)
• Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097) (Tuesday, 8 February)

Simon Chan

• [whatwg/streams] How to create a transformed WritableStream that waits for close? (Issue #1222) (Thursday, 24 February)
• Re: [whatwg/streams] 'Splitter' stream? (#1030) (Thursday, 17 February)

snianu

• Re: [w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170) (Wednesday, 23 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Tuesday, 22 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Tuesday, 22 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 16 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 16 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 16 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 16 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 16 February)
• Re: [w3c/editing] Add explainer for custom format read/write. (PR #392) (Wednesday, 16 February)
• Re: [w3c/editing] Add explainer for custom format read/write. (PR #392) (Wednesday, 16 February)
• [w3c/editing] Add explainer for custom format read/write. (PR #392) (Wednesday, 16 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Tuesday, 15 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 15 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 15 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 15 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 15 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 15 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 15 February)
• Re: [w3c/clipboard-apis] `ClipboardItem` constructor should throw when `items` are empty (Issue #169) (Monday, 14 February)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Thursday, 10 February)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Monday, 7 February)
• Re: [w3c/clipboard-apis] Clipboard Pickling: should the unsanitized option support a way to ask for all representations to be unsanitized? (Issue #167) (Monday, 7 February)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Friday, 4 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 4 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 4 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 4 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 4 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 4 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 4 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 4 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 4 February)
• Re: [w3c/clipboard-apis] Clipboard Pickling: should the unsanitized option support a way to ask for all representations to be unsanitized? (Issue #167) (Friday, 4 February)
• Re: [w3c/clipboard-apis] Should `clipboard.writeText()` replace `\n` characters with `\r\n` on Windows? (Issue #168) (Thursday, 3 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Thursday, 3 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 2 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 2 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 2 February)
• Re: [w3c/clipboard-apis] supported type should include MathML types (#141) (Wednesday, 2 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 1 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 1 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 1 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 1 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 1 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 1 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 1 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 1 February)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 1 February)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Tuesday, 1 February)

sspi

• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Monday, 21 February)

Tab Atkins Jr.

• [whatwg/webidl] Add self to acks (PR #1110) (Monday, 28 February)
• [w3c/clipboard-apis] [meta] Fix broken markup (PR #171) (Thursday, 24 February)
• Re: [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708) (Tuesday, 8 February)

Thomas Allmer

• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 8 February)

Thomas Steiner

• Re: [w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170) (Wednesday, 16 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 16 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 16 February)
• [w3c/clipboard-apis] Feature detection for supported clipboard formats (Issue #170) (Wednesday, 16 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Wednesday, 16 February)
• Re: [w3c/permissions] Semantic Permission Bundles (#191) (Tuesday, 8 February)
• Re: [w3c/permissions] Semantic Permission Bundles (#191) (Friday, 4 February)

Titouan Rigoudy

• Re: [whatwg/fetch] Should 0.0.0.0 always be a network error? (#1117) (Thursday, 24 February)

toastal

• Re: [w3c/manifest] Why is purpose a "unordered set of unique space-separated tokens"? (#903) (Friday, 4 February)

Tom Schuster

• Re: [whatwg/webidl] Should DOMException.[[Prototype]] be %Error%? (Issue #1107) (Saturday, 26 February)

Travis Leithead

• Re: [w3c/editing] Update meeting invite link (PR #391) (Friday, 11 February)
• Re: [w3c/editing] Update meeting invite link (PR #391) (Friday, 11 February)
• Re: [w3c/editing] Updating video conferencing link to Jitsi (PR #389) (Thursday, 10 February)
• Re: [w3c/editing] Updating video conferencing link to Jitsi (PR #389) (Thursday, 10 February)
• [w3c/editing] Add Feb 10 minutes (PR #390) (Thursday, 10 February)

Val

• Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384) (Thursday, 17 February)

Varren Jones

• [whatwg/webidl] Video (Issue #1108) (Friday, 25 February)

Veit Kunz

• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Monday, 14 February)

venmathiraj S

• Re: [w3ctag/design-reviews] Modification of selection APIs to account for shadow dom (Issue #694) (Thursday, 17 February)

Victor Costan

• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Tuesday, 1 February)

vinodpotru

• [w3c/ServiceWorker] when I deploy my app new version, latest version/changes not updated at the first time reload (Issue #1627) (Wednesday, 23 February)

W3C Bot

• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1032) (Thursday, 17 February)
• Re: [w3c/permissions] Tidied up document using tidy-html5 (PR #358) (Wednesday, 9 February)

WalaceProstituto

• [whatwg/dom] Walace Oliveira Branco (Issue #1056) (Tuesday, 8 February)

Wanming Lin

• [w3c/permissions] Automation: Need two more steps to handle closed browsing context and user prompts (#347) (Friday, 4 February)

Wenson Hsieh

• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Monday, 21 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Monday, 21 February)
• Re: [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Monday, 21 February)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Wednesday, 9 February)
• Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166) (Wednesday, 2 February)
• Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166) (Wednesday, 2 February)

Westbrook Johnson

• Re: [WICG/webcomponents] Place to chat about Web Components standardization (Issue #956) (Wednesday, 23 February)

Xiaocheng Hu

• Re: [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708) (Tuesday, 8 February)

Yajing Tang

• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 17 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 17 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 17 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 17 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 17 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 17 February)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Thursday, 17 February)

Yoav Weiss

• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Friday, 25 February)
• Re: [whatwg/fetch] CH processing, cross-origin redirects and service workers (#800) (Thursday, 10 February)
• Re: [whatwg/fetch] CH processing, cross-origin redirects and service workers (#800) (Thursday, 10 February)
• Re: [whatwg/fetch] Client Hints infrastructure (#1072) (Thursday, 10 February)
• Re: [whatwg/fetch] Client Hints infrastructure (#1072) (Thursday, 10 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Wednesday, 9 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Wednesday, 9 February)
• Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388) (Wednesday, 9 February)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Wednesday, 9 February)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Wednesday, 9 February)

Yonatan

• Re: [whatwg/dom] General DOM effect/Object mutation DOM effect (Issue #1049) (Tuesday, 8 February)

youennf

• [w3c/permissions] Provide guidelines or heuristics to prevent fingerprinting in case permission is denied (Issue #361) (Wednesday, 9 February)
• [w3c/permissions] Automation: "set permission" granularity (#348) (Friday, 4 February)

yulia

• Re: [whatwg/webidl] Allow static operations to have the same name as regular operations (Issue #1097) (Monday, 7 February)

Yutaka Hirano

• Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404) (Friday, 18 February)
• Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Tuesday, 8 February)
• [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Wednesday, 2 February)

Yves Lafon

• Re: [w3ctag/design-reviews] Markup based Client Hints delegation for third-party content (Issue #702) (Monday, 21 February)

zamfofex

• Re: [whatwg/url] Support relative URLs (#531) (Saturday, 12 February)
• Re: [whatwg/url] Support relative URLs (#531) (Wednesday, 9 February)
• Re: [whatwg/url] Support relative URLs (#531) (Wednesday, 9 February)

ธนายุทธ จันทร์มี

• [whatwg/webidl] ไทยพาณิชย์ (Issue #1096) (Sunday, 6 February)

‮rekcäH nitraM‮

• Re: [WICG/webcomponents] [WebDriver] Testability of web components (#771) (Monday, 14 February)

Ádám Liszkai

• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Saturday, 5 February)

Last message date: Monday, 28 February 2022 22:04:13 UTC