public-webapps-github@w3.org from December 2021 by author

1kongpcone

• [w3ctag/design-reviews] Oenkongpc (Issue #701) (Monday, 20 December)

=JeffH

• Re: [w3c/permissions] Rename PermissionName enum to PowerfulFeatureName (#286) (Thursday, 2 December)
• Re: [w3c/permissions] Editorial: Relationship to the Permissions Policy specification (#264) (Thursday, 2 December)

Aaron Gustafson

• Re: [w3c/manifest] Feature request: access to menu bar and context menus (Issue #1025) (Thursday, 9 December)
• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Tuesday, 7 December)
• Re: [w3c/manifest] Distinction between browser and minimal-ui (Issue #1023) (Tuesday, 7 December)
• Re: [w3c/manifest] Feature request: access to menu bar and context menus (Issue #1025) (Tuesday, 7 December)

Adam Rice

• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Wednesday, 1 December)

Adrian

• Re: [WICG/webcomponents] HTML Modules (#645) (Thursday, 2 December)

alancutter

• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Monday, 13 December)
• Re: [w3ctag/design-reviews] Web App Launch Handler (Issue #683) (Friday, 10 December)

Alastair Coote

• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Monday, 20 December)
• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Monday, 13 December)

Alex Keng

• Re: [w3c/editing] EditContext: event constructors are wrong (Issue #367) (Friday, 10 December)
• Re: [w3c/editing] EditContext: should editContext be on Element? (Issue #369) (Friday, 10 December)
• Re: [w3c/editing] EditContext: how is bold represented? (Issue #368) (Friday, 10 December)
• Re: [w3c/editing] EditContext: should editContext be on Element? (Issue #369) (Friday, 10 December)
• Re: [w3c/editing] EditContext: should editContext be on Element? (Issue #369) (Friday, 10 December)
• Re: [w3c/editing] Add a link to the EditContext Spec (PR #364) (Wednesday, 1 December)
• Re: [w3c/editing] Add a link to the EditContext Spec (PR #364) (Wednesday, 1 December)

Alexis Menard

• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Wednesday, 15 December)
• Re: [w3ctag/design-reviews] Pen Events API (#553) (Wednesday, 8 December)
• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Tuesday, 7 December)

Alfredo Velasco

• [whatwg/webidl] Oops, never mind. I was thinking dot === indistinguishable rather than distinguishable. (Issue #1070) (Wednesday, 1 December)

Ali Mert Çakar

• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Monday, 13 December)

Alwin Blok

• Re: [whatwg/url] Disallow all C0 control and DEL codepoints in hosts (PR #673) (Monday, 27 December)

Amy Guy

• Re: [w3ctag/design-reviews] EPUB 3.3 (Issue #684) (Wednesday, 8 December)
• Re: [w3ctag/design-reviews] Conditional Focus (When Display-Capture Starts) (#679) (Wednesday, 8 December)
• Re: [w3ctag/design-reviews] Conditional Focus (When Display-Capture Starts) (#679) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Same-origin prerendering triggered by speculationrules (#667) (Tuesday, 7 December)

Anders Rundgren

• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Monday, 20 December)

Andreu Botella

• Re: [whatwg/fetch] Editorial: use HTML's definition of entry (PR #1364) (Thursday, 2 December)
• [whatwg/xhr] Editorial: Point the remaining entry list links to the HTML spec (PR #339) (Wednesday, 1 December)

Anne van Kesteren

• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Monday, 20 December)
• Re: [whatwg/fetch] Review Draft Publication: December 2021 (PR #1376) (Monday, 20 December)
• Re: [whatwg/encoding] Review Draft Publication: December 2021 (PR #278) (Monday, 20 December)
• Re: [whatwg/fetch] Review Draft Publication: December 2021 (PR #1376) (Monday, 20 December)
• Re: [whatwg/fetch] Meta: fix breakage due to WebSockets (PR #1377) (Monday, 20 December)
• [whatwg/fetch] Meta: fix breakage due to WebSockets (PR #1377) (Monday, 20 December)
• Re: [whatwg/dom] Review Draft Publication: December 2021 (PR #1044) (Monday, 20 December)
• [whatwg/fetch] Review Draft Publication: December 2021 (PR #1376) (Monday, 20 December)
• [whatwg/encoding] Review Draft Publication: December 2021 (PR #278) (Monday, 20 December)
• [whatwg/dom] Review Draft Publication: December 2021 (PR #1044) (Monday, 20 December)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Friday, 17 December)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Friday, 17 December)
• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Friday, 17 December)
• Re: [whatwg/xhr] Editorial: align with Fetch renaming (PR #340) (Monday, 13 December)
• Re: [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Monday, 13 December)
• [whatwg/xhr] Editorial: align with Fetch renaming (PR #340) (Monday, 13 December)
• Re: [whatwg/fetch] Rename response processing algorithms (PR #1369) (Monday, 13 December)
• Re: [whatwg/fetch] Editorial: a network error's body is always null (PR #1370) (Monday, 13 December)
• Re: [whatwg/webidl] Editorial: use cite element in IPR section (PR #1076) (Monday, 13 December)
• [whatwg/webidl] Editorial: use cite element in IPR section (PR #1076) (Monday, 13 December)
• [whatwg/fetch] Editorial: a network error's body is always null (PR #1370) (Monday, 13 December)
• [whatwg/fetch] Rename response processing algorithms (PR #1369) (Monday, 13 December)
• Re: [whatwg/fetch] Clarify which network errors create a resource timing entry (#1215) (Monday, 13 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 13 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 13 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 13 December)
• Re: [WICG/webcomponents] Upstreaming Shadow DOM and outstanding v1 work (#661) (Monday, 13 December)
• Re: [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Monday, 13 December)
• Re: [w3ctag/design-reviews] Pre-CR review: DOM Review Draft — Published 21 June 2021 (#658) (Friday, 10 December)
• Re: [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Friday, 10 December)
• Re: [w3ctag/design-reviews] Pre-CR review: DOM Review Draft — Published 21 June 2021 (#658) (Friday, 10 December)
• Re: [w3c/editing] Each specification in its own repository (Issue #374) (Friday, 10 December)
• [w3c/editing] EditContext: processing model (Issue #375) (Friday, 10 December)
• Re: [w3c/editing] EditContext: how is bold represented? (Issue #368) (Friday, 10 December)
• Re: [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Friday, 10 December)
• Re: [whatwg/dom] Encourage use of AbortError for cancellation? (#927) (Friday, 10 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [whatwg/dom] Observe changes in computed styles via MutationObserver? (Issue #1041) (Wednesday, 8 December)
• Re: [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Tuesday, 7 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Tuesday, 7 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Tuesday, 7 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Tuesday, 7 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Tuesday, 7 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Tuesday, 7 December)
• Re: [w3c/editing] EditContext: how is bold represented? (Issue #368) (Tuesday, 7 December)
• Re: [w3c/editing] Each specification in its own repository (Issue #374) (Tuesday, 7 December)
• [w3c/editing] Each specification in its own repository (Issue #374) (Monday, 6 December)
• Re: [w3c/editing] Secure context for EditContext? (#344) (Monday, 6 December)
• [w3c/editing] EditContext: define internal model (Issue #373) (Monday, 6 December)
• [w3c/editing] EditContext: "it is focusable" is underdefined (Issue #372) (Monday, 6 December)
• [w3c/editing] EditContext: "is activated" is not defined (Issue #371) (Monday, 6 December)
• [w3c/editing] EditContext: supported element list seems somewhat arbitrary (Issue #370) (Monday, 6 December)
• [w3c/editing] EditContext: should editContext be on Element? (Issue #369) (Monday, 6 December)
• [w3c/editing] EditContext: how is bold represented? (Issue #368) (Monday, 6 December)
• [w3c/editing] EditContext: event constructors are wrong (Issue #367) (Monday, 6 December)
• Re: [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Monday, 6 December)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Monday, 6 December)
• Re: [whatwg/dom] Aborting: clarify usage for non-promise APIs (PR #1040) (Monday, 6 December)
• Re: [whatwg/dom] Be clearer that not all aborting ends with an "AbortError" DOMException (#961) (Monday, 6 December)
• [whatwg/dom] Aborting: clarify usage for non-promise APIs (PR #1040) (Monday, 6 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Monday, 6 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Monday, 6 December)
• Re: [whatwg/fetch] should VARY be a cors-safelisted header? (Issue #1365) (Friday, 3 December)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Friday, 3 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Friday, 3 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 3 December)
• Re: [whatwg/dom] Consider adding document.parseURL(url) (#356) (Friday, 3 December)
• Re: [whatwg/fetch] Use structured fields for CORS headers (#1216) (Thursday, 2 December)
• Re: [whatwg/fetch] Editorial: use HTML's definition of entry (PR #1364) (Thursday, 2 December)
• Re: [whatwg/fetch] Editorial: use HTML's definition of entry (PR #1364) (Thursday, 2 December)
• [whatwg/fetch] Editorial: use HTML's definition of entry (PR #1364) (Thursday, 2 December)
• Re: [whatwg/webidl] Fix ObservableArray example (PR #1071) (Thursday, 2 December)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 2 December)
• Re: [whatwg/fetch] what is aborted flag of fetch's response really is? (Issue #1363) (Thursday, 2 December)
• Re: [whatwg/fetch] what is aborted flag of fetch's response really is? (Issue #1363) (Thursday, 2 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Thursday, 2 December)
• Re: [whatwg/fetch] what is aborted flag of fetch's response really is? (Issue #1363) (Wednesday, 1 December)
• Re: [whatwg/fetch] propagate request tainted origin flag and/or URL list through service workers (#1335) (Wednesday, 1 December)
• Re: [whatwg/fetch] Request constructor should propagate origin internal field (#1321) (Wednesday, 1 December)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Wednesday, 1 December)
• Re: [whatwg/xhr] Editorial: Point the remaining entry list links to the HTML spec (PR #339) (Wednesday, 1 December)
• Re: [whatwg/xhr] Editorial: Point the remaining entry list links to the HTML spec (PR #339) (Wednesday, 1 December)

Ari Chivukula

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

Ben Kelly

• Re: [whatwg/fetch] should VARY be a cors-safelisted header? (Issue #1365) (Friday, 3 December)
• [whatwg/fetch] should VARY be a cors-safelisted header? (Issue #1365) (Thursday, 2 December)

Benjamin Gruenbaum

• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Monday, 6 December)

Benjamin Kaiser

• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Saturday, 4 December)

Bersatu3552

• [whatwg/webidl] Intent to use Constants (Issue #1075) (Thursday, 9 December)

Bo Cupp

• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Friday, 17 December)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Friday, 17 December)
• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Friday, 17 December)
• Re: [w3c/clipboard-apis] Can`t get full html/text from clipboard (#149) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Wednesday, 15 December)
• Re: [w3ctag/design-reviews] Pen Events API (#553) (Tuesday, 14 December)

Boris Zbarsky

• Re: [whatwg/webidl] [SameObject]/[NewObject] on Promise-type attributes should be allowed (#71) (Friday, 17 December)

caoweiju

• Re: [whatwg/fetch] what is aborted flag of fetch's response really is? (Issue #1363) (Thursday, 2 December)
• [whatwg/fetch] what is aborted flag of fetch's response really is? (Issue #1363) (Wednesday, 1 December)

CapturedTruth

• [whatwg/fetch] OP Online Contract (Issue #1362) (Wednesday, 1 December)

caraitto

• Re: [w3c/editing] Clarify PII concerns in the explainer. (PR #365) (Friday, 3 December)

Catclaws12

• [whatwg/streams] Nhc (Issue #1200) (Tuesday, 21 December)

Chris Dumez

• Re: [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Friday, 10 December)

Chris Harrelson

• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Friday, 10 December)
• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Friday, 10 December)

Christian Liebel

• Re: [w3c/manifest] Feature request: access to menu bar and context menus (Issue #1025) (Wednesday, 8 December)
• Re: [w3c/manifest] <link rel="manifest" href="/messenger-manifest.json" crossorigin="use-credentials"> (Issue #1021) (Wednesday, 1 December)

Corentin Wallez

• Re: [w3ctag/design-reviews] WebGPU and WGSL (#626) (Tuesday, 7 December)

CSS Meeting Bot

• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Friday, 10 December)

cstavaru

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

cynthia

• Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696) (Monday, 20 December)
• Re: [w3ctag/design-reviews] Oenkongpc (Issue #701) (Monday, 20 December)
• Re: [w3ctag/design-reviews] WebGPU and WGSL (#626) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Handwriting Recognition API (#591) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Handwriting Recognition API (#591) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Back/Forward Cache (#628) (Monday, 6 December)
• Re: [w3ctag/design-reviews] Back/Forward Cache (#628) (Monday, 6 December)

Damian

• Re: [w3c/IndexedDB] Why is IndexedDB this bad? (Issue #369) (Monday, 20 December)
• [w3c/IndexedDB] Why is IndexedDB this bad? (Issue #369) (Sunday, 19 December)

Daniel

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

Daniel Appelquist

• Re: [w3ctag/design-reviews] renderPriority element attribute (#676) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Monday, 13 December)
• Re: [w3ctag/design-reviews] Credential Management: Conditional Mediation (Issue #692) (Thursday, 9 December)
• Re: [w3ctag/design-reviews] Distributed Tracing WG: Baggage specification (#650) (Thursday, 9 December)
• Re: [w3ctag/design-reviews] Feature policy for Keyboard API (Issue #685) (Thursday, 9 December)
• Re: [w3ctag/design-reviews] Feature policy for Keyboard API (Issue #685) (Thursday, 9 December)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Wednesday, 8 December)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Wednesday, 8 December)
• Re: [w3ctag/design-reviews] EPUB 3.3 (Issue #684) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Early design review of modal close signals/ModalCloseWatcher (#594) (Thursday, 2 December)

Daniel Munyola Luvandale

• [whatwg/encoding] whatenco-# (Issue #277) (Saturday, 11 December)

Darien Maillet Valentine

• Re: [whatwg/webidl] “Unicode character” should likely say “Unicode scalar value” in intro to lexical grammar (Issue #1080) (Tuesday, 28 December)
• [whatwg/webidl] “Unicode character” should likely say “Unicode scalar value” in intro to lexical grammar (Issue #1080) (Saturday, 25 December)
• [whatwg/webidl] Why is "unrestricted" an alternative of ArgumentNameKeyword? (Issue #1079) (Friday, 24 December)
• [whatwg/webidl] Type recursion (Issue #1078) (Saturday, 18 December)
• Re: [whatwg/webidl] [SameObject]/[NewObject] on Promise-type attributes should be allowed (#71) (Friday, 17 December)
• Re: [whatwg/webidl] [SameObject]/[NewObject] on Promise-type attributes should be allowed (#71) (Thursday, 16 December)
• Re: [whatwg/webidl] [SameObject]/[NewObject] on Promise-type attributes should be allowed (#71) (Thursday, 16 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Saturday, 4 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Thursday, 2 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Thursday, 2 December)

Dave Cramer

• Re: [w3ctag/design-reviews] EPUB 3.3 (Issue #684) (Wednesday, 8 December)

Dexter Esajas

• [w3c/ServiceWorker] How to manipulate the initial page request (which is automatically) handled by the service worker (Issue #1622) (Wednesday, 22 December)

Diego Gonzalez

• [w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695) (Monday, 6 December)

Diego Lesmes

• Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Sunday, 12 December)

Djfurb

• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Monday, 6 December)

Domenic Denicola

• Re: [whatwg/fetch] Review Draft Publication: December 2021 (PR #1376) (Monday, 20 December)
• Re: [whatwg/encoding] Review Draft Publication: December 2021 (PR #278) (Monday, 20 December)
• Re: [whatwg/dom] Review Draft Publication: December 2021 (PR #1044) (Monday, 20 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 16 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 16 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 16 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 15 December)
• Re: [whatwg/streams] Editorial: disambiguate WebSocket references (PR #1198) (Wednesday, 15 December)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Tuesday, 14 December)
• Re: [whatwg/url] Inconsistency between Chrome vs Node.js parsing (Issue #677) (Tuesday, 14 December)
• Re: [whatwg/url] Inconsistency between Chrome vs Node.js parsing (Issue #677) (Tuesday, 14 December)
• Re: [whatwg/url] Inconsistency between Chrome vs Node.js parsing (Issue #677) (Tuesday, 14 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 14 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 14 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] "FYI" Review of new window.open() behavior (Issue #691) (Tuesday, 14 December)
• Re: [whatwg/streams] Editorial: disambiguate WebSocket references (PR #1198) (Monday, 13 December)
• Re: [whatwg/streams] Editorial: disambiguate WebSocket references (PR #1198) (Monday, 13 December)
• Re: [whatwg/streams] Editorial: disambiguate WebSocket references (PR #1198) (Monday, 13 December)
• Re: [whatwg/streams] Editorial: disambiguate WebSocket references (PR #1198) (Monday, 13 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Monday, 13 December)
• Re: [whatwg/webidl] Editorial: use cite element in IPR section (PR #1076) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 9 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 9 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Wednesday, 8 December)
• Re: [whatwg/dom] Add abortController.close / abortSignal.closed (PR #1042) (Wednesday, 8 December)
• Re: [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Wednesday, 8 December)
• Re: [whatwg/dom] Aborting: clarify usage for non-promise APIs (PR #1040) (Monday, 6 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Friday, 3 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Friday, 3 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Thursday, 2 December)
• Re: [whatwg/webidl] Fix ObservableArray example (PR #1071) (Thursday, 2 December)
• Re: [whatwg/webidl] Rename LegacyNoInterfaceObject? (Issue #1072) (Wednesday, 1 December)
• Re: [whatwg/streams] Editorial: align .webidl files with WebIDL from spec text (PR #1192) (Wednesday, 1 December)
• Re: [whatwg/streams] Editorial: align .webidl files with WebIDL from spec text (PR #1192) (Wednesday, 1 December)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Wednesday, 1 December)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Wednesday, 1 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Wednesday, 1 December)
• [whatwg/webidl] Fix ObservableArray example (PR #1071) (Wednesday, 1 December)
• Re: [w3ctag/design-reviews] ObservableArray, and its use by adoptedStyleSheets (Issue #693) (Wednesday, 1 December)

Dominique Hazael-Massieux

• Re: [whatwg/webidl] IDL-level support for permission checks? (Issue #1066) (Thursday, 2 December)

Elad Alon

• Re: [w3ctag/design-reviews] Conditional Focus (When Display-Capture Starts) (#679) (Wednesday, 8 December)

Etherian

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

Evan Brass

• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Tuesday, 21 December)

fantasai

• [w3c/manifest] "Default display mode" section is super confusing (Issue #1024) (Friday, 3 December)

flachware

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

Florian Rivoal

• Re: [w3c/manifest] Transfer display-mode to mediaqueries-5 (PR #1022) (Saturday, 18 December)
• Re: [w3c/manifest] Distinction between browser and minimal-ui (Issue #1023) (Tuesday, 7 December)
• Re: [w3c/manifest] Distinction between browser and minimal-ui (Issue #1023) (Tuesday, 7 December)
• Re: [w3c/manifest] Transfer display-mode to mediaqueries-5 (PR #1022) (Monday, 6 December)
• Re: [w3c/manifest] Transfer display-mode to mediaqueries-5 (PR #1022) (Saturday, 4 December)
• Re: [w3c/manifest] "Default display mode" section is super confusing (Issue #1024) (Friday, 3 December)
• [w3c/manifest] Distinction between browser and minimal-ui (Issue #1023) (Friday, 3 December)
• [w3c/manifest] Transfer display-mode to mediaqueries-5 (PR #1022) (Friday, 3 December)

François Beaufort

• [w3ctag/design-reviews] HIDDevice forget() (Issue #703) (Monday, 27 December)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Tuesday, 14 December)

Frederik Braun

• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Thursday, 16 December)

fukang wang

• [WICG/webcomponents] why are gaps between custom-element using shadow root (Issue #947) (Thursday, 23 December)

Fuqiao Xue

• Re: [whatwg/webidl] “Unicode character” should likely say “Unicode scalar value” in intro to lexical grammar (Issue #1080) (Tuesday, 28 December)
• [w3c/manifest] Link to manifest-app-info in the README (Issue #1027) (Wednesday, 15 December)

github-actions[bot]

• [w3c/manifest] Tidied up document using tidy-html5 (PR #1028) (Saturday, 18 December)

gongph

• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Tuesday, 7 December)

Hactar

• [w3c/uievents-code] Possible typo: "Page Down" listed as key name for "End" (Issue #33) (Wednesday, 22 December)

Hadley Beeman

• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Wednesday, 8 December)

Harald Alvestrand

• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)

hober

• Re: [w3ctag/design-reviews] Web App Launch Handler (Issue #683) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Web App Launch Handler (Issue #683) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] HTMLPopupElement (#680) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] HTMLPopupElement (#680) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] HTMLPopupElement (#680) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] WebAssembly js-types API (#532) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] WebAssembly js-types API (#532) (Tuesday, 7 December)

Ian Clelland

• Re: [w3c/permissions] Hi (Issue #343) (Tuesday, 21 December)
• Re: [w3c/permissions] Hi (Issue #343) (Tuesday, 21 December)

ianbjacobs

• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Wednesday, 8 December)

Illia Klimov

• Re: [w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695) (Wednesday, 15 December)

Jakub T. Jankiewicz

• Re: [w3c/ServiceWorker] What happens with event.respondWith(Promise.reject(err))? (#150) (Sunday, 26 December)

James Browning

• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Monday, 20 December)
• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Sunday, 19 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Thursday, 2 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Thursday, 2 December)
• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Wednesday, 1 December)

James M Snell

• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Sunday, 19 December)
• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Saturday, 18 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Thursday, 16 December)
• Re: [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Friday, 10 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Thursday, 9 December)
• Re: [whatwg/dom] Add abortController.close / abortSignal.closed (PR #1042) (Thursday, 9 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Wednesday, 8 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Wednesday, 8 December)
• [whatwg/dom] Add abortController.close / abortSignal.closed (PR #1042) (Wednesday, 8 December)
• Re: [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Tuesday, 7 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Monday, 6 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Monday, 6 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Friday, 3 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Friday, 3 December)
• [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Friday, 3 December)
• Re: [whatwg/dom] Symbols should be allowed as Event types. (#331) (Friday, 3 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Friday, 3 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Thursday, 2 December)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Wednesday, 1 December)
• [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Wednesday, 1 December)
• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Wednesday, 1 December)

Jan-Ivar Bruaroey

• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 16 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Monday, 13 December)

jayr2trilly

• Re: [w3c/manifest] Adding protocolhandlers (#969) (Wednesday, 1 December)
• [w3c/manifest] <link rel="manifest" href="/messenger-manifest.json" crossorigin="use-credentials"> (Issue #1021) (Wednesday, 1 December)

Jeffrey Yasskin

• Re: [w3c/permissions] I discovered the Time Explorer badge on Google Arts & Culture! (Issue #341) (Friday, 17 December)

Jikstra

• Re: [whatwg/url] Should we unescape characters in path? (#606) (Tuesday, 28 December)

Jimmy Wärting

• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Monday, 20 December)
• [whatwg/webidl] No consistency of enumerable in the `next` method (Issue #1073) (Thursday, 2 December)

Jo (51D) Rabin

• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Monday, 13 December)

Jochen Kühner

• Re: [WICG/webcomponents] Cascading Style Sheet module scripts (#759) (Friday, 17 December)

Joey Arhar

• Re: [w3ctag/design-reviews] Beforematch event and content-visibility: hidden-matchable (#511) (Wednesday, 15 December)

Johannes Wilm

• Re: [w3c/editing] CfC: Publish "EditContext API" as a First Public Working Draft (FPWD) (Issue #366) (Tuesday, 14 December)
• Re: [w3c/editing] Link to Dec 10 minutes (PR #376) (Saturday, 11 December)
• Re: [w3c/editing] Link to Dec 10 minutes (PR #376) (Saturday, 11 December)
• Re: [w3c/editing] EditContext: how is bold represented? (Issue #368) (Friday, 10 December)
• Re: [w3c/editing] Each specification in its own repository (Issue #374) (Tuesday, 7 December)
• Re: [w3c/editing] Each specification in its own repository (Issue #374) (Monday, 6 December)
• [w3c/editing] CfC: Publish "EditContext API" as a First Public Working Draft (FPWD) (Issue #366) (Thursday, 2 December)
• Re: [w3c/editing] Add a link to the EditContext Spec (PR #364) (Wednesday, 1 December)
• Re: [w3c/editing] Add a link to the EditContext Spec (PR #364) (Wednesday, 1 December)
• Re: [w3c/editing] Add a link to the EditContext Spec (PR #364) (Wednesday, 1 December)
• Re: [w3c/editing] Add a link to the EditContext Spec (PR #364) (Wednesday, 1 December)
• [w3c/editing] Add a link to the EditContext Spec (PR #364) (Wednesday, 1 December)

Joshua Bell

• Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or FrozenArray<DOMString>)? (#235) (Wednesday, 22 December)
• Re: [w3c/IndexedDB] Why is IndexedDB this bad? (Issue #369) (Tuesday, 21 December)
• Re: [w3c/IndexedDB] Why is IndexedDB this bad? (Issue #369) (Monday, 20 December)
• Re: [w3c/IndexedDB] Why is IndexedDB this bad? (Issue #369) (Monday, 20 December)

JR Conlin

• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Monday, 20 December)
• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Monday, 20 December)
• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Monday, 20 December)

Justin Fagnani

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

Kagami Sascha Rosylight

• Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or FrozenArray<DOMString>)? (#235) (Wednesday, 22 December)
• Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or FrozenArray<DOMString>)? (#235) (Wednesday, 22 December)
• Re: [w3c/uievents] Reflect the reality for the focus event order (#290) (Thursday, 9 December)
• Re: [w3c/uievents] Reflect the reality for the focus event order (#290) (Thursday, 9 December)
• Re: [w3c/clipboard-apis] Consider renaming master branch (#131) (Sunday, 5 December)
• Re: [w3c/clipboard-apis] Consider renaming master branch (#131) (Sunday, 5 December)
• Re: [whatwg/webidl] IDL-level support for permission checks? (Issue #1066) (Thursday, 2 December)
• Re: [whatwg/webidl] Rename LegacyNoInterfaceObject? (Issue #1072) (Wednesday, 1 December)
• [whatwg/webidl] Rename LegacyNoInterfaceObject? (Issue #1072) (Wednesday, 1 December)

Kai Ninomiya

• Re: [whatwg/webidl] [SameObject]/[NewObject] on Promise-type attributes should be allowed (#71) (Thursday, 16 December)
• Re: [whatwg/webidl] [SameObject]/[NewObject] on Promise-type attributes should be allowed (#71) (Thursday, 16 December)
• [whatwg/webidl] [SameObject]/[NewObject] should be allowed on unions and other objects (Issue #1077) (Thursday, 16 December)

Kari Söderholm

• Re: [WICG/webcomponents] Upstreaming Shadow DOM and outstanding v1 work (#661) (Monday, 13 December)
• Re: [WICG/webcomponents] Upstreaming Shadow DOM and outstanding v1 work (#661) (Monday, 13 December)

Karl

• Re: [whatwg/url] Disallow all C0 control and DEL codepoints in hosts (PR #673) (Friday, 24 December)
• [whatwg/url] [Editorial] Correct the note about the IDNA fast-path for ASCII domains (PR #678) (Wednesday, 22 December)

Kenneth Rohde Christiansen

• Re: [w3ctag/design-reviews] Web App Launch Handler (Issue #683) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Web App Launch Handler (Issue #683) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Web App Launch Handler (Issue #683) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Pen Events API (#553) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Compute Pressure API (#621) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] WebGPU and WGSL (#626) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Gamepad API input events (#662) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682) (Tuesday, 7 December)

KV Pasupuleti

• Re: [w3c/ServiceWorker] consider how Client API should behave with bfcache (#1038) (Friday, 17 December)

Lea Verou

• Re: [w3ctag/design-reviews] Pre-CR review: DOM Review Draft — Published 21 June 2021 (#658) (Friday, 10 December)
• Re: [w3ctag/design-reviews] Pre-CR review: DOM Review Draft — Published 21 June 2021 (#658) (Thursday, 9 December)
• Re: [w3ctag/design-reviews] "FYI" Review of new window.open() behavior (Issue #691) (Thursday, 9 December)
• Re: [w3ctag/design-reviews] "FYI" Review of new window.open() behavior (Issue #691) (Thursday, 9 December)
• Re: [w3ctag/design-reviews] Web App Launch Handler (Issue #683) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] HTMLPopupElement (#680) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] HTMLPopupElement (#680) (Tuesday, 7 December)

Louise Brett

• Re: [w3ctag/design-reviews] Dark mode support for web apps (Issue #696) (Tuesday, 21 December)
• [w3ctag/design-reviews] Dark mode support for web apps (Issue #696) (Thursday, 9 December)

luffy2005

• Re: [whatwg/streams] Assert there are no pending reads when releasing lock (#1168) (Saturday, 11 December)

Manish Goregaokar

• [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Tuesday, 28 December)

Marco Colli

• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Monday, 20 December)
• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Monday, 20 December)

Marcos Cáceres

• Re: [w3c/permissions] Hi (Issue #343) (Wednesday, 22 December)
• Re: [w3c/permissions] Hi (Issue #342) (Tuesday, 21 December)
• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1028) (Saturday, 18 December)
• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1028) (Saturday, 18 December)
• Re: [w3c/manifest] Transfer display-mode to mediaqueries-5 (PR #1022) (Saturday, 18 December)
• Re: [w3c/manifest] Update tidyconfig.txt (PR #1026) (Saturday, 18 December)
• Re: [w3c/manifest] "Default display mode" section is super confusing (Issue #1024) (Wednesday, 8 December)
• Re: [w3c/permissions] Editorial: Relocate more powerful features. (PR #335) (Tuesday, 7 December)
• Re: [w3c/permissions] Editorial: relocate "background-fetch", "display-capture", "xr" (PR #334) (Tuesday, 7 December)
• Re: [w3c/permissions] Editorial: relocate "background-fetch", "display-capture", "xr" (PR #334) (Tuesday, 7 December)
• Re: [w3c/manifest] Distinction between browser and minimal-ui (Issue #1023) (Tuesday, 7 December)
• Re: [w3c/manifest] Distinction between browser and minimal-ui (Issue #1023) (Tuesday, 7 December)
• Re: [w3c/manifest] Distinction between browser and minimal-ui (Issue #1023) (Tuesday, 7 December)
• Re: [w3c/manifest] Distinction between browser and minimal-ui (Issue #1023) (Tuesday, 7 December)
• Re: [w3c/manifest] Distinction between browser and minimal-ui (Issue #1023) (Tuesday, 7 December)
• Re: [w3c/manifest] Transfer display-mode to mediaqueries-5 (PR #1022) (Tuesday, 7 December)
• Re: [w3c/manifest] Transfer display-mode to mediaqueries-5 (PR #1022) (Tuesday, 7 December)
• Re: [w3c/manifest] Distinction between browser and minimal-ui (Issue #1023) (Tuesday, 7 December)
• Re: [w3c/manifest] Distinction between browser and minimal-ui (Issue #1023) (Tuesday, 7 December)

Masayuki Nakano

• Re: [w3c/editing] EditContext: Are the events for `EditContext` propagated in the DOM tree? (#341) (Monday, 13 December)
• [w3c/editing] "Squiggle" should be "Wavy" as a value of underlineStyle of TextFormat (Issue #382) (Monday, 13 December)
• Re: [w3c/editing] When EditContext.updateSelection is called with offset between a surrogate pair, what should happen? (Issue #381) (Monday, 13 December)
• [w3c/editing] When EditContext.updateSelection is called with offset between a surrogate pair, what should happen? (Issue #381) (Monday, 13 December)
• [w3c/editing] EditContext has compositionRange(Start|End) but TextUpdateEvent has composition(Start|End) (Issue #380) (Monday, 13 December)
• [w3c/editing] Shuold the methods of EditContext throw an exception if they abort due to not activated? (Issue #379) (Monday, 13 December)
• [w3c/editing] It might help to write clearer code, if EditContext would have some attributes (Issue #378) (Monday, 13 December)
• [w3c/editing] EditContext.isInComposition should be renamed to `isComposing` (Issue #377) (Monday, 13 December)

Mason Freed

• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] "FYI" Review of new window.open() behavior (Issue #691) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] "FYI" Review of new window.open() behavior (Issue #691) (Tuesday, 14 December)
• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Friday, 10 December)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Tuesday, 7 December)
• [w3ctag/design-reviews] Modification of selection APIs to account for shadow dom (Issue #694) (Friday, 3 December)
• [w3ctag/design-reviews] ObservableArray, and its use by adoptedStyleSheets (Issue #693) (Wednesday, 1 December)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Wednesday, 1 December)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Wednesday, 1 December)

Matt Giuca

• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Thursday, 30 December)
• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Friday, 3 December)

Matt Reynolds

• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Wednesday, 29 December)

Mattias Buelens

• Re: [whatwg/streams] `SetUpTransformStreamDefaultControllerFromTransformer` doesn't ensure that `transformAlgorithm` and `flushAlgorithm` return `Promise` (Issue #1201) (Sunday, 26 December)
• Re: [whatwg/streams] WritableStreamDefaultController uses AbortSignal on Worklet where it isn't exposed (Issue #1199) (Friday, 17 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 16 December)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Thursday, 16 December)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Wednesday, 15 December)
• Re: [whatwg/streams] Assert there are no pending reads when releasing lock (#1168) (Wednesday, 15 December)
• Re: [whatwg/streams] Editorial: disambiguate WebSocket references (PR #1198) (Tuesday, 14 December)
• Re: [whatwg/streams] Editorial: disambiguate WebSocket references (PR #1198) (Monday, 13 December)
• Re: [whatwg/streams] Editorial: disambiguate WebSocket references (PR #1198) (Monday, 13 December)
• [whatwg/streams] Editorial: disambiguate WebSocket references (PR #1198) (Monday, 13 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Thursday, 9 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Thursday, 9 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Wednesday, 8 December)
• Re: [whatwg/dom] Add abortController.close / abortSignal.closed (PR #1042) (Wednesday, 8 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Monday, 6 December)
• Re: [whatwg/dom] AbortController.prototype.timeout and AbortController.prototype.cancel (Issue #1039) (Monday, 6 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Wednesday, 1 December)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Wednesday, 1 December)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Wednesday, 1 December)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Wednesday, 1 December)
• [whatwg/streams] Editorial: align .webidl files with WebIDL from spec text (PR #1192) (Wednesday, 1 December)

mbrodesser

• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 17 December)
• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Friday, 17 December)
• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Friday, 17 December)
• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Thursday, 16 December)
• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Thursday, 16 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 16 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 14 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 14 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 14 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 14 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 14 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 10 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 10 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 10 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 9 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 9 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 7 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 7 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 7 December)

Mguiteria

• Re: [w3c/IndexedDB] Update the web-platform-tests URL (#241) (a86ca88) (Thursday, 16 December)

Mike Taylor

• Re: [w3c/permissions] Hi (Issue #343) (Tuesday, 21 December)
• Re: [w3c/permissions] I discovered the Chromecast badge on Google Arts & Culture! (Issue #337) (Tuesday, 14 December)
• Re: [w3c/permissions] I discovered the Chromecast badge on Google Arts & Culture! (Issue #337) (Tuesday, 14 December)
• Re: [w3c/permissions] I discovered the Pet Portraits badge on Google Arts & Culture! (Issue #338) (Tuesday, 14 December)
• Re: [w3c/permissions] I discovered the Pet Portraits badge on Google Arts & Culture! (Issue #338) (Tuesday, 14 December)
• Re: [w3c/permissions] I discovered the Pocket Gallery badge on Google Arts & Culture! (Issue #339) (Tuesday, 14 December)
• Re: [w3c/permissions] I discovered the Pocket Gallery badge on Google Arts & Culture! (Issue #339) (Tuesday, 14 December)
• Re: [w3c/permissions] I discovered the Know it all badge on Google Arts & Culture! (Issue #340) (Tuesday, 14 December)
• Re: [w3c/permissions] I discovered the Know it all badge on Google Arts & Culture! (Issue #340) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640) (Monday, 13 December)
• [w3c/permissions] Editorial: relocate nfc powerful feature. (PR #336) (Friday, 10 December)
• Re: [w3c/permissions] Ensure "nfc" is integrated into parent spec (Issue #328) (Friday, 10 December)
• Re: [w3c/permissions] Ensure "nfc" is integrated into parent spec (Issue #328) (Friday, 10 December)
• Re: [w3c/permissions] Editorial: Relocate more powerful features. (PR #335) (Tuesday, 7 December)
• [w3c/permissions] Editorial: Relocate more powerful features. (PR #335) (Friday, 3 December)
• Re: [w3c/permissions] Ensure "accelerometer" is integrated into parent spec (#296) (Friday, 3 December)
• Re: [w3c/permissions] Ensure "accelerometer" is integrated into parent spec (#296) (Friday, 3 December)
• Re: [w3c/permissions] Ensure "gyroscope" is integrated into Gyroscope API (Issue #321) (Friday, 3 December)
• Re: [w3c/permissions] Ensure "gyroscope" is integrated into Gyroscope API (Issue #321) (Friday, 3 December)
• Re: [w3c/permissions] Ensure "camera" & "microphone" are defined in their parent spec (Issue #323) (Friday, 3 December)
• Re: [w3c/permissions] Ensure "camera" & "microphone" are defined in their parent spec (Issue #323) (Friday, 3 December)
• Re: [w3c/permissions] Ensure "magnetometer" is integrated into parent spec (Issue #326) (Friday, 3 December)
• Re: [w3c/permissions] Ensure "magnetometer" is integrated into parent spec (Issue #326) (Friday, 3 December)

Ms2ger

• Re: [whatwg/dom] Expose events/aborts everywhere (#1024) (Tuesday, 21 December)
• Re: [w3ctag/design-reviews] WebAssembly js-types API (#532) (Wednesday, 8 December)
• Re: [whatwg/dom] Expose events/aborts everywhere (#1024) (Thursday, 2 December)

Nina Satragno

• Re: [w3ctag/design-reviews] Credential Management: Conditional Mediation (Issue #692) (Thursday, 9 December)

Noam Rosenthal

• Re: [whatwg/fetch] Integration with preload (PR #1342) (Thursday, 16 December)
• Re: [w3c/ServiceWorker] Pass controller from fetch, and abort SW fetch when it's canceled (PR #1620) (Tuesday, 14 December)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Tuesday, 14 December)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Tuesday, 14 December)
• Re: [whatwg/xhr] Editorial: align with Fetch renaming (PR #340) (Monday, 13 December)
• Re: [whatwg/fetch] Rename response processing algorithms (PR #1369) (Monday, 13 December)
• Re: [whatwg/fetch] Editorial: a network error's body is always null (PR #1370) (Monday, 13 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 13 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 13 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 13 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 13 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 13 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Tuesday, 7 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Tuesday, 7 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Tuesday, 7 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Tuesday, 7 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Tuesday, 7 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Tuesday, 7 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Tuesday, 7 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Tuesday, 7 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Tuesday, 7 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Friday, 3 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 3 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 3 December)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Friday, 3 December)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Wednesday, 1 December)

Owen Buckley

• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Tuesday, 14 December)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Wednesday, 1 December)

Patrick Meenan

• [w3ctag/design-reviews] Priority Hints API (Issue #704) (Monday, 27 December)

Peter Linss

• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] "FYI" Review of new window.open() behavior (Issue #691) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Monday, 13 December)

Qinglin Song

• Re: [w3c/manifest] Feature request: access to menu bar and context menus (Issue #1025) (Thursday, 9 December)
• Re: [w3c/manifest] Feature request: access to menu bar and context menus (Issue #1025) (Tuesday, 7 December)
• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Saturday, 4 December)
• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Friday, 3 December)

ralyodio

• Re: [whatwg/fetch] Why does Fetch specify a max redirect count of 20? (#576) (Monday, 6 December)

Reilly Grant

• Re: [w3c/permissions] Interaction between browser and system permissions (Issue #332) (Friday, 3 December)

Rossen Atanassov

• Re: [w3ctag/design-reviews] User Preference Media Features Client Hints Headers (#632) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] User Preference Media Features Client Hints Headers (#632) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] Scroll-linked Animations (#521) (Monday, 13 December)
• Re: [w3ctag/design-reviews] Capability Delegation (#655) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] Capability Delegation (#655) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] WebTransport review request (#669) (Tuesday, 7 December)
• Re: [w3ctag/design-reviews] WebTransport review request (#669) (Tuesday, 7 December)

Ryosuke Niwa

• Re: [WICG/webcomponents] why are gaps between custom-element using shadow root (Issue #947) (Thursday, 23 December)
• Re: [WICG/webcomponents] why are gaps between custom-element using shadow root (Issue #947) (Thursday, 23 December)
• Re: [WICG/webcomponents] `customElements.upgrade` does not upgrade node subtrees cloned from `template` contents via `cloneNode` (Issue #946) (Wednesday, 22 December)
• Re: [WICG/webcomponents] `customElements.upgrade` does not upgrade node subtrees cloned from `template` contents via `cloneNode` (Issue #946) (Wednesday, 22 December)
• Re: [WICG/webcomponents] `customElements.upgrade` does not upgrade node subtrees cloned from `template` contents via `cloneNode` (Issue #946) (Wednesday, 22 December)

Sangeeth Sudheer

• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Friday, 17 December)
• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Friday, 17 December)

Sasha Firsov

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

Sean Bannister

• Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626) (Sunday, 26 December)

serna0888

• [whatwg/webidl] Nnn (Issue #1074) (Saturday, 4 December)

shehi

• Re: [w3c/push-api] Firing `pushsubscriptionchange` when permission is regranted (#236) (Tuesday, 28 December)

Simon Fraser

• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Friday, 10 December)
• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Friday, 10 December)

smaug----

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

snianu

• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Monday, 20 December)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Friday, 17 December)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Wednesday, 15 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 14 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 13 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 9 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 9 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/editing] Clarify PII concerns in the explainer. (PR #365) (Wednesday, 8 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 8 December)
• Re: [w3c/editing] Clarify PII concerns in the explainer. (PR #365) (Friday, 3 December)
• Re: [w3c/editing] Clarify PII concerns in the explainer. (PR #365) (Friday, 3 December)
• Re: [w3c/editing] Clarify PII concerns in the explainer. (PR #365) (Friday, 3 December)
• Re: [w3c/editing] Clarify PII concerns in the explainer. (PR #365) (Thursday, 2 December)
• [w3c/editing] Clarify PII concerns in the explainer. (PR #365) (Thursday, 2 December)
• Re: [w3c/editing] Add a link to the EditContext Spec (PR #364) (Wednesday, 1 December)

Surma

• Re: [whatwg/dom] Observe changes in computed styles via MutationObserver? (Issue #1041) (Wednesday, 8 December)
• Re: [whatwg/dom] Observe changes in computed styles via MutationObserver? (Issue #1041) (Wednesday, 8 December)
• [whatwg/dom] Observe changes in computed styles via MutationObserver? (Issue #1041) (Tuesday, 7 December)

Thomas Steiner

• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Tuesday, 14 December)
• Re: [w3ctag/design-reviews] User Preference Media Features Client Hints Headers (#632) (Tuesday, 14 December)
• Re: [w3c/manifest] Feature request: access to menu bar and context menus (Issue #1025) (Wednesday, 8 December)

Till Schneidereit

• Re: [whatwg/streams] `SetUpTransformStreamDefaultControllerFromTransformer` doesn't ensure that `transformAlgorithm` and `flushAlgorithm` return `Promise` (Issue #1201) (Sunday, 26 December)
• Re: [whatwg/streams] `SetUpTransformStreamDefaultControllerFromTransformer` doesn't ensure that `transformAlgorithm` and `flushAlgorithm` return `Promise` (Issue #1201) (Sunday, 26 December)
• [whatwg/streams] `SetUpTransformStreamDefaultControllerFromTransformer` doesn't ensure that `transformAlgorithm` and `flushAlgorithm` return `Promise` (Issue #1201) (Sunday, 26 December)

Timothy Gu

• Re: [whatwg/url] [Editorial] Correct the note about the IDNA fast-path for ASCII domains (PR #678) (Thursday, 23 December)
• Re: [whatwg/webidl] No consistency of enumerable in the `next` method (Issue #1073) (Friday, 3 December)

Titieom11

• [w3c/permissions] Hi (Issue #343) (Monday, 20 December)
• [w3c/permissions] Hi (Issue #342) (Monday, 20 December)
• [w3c/permissions] I discovered the Time Explorer badge on Google Arts & Culture! (Issue #341) (Friday, 17 December)
• [w3c/permissions] I discovered the Know it all badge on Google Arts & Culture! (Issue #340) (Tuesday, 14 December)
• [w3c/permissions] I discovered the Pocket Gallery badge on Google Arts & Culture! (Issue #339) (Tuesday, 14 December)
• [w3c/permissions] I discovered the Pet Portraits badge on Google Arts & Culture! (Issue #338) (Tuesday, 14 December)
• [w3c/permissions] I discovered the Chromecast badge on Google Arts & Culture! (Issue #337) (Tuesday, 14 December)
• Re: [w3c/permissions] Editorial: relocate nfc powerful feature. (PR #336) (Saturday, 11 December)

Tobie Langel

• Re: [whatwg/streams] Editorial: disambiguate WebSocket references (PR #1198) (Monday, 13 December)

Tom Schuster

• [whatwg/streams] WritableStreamDefaultController uses AbortSignal on Worklet where it isn't exposed (Issue #1199) (Friday, 17 December)

Travis Leithead

• Re: [w3c/editing] CfC: Publish "EditContext API" as a First Public Working Draft (FPWD) (Issue #366) (Friday, 10 December)
• [w3c/editing] Link to Dec 10 minutes (PR #376) (Friday, 10 December)
• Re: [w3c/editing] Add a link to the EditContext Spec (PR #364) (Friday, 3 December)
• Re: [w3c/editing] Add a link to the EditContext Spec (PR #364) (Friday, 3 December)
• Re: [w3c/editing] CfC: Publish "EditContext API" as a First Public Working Draft (FPWD) (Issue #366) (Friday, 3 December)

Tristan Fraipont

• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Friday, 17 December)

UnrealUUId

• [w3c/manifest] Update tidyconfig.txt (PR #1026) (Friday, 10 December)

Vladimir Gorej

• Re: [whatwg/url] Inconsistency between Chrome vs Node.js parsing (Issue #677) (Wednesday, 15 December)
• [whatwg/url] Inconsistency between Chrome vs Node.js parsing (Issue #677) (Tuesday, 14 December)

vmpstr

• Re: [w3ctag/design-reviews] renderPriority element attribute (#676) (Saturday, 18 December)

W3C Bot

• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1028) (Saturday, 18 December)

Wendy Seltzer

• Re: [w3c/manifest] Transfer display-mode to mediaqueries-5 (PR #1022) (Monday, 6 December)

Westbrook Johnson

• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Thursday, 30 December)
• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Thursday, 30 December)

Will Cassella

• [w3ctag/design-reviews] Review Request for adding video- prefixed media features (Issue #697) (Thursday, 9 December)

Xiaoqian Wu

• Re: [w3c/editing] Each specification in its own repository (Issue #374) (Monday, 20 December)
• Re: [w3c/editing] CfC: Publish "EditContext API" as a First Public Working Draft (FPWD) (Issue #366) (Tuesday, 14 December)

youennf

• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 16 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 15 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Wednesday, 8 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Friday, 3 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Friday, 3 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• Re: [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)
• [whatwg/streams] Explainer for proposed stream changes related to VideoFrame processing (PR #1193) (Thursday, 2 December)

Yutaka Hirano

• Re: [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Monday, 13 December)
• Re: [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Monday, 13 December)
• Re: [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Friday, 10 December)
• Re: [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Friday, 10 December)
• Re: [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Friday, 10 December)
• Re: [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Friday, 10 December)
• Re: [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Tuesday, 7 December)
• [whatwg/fetch] Remove "WebSocket protocol alterations" (PR #1366) (Tuesday, 7 December)

Yves Lafon

• Re: [w3ctag/design-reviews] Private Network Access (aka CORS-RFC1918) (#572) (Thursday, 9 December)
• Re: [w3ctag/design-reviews] Private Network Access (aka CORS-RFC1918) (#572) (Thursday, 9 December)

zbyte-king

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

zenoneczek

• [whatwg/fetch] https://player.pl/programy-online/superwizjer-odcinki,337/odcinek-1229,S04E1229,199407 (Issue #1367) (Tuesday, 7 December)

狒狒神

• Re: [WICG/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Monday, 20 December)

Last message date: Thursday, 30 December 2021 19:41:20 UTC