public-webapps-github@w3.org from July 2026 by author

Addison Phillips

• Re: [w3c/manifest] Manifest name: USVString or not? (Issue #1228) (Thursday, 23 July)
• [w3c/manifest] Have an "Internationalization Considerations" section? (Issue #1232) (Thursday, 23 July)
• [w3c/manifest] Use template for character references (Issue #1231) (Thursday, 23 July)
• [w3c/manifest] Are `*_localized` items clearly allowed in shortcut items? (Issue #1230) (Thursday, 23 July)
• [w3c/manifest] Provide examples of non-ASCII in the path and host parts of `id` (Issue #1229) (Thursday, 23 July)
• [w3c/manifest] "cannot be used together" editing woes (Issue #1227) (Thursday, 9 July)

afriadishariff-lab

• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Thursday, 16 July)
• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Thursday, 16 July)

Alex Russell

• Re: [w3ctag/design-reviews] Media Capture Capability Elements (part of PEPC) (Issue #1218) (Monday, 27 July)

Alexander Kyereboah

• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Tuesday, 7 July)

Ana Sollano Kim

• Re: [w3ctag/design-reviews] Incubation: Platform-provided behaviors for custom elements (Issue #1219) (Thursday, 23 July)

Andrew Sutherland

• Re: [w3c/ServiceWorker] Add race-network-and-cache source to static routing api. (PR #1764) (Friday, 31 July)
• Re: [w3c/ServiceWorker] Should a service worker be allowed to register new service workers? (#1117) (Friday, 3 July)

Andrew Whalley

• Re: [w3ctag/design-reviews] Other Spec Review: CRA web browser standard (Issue #1239) (Thursday, 30 July)

Anne van Kesteren

• [whatwg/dom] Order shadow root concepts consistently (PR #1496) (Saturday, 18 July)
• Re: [whatwg/dom] Editorial: lean on early return in attach a shadow root (PR #1495) (Saturday, 18 July)
• [whatwg/dom] Editorial: lean on early return in attach a shadow root (PR #1495) (Saturday, 18 July)
• Re: [whatwg/webidl] Is a function signature with a parameter type `(DOMString or Interface)` a footgun? (Issue #1604) (Saturday, 18 July)
• Re: [whatwg/fullscreen] Review Draft Publication: July 2026 (PR #263) (Friday, 17 July)
• [whatwg/fullscreen] Review Draft Publication: July 2026 (PR #263) (Friday, 17 July)
• Re: [whatwg/dom] Define the realm of nodes (#977) (Friday, 17 July)
• Re: [whatwg/dom] Create nodes in the realm of the document they are created for (PR #1491) (Friday, 17 July)
• Re: [whatwg/dom] Restore active custom element constructor map entries after construction (PR #1494) (Friday, 17 July)
• Re: [whatwg/dom] Restore active custom element constructor map entries after construction (PR #1494) (Friday, 17 July)
• [whatwg/dom] Restore active custom element constructor map entries after construction (PR #1494) (Friday, 17 July)
• Re: [whatwg/dom] Clarify create an element assertion (Issue #1338) (Wednesday, 15 July)
• Re: [whatwg/dom] Clarify create an element assertion (PR #1485) (Wednesday, 15 July)
• Re: [whatwg/dom] Clarify create an element assertion (PR #1485) (Wednesday, 15 July)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Tuesday, 14 July)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Tuesday, 14 July)
• Re: [whatwg/dom] Define a mapping to a Selectors Element Tree (#542) (Tuesday, 14 July)
• Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926) (Tuesday, 14 July)
• Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926) (Monday, 13 July)
• Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926) (Monday, 13 July)
• Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926) (Monday, 13 July)
• [whatwg/dom] Factor out find a named element and rename a collection's nodes (PR #1493) (Sunday, 12 July)
• Re: [whatwg/dom] Define a mapping to a Selectors Element Tree (#542) (Sunday, 12 July)
• [whatwg/dom] Copy a document's base URL when cloning (PR #1492) (Saturday, 11 July)
• Re: [whatwg/dom] `event.target` not cleared if event is not fired on `ShadowRoot` (Issue #1072) (Saturday, 11 July)
• Re: [whatwg/dom] `event.target` not cleared if event is not fired on `ShadowRoot` (Issue #1072) (Saturday, 11 July)
• Re: [whatwg/dom] Define the realm of nodes (#977) (Friday, 10 July)
• Re: [whatwg/dom] Define the realm of nodes (#977) (Friday, 10 July)
• Re: [whatwg/dom] Create nodes in the realm of the document they are created for (PR #1491) (Friday, 10 July)
• Re: [whatwg/dom] Create nodes in the realm of the document they are created for (PR #1491) (Friday, 10 July)
• [whatwg/dom] Create nodes in the realm of the document they are created for (PR #1491) (Friday, 10 July)
• Re: [whatwg/dom] Adopting children of an intentional null shadow root goes wrong (Issue #1429) (Thursday, 9 July)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Thursday, 9 July)
• Re: [whatwg/dom] replaceChildren can not replace a Document's documentElement (Issue #1045) (Thursday, 9 July)
• Re: [whatwg/dom] Let replaceChildren() replace a document's children (PR #1487) (Thursday, 9 July)
• Re: [whatwg/dom] What does adoptNode() return for DocumentFragment? (#813) (Thursday, 9 July)
• Re: [whatwg/dom] Adopt a DocumentFragment with a host like any other node (PR #1486) (Thursday, 9 July)
• Re: [whatwg/webidl] Is a function signature with a parameter type `(DOMString or Interface)` a footgun? (Issue #1604) (Thursday, 9 July)
• Re: [whatwg/dom] Editorial: type arguments in event dispatch algorithms (PR #1490) (Thursday, 9 July)
• Re: [w3c/permissions] Rename document (Issue #478) (Thursday, 9 July)
• [whatwg/dom] Editorial: type arguments in event dispatch algorithms (PR #1490) (Thursday, 9 July)
• Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707) (Thursday, 9 July)
• Re: [whatwg/dom] Editorial: name event path items and clarify target selection (PR #1489) (Thursday, 9 July)
• Re: [w3c/permissions] Rename document (Issue #478) (Thursday, 9 July)
• [whatwg/dom] Editorial: name event path items and clarify target selection (PR #1489) (Thursday, 9 July)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Thursday, 9 July)
• Re: [whatwg/dom] replaceChild() has odd mutation observer behavior after #754 (#814) (Thursday, 9 July)
• Re: [whatwg/dom] Adopt node before removing child in replace (PR #1488) (Thursday, 9 July)
• Re: [whatwg/dom] Adopt node before removing child in replace (PR #1488) (Wednesday, 8 July)
• [whatwg/dom] Adopt node before removing child in replace (PR #1488) (Wednesday, 8 July)
• Re: [whatwg/dom] Let replaceChildren() replace a document's children (PR #1487) (Wednesday, 8 July)
• [whatwg/dom] Let replaceChildren() replace a document's children (PR #1487) (Wednesday, 8 July)
• Re: [whatwg/dom] Trouble understanding a parable of specification, under the "ensure pre-insertion validity" list of steps (#870) (Wednesday, 8 July)
• Re: [whatwg/dom] Editorial: improve ensure pre-insert validity (PR #1484) (Wednesday, 8 July)
• Re: [whatwg/dom] Editorial: improve ensure pre-insert validity (PR #1484) (Wednesday, 8 July)
• [whatwg/dom] Adopt a DocumentFragment with a host like any other node (PR #1486) (Wednesday, 8 July)
• Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819) (Wednesday, 8 July)
• Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819) (Wednesday, 8 July)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Wednesday, 8 July)
• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Wednesday, 8 July)
• Re: [whatwg/dom] Define "has event listener" operation (#453) (Wednesday, 8 July)
• Re: [whatwg/dom] Improving "find slottables" (Issue #1063) (Wednesday, 8 July)
• Re: [whatwg/dom] Improving "find slottables" (Issue #1063) (Wednesday, 8 July)
• Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564) (Wednesday, 8 July)
• Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564) (Wednesday, 8 July)
• Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564) (Wednesday, 8 July)
• Re: [whatwg/dom] Which target could we expose in Event Timing? (#838) (Wednesday, 8 July)
• Re: [whatwg/dom] Increase the ability to query whether the host environment supports a specific event (#968) (Wednesday, 8 July)
• Re: [whatwg/dom] Increase the ability to query whether the host environment supports a specific event (#968) (Wednesday, 8 July)
• Re: [whatwg/dom] replaceChildren can not replace a Document's documentElement (Issue #1045) (Wednesday, 8 July)
• [whatwg/dom] Clarify create an element assertion (PR #1485) (Wednesday, 8 July)
• Re: [whatwg/dom] Proposal: Allow WebIDL bindings to expose method parameters' types (Issue #1182) (Wednesday, 8 July)
• Re: [whatwg/dom] Proposal: A new way to do feature detection for members (Issue #1181) (Wednesday, 8 July)
• Re: [whatwg/dom] Proposal: Allow WebIDL binding to expose parameters' types and enums' values (Issue #1183) (Wednesday, 8 July)
• Re: [whatwg/dom] Variable strength aborting (Issue #1215) (Wednesday, 8 July)
• Re: [whatwg/dom] Variable strength aborting (Issue #1215) (Wednesday, 8 July)
• Re: [whatwg/dom] Make it possible to wrap [parts of] the contents of a <textarea> or <input> in a Range (Issue #1375) (Wednesday, 8 July)
• Re: [whatwg/dom] Editorial: improve ensure pre-insert validity (PR #1484) (Wednesday, 8 July)
• [whatwg/dom] Editorial: improve ensure pre-insert validity (PR #1484) (Wednesday, 8 July)
• Re: [whatwg/dom] Please add the links to the old versions? (Issue #1067) (Wednesday, 8 July)
• Re: [whatwg/dom] Blame stopped working (Issue #1367) (Tuesday, 7 July)
• Re: [whatwg/dom] Blame stopped working (Issue #1367) (Tuesday, 7 July)
• Re: [whatwg/dom] Ranges and Attr nodes (#607) (Tuesday, 7 July)
• Re: [whatwg/dom] Expose document fragment serialization algorithm (#965) (Tuesday, 7 July)
• Re: [whatwg/dom] Expose document fragment serialization algorithm (#965) (Tuesday, 7 July)
• Re: [whatwg/dom] Strange behavior with `insertBefore` vs `appendChild` and transitions (#880) (Tuesday, 7 July)
• Re: [whatwg/dom] Strange behavior with `insertBefore` vs `appendChild` and transitions (#880) (Tuesday, 7 July)
• Re: [whatwg/dom] Element.replaceChild should allow for `old, new` argument ordering if `new` is a new element and `old` is a child of Element (#847) (Tuesday, 7 July)
• Re: [whatwg/dom] Element.replaceChild should allow for `old, new` argument ordering if `new` is a new element and `old` is a child of Element (#847) (Tuesday, 7 July)
• Re: [whatwg/dom] classes are compared without Unicode normalization (#793) (Tuesday, 7 July)
• Re: [whatwg/dom] classes are compared without Unicode normalization (#793) (Tuesday, 7 July)
• Re: [whatwg/dom] Why is `createProcessingInstruction(…)` allowed in HTML, but `createCDATASection(…)` isn’t? (#798) (Tuesday, 7 July)
• Re: [whatwg/dom] Why is `createProcessingInstruction(…)` allowed in HTML, but `createCDATASection(…)` isn’t? (#798) (Tuesday, 7 July)
• Re: [whatwg/dom] Address feedback from Travis and Sangwhan (#702) (Tuesday, 7 July)
• Re: [whatwg/dom] Editorial: address assorted feedback (PR #1483) (Tuesday, 7 July)
• [whatwg/dom] Editorial: address assorted feedback (PR #1483) (Tuesday, 7 July)
• Re: [whatwg/dom] Refactor toggle attribute (#663) (Tuesday, 7 July)
• Re: [whatwg/dom] Refactor toggle attribute (#663) (Tuesday, 7 July)
• Re: [whatwg/dom] Abstract common logic in toggleAttribute() and setAttribute()? (#657) (Tuesday, 7 July)
• Re: [whatwg/dom] Abstract common logic in toggleAttribute() and setAttribute()? (#657) (Tuesday, 7 July)
• Re: [whatwg/dom] "To validate and extract a namespace and qualifiedName" could use clarification about case-insensitivity (#680) (Tuesday, 7 July)
• Re: [whatwg/dom] "To validate and extract a namespace and qualifiedName" could use clarification about case-insensitivity (#680) (Tuesday, 7 July)
• Re: [whatwg/dom] Allow <menu>, <ul>, <ol>, <li> to attach shadow (#676) (Tuesday, 7 July)
• Re: [whatwg/dom] Allow <menu>, <ul>, <ol>, <li> to attach shadow (#676) (Tuesday, 7 July)
• Re: [whatwg/dom] Make "inner invoke" use "remove an event listener" (#758) (Tuesday, 7 July)
• Re: [whatwg/dom] Make "inner invoke" use "remove an event listener" (#758) (Tuesday, 7 July)
• Re: [whatwg/dom] Make "inner invoke" use "remove an event listener" (#651) (Tuesday, 7 July)
• Re: [whatwg/dom] Make "inner invoke" use "remove an event listener" (#651) (Tuesday, 7 July)
• Re: [whatwg/dom] document.open()'s mutation event suppression (#640) (Tuesday, 7 July)
• Re: [whatwg/dom] Editorial: consider linking "present" consistently (#574) (Tuesday, 7 July)
• Re: [whatwg/dom] Editorial: remove remaining dictionary "is present" usage (PR #1482) (Tuesday, 7 July)
• [whatwg/dom] Editorial: remove remaining dictionary "is present" usage (PR #1482) (Tuesday, 7 July)
• Re: [whatwg/dom] Node Tree section should probably include Attr (#457) (Tuesday, 7 July)
• Re: [whatwg/dom] Node Tree section should probably include Attr (#457) (Tuesday, 7 July)
• Re: [whatwg/dom] Ranges and Attr nodes (#607) (Tuesday, 7 July)
• Re: [whatwg/dom] Use `commonAncestorContainer` in concept-range-clone (#56) (Tuesday, 7 July)
• Re: [whatwg/dom] Editorial: abstract getting the common ancestor (PR #1481) (Tuesday, 7 July)
• Re: [whatwg/dom] Editorial: abstract getting the common ancestor (PR #1481) (Tuesday, 7 July)
• [whatwg/dom] Editorial: abstract getting the common ancestor (PR #1481) (Tuesday, 7 July)
• Re: [whatwg/dom] Restore deep cloning of shadow root contents. (PR #1480) (Monday, 6 July)
• Re: [whatwg/dom] Restore deep cloning of shadow root contents. (PR #1480) (Monday, 6 July)
• Re: [whatwg/url] Report a validation error for IPv4 addresses from non-ASCII input (PR #925) (Monday, 6 July)
• Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926) (Saturday, 4 July)
• Re: [whatwg/dom] Update element adoption logic for scoped registry (PR #1437) (Friday, 3 July)
• Re: [whatwg/dom] Editorial: make adopt traverse the tree less (PR #1427) (Friday, 3 July)
• Re: [whatwg/dom] Remove mentions of XSLT from the DOM spec (PR #1400) (Friday, 3 July)
• Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479) (Friday, 3 July)
• Re: [whatwg/webidl] Update PropertyDescriptor [[Get]]/[[Set]] to [[Getter]]/[[Setter]] (PR #1613) (Friday, 3 July)
• Re: [whatwg/webidl] Update PropertyDescriptor [[Get]]/[[Set]] to [[Getter]]/[[Setter]] (PR #1613) (Friday, 3 July)
• Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479) (Friday, 3 July)
• Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479) (Friday, 3 July)
• Re: [whatwg/fetch] Anchor permanence for https://fetch.spec.whatwg.org/#methods (Issue #1932) (Thursday, 2 July)
• Re: [whatwg/fetch] Anchor permanence for https://fetch.spec.whatwg.org/#methods (Issue #1932) (Thursday, 2 July)
• Re: [whatwg/fetch] Meta: make methods a required ID (PR #1939) (Thursday, 2 July)
• [whatwg/fetch] Meta: make methods a required ID (PR #1939) (Thursday, 2 July)
• Re: [w3c/ServiceWorker] Redesign of "extract header list values" expected (#1360) (Thursday, 2 July)
• Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478) (Thursday, 2 July)
• Re: [whatwg/url] Meta: UTS46 feedback (Issue #744) (Thursday, 2 July)
• Re: [whatwg/url] Meta: UTS46 feedback (Issue #744) (Thursday, 2 July)
• Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478) (Thursday, 2 July)
• Re: [whatwg/dom] Add and export get an element by ID (PR #1476) (Thursday, 2 July)
• Re: [whatwg/dom] Fix NodeIterator pre-remove steps for ancestors of root (PR #1477) (Thursday, 2 July)
• Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479) (Thursday, 2 July)
• [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479) (Thursday, 2 July)
• Re: [whatwg/dom] Fix NodeIterator pre-remove steps for ancestors of root (PR #1477) (Thursday, 2 July)
• Re: [whatwg/dom] NodeIterator's pre-removing steps does not match browsers (#907) (Thursday, 2 July)
• Re: [whatwg/dom] Fix NodeIterator pre-remove steps for ancestors of root (PR #1477) (Thursday, 2 July)
• Re: [whatwg/url] Enumerate differences with URI & IRI in an appendix (PR #923) (Thursday, 2 July)
• [whatwg/url] Report a validation error for IPv4 addresses from non-ASCII input (PR #925) (Thursday, 2 July)
• Re: [whatwg/url] Close more gaps between URL writing and parser sections (PR #924) (Thursday, 2 July)
• Re: [whatwg/url] Close more gaps between URL writing and parser sections (PR #924) (Thursday, 2 July)
• Re: [whatwg/url] It is unlikely that the spec's two definitions of valid URL strings are equal (Issue #704) (Wednesday, 1 July)
• [whatwg/url] Close more gaps between URL writing and parser sections (PR #924) (Wednesday, 1 July)
• Re: [whatwg/url] Enumerate differences with URI & IRI in an appendix (PR #923) (Wednesday, 1 July)
• [whatwg/url] Enumerate differences with URI & IRI in an appendix (PR #923) (Wednesday, 1 July)
• Re: [whatwg/fetch] Integrating the HTTP QUERY method (RFC 10008): method normalization, CORS, and caching (Issue #1938) (Wednesday, 1 July)
• Re: [whatwg/url] Define valid IPv6-address string inline (PR #917) (Wednesday, 1 July)
• Re: [whatwg/url] RFC 4291 is not really sufficient to define "valid IPv6-address string" (Issue #916) (Wednesday, 1 July)
• Re: [whatwg/url] Define valid IPv6-address string inline (PR #917) (Wednesday, 1 July)
• Re: [whatwg/url] Valid domain needs to account for ending with a number (PR #918) (Wednesday, 1 July)
• Re: [whatwg/url] Valid domain needs to account for ending with a number (PR #918) (Wednesday, 1 July)
• Re: [whatwg/url] Make relative-URL-with-fragment string account for opaque-path base URLs (PR #920) (Wednesday, 1 July)
• Re: [whatwg/url] Path segments can be empty (PR #919) (Wednesday, 1 July)
• Re: [whatwg/url] What is an opaque path? (Issue #922) (Wednesday, 1 July)
• Re: [whatwg/url] A branch of the "ends in a number checker" cannot be hit (Issue #865) (Wednesday, 1 July)
• Re: [whatwg/url] Simplify ends in a number checker (PR #921) (Wednesday, 1 July)

anonghuser

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

antstar28-ui

• [whatwg/url] Ab (Issue #927) (Friday, 10 July)

aqwaaqz-pixel

• [whatwg/webidl] Intent to use Constants (Issue #1623) (Sunday, 26 July)

Ben Francis

• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 2 July)

Ben Kelly

• Re: [w3c/ServiceWorker] Should a service worker be allowed to register new service workers? (#1117) (Wednesday, 15 July)

Brian Kardell

• Re: [w3ctag/design-reviews] WG Revision: CSSPseudoElement (Issue #1233) (Wednesday, 15 July)
• Re: [w3ctag/design-reviews] WG Revision: CSSPseudoElement (Issue #1233) (Wednesday, 15 July)

carlaarchuleta707-lgtm

• Re: [whatwg/webidl] Intent to use Constants (Issue #1618) (Monday, 13 July)
• [whatwg/webidl] Intent to use Constants (Issue #1618) (Monday, 13 July)

Christian Biesinger

• Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) (Friday, 24 July)

Christian Liebel

• Re: [w3ctag/design-reviews] Other Spec Review: HTML menu elements (Issue #1242) (Friday, 10 July)
• [w3c/manifest] [DRAFT] Check against i18n Review Checklist (Issue #1223) (Thursday, 2 July)
• Re: [w3c/manifest] Redefine application context on top-level traversable (PR #1219) (Thursday, 2 July)
• Re: [w3c/manifest] chore: update SchemaStore URLs to www.schemastore.org (PR #1220) (Thursday, 2 July)
• Re: [w3c/manifest] chore: update SchemaStore URLs to www.schemastore.org (PR #1220) (Thursday, 2 July)
• Re: [w3c/manifest] chore: update SchemaStore URLs to www.schemastore.org (PR #1220) (Thursday, 2 July)
• [w3c/manifest] chore: update SchemaStore URLs to www.schemastore.org (PR #1220) (Thursday, 2 July)
• Re: [w3c/manifest] Redefine application context on top-level traversable (PR #1219) (Thursday, 2 July)
• Re: [w3c/manifest] Add `color_scheme_dark` member and themeable members (PR #1205) (Thursday, 2 July)
• Re: [w3ctag/design-reviews] Other Spec Review: CRA web browser standard (Issue #1239) (Wednesday, 1 July)

Copilot

• Re: [w3c/manifest] editorial: add missing assertion to chosen-display-mode algorithm (PR #1238) (Monday, 27 July)
• Re: [w3c/manifest] Editorial: don't reference WebIDL identifier (PR #1237) (Monday, 27 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 23 July)
• Re: [w3c/manifest] editorial: fix typos, grammar, and a stray definition (PR #1233) (Thursday, 23 July)
• Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224) (Thursday, 23 July)
• Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221) (Thursday, 23 July)

Dan Clark

• Re: [w3c/clipboard-apis] Remove clipboardchange event (and replace it possibly with a promise returning method) (Issue #228) (Friday, 31 July)
• Re: [w3c/clipboard-apis] Remove clipboardchange event (and replace it possibly with a promise returning method) (Issue #228) (Friday, 31 July)
• Re: [w3c/clipboard-apis] ClipboardChange even spec: Callout details for cross-origin iframes and fencedframes (Issue #226) (Friday, 31 July)
• Re: [w3c/clipboard-apis] ClipboardChange even spec: Callout details for cross-origin iframes and fencedframes (Issue #226) (Friday, 31 July)
• Re: [whatwg/dom] Add reference target to shadow root (PR #1353) (Wednesday, 29 July)
• [w3c/editing] When should metadata-content elements like <style> be editable? (Issue #546) (Thursday, 23 July)
• Re: [w3ctag/design-reviews] Other Spec Review: Responsively-sized iframes (Issue #1223) (Wednesday, 22 July)
• Re: [w3ctag/design-reviews] Other Spec Review: Responsively-sized iframes (Issue #1223) (Tuesday, 14 July)
• Re: [w3ctag/design-reviews] Other Spec Review: `textStream()` for `Blob` and `Body` (Issue #1236) (Wednesday, 8 July)
• Re: [w3ctag/design-reviews] Other Spec Review: `textStream()` for `Blob` and `Body` (Issue #1236) (Wednesday, 8 July)
• Re: [w3ctag/design-reviews] Other Spec Review: `textStream()` for `Blob` and `Body` (Issue #1236) (Tuesday, 7 July)

Daniel Ehrenberg

• Re: [w3ctag/design-reviews] Other Spec Review: CRA web browser standard (Issue #1239) (Wednesday, 22 July)
• Re: [w3ctag/design-reviews] Other Spec Review: CRA web browser standard (Issue #1239) (Tuesday, 14 July)

Daniel Murphy

• Re: [w3c/manifest] Have an "Internationalization Considerations" section? (Issue #1232) (Thursday, 23 July)
• Re: [w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234) (Thursday, 23 July)
• Re: [w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234) (Thursday, 23 July)
• Re: [w3c/manifest] Use template for character references (Issue #1231) (Thursday, 23 July)
• Re: [w3c/manifest] Format U+002F character references using W3C I18N template (PR #1235) (Thursday, 23 July)
• Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224) (Thursday, 23 July)
• [w3c/manifest] Format U+002F character references using W3C I18N template (PR #1235) (Thursday, 23 July)
• [w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234) (Thursday, 23 July)
• Re: [w3c/manifest] editorial: fix typos, grammar, and a stray definition (PR #1233) (Thursday, 23 July)
• Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221) (Thursday, 23 July)
• Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221) (Thursday, 23 July)
• Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221) (Thursday, 23 July)
• Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221) (Thursday, 23 July)
• Re: [w3c/manifest] chore: fix SchemaStore links and drop the embedded schema view (PR #1220) (Thursday, 23 July)
• Re: [w3c/manifest] chore: fix SchemaStore links and drop the embedded schema view (PR #1220) (Thursday, 23 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 23 July)
• Re: [w3c/manifest] chore: fix SchemaStore links and drop the embedded schema view (PR #1220) (Thursday, 2 July)
• Re: [w3c/manifest] Redefine application context on top-level traversable (PR #1219) (Thursday, 2 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 2 July)

David A

• Re: [w3ctag/design-reviews] Other Spec Review: CSS scroll-axis-lock (Issue #1248) (Friday, 24 July)
• [w3ctag/design-reviews] Other Spec Review: CSS scroll-axis-lock (Issue #1248) (Tuesday, 21 July)

dillonstreator

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

Domenic Denicola

• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Thursday, 16 July)
• Re: [whatwg/url] Report a validation error for IPv4 addresses from non-ASCII input (PR #925) (Sunday, 5 July)
• Re: [whatwg/url] It is unlikely that the spec's two definitions of valid URL strings are equal (Issue #704) (Thursday, 2 July)
• Re: [whatwg/url] Close more gaps between URL writing and parser sections (PR #924) (Thursday, 2 July)
• Re: [whatwg/url] Enumerate differences with URI & IRI in an appendix (PR #923) (Thursday, 2 July)
• Re: [whatwg/url] It is unlikely that the spec's two definitions of valid URL strings are equal (Issue #704) (Wednesday, 1 July)
• Re: [whatwg/url] Define valid IPv6-address string inline (PR #917) (Wednesday, 1 July)
• Re: [whatwg/url] Valid domain needs to account for ending with a number (PR #918) (Wednesday, 1 July)
• Re: [whatwg/url] Valid domain needs to account for ending with a number (PR #918) (Wednesday, 1 July)
• Re: [whatwg/url] Make relative-URL-with-fragment string account for opaque-path base URLs (PR #920) (Wednesday, 1 July)
• Re: [whatwg/url] Path segments can be empty (PR #919) (Wednesday, 1 July)
• Re: [whatwg/url] Simplify ends in a number checker (PR #921) (Wednesday, 1 July)

Dominic Farolino

• Re: [w3c/manifest] Manifest name: USVString or not? (Issue #1228) (Friday, 24 July)
• Re: [whatwg/dom] Clarify create an element assertion (PR #1485) (Wednesday, 15 July)
• [w3c/manifest] Manifest name: USVString or not? (Issue #1228) (Tuesday, 14 July)
• Re: [whatwg/dom] Adopt node before removing child in replace (PR #1488) (Thursday, 9 July)
• Re: [w3ctag/design-reviews] Other Spec Review: HTML menu elements (Issue #1242) (Wednesday, 1 July)

dwaltersbal-mlg

• [w3c/manifest] Create SECURITY.md (PR #1226) (Monday, 6 July)

Ehsan Toreini

• Re: [w3ctag/design-reviews] WG Revision: WebTransport (Issue #1212) (Friday, 24 July)
• Re: [w3ctag/design-reviews] Incubation: FedCM: Support showing third-party iframe origins in the UI (Issue #1136) (Friday, 24 July)
• Re: [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173) (Friday, 3 July)

Filip Skokan

• Re: [whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943) (Sunday, 26 July)

franatayoga26-lab

• [whatwg/webidl] Bocil smp (Issue #1621) (Thursday, 23 July)

Franklin Bridges

• [whatwg/webidl] Intent to use Constants (Issue #1620) (Saturday, 18 July)

freedebreuil

• Re: [w3ctag/design-reviews] Other Spec Review: Single-Axis Scroll Containers (Issue #1222) (Tuesday, 21 July)

Frédéric Wang Nélar

• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Tuesday, 28 July)
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Monday, 20 July)
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Wednesday, 15 July)
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Wednesday, 15 July)
• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Friday, 10 July)

github-actions[bot]

• [w3c/manifest] Tidied up document using tidy-html5 (PR #1236) (Thursday, 23 July)
• [w3c/manifest] Tidied up document using tidy-html5 (PR #1222) (Thursday, 2 July)

Greg Gibson

• Re: [WICG/webcomponents] Reference Target "phase 2": seeking feedback and use cases (Issue #1111) (Thursday, 2 July)

Gregory Terzian

• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Sunday, 12 July)
• [w3c/ServiceWorker] cache and cache-storage algos forgets to queue a task to resolve promise. (Issue #1831) (Thursday, 9 July)

guidou

• [w3ctag/design-reviews] Incubation: WebRTC Diagnostic Logging (Issue #1250) (Monday, 27 July)

Guillaume

• [whatwg/dom] Scope-match a selectors string including a pseudo-element selector (Issue #1497) (Tuesday, 21 July)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Monday, 20 July)

Hamza Ironside

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

Heather Flanagan

• Re: [w3ctag/design-reviews] Incubation: Autofill Event (Issue #1197) (Sunday, 19 July)

J. King

• Re: [whatwg/url] What is an opaque path? (Issue #922) (Thursday, 2 July)

James C. Wise

• Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926) (Tuesday, 14 July)
• Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926) (Tuesday, 14 July)
• Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926) (Tuesday, 14 July)
• Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926) (Monday, 13 July)
• Re: [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926) (Monday, 13 July)
• Re: [whatwg/url] Ab (Issue #927) (Friday, 10 July)
• [whatwg/url] Can a URL have a segmented path with zero segments? (Issue #926) (Saturday, 4 July)

James M Snell

• Re: [whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943) (Tuesday, 28 July)
• Re: [whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943) (Sunday, 26 July)
• [whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943) (Tuesday, 21 July)
• Re: [whatwg/streams] Revisiting ReadableStream.from(syncIter) and ReadableStream.from(str) (Issue #1376) (Thursday, 16 July)
• [whatwg/streams] Revisiting ReadableStream.from(syncIter) and ReadableStream.from(str) (Issue #1376) (Monday, 13 July)
• [whatwg/fetch] Add onInformation interim response support (PR #1942) (Saturday, 11 July)
• [whatwg/fetch] Sending trailers (PR #1941) (Saturday, 11 July)
• Re: [whatwg/fetch] Add .trailers to Response/Request (PR #1940) (Saturday, 11 July)
• Re: [whatwg/fetch] Trailer support in the API (#981) (Saturday, 11 July)
• Re: [whatwg/fetch] Add .trailers to Response/Request (PR #1940) (Saturday, 11 July)
• [whatwg/fetch] Add .trailers to Response/Request (PR #1940) (Saturday, 11 July)

Jibb Smart

• Re: [w3c/gamepad] Add device orientation support (Issue #211) (Wednesday, 15 July)

Joey Arhar

• Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413) (Tuesday, 14 July)
• Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413) (Wednesday, 8 July)

Jordan Harband

• Re: [whatwg/webidl] Is a function signature with a parameter type `(DOMString or Interface)` a footgun? (Issue #1604) (Thursday, 9 July)

Josh Matthews

• [whatwg/webidl] Check for detached buffer source when checking if transferable is inverted (Issue #1619) (Saturday, 18 July)

Julian Reschke

• Re: [whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943) (Tuesday, 28 July)

Julien Cayzac

• Re: [w3c/screen-orientation] Editorial: clarify the natural screen orientation (PR #278) (Sunday, 26 July)
• Re: [w3c/screen-orientation] Square (1:1) screens fall outside both screen orientation values lists (Issue #279) (Friday, 24 July)
• Re: [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222) (Tuesday, 21 July)
• Re: [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222) (Tuesday, 21 July)
• [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222) (Friday, 17 July)
• Re: [w3c/screen-orientation] "natural" is ambiguous (Issue #275) (Friday, 10 July)

Kagami Sascha Rosylight

• Re: [whatwg/webidl] Is a function signature with a parameter type `(DOMString or Interface)` a footgun? (Issue #1604) (Thursday, 16 July)
• Re: [w3c/gamepad] Add device orientation support (Issue #211) (Tuesday, 14 July)

Keith Cirkel

• Re: [whatwg/dom] Restore active custom element constructor map entries after construction (PR #1494) (Friday, 17 July)
• Re: [whatwg/dom] Restore active custom element constructor map entries after construction (PR #1494) (Friday, 17 July)

Kenta Moriuchi

• [whatwg/fetch] Make `Response.redirect()` headers mutable (PR #1944) (Thursday, 30 July)

Kyle

• [w3c/clipboard-apis] [Security Proposal] Allow ClipboardItem to accept a BufferSource such as Uint8Array to harmonize with memory sanitizations (Issue #251) (Saturday, 11 July)

L. David Baron

• Re: [w3ctag/design-reviews] Other Spec Review: HTML menu elements (Issue #1242) (Friday, 10 July)
• [w3ctag/design-reviews] Other Spec Review: HTML menu elements (Issue #1242) (Wednesday, 1 July)

Lea Verou

• Re: [w3ctag/design-reviews] Incubation: Platform-provided behaviors for custom elements (Issue #1219) (Thursday, 30 July)

Lee Ash

• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Sunday, 12 July)

Lia Hiscock

• [w3ctag/design-reviews] Question: Review manifest-first Web Install API (Issue #1245) (Tuesday, 14 July)
• Re: [w3ctag/design-reviews] (brand new ✨) Web Install API (Issue #1051) (Monday, 13 July)

Linus Groh

• Re: [whatwg/webidl] Is a function signature with a parameter type `(DOMString or Interface)` a footgun? (Issue #1604) (Thursday, 9 July)
• Re: [whatwg/webidl] Update PropertyDescriptor [[Get]]/[[Set]] to [[Getter]]/[[Setter]] (PR #1613) (Thursday, 2 July)

liudonghua

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

Lola

• Re: [w3ctag/design-reviews] WG New Spec: DID Resolution (Issue #1157) (Thursday, 23 July)
• Re: [w3ctag/design-reviews] Other Spec Review: overscroll-behavior: chain (Issue #1228) (Thursday, 16 July)

Luke Warlow

• Re: [w3ctag/design-reviews] Other Spec Review: CSS scroll-axis-lock (Issue #1248) (Thursday, 23 July)
• Re: [w3ctag/design-reviews] Other Spec Review: overscroll-behavior: chain (Issue #1228) (Thursday, 16 July)
• Re: [w3ctag/design-reviews] Other Spec Review: Single-Axis Scroll Containers (Issue #1222) (Thursday, 16 July)
• Re: [w3ctag/design-reviews] WG Revision: CSS Anchor Positioning Level 1 (Issue #1182) (Thursday, 9 July)

Léonie Watson

• Re: [w3c/screen-orientation] Editorial: add Léonie Watson as co-editor (PR #280) (Friday, 24 July)
• Re: [w3c/screen-orientation] "natural" is ambiguous (Issue #275) (Thursday, 9 July)

Manu Sporny

• [w3ctag/design-reviews] WG New Spec: Recognized Entities v1.0 (Issue #1249) (Sunday, 26 July)

Marcos Cáceres

• [w3c/manifest] Should `display-mode` be gated for cross-origin iframes? (Issue #1239) (Friday, 24 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Friday, 24 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Friday, 24 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Friday, 24 July)
• [w3c/manifest] editorial: add missing assertion to chosen-display-mode algorithm (PR #1238) (Friday, 24 July)
• Re: [w3c/manifest] user initiated 'uninstall' event (#1201) (Thursday, 23 July)
• [w3c/manifest] Editorial: don't reference WebIDL identifier (PR #1237) (Thursday, 23 July)
• Re: [w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234) (Thursday, 23 July)
• Re: [w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234) (Thursday, 23 July)
• Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224) (Thursday, 23 July)
• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1236) (Thursday, 23 July)
• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1236) (Thursday, 23 July)
• Re: [w3c/manifest] Internationalization -> Internationalization Considerations, clarifications (PR #1234) (Thursday, 23 July)
• Re: [w3c/manifest] Format U+002F character references using W3C I18N template (PR #1235) (Thursday, 23 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 23 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 23 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 23 July)
• Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224) (Thursday, 23 July)
• Re: [w3c/manifest] Manifest name: USVString or not? (Issue #1228) (Thursday, 23 July)
• Re: [w3c/manifest] "cannot be used together" editing woes (Issue #1227) (Thursday, 23 July)
• Re: [w3c/manifest] editorial: fix typos, grammar, and a stray definition (PR #1233) (Thursday, 23 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 23 July)
• Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224) (Thursday, 23 July)
• [w3c/manifest] editorial: fix typos, grammar, and a stray definition (PR #1233) (Thursday, 23 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 23 July)
• Re: [w3c/manifest] Manifest name: USVString or not? (Issue #1228) (Thursday, 23 July)
• Re: [w3c/manifest] Editorial: Split privacy and security considerations into separate sections (PR #1224) (Thursday, 23 July)
• Re: [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221) (Thursday, 23 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 23 July)
• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1222) (Thursday, 23 July)
• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1222) (Thursday, 23 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 23 July)
• Re: [w3c/screen-orientation] Fix iframe promise rejection in unloading document cleanup (PR #268) (Thursday, 23 July)
• [w3c/screen-orientation] Editorial: add Léonie Watson as co-editor (PR #280) (Thursday, 23 July)
• Re: [w3c/screen-orientation] Should pending promise be abort if document isn't top-level? (Issue #257) (Thursday, 23 July)
• Re: [w3c/screen-orientation] Editorial: clarify the natural screen orientation (PR #278) (Thursday, 23 July)
• [w3c/screen-orientation] Square (1:1) screens fall outside both screen orientation values lists (Issue #279) (Thursday, 23 July)
• [w3c/screen-orientation] Editorial: clarify the natural screen orientation (PR #278) (Thursday, 23 July)
• Re: [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222) (Saturday, 18 July)
• Re: [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222) (Saturday, 18 July)
• Re: [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222) (Saturday, 18 July)
• Re: [w3ctag/design-reviews] Question: Review manifest-first Web Install API (Issue #1245) (Thursday, 16 July)
• Re: [w3ctag/design-reviews] Question: Review manifest-first Web Install API (Issue #1245) (Thursday, 16 July)
• Re: [w3ctag/design-reviews] Question: Review manifest-first Web Install API (Issue #1245) (Wednesday, 15 July)
• Re: [w3ctag/design-reviews] [wg/webappsec] Web Application Security Working Group Charter (Issue #1244) (Wednesday, 15 July)
• Re: [w3ctag/design-reviews] (brand new ✨) Web Install API (Issue #1051) (Tuesday, 14 July)
• Re: [w3c/permissions] Rename document (Issue #478) (Tuesday, 14 July)
• Re: [w3c/permissions] Rename document (Issue #478) (Monday, 13 July)
• Re: [w3c/manifest] chore: fix SchemaStore links and drop the embedded schema view (PR #1220) (Thursday, 9 July)
• Re: [w3c/manifest] Create SECURITY.md (PR #1226) (Thursday, 9 July)
• [w3c/manifest] Split privacy and security considerations into separate sections (PR #1224) (Friday, 3 July)
• [w3c/manifest] Recommend user agents let users inspect and modify shortcut URLs (PR #1221) (Thursday, 2 July)
• Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218) (Thursday, 2 July)
• Re: [w3c/manifest] Redefine application context on top-level traversable (PR #1219) (Thursday, 2 July)
• Re: [w3c/manifest] Redefine application context on top-level traversable (PR #1219) (Thursday, 2 July)

Mark Nottingham

• Re: [whatwg/fetch] Add getStructured/setStructured to Headers (PR #1943) (Tuesday, 28 July)
• Re: [whatwg/fetch] Integrating the HTTP QUERY method (RFC 10008): method normalization, CORS, and caching (Issue #1938) (Wednesday, 1 July)

Martin Thomson

• Re: [whatwg/url] Enumerate differences with URI & IRI in an appendix (PR #923) (Thursday, 2 July)

Masayuki Nakano

• Re: [w3c/uievents] Use `USVString` for input and composition events (Issue #352) (Thursday, 30 July)

Matthew Tylee Atkinson

• Re: [w3ctag/design-reviews] [wg/atag] Authoring Tools Accessibility Guidelines Group Charter (Issue #1241) (Thursday, 16 July)
• Re: [w3ctag/design-reviews] [wg/atag] Authoring Tools Accessibility Guidelines Group Charter (Issue #1241) (Thursday, 16 July)
• Re: [w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172) (Wednesday, 8 July)
• Re: [w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172) (Wednesday, 8 July)
• Re: [w3ctag/design-reviews] Service discovery (Issue #1243) (Thursday, 2 July)
• [w3ctag/design-reviews] Service discovery (Issue #1243) (Wednesday, 1 July)

Mattias Buelens

• Re: [whatwg/streams] Use `async iterable` webidl type in ReadableStream.from (PR #1310) (Friday, 17 July)
• Re: [whatwg/streams] Use `async iterable` webidl type in ReadableStream.from (PR #1310) (Friday, 17 July)
• Re: [whatwg/streams] Use `async_sequence` in `ReadableStream.from` (PR #1372) (Friday, 17 July)
• Re: [whatwg/streams] Revisiting ReadableStream.from(syncIter) and ReadableStream.from(str) (Issue #1376) (Wednesday, 15 July)
• Re: [whatwg/streams] Use `async_sequence` in `ReadableStream.from` (PR #1372) (Monday, 13 July)
• Re: [whatwg/streams] Use `async_sequence` in `ReadableStream.from` (PR #1372) (Saturday, 4 July)

mawalamurday-droid

• [whatwg/webidl] Intent to use bigint/numeric union (Issue #1617) (Wednesday, 8 July)

Max Waterman

• Re: [w3c/manifest] user initiated 'uninstall' event (#1201) (Friday, 24 July)

Meghan Denny

• Re: [whatwg/webidl] DOMException name proposal (Issue #1622) (Thursday, 23 July)
• Re: [whatwg/webidl] Bocil smp (Issue #1621) (Thursday, 23 July)
• Re: [whatwg/webidl] Intent to use Constants (Issue #1620) (Sunday, 19 July)
• Re: [whatwg/webidl] Intent to use Constants (Issue #1618) (Tuesday, 14 July)
• Re: [whatwg/webidl] Intent to use Constants (Issue #1616) (Sunday, 5 July)
• Re: [whatwg/url] What is an opaque path? (Issue #922) (Wednesday, 1 July)

Michael Aufreiter

• [w3c/editing] IOS Safari: Ability to opt-out of Form assistant bar (which is useless for single-field editors and takes up a lot of space) (Issue #545) (Sunday, 19 July)
• Re: [w3c/editing] Chrome: Selection barrier at details element when contenteditable=true (Issue #538) (Thursday, 9 July)
• [w3c/uievents] Add normative note to spec regarding "modifier keys on mobile platforms" (Issue #417) (Thursday, 9 July)
• Re: [w3c/editing] Inconsistent `KeyboardEvent.shiftKey` behavior for virtual keyboard autocapitalization (Issue #542) (Thursday, 9 July)
• Re: [w3c/editing] Inconsistent `KeyboardEvent.shiftKey` behavior for virtual keyboard autocapitalization (Issue #542) (Thursday, 9 July)
• [w3c/editing] Inconsistent `KeyboardEvent.shiftKey` behavior for virtual keyboard autocapitalization (Issue #542) (Thursday, 9 July)

Mike Taylor

• Re: [w3c/permissions] Rename document (Issue #478) (Monday, 13 July)
• Re: [w3c/permissions] Rename document (Issue #478) (Thursday, 9 July)

misterprincess-prog

• [whatwg/webidl] Intent to use Constants (Issue #1616) (Saturday, 4 July)

Monica Chintala

• [w3c/ServiceWorker] Editorial: queue a task to reject promise in InstallEvent.addRoutes (PR #1839) (Friday, 31 July)
• [w3ctag/design-reviews] Other Spec Review: JS Self-Profiling Markers (ProfilerSample.marker) (Issue #1251) (Wednesday, 29 July)
• Re: [w3c/ServiceWorker] Request's origin needs to be set for [[Update]] algorithm (#1447) (Friday, 24 July)
• Re: [w3c/ServiceWorker] Request's origin needs to be set for [[Update]] algorithm (#1447) (Friday, 24 July)
• Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273) (Friday, 24 July)
• Re: [w3c/ServiceWorker] Add a WPT test for credentialed requests in register()/update (#1435) (Friday, 24 July)
• Re: [w3c/ServiceWorker] Should update() always reject if there is an installing worker? (#1429) (Friday, 24 July)
• Re: [w3c/ServiceWorker] Should we restore the registration record removing step in Clear Registration? (#1433) (Thursday, 23 July)
• Re: [w3c/ServiceWorker] Should we restore the registration record removing step in Clear Registration? (#1433) (Thursday, 23 July)
• Re: [w3c/ServiceWorker] What happens to the request body if the fetch isn't handled? (#1191) (Thursday, 23 July)
• Re: [w3c/ServiceWorker] Editorial: queue a task in Client / Clients API (PR #1836) (Thursday, 23 July)
• Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerGlobalScope.skipWaiting (PR #1835) (Thursday, 23 July)
• Re: [w3c/ServiceWorker] Build spec using travis (#1099) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Build spec using travis (#1099) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Editorial: queue a task in NavigationPreloadManager (PR #1834) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerContainer.getRegistration (PR #1833) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerContainer.getRegistration (PR #1833) (Friday, 17 July)
• Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Should register() trigger an update if only updateViaCache changes? (#1414) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Consider exposing Page Lifecycle state to service-worker (#1345) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Is respondWith(fetch(event.request)) always the same as not calling respondWith()? (#1395) (Friday, 17 July)
• Re: [w3c/ServiceWorker] spec should document Cache API HEIST mitigations (#1396) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Fully inline (.js + json manifest) service worker (#1392) (Thursday, 16 July)
• Re: [w3c/ServiceWorker] Fully inline (.js + json manifest) service worker (#1392) (Thursday, 16 July)
• Re: [w3c/ServiceWorker] Add WPT for an in-scope iframe inside a data URL iframe. (#1393) (Thursday, 16 July)
• Re: [w3c/ServiceWorker] Add WPT for an in-scope iframe inside a data URL iframe. (#1393) (Thursday, 16 July)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Thursday, 16 July)
• [w3c/ServiceWorker] Editorial: serialize CacheStorage access on a dedicated parallel queue (PR #1838) (Thursday, 16 July)
• [w3c/ServiceWorker] Editorial: queue a task in Cache API (PR #1837) (Thursday, 16 July)
• [w3c/ServiceWorker] Editorial: queue a task in Client / Clients API (PR #1836) (Thursday, 16 July)
• [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerGlobalScope.skipWaiting (PR #1835) (Thursday, 16 July)
• [w3c/ServiceWorker] Editorial: queue a task in NavigationPreloadManager (PR #1834) (Thursday, 16 July)
• [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerContainer.getRegistration (PR #1833) (Thursday, 16 July)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Wednesday, 15 July)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Wednesday, 15 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Wednesday, 15 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Wednesday, 15 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Tuesday, 14 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Tuesday, 14 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Tuesday, 14 July)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 13 July)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Monday, 13 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Monday, 13 July)
• [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Monday, 13 July)
• Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292) (Friday, 10 July)
• Re: [w3c/ServiceWorker] clients.get() should not resolve before sandboxing determines the origin of the client (#1385) (Thursday, 9 July)
• Re: [w3c/ServiceWorker] A description mistake in spec document (#1391) (Thursday, 9 July)
• Re: [w3c/ServiceWorker] clients.get() should not resolve before sandboxing determines the origin of the client (#1385) (Thursday, 9 July)
• Re: [w3c/ServiceWorker] clients.get() should not resolve before sandboxing determines the origin of the client (#1385) (Thursday, 9 July)
• Re: [w3c/ServiceWorker] Redesign Service-Worker-Allowed header extraction (PR #1830) (Monday, 6 July)
• Re: [w3c/ServiceWorker] ready promise is kind of weird after you call unregister() (#1279) (Friday, 3 July)
• Re: [w3c/ServiceWorker] ready promise is kind of weird after you call unregister() (#1279) (Friday, 3 July)
• Re: [w3c/ServiceWorker] Cache's put() says it clones the response (#1382) (Friday, 3 July)
• Re: [w3c/ServiceWorker] Cache's put() says it clones the response (#1382) (Friday, 3 July)
• Re: [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367) (Friday, 3 July)
• Re: [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367) (Friday, 3 July)
• Re: [w3c/ServiceWorker] ready promise doesn't work right when controlling registration is resurrected (#1198) (Friday, 3 July)
• Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Friday, 3 July)
• Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Friday, 3 July)
• Re: [w3c/ServiceWorker] Should a service worker be allowed to register new service workers? (#1117) (Thursday, 2 July)
• Re: [w3c/ServiceWorker] Web Authentication API access in service worker (#1369) (Thursday, 2 July)
• Re: [w3c/ServiceWorker] Web Authentication API access in service worker (#1369) (Thursday, 2 July)

Nicolas Lebacq

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

Nicolás Peña Moreno

• Re: [whatwg/dom] Which target could we expose in Event Timing? (#838) (Wednesday, 8 July)

Nikolaos S. Papaspyrou

• Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198) (Thursday, 16 July)

Noam Rosenthal

• [w3ctag/design-reviews] Question: can we better define the intention of the "disable scripting" user preference (Issue #1247) (Tuesday, 21 July)
• Re: [whatwg/dom] Adopt node before removing child in replace (PR #1488) (Wednesday, 8 July)
• Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814) (Wednesday, 8 July)
• Re: [whatwg/dom] Editorial: improve ensure pre-insert validity (PR #1484) (Wednesday, 8 July)
• Re: [w3ctag/design-reviews] Other Spec Review: `textStream()` for `Blob` and `Body` (Issue #1236) (Wednesday, 8 July)
• Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478) (Thursday, 2 July)
• Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478) (Thursday, 2 July)
• Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478) (Thursday, 2 July)
• Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478) (Thursday, 2 July)
• Re: [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478) (Thursday, 2 July)
• [whatwg/dom] Remove "allow declarative shadow roots" (PR #1478) (Wednesday, 1 July)

Otto Mora

• Re: [w3ctag/design-reviews] WG New Spec: DID Resolution (Issue #1157) (Friday, 17 July)

Patrick Meenan

• Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854) (Tuesday, 28 July)

Patryk Chodur

• Re: [w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246) (Wednesday, 29 July)
• Re: [w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246) (Wednesday, 29 July)
• Re: [w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246) (Thursday, 16 July)
• Re: [w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246) (Thursday, 16 July)
• Re: [w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246) (Thursday, 16 July)
• [w3ctag/design-reviews] WG New Spec: Additional Windowing Controls (Issue #1246) (Thursday, 16 July)

Piers Wombwell

• [whatwg/dom] Restore deep cloning of shadow root contents. (PR #1480) (Saturday, 4 July)

Psychpsyo (Cameron)

• [w3c/editing] Actually return true from indent command (PR #547) (Friday, 31 July)
• [w3c/editing] Actually return true from forwarddelete (PR #544) (Sunday, 19 July)
• Re: [w3c/editing] Spec for InsertImage command is (no longer) 'correct'. (Issue #543) (Thursday, 16 July)
• [w3c/editing] Spec for InsertImage command is (no longer) 'correct'. (Issue #543) (Thursday, 16 July)

q2p

• Re: [w3c/FileAPI] Allow `createObjectURL` to retain filename from `File` (and similar) objects (Issue #203) (Tuesday, 28 July)

Randell Jesup

• Re: [w3c/gamepad] Add device orientation support (Issue #211) (Tuesday, 14 July)
• Re: [w3c/gamepad] DOM Elements Integration (Issue #227) (Tuesday, 14 July)
• [w3c/gamepad] Trigger HTML activation (PR #230) (Friday, 10 July)

Renato Iannella

• Re: [w3c/permissions] Rename document (Issue #478) (Wednesday, 15 July)
• Re: [w3c/permissions] Rename document (Issue #478) (Tuesday, 14 July)
• Re: [w3c/permissions] Rename document (Issue #478) (Friday, 10 July)
• Re: [w3c/permissions] Rename document (Issue #478) (Thursday, 9 July)
• [w3c/permissions] Rename document (Issue #478) (Thursday, 9 July)

Rob Paveza

• Re: [w3ctag/design-reviews] Question: Review manifest-first Web Install API (Issue #1245) (Wednesday, 15 July)

Sam Atkins

• [w3c/clipboard-apis] "allowed to show a popup" definition link goes nowhere (Issue #250) (Friday, 10 July)

Shannon Booth

• Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479) (Friday, 3 July)
• Re: [whatwg/dom] Handle NodeIterator node removal during filtering (PR #1479) (Thursday, 2 July)
• Re: [whatwg/dom] Fix NodeIterator pre-remove steps for ancestors of root (PR #1477) (Thursday, 2 July)

shaunwashington5555-svg

• [whatwg/webidl] DOMException name proposal (Issue #1622) (Thursday, 23 July)

Shay Cojocaru

• Re: [w3ctag/design-reviews] Incubation: Proofreader API (Issue #1146) (Monday, 20 July)

Sialuriano

• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Monday, 13 July)
• Re: [whatwg/storage] Add top-level site to storage key. (#127) (PR #144) (Monday, 13 July)

sideshowbarker

• Re: [whatwg/fullscreen] Review Draft Publication: July 2026 (PR #263) (Friday, 17 July)
• Re: [whatwg/dom] Create nodes in the realm of the document they are created for (PR #1491) (Friday, 17 July)

Simone Onofri

• Re: [w3ctag/design-reviews] [wg/webappsec] Web Application Security Working Group Charter (Issue #1244) (Friday, 24 July)

smaug----

• Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413) (Wednesday, 29 July)
• Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413) (Wednesday, 29 July)
• Re: [whatwg/dom] Adopt a DocumentFragment with a host like any other node (PR #1486) (Thursday, 9 July)
• Re: [whatwg/dom] Adopt a DocumentFragment with a host like any other node (PR #1486) (Thursday, 9 July)
• Re: [whatwg/dom] Let replaceChildren() replace a document's children (PR #1487) (Thursday, 9 July)
• Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413) (Thursday, 2 July)

Sun Shin

• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Thursday, 9 July)

Tab Atkins Jr.

• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Monday, 20 July)
• Re: [whatwg/dom] Element.matches and pseudo-elements (#185) (Monday, 13 July)
• Re: [whatwg/dom] Define a mapping to a Selectors Element Tree (#542) (Monday, 13 July)

The Moisrex

• Re: [whatwg/url] What is an opaque path? (Issue #922) (Monday, 20 July)

Tzviya

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

udascojonard03-jpg

• [w3ctag/design-reviews] Incubation: (Issue #1252) (Friday, 31 July)

Vincent Scheib

• Re: [w3c/pointerlock] Should not release pointer lock when pressing esc while fullscreen keyboard lock is active (Issue #110) (Friday, 10 July)

W3C Bot

• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1236) (Thursday, 23 July)
• Re: [w3c/manifest] Tidied up document using tidy-html5 (PR #1222) (Thursday, 23 July)
• [w3ctag/design-reviews] [wg/webappsec] Web Application Security Working Group Charter (Issue #1244) (Saturday, 4 July)

Will Abramson

• Re: [w3ctag/design-reviews] WG New Spec: DID Resolution (Issue #1157) (Friday, 31 July)
• Re: [w3ctag/design-reviews] WG New Spec: DID Resolution (Issue #1157) (Friday, 24 July)
• Re: [w3ctag/design-reviews] WG New Spec: DID Resolution (Issue #1157) (Tuesday, 7 July)

Xiaoqian Wu

• Re: [w3c/editing] forming of community editing group (Issue #541) (Thursday, 9 July)
• [w3c/manifest] Prepare the Manifest spec for CR (Issue #1225) (Monday, 6 July)

Yoichi Osato

• Re: [w3ctag/design-reviews] Incubation: Prerendering cross-origin iframes (Issue #1207) (Wednesday, 1 July)

Yoshisato Yanagisawa

• Re: [w3c/ServiceWorker] w3c/ServiceWorker (Issue #1826) (Thursday, 30 July)
• Re: [w3c/ServiceWorker] Add a WPT test for credentialed requests in register()/update (#1435) (Friday, 24 July)
• Re: [w3c/ServiceWorker] Editorial: queue a task in Client / Clients API (PR #1836) (Thursday, 23 July)
• Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerGlobalScope.skipWaiting (PR #1835) (Thursday, 23 July)
• Re: [w3c/ServiceWorker] Editorial: queue a task in NavigationPreloadManager (PR #1834) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerContainer.getRegistration (PR #1833) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Editorial: queue a task in ServiceWorkerContainer.getRegistration (PR #1833) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Friday, 17 July)
• Re: [w3c/ServiceWorker] Fully inline (.js + json manifest) service worker (#1392) (Thursday, 16 July)
• Re: [w3c/ServiceWorker] Add WPT for an in-scope iframe inside a data URL iframe. (#1393) (Thursday, 16 July)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Thursday, 16 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Thursday, 16 July)
• Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755) (Wednesday, 15 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Wednesday, 15 July)
• Re: [w3c/ServiceWorker] Editorial: clarify FetchEvent clientId, resultingClientId, and replacesClientId initialization (PR #1832) (Tuesday, 14 July)
• Re: [w3c/ServiceWorker] cache and cache-storage algos forgets to queue a task to resolve promise. (Issue #1831) (Friday, 10 July)
• Re: [w3c/ServiceWorker] cache and cache-storage algos forgets to queue a task to resolve promise. (Issue #1831) (Friday, 10 July)
• Re: [w3c/ServiceWorker] A description mistake in spec document (#1391) (Friday, 10 July)
• Re: [w3c/ServiceWorker] Redesign Service-Worker-Allowed header extraction (PR #1830) (Monday, 6 July)
• Re: [w3c/ServiceWorker] Redesign of "extract header list values" expected (#1360) (Monday, 6 July)
• Re: [w3c/ServiceWorker] Should a service worker be allowed to register new service workers? (#1117) (Monday, 6 July)
• Re: [w3c/ServiceWorker] Redesign Service-Worker-Allowed header extraction (PR #1830) (Friday, 3 July)
• [w3c/ServiceWorker] Redesign Service-Worker-Allowed header extraction (PR #1830) (Friday, 3 July)

Yves Lafon

• Re: [w3ctag/design-reviews] Incubation: Connection Allowlists (Issue #1173) (Thursday, 9 July)

Last message date: Friday, 31 July 2026 23:49:54 UTC