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

1cg

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Sunday, 18 February)

Adam Rice

• Re: [whatwg/streams] Add explainer for ReadableStream async iteration (PR #1306) (Tuesday, 20 February)
• Re: [whatwg/streams] Add explainer for ReadableStream async iteration (PR #1306) (Tuesday, 20 February)

Aetinx

• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Friday, 16 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 15 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 15 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 15 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Friday, 9 February)

Alex Rudenko

• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Thursday, 29 February)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Thursday, 29 February)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Thursday, 29 February)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Thursday, 22 February)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Monday, 19 February)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Monday, 12 February)

Amy Guy

• Re: [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) (Monday, 26 February)
• Re: [w3ctag/design-reviews] BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure using BBS Signatures (Issue #922) (Monday, 26 February)
• Re: [w3ctag/design-reviews] Verifiable Credential Status List 2021 (Issue #874) (Thursday, 22 February)
• Re: [w3ctag/design-reviews] Verifiable Credential Status List 2021 (Issue #874) (Thursday, 22 February)
• Re: [w3ctag/design-reviews] Verifiable Credentials Data Model v2.0 (Issue #860) (Thursday, 22 February)
• Re: [w3ctag/design-reviews] Verifiable Credentials Data Model v2.0 (Issue #860) (Thursday, 22 February)
• Re: [w3ctag/design-reviews] TAG review request for the IDP signin status API (Issue #884) (Monday, 19 February)
• Re: [w3ctag/design-reviews] FedCM multi IDP support (Issue #803) (Monday, 19 February)
• Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823) (Tuesday, 13 February)
• Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823) (Tuesday, 13 February)
• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Monday, 5 February)
• Re: [w3ctag/design-reviews] Feature detection for supported clipboard formats (Issue #901) (Monday, 5 February)
• Re: [w3ctag/design-reviews] `field-sizing` CSS property (Issue #890) (Monday, 5 February)
• Re: [w3ctag/design-reviews] `field-sizing` CSS property (Issue #890) (Monday, 5 February)

Andrea Giammarchi

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

Anne van Kesteren

• Re: [whatwg/webidl] Intent to use BigInt/numeric union in WebNN (Issue #1388) (Thursday, 29 February)
• Re: [whatwg/webidl] Intent to use BigInt/numeric union in WebNN (Issue #1388) (Thursday, 29 February)
• Re: [whatwg/webidl] Intent to use BigInt/numeric union in WebNN (Issue #1388) (Wednesday, 28 February)
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Wednesday, 28 February)
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Wednesday, 28 February)
• Re: [whatwg/dom] "connected" should be defined for all kinds of nodes (Issue #1259) (Wednesday, 28 February)
• Re: [whatwg/dom] Define 'connected' for all nodes (PR #1260) (Wednesday, 28 February)
• Re: [whatwg/dom] Define 'connected' for all nodes (PR #1260) (Wednesday, 28 February)
• Re: [whatwg/dom] "connected" should be defined for all kinds of nodes (Issue #1259) (Tuesday, 27 February)
• Re: [whatwg/dom] createEvent("textevent") creates a TextEvent (PR #1254) (Friday, 23 February)
• Re: [whatwg/dom] createEvent("textevent") creates a TextEvent (PR #1254) (Friday, 23 February)
• Re: [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Thursday, 22 February)
• Re: [whatwg/xhr] Review Draft Publication: February 2024 (PR #386) (Monday, 19 February)
• Re: [whatwg/streams] Review Draft Publication: February 2024 (PR #1305) (Monday, 19 February)
• Re: [whatwg/xhr] Review Draft Publication: February 2024 (PR #386) (Monday, 19 February)
• Re: [whatwg/xhr] Review Draft Publication: February 2024 (PR #386) (Monday, 19 February)
• Re: [whatwg/url] Review Draft Publication: February 2024 (PR #823) (Monday, 19 February)
• [whatwg/url] Review Draft Publication: February 2024 (PR #823) (Monday, 19 February)
• [whatwg/xhr] Review Draft Publication: February 2024 (PR #386) (Monday, 19 February)
• [whatwg/streams] Review Draft Publication: February 2024 (PR #1305) (Monday, 19 February)
• Re: [whatwg/webidl] Intent to use bigint/numeric union (#959) (Saturday, 17 February)
• Re: [whatwg/dom] How should `clonable` work in `cloneNode(false)`? (Issue #1249) (Friday, 16 February)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Friday, 16 February)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Friday, 16 February)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Thursday, 15 February)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Thursday, 15 February)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Thursday, 15 February)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Thursday, 15 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 14 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 14 February)
• Re: [whatwg/fetch] Editorial: Export fetch controller/serialized abort reason (PR #1736) (Tuesday, 13 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 13 February)
• Re: [w3c/permissions] Editorial: Use `object` for PermissionSetParameters.descriptor (PR #444) (Tuesday, 13 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 13 February)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Tuesday, 13 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 13 February)
• Re: [whatwg/url] Inconsistency in Handling `special-scheme-missing-following-solidus` URLs (Issue #822) (Friday, 9 February)
• Re: [whatwg/url] Inconsistency in Handling `special-scheme-missing-following-solidus` URLs (Issue #822) (Friday, 9 February)
• Re: [whatwg/url] Inconsistency in Handling `special-scheme-missing-following-solidus` URLs (Issue #822) (Friday, 9 February)
• Re: [whatwg/url] Inconsistency in Handling `special-scheme-missing-following-solidus` URLs (Issue #822) (Friday, 9 February)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Friday, 9 February)
• Re: [whatwg/webidl] Update ongoing promise in async iterator return() method (PR #1387) (Friday, 9 February)
• Re: [whatwg/dom] createEvent("textevent") creates a TextEvent (PR #1254) (Thursday, 8 February)
• Re: [whatwg/fetch] Service worker "handle fetch" seems to assume it's called in parallel (Issue #1734) (Wednesday, 7 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 6 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 6 February)
• Re: [whatwg/url] Hoist "forbidden domain code point" check into "domain to ASCII" (Issue #818) (Friday, 2 February)
• Re: [whatwg/fetch] Fetch with Flask or Microdot (Issue #1733) (Friday, 2 February)
• Re: [whatwg/fetch] Fetch with Flask or Microdot (Issue #1733) (Friday, 2 February)
• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Friday, 2 February)
• Re: [whatwg/encoding] Make encodeInto() throw when given a detached buffer (Issue #324) (Thursday, 1 February)
• [w3c/uievents] Standardize layerX/layerY on UIEvent (Issue #371) (Thursday, 1 February)
• Re: [whatwg/webidl] Added a definition of {{StringContext}} extended attribute. (#841) (Thursday, 1 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 1 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 1 February)
• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Thursday, 1 February)
• Re: [whatwg/dom] Side effects due to tree insertion or removal (script, iframe) (#808) (Thursday, 1 February)

Anssi Kostiainen

• Re: [w3ctag/design-reviews] Updated review of WebNN API (Issue #933) (Thursday, 29 February)
• Re: [w3ctag/design-reviews] DeviceOrientation Event Specification (Issue #928) (Sunday, 25 February)
• [w3ctag/design-reviews] Local Peer-to-Peer API (Issue #932) (Tuesday, 13 February)
• [w3ctag/design-reviews] DeviceOrientation Event Specification (Issue #928) (Monday, 5 February)

Ari Chivukula

• Re: [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Wednesday, 28 February)
• Re: [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Wednesday, 21 February)

Ben Lesh

• Re: [whatwg/fetch] Fetch body streams are not full duplex (#1254) (Friday, 23 February)

Benjamin M. Case

• Re: [w3ctag/design-reviews] Early design review request: IPA (Issue #823) (Tuesday, 13 February)

bockmurat

• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Wednesday, 7 February)

Brad Isbell

• Re: [w3c/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Monday, 19 February)

Brandon Zylstra

• Re: [WICG/webcomponents] Why do we really need hyphens? (#658) (Thursday, 22 February)

Brian Kardell

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Thursday, 29 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 19 February)

Bruce B. Anderson

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 22 February)
• Re: [whatwg/dom] Support for appending a cloned template adjacent to an existing element (Issue #1250) (Saturday, 3 February)
• Re: [whatwg/dom] Support for appending a cloned template adjacent to an existing element (Issue #1250) (Saturday, 3 February)
• [whatwg/dom] Support for appending a cloned template adjacent to an existing element (Issue #1250) (Saturday, 3 February)

bulk88

• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 6 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Monday, 5 February)

Camille Lamy

• Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Thursday, 8 February)

Caridy Patiño

• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Wednesday, 14 February)
• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Wednesday, 14 February)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Friday, 9 February)

Chris Harrelson

• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Tuesday, 13 February)

Chris Lilley

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

Christian Biesinger

• Re: [w3ctag/design-reviews] TAG review request for the IDP signin status API (Issue #884) (Wednesday, 21 February)

CSS Meeting Bot

• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Thursday, 8 February)
• Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Thursday, 8 February)

Daniel Adams

• Re: [w3c/gamepad] Drop SecureContext extended attrs from interfaces (PR #194) (Thursday, 22 February)
• Re: [w3c/gamepad] Drop SecureContext extended attrs from interfaces (PR #194) (Friday, 16 February)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Wednesday, 28 February)
• Re: [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Wednesday, 21 February)
• Re: [w3ctag/design-reviews] (Document Subtitle): Early review for adding a new value to the standard list of `name`s for a meta tag (Issue #819) (Monday, 19 February)
• Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Wednesday, 14 February)
• Re: [w3ctag/design-reviews] Review Request for Attribution Reporting API (Issue #724) (Monday, 12 February)
• Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523) (Monday, 12 February)
• Re: [w3ctag/design-reviews] TAG spec review of Storage Access Heuristics (Issue #919) (Friday, 9 February)
• Re: [w3ctag/design-reviews] TAG spec review of Storage Access Heuristics (Issue #919) (Friday, 9 February)
• Re: [w3ctag/design-reviews] Fullscreen Popup Windows (Issue #840) (Sunday, 4 February)

Daniel Ehrenberg

• Re: [whatwg/webidl] Add support for AsyncContext (PR #1369) (Wednesday, 21 February)

Daniel Montalvo

• [w3ctag/design-reviews] WAI-ARIA 1.3 FPWD (Issue #927) (Friday, 2 February)

Daniel Murphy

• [w3c/manifest] When generating a 'default' manifest (where there wasn't any linked), manifest_url doesn't exit (Issue #1111) (Thursday, 29 February)

dapace1977

• [w3ctag/design-reviews] Regard to phone being broken into (Issue #929) (Tuesday, 6 February)

Diego Gonzalez

• Re: [w3ctag/design-reviews] (Document Subtitle): Early review for adding a new value to the standard list of `name`s for a meta tag (Issue #819) (Monday, 19 February)
• Re: [w3ctag/design-reviews] (Document Subtitle): Early review for adding a new value to the standard list of `name`s for a meta tag (Issue #819) (Monday, 19 February)

Domenic Denicola

• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Thursday, 29 February)
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Tuesday, 27 February)
• Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737) (Thursday, 22 February)
• Re: [whatwg/fetch] Support ServiceWorker Static Routing API (PR #1737) (Thursday, 22 February)
• Re: [whatwg/webidl] Update ongoing promise in async iterator return() method (PR #1387) (Tuesday, 13 February)
• Re: [whatwg/webidl] Update ongoing promise in async iterator return() method (PR #1387) (Friday, 9 February)
• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Wednesday, 7 February)
• Re: [whatwg/fetch] Service worker "handle fetch" seems to assume it's called in parallel (Issue #1734) (Wednesday, 7 February)
• Re: [whatwg/fetch] Service worker "handle fetch" seems to assume it's called in parallel (Issue #1734) (Wednesday, 7 February)
• [whatwg/fetch] Service worker "handle fetch" seems to assume it's called in parallel (Issue #1734) (Wednesday, 7 February)
• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Wednesday, 7 February)
• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Wednesday, 7 February)
• Re: [whatwg/webidl] Added a definition of {{StringContext}} extended attribute. (#841) (Saturday, 3 February)
• Re: [whatwg/streams] Editorial: Export definition "writable stream writer" (PR #1304) (Thursday, 1 February)
• Re: [whatwg/streams] Editorial: Export definition "writable stream writer" (PR #1304) (Thursday, 1 February)

Dominic Farolino

• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Thursday, 29 February)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Thursday, 29 February)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Thursday, 29 February)
• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Thursday, 29 February)
• [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Wednesday, 28 February)
• Re: [whatwg/dom] Side effects due to tree insertion or removal (script, iframe) (#808) (Thursday, 22 February)
• [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Wednesday, 14 February)

Dominique Hazael-Massieux

• [w3ctag/design-reviews] Updated review of WebNN API (Issue #933) (Thursday, 15 February)
• Re: [WICG/webcomponents] chore: update w3c.json (d50571f) (Monday, 12 February)

Dwayne Robinson

• Re: [whatwg/webidl] Intent to use BigInt/numeric union in WebNN (Issue #1388) (Thursday, 29 February)
• Re: [whatwg/webidl] Intent to use BigInt/numeric union in WebNN (Issue #1388) (Thursday, 29 February)
• Re: [whatwg/webidl] Intent to use BigInt/numeric union in WebNN (Issue #1388) (Thursday, 29 February)
• Re: [whatwg/webidl] Intent to use bigint/numeric union (#959) (Saturday, 17 February)
• [whatwg/webidl] Intent to use BigInt/numeric union (Issue #1388) (Saturday, 17 February)
• Re: [whatwg/webidl] Intent to use bigint/numeric union (#959) (Saturday, 17 February)

Edgar Chen

• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Tuesday, 13 February)

Emmanuel Sarmiento

• Re: [whatwg/dom] Define 'connected' for all nodes (68df785) (Wednesday, 28 February)

Evan Stade

• Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Thursday, 1 February)

fergald

• Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Wednesday, 21 February)

François Beaufort

• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Wednesday, 14 February)

François Daoust

• [w3c/ServiceWorker] Update interface for install event in summary table (PR #1706) (Thursday, 22 February)
• [w3c/ServiceWorker] Flag ServiceWorkerGlobalScope as SecureContext (PR #1704) (Wednesday, 7 February)

Frederik Braun

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

Gabriel Brito

• [w3c/gamepad] Add trigger rumble effect (PR #195) (Thursday, 29 February)
• [w3ctag/design-reviews] Gamepad Trigger Rumble Extension (Issue #934) (Friday, 16 February)

Gary Kacmarcik

• Re: [w3c/uievents] Specify the textInput event (PR #362) (Wednesday, 21 February)
• Re: [w3c/uievents] Specify the `textInput` event (Issue #353) (Wednesday, 21 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Wednesday, 21 February)
• [w3c/uievents] Remove "Changes" section from spec (Issue #373) (Thursday, 8 February)
• [w3c/uievents] Remove "DOM Event Architecture" from spec (Issue #372) (Thursday, 8 February)
• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Wednesday, 7 February)

github-actions[bot]

• [w3c/permissions] Tidied up document using tidy-html5 (PR #442) (Monday, 12 February)

Greg Whitworth

• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Wednesday, 14 February)

Hadley Beeman

• Re: [w3ctag/design-reviews] requestStorageAccessFor (Issue #808) (Monday, 12 February)
• Re: [w3ctag/design-reviews] requestStorageAccessFor (Issue #808) (Monday, 12 February)

Henri Sivonen

• [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821) (Tuesday, 6 February)
• [whatwg/url] CheckHyphens isn't set to beStrict (Issue #820) (Monday, 5 February)
• [whatwg/url] Encourage denoting character-attributable errors by the REPLACEMENT CHARACTER (Issue #819) (Friday, 2 February)
• [whatwg/url] Hoist "forbidden domain code point" check into "domain to ASCII" (Issue #818) (Friday, 2 February)
• [whatwg/url] Explain why valid domain needs to run ToUnicode (Issue #817) (Friday, 2 February)
• [whatwg/url] Clearly mark conformance checking-only aspects of the IDNA section (Issue #816) (Friday, 2 February)

Hiroki Nakagawa

• [w3ctag/design-reviews] Speculation rules: target_hint field (Issue #931) (Tuesday, 13 February)

hober

• Re: [w3ctag/design-reviews] (Document Subtitle): Early review for adding a new value to the standard list of `name`s for a meta tag (Issue #819) (Monday, 19 February)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Monday, 5 February)

Isabel Leccese

• Re: [WICG/webcomponents] Measuring performance of shadow DOM (#848) (Sunday, 11 February)

James M Snell

• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Thursday, 29 February)
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Wednesday, 28 February)
• [whatwg/fetch] Fetch support for explicit resource management (Issue #1741) (Tuesday, 27 February)
• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Tuesday, 27 February)
• [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Tuesday, 27 February)

Jan-Ivar Bruaroey

• Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414) (Wednesday, 14 February)
• Re: [w3c/permissions] Add another permission state "always-ask" (from one-time grants)? (Issue #414) (Wednesday, 14 February)

jarhar

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

Jeffrey Yasskin

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

Jerry Green

• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Friday, 9 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 8 February)

Jesse Sutherland

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

Jim (JR)

• Re: [w3c/gamepad] Please don't restrict to a secure context (#145) (Thursday, 8 February)

Jochen Kühner

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

joe Jankowiak

• Re: [w3c/gamepad] Please don't restrict to a secure context (#145) (Wednesday, 7 February)

Joey Arhar

• Re: [whatwg/fullscreen] Don't close ancestor popovers when fullscreening (PR #237) (Tuesday, 6 February)

Johann Hofmann

• Re: [w3ctag/design-reviews] requestStorageAccessFor (Issue #808) (Monday, 12 February)

Johannes

• Re: [whatwg/url] Allow `[` and `]` as URL code-points (Issue #753) (Wednesday, 21 February)

John Funnell

• Re: [w3ctag/design-reviews] Web Audio API: RenderCapacity API (Issue #843) (Wednesday, 21 February)

Joshua Bell

• Re: [whatwg/webidl] Intent to use bigint/numeric union (#959) (Saturday, 17 February)

Justin Fagnani

• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Wednesday, 14 February)
• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Wednesday, 14 February)

Kagami Sascha Rosylight

• Re: [w3c/gamepad] Drop SecureContext extended attrs from interfaces (PR #194) (Tuesday, 20 February)
• Re: [w3c/push-api] Declarative Web Push (Issue #360) (Wednesday, 14 February)
• [w3c/permissions] Editorial: Use `object` for PermissionSetParameters.descriptor (PR #444) (Tuesday, 13 February)
• Re: [w3c/push-api] Declarative Web Push (Issue #360) (Tuesday, 13 February)
• [w3c/permissions] Turn PermissionSetParameters.descriptor into an object (Issue #443) (Tuesday, 13 February)
• Re: [w3c/clipboard-apis] [Async Clipboard API] Use Stream APIs to provide data during write (Issue #212) (Monday, 12 February)
• Re: [w3c/clipboard-apis] [Async Clipboard API] Use Stream APIs to provide data during write (Issue #212) (Monday, 12 February)
• Re: [w3c/clipboard-apis] [Async Clipboard API] Use Stream APIs to provide data during write (Issue #212) (Saturday, 10 February)
• Re: [w3c/clipboard-apis] [Async Clipboard API] Use Stream APIs to provide data during write (Issue #212) (Friday, 9 February)
• Re: [w3c/clipboard-apis] [Async Clipboard API] Use Stream APIs to provide data during write (Issue #212) (Friday, 9 February)
• [w3c/permissions] Editorial: Disambiguate `parameters` in Set Permission steps (PR #441) (Thursday, 8 February)
• [w3c/permissions] Disambiguate "parameters" in Set Permission steps (Issue #440) (Thursday, 8 February)
• Re: [w3c/gamepad] Please don't restrict to a secure context (#145) (Thursday, 8 February)

Karttekay Grover

• Re: [whatwg/fetch] Update Note on Request Destination / CSP directive (Issue #1466) (Saturday, 10 February)
• [whatwg/fetch] Updated csp directive with latest values (#1466) (PR #1735) (Saturday, 10 February)

Keith Cirkel

• Re: [w3ctag/design-reviews] Invokers API (Issue #920) (Monday, 26 February)

Khushal Sagar

• Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886) (Tuesday, 20 February)
• Re: [w3ctag/design-reviews] Cross-document View Transitions API (Issue #851) (Friday, 2 February)

Koji Ishii

• Re: [w3ctag/design-reviews] text-wrap: pretty (Issue #864) (Monday, 26 February)

Krzysztof Kotowicz

• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Monday, 26 February)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Monday, 26 February)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Monday, 26 February)

Lea Verou

• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Monday, 26 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 19 February)
• Re: [w3ctag/design-reviews] Observable API (Issue #902) (Tuesday, 13 February)
• Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Saturday, 10 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 10 February)
• [whatwg/dom] Improve API of `insertAdjacent*()` methods (Issue #1251) (Saturday, 3 February)

lexx9999

• Re: [w3c/ServiceWorker] Allow service workers to detect light/dark mode (#1577) (Thursday, 29 February)

Liam DeBeasi

• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) (Tuesday, 27 February)

Lingyan

• Re: [w3ctag/design-reviews] Side Panel (Issue #903) (Tuesday, 20 February)

Luis Pato

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

Luke Warlow

• Re: [w3ctag/design-reviews] Invokers API (Issue #920) (Monday, 26 February)
• Re: [w3ctag/design-reviews] Invokers API (Issue #920) (Monday, 26 February)
• Re: [w3ctag/design-reviews] Invokers API (Issue #920) (Monday, 26 February)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Monday, 26 February)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Monday, 26 February)
• Re: [whatwg/dom] Integration with trusted types inside of node conversion (PR #1258) (Monday, 26 February)
• Re: [whatwg/webidl] Added a definition of {{StringContext}} extended attribute. (#841) (Monday, 26 February)
• Re: [whatwg/webidl] Added a definition of {{StringContext}} extended attribute. (#841) (Monday, 26 February)
• Re: [whatwg/dom] Integration with trusted types inside of node conversion (PR #1258) (Monday, 26 February)
• Re: [whatwg/dom] Integration with trusted types inside of node conversion (PR #1258) (Thursday, 22 February)
• [whatwg/dom] Integration with trusted types inside of node conversion (PR #1258) (Thursday, 22 February)

Manish Goregaokar

• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Friday, 9 February)

Marcos Cáceres

• Re: [w3c/gamepad] Drop SecureContext extended attrs from interfaces (PR #194) (Thursday, 22 February)
• Re: [w3c/gamepad] Please don't restrict to a secure context (#145) (Thursday, 22 February)
• Re: [w3c/gamepad] Drop SecureContext extended attrs from interfaces (PR #194) (Thursday, 22 February)
• Re: [w3c/gamepad] Drop SecureContext extended attrs from interfaces (PR #194) (Wednesday, 21 February)
• Re: [w3c/gamepad] Drop SecureContext extended attrs from interfaces (PR #194) (Tuesday, 20 February)
• Re: [w3c/gamepad] Drop SecureContext extended attrs from interfaces (PR #194) (Friday, 16 February)
• [w3c/gamepad] Drop SecureContext extended attrs from interfaces (PR #194) (Thursday, 15 February)
• Re: [w3c/gamepad] Add `[SecureContext]` tags to the interfaces (PR #192) (Thursday, 15 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 15 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 15 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 15 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 15 February)
• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) (Thursday, 15 February)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Thursday, 15 February)
• Re: [w3c/gamepad] Support trackpad touch events / inputs (#34) (Friday, 9 February)
• Re: [w3c/gamepad] Please don't restrict to a secure context (#145) (Friday, 9 February)
• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Wednesday, 7 February)
• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Wednesday, 7 February)
• Re: [w3c/gamepad] Add `[SecureContext]` tags to the interfaces (PR #192) (Wednesday, 7 February)
• Re: [w3c/gamepad] Add `[SecureContext]` tags to the interfaces (PR #192) (Wednesday, 7 February)
• Re: [w3c/gamepad] Add `[SecureContext]` tags to the interfaces (PR #192) (Wednesday, 7 February)
• Re: [w3c/gamepad] Add `[SecureContext]` tags to the interfaces (PR #192) (Wednesday, 7 February)
• Re: [w3c/gamepad] Add `[SecureContext]` tags to the interfaces (PR #192) (Wednesday, 7 February)
• Re: [w3c/gamepad] Add `[SecureContext]` tags to the interfaces (PR #192) (Wednesday, 7 February)

Marijn Kruisselbrink

• Re: [w3c/ServiceWorker] Update interface for install event in summary table (PR #1706) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] Update interface for install event in summary table (PR #1706) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] Flag ServiceWorkerGlobalScope as SecureContext (PR #1704) (Thursday, 15 February)
• Re: [w3c/ServiceWorker] Flag ServiceWorkerGlobalScope as SecureContext (PR #1704) (Thursday, 15 February)
• Re: [w3c/ServiceWorker] Editorial: Rename both `controller` variables in Handle Fetch algorithm. (PR #1705) (Thursday, 15 February)
• [w3c/ServiceWorker] Editorial: Rename both `controller` variables in Handle Fetch algorithm. (PR #1705) (Thursday, 15 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 15 February)
• [whatwg/fetch] Editorial: Export fetch controller/serialized abort reason (PR #1736) (Monday, 12 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Saturday, 10 February)

MarleshiaM

• Re: [w3c/manifest] Adding protocol handlers (PR #1110) (Saturday, 3 February)

Martin Thomson

• Re: [w3ctag/design-reviews] Invokers API (Issue #920) (Monday, 26 February)
• Re: [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Monday, 26 February)
• Re: [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Monday, 26 February)
• Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886) (Monday, 19 February)
• Re: [w3c/editing] Delayed clipboard rendering TAG feedback (Issue #459) (Tuesday, 6 February)
• [w3c/editing] Delayed clipboard rendering TAG feedback (Issue #459) (Monday, 5 February)

Masayuki Nakano

• Re: [w3c/uievents] Specify the textInput event (PR #362) (Wednesday, 7 February)

Mason Freed

• Re: [w3ctag/design-reviews] Invokers API (Issue #920) (Wednesday, 28 February)
• [whatwg/dom] Add serializable to ShadowRoot and "attach a shadow root" (PR #1256) (Friday, 16 February)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Thursday, 15 February)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Thursday, 15 February)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Saturday, 10 February)
• [whatwg/dom] Make some ShadowRoot attributes mutable (Issue #1252) (Tuesday, 6 February)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Friday, 2 February)
• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Friday, 2 February)
• Re: [whatwg/fullscreen] Don't close ancestor popovers when fullscreening (PR #237) (Thursday, 1 February)

Matt Erbst

• Re: [w3c/IndexedDB] Rename "array key" to "composite key" (#360) (Monday, 26 February)

Matt Giuca

• Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039) (Monday, 26 February)
• Re: [w3ctag/design-reviews] Tabbed web apps (Issue #841) (Wednesday, 21 February)

Matt Reynolds

• Re: [w3c/gamepad] Add trackpad button support (Issue #191) (Thursday, 22 February)
• Re: [w3c/gamepad] Drop SecureContext extended attrs from interfaces (PR #194) (Tuesday, 20 February)
• [w3c/gamepad] Allow initializing the gamepad index to a specific value (PR #193) (Friday, 9 February)
• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Friday, 9 February)

Matthew Phillips

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 22 February)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 22 February)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 22 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 10 February)

Matthew Tylee Atkinson

• Re: [w3ctag/design-reviews] WAI-ARIA 1.3 FPWD (Issue #927) (Monday, 19 February)
• Re: [w3ctag/design-reviews] WAI-ARIA 1.3 FPWD (Issue #927) (Monday, 19 February)
• Re: [w3ctag/design-reviews] WAI-ARIA 1.3 FPWD (Issue #927) (Wednesday, 7 February)

Mattias Buelens

• Re: [whatwg/streams] Discussion: How should streams handle Explicit Resource Management (Issue #1307) (Wednesday, 28 February)
• [whatwg/streams] Add explainer for ReadableStream async iteration (PR #1306) (Monday, 19 February)
• [whatwg/webidl] Update ongoing promise in async iterator return() method (PR #1387) (Wednesday, 7 February)

Mayank

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

Merwan

• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) (Thursday, 15 February)
• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) (Wednesday, 7 February)

Michael Warren

• Re: [WICG/webcomponents] Observing slotchange mutation records: a `SlotChangeObserver` API similar to `MutationObserver` with `childList:true` (Issue #1042) (Sunday, 11 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 10 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 10 February)

Mike Taylor

• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Thursday, 29 February)
• Re: [w3c/permissions] Add userContext field to WebDriver BiDi's setPermission (PR #438) (Monday, 12 February)
• Re: [w3c/permissions] Disambiguate "parameters" in Set Permission steps (Issue #440) (Monday, 12 February)
• Re: [w3c/permissions] Editorial: Disambiguate `parameters` in Set Permission steps (PR #441) (Monday, 12 February)
• Re: [w3c/permissions] Editorial: Disambiguate `parameters` in Set Permission steps (PR #441) (Monday, 12 February)
• Re: [w3c/permissions] Editorial: Disambiguate `parameters` in Set Permission steps (PR #441) (Monday, 12 February)

Mirko Brodesser

• Re: [whatwg/dom] Integration with trusted types inside of node conversion (PR #1258) (Monday, 26 February)
• Re: [whatwg/webidl] Added a definition of {{StringContext}} extended attribute. (#841) (Monday, 26 February)
• Re: [whatwg/dom] Integration with trusted types inside of node conversion (PR #1258) (Monday, 26 February)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Monday, 26 February)

Mohamed Mansour

• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Monday, 12 February)

Ms2ger

• Re: [whatwg/webidl] Added a definition of {{StringContext}} extended attribute. (#841) (Thursday, 1 February)

Nan Lin

• Re: [w3ctag/design-reviews] Review Request for Attribution Reporting API (Issue #724) (Tuesday, 13 February)

Nathan Knowler

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

Nidhi Jaju

• [w3ctag/design-reviews] Zstandard Content-Encoding (Issue #930) (Wednesday, 7 February)

Nilesh

• Re: [WICG/webcomponents] Proposal: Allow custom elements to be in any namespace (#634) (Thursday, 15 February)

Noam Rosenthal

• Re: [whatwg/dom] Introduce DOM post-insertion steps (PR #1261) (Wednesday, 28 February)
• Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886) (Monday, 19 February)
• Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886) (Monday, 19 February)
• Re: [whatwg/fetch] Editorial: Export fetch controller/serialized abort reason (PR #1736) (Wednesday, 14 February)

npm1

• Re: [w3ctag/design-reviews] FedCM: LoginHint, UserInfo, and RPContext (Issue #839) (Tuesday, 20 February)
• Re: [w3ctag/design-reviews] FedCM multi IDP support (Issue #803) (Tuesday, 20 February)

Oliver Dunk

• Re: [whatwg/fetch] Authorization-removal change was compatibility-breaking (Issue #1631) (Tuesday, 20 February)

Onkar Ruikar

• Re: [w3c/gamepad] Add `[SecureContext]` tags to the interfaces (PR #192) (Monday, 5 February)
• [w3c/gamepad] Add `[SecureContext]` tags to the interfaces (PR #192) (Monday, 5 February)

Oxford Harrison

• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Monday, 12 February)
• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Sunday, 11 February)

PatLub85

• [whatwg/fetch] Fetch with Flask or Microdot (Issue #1733) (Friday, 2 February)

Patrick H. Lauke

• Re: [w3c/touch-events] Add constructors (219546b) (Monday, 12 February)

patrick kettner

• Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Wednesday, 7 February)
• Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Wednesday, 7 February)
• Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Tuesday, 6 February)

Patrick Meenan

• [whatwg/fetch] Add compression dictionary negotiation and decoding to the fetch processing model (Issue #1739) (Monday, 26 February)

Patrick Nelson

• Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217) (Wednesday, 28 February)

Peter Linss

• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] text-wrap: pretty (Issue #864) (Monday, 26 February)
• Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886) (Monday, 19 February)
• Re: [w3ctag/design-reviews] FedCM: LoginHint, UserInfo, and RPContext (Issue #839) (Monday, 19 February)
• Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723) (Wednesday, 14 February)
• Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723) (Wednesday, 14 February)
• Re: [w3ctag/design-reviews] Isolated Web Apps (Issue #842) (Tuesday, 13 February)
• Re: [w3ctag/design-reviews] Isolated Web Apps (Issue #842) (Tuesday, 13 February)
• Re: [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Tuesday, 13 February)
• Re: [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Tuesday, 13 February)
• Re: [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Monday, 12 February)
• Re: [w3ctag/design-reviews] Isolated Web Apps (Issue #842) (Monday, 12 February)
• Re: [w3ctag/design-reviews] Spec review for CSS Nesting (Issue #791) (Monday, 5 February)
• Re: [w3ctag/design-reviews] Spec review for CSS Nesting (Issue #791) (Monday, 5 February)

Peter Van der Beken

• Re: [whatwg/dom] Enforce same parameters for attachShadow on declarative shadow root (PR #1246) (Monday, 12 February)

Philip Chimento

• Re: [whatwg/dom] Expose AbortSignal.timeout on all globals (PR #1253) (Thursday, 29 February)
• Re: [whatwg/dom] Expose AbortSignal.timeout on all globals (PR #1253) (Thursday, 29 February)
• [whatwg/dom] Expose AbortSignal.timeout on all globals (PR #1253) (Wednesday, 7 February)

Philippe Le Hegaret

• Re: [WICG/webcomponents] chore: update w3c.json (d50571f) (Monday, 12 February)

Pierre-Anthony Lemieux

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

Pipo

• Re: [w3c/ServiceWorker] Provide a way to skipWaiting when the last tab refreshes (#1238) (Wednesday, 28 February)

polywock

• [w3c/uievents] KeyboardEvent.getKeyState() (Issue #374) (Saturday, 17 February)

RedYetiDev

• Re: [whatwg/url] Inconsistency in Handling `special-scheme-missing-following-solidus` URLs (Issue #822) (Friday, 9 February)
• Re: [whatwg/url] Inconsistency in Handling `special-scheme-missing-following-solidus` URLs (Issue #822) (Friday, 9 February)
• [whatwg/url] Inconsistency in Handling `special-scheme-missing-following-solidus` URLs (Issue #822) (Friday, 9 February)

Reilly Grant

• Re: [w3ctag/design-reviews] Isolated Web Apps (Issue #842) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] Isolated Web Apps (Issue #842) (Tuesday, 13 February)
• Re: [w3ctag/design-reviews] Isolated Web Apps (Issue #842) (Tuesday, 13 February)

Rob Eisenberg

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 22 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 10 February)

Robert Knight

• Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Thursday, 1 February)

robglidden

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Thursday, 29 February)

Ryosuke Niwa

• Re: [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Wednesday, 21 February)
• Re: [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Wednesday, 21 February)
• Re: [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Wednesday, 21 February)
• Re: [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Wednesday, 21 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 19 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 19 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 12 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 12 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 12 February)
• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Monday, 12 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Sunday, 11 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Sunday, 11 February)

Sanket Joshi

• Re: [w3ctag/design-reviews] New attribute to control UA-provided writing assistance (Issue #924) (Thursday, 15 February)

Sasha Firsov

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 22 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 19 February)
• Re: [w3ctag/design-reviews] HTML Modules (#334) (Tuesday, 6 February)

Scott Haseley

• Re: [w3c/ServiceWorker] Editorial: Rename both `controller` variables in Handle Fetch algorithm. (PR #1705) (Thursday, 15 February)
• Re: [whatwg/fetch] Editorial: Export fetch controller/serialized abort reason (PR #1736) (Tuesday, 13 February)

segfault

• Re: [WICG/webcomponents] Why do we really need hyphens? (#658) (Thursday, 22 February)

Shannon Moeller

• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Wednesday, 14 February)
• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Monday, 12 February)
• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Monday, 12 February)
• Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Sunday, 11 February)
• [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049) (Sunday, 11 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Sunday, 11 February)

Shunya Shishido

• Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737) (Thursday, 22 February)
• Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737) (Thursday, 22 February)
• Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737) (Thursday, 22 February)
• Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737) (Thursday, 22 February)
• Re: [whatwg/fetch] Support ServiceWorker Static Routing API (PR #1737) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 22 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• [whatwg/fetch] Support ServiceWorker Static Routing API (PR #1737) (Friday, 16 February)

sideshowbarker

• Re: [whatwg/streams] Review Draft Publication: February 2024 (PR #1305) (Monday, 19 February)

Silas

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

Simon Friedberger

• [whatwg/fetch] Redirect loop handling not discussed (Issue #1738) (Thursday, 22 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 14 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 14 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 13 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 13 February)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Monday, 12 February)

Simon Pieters

• [whatwg/dom] Define 'connected' for all nodes (PR #1260) (Tuesday, 27 February)
• [whatwg/dom] "connected" should be defined for all kinds of nodes (Issue #1259) (Tuesday, 27 February)
• Re: [w3c/uievents] Define events for drag-and-drop operations (textInput etc) (Issue #367) (Friday, 23 February)
• Re: [w3c/uievents] Require support for legacy events (Issue #366) (Friday, 23 February)
• Re: [whatwg/dom] createEvent("textevent") creates a TextEvent (PR #1254) (Friday, 23 February)
• Re: [whatwg/dom] createEvent("textevent") creates a TextEvent (PR #1254) (Friday, 23 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Friday, 23 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Tuesday, 20 February)
• Re: [w3c/editing] Define behavior of pressing enter in inline editing host (Issue #430) (Thursday, 15 February)
• Re: [w3c/uievents] Require support for legacy events (Issue #366) (Wednesday, 14 February)
• Re: [whatwg/dom] createEvent("textevent") creates a TextEvent (PR #1254) (Friday, 9 February)
• Re: [whatwg/dom] createEvent("textevent") creates a TextEvent (PR #1254) (Friday, 9 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 8 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 8 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 8 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 8 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 8 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Thursday, 8 February)
• Re: [whatwg/dom] createEvent("textevent") creates a TextEvent (PR #1254) (Thursday, 8 February)
• [whatwg/dom] createEvent("textevent") creates a TextEvent (PR #1254) (Thursday, 8 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Friday, 2 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Friday, 2 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Friday, 2 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Friday, 2 February)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Friday, 2 February)
• Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369) (Thursday, 1 February)

smaug----

• Re: [WICG/webcomponents] April Face-to-face Scheduling/Agenda (Issue #1050) (Monday, 19 February)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Thursday, 15 February)
• Re: [w3c/uievents] Standardize layerX/layerY on UIEvent (Issue #371) (Monday, 12 February)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Friday, 9 February)
• Re: [whatwg/dom] Draft integration with Trusted Types, take 2. (PR #1247) (Friday, 9 February)
• Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Wednesday, 7 February)
• Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Wednesday, 7 February)
• Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Wednesday, 7 February)

snianu

• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Friday, 23 February)
• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Thursday, 22 February)
• Re: [w3c/clipboard-apis] Topic: ‘unsanitized’ option to allow developers to opt-out of UA-provided sanitization (Issue #206) (Wednesday, 14 February)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Wednesday, 14 February)
• Re: [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Tuesday, 13 February)
• Re: [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Monday, 12 February)
• Re: [w3c/clipboard-apis] [Async Clipboard API] Use Stream APIs to provide data during write (Issue #212) (Monday, 12 February)
• Re: [w3c/clipboard-apis] [Async Clipboard API] Use Stream APIs to provide data during write (Issue #212) (Monday, 12 February)
• Re: [w3c/clipboard-apis] [Async Clipboard API] Use Stream APIs to provide data during write (Issue #212) (Monday, 12 February)
• Re: [w3c/clipboard-apis] [Async Clipboard API] Use Stream APIs to provide data during write (Issue #212) (Friday, 9 February)
• Re: [w3c/clipboard-apis] [Async Clipboard API] Use Stream APIs to provide data during write (Issue #212) (Friday, 9 February)
• [w3c/clipboard-apis] [Async Clipboard API] Use Stream APIs to provide data during write (Issue #212) (Friday, 9 February)
• Re: [w3ctag/design-reviews] Delayed Clipboard Rendering (Issue #925) (Thursday, 8 February)
• Re: [w3c/editing] Delayed clipboard rendering TAG feedback (Issue #459) (Thursday, 8 February)
• Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Wednesday, 7 February)
• Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Wednesday, 7 February)
• Re: [w3c/clipboard-apis] Read Blob data for the supported formats on-demand during getType. (Issue #191) (Wednesday, 7 February)
• Re: [w3c/editing] Support navigator.clipboard inside of Service Workers (Issue #458) (Tuesday, 6 February)
• Re: [w3c/editing] Delayed clipboard rendering TAG feedback (Issue #459) (Tuesday, 6 February)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Tuesday, 6 February)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Tuesday, 6 February)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Tuesday, 6 February)
• Re: [w3c/clipboard-apis] Add non-normative and optional texts. (PR #208) (Tuesday, 6 February)
• Re: [w3c/clipboard-apis] `supports` should take a dictionary instead of a DOMString as argument for readability (Issue #211) (Tuesday, 6 February)
• Re: [w3c/clipboard-apis] `supports` should take a dictionary instead of a DOMString as argument for readability (Issue #211) (Tuesday, 6 February)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Monday, 5 February)

steimelchrome

• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Tuesday, 27 February)
• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Wednesday, 14 February)
• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Wednesday, 14 February)

Steve Orvell

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

su

• Re: [whatwg/fetch] Proposal: fetch with multiple AbortSignals (#905) (Saturday, 17 February)

TAMURA, Kent

• Re: [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Wednesday, 21 February)
• Re: [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Tuesday, 6 February)

ThaWizzKidd

• Re: [w3c/touch-events] Add constructors (219546b) (Monday, 12 February)
• Re: [w3c/touch-events] Add constructors (219546b) (Monday, 12 February)
• Re: [w3c/touch-events] Add constructors (219546b) (Monday, 12 February)

Tom Schuster

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

Ur100

• Re: [whatwg/url] A '@' character in the host part of file URLs (Issue #805) (Monday, 5 February)

Valentin Gosu

• [whatwg/fetch] Reconsider default Accept values for images (Issue #1740) (Tuesday, 27 February)

Vincent Scheib

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

vmpstr

• [w3ctag/design-reviews] View Transition Classes (Issue #938) (Thursday, 22 February)
• Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886) (Tuesday, 20 February)

W3C Bot

• Re: [w3c/permissions] Tidied up document using tidy-html5 (PR #442) (Tuesday, 13 February)

Westbrook Johnson

• Re: [WICG/webcomponents] April Face-to-face Scheduling/Agenda (Issue #1050) (Monday, 26 February)
• [WICG/webcomponents] April Face-to-face Scheduling/Agenda (Issue #1050) (Friday, 16 February)

Wii

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

Yehia Mohamed

• Re: [whatwg/webidl] Update ongoing promise in async iterator return() method (400ce04) (Thursday, 22 February)

yi-gu

• [w3ctag/design-reviews] FedCM API extension: Button Mode and User Other Account API (Issue #935) (Friday, 16 February)

Yoav Weiss

• Re: [whatwg/fetch] Content codings (Content-Encoding) (#716) (Tuesday, 13 February)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 21 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 16 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 15 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 15 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 15 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Thursday, 15 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Wednesday, 14 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Tuesday, 13 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Tuesday, 13 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Tuesday, 13 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Tuesday, 13 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Friday, 9 February)
• Re: [w3c/ServiceWorker] ServiceWorker static routing API (PR #1701) (Monday, 5 February)

Yves Lafon

• Re: [w3ctag/design-reviews] Zstandard Content-Encoding (Issue #930) (Thursday, 22 February)
• Re: [w3ctag/design-reviews] Zstandard Content-Encoding (Issue #930) (Thursday, 22 February)

Zhou Shuangshuang

• Re: [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Thursday, 22 February)
• Re: [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Wednesday, 21 February)
• Re: [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Wednesday, 21 February)
• Re: [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Wednesday, 21 February)
• [w3c/selection-api] Skip posting a task for `selectionchange` event in some cases (Issue #170) (Thursday, 1 February)

一丝

• Re: [w3c/clipboard-apis] mac os doesn't recognize 'image/svg+xml' mime type (#105) (Friday, 23 February)
• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Friday, 23 February)
• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Thursday, 22 February)

Łukasz

• Re: [whatwg/fetch] Redirect loop handling not discussed (Issue #1738) (Thursday, 22 February)

Last message date: Thursday, 29 February 2024 23:36:40 UTC