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

Aaron Gustafson

• Re: [w3c/manifest] Add members for localization (PR #1101) (Tuesday, 8 October)

Aaron Leventhal

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 25 October)
• Re: [WICG/webcomponents] Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements (Issue #1073) (Tuesday, 15 October)
• Re: [WICG/webcomponents] Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements (Issue #1073) (Monday, 7 October)
• Re: [WICG/webcomponents] Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements (Issue #1073) (Tuesday, 1 October)

AbdellahBoutmad

• [whatwg/dom] Fix Minor Writing Errors (PR #1314) (Sunday, 6 October)

abhish-shrivastava

• Re: [w3c/selection-api] Improve selection.isCollapsed (Issue #337) (Wednesday, 9 October)
• Re: [w3c/selection-api] Improve selection.isCollapsed (Issue #337) (Monday, 7 October)
• [w3c/selection-api] Improve selection.isCollapsed (Issue #337) (Monday, 7 October)

Abhishek Shanthkumar

• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Friday, 25 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Thursday, 24 October)
• Re: [w3c/IndexedDB] Delete entire site data on data corruption/loss? (Issue #431) (Wednesday, 16 October)
• Re: [w3c/IndexedDB] Specify the exception for read failures arising due to partial data loss on the file system (Issue #423) (Wednesday, 16 October)
• [w3c/IndexedDB] Delete entire site data on data corruption/loss? (Issue #431) (Tuesday, 15 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Monday, 14 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Monday, 14 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Monday, 14 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Friday, 11 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Friday, 11 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Friday, 11 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Thursday, 10 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Thursday, 10 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Thursday, 10 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Thursday, 10 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Wednesday, 9 October)
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) (Wednesday, 9 October)
• [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Tuesday, 8 October)

Adam Rice

• Re: [whatwg/streams] Unified way to clean up after ReadableStream finished/errored/was canceled (Issue #1329) (Thursday, 31 October)
• Re: [whatwg/encoding] Editorial: use leading and trailing surrogate (PR #309) (Friday, 4 October)

adrianhelvikspond

• Re: [WICG/webcomponents] Anonymous Custom Elements (Issue #1074) (Monday, 14 October)

Akash

• Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283) (Sunday, 6 October)
• Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283) (Wednesday, 2 October)

Alexandre Nderagakura

• Re: [w3ctag/design-reviews] FYI Private State Token API Permissions Policy Default Allowlist Wildcard (Issue #990) (Thursday, 31 October)

Andrea Giammarchi

• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 31 October)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 31 October)
• Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081) (Thursday, 17 October)
• Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318) (Wednesday, 16 October)
• Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318) (Tuesday, 15 October)
• Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318) (Tuesday, 15 October)
• Re: [whatwg/dom] DOM element with a name='currentScript' attribute can hijack document.currentScript.src (Issue #1315) (Tuesday, 8 October)
• Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283) (Friday, 4 October)

Andrew Kaster

• [whatwg/webidl] Promises: Return a PromiseCapability from react (PR #1445) (Saturday, 26 October)
• Re: [whatwg/webidl] `make` fails due to missing ECMAScript references (Issue #1444) (Saturday, 26 October)
• [whatwg/webidl] `make remote` fails due to missing ECMAScript references (Issue #1444) (Saturday, 26 October)
• [whatwg/webidl] Should react to a Promise steps return a PromiseCapability instead of a Promise? (Issue #1443) (Wednesday, 23 October)
• Re: [w3c/ServiceWorker] Steps for Update have an empty condition for async modules (Issue #1732) (Friday, 18 October)
• Re: [w3c/ServiceWorker] Steps for Update have an empty condition for async modules (Issue #1732) (Friday, 18 October)
• [w3c/ServiceWorker] Steps for Update have an empty condition for async modules (Issue #1732) (Friday, 18 October)
• Re: [w3c/ServiceWorker] Job promise is an ECMAScript type, not WebIDL (Issue #1731) (Thursday, 3 October)
• [w3c/ServiceWorker] Job promise is an ECMAScript type, not WebIDL (Issue #1731) (Thursday, 3 October)

Andrew Liu

• Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770) (Monday, 7 October)

Andrew Sutherland

• Re: [w3c/IndexedDB] Delete entire site data on data corruption/loss? (Issue #431) (Wednesday, 16 October)
• Re: [w3c/IndexedDB] Delete entire site data on data corruption/loss? (Issue #431) (Wednesday, 16 October)

Andrew Williams

• Re: [w3c/FileAPI] Blob URL store partitioning (#153) (Thursday, 31 October)
• Re: [w3c/FileAPI] Blob URL store partitioning (#153) (Monday, 28 October)
• [whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783) (Friday, 25 October)
• [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201) (Friday, 25 October)

Andy Edwards

• Re: [whatwg/streams] define semantics of {source,sink}.finally() (#636) (Thursday, 31 October)
• Re: [whatwg/streams] define semantics of {source,sink}.finally() (#636) (Thursday, 31 October)
• Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Tuesday, 29 October)
• Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) (Tuesday, 29 October)
• [whatwg/streams] Unified way to clean up after ReadableStream finished/errored/was canceled (Issue #1329) (Monday, 28 October)

Angelos Bouklis

• Re: [whatwg/fetch] Add a `timeout` option, to prevent hanging (#951) (Thursday, 24 October)

Anne van Kesteren

• Re: [w3c/push-api] Add Declarative Web Push (PR #385) (Thursday, 24 October)
• Re: [whatwg/fetch] Skip localhost when evaluating HSTS upgrades (PR #1781) (Thursday, 24 October)
• Re: [whatwg/fetch] Meta: reference new Structured Field Values RFC (PR #1782) (Thursday, 24 October)
• [whatwg/fetch] Meta: reference new Structured Field Values RFC (PR #1782) (Thursday, 24 October)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Thursday, 24 October)
• Re: [w3c/push-api] Declarative Web Push (Issue #360) (Thursday, 24 October)
• Re: [whatwg/fetch] Response body being null on 204/205/304 etc doesn't match any implementation (Issue #1779) (Wednesday, 23 October)
• [w3c/clipboard-apis] SVG sanitization not defined (Issue #229) (Wednesday, 23 October)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Tuesday, 22 October)
• Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391) (Monday, 21 October)
• Re: [whatwg/dom] Steps of removing a node definition about live range do not match with browsers if the range is in a shadow DOM and the shadow itself is removed (Issue #1274) (Saturday, 19 October)
• Re: [whatwg/fetch] Can the set of safelisted methods be extended? (Issue #1774) (Thursday, 17 October)
• Re: [whatwg/dom] Update README.mdkoko (PR #1316) (Wednesday, 9 October)
• Re: [whatwg/dom] DOM element with a name='currentScript' attribute can hijack document.currentScript.src (Issue #1315) (Tuesday, 8 October)
• Re: [whatwg/dom] DOM element with a name='currentScript' attribute can hijack document.currentScript.src (Issue #1315) (Tuesday, 8 October)
• Re: [whatwg/encoding] Editorial: use leading and trailing surrogate (PR #309) (Friday, 4 October)
• Re: [whatwg/encoding] Editorial: use leading and trailing surrogate (PR #309) (Friday, 4 October)
• Re: [whatwg/encoding] Editorial: use leading and pending surrogate (PR #309) (Friday, 4 October)
• Re: [whatwg/encoding] If gb18030 is revised, consider aligning the Encoding Standard (#27) (Friday, 4 October)
• Re: [whatwg/encoding] Reflect changes in GB 18030-2022 (Issue #312) (Friday, 4 October)
• Re: [whatwg/encoding] Reflect changes in GB 18030-2022 (Issue #312) (Friday, 4 October)
• Re: [whatwg/encoding] Adopt GB18030-2022 (PR #336) (Friday, 4 October)
• Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283) (Friday, 4 October)
• Re: [whatwg/dom] Methods on ChildNode and ParentNode that take `(Node or DOMString)... nodes` should not use an intermediate DocumentFragment (Issue #1313) (Friday, 4 October)
• Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737) (Wednesday, 2 October)
• Re: [whatwg/encoding] Adopt GB18030-2022 (PR #336) (Wednesday, 2 October)
• Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737) (Tuesday, 1 October)
• Re: [whatwg/fetch] Clarify that request.origin cannot be "client" at certain points (PR #1776) (Tuesday, 1 October)
• Re: [whatwg/fetch] Unclear how to serialize request origin "client" (Issue #1773) (Tuesday, 1 October)
• Re: [whatwg/fetch] Clarify that request.origin cannot be "client" at certain points (PR #1776) (Tuesday, 1 October)
• Re: [whatwg/fetch] Clarify that request.origin cannot be "client" at certain points (PR #1776) (Tuesday, 1 October)

Anssi Kostiainen

• Re: [w3ctag/design-reviews] Updated review of WebNN API (Issue #933) (Thursday, 24 October)
• Re: [w3ctag/design-reviews] Vibration API (Issue #971) (Thursday, 10 October)
• Re: [w3ctag/design-reviews] Vibration API (Issue #971) (Wednesday, 9 October)
• Re: [w3ctag/design-reviews] Vibration API (Issue #971) (Wednesday, 2 October)

anuoua

• Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318) (Tuesday, 15 October)
• [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318) (Tuesday, 15 October)
• [whatwg/dom] Proposal: getImageData api for all element，not limited to canvas (Issue #1317) (Tuesday, 15 October)

Anusha Muley

• [w3ctag/design-reviews] Allowing SameSite=None Cookies in Sandboxed Contexts (Issue #1004) (Wednesday, 16 October)

astratgeovendi01

• [whatwg/encoding] In blink, we only do the lookup by frame name in the local process. So in all cases where we host the navigation in a different process, the lookup by name just never works. (Issue #337) (Wednesday, 30 October)

baxfax

• Re: [w3c/charter-html] WebPlat charter: Deliverable state (#155) (Monday, 21 October)

Ben Francis

• Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996) (Monday, 21 October)
• Re: [w3c/manifest] Unbind computed id from start_url (Issue #1148) (Tuesday, 15 October)
• Re: [w3c/manifest] Clarification needed for document URL (Issue #1147) (Monday, 14 October)

Ben Kelly

• Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770) (Tuesday, 8 October)

Ben Visness

• Re: [whatwg/webidl] Intent use number / bigint union type (Issue #1426) (Thursday, 3 October)

Benjaminyourass

• Re: [whatwg/dom] I'd expect consistency with () which has the connected check. (Issue #1319) (Saturday, 19 October)
• [whatwg/dom] I'd expect consistency with () which has the connected check. (Issue #1319) (Saturday, 19 October)

br3nt

• Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081) (Monday, 21 October)
• Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081) (Sunday, 20 October)
• [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081) (Wednesday, 16 October)

Brett Zamir

• Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224) (Wednesday, 2 October)

brusshamilton

• [w3ctag/design-reviews] Review for Protected Audiences Bidding and Auction Services API (Issue #1009) (Friday, 25 October)

Camille Lamy

• Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440) (Wednesday, 9 October)

Carlos Lopez

• Re: [WICG/webcomponents] [a11y]: An exhaustive look at support for using HTMLInputElement with Web Components (Issue #996) (Tuesday, 1 October)

carlosjeurissen

• Re: [w3c/manifest] Web Manifest Overrides (Issue #1045) (Tuesday, 1 October)

Christian Biesinger

• Re: [w3ctag/design-reviews] Early Design Review: Lightweight FedCM (Issue #986) (Thursday, 24 October)

Christian Liebel

• Re: [w3c/manifest] prefer_related_applications is single engine feature (#957) (Wednesday, 16 October)
• Re: [w3c/manifest] related_applications is single engine feature (#956) (Wednesday, 16 October)
• Re: [w3c/manifest] prefer_related_applications is single engine feature (#957) (Wednesday, 16 October)
• Re: [w3c/manifest] "internationalization" section (Issue #1090) (Tuesday, 15 October)
• Re: [w3c/manifest] Clarify case-insensitive parsing for enum values (Issue #1142) (Tuesday, 15 October)
• [w3c/manifest] Make enums case-insensitive (PR #1149) (Tuesday, 15 October)
• Re: [w3c/manifest] shortcuts and localizability (Issue #1087) (Tuesday, 8 October)
• Re: [w3c/manifest] Use of `CanonicalizeUnicodeLocaleId` (Issue #1084) (Tuesday, 8 October)
• Re: [w3c/manifest] "security sensitive" items interaction with localization (Issue #1086) (Tuesday, 8 October)
• Re: [w3c/manifest] "localizable members" should be defined separately? (Issue #1080) (Tuesday, 8 October)
• Re: [w3c/manifest] Application name section might need localization support (Issue #1088) (Tuesday, 8 October)
• Re: [w3c/manifest] Add members for localization (PR #1101) (Tuesday, 8 October)
• Re: [w3c/manifest] No language/direction metadata for shortcuts? (Issue #1078) (Tuesday, 8 October)
• Re: [w3c/manifest] `name` and `short_name` (and other localizable member's) relationship to localization and accessibility (Issue #1085) (Tuesday, 8 October)
• Re: [w3c/manifest] Add optional `translations` member (#676) (Tuesday, 8 October)
• Re: [w3c/manifest] No way to localize icons? (Issue #1077) (Tuesday, 8 October)
• Re: [w3c/manifest] Up Dating a Galaxy A13a 5GHz Repository (Issue #1146) (Thursday, 3 October)

Christoph Scheffauer

• Re: [WICG/webcomponents] Proposal: Allow custom elements to be in any namespace (#634) (Wednesday, 2 October)

christophe geiser

• [WICG/webcomponents] Form associated custom elements: cross shadow root form participation (Issue #1075) (Sunday, 6 October)

Claudia Meadows

• Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Thursday, 31 October)

Cyberetek

• [whatwg/streams] https://www.facebook.com/pages/Ptsunan-Rubbre-Pabrik-Getah-Karet-Palembang-Kertapati/499702870401821?mibextid=rS40aB7S9Ucbxw6v (Issue #1328) (Friday, 4 October)

DadvDadv

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

Dan Clark

• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Thursday, 24 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Thursday, 24 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Tuesday, 15 October)

Dan Dumont

• Re: [w3c/ServiceWorker] Service Worker as secure storage and provider for access token and refresh token (Issue #1626) (Wednesday, 23 October)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002) (Wednesday, 30 October)
• Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002) (Wednesday, 30 October)
• Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994) (Wednesday, 9 October)
• Re: [w3ctag/design-reviews] TAG Review for CSS Values & Units Level 5 (Issue #993) (Wednesday, 9 October)
• Re: [w3ctag/design-reviews] TAG Review for CSS Values & Units Level 5 (Issue #993) (Wednesday, 9 October)

Daniel Herr

• Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059) (Wednesday, 30 October)

Daniel Murphy

• Re: [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Add guidance for user agents about how to prevent malicious localization strings (Issue #1150) (Thursday, 31 October)
• Re: [w3c/manifest] Relationship between nestedly scoped web app manifests? (#539) (Thursday, 31 October)
• Re: [w3c/manifest] Relationship between nestedly scoped web app manifests? (#539) (Thursday, 31 October)
• Re: [w3c/manifest] Add guidance for user agents about how to prevent malicious localization strings (Issue #1150) (Thursday, 31 October)
• Re: [w3c/manifest] How to extend the scope to ensure that the PWA provides the same user experience when accessing pages in different domains? (#964) (Friday, 25 October)
• Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996) (Wednesday, 23 October)
• Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996) (Tuesday, 22 October)
• [w3c/manifest] Add guidance for user agents about how to prevent malicious localization strings (Issue #1150) (Monday, 21 October)
• Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996) (Monday, 21 October)
• Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996) (Monday, 21 October)
• Re: [w3c/manifest] prefer_related_applications is single engine feature (#957) (Wednesday, 16 October)
• Re: [w3c/manifest] related_applications is single engine feature (#956) (Wednesday, 16 October)
• Re: [w3c/manifest] Add members for localization (PR #1101) (Friday, 11 October)

Danny Engelman

• Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081) (Thursday, 17 October)

darien maillet valentine

• Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283) (Sunday, 6 October)

David A

• Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994) (Friday, 25 October)
• Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994) (Friday, 11 October)

Derek Schuff

• Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002) (Wednesday, 30 October)
• Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002) (Wednesday, 23 October)
• Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002) (Wednesday, 23 October)
• [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002) (Tuesday, 8 October)

Di Zhang

• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Tuesday, 22 October)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Monday, 21 October)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Monday, 21 October)
• Re: [w3c/selection-api] Define to remove selection range automatically if a selection range is modified into different selection root (Issue #175) (Thursday, 17 October)
• Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168) (Thursday, 17 October)
• Re: [whatwg/dom] Steps of removing a node definition about live range do not match with browsers if the range is in a shadow DOM and the shadow itself is removed (Issue #1274) (Thursday, 17 October)
• Re: [w3c/selection-api] Add `selectionRoot` option to getComposedRanges parameter options (Issue #180) (Tuesday, 15 October)
• Re: [w3c/selection-api] Add `selectionRoot` option to getComposedRanges parameter options (Issue #180) (Tuesday, 15 October)
• Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336) (Tuesday, 15 October)
• Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336) (Wednesday, 9 October)
• Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336) (Monday, 7 October)

Dipika Bhattacharya

• [w3c/manifest] Clarification needed for document URL (Issue #1147) (Wednesday, 9 October)

Domenic Denicola

• Re: [w3c/FileAPI] google chrome can’t be installed on iPhone (Issue #202) (Wednesday, 30 October)
• Re: [whatwg/webidl] Editorial: replace uses of the Type macro with is-a tests (PR #1447) (Tuesday, 29 October)
• Re: [whatwg/webidl] Should react to a Promise steps return a PromiseCapability instead of a Promise? (Issue #1443) (Tuesday, 29 October)
• Re: [whatwg/webidl] Promises: Return a PromiseCapability from react (PR #1445) (Tuesday, 29 October)
• Re: [whatwg/webidl] Editorial: replace uses of the Type macro with is-a tests (PR #1447) (Tuesday, 29 October)
• Re: [whatwg/webidl] Promises: Return a PromiseCapability from react (PR #1445) (Tuesday, 29 October)
• Re: [whatwg/webidl] `make` fails due to missing ECMAScript references (Issue #1444) (Tuesday, 29 October)
• Re: [whatwg/webidl] Fix Iterator prototype reference (PR #1446) (Tuesday, 29 October)
• Re: [whatwg/streams] Editorial: replace uses of the Type macro with is-a tests (PR #1330) (Tuesday, 29 October)
• Re: [whatwg/streams] Editorial: replace uses of the Type macro with is-a tests (PR #1330) (Tuesday, 29 October)
• Re: [whatwg/webidl] Editorial: replace uses of the Type macro with is-a tests (PR #1447) (Tuesday, 29 October)
• Re: [whatwg/webidl] Promises: Return a PromiseCapability from react (PR #1445) (Monday, 28 October)
• [whatwg/webidl] Fix Iterator prototype reference (PR #1446) (Monday, 28 October)
• Re: [whatwg/webidl] Should react to a Promise steps return a PromiseCapability instead of a Promise? (Issue #1443) (Thursday, 24 October)
• Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440) (Tuesday, 8 October)
• Re: [whatwg/dom] Fix Minor Writing Errors (PR #1314) (Monday, 7 October)

Dominic Farolino

• [w3c/selection-api] Reference the move primitive in DOM mutations section (PR #341) (Wednesday, 30 October)
• [w3c/selection-api] Editorial: Correctly reference `{{Document/getSelection()}}` (PR #339) (Wednesday, 30 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Wednesday, 16 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 15 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 15 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 15 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 15 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Tuesday, 15 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 10 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 10 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 10 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 10 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 10 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 10 October)
• Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) (Thursday, 10 October)

Elad Alon

• Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962) (Wednesday, 30 October)
• Re: [w3ctag/design-reviews] Element Capture (Issue #954) (Friday, 25 October)
• Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962) (Tuesday, 22 October)
• Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962) (Wednesday, 16 October)
• Re: [w3ctag/design-reviews] Element Capture (Issue #954) (Wednesday, 16 October)

Eric Lawrence

• Re: [whatwg/fetch] Skip localhost when evaluating HSTS upgrades (PR #1781) (Wednesday, 30 October)
• Re: [whatwg/fetch] Skip localhost when evaluating HSTS upgrades (PR #1781) (Wednesday, 30 October)
• [whatwg/fetch] Skip localhost when evaluating HSTS upgrades (PR #1781) (Thursday, 24 October)
• [whatwg/fetch] Exclude localhost from HTTPS upgrades (Issue #1780) (Thursday, 24 October)

Evan Stade

• Re: [whatwg/storage] StorageEstimate.quota + Storage Pressure (#73) (Thursday, 31 October)
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) (Thursday, 24 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Tuesday, 15 October)
• Re: [w3c/IndexedDB] Configurable task priority for IDBRequest and IDBTransaction? (Issue #428) (Friday, 11 October)
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) (Wednesday, 9 October)
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) (Tuesday, 8 October)
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) (Tuesday, 8 October)

fantasai

• Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003) (Thursday, 31 October)
• [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003) (Monday, 14 October)

Filimon Danopoulos

• Re: [WICG/webcomponents] Anonymous Custom Elements (Issue #1074) (Tuesday, 1 October)

FND

• Re: [whatwg/dom] Proposal: rate limiting event listeners (debounce / throttle) (Issue #1298) (Thursday, 3 October)

Gingeh

• Re: [w3c/selection-api] Determine whether addRange() and removeAllRanges() should reset direction (#3) (Sunday, 13 October)

github-actions[bot]

• [w3c/selection-api] Tidied up document using tidy-html5 (PR #340) (Wednesday, 30 October)

Han Seoul-Oh

• Re: [w3c/uievents] Need virtual key codes (Issue #377) (Tuesday, 8 October)

Isaiah Inuwa

• Re: [w3c/manifest] related_applications is single engine feature (#956) (Thursday, 31 October)

Ivan Herman

• [w3ctag/design-reviews] EPUB 3.3 2024-20-27 Recommendation with Candidate Corrections (Issue #1006) (Thursday, 17 October)

Jake Archibald

• [whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320) (Thursday, 31 October)

James Browning

• Re: [WICG/webcomponents] Anonymous Custom Elements (Issue #1074) (Tuesday, 1 October)

James Craig

• Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) (Friday, 25 October)

James M Snell

• Re: [whatwg/fetch] Allow request take AsyncIterable body? (#1291) (Thursday, 10 October)

Jamie Mansfield

• [w3c/uievents] Fix misspelling of nativeKey (PR #387) (Saturday, 5 October)

Jan Martin

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

Jeffrey Yasskin

• Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962) (Wednesday, 30 October)
• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Wednesday, 30 October)
• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Tuesday, 29 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Tuesday, 29 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Friday, 25 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Thursday, 24 October)
• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) (Wednesday, 23 October)
• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) (Wednesday, 23 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Tuesday, 22 October)
• Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994) (Monday, 21 October)
• Re: [w3ctag/design-reviews] A layer attribute for layering of linked CSS style sheets in HTML (Issue #970) (Thursday, 17 October)
• Re: [w3ctag/design-reviews] A layer attribute for layering of linked CSS style sheets in HTML (Issue #970) (Thursday, 17 October)
• Re: [w3ctag/design-reviews] CSS Selectors 4; :local-link (Issue #998) (Thursday, 17 October)
• Re: [w3ctag/design-reviews] CSS Selectors 4; :local-link (Issue #998) (Thursday, 17 October)
• Re: [w3ctag/design-reviews] Realms Initialization Control (Issue #985) (Tuesday, 15 October)
• Re: [w3ctag/design-reviews] Realms Initialization Control (Issue #985) (Tuesday, 15 October)
• Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003) (Monday, 14 October)
• Re: [w3ctag/design-reviews] CSS Scoping; :has-slotted (Issue #999) (Monday, 14 October)

Jelle Raaijmakers

• [w3c/selection-api] Scheduling an selectionchange event does not set "has scheduled selectionchange event" to true (Issue #338) (Wednesday, 9 October)

Joe Pea

• Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076) (Sunday, 13 October)
• Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076) (Sunday, 13 October)
• Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076) (Sunday, 13 October)
• [WICG/webcomponents] case-sensitive attribute APIs would be useful. (Issue #1076) (Sunday, 13 October)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Saturday, 12 October)
• Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069) (Saturday, 12 October)

Joey Arhar

• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Thursday, 31 October)
• [w3ctag/design-reviews] CSS :open pseudo-class (Issue #1010) (Monday, 28 October)
• [w3ctag/design-reviews] Customizable select element (Issue #1007) (Thursday, 17 October)

Johannes Wilm

• Re: [w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169) (Monday, 7 October)
• Re: [w3c/clipboard-apis] ClipboardChange event spec: Callout transient user activation should be applied for focus requirement. (Issue #225) (Monday, 7 October)
• Re: [w3c/clipboard-apis] Clipboard Change Event API (Issue #227) (Monday, 7 October)
• Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468) (Monday, 7 October)
• Re: [w3c/editing] Clarify the nested case of `contenteditable=true` and `contenteditable=plaintext-only` (Issue #470) (Monday, 7 October)
• [w3c/editing] CfC: Enable automated publication system for all Web Editing WG specs (Issue #471) (Wednesday, 2 October)

Josh Karlin

• Re: [w3ctag/design-reviews] Shared Storage API (Issue #747) (Thursday, 10 October)

Joshua Bell

• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Friday, 25 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Tuesday, 15 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Tuesday, 15 October)
• Re: [w3c/IndexedDB] Specify the exception for read failures arising due to partial data loss on the file system (Issue #423) (Tuesday, 15 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Tuesday, 15 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Monday, 14 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Friday, 11 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Thursday, 10 October)
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) (Tuesday, 8 October)
• Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430) (Tuesday, 8 October)

Juan5212

• [whatwg/webidl] conda (Issue #1442) (Sunday, 13 October)

juj

• [whatwg/dom] DOM element with a name='currentScript' attribute can hijack document.currentScript.src (Issue #1315) (Tuesday, 8 October)

Julian Reschke

• Re: [whatwg/fetch] Can the set of safelisted methods be extended? (Issue #1774) (Thursday, 17 October)

Julien Cayzac

• Re: [w3c/manifest] Add members for localization (PR #1101) (Saturday, 26 October)

Jun

• Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440) (Tuesday, 8 October)
• Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440) (Monday, 7 October)

Justin Fagnani

• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 29 October)
• Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081) (Monday, 21 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Wednesday, 16 October)
• Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076) (Sunday, 13 October)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Thursday, 3 October)
• Re: [WICG/webcomponents] Manage pseudo class matching state for custom elements (#813) (Thursday, 3 October)

Kagami Sascha Rosylight

• Re: [w3c/FileAPI] Removed extra "be" in sentence. (PR #200) (Thursday, 24 October)
• Re: [w3c/FileAPI] Removed extra "be" in sentence. (PR #200) (Thursday, 24 October)

Keith Cirkel

• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Wednesday, 30 October)
• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Friday, 25 October)
• [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Thursday, 17 October)
• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Tuesday, 15 October)
• [WICG/webcomponents] [Scoped Registries] Disconnected elements can retain their "origin" by utilising the dangling TreeScope ptr (Issue #1078) (Tuesday, 15 October)
• Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076) (Sunday, 13 October)
• Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076) (Sunday, 13 October)

Kerryhopkins

• [w3c/FileAPI] google chrome can’t be installed on iPhone (Issue #202) (Wednesday, 30 October)

Kevin McNee

• Re: [w3ctag/design-reviews] Early design review: Future browsing context group dependency hint (Issue #979) (Tuesday, 22 October)
• Re: [w3ctag/design-reviews] Early design review: Future browsing context group dependency hint (Issue #979) (Wednesday, 9 October)

Kokobaran

• [whatwg/dom] Update README.mdkoko (PR #1316) (Wednesday, 9 October)

Kristoffer Strube

• [w3c/FileAPI] Removed extra "be" in sentence. (PR #200) (Thursday, 24 October)

Kurt Catti-Schmidt

• [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) (Tuesday, 1 October)

Kyle Evans

• Re: [whatwg/fetch] Add request Content-Length to PerformanceResourceTiming entries (Issue #1777) (Tuesday, 29 October)

L. David Baron

• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 31 October)
• Re: [whatwg/dom] Methods on ChildNode and ParentNode that take `(Node or DOMString)... nodes` should not use an intermediate DocumentFragment (Issue #1313) (Friday, 4 October)
• Re: [whatwg/dom] Methods on ChildNode and ParentNode that take `(Node or DOMString)... nodes` should not use an intermediate DocumentFragment (Issue #1313) (Friday, 4 October)
• [whatwg/dom] Methods on ChildNode and ParentNode that take `(Node or DOMString)... nodes` should not use an intermediate DocumentFragment (Issue #1313) (Friday, 4 October)

Lea Verou

• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Tuesday, 29 October)
• Re: [w3ctag/design-reviews] View Transition Classes (Issue #938) (Monday, 28 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Friday, 25 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Friday, 25 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Friday, 25 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Tuesday, 22 October)
• Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283) (Friday, 4 October)
• Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283) (Friday, 4 October)

Makoto Kato

• Re: [w3c/screen-orientation] Add can-lock-orientation media feature to detect if locking is possible (Issue #206) (Friday, 18 October)

Marcos Cáceres

• [w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880) (Thursday, 31 October)
• Re: [w3c/manifest] Require document to be in scope to be styled by the manifest (#791) (Thursday, 31 October)
• Re: [w3c/manifest] Require document to be in scope to be styled by the manifest (#791) (Thursday, 31 October)
• Re: [w3c/manifest] Require document to be in scope to be styled by the manifest (#791) (Thursday, 31 October)
• [w3c/manifest] Unbind computed id from start_url (Issue #1148) (Monday, 14 October)
• Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217) (Thursday, 10 October)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Thursday, 10 October)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Thursday, 10 October)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Thursday, 10 October)
• Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196) (Thursday, 10 October)

Marijn Kruisselbrink

• Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996) (Monday, 21 October)
• Re: [w3c/ServiceWorker] Job promise is an ECMAScript type, not WebIDL (Issue #1731) (Thursday, 3 October)

Mark Nottingham

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Monday, 28 October)
• Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770) (Friday, 11 October)
• Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770) (Monday, 7 October)

Mark S. Miller

• Re: [w3ctag/design-reviews] Realms Initialization Control (Issue #985) (Wednesday, 16 October)

Martin Thomson

• Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Wednesday, 30 October)
• Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005) (Wednesday, 30 October)
• Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001) (Tuesday, 29 October)
• Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001) (Tuesday, 29 October)
• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) (Tuesday, 29 October)
• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) (Tuesday, 29 October)
• Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001) (Tuesday, 29 October)
• Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002) (Wednesday, 23 October)
• Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002) (Wednesday, 23 October)
• Re: [w3ctag/design-reviews] FYI Private State Token API Permissions Policy Default Allowlist Wildcard (Issue #990) (Tuesday, 22 October)
• Re: [w3ctag/design-reviews] FYI Private State Token API Permissions Policy Default Allowlist Wildcard (Issue #990) (Tuesday, 22 October)
• Re: [w3ctag/design-reviews] Early design review: Future browsing context group dependency hint (Issue #979) (Tuesday, 22 October)
• Re: [w3ctag/design-reviews] Early design review: Future browsing context group dependency hint (Issue #979) (Tuesday, 22 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Thursday, 17 October)
• Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995) (Wednesday, 16 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Wednesday, 16 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Wednesday, 16 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Tuesday, 15 October)
• Re: [w3ctag/design-reviews] Vibration API (Issue #971) (Wednesday, 9 October)
• Re: [w3ctag/design-reviews] Vibration API (Issue #971) (Wednesday, 9 October)
• Re: [w3ctag/design-reviews] Vibration API (Issue #971) (Wednesday, 9 October)
• Re: [w3ctag/design-reviews] Early design review: Future browsing context group dependency hint (Issue #979) (Tuesday, 8 October)

Masayuki Nakano

• Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468) (Friday, 18 October)
• Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468) (Wednesday, 2 October)

Mason Freed

• Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078) (Tuesday, 15 October)

Matt Giuca

• Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996) (Wednesday, 23 October)
• Re: [w3c/manifest] Add members for localization (PR #1101) (Tuesday, 8 October)

Matt Reynolds

• Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217) (Friday, 11 October)
• Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217) (Friday, 11 October)
• Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217) (Thursday, 10 October)
• [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217) (Thursday, 10 October)
• [w3c/gamepad] eventInitDict parameter in GamepadEvent constructor should be optional (Issue #216) (Thursday, 10 October)

Matteo Collina

• Re: [whatwg/fetch] Allow request take AsyncIterable body? (#1291) (Thursday, 10 October)

Matthew Phillips

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

Matthew Tylee Atkinson

• Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962) (Wednesday, 30 October)
• Re: [w3ctag/design-reviews] [HTML] Canvas place element (Issue #997) (Monday, 21 October)
• Re: [w3ctag/design-reviews] Element Capture (Issue #954) (Wednesday, 9 October)

Meghan Denny

• Re: [whatwg/encoding] In blink, we only do the lookup by frame name in the local process. So in all cases where we host the navigation in a different process, the lookup by name just never works. (Issue #337) (Wednesday, 30 October)
• Re: [whatwg/webidl] conda (Issue #1442) (Monday, 14 October)
• Re: [whatwg/streams] https://www.facebook.com/pages/Ptsunan-Rubbre-Pabrik-Getah-Karet-Palembang-Kertapati/499702870401821?mibextid=rS40aB7S9Ucbxw6v (Issue #1328) (Friday, 4 October)
• Re: [whatwg/streams] https://www.facebook.com/pages/Ptsunan-Rubbre-Pabrik-Getah-Karet-Palembang-Kertapati/499702870401821?mibextid=rS40aB7S9Ucbxw6v (Issue #1328) (Friday, 4 October)

Michael Ficarra

• [whatwg/streams] Editorial: replace uses of the Type macro with is-a tests (PR #1330) (Monday, 28 October)
• [whatwg/webidl] Editorial: replace uses of the Type macro with is-a tests (PR #1447) (Monday, 28 October)

Michael Hagood

• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Friday, 18 October)

Michael Warren

• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Tuesday, 29 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Tuesday, 29 October)

Michnia611

• Re: [whatwg/fetch] Make get, decode, and split handle edge cases correctly (3153e5e) (Wednesday, 2 October)

Mike Jackson

• Re: [w3ctag/design-reviews] systemEntropy addition to PerformanceNavigationTiming (Issue #878) (Thursday, 17 October)

Mike West

• Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440) (Tuesday, 8 October)
• Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440) (Monday, 7 October)
• [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440) (Monday, 7 October)

minfrin

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 2 October)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 2 October)

Ming-Ying Chung

• Re: [whatwg/fetch] Refactor quota based on new explainer (66d4fc1) (Tuesday, 29 October)

Ms2ger

• [whatwg/webidl] ConvertToInt should take an explicit argument for its conversion approach (Issue #1439) (Thursday, 3 October)

Noam Rosenthal

• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 31 October)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 31 October)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 31 October)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 28 October)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Monday, 28 October)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Friday, 25 October)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Friday, 25 October)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 24 October)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 24 October)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 24 October)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 24 October)
• Re: [whatwg/fetch] Deferred fetching (PR #1647) (Thursday, 24 October)
• Re: [whatwg/fetch] Response body being null on 204/205/304 etc doesn't match any implementation (Issue #1779) (Thursday, 24 October)
• [whatwg/fetch] Response body being null on 204/205/304 etc doesn't match any implementation (Issue #1779) (Wednesday, 23 October)
• [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001) (Thursday, 3 October)

Nolan Lawson

• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Thursday, 31 October)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Tuesday, 29 October)
• Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043) (Saturday, 12 October)
• Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224) (Wednesday, 2 October)

Oliver Dunk

• Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Thursday, 31 October)

Patrick McDougle

• Re: [whatwg/dom] Should there be a declarative version of adoptedStyleSheets? (#910) (Wednesday, 9 October)

Paul Draper

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

Peter H. Jin

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 9 October)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Wednesday, 2 October)

Peter Linss

• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) (Tuesday, 29 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Monday, 14 October)

phumai98

• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) (Thursday, 31 October)

Pierre Ossman (ThinLinc team)

• Re: [w3c/uievents] Dead key symbols not included in KeyboardEvent (Issue #343) (Monday, 21 October)

Poetic29

• [w3c/manifest] Up Dating a Galaxy A13a 5GHz Repository (Issue #1146) (Thursday, 3 October)

Rachel Andrew

• Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003) (Tuesday, 15 October)

Rick Byers

• Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440) (Monday, 7 October)

Rob Eisenberg

• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076) (Sunday, 13 October)
• Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076) (Sunday, 13 October)

robglidden

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Thursday, 3 October)
• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Thursday, 3 October)

Ryosuke Niwa

• Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Thursday, 31 October)
• [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Thursday, 31 October)
• Re: [w3c/selection-api] Editorial: Correctly reference `{{Document/getSelection()}}` (PR #339) (Wednesday, 30 October)
• Re: [w3c/selection-api] Editorial: Correctly reference `{{Document/getSelection()}}` (PR #339) (Wednesday, 30 October)
• Re: [w3c/selection-api] Editorial: Correctly reference `{{Document/getSelection()}}` (PR #339) (Wednesday, 30 October)
• Re: [w3c/selection-api] Clarify association between a selection and its range (#2) (Monday, 21 October)
• Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081) (Wednesday, 16 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [w3c/selection-api] Improve selection.isCollapsed (Issue #337) (Monday, 7 October)
• Re: [w3c/selection-api] Improve selection.isCollapsed (Issue #337) (Monday, 7 October)
• Re: [WICG/webcomponents] Manage pseudo class matching state for custom elements (#813) (Friday, 4 October)
• Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283) (Friday, 4 October)

Sainan

• Re: [w3ctag/design-reviews] Cryptographically secure random UUIDs (#623) (Sunday, 13 October)

Sasha Firsov

• Re: [WICG/webcomponents] Anonymous Custom Elements (Issue #1074) (Friday, 18 October)

Sean Feng

• Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336) (Thursday, 17 October)
• Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336) (Sunday, 6 October)
• Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336) (Tuesday, 1 October)

Sean4572435243

• Re: [w3c/ServiceWorker] _Deleted_ (Issue #1733) (Monday, 21 October)
• [w3c/ServiceWorker] after upgrading to 8.0.10, Blazor publishing with AOT:true freezes when trying to precompile System.Private.CoreLib.dll (Issue #1733) (Monday, 21 October)

Shunya Shishido

• Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737) (Wednesday, 2 October)

sideshowbarker

• Re: [whatwg/webidl] Fix Iterator prototype reference (PR #1446) (Tuesday, 29 October)

smaug----

• Re: [whatwg/dom] Methods on ChildNode and ParentNode that take `(Node or DOMString)... nodes` should not use an intermediate DocumentFragment (Issue #1313) (Wednesday, 9 October)
• Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283) (Friday, 4 October)

Srabon Chowdhury

• Re: [whatwg/dom] Document.defaultCharset (#58) (Friday, 25 October)
• Re: [whatwg/dom] Document.defaultCharset (#58) (Friday, 25 October)

Steven Becker

• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) (Tuesday, 22 October)
• Re: [w3c/IndexedDB] Add descending order for getAll() and getAllKeys() (#130) (Monday, 14 October)
• Re: [w3c/IndexedDB] Add direction option to getAll() and getAllKeys() (Issue #427) (Monday, 14 October)
• Re: [w3c/IndexedDB] Add direction option to getAll() and getAllKeys() (Issue #427) (Monday, 14 October)
• Re: [w3c/IndexedDB] Allow indexing on Request/Response properties (#305) (Tuesday, 1 October)
• [w3c/ServiceWorker] Should IndexedDB allow indexing on Request/Response properties (Issue #1730) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] boolean should be a valid key (#76) (Tuesday, 1 October)
• [w3c/IndexedDB] Support Temporal as key/value (Issue #429) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] Why is delete() disallowed for key cursors? (#62) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] Add IDBCursor.close() (#185) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] Streaming data to/from IndexedDB (Issue #419) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] Projection Support (#366) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] Projection Support (#366) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] Add a new event `onbeforecommit` on the interface IDBTransaction (#314) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] Add a new event `onbeforecommit` on the interface IDBTransaction (#314) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] Add a new event `onbeforecommit` on the interface IDBTransaction (#314) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] Add a new event `onbeforecommit` on the interface IDBTransaction (#314) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] Batch get/getAll (Issue #376) (Tuesday, 1 October)
• Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) (Tuesday, 1 October)
• [w3c/IndexedDB] Configurable task priority for IDBRequest and IDBTransaction? (Issue #428) (Tuesday, 1 October)
• [w3c/IndexedDB] Add direction option to getAll() and getAllKeys() (Issue #427) (Tuesday, 1 October)

Tab Atkins Jr.

• Re: [WICG/webcomponents] [exportparts] support exporting via wildcards `exportparts="*, primary-*"` (Issue #1051) (Wednesday, 2 October)

Tantek Çelik

• [w3ctag/design-reviews] Vision for W3C: request horizontal architectural review and wide TAG review (Issue #1008) (Thursday, 24 October)

Thai Pangsakulyanont

• Re: [whatwg/fetch] Allow request take AsyncIterable body? (#1291) (Thursday, 10 October)

thesmartwon

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

Timothy Hatcher

• Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321) (Thursday, 31 October)

Tito

• Re: [WICG/webcomponents] . (Issue #1079) (Thursday, 17 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] getOuterHTML (Issue #1079) (Wednesday, 16 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] getOuterHTML (Issue #1079) (Wednesday, 16 October)
• [WICG/webcomponents] getOutterHTML (Issue #1079) (Wednesday, 16 October)

Travis Leithead

• Re: [w3c/uievents-code] CFC to publish UI Events KeyboardEvent code Values as a Proposed Recommendation in the WebApps WG (Issue #43) (Wednesday, 16 October)

Tristan Fraipont

• Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318) (Thursday, 17 October)
• Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318) (Wednesday, 16 October)

W3C Bot

• Re: [w3c/FileAPI] Removed extra "be" in sentence. (PR #200) (Thursday, 24 October)

Westbrook Johnson

• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Thursday, 31 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Friday, 25 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Friday, 25 October)
• Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000) (Wednesday, 23 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Wednesday, 23 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080) (Wednesday, 16 October)
• Re: [WICG/webcomponents] getOuterHTML (Issue #1079) (Wednesday, 16 October)
• Re: [w3ctag/design-reviews] Reference Target (Issue #961) (Tuesday, 15 October)
• Re: [WICG/webcomponents] [exportparts] support exporting via wildcards `exportparts="*, primary-*"` (Issue #1051) (Wednesday, 2 October)
• Re: [WICG/webcomponents] Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements (Issue #1073) (Tuesday, 1 October)
• Re: [WICG/webcomponents] Possibile way for cross shadowDom exclusive interactive elements (Issue #1054) (Tuesday, 1 October)
• Re: [WICG/webcomponents] [exportparts] support exporting via wildcards `exportparts="*, primary-*"` (Issue #1051) (Tuesday, 1 October)
• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Tuesday, 1 October)
• Re: [WICG/webcomponents] Add delegatesLabel and a content attribute to specify the label element within a shadow tree (#916) (Tuesday, 1 October)
• Re: [WICG/webcomponents] Add delegatesLabel and a content attribute to specify the label element within a shadow tree (#916) (Tuesday, 1 October)
• Re: [WICG/webcomponents] RfC: An alternative approach to accessibility across shadow boundaries (#898) (Tuesday, 1 October)
• Re: [WICG/webcomponents] RfC: An alternative approach to accessibility across shadow boundaries (#898) (Tuesday, 1 October)
• Re: [WICG/webcomponents] [a11y]: An exhaustive look at support for using HTMLInputElement with Web Components (Issue #996) (Tuesday, 1 October)
• Re: [WICG/webcomponents] [Proposal] Stylesheet Observer (Issue #1041) (Tuesday, 1 October)
• Re: [WICG/webcomponents] Allows slots to ignore surrounding whitespace (Issue #1056) (Tuesday, 1 October)
• Re: [WICG/webcomponents] What's the right target of anchor link inside shadowDom (Issue #1048) (Tuesday, 1 October)
• Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065) (Tuesday, 1 October)
• Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065) (Tuesday, 1 October)

Xiaoqian Wu

• Re: [w3c/editing] CfC: Enable automated publication system for all Web Editing WG specs (Issue #471) (Monday, 21 October)
• Re: [w3c/editing] CfC: Enable automated publication system for all Web Editing WG specs (Issue #471) (Monday, 21 October)

Yoav Weiss

• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Tuesday, 22 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Thursday, 17 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Wednesday, 16 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Wednesday, 16 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Wednesday, 16 October)
• Re: [w3ctag/design-reviews] Multiple import maps (Issue #980) (Wednesday, 16 October)

Yuval

• [WICG/webcomponents] A components framework based on <template> (Issue #1077) (Monday, 14 October)

Ziad El Khoury Hanna

• Re: [w3c/uievents] Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) (#181) (Friday, 4 October)
• Re: [w3c/uievents] Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) (#181) (Friday, 4 October)

Last message date: Thursday, 31 October 2024 22:59:13 UTC