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

Ahmad Saleem

• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Saturday, 13 December)

Alex Rudenko

• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Wednesday, 10 December)
• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Wednesday, 10 December)

Alice

• [WICG/webcomponents] Reference Target: feedback from developers (Issue #1120) (Friday, 19 December)

Andrew Williams

• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Monday, 1 December)
• Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Monday, 1 December)
• Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Monday, 1 December)

Angelwoolridge

• [whatwg/webidl] DOMException name proposal (Issue #1552) (Monday, 8 December)

Anne van Kesteren

• Re: [whatwg/encoding] ISO-2022-JP does not reset state when returning error (Issue #358) (Sunday, 21 December)
• [whatwg/encoding] ISO-2022-JP does not reset state when returning error (Issue #358) (Sunday, 21 December)
• Re: [whatwg/fetch] Editorial: fix typo (PR #1900) (Friday, 19 December)
• Re: [whatwg/fetch] Editorial: fix typo (PR #1900) (Friday, 19 December)
• Re: [whatwg/fetch] Add "text" destination type, for JavaScript text imports (PR #1898) (Thursday, 18 December)
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Thursday, 18 December)
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Thursday, 18 December)
• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Thursday, 18 December)
• Re: [whatwg/dom] Implementations do not match spec behavior for .adoptNode(attr) (Issue #1440) (Tuesday, 16 December)
• Re: [whatwg/dom] [meta] MutationObserver improvements tracking issue (Issue #1439) (Tuesday, 16 December)
• Re: [whatwg/dom] downloads.download() should be appear in the API (Issue #1438) (Tuesday, 16 December)
• Re: [whatwg/dom] downloads.download() should be appear in the API (Issue #1438) (Tuesday, 16 December)
• Re: [whatwg/dom] Consider adding localNameFilter to MutationObserver (#398) (Tuesday, 16 December)
• Re: [whatwg/dom] [meta] MutationObserver improvements tracking issue (Issue #1439) (Tuesday, 16 December)
• Re: [w3c/FileAPI] "package data" reuses type variable (#124) (Tuesday, 16 December)
• Re: [whatwg/dom] Implementations do not match spec behavior for .adoptNode(attr) (Issue #1440) (Monday, 15 December)
• Re: [whatwg/fetch] Review Draft Publication: December 2025 (PR #1897) (Monday, 15 December)
• Re: [whatwg/dom] Review Draft Publication: December 2025 (PR #1441) (Monday, 15 December)
• Re: [whatwg/fetch] Review Draft Publication: December 2025 (PR #1897) (Monday, 15 December)
• Re: [whatwg/dom] Review Draft Publication: December 2025 (PR #1441) (Monday, 15 December)
• [whatwg/fetch] Review Draft Publication: December 2025 (PR #1897) (Monday, 15 December)
• [whatwg/dom] Review Draft Publication: December 2025 (PR #1441) (Monday, 15 December)
• Re: [whatwg/fetch] Lowercasing of scheme in URL in conflict with WPT test for CORS check (Issue #1895) (Thursday, 11 December)
• Re: [whatwg/fetch] Lowercasing of scheme in URL in conflict with WPT test for CORS check (Issue #1895) (Thursday, 11 December)
• Re: [w3c/clipboard-apis] `ClipboardItem`: clarify mime parsing (Issue #242) (Thursday, 11 December)
• Re: [whatwg/fetch] Lowercasing of scheme in URL in conflict with WPT test for CORS check (Issue #1895) (Wednesday, 10 December)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Tuesday, 9 December)
• Re: [w3c/push-api] check and consume user activation (PR #348) (Monday, 8 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Monday, 8 December)
• Re: [whatwg/dom] Add PlainTextRange interface (PR #1404) (Monday, 8 December)
• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Monday, 8 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Friday, 5 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Friday, 5 December)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Thursday, 4 December)
• Re: [whatwg/fetch] Update and rename .pr-preview.json to .pr-preview.json. (#1267) (Thursday, 4 December)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Thursday, 4 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Thursday, 4 December)
• Re: [w3c/FileAPI] Top-level navigations to blob URLs with media mime types result in resource load subject to partitioning (Issue #210) (Wednesday, 3 December)
• Re: [w3c/FileAPI] Update "obtain a blob object" to handle top-level self-fetch (PR #216) (Wednesday, 3 December)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Wednesday, 3 December)
• Re: [whatwg/fetch] Bypass blob URL partitioning for top-level self fetches (PR #1879) (Wednesday, 3 December)
• Re: [whatwg/fetch] Request with credentials included, but only if they are partitioned (Issue #1892) (Wednesday, 3 December)
• Re: [whatwg/encoding] Fix link error (PR #357) (Wednesday, 3 December)
• Re: [whatwg/encoding] Fix link error (PR #357) (Wednesday, 3 December)
• Re: [whatwg/encoding] Fix link error (PR #357) (Wednesday, 3 December)
• Re: [whatwg/storage] Fix markup error (PR #189) (Wednesday, 3 December)
• Re: [whatwg/storage] Fix markup error (PR #189) (Wednesday, 3 December)
• Re: [whatwg/fullscreen] Fix link error (PR #252) (Wednesday, 3 December)
• Re: [whatwg/fullscreen] Fix link error (PR #252) (Wednesday, 3 December)
• Re: [whatwg/webidl] Fix markup error (PR #1550) (Wednesday, 3 December)
• Re: [whatwg/webidl] Fix markup error (PR #1550) (Wednesday, 3 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Editorial: modernize convert nodes into a node (PR #1435) (Tuesday, 2 December)
• Re: [w3c/push-api] check and consume user activation (PR #348) (Tuesday, 2 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/fetch] New Proposal: Fetch retry (Issue #1838) (Tuesday, 2 December)
• Re: [whatwg/storage] Maximum file size that storage should support (Issue #181) (Tuesday, 2 December)
• Re: [w3c/push-api] check and consume user activation (PR #348) (Tuesday, 2 December)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 1 December)
• Re: [w3c/push-api] Drop permissionState()'s argument? (Issue #417) (Monday, 1 December)
• Re: [w3c/push-api] Does PushManager subscribe() need transient activation check? (Issue #346) (Monday, 1 December)
• Re: [w3c/push-api] check and consume user activation (PR #348) (Monday, 1 December)
• Re: [w3c/push-api] Make permissionState() queue a task (PR #416) (Monday, 1 December)
• Re: [w3c/push-api] Make permissionState() queue a task (PR #416) (Monday, 1 December)
• Re: [w3c/push-api] Make permissionState() queue a task (PR #416) (Monday, 1 December)
• [w3c/push-api] Drop permissionState()'s argument? (Issue #417) (Monday, 1 December)
• [w3c/push-api] Make permissionState() queue a task (PR #416) (Monday, 1 December)
• Re: [whatwg/dom] Editorial: modernize mutation observers (PR #1436) (Monday, 1 December)
• Re: [whatwg/dom] Make DOMTokenList's supported token concept also depend on element (PR #1431) (Monday, 1 December)
• Re: [whatwg/dom] Adopting children of an intentional null shadow root goes wrong (Issue #1429) (Monday, 1 December)

Ari Chivukula

• Re: [whatwg/fetch] Request with credentials included, but only if they are partitioned (Issue #1892) (Friday, 5 December)

Ashley Claymore

• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Wednesday, 10 December)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Tuesday, 9 December)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Monday, 8 December)

atzufuki

• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Monday, 15 December)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Monday, 15 December)

Bramus

• Re: [whatwg/dom] Allow `MutationObserver` to observe (certain) element property changes (Issue #1340) (Friday, 12 December)

Bruce B. Anderson

• [whatwg/dom] Support for building an optimal, nested CSSStylesheet programmatically (Issue #1442) (Saturday, 20 December)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 1 December)

bvandersloot-mozilla

• Re: [whatwg/fetch] Add `Prefer: safe` HTTP header (Issue #1891) (Monday, 1 December)
• [whatwg/fetch] Add `Prefer: safe` HTTP header (Issue #1891) (Monday, 1 December)

Carlos Lopez

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 1 December)

Charlie Harrison

• Re: [whatwg/fetch] Request with credentials included, but only if they are partitioned (Issue #1892) (Wednesday, 3 December)
• Re: [whatwg/fetch] Request with credentials included, but only if they are partitioned (Issue #1892) (Tuesday, 2 December)
• [whatwg/fetch] Request with credentials included, but only if they are partitioned (Issue #1892) (Tuesday, 2 December)

Christian Liebel

• Re: [w3ctag/design-reviews] ViewTransitions: waitUntil() method (Issue #1158) (Monday, 8 December)
• Re: [w3ctag/design-reviews] ViewTransitions: waitUntil() method (Issue #1158) (Monday, 8 December)
• Re: [w3ctag/design-reviews] [wg/webextensions] Web Extensions Working Group (Issue #1138) (Monday, 8 December)
• Re: [w3ctag/design-reviews] [wg/webextensions] Web Extensions Working Group (Issue #1138) (Monday, 8 December)
• Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784) (Saturday, 6 December)

Claudia Meadows

• Re: [whatwg/dom] Proposal: add `childFilter` option to `MutationObserverInit` (#905) (Sunday, 28 December)

Daniel Murphy

• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 30 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 30 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Monday, 29 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 16 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 9 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 9 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Monday, 8 December)
• Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784) (Saturday, 6 December)

David A

• [w3ctag/design-reviews] WG New Spec: trigger-scope (Issue #1175) (Thursday, 4 December)

davidsgrogan

• Re: [w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172) (Wednesday, 17 December)

Delaney

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 1 December)

Dibyajyoti Pal

• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 30 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 30 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 30 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 30 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 30 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 16 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 16 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Thursday, 11 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Thursday, 11 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Wednesday, 10 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Wednesday, 10 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Wednesday, 10 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 9 December)
• Re: [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Tuesday, 9 December)
• [w3c/manifest] Update manifest spec to consider manifest updates for icon urls to be cache-control:immutable (PR #1199) (Monday, 8 December)

Dick Hardt

• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Wednesday, 17 December)
• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Friday, 12 December)
• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Friday, 12 December)
• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Thursday, 11 December)

Diego Gonzalez

• [w3ctag/design-reviews] Incubation: @supports at-rule (Issue #1176) (Tuesday, 9 December)

Dominic Farolino

• Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876) (Tuesday, 30 December)
• Re: [whatwg/fetch] Spec 'text directive user activation' boolean (PR #1876) (Tuesday, 30 December)
• Re: [whatwg/dom] Editorial: modernize convert nodes into a node (PR #1435) (Tuesday, 2 December)

Eemeli Aro

• Re: [whatwg/fetch] Add "text" destination type, for JavaScript text imports (PR #1898) (Thursday, 18 December)
• [whatwg/fetch] Add "text" destination type, for JavaScript text imports (PR #1898) (Wednesday, 17 December)

Ellie

• Re: [whatwg/fetch] Add `Prefer: safe` HTTP header (Issue #1891) (Tuesday, 2 December)
• Re: [whatwg/fetch] Add `Prefer: safe` HTTP header (Issue #1891) (Monday, 1 December)
• Re: [whatwg/fetch] Add `Prefer: safe` HTTP header (Issue #1891) (Monday, 1 December)
• Re: [whatwg/fetch] Add `Prefer: safe` HTTP header (Issue #1891) (Monday, 1 December)

Eric A. Meyer

• Re: [WICG/webcomponents] Update reference-target-explainer.md (PR #1119) (Tuesday, 9 December)
• Re: [WICG/webcomponents] Update reference-target-explainer.md (PR #1119) (Tuesday, 9 December)
• [WICG/webcomponents] Update reference-target-explainer.md (PR #1119) (Friday, 5 December)

Eric Lawrence

• Re: [w3c/clipboard-apis] Standardize Clipboard Source url, aka the URL from which the content has been copied from (Issue #244) (Friday, 12 December)

Eric P

• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Monday, 15 December)

Eriko Kurimoto

• Re: [whatwg/storage] Maximum file size that storage should support (Issue #181) (Tuesday, 2 December)

Evgeny Kapun

• [whatwg/dom] concept-node-equals definition is not correct (Issue #1443) (Tuesday, 30 December)

fantasai

• [w3ctag/design-reviews] WG Revision: CSS Anchor Positioning Level 1 (Issue #1182) (Tuesday, 23 December)

Hadley Beeman

• Re: [w3ctag/design-reviews] ServiceWorkerAutoPreload (Issue #1108) (Monday, 15 December)
• Re: [w3ctag/design-reviews] [wg/i18n-core] i18n WG rechartering 2025 (Issue #1180) (Monday, 15 December)
• Re: [w3ctag/design-reviews] [wg/i18n-core] i18n WG rechartering 2025 (Issue #1180) (Monday, 15 December)

hamidulh110-coder

• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) (Thursday, 18 December)
• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) (Thursday, 18 December)

Hidde de Vries

• [w3ctag/design-reviews] WG New Spec: Web Sustainability Guidelines (Issue #1181) (Wednesday, 17 December)

innotommy

• [w3c/screen-orientation] Strengthen Anti-Fingerprinting Requirements from SHOULD → MUST (Issue #277) (Wednesday, 3 December)
• [w3c/screen-orientation] Add Permissions Policy Integration to Control Orientation Data Flow in Embedded Contexts (Issue #276) (Wednesday, 3 December)

ispypoodles-spec

• Re: [whatwg/dom] Editorial: modernize mutation observers (61246e6) (Tuesday, 16 December)

Jacques Newman

• Re: [w3ctag/design-reviews] Incubation: Scoped Focusgroup (Issue #1152) (Wednesday, 3 December)

James Browning

• [whatwg/dom] Implementations do not match spec behavior for .adoptNode(attr) (Issue #1440) (Monday, 15 December)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Monday, 8 December)

James M Snell

• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Friday, 5 December)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Friday, 5 December)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Friday, 5 December)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Thursday, 4 December)

Jan-Ivar Bruaroey

• Re: [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Friday, 12 December)
• [whatwg/fetch] Add webtransport-hashes to request, wired down to create a connection (PR #1896) (Thursday, 11 December)

Jayson Chen

• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 9 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Monday, 8 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Friday, 5 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Friday, 5 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Friday, 5 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Thursday, 4 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Tuesday, 2 December)
• Re: [whatwg/dom] Adopting children of an intentional null shadow root goes wrong (Issue #1429) (Monday, 1 December)

Jeffrey Yasskin

• Re: [w3ctag/design-reviews] Web Authentication Immediate Mediation (Issue #1092) (Tuesday, 9 December)
• Re: [w3ctag/design-reviews] Web Authentication Immediate Mediation (Issue #1092) (Tuesday, 9 December)
• Re: [whatwg/fetch] Request with credentials included, but only if they are partitioned (Issue #1892) (Friday, 5 December)
• Re: [w3ctag/design-reviews] ServiceWorkerAutoPreload (Issue #1108) (Tuesday, 2 December)

Jimmy Wärting

• Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Saturday, 6 December)

Johannes Wilm

• Re: [w3c/editing] Question About Using EditContext with WYSIWYG Editors (Issue #520) (Tuesday, 23 December)
• Re: [w3c/editing] Question About Using EditContext with WYSIWYG Editors (Issue #520) (Tuesday, 23 December)
• Re: [w3c/editing] Question About Using EditContext with WYSIWYG Editors (Issue #520) (Tuesday, 23 December)
• Re: [w3c/editing] Safari Desktop: When aborting a composition after pressing a dead key (e.g. `^`) in oncompositionend event.data will have `""` while `"^"` is expected (Issue #505) (Friday, 12 December)
• Re: [w3c/editing] Create repro for #505. (PR #519) (Friday, 12 December)
• Re: [w3c/editing] Safari Desktop: `insertReplacementText` not fired (Issue #494) (Friday, 12 December)
• Re: [w3c/editing] Chrome Desktop + Android: document.execCommand does not trigger a 'historyUndo' onbeforinput event after running document.execCommand('undo') (Issue #504) (Friday, 12 December)
• Re: [w3c/editing] Safari Desktop: When aborting a composition after pressing a dead key (e.g. `^`) in oncompositionend event.data will have `""` while `"^"` is expected (Issue #505) (Friday, 12 December)
• Re: [w3c/editing] Safari Desktop: Adding an empty span to an otherwise empty editable element, makes the element unselectable (Issue #516) (Friday, 12 December)
• Re: [w3c/editing] Safari Desktop: Conditional Show/ Hide of br element in contenteditable element make caret disappear (Issue #499) (Friday, 12 December)
• Re: [w3c/editing] Safari Desktop: Editing an empty `<a>` makes content leak outside the `<a>` (Issue #497) (Friday, 12 December)
• Re: [w3c/editing] Safari Desktop: position: relative on parent of empty text div makes content leak outside the text div. (Issue #496) (Friday, 12 December)
• Re: [w3c/editing] Safari Desktop: `insertReplacementText` not fired (Issue #494) (Friday, 12 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Friday, 12 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)
• Re: [w3c/editing] Nested editing hosts do not need to be wrapped in insertParagraph (Issue #490) (Thursday, 11 December)
• Re: [w3c/clipboard-apis] Questions about implementing `clipboard.write` (Issue #237) (Thursday, 11 December)
• Re: [w3c/editing] add a draft charter for the 2025 recharter (PR #515) (Thursday, 11 December)
• Re: [w3c/clipboard-apis] `ClipboardItem`: clarify mime parsing (Issue #242) (Thursday, 11 December)
• Re: [w3c/clipboard-apis] Standardize Clipboard Source url, aka the URL from which the content has been copied from (Issue #244) (Thursday, 11 December)
• Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240) (Thursday, 11 December)
• Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243) (Thursday, 11 December)
• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event API specification (PR #239) (Thursday, 11 December)
• Re: [w3c/editing] TPAC 2025 - Agenda (Issue #487) (Thursday, 11 December)
• Re: [w3c/editing] new document defining editing behavior - name is needed (Issue #488) (Thursday, 11 December)
• Re: [w3c/editing] new document defining editing behavior - name is needed (Issue #488) (Thursday, 11 December)
• Re: [w3c/editing] add a draft charter for the 2025 recharter (PR #515) (Thursday, 11 December)
• Re: [w3c/editing] Chrome Desktop + Android: document.execCommand does not trigger a 'historyUndo' onbeforinput event after running document.execCommand('undo') (Issue #504) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Conditional Show/ Hide of br element in contenteditable element make caret disappear (Issue #499) (Thursday, 11 December)
• Re: [w3c/editing] Safari/Chrome: Caret Rendering inconsistent with empty placeholder across browsers (Issue #498) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Editing an empty `<a>` makes content leak outside the `<a>` (Issue #497) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: position: relative on parent of empty text div makes content leak outside the text div. (Issue #496) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: `insertReplacementText` not fired (Issue #494) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)
• Re: [w3c/editing] Rename 512.html to 513.html and add repro for #516 (PR #517) (Wednesday, 10 December)
• Re: [w3c/editing] add a draft charter for the 2025 recharter (PR #515) (Monday, 8 December)

Josh Tumath

• Re: [w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172) (Friday, 19 December)

Julian Descottes

• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Thursday, 11 December)
• Re: [whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Wednesday, 10 December)

Justin Fagnani

• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Monday, 15 December)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Monday, 15 December)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Monday, 15 December)

Kagami Sascha Rosylight

• Re: [w3c/push-api] Define and use the p256dh/auth internal slots (PR #414) (Monday, 8 December)
• Re: [w3c/push-api] check and consume user activation (PR #348) (Tuesday, 2 December)
• Re: [w3c/push-api] check and consume user activation (PR #348) (Monday, 1 December)
• Re: [w3c/push-api] Make permissionState() queue a task (PR #416) (Monday, 1 December)

karintou8710

• Re: [w3c/editing] Question About Using EditContext with WYSIWYG Editors (Issue #520) (Tuesday, 23 December)
• [w3c/editing] Question About Using EditContext with WYSIWYG Editors (Issue #520) (Tuesday, 23 December)

Karl Dubost

• Re: [w3c/clipboard-apis] Standardize Clipboard Source url, aka the URL from which the content has been copied from (Issue #244) (Tuesday, 2 December)
• Re: [w3c/clipboard-apis] Standardize Clipboard Source url (Issue #244) (Tuesday, 2 December)
• Re: [w3c/clipboard-apis] Standardize Clipboard Source url (Issue #244) (Tuesday, 2 December)

Keith Cirkel

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 1 December)

kerrysuegreen5-cyber

• [whatwg/webidl] Intent to use Constants (Issue #1554) (Friday, 19 December)

Kevin Gibbons

• Re: [whatwg/dom] Userland AbortSignal (Issue #1195) (Wednesday, 24 December)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Friday, 5 December)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Friday, 5 December)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Friday, 5 December)
• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Thursday, 4 December)

Kotaro Chikuba

• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Tuesday, 16 December)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Monday, 15 December)

Lea Verou

• Re: [whatwg/dom] [meta] MutationObserver improvements tracking issue (Issue #1439) (Tuesday, 16 December)
• Re: [whatwg/dom] Add new mutation observer init options elementByAttributeFilter and elementFilter (#885) (Tuesday, 16 December)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Tuesday, 16 December)
• Re: [whatwg/dom] Allow `MutationObserver` to observe across `<slot>`s (Issue #1415) (Monday, 15 December)
• Re: [whatwg/dom] Consider adding localNameFilter to MutationObserver (#398) (Sunday, 14 December)
• [whatwg/dom] MutationObserver improvements meta-issue (Issue #1439) (Saturday, 13 December)
• Re: [whatwg/dom] Allow `MutationObserver` to observe across `<slot>`s (Issue #1415) (Saturday, 13 December)
• Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283) (Saturday, 13 December)
• Re: [whatwg/dom] Proposal: add `childFilter` option to `MutationObserverInit` (#905) (Saturday, 13 December)
• Re: [whatwg/dom] Allow `MutationObserver` to observe (certain) element property changes (Issue #1340) (Saturday, 13 December)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Friday, 12 December)
• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Friday, 12 December)
• Re: [whatwg/dom] Allow `MutationObserver` to observe (certain) element property changes (Issue #1340) (Friday, 12 December)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Friday, 5 December)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Friday, 5 December)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Tuesday, 2 December)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 1 December)

Logan Hunt

• Re: [w3c/uievents] Dispatch a click event when keyup or keydown? (#174) (Wednesday, 10 December)

Lola

• Re: [w3ctag/design-reviews] Digital Credentials API (Issue #1119) (Friday, 5 December)
• Re: [w3ctag/design-reviews] Digital Credentials API (Issue #1119) (Friday, 5 December)
• Re: [w3ctag/design-reviews] Incubation: PWA (same-site) Origin Migration (Issue #1164) (Thursday, 4 December)

lorainejarrell373-svg

• [w3c/IndexedDB] I was hacked from somebody by your website (Issue #483) (Monday, 22 December)

Luke Warlow

• Re: [whatwg/fullscreen] Add keyboard locking option (PR #232) (Saturday, 20 December)
• Re: [whatwg/fullscreen] Keyboard lock (Issue #231) (Saturday, 20 December)

Marcos Cáceres

• Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Friday, 12 December)
• Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Thursday, 11 December)
• Re: [w3ctag/design-reviews] Prompt API (Issue #1093) (Tuesday, 9 December)
• Re: [w3ctag/design-reviews] Digital Credentials API (Issue #1119) (Monday, 8 December)

Marijn Kruisselbrink

• Re: [w3ctag/design-reviews] Incubation: PWA (same-site) Origin Migration (Issue #1164) (Thursday, 4 December)

Martin Thomson

• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Thursday, 18 December)
• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Thursday, 18 December)
• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Tuesday, 16 December)
• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Thursday, 11 December)
• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Thursday, 11 December)
• Re: [w3ctag/design-reviews] Define DC API behavior in Private Browsing Mode (Issue #1178) (Thursday, 11 December)
• Re: [w3ctag/design-reviews] [wg/pointer-events] Pointer Events Working Group rechartering (Issue #1165) (Tuesday, 2 December)
• Re: [w3ctag/design-reviews] [wg/pointer-events] Pointer Events Working Group rechartering (Issue #1165) (Tuesday, 2 December)
• Re: [whatwg/fetch] Add `Prefer: safe` HTTP header (Issue #1891) (Tuesday, 2 December)

Masayuki Nakano

• Re: [w3c/editing] Expose event.getTargetRanges() in oncompositionstart (and possibly oncompositionend as well) (Issue #511) (Friday, 12 December)
• Re: [w3c/editing] All browsers: Add ability to cancel character composition (IME) at the very beginning (Issue #508) (Friday, 12 December)
• Re: [w3c/pointerlock] `movementX` and `movementY` for `pointermove` (and `pointerrawupdate`) should be the difference from the previous event for the same `pointerId` (Issue #104) (Friday, 12 December)
• Re: [w3c/editing] Firefox: Clicking a placeholder inside a contenteditable element does not focus the element (Issue #502) (Friday, 12 December)
• Re: [w3c/editing] Firefox: Cursor is misaligned on centered text with placeholder (Issue #501) (Friday, 12 December)
• Re: [w3c/editing] Firefox: Cursor is misaligned on centered text with placeholder (Issue #501) (Friday, 12 December)
• Re: [w3c/editing] Firefox: Empty fields with placeholder are not keyboard selectable (Issue #500) (Friday, 12 December)
• Re: [w3c/editing] Firefox: event.getTargetRanges() in beforeinput not consistent with window.getSelection() (Issue #493) (Friday, 12 December)
• [w3c/pointerlock] `movementX` and `movementY` for `pointermove` (and `pointerrawupdate`) should be the difference from the previous event for the same `pointerId` (Issue #104) (Thursday, 11 December)

Matt Reynolds

• Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Saturday, 13 December)

Matthew Tylee Atkinson

• Re: [w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172) (Wednesday, 17 December)
• Re: [w3ctag/design-reviews] WG New Spec: Scroll-Triggered Animations (Issue #1167) (Wednesday, 17 December)

Max Patiiuk

• [WICG/webcomponents] TypeScript & Framework Support for Scoped Custom Element Registries (Issue #1118) (Thursday, 4 December)

Meghan Denny

• Re: [whatwg/webidl] Intent to use Constants (Issue #1555) (Friday, 26 December)
• Re: [whatwg/webidl] DOMException name proposal (Issue #1552) (Monday, 8 December)

Michael Aufreiter

• Re: [w3c/editing] Ability to anchor a popover to the native selection rectangle using CSS Anchor Positioning (Issue #518) (Sunday, 14 December)
• Re: [w3c/editing] Safari Desktop: Adding an empty span to an otherwise empty editable element, makes the element unselectable (Issue #516) (Sunday, 14 December)
• Re: [w3c/editing] Safari Desktop: Conditional Show/ Hide of br element in contenteditable element make caret disappear (Issue #499) (Sunday, 14 December)
• Re: [w3c/editing] Safari Desktop: Adding an empty span to an otherwise empty editable element, makes the element unselectable (Issue #516) (Sunday, 14 December)
• Re: [w3c/editing] Firefox + Chrome Desktop + Android: document.execCommand does not trigger a 'historyUndo' onbeforinput event after running document.execCommand('undo') (Issue #504) (Sunday, 14 December)
• Re: [w3c/editing] Firefox: event.getTargetRanges() in beforeinput not consistent with window.getSelection() (Issue #493) (Sunday, 14 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Sunday, 14 December)
• Re: [w3c/editing] Safari Desktop: position: relative on parent of empty text div makes content leak outside the text div. (Issue #496) (Saturday, 13 December)
• Re: [w3c/editing] Safari Desktop: Editing an empty `<a>` makes content leak outside the `<a>` (Issue #497) (Saturday, 13 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Saturday, 13 December)
• Re: [w3c/editing] Safari Desktop: `insertReplacementText` not fired (Issue #494) (Saturday, 13 December)
• Re: [w3c/editing] Safari Desktop: When aborting a composition after pressing a dead key (e.g. `^`) in oncompositionend event.data will have `""` while `"^"` is expected (Issue #505) (Friday, 12 December)
• Re: [w3c/editing] Safari Desktop: When aborting a composition after pressing a dead key (e.g. `^`) in oncompositionend event.data will have `""` while `"^"` is expected (Issue #505) (Friday, 12 December)
• [w3c/editing] Create repro for #505. (PR #519) (Friday, 12 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)
• [w3c/editing] Ability to anchor a popover to the native selection rectangle using CSS Anchor Positioning (Issue #518) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)
• Re: [w3c/editing] Chrome Desktop + Android: document.execCommand does not trigger a 'historyUndo' onbeforinput event after running document.execCommand('undo') (Issue #504) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: When aborting a composition after pressing a dead key (e.g. `^`) in oncompositionend event.data will have `""` while `"^"` is expected (Issue #505) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: position: relative on parent of empty text div makes content leak outside the text div. (Issue #496) (Thursday, 11 December)
• Re: [w3c/editing] Safari Desktop: Conditional Show/ Hide of br element in contenteditable element make caret disappear (Issue #499) (Thursday, 11 December)
• Re: [w3c/editing] Rename 512.html to 513.html and add repro for #516 (PR #517) (Wednesday, 10 December)
• [w3c/editing] Rename 512.html to 513.html and add repro for #516 (PR #517) (Wednesday, 10 December)
• Re: [w3c/editing] Safari Desktop: Adding an empty span to an otherwise empty element, makes the element unselectable (Issue #516) (Wednesday, 10 December)
• [w3c/editing] Safari Desktop: Adding an empty span to an otherwise empty element, makes the element unselectable (Issue #516) (Wednesday, 10 December)
• Re: [w3c/editing] Safari Desktop: When aborting a composition after pressing a dead key (e.g. `^`) in oncompositionend event.data will have `""` while `"^"` is expected (Issue #505) (Wednesday, 10 December)

Michael Ficarra

• Re: [whatwg/dom] Add abortSignal.addAbortCallback (PR #1425) (Wednesday, 10 December)
• Re: [whatwg/dom] Add a method like .addTeardown to AbortSignal (Issue #1289) (Tuesday, 9 December)

Mike West

• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Tuesday, 9 December)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Friday, 5 December)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Friday, 5 December)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Thursday, 4 December)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Thursday, 4 December)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Thursday, 4 December)
• [whatwg/url] Define the "extract an origin" operation. (PR #892) (Thursday, 4 December)

Mohamed Amir Yosef

• Re: [w3ctag/design-reviews] Define DC API behavior in Private Browsing Mode (Issue #1178) (Thursday, 11 December)
• Re: [w3ctag/design-reviews] Define DC API behavior in Private Browsing Mode (Issue #1178) (Thursday, 11 December)
• [w3ctag/design-reviews] Define DC API behavior in Private Browsing Mode (Issue #1178) (Wednesday, 10 December)

mollawashim91

• [whatwg/webidl] Intent to use Constants mdwasimmulla2@gmail.com (Issue #1553) (Friday, 12 December)

Monica Chintala

• Re: [w3c/ServiceWorker] Clone response in Lookup Race Response algorithm (PR #1811) (Wednesday, 10 December)

Mustaq Ahmed

• Re: [w3c/pointerlock] `movementX` and `movementY` for `pointermove` (and `pointerrawupdate`) should be the difference from the previous event for the same `pointerId` (Issue #104) (Thursday, 11 December)

NAGAYAMA Toshiaki

• [whatwg/dom] downloads.download() should be appear in the API (Issue #1438) (Friday, 12 December)

NAME-sovsec

• Re: [w3c/clipboard-apis] Add comprehensive clipboardchange event API specification (PR #239) (Thursday, 11 December)

Nicholas Car

• [w3ctag/design-reviews] WG Revision: SHACL 1.2 SPARQL (Issue #1174) (Monday, 1 December)

Nikita Skovoroda

• Re: [whatwg/encoding] ISO-2022-JP does not reset state when returning error (Issue #358) (Monday, 22 December)
• Re: [whatwg/encoding] ISO-2022-JP does not reset state when returning error (Issue #358) (Sunday, 21 December)
• Re: [whatwg/encoding] ISO-2022-JP does not reset state when returning error (Issue #358) (Sunday, 21 December)

Noam Rosenthal

• [w3ctag/design-reviews] Incubation: seamless page transition with deferred commit (Issue #1177) (Tuesday, 9 December)

Owen Buckley

• Re: [WICG/webcomponents] TypeScript & Framework Support for Scoped Custom Element Registries (Issue #1118) (Wednesday, 10 December)

Pascal Schilp

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Friday, 5 December)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 1 December)

Patrick Meenan

• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Thursday, 18 December)
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Tuesday, 16 December)

PATRIK GOLIS

• Re: [w3c/clipboard-apis] [clipboard-apis] .write() for text/html doesn't define a canonical form (Issue #233) (Wednesday, 17 December)

Perchidenise

• [whatwg/fetch] Index.html (Issue #1901) (Wednesday, 24 December)

Peter Beverloo

• Re: [w3c/push-api] Drop permissionState()'s argument? (Issue #417) (Monday, 1 December)

Philip Jägenstedt

• Re: [whatwg/fullscreen] Fix #245 - Addressing new popover values (PR #247) (Thursday, 18 December)
• Re: [whatwg/fullscreen] Fix #245 - Addressing new popover values (PR #247) (Thursday, 18 December)

Philippe Le Hegaret

• Re: [w3c/uievents] Standardize common gestures event (#293) (Tuesday, 16 December)

Pierre-Antoine Champin

• Re: [w3ctag/design-reviews] WG New Spec: RDF 1.2 N-Triples (Issue #1161) (Friday, 19 December)

Psychpsyo (Cameron)

• Re: [w3c/uievents] keydown does not specify whether modifier keys should be indicated on dispatched click event (Issue #406) (Tuesday, 9 December)
• [w3c/uievents] keydown does not specify whether modifier keys should be indicated on dispatched click event (Issue #406) (Tuesday, 9 December)

quangthangt528-rgb

• [whatwg/webidl] Intent to use Constants (Issue #1555) (Friday, 26 December)

Rakina Zata Amni

• Re: [whatwg/fetch] New Proposal: Fetch retry (Issue #1838) (Monday, 1 December)

ranaandixon704-eng

• Re: [whatwg/webidl] Allow a separate getter/setter attribute pair (Issue #1506) (Sunday, 7 December)

Reilly Grant

• Re: [w3ctag/design-reviews] Prompt API (Issue #1093) (Tuesday, 9 December)

Rik Cabanier

• Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Monday, 15 December)
• Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Friday, 12 December)
• Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Thursday, 11 December)
• Re: [w3c/gamepad] Add support for a PCM buffer to the gamepad actuator (Issue #186) (Wednesday, 10 December)

Rob Eisenberg

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Friday, 5 December)

Robbie Speed

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 1 December)

roraja

• Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243) (Tuesday, 2 December)
• Re: [w3c/clipboard-apis] `changeId` interaction between `clipboard.write` and `clipboardchange` (Issue #243) (Tuesday, 2 December)

Ryosuke Niwa

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Friday, 12 December)
• Re: [WICG/webcomponents] TypeScript & Framework Support for Scoped Custom Element Registries (Issue #1118) (Thursday, 4 December)
• Re: [WICG/webcomponents] TypeScript & Framework Support for Scoped Custom Element Registries (Issue #1118) (Thursday, 4 December)
• Re: [WICG/webcomponents] TypeScript & Framework Support for Scoped Custom Element Registries (Issue #1118) (Thursday, 4 December)

Sam Goto

• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Thursday, 18 December)
• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Tuesday, 16 December)
• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Friday, 12 December)
• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Friday, 12 December)
• Re: [w3ctag/design-reviews] Incubation: Email Verification Protocol (Issue #1169) (Friday, 12 December)

Sarven Capadisli

• Re: [w3ctag/design-reviews] WG New Spec: RDF 1.2 N-Triples (Issue #1161) (Friday, 19 December)
• Re: [w3ctag/design-reviews] WG New Spec: RDF 1.2 N-Triples (Issue #1161) (Thursday, 18 December)
• Re: [w3ctag/design-reviews] WG New Spec: RDF 1.2 Concepts and Abstract Data Model (Issue #1159) (Thursday, 18 December)

Shannon Booth

• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Wednesday, 24 December)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Tuesday, 9 December)
• Re: [whatwg/url] Define the "extract an origin" operation. (PR #892) (Monday, 8 December)

Shiba

• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 1 December)

Shunya Shishido

• Re: [w3c/ServiceWorker] Clone response in Lookup Race Response algorithm (PR #1811) (Tuesday, 9 December)
• [w3c/ServiceWorker] Accept-CH frame duplicates fetch events and preloads (Issue #1810) (Monday, 8 December)
• Re: [w3ctag/design-reviews] ServiceWorkerAutoPreload (Issue #1108) (Wednesday, 3 December)

sideshowbarker

• Re: [whatwg/fetch] Index.html (Issue #1901) (Wednesday, 24 December)
• Re: [whatwg/webidl] Intent to use Constants (Issue #1554) (Friday, 19 December)
• Re: [w3c/uievents] Remove redundant checkbox in PR template (PR #410) (Thursday, 18 December)
• Re: [w3c/uievents] Remove redundant checkbox in PR template (PR #410) (Thursday, 18 December)
• Re: [w3c/uievents] Fix misspelling of nativeKey (PR #387) (Wednesday, 17 December)
• Re: [w3c/uievents] Fix misspelling of nativeKey (PR #387) (Wednesday, 17 December)
• Re: [w3c/uievents] Fix misspelling of nativeKey (PR #387) (Wednesday, 17 December)
• Re: [w3c/uievents] Fix build errors (PR #408) (Wednesday, 17 December)
• Re: [w3c/uievents] Fix build errors (PR #408) (Wednesday, 17 December)
• Re: [w3c/uievents] Add a note in ui events spec about UA-provided writing assistance text insertion event ordering. (PR #378) (Tuesday, 16 December)
• Re: [w3c/uievents] Fire keypress event for Enter, Shift+Enter, and Ctrl+Enter keys (PR #392) (Tuesday, 16 December)
• Re: [whatwg/webidl] Intent to use Constants mdwasimmulla2@gmail.com (Issue #1553) (Saturday, 13 December)

Simon Pieters

• [w3c/uievents] Remove redundant checkbox in PR template (PR #410) (Thursday, 18 December)
• Re: [w3c/uievents] Fire keypress event for Enter, Shift+Enter, and Ctrl+Enter keys (PR #392) (Thursday, 18 December)
• [w3c/uievents] No PR diff previews (Issue #409) (Wednesday, 17 December)
• Re: [w3c/uievents] Status code in load event detail (#92) (Wednesday, 17 December)
• Re: [w3c/uievents] Status code in load event detail (#92) (Wednesday, 17 December)
• Re: [w3c/uievents] Remove the generated spec from the tree (Issue #407) (Wednesday, 17 December)
• Re: [w3c/uievents] Remove the generated spec from the tree (Issue #407) (Wednesday, 17 December)
• [w3c/uievents] Fix build errors (PR #408) (Wednesday, 17 December)
• [w3c/uievents] Remove the generated spec from the tree (Issue #407) (Wednesday, 17 December)
• Re: [w3c/uievents] Fix misspelling of nativeKey (PR #387) (Tuesday, 16 December)
• Re: [w3c/uievents] Fix misspelling of nativeKey (PR #387) (Tuesday, 16 December)
• Re: [w3c/uievents] Add a note in ui events spec about UA-provided writing assistance text insertion event ordering. (PR #378) (Tuesday, 16 December)
• Re: [w3c/uievents] Make CompositionEvent.init take a Window rather than WindowProxy (PR #379) (Tuesday, 16 December)
• Re: [w3c/uievents] Fix misspelling of nativeKey (PR #387) (Tuesday, 16 December)
• Re: [w3c/uievents] Fire keypress event for Enter, Shift+Enter, and Ctrl+Enter keys (PR #392) (Tuesday, 16 December)

stat3ofconsc3ience

• Re: [w3c/ServiceWorker] Preventing server-forced updates (#822) (Tuesday, 23 December)

Stephanie Zhang

• Re: [whatwg/dom] Add FormControlRange interface (PR #1404) (Thursday, 4 December)

Stephen McGruer

• Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015) (Monday, 15 December)

Steve Orvell

• Re: [whatwg/dom] Allow `MutationObserver` to observe across `<slot>`s (Issue #1415) (Saturday, 13 December)
• Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) (Monday, 1 December)

Steven Becker

• Re: [w3c/IndexedDB] Mark transactions inactive during key serialization (PR #479) (Monday, 1 December)

Tab Atkins Jr.

• [whatwg/webidl] Fix markup error (PR #1550) (Tuesday, 2 December)
• Re: [whatwg/encoding] Fix link error (PR #357) (Tuesday, 2 December)
• [whatwg/encoding] Fix link error (PR #357) (Tuesday, 2 December)
• [whatwg/storage] Fix markup error (PR #189) (Tuesday, 2 December)
• [whatwg/fullscreen] Fix link error (PR #252) (Tuesday, 2 December)

tanu18

• Re: [w3c/clipboard-apis] Standardize Clipboard Source url, aka the URL from which the content has been copied from (Issue #244) (Wednesday, 3 December)
• Re: [w3c/clipboard-apis] Standardize Clipboard Source url (Issue #244) (Tuesday, 2 December)

Taym Haddadi

• Re: [whatwg/streams] Do the abort steps of ReadableStreamPipeTo really guarantee the abort callback to be called before cancel? (Issue #1229) (Saturday, 6 December)

Tim Flynn

• [whatwg/fetch] Should the reload-navigation flag behave similarly to the "reload" cache mode? (Issue #1899) (Thursday, 18 December)

Tim van der Lippe

• [whatwg/fetch] Editorial: fix typo (PR #1900) (Friday, 19 December)
• Re: [whatwg/fetch] Lowercasing of scheme in URL in conflict with WPT test for CORS check (Issue #1895) (Thursday, 11 December)
• Re: [whatwg/fetch] Lowercasing of scheme in URL in conflict with WPT test for CORS check (Issue #1895) (Thursday, 11 December)
• [whatwg/fetch] Lowercasing of scheme in URL in conflict with WPT test for CORS check (Issue #1895) (Tuesday, 9 December)

Ultraslayyy

• [w3c/FileAPI] Editorial: Avoid shadowing `type` parameter in `package data` algorithm (PR #218) (Tuesday, 16 December)
• Re: [w3c/FileAPI] "package data" reuses type variable (#124) (Tuesday, 16 December)
• Re: [w3c/FileAPI] "package data" reuses type variable (#124) (Tuesday, 16 December)

Valery Zinchenko

• Re: [whatwg/dom] Make it possible to observe connected-ness of a node (#533) (Friday, 12 December)

VampVera

• Re: [w3c/clipboard-apis] Scope events to GlobalEventHandlers (PR #196) (Tuesday, 2 December)

W3C Bot

• Re: [w3c/uievents] Fix misspelling of nativeKey (PR #387) (Tuesday, 16 December)
• Re: [w3c/FileAPI] Editorial: Avoid shadowing `type` parameter in `package data` algorithm (PR #218) (Tuesday, 16 December)
• [w3ctag/design-reviews] [wg/i18n-core] i18n WG rechartering 2025 (Issue #1180) (Friday, 12 December)
• [w3ctag/design-reviews] [[wg/vc] Verifiable Credentials Working Group (Issue #1179) (Thursday, 11 December)

Wenson Hsieh

• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Sunday, 14 December)
• Re: [w3c/editing] Safari Desktop: Doesn't fire inputType 'formatBold', 'formatItalic' etc. in beforeinput (Issue #492) (Thursday, 11 December)

Westbrook Johnson

• Re: [WICG/webcomponents] Update reference-target-explainer.md (PR #1119) (Tuesday, 9 December)
• Re: [WICG/webcomponents] Update reference-target-explainer.md (PR #1119) (Tuesday, 9 December)
• Re: [WICG/webcomponents] Update reference-target-explainer.md (PR #1119) (Friday, 5 December)

Xiaoqian Wu

• [w3c/editing] add a draft charter for the 2025 recharter (PR #515) (Monday, 8 December)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] Clone response in Lookup Race Response algorithm (PR #1811) (Friday, 12 December)
• Re: [w3c/ServiceWorker] Clone response in Lookup Race Response algorithm (PR #1811) (Wednesday, 10 December)
• Re: [w3c/ServiceWorker] Clone response in Lookup Race Response algorithm (PR #1811) (Tuesday, 9 December)
• [w3c/ServiceWorker] Clone response in Lookup Race Response algorithm (PR #1811) (Tuesday, 9 December)
• Re: [w3c/ServiceWorker] Accept-CH frame duplicates fetch events and preloads (Issue #1810) (Monday, 8 December)
• Re: [w3c/ServiceWorker] Editorial: export "Fire Functional Event" arguments (PR #1809) (Friday, 5 December)
• Re: [w3c/ServiceWorker] Preserve sec-fetch-dest for passed navigate requests (Issue #1803) (Monday, 1 December)

yussie6brey-design

• Re: [whatwg/dom] Missing machinery for associated Event data (Issue #1328) (Saturday, 13 December)

Zgroza (Luke Klimek)

• Re: [w3c/clipboard-apis] Proposal: Identifying whether the clipboard has changed without re-reading it (Issue #232) (Thursday, 4 December)

李大仁

• Re: [whatwg/fetch] Replace request's "window" with "traversable for user prompts" (PR #1823) (Tuesday, 9 December)

Last message date: Tuesday, 30 December 2025 18:34:31 UTC