public-webapps-github@w3.org from November 2023 by author

0912745177

• Re: [whatwg/fetch] ls (Issue #1723) (Wednesday, 15 November)
• [whatwg/fetch] ls (Issue #1723) (Wednesday, 15 November)

09139626334

• Re: [w3c/IndexedDB] 53db883f495fc71bb5168f0e7e91561af1005b9 (Issue #414) (Thursday, 16 November)
• [w3c/IndexedDB] 53db883f495fc71bb5168f0e7e91561af1005b9 (Issue #414) (Thursday, 16 November)

7ombie

• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Tuesday, 28 November)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Tuesday, 21 November)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Tuesday, 21 November)

Aaron Gustafson

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

Adam Sobieski

• Re: [whatwg/dom] Selecting Events with Style (Issue #1233) (Wednesday, 29 November)
• Re: [whatwg/dom] Selecting Events with Style (Issue #1233) (Friday, 10 November)
• Re: [whatwg/dom] Selecting Events with Style (Issue #1233) (Thursday, 9 November)
• Re: [whatwg/dom] Selecting Events with Style (Issue #1233) (Wednesday, 8 November)
• [whatwg/dom] Selecting Events with Style (Issue #1233) (Wednesday, 8 November)

Addison Phillips

• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Wednesday, 29 November)
• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Monday, 6 November)

Alex Rudenko

• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Tuesday, 28 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Tuesday, 28 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Monday, 27 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 27 November)
• [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Monday, 27 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Friday, 17 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 15 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 9 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 8 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 7 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 7 November)

Alvin Ji

• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)
• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)

Alwin Blok

• Re: [whatwg/url] Support relative URLs (#531) (Friday, 17 November)

Amy Guy

• Re: [w3ctag/design-reviews] VC JSON Schema (Issue #859) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] Verifiable Credential Status List 2021 (Issue #874) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] VC JSON Schema (Issue #859) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] VC JSON Schema (Issue #859) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] Verifiable Credentials Data Model v2.0 (Issue #860) (Wednesday, 22 November)
• Re: [w3ctag/design-reviews] The CSS `word-break: auto-phrase` property (Issue #891) (Wednesday, 22 November)
• Re: [w3ctag/design-reviews] Tag review request for the "Dubbing and Audio description Profiles of TTML2" (Issue #897) (Monday, 13 November)
• Re: [w3ctag/design-reviews] Tag review request for the "Dubbing and Audio description Profiles of TTML2" (Issue #897) (Monday, 13 November)

Andrew Sutherland

• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Monday, 20 November)

Anne van Kesteren

• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 29 November)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Tuesday, 28 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 28 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Tuesday, 28 November)
• Re: [whatwg/dom] Corresponding attribute for clonable of ShadowRootInit? (Issue #1236) (Tuesday, 28 November)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Tuesday, 28 November)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Tuesday, 28 November)
• Re: [whatwg/fetch] CORB is blocked (Issue #1725) (Sunday, 26 November)
• Re: [whatwg/fetch] CORB is blocked (Issue #1725) (Sunday, 26 November)
• [w3c/clipboard-apis] Optional data types description seems wrong (Issue #200) (Thursday, 23 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 23 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 23 November)
• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Wednesday, 22 November)
• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Wednesday, 22 November)
• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Monday, 20 November)
• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Thursday, 16 November)
• [whatwg/webidl] Offer [[ArrayBufferDetachKey]] abstraction? (Issue #1375) (Thursday, 16 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 15 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Monday, 13 November)
• Re: [whatwg/dom] Selecting Events with Style (Issue #1233) (Thursday, 9 November)
• Re: [whatwg/dom] Selecting Events with Style (Issue #1233) (Wednesday, 8 November)
• Re: [whatwg/fetch] Deferred fetching feedback (Issue #1715) (Wednesday, 8 November)
• Re: [whatwg/fetch] Remove Authorization header upon cross-origin redirect (PR #1544) (Wednesday, 8 November)
• Re: [whatwg/fetch] Deferred fetching feedback (Issue #1715) (Wednesday, 8 November)
• Re: [whatwg/webidl] Allowing throwing an exception with a specific message (Issue #1374) (Wednesday, 8 November)
• [whatwg/webidl] Allowing throwing an exception with a specific message (Issue #1374) (Wednesday, 8 November)
• Re: [whatwg/fetch] Deferred fetching feedback (Issue #1715) (Wednesday, 8 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 8 November)
• Re: [whatwg/fetch] Editorial: clarify preflight-request headers (PR #1719) (Wednesday, 8 November)
• Re: [whatwg/fetch] Wording suggests that CORS-preflight requests systematically include an Access-Control-Request-Headers header (Issue #1717) (Wednesday, 8 November)
• Re: [whatwg/fetch] Wording suggests that CORS-preflight requests systematically include an Access-Control-Request-Headers header (Issue #1717) (Wednesday, 8 November)
• Re: [whatwg/fetch] Editorial: clarify preflight-request headers (PR #1719) (Wednesday, 8 November)
• Re: [whatwg/fetch] Editorial: clarify preflight-request headers (PR #1719) (Wednesday, 8 November)
• Re: [whatwg/fetch] Editorial: initialize a response does not have an optional argument (PR #1721) (Tuesday, 7 November)
• Re: [whatwg/fetch] Editorial: initialize a response does not have an optional argument (PR #1721) (Tuesday, 7 November)
• [whatwg/fetch] Editorial: initialize a response does not have an optional argument (PR #1721) (Tuesday, 7 November)
• Re: [whatwg/url] IdnaTestV2.json "xn--xn--a--gua.pt" test case problem (Issue #803) (Monday, 6 November)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Monday, 6 November)

Anton Maliev

• [w3ctag/design-reviews] TAG spec review of Storage Access Heuristics (Issue #919) (Wednesday, 29 November)

Ari Chivukula

• Re: [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Monday, 20 November)
• Re: [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Thursday, 16 November)
• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) (Tuesday, 14 November)
• [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Monday, 13 November)

Ashish Maurya

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

Ben Francis

• Re: [w3c/manifest] Identifier for external interpretation (Issue #1104) (Tuesday, 14 November)
• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Tuesday, 14 November)

Boris

• Re: [w3c/clipboard-apis] Add method `match` (`clipboard.match(regex)`) to check clipboard for pattern matching before reading - as it is done in iOS (Issue #199) (Wednesday, 8 November)
• [w3c/clipboard-apis] Add method `match` (`clipboard.match(regex)`) to check clipboard for pattern matching before reading - as it is done in iOS (Issue #199) (Wednesday, 8 November)

Brandon Jones

• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 28 November)

Brian Kardell

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] Spring 2021 Virtual Meeting (#911) (Thursday, 9 November)

Bruce B. Anderson

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 17 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Monday, 13 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Saturday, 11 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Saturday, 11 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Wednesday, 8 November)

Chris Harrelson

• Re: [w3ctag/design-reviews] ServiceWorker static routing API (Issue #863) (Friday, 10 November)

Christian Liebel

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

Claudia Meadows

• Re: [whatwg/url] Add `URL.from(object)` constructor? (Issue #782) (Saturday, 11 November)

cle

• [w3c/permissions] Create SECURITY.md (PR #423) (Friday, 3 November)

cstavaru

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

cynthia

• Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912) (Tuesday, 14 November)

Dan Clark

• Re: [w3c/uievents] Order of keydown relative to compositionstart (Issue #360) (Friday, 10 November)
• [w3c/uievents] Order of keydown relative to compositionstart (Issue #360) (Thursday, 9 November)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Review request for Protected Audience (Issue #723) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] CSS Spelling and Grammar Customization (Issue #913) (Wednesday, 22 November)
• Re: [w3ctag/design-reviews] CSS Spelling and Grammar Customization (Issue #913) (Wednesday, 22 November)
• Re: [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Monday, 20 November)
• Re: [w3ctag/design-reviews] Eligibility for autofill (Issue #831) (Thursday, 16 November)
• Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906) (Tuesday, 14 November)
• Re: [w3ctag/design-reviews] Intersection Observer Scroll Margin (Issue #905) (Monday, 13 November)

Daniel Baulig

• Re: [w3c/ServiceWorker] Self hosted applications (Issue #1668) (Wednesday, 1 November)

Daniel Murphy

• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Friday, 3 November)
• Re: [w3c/manifest] Identifier for external interpretation (Issue #1104) (Wednesday, 1 November)

Danny Ayers

• Re: [w3c/manifest] Identifier for external interpretation (Issue #1104) (Thursday, 2 November)
• [w3c/manifest] Identifier for external interpretation (Issue #1104) (Wednesday, 1 November)

Danny Engelman

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

Datner

• Re: [whatwg/streams] ReadableStream.prototype.arrayBuffer() (#1019) (Thursday, 9 November)

Dave Rupert

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

Dave Seidman

• Re: [w3c/uievents] Expose 'inertial scrolling state' in wheel events (#58) (Thursday, 2 November)

David Alsh

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

Domenic Denicola

• Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { min }) (#1145) (Monday, 13 November)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { min }) (#1145) (Monday, 13 November)
• Re: [whatwg/webidl] Allowing throwing an exception with a specific message (Issue #1374) (Wednesday, 8 November)
• Re: [whatwg/webidl] Allowing throwing an exception with a specific message (Issue #1374) (Wednesday, 8 November)
• Re: [whatwg/url] IdnaTestV2.json "xn--xn--a--gua.pt" test case problem (Issue #803) (Monday, 6 November)
• Re: [whatwg/url] IdnaTestV2.json "xn--xn--a--gua.pt" test case problem (Issue #803) (Sunday, 5 November)
• Re: [whatwg/url] Meta: UTS46 feedback (Issue #744) (Sunday, 5 November)
• [whatwg/url] IdnaTestV2.json "xn--xn--a--gua.pt" test case problem (Issue #803) (Sunday, 5 November)

Dominik Röttsches

• Re: [w3ctag/design-reviews] Animating font-palette (Issue #915) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] Animating font-palette (Issue #915) (Friday, 10 November)

ehsanKey

• Re: [w3c/ServiceWorker] Assets caching in browsers behaves differently between localhost and deployment (Issue #1689) (Monday, 6 November)
• Re: [w3c/ServiceWorker] Assets caching in browsers behaves differently between localhost and deployment (Issue #1689) (Monday, 6 November)

EhsanKey_

• [w3c/ServiceWorker] How can I control and manage socket events in Service Workers? (Issue #1697) (Friday, 3 November)

Emilio Cobos Álvarez

• Re: [whatwg/fullscreen] Document fullscreening vs. modal dialog (Issue #227) (Thursday, 30 November)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Tuesday, 28 November)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Tuesday, 28 November)
• Re: [whatwg/dom] Selecting Events with Style (Issue #1233) (Tuesday, 28 November)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Tuesday, 28 November)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Monday, 27 November)
• Re: [whatwg/dom] Element.attachShadow should set the declarative flag to false of an existing declarative shadow dom. (Issue #1234) (Monday, 27 November)
• Re: [whatwg/dom] Element.attachShadow should set the declarative flag to false of an existing declarative shadow dom. (Issue #1234) (Monday, 27 November)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Monday, 27 November)
• [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match (Issue #1235) (Sunday, 26 November)
• [whatwg/dom] Element.attachShadow should set the declarative flag to false of an existing declarative shadow dom. (Issue #1234) (Sunday, 26 November)

Eugene Zemtsov

• Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912) (Wednesday, 15 November)
• Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912) (Tuesday, 14 November)
• Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912) (Tuesday, 14 November)

Evan Stade

• Re: [w3c/clipboard-apis] Read Blob data for the supported formats on-demand during getType. (Issue #191) (Friday, 17 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Friday, 3 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Friday, 3 November)

fergald

• Re: [whatwg/fetch] Deferred fetching feedback (Issue #1715) (Wednesday, 8 November)

Francis McCabe

• Re: [w3ctag/design-reviews] WebAssembly JavaScript Promise Integration API (Issue #809) (Thursday, 2 November)

Frank Lemanschik

• Re: [w3c/FileAPI] Define chunk size for `ReadableStream` created by `blob::stream()` (#144) (Thursday, 9 November)

François Daoust

• Re: [w3c/manifest] Replace ref to obsoleted RFC7540 with ref to RFC9110 (PR #1106) (Monday, 27 November)
• [w3c/manifest] Replace ref to obsoleted RFC7540 with ref to RFC9110 (PR #1106) (Monday, 27 November)

Frederik Braun

• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 16 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Monday, 13 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 8 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 8 November)

fwad

• Re: [w3c/uievents] Order of keydown relative to compositionstart (Issue #360) (Thursday, 9 November)

Gabriel Brito

• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 27 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 27 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 27 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 27 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 20 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Saturday, 18 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Saturday, 18 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Saturday, 18 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Thursday, 16 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Thursday, 16 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Thursday, 16 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 14 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 14 November)
• [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 14 November)

Gabriel Corona

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Monday, 27 November)

Georges Haidar

• Re: [whatwg/fetch] More informative error types (#526) (Wednesday, 8 November)

github-actions[bot]

• [w3c/permissions] Tidied up document using tidy-html5 (PR #429) (Wednesday, 22 November)

Hadley Beeman

• Re: [w3ctag/design-reviews] Specification review request for Verifiable Credential Data Integrity (Issue #850) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] Specification review request for Verifiable Credential Data Integrity (Issue #850) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Monday, 20 November)
• Re: [w3ctag/design-reviews] Permissions Policy Reporting and Report-Only mode (Issue #909) (Monday, 20 November)
• Re: [w3ctag/design-reviews] Early Design Review: Opener Protections (Issue #916) (Thursday, 16 November)
• Re: [w3ctag/design-reviews] Web Printing API (Issue #910) (Thursday, 16 November)
• Re: [w3ctag/design-reviews] Web Printing API (Issue #910) (Monday, 13 November)

hhmhy

• [whatwg/fetch] google font family trubleshooting (Issue #1722) (Monday, 13 November)

hvanops

• Re: [w3c/pointerlock] feature request : Allow to set pointer position upon release (#61) (Monday, 6 November)

iteriani

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Monday, 13 November)

James Browning

• Re: [whatwg/url] Add `URL.from(object)` constructor? (Issue #782) (Saturday, 11 November)

James Howard

• Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49) (Wednesday, 1 November)

James M Snell

• Re: [whatwg/streams] Add ReadableStreamBYOBReader.prototype.read(view, { min }) (#1145) (Monday, 13 November)

Jared White

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

Jeffrey Yasskin

• Re: [w3ctag/design-reviews] VC JSON Schema (Issue #859) (Tuesday, 28 November)

jgraham

• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)

Jimmy Wärting

• Re: [whatwg/fetch] Consider response.throwIfNotOk() (Issue #1679) (Wednesday, 1 November)

Jochen Kühner

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

Joe Pea

• Re: [WICG/webcomponents] A better solution for ElementInternals (Issue #1036) (Thursday, 16 November)
• Re: [WICG/webcomponents] A better solution for ElementInternals (Issue #1036) (Thursday, 16 November)
• Re: [WICG/webcomponents] A better solution for ElementInternals (Issue #1036) (Thursday, 16 November)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Thursday, 16 November)
• Re: [WICG/webcomponents] How to define APIs only for custom element authors (#758) (Wednesday, 15 November)
• [WICG/webcomponents] A better solution for ElementInternals (Issue #1036) (Wednesday, 15 November)
• Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962) (Wednesday, 15 November)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 4 November)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 4 November)

Johannes Wilm

• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Tuesday, 14 November)

Jonathan

• Re: [w3c/pointerlock] feature request : Allow to set pointer position upon release (#61) (Friday, 10 November)

jub0bs

• Re: [whatwg/fetch] Wording suggests that CORS-preflight requests systematically include an Access-Control-Request-Headers header (Issue #1717) (Tuesday, 7 November)

Justin Fagnani

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 11 November)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 8 November)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 3 November)
• Re: [whatwg/fetch] Consider response.throwIfNotOk() (Issue #1679) (Wednesday, 1 November)

Kagami Sascha Rosylight

• [whatwg/dom] Corresponding attribute for clonable of ShadowRootInit? (Issue #1236) (Sunday, 26 November)
• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Wednesday, 22 November)
• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Wednesday, 22 November)
• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Wednesday, 22 November)
• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Tuesday, 21 November)
• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Monday, 20 November)
• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Sunday, 19 November)
• Re: [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Thursday, 16 November)
• [whatwg/fetch] Incremental read: Why only Uint8Array instead of BufferSource? (Issue #1724) (Thursday, 16 November)
• [whatwg/streams] read all bytes: Why only Uint8Array instead of general BufferSource? (Issue #1299) (Tuesday, 14 November)

Keith Cirkel

• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Monday, 6 November)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Sunday, 5 November)

Khaledolaywah

• Re: [whatwg/url] Meta: update repository files (aa64bb2) (Monday, 27 November)

Khalyomede

• Re: [w3c/manifest] icon density should be supported (#118) (Tuesday, 21 November)

Kim Andersen

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

Lea Verou

• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Monday, 27 November)
• Re: [w3ctag/design-reviews] Animating font-palette (Issue #915) (Monday, 27 November)
• Re: [w3ctag/design-reviews] Animating font-palette (Issue #915) (Monday, 27 November)
• Re: [w3ctag/design-reviews] View Transitions: list of types (Issue #908) (Monday, 13 November)

Luca Casonato

• Re: [whatwg/fetch] Editorial: initialize a response does not have an optional argument (PR #1721) (Tuesday, 7 November)

lukas

• [w3c/DOM-Parsing] Proposal on how to deal with <script>-blocks when appending to the DOM (Issue #76) (Sunday, 26 November)

Luke Warlow

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 4 November)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 4 November)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 3 November)

Malte Jürgens

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

Manu Sporny

• Re: [w3ctag/design-reviews] Verifiable Credential Status List 2021 (Issue #874) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] Verifiable Credentials Data Model v2.0 (Issue #860) (Tuesday, 21 November)

Marcos Cáceres

• Re: [w3c/manifest] Replace ref to obsoleted RFC7540 with ref to RFC9110 (PR #1106) (Wednesday, 29 November)
• Re: [w3c/manifest] icon density should be supported (#118) (Wednesday, 29 November)
• Re: [w3c/manifest] icon density should be supported (#118) (Wednesday, 29 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Wednesday, 29 November)
• Re: [w3c/manifest] Replace ref to obsoleted RFC7540 with ref to RFC9110 (PR #1106) (Wednesday, 29 November)
• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Wednesday, 29 November)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Wednesday, 29 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 28 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 28 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 28 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 28 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 28 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 28 November)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Friday, 24 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 21 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 21 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 20 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 20 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 20 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 20 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 20 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 20 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 20 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 20 November)
• Re: [w3c/manifest] Identifier for external interpretation (Issue #1104) (Monday, 20 November)
• Re: [w3c/manifest] Identifier for external interpretation (Issue #1104) (Monday, 20 November)
• Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039) (Monday, 20 November)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Monday, 20 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 20 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Monday, 20 November)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Monday, 20 November)
• Re: [w3c/manifest] Ability to dynamically change app icon (#663) (Monday, 20 November)
• Re: [w3c/manifest] icon density should be supported (#118) (Monday, 20 November)
• Re: [w3c/permissions] Add Permissions Registry back to main document (PR #426) (Sunday, 19 November)
• Re: [w3c/permissions] Add Permissions Registry back to main document (PR #426) (Sunday, 19 November)
• Re: [w3c/permissions] Add Permissions Registry back to main document (PR #426) (Sunday, 19 November)
• Re: [w3c/permissions] Add Permissions Registry back to main document (PR #426) (Sunday, 19 November)
• Re: [w3c/permissions] Add Permissions Registry back to main document (PR #426) (Friday, 17 November)
• Re: [w3c/manifest] Editorial: Consistent manifest naming (PR #1099) (Wednesday, 15 November)
• Re: [w3c/manifest] Editorial: Consistent manifest naming (PR #1099) (Wednesday, 15 November)
• Re: [w3c/manifest] Editorial: remove “commonly” to reflect actual JSON encoding (PR #1100) (Wednesday, 15 November)
• Re: [w3c/manifest] JSON "commonly" encoded in Unicode (Issue #1089) (Wednesday, 15 November)
• Re: [w3c/manifest] Editorial: remove “commonly” to reflect actual JSON encoding (PR #1100) (Wednesday, 15 November)
• Re: [w3c/manifest] Editorial: remove “commonly” to reflect actual JSON encoding (PR #1100) (Wednesday, 15 November)
• Re: [w3c/manifest] Editorial: remove “commonly” to reflect actual JSON encoding (PR #1100) (Wednesday, 15 November)
• Re: [w3c/manifest] Editorial: Consistent manifest naming (PR #1099) (Friday, 3 November)
• Re: [w3c/manifest] Editorial: Consistent manifest naming (PR #1099) (Friday, 3 November)
• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Friday, 3 November)
• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Friday, 3 November)
• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Friday, 3 November)
• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Friday, 3 November)
• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Friday, 3 November)

Martin Thomson

• [whatwg/fullscreen] Keyboard lock (Issue #231) (Thursday, 30 November)

Mason Freed

• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Tuesday, 28 November)
• Re: [whatwg/dom] Corresponding attribute for clonable of ShadowRootInit? (Issue #1236) (Tuesday, 28 November)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Tuesday, 28 November)
• Re: [whatwg/dom] Element.attachShadow should set the declarative flag to false of an existing declarative shadow dom. (Issue #1234) (Monday, 27 November)
• Re: [whatwg/dom] Should attachShadow throw or override when an existing declarative shadow root doesn't match? (Issue #1235) (Monday, 27 November)
• Re: [whatwg/dom] Element.attachShadow should set the declarative flag to false of an existing declarative shadow dom. (Issue #1234) (Monday, 27 November)

Matt Giuca

• Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039) (Monday, 20 November)
• Re: [w3c/manifest] icon density should be supported (#118) (Monday, 20 November)
• Re: [w3c/manifest] icon density should be supported (#118) (Monday, 20 November)
• Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039) (Thursday, 16 November)
• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Thursday, 16 November)
• Re: [w3c/manifest] [DRAFT—DO NOT MERGE/REVIEW] Add members for localization (PR #1101) (Monday, 6 November)

Matt Reynolds

• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 28 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 28 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Friday, 17 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 14 November)
• Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190) (Tuesday, 14 November)
• Re: [w3c/gamepad] Advanced gamepad haptics API (Issue #189) (Friday, 10 November)

Matthew Phillips

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Monday, 13 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Monday, 13 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 8 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Wednesday, 8 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Tuesday, 7 November)
• [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Tuesday, 7 November)

Mattias Buelens

• Re: [whatwg/streams] BYOB with "fill at least" semantics (#1175) (Monday, 13 November)
• Re: [whatwg/streams] ReadableStreamBYOBReader.prototype.readFully(view) (#1143) (Monday, 13 November)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.prototype.read(view, { min }) (#1145) (Monday, 13 November)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.prototype.read(view, { min }) (#1145) (Monday, 13 November)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { min }) (#1145) (Friday, 10 November)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { min }) (#1145) (Friday, 10 November)

meacer

• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Monday, 27 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Monday, 27 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Monday, 27 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Monday, 27 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 16 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 16 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Thursday, 16 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 15 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 15 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 15 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Monday, 13 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Monday, 13 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 8 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 8 November)
• Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655) (Wednesday, 1 November)

Mike Taylor

• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #431) (Tuesday, 28 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 28 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 28 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: add <div class="algorithm"> in missing places (PR #427) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: add <div class="algorithm"> in missing places (PR #427) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: add <div class="algorithm"> in missing places (PR #427) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: add <div class="algorithm"> in missing places (PR #427) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: add <div class="algorithm"> in missing places (PR #427) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: Tidied up document using tidy-html5 (PR #429) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: Tidied up document using tidy-html5 (PR #429) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: Replace all <a>foo</a> with [=foo=] (PR #428) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: Replace all <a>foo</a> with [=foo=] (PR #428) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 20 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 20 November)
• Re: [w3c/permissions] Add Permissions Registry back to main document (PR #426) (Friday, 17 November)
• Re: [w3c/permissions] Add Permissions Registry back to main document (PR #426) (Friday, 17 November)
• Re: [w3c/permissions] Add Permissions Registry back to main document (PR #426) (Friday, 17 November)
• Re: [w3c/permissions] Add Permissions Registry back to main document (PR #426) (Thursday, 16 November)
• [w3c/permissions] Add Permissions Registry back to main document (PR #426) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 15 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 15 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 9 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 8 November)
• Re: [w3c/permissions] Create SECURITY.md (PR #423) (Saturday, 4 November)
• Re: [w3c/permissions] Create SECURITY.md (PR #423) (Saturday, 4 November)

Ming-Ying Chung

• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 13 November)
• Re: [whatwg/fetch] Deferred fetching feedback (Issue #1715) (Thursday, 9 November)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 2 November)

Morten Stenshorne

• [w3ctag/design-reviews] @page margin boxes (Issue #918) (Thursday, 16 November)

Ms2ger

• Re: [whatwg/webidl] Add support for AsyncContext (PR #1369) (Friday, 17 November)

Munira

• [w3ctag/design-reviews] Animating font-palette (Issue #915) (Thursday, 9 November)

Nigel Megitt

• Re: [w3ctag/design-reviews] Tag review request for the "Dubbing and Audio description Profiles of TTML2" (Issue #897) (Monday, 13 November)
• Re: [w3ctag/design-reviews] Tag review request for the "Dubbing and Audio description Profiles of TTML2" (Issue #897) (Thursday, 9 November)

Nitin Pandey

• [whatwg/fetch] CORB is blocked (Issue #1725) (Sunday, 26 November)

Noam Rosenthal

• Re: [w3ctag/design-reviews] Long Animation Frame API (LoAF) (Issue #911) (Tuesday, 21 November)

Nolan Lawson

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

Norren

• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Tuesday, 21 November)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Thursday, 16 November)

Oliver Dunk

• Re: [w3c/ServiceWorker] Support `close()` method in ServiceWorkerGlobalScope (Issue #1696) (Wednesday, 1 November)

Oliver Williams

• Re: [WICG/webcomponents] update to use import attributes syntax (PR #1039) (Thursday, 23 November)
• [WICG/webcomponents] update to use import attributes syntax (PR #1039) (Wednesday, 22 November)

otabek-git

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)

papatiya

• [whatwg/webidl] 215 (Issue #1373) (Tuesday, 7 November)

Pascal Schilp

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 11 November)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 3 November)

Peter Linss

• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Thursday, 30 November)
• Re: [w3ctag/design-reviews] VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport (Issue #768) (Thursday, 30 November)

Philip Jägenstedt

• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Thursday, 30 November)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Thursday, 30 November)
• Re: [whatwg/fullscreen] Document fullscreening vs. modal dialog (Issue #227) (Thursday, 30 November)

Philipp Hancke

• Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912) (Tuesday, 14 November)
• Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912) (Thursday, 9 November)

Pierre-Anthony Lemieux

• [w3ctag/design-reviews] Adding support for High Dynamic Range (HDR) imagery to HTML Canvas (Issue #917) (Monday, 13 November)

Reilly Grant

• Re: [w3c/pointerlock] feature request : Allow to set pointer position upon release (#61) (Friday, 10 November)

Richard C Yeh

• [w3c/uievents] Disable autocomplete on tools/key-event-viewer.html (Issue #363) (Wednesday, 29 November)

Richard Gibson

• Re: [whatwg/webidl] non-readonly [FrozenArray] attributes are footguns as currently specced (#810) (Thursday, 30 November)

Rimas Misevičius

• Re: [whatwg/url] IdnaTestV2.json "xn--xn--a--gua.pt" test case problem (Issue #803) (Monday, 6 November)

Rob Eisenberg

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Thursday, 9 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Wednesday, 8 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Tuesday, 7 November)

Rossen Atanassov

• Re: [w3ctag/design-reviews] Long Animation Frame API (LoAF) (Issue #911) (Tuesday, 21 November)

Rune Lillesveen

• Re: [w3ctag/design-reviews] CSS State Container Queries (Issue #885) (Wednesday, 1 November)

Sachin Jain

• Re: [whatwg/fetch] Remove Authorization header upon cross-origin redirect (PR #1544) (Wednesday, 8 November)

Sanket Joshi

• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Monday, 20 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 18 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Friday, 17 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 16 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Wednesday, 15 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Tuesday, 14 November)
• Re: [w3c/clipboard-apis] Allow empty ClipboardItem. (PR #198) (Wednesday, 8 November)
• Re: [w3c/clipboard-apis] Make it possible to read image/svg+xml from the clipboard (#92) (Thursday, 2 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 2 November)
• Re: [w3c/editing] Remove write and add more details on read. (PR #456) (Wednesday, 1 November)

Santiago Persico

• Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Friday, 17 November)

Sara Tang

• Re: [w3ctag/design-reviews] Review request for Confirmation of Action API (Issue #713) (Wednesday, 29 November)

Sasha Firsov

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 14 November)

Shivani Sharma

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

Shu-yu Guo

• Re: [whatwg/webidl] Allowing throwing an exception with a specific message (Issue #1374) (Wednesday, 8 November)

Silas

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

Simon Pieters

• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Wednesday, 29 November)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Friday, 24 November)
• Re: [w3c/uievents] Specify the textInput event (PR #362) (Friday, 24 November)
• [w3c/uievents] Specify the textInput event (PR #362) (Friday, 24 November)
• [w3c/uievents] Cancelable/default action for keydown, composition*, beforeinput, textInput, input (Issue #361) (Thursday, 23 November)
• Re: [w3c/uievents] `beforeinput` and `compositionupdate` event order (Issue #354) (Thursday, 23 November)

sirisian

• [WICG/webcomponents] Allowing for more complex slotted styling by rewriting host rules into global CSS rules (Issue #1038) (Monday, 20 November)
• [WICG/webcomponents] Modify :is() and :where() to support selecting derived node types (Issue #1037) (Sunday, 19 November)
• Re: [w3c/pointerlock] feature request : Allow to set pointer position upon release (#61) (Friday, 10 November)

Slava Fomin II

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

smaug----

• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Thursday, 30 November)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Monday, 20 November)

snianu

• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Thursday, 30 November)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Thursday, 30 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Wednesday, 29 November)
• Re: [w3c/clipboard-apis] Optional data types description seems wrong (Issue #200) (Wednesday, 29 November)
• Re: [w3c/clipboard-apis] Read Blob data for the supported formats on-demand during getType. (Issue #191) (Tuesday, 21 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Tuesday, 21 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Tuesday, 21 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Monday, 20 November)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Monday, 20 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 18 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 18 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 18 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 18 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 18 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 18 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 18 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 18 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 18 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Saturday, 18 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 16 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 16 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 16 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 16 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 16 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 16 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 16 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 16 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Wednesday, 15 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Wednesday, 15 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Tuesday, 14 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Tuesday, 14 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Tuesday, 14 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Tuesday, 14 November)
• Re: [w3c/editing] Linked privacy security doc is for older pickling proposal? (Issue #452) (Tuesday, 14 November)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Tuesday, 14 November)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Tuesday, 14 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Friday, 10 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Friday, 10 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Friday, 10 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 9 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Thursday, 9 November)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Thursday, 9 November)
• Re: [w3c/clipboard-apis] Allow empty ClipboardItem. (PR #198) (Thursday, 9 November)
• Re: [w3c/clipboard-apis] Should reading the clipboard throw DataError or empty clipboard items? (Issue #179) (Thursday, 9 November)
• Re: [w3c/clipboard-apis] Should reading the clipboard throw DataError or empty clipboard items? (Issue #179) (Thursday, 9 November)
• Re: [w3c/clipboard-apis] Allow empty ClipboardItem. (PR #198) (Thursday, 9 November)
• Re: [w3c/clipboard-apis] Allow empty ClipboardItem. (PR #198) (Wednesday, 8 November)
• Re: [w3c/clipboard-apis] Allow empty ClipboardItem. (PR #198) (Wednesday, 8 November)
• Re: [w3c/clipboard-apis] Allow empty ClipboardItem. (PR #198) (Tuesday, 7 November)
• [w3c/clipboard-apis] Allow empty ClipboardItem. (PR #198) (Tuesday, 7 November)
• Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439) (Tuesday, 7 November)
• Re: [w3c/clipboard-apis] Should reading the clipboard throw DataError or empty clipboard items? (Issue #179) (Tuesday, 7 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Friday, 3 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Friday, 3 November)
• Re: [w3c/clipboard-apis] Add `unsanitized` option to async clipboard API. (PR #197) (Friday, 3 November)
• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Wednesday, 1 November)
• Re: [w3c/editing] Remove write and add more details on read. (PR #456) (Wednesday, 1 November)

Stephen Chenney

• Re: [w3ctag/design-reviews] CSS Spelling and Grammar Customization (Issue #913) (Monday, 6 November)
• [w3ctag/design-reviews] CSS ::selection Inheritance Model (Issue #914) (Friday, 3 November)
• [w3ctag/design-reviews] CSS Spelling and Grammar Customization (Issue #913) (Friday, 3 November)

Sumit Sahoo

• Re: [whatwg/fetch] Streaming upload (Issue #1438) (Tuesday, 28 November)

Tab Atkins Jr.

• [whatwg/url] [editorial] Rephrase encoding note to make the implications clearer. (PR #804) (Monday, 6 November)

tcaptan-cr

• Re: [w3ctag/design-reviews] Intersection Observer Scroll Margin (Issue #905) (Tuesday, 21 November)

tguild

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

Thiago Perrotta

• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Friday, 24 November)
• [w3c/permissions] Editorial: Replace all <a>foo</a> with [=foo=] (PR #428) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: add <div class="algorithm"> in missing places (PR #427) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: add <div class="algorithm"> in missing places (PR #427) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: add <div class="algorithm"> in missing places (PR #427) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: add <div class="algorithm"> in missing places (PR #427) (Wednesday, 22 November)
• Re: [w3c/permissions] Editorial: add <div class="algorithm"> in missing places (PR #427) (Wednesday, 22 November)
• [w3c/permissions] Editorial: add <div class="algorithm"> in missing places (PR #427) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 22 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 21 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Sunday, 19 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Sunday, 19 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Friday, 17 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 16 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 15 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 15 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 14 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 14 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 14 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 14 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 14 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 14 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 9 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 9 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 9 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 9 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 9 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 9 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Thursday, 9 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Wednesday, 8 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 7 November)
• Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Tuesday, 7 November)
• [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425) (Monday, 6 November)
• Re: [w3c/permissions] Umbrella / Meta: Browser Permissions for WebDriver BiDi as an extension module (Issue #424) (Monday, 6 November)
• [w3c/permissions] Umbrella / Meta: Browser Permissions for WebDriver BiDi as an extension module (Issue #424) (Monday, 6 November)

Tom Wilkinson

• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Monday, 13 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Monday, 13 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)
• Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035) (Friday, 10 November)

vmpstr

• Re: [w3ctag/design-reviews] View Transitions: list of types (Issue #908) (Monday, 13 November)

W3C Bot

• Re: [w3c/permissions] Tidied up document using tidy-html5 (PR #429) (Wednesday, 22 November)

wattroll

• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Friday, 24 November)
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Friday, 24 November)

Westbrook Johnson

• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Wednesday, 22 November)
• Re: [WICG/webcomponents] Quarterly Face to Face Scheduling (Issue #1031) (Monday, 20 November)

Xiaoqian Wu

• Re: [w3c/manifest] x (Issue #1105) (Monday, 20 November)

Yoav Weiss

• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Wednesday, 29 November)
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Tuesday, 28 November)
• Re: [w3ctag/design-reviews] Soft Navigations (Issue #879) (Thursday, 9 November)
• Re: [whatwg/fetch] Deferred fetching feedback (Issue #1715) (Wednesday, 8 November)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] Add a static routing API support. (PR #1686) (Tuesday, 28 November)
• Re: [w3c/ServiceWorker] Add a static routing API support. (PR #1686) (Friday, 17 November)
• Re: [w3c/ServiceWorker] Add a static routing API support. (PR #1686) (Friday, 17 November)

youennf

• [w3c/permissions] Can 'prompt the user to choose' return deny after some implementation specific timeout? (Issue #430) (Thursday, 23 November)

Yves Lafon

• Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875) (Monday, 20 November)
• Re: [w3ctag/design-reviews] CSS `text-spacing` property and its longhands (Issue #907) (Thursday, 16 November)
• Re: [w3ctag/design-reviews] CSS `text-spacing` property and its longhands (Issue #907) (Thursday, 16 November)

ZxSix666

• Re: [w3c/manifest] x (Issue #1105) (Monday, 20 November)
• Re: [w3c/manifest] x (Issue #1105) (Monday, 20 November)
• Re: [w3c/manifest] x (Issue #1105) (Monday, 20 November)
• [w3c/manifest] x (Issue #1105) (Monday, 20 November)

一丝

• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Sunday, 5 November)
• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Thursday, 2 November)
• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Wednesday, 1 November)

Last message date: Thursday, 30 November 2023 23:08:43 UTC