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

abbydav

• [whatwg/url] Help I don't know what my bf did to my phone or how to fix it is so much for so long to every phone! D':: (Issue #743) (Thursday, 19 January)

Adam Langley

• Re: [w3ctag/design-reviews] WebAuthn PRF extension (Issue #806) (Tuesday, 24 January)
• [w3ctag/design-reviews] WebAuthn PRF extension (Issue #806) (Tuesday, 17 January)

Adam Rice

• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Thursday, 26 January)
• Re: [whatwg/streams] Should the underlying source be pinged for cancel when a close request exists? (Issue #1252) (Tuesday, 24 January)
• Re: [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733) (Friday, 13 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 13 January)
• Re: [whatwg/url] can't parse urls starting with xn-- (#438) (Thursday, 12 January)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Wednesday, 11 January)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Tuesday, 10 January)

Alan Stearns

• Re: [w3ctag/design-reviews] Spec review for CSS Nesting (Issue #791) (Friday, 6 January)

Alastor Wu

• [w3ctag/design-reviews] Spec review for Autoplay Policy Detection API (Issue #810) (Friday, 27 January)

Alex Russell

• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Tuesday, 10 January)

Alexis Hunt

• Re: [whatwg/url] Editorial: point out API section is not suitable for all (PR #738) (Tuesday, 17 January)

Allan Bonadio

• Re: [w3c/uievents] definition of MouseEvent.clientX and clientY seems wrong (Issue #339) (Wednesday, 4 January)

Alwin Blok

• Re: [whatwg/url] Windows drive letter uppercasing (#515) (Monday, 16 January)
• Re: [whatwg/url] Windows drive letter uppercasing (#515) (Saturday, 14 January)

Amy Guy

• Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Thursday, 12 January)
• Re: [w3ctag/design-reviews] Review of IMSC-HRM (Issue #788) (Monday, 9 January)

Anatoli Babenia

• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Friday, 13 January)
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Thursday, 12 January)
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Thursday, 12 January)
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Thursday, 12 January)
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Thursday, 12 January)

Andreu Botella

• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Thursday, 26 January)
• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Thursday, 19 January)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Wednesday, 18 January)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Wednesday, 18 January)
• Re: [whatwg/streams] add TrasformStream finally callback (PR #1231) (Thursday, 12 January)
• Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Tuesday, 3 January)

Andrew Sutherland

• Re: [w3c/ServiceWorker] Questions regarding inevitable nature of performance gains and losses of ServiceWorker (Issue #1667) (Monday, 23 January)
• Re: [w3c/ServiceWorker] Questions regarding inevitable nature of performance gains and losses of ServiceWorker (Issue #1667) (Friday, 20 January)

Andy Earnshaw

• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Thursday, 12 January)
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Thursday, 12 January)
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Thursday, 12 January)
• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Wednesday, 11 January)
• Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Tuesday, 3 January)

Anne van Kesteren

• Re: [w3ctag/design-reviews] FYI - Add optional `submitter` parameter to the `FormData` constructor (Issue #812) (Tuesday, 31 January)
• Re: [w3ctag/design-reviews] How should web standards use the new JavaScript Symbol.dispose protocol? (Discussion #800) (Friday, 27 January)
• Re: [whatwg/fetch] Possible typo in "The `Allow` header is not relevant for the purp..." (Issue #1598) (Friday, 27 January)
• Re: [whatwg/fetch] Possible typo in "The `Allow` header is not relevant for the purp..." (Issue #1598) (Friday, 27 January)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Friday, 27 January)
• Re: [whatwg/xhr] FormData: Add ability to specify submitter in addition to <form> (#262) (Friday, 27 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Friday, 27 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Friday, 27 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Thursday, 26 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Thursday, 26 January)
• Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Header class (PR #1596) (Thursday, 26 January)
• Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Header class (PR #1596) (Thursday, 26 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Wednesday, 25 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Wednesday, 25 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Wednesday, 25 January)
• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Wednesday, 25 January)
• Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226) (Wednesday, 25 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Wednesday, 25 January)
• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Wednesday, 25 January)
• Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226) (Wednesday, 25 January)
• Re: [whatwg/fetch] Editorial: Remove `prefetch-src` (PR #1595) (Wednesday, 25 January)
• Re: [whatwg/fetch] Editorial: Remove `prefetch-src` (PR #1595) (Wednesday, 25 January)
• Re: [whatwg/fetch] Editorial: Remove `prefetch-src` (PR #1595) (Wednesday, 25 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Wednesday, 25 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Wednesday, 25 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Wednesday, 25 January)
• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Wednesday, 25 January)
• Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226) (Wednesday, 25 January)
• Re: [whatwg/fetch] String representations for Fetch API objects (Issue #1575) (Wednesday, 25 January)
• Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Header class (PR #1596) (Wednesday, 25 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 24 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 24 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 24 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 24 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 24 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 24 January)
• Re: [whatwg/url] Should protocol setter remove tabs and newline? (#609) (Tuesday, 24 January)
• Re: [whatwg/url] Should protocol setter remove tabs and newline? (#609) (Tuesday, 24 January)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Tuesday, 24 January)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Tuesday, 24 January)
• [whatwg/url] Be clearer that non-UTF-8 code paths are only relevant for a small subset of implementations (Issue #746) (Tuesday, 24 January)
• Re: [whatwg/url] Named validation errors (#502) (Monday, 23 January)
• Re: [whatwg/url] Named validation errors (#502) (Monday, 23 January)
• Re: [whatwg/url] Editorial: rely on Infra's code point length (PR #745) (Monday, 23 January)
• Re: [whatwg/url] Named validation errors (#502) (Monday, 23 January)
• [whatwg/url] Editorial: rely on Infra's code point length (PR #745) (Monday, 23 January)
• Re: [whatwg/url] Issues with UTS #46 tests (#341) (Monday, 23 January)
• Re: [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733) (Monday, 23 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Monday, 23 January)
• [whatwg/url] Meta: UTS46 feedback (Issue #744) (Monday, 23 January)
• Re: [whatwg/url] Should we ignore IPv6 zone identifiers when parsing a URL? (Issue #742) (Monday, 23 January)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 20 January)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 20 January)
• Re: [whatwg/url] Issues with UTS #46 tests (#341) (Friday, 20 January)
• Re: [w3ctag/design-reviews] How should web standards use the new JavaScript Symbol.dispose protocol? (Discussion #800) (Friday, 20 January)
• Re: [whatwg/dom] document.execCommand('copy') is deprecated so is it any other solution for support ios device. (Issue #1144) (Friday, 20 January)
• Re: [whatwg/dom] document.execCommand('copy') is deprecated so is it any other solution for support ios device. (Issue #1144) (Friday, 20 January)
• Re: [whatwg/url] Defered validation error reporting in IPv4 parser (Issue #706) (Friday, 20 January)
• Re: [whatwg/url] Redo validation errors in the IPv4 parser (PR #739) (Friday, 20 January)
• Re: [whatwg/url] Issues with UTS #46 tests (#341) (Friday, 20 January)
• Re: [whatwg/url] Should we ignore IPv6 zone identifiers when parsing a URL? (Issue #742) (Friday, 20 January)
• Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Thursday, 19 January)
• Re: [whatwg/url] Should we ignore IPv6 zone identifiers when parsing a URL? (Issue #742) (Thursday, 19 January)
• Re: [whatwg/url] Redo validation errors in the IPv4 parser (PR #739) (Thursday, 19 January)
• Re: [whatwg/url] Meta: preserve IDs per anchor permanence policy (PR #741) (Thursday, 19 January)
• Re: [whatwg/url] Anchor permanence for URI parameters (Issue #740) (Thursday, 19 January)
• Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Thursday, 19 January)
• [whatwg/url] Meta: preserve IDs per anchor permanence policy (PR #741) (Thursday, 19 January)
• Re: [w3c/FileAPI] createObjectURL with ReadableStream (Issue #189) (Thursday, 19 January)
• Re: [w3c/FileAPI] createObjectURL with ReadableStream (Issue #189) (Thursday, 19 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Thursday, 19 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Thursday, 19 January)
• Re: [whatwg/fetch] Should the cache control default mode match how the page is loaded? (#289) (Wednesday, 18 January)
• Re: [whatwg/url] Should protocol setter remove tabs and newline? (#609) (Wednesday, 18 January)
• Re: [whatwg/url] Editorial: point out API section is not suitable for all (PR #738) (Tuesday, 17 January)
• Re: [whatwg/url] Clarify scope of API define in the spec or split specs (#535) (Tuesday, 17 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 17 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 17 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 17 January)
• Re: [whatwg/url] Redo validation errors in the IPv4 parser (PR #739) (Tuesday, 17 January)
• Re: [whatwg/url] Defered validation error reporting in IPv4 parser (Issue #706) (Tuesday, 17 January)
• [whatwg/url] Redo validation errors in the IPv4 parser (PR #739) (Tuesday, 17 January)
• Re: [whatwg/fetch] Rename "extract-value flag" to "extract-value" and define it as a boolean (Issue #1567) (Tuesday, 17 January)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Tuesday, 17 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Tuesday, 17 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Tuesday, 17 January)
• Re: [whatwg/fetch] Rename "extract-value flag" to "extract-value" and define it as a boolean (Issue #1567) (Tuesday, 17 January)
• Re: [whatwg/url] Proposal: Add a normalization interface (Issue #729) (Tuesday, 17 January)
• Re: [whatwg/url] Removing trailing C0 control or space at basic URL parser makes difference with override (#542) (Tuesday, 17 January)
• Re: [whatwg/url] Editorial: point out API section is not suitable for all (PR #738) (Tuesday, 17 January)
• [whatwg/url] Editorial: point out API section is not suitable for all (PR #738) (Tuesday, 17 January)
• Re: [whatwg/url] Define domain label (#435) (Tuesday, 17 January)
• Re: [whatwg/url] Editorial: define domain label (PR #737) (Tuesday, 17 January)
• Re: [whatwg/url] Editorial: define domain label (PR #737) (Tuesday, 17 January)
• Re: [whatwg/url] Editorial: define domain label (PR #737) (Tuesday, 17 January)
• [whatwg/url] Editorial: define domain label (PR #737) (Tuesday, 17 January)
• Re: [whatwg/url] Editorial: define URL path segment (PR #736) (Tuesday, 17 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 17 January)
• Re: [whatwg/url] URLSearchParams and URL [Serializable] (#370) (Tuesday, 17 January)
• [whatwg/url] Editorial: define URL path segment (PR #736) (Monday, 16 January)
• Re: [whatwg/url] [ideas] Get value as number, date & boolean (Issue #702) (Monday, 16 January)
• Re: [whatwg/url] [ideas] Get value as number, date & boolean (Issue #702) (Monday, 16 January)
• Re: [whatwg/url] URLSearchParams and URL [Serializable] (#370) (Monday, 16 January)
• [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Monday, 16 January)
• Re: [whatwg/url] Make URL's origin getter return null for file URLs (#506) (Monday, 16 January)
• Re: [whatwg/fetch] Discuss: Removing `cache: reload` option from the API (#902) (Monday, 16 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Monday, 16 January)
• Re: [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733) (Monday, 16 January)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 16 January)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 16 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Monday, 16 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Monday, 16 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Monday, 16 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Monday, 16 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Monday, 16 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Monday, 16 January)
• Re: [whatwg/dom] Meta: address xref issues (PR #1143) (Monday, 16 January)
• Re: [whatwg/dom] Meta: address xref issues (PR #1143) (Monday, 16 January)
• Re: [whatwg/dom] Meta: address xref issues (PR #1143) (Monday, 16 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Monday, 16 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Monday, 16 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Monday, 16 January)
• [whatwg/dom] Meta: address xref issues (PR #1143) (Monday, 16 January)
• Re: [whatwg/url] Windows drive letter uppercasing (#515) (Monday, 16 January)
• Re: [whatwg/url] Windows drive letter uppercasing (#515) (Monday, 16 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2023 (PR #214) (Monday, 16 January)
• [whatwg/fullscreen] Review Draft Publication: January 2023 (PR #214) (Monday, 16 January)
• Re: [whatwg/url] Windows drive letter uppercasing (#515) (Monday, 16 January)
• Re: [whatwg/url] Windows drive letter uppercasing (#515) (Monday, 16 January)
• Re: [whatwg/url] Windows drive letter uppercasing (#515) (Monday, 16 January)
• [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Monday, 16 January)
• Re: [whatwg/storage] Define a storage task source (PR #155) (Monday, 16 January)
• Re: [whatwg/storage] Define task source (#89) (Monday, 16 January)
• Re: [whatwg/storage] Define a storage task source (PR #155) (Monday, 16 January)
• Re: [whatwg/storage] Define a storage task source (PR #155) (Monday, 16 January)
• Re: [whatwg/storage] Define a storage task source (PR #155) (Monday, 16 January)
• Re: [whatwg/xhr] Add link to declarative shadow dom opt-in (#300) (Saturday, 14 January)
• Re: [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733) (Saturday, 14 January)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 13 January)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 13 January)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 13 January)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 13 January)
• Re: [whatwg/url] Named validation errors (#502) (Friday, 13 January)
• Re: [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733) (Friday, 13 January)
• Re: [whatwg/storage] Define a storage task source (PR #155) (Friday, 13 January)
• Re: [whatwg/storage] Define a storage task source (PR #155) (Friday, 13 January)
• Re: [whatwg/storage] Define a storage task source (PR #155) (Friday, 13 January)
• Re: [whatwg/storage] Define a storage task source (PR #155) (Friday, 13 January)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Friday, 13 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Friday, 13 January)
• Re: [whatwg/fetch] blob: URLs and range requests (#1070) (Friday, 13 January)
• Re: [whatwg/fetch] Editorial: Add <div algorithm> tags to fetch (PR #1591) (Friday, 13 January)
• Re: [whatwg/fetch] Editorial: Add <div algorithm> tags to fetch (PR #1591) (Friday, 13 January)
• Re: [whatwg/fetch] Editorial: Add <div algorithm> tags to fetch (PR #1591) (Friday, 13 January)
• Re: [whatwg/fetch] Editorial: Add <div algorithm> tags to fetch (PR #1591) (Friday, 13 January)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Friday, 13 January)
• Re: [whatwg/url] Issues with UTS #46 tests (#341) (Thursday, 12 January)
• [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733) (Thursday, 12 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Thursday, 12 January)
• Re: [whatwg/fetch] COEP:credentialless and the HTTP cache. (#1253) (Thursday, 12 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Thursday, 12 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Thursday, 12 January)
• Re: [whatwg/url] can't parse urls starting with xn-- (#438) (Thursday, 12 January)
• Re: [whatwg/url] can't parse urls starting with xn-- (#438) (Thursday, 12 January)
• Re: [whatwg/dom] Make Document origin alias its policy container's origin. (PR #1142) (Wednesday, 11 January)
• Re: [whatwg/dom] Make Document origin alias its policy container's origin. (PR #1142) (Wednesday, 11 January)
• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Wednesday, 11 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Wednesday, 11 January)
• Re: [whatwg/fetch] Update RFC 7234 usage to RFC 9111 (Issue #1558) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: account for HTTP updates (PR #1587) (Tuesday, 10 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: account for HTTP updates (PR #1587) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: account for HTTP updates (PR #1587) (Tuesday, 10 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 10 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 10 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 10 January)
• Re: [whatwg/url] Issues with UTS #46 tests (#341) (Tuesday, 10 January)
• Re: [whatwg/url] can't parse urls starting with xn-- (#438) (Tuesday, 10 January)
• Re: [whatwg/url] Double-encoded IDNA labels don't roundtrip (#603) (Tuesday, 10 January)
• Re: [whatwg/url] Double-encoded IDNA labels don't roundtrip (#603) (Tuesday, 10 January)
• Re: [whatwg/url] Double-encoded IDNA labels don't roundtrip (#603) (Tuesday, 10 January)
• Re: [whatwg/url] can't parse urls starting with xn-- (#438) (Tuesday, 10 January)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Tuesday, 10 January)
• Re: [whatwg/fetch] Update RFC 7234 usage to RFC 9111 (Issue #1558) (Monday, 9 January)
• Re: [whatwg/fetch] Editorial: account for HTTP updates (PR #1587) (Monday, 9 January)
• Re: [whatwg/fetch] Editorial: account for HTTP updates (PR #1587) (Monday, 9 January)
• [whatwg/fetch] Editorial: account for HTTP updates (PR #1587) (Friday, 6 January)
• Re: [whatwg/fetch] Update RFC 7234 usage to RFC 9111 (Issue #1558) (Friday, 6 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Thursday, 5 January)
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Wednesday, 4 January)
• Re: [whatwg/url] Allow encoding of null values. (Issue #732) (Wednesday, 4 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Tuesday, 3 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Tuesday, 3 January)
• Re: [whatwg/fetch] Editorial: correct keepalive note (PR #1586) (Tuesday, 3 January)
• [whatwg/fetch] Editorial: correct keepalive note (PR #1586) (Tuesday, 3 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Tuesday, 3 January)
• Re: [whatwg/fetch] Editorial: clean up definitions of network errors (PR #1561) (Tuesday, 3 January)
• Re: [whatwg/fetch] Editorial: clean up definitions of network errors (PR #1561) (Tuesday, 3 January)
• Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. #1536 (PR #1536) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Does Server-Timing work when not exposed through Access-Control-Expose-Headers? (Issue #1511) (Tuesday, 3 January)
• Re: [whatwg/fetch] Use internal response for Server-Timing (PR #1584) (Tuesday, 3 January)
• Re: [whatwg/fetch] Use internal response for Server-Timing (PR #1584) (Tuesday, 3 January)
• Re: [whatwg/fetch] Use internal response for Server-Timing (PR #1584) (Tuesday, 3 January)
• Re: [whatwg/fetch] Editorial: add <div algorithm> to HTTP extensions (PR #1582) (Tuesday, 3 January)
• Re: [whatwg/fetch] Editorial: add <div algorithm> to HTTP extensions (PR #1582) (Tuesday, 3 January)
• Re: [whatwg/fetch] Fix bikeshed link errors for implementation-defined and url (Issue #1580) (Tuesday, 3 January)
• Re: [whatwg/fetch] Editorial: Fix implementation-defined links (PR #1581) (Tuesday, 3 January)
• Re: [whatwg/webidl] Decimal regular expression has “dead code” (so to speak) (Issue #1218) (Monday, 2 January)
• Re: [whatwg/url] Setters can cause failure to roundtrip (#651) (Monday, 2 January)
• Re: [whatwg/url] Ensure the API roundtrips for opaque paths (PR #728) (Monday, 2 January)
• Re: [whatwg/fetch] Looking for private communication channel (Issue #1583) (Monday, 2 January)
• Re: [whatwg/fetch] Looking for private communication channel (Issue #1583) (Monday, 2 January)

Anton Bessonov

• Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226) (Wednesday, 25 January)
• Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226) (Wednesday, 25 January)
• Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226) (Sunday, 22 January)

arturjanc

• Re: [whatwg/fetch] Discuss: Removing `cache: reload` option from the API (#902) (Monday, 16 January)

Austin Sullivan

• [w3ctag/design-reviews] Moving non-OPFS files for the File System Access API (Issue #805) (Tuesday, 17 January)
• Re: [whatwg/storage] Define a storage task source (PR #155) (Friday, 13 January)
• [whatwg/storage] Define a storage task source (PR #155) (Tuesday, 10 January)

Avi Drissman

• Re: [w3c/editing] Change the types used on macOS (PR #416) (Thursday, 12 January)

Azycek1

• [whatwg/encoding] Password (Issue #300) (Thursday, 5 January)

Bar Hemo

• Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989) (Thursday, 26 January)

bemes9226

• [whatwg/dom] document.execCommand('copy') is deprecated so is it any other solution for support ios device. (Issue #1144) (Wednesday, 18 January)

Ben Francis

• Re: [w3c/manifest] Manifest processing should not be a function of document URL (#668) (Thursday, 19 January)

Ben Kelly

• Re: [whatwg/dom] Make Document origin alias its policy container's origin. (PR #1142) (Wednesday, 11 January)
• [whatwg/dom] Make Document origin alias its policy container's origin. (PR #1142) (Tuesday, 10 January)

Benjamin De Kosnik

• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Thursday, 19 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Thursday, 19 January)

bigopon

• Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819) (Monday, 30 January)

Brian E Carpenter

• Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Thursday, 19 January)
• Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Thursday, 19 January)

Brian Kardell

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Wednesday, 25 January)

Bruce B. Anderson

• Re: [WICG/webcomponents] Explicit support for nested forms inside ShadowRoots (Issue #981) (Sunday, 1 January)

bvandersloot-mozilla

• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Monday, 16 January)
• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Monday, 16 January)

Carlos Lopez

• Re: [whatwg/dom] Allow custom "get the parent" algorithms for EventTargets (#583) (Monday, 30 January)
• Re: [WICG/webcomponents] Shadow dom innerhtml and CSP unsafe-inline (#627) (Monday, 23 January)
• Re: [WICG/webcomponents] HTML Modules: JavaScript Scoping of ShadowDom Children (Issue #959) (Wednesday, 11 January)

chaals

• [w3c/permissions] add accessibility considerations (PR #412) (Wednesday, 25 January)

Charlie Harrison

• Re: [w3ctag/design-reviews] Review Request for Attribution Reporting API (Issue #724) (Tuesday, 3 January)

Chris Dumez

• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Wednesday, 25 January)
• Re: [w3c/gamepad] GamepadHapticActuator.playEffect() algorithm seems wrong with regards to `[[playingEffectPromise]]` (Issue #179) (Wednesday, 11 January)
• Re: [w3c/gamepad] GamepadHapticActuator.playEffect() algorithm seems wrong with regards to `[[playingEffectPromise]]` (Issue #179) (Wednesday, 11 January)
• [w3c/gamepad] GamepadHapticActuator.playEffect() algorithm seems wrong with regards to `[[playingEffectPromise]]` (Issue #179) (Wednesday, 11 January)
• Re: [w3c/gamepad] Shouldn't Gamepad.vibrationActuator be nullable? (Issue #178) (Tuesday, 10 January)
• [w3c/gamepad] Shouldn't Gamepad.vibrationActuator be nullable? (Issue #178) (Tuesday, 10 January)
• Re: [w3c/gamepad] Valid values for GamepadEffectParameters.strongMagnitude / weakMagnitude (Issue #176) (Tuesday, 10 January)
• Re: [w3c/gamepad] Valid values for GamepadEffectParameters.strongMagnitude / weakMagnitude (Issue #176) (Tuesday, 10 January)
• Re: [w3c/gamepad] Specify that GamepadEffectParameters.startDelay is a value in milliseconds (Issue #177) (Tuesday, 10 January)
• [w3c/gamepad] Specify that GamepadEffectParameters.startDelay is a value in milliseconds (Issue #177) (Tuesday, 10 January)
• Re: [w3c/gamepad] Valid values for GamepadEffectParameters.strongMagnitude / weakMagnitude (Issue #176) (Tuesday, 10 January)
• [w3c/gamepad] Valid values for GamepadEffectParameters.strongMagnitude / weakMagnitude (Issue #176) (Tuesday, 10 January)

Chris Harrelson

• Re: [whatwg/dom] Add convenient, ergonomic, performant API for sorting siblings (#586) (Thursday, 12 January)

Christophe Coevoet

• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) (Tuesday, 31 January)

chydonp2

• Re: [w3c/manifest] chore: tidy up index.html (#1028) (f8d326b) (Wednesday, 11 January)
• Re: [w3c/manifest] chore: tidy up index.html (#1028) (f8d326b) (Wednesday, 11 January)

Cklim143

• Re: [w3c/IndexedDB] Future: Support Tuples as compound keys (Issue #390) (Tuesday, 24 January)

Dan Robertson

• Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Header class (PR #1596) (Thursday, 26 January)
• Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Header class (PR #1596) (Thursday, 26 January)
• Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Header class (PR #1596) (Wednesday, 25 January)
• [whatwg/fetch] Editorial: add <div algorithm> wrappers to Header class (PR #1596) (Wednesday, 25 January)
• Re: [whatwg/fetch] blob: URLs and range requests (#1070) (Tuesday, 17 January)
• [whatwg/fetch] Editorial: Add <div algorithm> tags to fetch (PR #1591) (Thursday, 12 January)
• Re: [whatwg/fetch] Editorial: account for HTTP updates (PR #1587) (Monday, 9 January)
• Re: [whatwg/fetch] Editorial: account for HTTP updates (PR #1587) (Friday, 6 January)
• Re: [whatwg/fetch] blob: URLs and range requests (#1070) (Friday, 6 January)
• Re: [whatwg/fetch] Editorial: Fix implementation-defined links (PR #1581) (Monday, 2 January)
• Re: [whatwg/fetch] Fix bikeshed link errors for implementation-definedd and url (Issue #1580) (Monday, 2 January)
• Re: [whatwg/fetch] Editorial: Fix url and implementation-defined links (PR #1581) (Monday, 2 January)

Daniel (dB.) Doubrovkine

• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Thursday, 5 January)
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Thursday, 5 January)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 (Issue #811) (Monday, 30 January)
• Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Friday, 27 January)
• Re: [w3ctag/design-reviews] Spec review for CSS Nesting (Issue #791) (Wednesday, 4 January)
• Re: [w3ctag/design-reviews] How should web standards use the new JavaScript Symbol.dispose protocol? (Issue #794) (Wednesday, 4 January)

Daniel Ehrenberg

• Re: [w3ctag/design-reviews] How should web standards use the new JavaScript Symbol.dispose protocol? (Discussion #800) (Thursday, 19 January)
• Re: [w3ctag/design-reviews] How should web standards use the new JavaScript Symbol.dispose protocol? (Discussion #800) (Thursday, 19 January)
• Re: [w3ctag/design-reviews] How should web standards use the new JavaScript Symbol.dispose protocol? (Discussion #800) (Wednesday, 18 January)

Danny Engelman

• Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Thursday, 12 January)
• [WICG/webcomponents] FireFox ::part styles its own shadowRoot, which it should not? (Issue #982) (Sunday, 1 January)

Darien Maillet Valentine

• Re: [whatwg/webidl] Make the dictionary <-> ordered map correspondence clearer about order (Issue #1257) (Thursday, 26 January)

David Bokan

• Re: [w3c/uievents] definition of MouseEvent.clientX and clientY seems wrong (Issue #339) (Tuesday, 3 January)
• Re: [w3c/uievents] definition of MouseEvent.clientX and clientY seems wrong (Issue #339) (Tuesday, 3 January)

David Judge

• [w3c/ServiceWorker] Self hosted applications (Issue #1668) (Saturday, 21 January)

David Singer

• Re: [whatwg/url] Editorial: define URL path segment (PR #736) (Monday, 16 January)

Denis Pushkarev

• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Tuesday, 24 January)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Tuesday, 24 January)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Saturday, 21 January)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Saturday, 21 January)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Friday, 20 January)

dimtabu

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

Dmitry Iv.

• Re: [WICG/webcomponents] Template instantiation: Fix typo (PR #948) (Wednesday, 25 January)

Domenic Denicola

• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 27 January)
• Re: [whatwg/webidl] Make the dictionary <-> ordered map correspondence clearer about order (Issue #1257) (Thursday, 26 January)
• [whatwg/webidl] Make the dictionary <-> ordered map correspondence clearer about order (Issue #1257) (Thursday, 26 January)
• Re: [whatwg/webidl] Allow DOMException subclasses to be used as exceptions (PR #1211) (Wednesday, 25 January)
• Re: [whatwg/webidl] Allow DOMException subclasses to be used as exceptions (PR #1211) (Wednesday, 25 January)
• Re: [whatwg/dom] Proposal: AbortSignal.wrap (Issue #1147) (Wednesday, 25 January)
• Re: [whatwg/url] Named validation errors (#502) (Wednesday, 25 January)
• Re: [whatwg/dom] Provide a mechanism for allowing EventTarget trees to make use of bubbling (Issue #1146) (Wednesday, 25 January)
• Re: [whatwg/dom] Provide a mechanism for allowing EventTarget trees to make use of bubbling (Issue #1146) (Wednesday, 25 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 24 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 24 January)
• Re: [whatwg/url] Editorial: rely on Infra's code point length (PR #745) (Monday, 23 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 23 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 23 January)
• Re: [whatwg/url] Redo validation errors in the IPv4 parser (PR #739) (Thursday, 19 January)
• Re: [whatwg/url] Meta: preserve IDs per anchor permanence policy (PR #741) (Thursday, 19 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Thursday, 19 January)
• Re: [w3ctag/design-reviews] How should web standards use the new JavaScript Symbol.dispose protocol? (Discussion #800) (Thursday, 19 January)
• Re: [w3ctag/design-reviews] How should web standards use the new JavaScript Symbol.dispose protocol? (Discussion #800) (Wednesday, 18 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 18 January)
• Re: [whatwg/url] Editorial: point out API section is not suitable for all (PR #738) (Tuesday, 17 January)
• Re: [whatwg/url] Editorial: define domain label (PR #737) (Tuesday, 17 January)
• Re: [whatwg/fetch] `prefetch` initiator appears to be unused (#1008) (Tuesday, 17 January)
• Re: [whatwg/fetch] `prefetch` initiator appears to be unused (#1008) (Tuesday, 17 January)
• Re: [whatwg/url] Editorial: define URL path segment (PR #736) (Tuesday, 17 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2023 (PR #214) (Monday, 16 January)
• Re: [whatwg/url] Windows drive letter uppercasing (#515) (Monday, 16 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Monday, 16 January)
• Re: [whatwg/storage] Define a storage task source (PR #155) (Monday, 16 January)
• Re: [whatwg/url] Windows drive letter uppercasing (#515) (Saturday, 14 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 13 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 13 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: account for HTTP updates (PR #1587) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 10 January)
• Re: [w3c/uievents] Specify the arguments of initMouseEvent() (#136) (Saturday, 7 January)
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Wednesday, 4 January)
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Wednesday, 4 January)
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Wednesday, 4 January)

Dominic Farolino

• Re: [whatwg/fetch] String representations for Fetch API objects (Issue #1575) (Tuesday, 24 January)
• Re: [whatwg/fetch] String representations for Fetch API objects (Issue #1575) (Monday, 23 January)

dontcallmedom-bot

• [w3c/uievents] Broken references in UI Events (Issue #340) (Friday, 27 January)
• [w3c/touch-events] Broken references in Touch Events - Level 2 (Issue #134) (Friday, 27 January)
• [w3c/ServiceWorker] Broken references in Service Workers Nightly (Issue #1669) (Friday, 27 January)

Edward Fox

• Re: [w3c/ServiceWorker] Questions regarding inevitable nature of performance gains and losses of ServiceWorker (Issue #1667) (Monday, 23 January)
• Re: [w3c/ServiceWorker] Questions regarding inevitable nature of performance gains and losses of ServiceWorker (Issue #1667) (Monday, 23 January)
• Re: [w3c/ServiceWorker] Questions regarding inevitable nature of performance gains and losses of ServiceWorker (Issue #1667) (Monday, 23 January)
• [w3c/ServiceWorker] Questions regarding inevitable nature of performance gains and losses of ServiceWorker (Issue #1667) (Friday, 20 January)

Elad Alon

• Re: [w3ctag/design-reviews] Collection of Screensharing-related UX Hints (Issue #744) (Monday, 9 January)

Emilio Cobos Álvarez

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 31 January)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Monday, 30 January)

fantasai

• Re: [w3ctag/design-reviews] baseline-source (Issue #801) (Tuesday, 17 January)
• Re: [w3ctag/design-reviews] baseline-source (Issue #801) (Thursday, 12 January)

fogoplayer

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

Francis McCabe

• [w3ctag/design-reviews] WebAssembly JavaScript Promise Integration API (Issue #809) (Tuesday, 24 January)

Frank Lemanschik

• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Tuesday, 24 January)

genaldo1

• [whatwg/streams] Genaldo Holanda (Issue #1251) (Friday, 13 January)

Guiccice

• Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Monday, 9 January)

Harald Alvestrand

• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Thursday, 26 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 17 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 17 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Wednesday, 11 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 10 January)
• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Tuesday, 10 January)

hathiphant

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Thursday, 12 January)

Henri Sivonen

• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Tuesday, 17 January)

Henrik Skupin

• Re: [whatwg/fetch] Fix bikeshed link errors for implementation-definedd and url (Issue #1580) (Monday, 2 January)

Ian Kilpatrick

• [w3ctag/design-reviews] baseline-source (Issue #801) (Wednesday, 11 January)

ianbjacobs

• [w3ctag/design-reviews] Request for review of two changes to Secure Payment Confirmation prior to CR (Issue #802) (Wednesday, 11 January)

James M Snell

• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Tuesday, 31 January)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Thursday, 26 January)
• [whatwg/dom] Proposal: AbortSignal.wrap (Issue #1147) (Wednesday, 25 January)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Sunday, 22 January)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Saturday, 21 January)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Friday, 20 January)
• Re: [whatwg/url] Add a size getter to URLSearchParams (PR #734) (Friday, 20 January)
• Re: [whatwg/url] Add value argument to URLSearchParams's has() and delete() (PR #735) (Friday, 20 January)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Friday, 13 January)
• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Friday, 13 January)

Jan-Ivar Bruaroey

• Re: [whatwg/webidl] Allow DOMException subclasses to be used as exceptions (PR #1211) (Wednesday, 25 January)
• Re: [whatwg/webidl] Allow DOMException subclasses to be used as exceptions (PR #1211) (Tuesday, 24 January)

Jeffrey Yasskin

• Re: [w3c/permissions] No references to accessibility (Issue #411) (Wednesday, 25 January)
• Re: [w3c/permissions] add accessibility considerations (PR #412) (Wednesday, 25 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 4 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 4 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 3 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 3 January)

Jeremy Roman

• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Tuesday, 17 January)

Jesper van den Ende

• Re: [w3c/ServiceWorker] windowClients state change events - loaded/unloaded (#1269) (Friday, 6 January)

jfjrvb24

• [whatwg/webidl] Intent to use Constants (Issue #1252) (Wednesday, 4 January)

Jimmy Wärting

• Re: [whatwg/url] Support relative URLs (#531) (Thursday, 5 January)
• Re: [w3c/FileAPI] Consider adding `blob.dataUrl()` method, or some other analogue to `readAsDataURL` (Issue #179) (Sunday, 1 January)

Johann Hofmann

• Re: [w3ctag/design-reviews] Spec review for Storage Access API (Issue #807) (Wednesday, 18 January)
• [w3ctag/design-reviews] Spec review for Storage Access API (Issue #807) (Wednesday, 18 January)

Johannes Wilm

• Re: [w3c/editing] Status of specs we are working on (Issue #413) (Thursday, 12 January)

Jon Jensen

• Re: [w3ctag/design-reviews] FYI - Add optional `submitter` parameter to the `FormData` constructor (Issue #812) (Tuesday, 31 January)
• Re: [w3ctag/design-reviews] FYI - Add optional `submitter` parameter to the `FormData` constructor (Issue #812) (Monday, 30 January)
• [w3ctag/design-reviews] FYI - Add optional `submitter` parameter to the `FormData` constructor (Issue #812) (Monday, 30 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Saturday, 28 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Thursday, 26 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Thursday, 26 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Wednesday, 25 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Wednesday, 25 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Wednesday, 25 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Wednesday, 25 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Wednesday, 25 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Tuesday, 24 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Monday, 23 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Monday, 23 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Thursday, 12 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Thursday, 12 January)
• [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Thursday, 12 January)

jub0bs

• [whatwg/fetch] Clarify why omitting CORS headers in the preflight response helps against side-channel attacks (Issue #1588) (Monday, 9 January)

JunLiangWang

• [whatwg/dom] Add Simplified Chinese translation (Issue #1141) (Tuesday, 10 January)

Justin Fagnani

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 31 January)
• Re: [WICG/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Friday, 27 January)
• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Wednesday, 25 January)
• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Monday, 23 January)
• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Monday, 23 January)

Justin Richer

• [whatwg/url] Anchor permanence for URI parameters (Issue #740) (Wednesday, 18 January)

Jérôme Beau

• Re: [WICG/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Friday, 27 January)

Kagami Sascha Rosylight

• [whatwg/streams] Should the "set up" algorithm for IDL-created WritableStreams wrap the write algorithm? (Issue #1253) (Monday, 30 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 27 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 27 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 27 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Thursday, 26 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Thursday, 26 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 23 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 23 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 23 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Monday, 23 January)
• [whatwg/streams] Should the underlying source be pinged for cancel when a close request exists? (Issue #1252) (Saturday, 21 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Thursday, 19 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Thursday, 19 January)
• Re: [w3c/FileAPI] createObjectURL with ReadableStream (Issue #189) (Thursday, 19 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 13 January)
• Re: [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 13 January)
• [w3c/FileAPI] Return a byte stream from "get stream" algorithm (PR #188) (Friday, 13 January)
• [whatwg/fetch] Set body with byte reading support (PR #1593) (Friday, 13 January)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Tuesday, 10 January)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Tuesday, 10 January)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 9 January)

Karl

• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Sunday, 29 January)
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Saturday, 28 January)
• Re: [whatwg/url] Meta: UTS46 feedback (Issue #744) (Monday, 23 January)
• Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Thursday, 19 January)
• Re: [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733) (Friday, 13 January)

Kasbr

• Re: [w3c/editing] Hi (Issue #418) (Saturday, 28 January)
• [w3c/editing] Hi (Issue #418) (Saturday, 28 January)

Keith Cirkel

• Re: [whatwg/dom] Allow custom "get the parent" algorithms for EventTargets (#583) (Monday, 30 January)
• Re: [whatwg/dom] Allow custom "get the parent" algorithms for EventTargets (#583) (Wednesday, 25 January)
• Re: [whatwg/dom] Provide a mechanism for allowing EventTarget trees to make use of bubbling (Issue #1146) (Wednesday, 25 January)
• [whatwg/dom] Provide a mechanism for allowing EventTarget trees to make use of bubbling (Issue #1146) (Tuesday, 24 January)

Kevin Gibbons

• Re: [w3ctag/design-reviews] How should web standards use the new JavaScript Symbol.dispose protocol? (Discussion #800) (Thursday, 19 January)

Khushal Sagar

• Re: [w3ctag/design-reviews] View Transitions API (Issue #748) (Wednesday, 11 January)

Kongpcmail

• Re: [w3c/IndexedDB] Clarify the handling of +0 and -0 in keys (Issue #375) (Sunday, 15 January)

Lavinia

• [whatwg/webidl] Intent to use bigint/numeric union (Issue #1254) (Sunday, 8 January)

Lea Verou

• Re: [w3ctag/design-reviews] FYI - Add optional `submitter` parameter to the `FormData` constructor (Issue #812) (Tuesday, 31 January)
• Re: [w3ctag/design-reviews] FYI - Add optional `submitter` parameter to the `FormData` constructor (Issue #812) (Tuesday, 31 January)
• Re: [w3ctag/design-reviews] FYI - Add optional `submitter` parameter to the `FormData` constructor (Issue #812) (Monday, 30 January)
• Re: [w3ctag/design-reviews] baseline-source (Issue #801) (Monday, 16 January)
• Re: [w3ctag/design-reviews] baseline-source (Issue #801) (Monday, 16 January)
• Re: [w3ctag/design-reviews] UI Events Keyboard Events Key Values review request (Issue #789) (Wednesday, 11 January)
• Re: [w3ctag/design-reviews] UI Events Keyboard Events Key Values review request (Issue #789) (Wednesday, 11 January)
• Re: [w3ctag/design-reviews] View Transitions API (Issue #748) (Tuesday, 10 January)

Lei Mingyu

• Re: [w3c/IndexedDB] How should IDB connections and outstanding IDB transactions behave when a page enters back/forward cache? (Issue #381) (Wednesday, 11 January)

Leo Balter

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Wednesday, 25 January)

Liam Murphy

• Re: [whatwg/webidl] WIP: switching maplike/setlike to use infra maps and sets (PR #1138) (Monday, 30 January)

Logan Rutkowski

• Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) (Monday, 2 January)

Luca Casonato

• Re: [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Thursday, 12 January)
• [whatwg/fetch] Add size limiter to `Body#formData` method (Issue #1592) (Thursday, 12 January)

lxylxy123456

• [whatwg/fetch] Possible typo in "The `Allow` header is not relevant for the purp..." (Issue #1598) (Thursday, 26 January)

Léonie Watson

• Re: [w3c/uievents-key] Tasks for wide review (Issue #57) (Monday, 30 January)
• Re: [w3c/uievents-code] Tasks for wide review (Issue #35) (Monday, 30 January)
• Re: [w3ctag/design-reviews] UI Events Keyboard Events Key Values review request (Issue #789) (Monday, 30 January)
• Re: [w3ctag/design-reviews] UI Events Keyboard Events Code Values review request (Issue #790) (Monday, 30 January)

Makoto Kato

• Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Tuesday, 31 January)
• Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Tuesday, 24 January)

Marcos Cáceres

• Re: [w3c/screen-orientation] Consume user activation (PR #218) (Tuesday, 24 January)
• Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Monday, 23 January)
• Re: [w3c/screen-orientation] Tidied up document using tidy-html5 (PR #241) (Monday, 23 January)
• Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Monday, 23 January)
• Re: [w3c/manifest] Ran tidy (PR #1067) (Monday, 23 January)
• Re: [w3c/manifest] Minor editorial cleanup / refactor of Manifest processing steps (PR #1066) (Monday, 23 January)

Marijn Kruisselbrink

• Re: [w3c/FileAPI] Return a byte stream from "get stream" algorithm (PR #188) (Tuesday, 17 January)

Mark Davis

• Re: [whatwg/url] Issues with UTS #46 tests (#341) (Friday, 20 January)
• Re: [whatwg/url] Issues with UTS #46 tests (#341) (Friday, 20 January)
• Re: [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733) (Tuesday, 17 January)
• Re: [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733) (Friday, 13 January)

Mark Nottingham

• Re: [whatwg/fetch] Specify cache mode impact on request headers (Issue #1599) (Tuesday, 31 January)
• Re: [whatwg/url] Should we ignore IPv6 zone identifiers when parsing a URL? (Issue #742) (Friday, 20 January)
• Re: [whatwg/url] Should we ignore IPv6 zone identifiers when parsing a URL? (Issue #742) (Thursday, 19 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Wednesday, 4 January)

Markus Scherer

• Re: [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733) (Tuesday, 17 January)
• Re: [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733) (Friday, 13 January)

Martin Thomson

• Re: [whatwg/url] Should we ignore IPv6 zone identifiers when parsing a URL? (Issue #742) (Monday, 23 January)
• Re: [whatwg/url] Should we ignore IPv6 zone identifiers when parsing a URL? (Issue #742) (Friday, 20 January)

Mason Freed

• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Friday, 27 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Friday, 27 January)
• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Wednesday, 25 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Monday, 23 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Monday, 23 January)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Monday, 23 January)
• Re: [whatwg/xhr] Add optional submitter argument to FormData constructor (PR #366) (Monday, 23 January)
• [whatwg/dom] Add DOMParser option to parse declarative shadow DOM (Issue #1145) (Thursday, 19 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Thursday, 19 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Thursday, 19 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Thursday, 19 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Thursday, 19 January)
• Re: [whatwg/dom] Add cloneable option to ShadowRootInit (Issue #1137) (Saturday, 14 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Saturday, 14 January)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Saturday, 14 January)
• Re: [whatwg/dom] Add cloneable option to ShadowRootInit (Issue #1137) (Friday, 13 January)
• Re: [whatwg/xhr] Add link to declarative shadow dom opt-in (#300) (Friday, 13 January)
• Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743) (Tuesday, 10 January)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Monday, 2 January)

Matt Giuca

• Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Wednesday, 25 January)
• Re: [w3c/manifest] Minor editorial cleanup / refactor of Manifest processing steps (PR #1066) (Wednesday, 25 January)
• Re: [w3c/manifest] Minor editorial cleanup / refactor of Manifest processing steps (PR #1066) (Monday, 23 January)
• Re: [w3c/manifest] Minor editorial cleanup / refactor of Manifest processing steps (PR #1066) (Monday, 23 January)
• Re: [w3c/manifest] Minor editorial cleanup / refactor of Manifest processing steps (PR #1066) (Monday, 23 January)
• Re: [w3c/manifest] Minor editorial cleanup / refactor of Manifest processing steps (PR #1066) (Monday, 23 January)
• Re: [w3c/manifest] Ran tidy (PR #1067) (Monday, 23 January)
• Re: [w3c/manifest] Ran tidy (PR #1067) (Monday, 23 January)
• Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Friday, 20 January)
• Re: [w3c/manifest] Manifest processing should not be a function of document URL (#668) (Friday, 20 January)
• Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Friday, 20 January)
• [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Friday, 20 January)
• [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (Issue #1068) (Friday, 20 January)
• Re: [w3c/manifest] Manifest processing should not be a function of document URL (#668) (Friday, 20 January)
• [w3c/manifest] Ran tidy (PR #1067) (Friday, 20 January)
• [w3c/manifest] Minor editorial cleanup / refactor of Manifest processing steps (PR #1066) (Friday, 20 January)
• Re: [w3c/manifest] Manifest processing should not be a function of document URL (#668) (Thursday, 19 January)
• Re: [w3c/manifest] Manifest processing should not be a function of document URL (#668) (Wednesday, 18 January)
• Re: [w3c/manifest] Manifest processing should not be a function of document URL (#668) (Wednesday, 18 January)

Matt Menke

• Re: [w3ctag/design-reviews] WebAuthn PRF extension (Issue #806) (Tuesday, 24 January)
• Re: [w3ctag/design-reviews] WebAuthn PRF extension (Issue #806) (Tuesday, 24 January)

Matthew Phillips

• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Tuesday, 17 January)
• Re: [whatwg/dom] Should there be a declarative version of adoptedStyleSheets? (#910) (Tuesday, 17 January)
• Re: [whatwg/dom] Should there be a declarative version of adoptedStyleSheets? (#910) (Tuesday, 17 January)

Menukavp

• [whatwg/url] https://dom.spec.whatwg.org/#event (Issue #747) (Thursday, 26 January)

Michael Cooper

• Re: [w3ctag/design-reviews] Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 (Issue #811) (Tuesday, 31 January)
• [w3ctag/design-reviews] Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 (Issue #811) (Monday, 30 January)

mreichhoff

• Re: [w3ctag/design-reviews] Spec Review for requestStorageAccessForOrigin (Issue #808) (Monday, 23 January)
• [w3ctag/design-reviews] Spec Review for requestStorageAccessForOrigin (Issue #808) (Monday, 23 January)

Mustaq Ahmed

• Re: [w3c/uievents] definition of MouseEvent.clientX and clientY seems wrong (Issue #339) (Tuesday, 3 January)
• Re: [w3c/uievents] definition of MouseEvent.clientX and clientY seems wrong (Issue #339) (Tuesday, 3 January)
• Re: [w3c/uievents] definition of MouseEvent.clientX and clientY seems wrong (Issue #339) (Tuesday, 3 January)

NhutTran98

• Re: [w3c/manifest] About updating the manifest (Issue #1060) (Thursday, 19 January)

Noam Rosenthal

• [whatwg/fetch] worker timing doesn't need to be TAO protected for subresources (Issue #1597) (Wednesday, 25 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Wednesday, 25 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Wednesday, 25 January)
• Re: [whatwg/fetch] Editorial: Remove `prefetch-src` (PR #1595) (Wednesday, 25 January)
• Re: [whatwg/fetch] Editorial: Remove `prefetch-src` (PR #1595) (Wednesday, 25 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Wednesday, 25 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Wednesday, 25 January)
• Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483) (Wednesday, 25 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Wednesday, 18 January)
• Re: [whatwg/fetch] Editorial: Remove `prefetch-src` (PR #1595) (Wednesday, 18 January)
• Re: [whatwg/fetch] Editorial: Remove `prefetch-src` (PR #1595) (Wednesday, 18 January)
• [whatwg/fetch] Editorial: Remove `prefetch-src` (PR #1595) (Wednesday, 18 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 18 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 18 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 18 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 18 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 18 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 18 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 18 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 18 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Monday, 16 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Friday, 13 January)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Friday, 13 January)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Friday, 13 January)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Friday, 13 January)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Friday, 13 January)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Friday, 13 January)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Friday, 13 January)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Friday, 13 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Wednesday, 11 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 11 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 10 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 10 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Saturday, 7 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Saturday, 7 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Saturday, 7 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Saturday, 7 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Friday, 6 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Friday, 6 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Friday, 6 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 5 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 4 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 4 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 4 January)
• Re: [whatwg/fetch] Send `Sec-Purpose: prefetch` header for prefetch requests (PR #1576) (Wednesday, 4 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 4 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 4 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Tuesday, 3 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Tuesday, 3 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Tuesday, 3 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Tuesday, 3 January)
• Re: [whatwg/fetch] Body sizes should be CORS rather than TAO protected (PR #1556) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579) (Tuesday, 3 January)
• Re: [whatwg/fetch] Use internal response for Server-Timing (PR #1584) (Tuesday, 3 January)
• Re: [whatwg/fetch] Use internal response for Server-Timing (PR #1584) (Tuesday, 3 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Monday, 2 January)
• [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Monday, 2 January)
• [whatwg/fetch] Use internal response for Server-Timing (PR #1584) (Sunday, 1 January)

Nolan Lawson

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Thursday, 26 January)

npm1

• [w3ctag/design-reviews] FedCM multi IDP support (Issue #803) (Wednesday, 11 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Wednesday, 4 January)
• Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Tuesday, 3 January)

omarsandoval1

• Re: [w3c/ServiceWorker] [BUG] setTimeout/setInterval mix with importScripts leads to DOMExeption (#1580) (Wednesday, 25 January)

Owen Buckley

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Friday, 27 January)

Patrick H. Lauke

• Re: [w3c/touch-events] 'Retargeting steps' expose closed Shadow DOM to the outside world (#92) (Saturday, 28 January)
• Re: [w3c/touch-events] Update retargeting steps link (PR #135) (Saturday, 28 January)
• [w3c/touch-events] Update retargeting steps link (PR #135) (Saturday, 28 January)

Patrick Meenan

• [whatwg/fetch] Specify cache mode impact on request headers (Issue #1599) (Tuesday, 31 January)

Philip Jägenstedt

• Re: [whatwg/url] can't parse urls starting with xn-- (#438) (Wednesday, 11 January)

redone9211

• Re: [whatwg/fetch] Rename "extract-value flag" to "extract-value" and define it as a boolean (Issue #1567) (Sunday, 22 January)

Robin Berjon

• Re: [w3ctag/design-reviews] Early design review for the Topics API (Issue #726) (Saturday, 14 January)

Ron Buckton

• Re: [w3ctag/design-reviews] How should web standards use the new JavaScript Symbol.dispose protocol? (Discussion #800) (Friday, 20 January)

Rossen Atanassov

• Re: [w3ctag/design-reviews] Collection of Screensharing-related UX Hints (Issue #744) (Monday, 9 January)

Ryosuke Niwa

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 31 January)
• Re: [WICG/webcomponents] delegatesFocus and non-tabbable, focusable elements (Issue #977) (Friday, 13 January)
• Re: [WICG/webcomponents] delegatesFocus and non-tabbable, focusable elements (Issue #977) (Friday, 13 January)
• Re: [WICG/webcomponents] FireFox ::part styles its own shadowRoot, which it should not? (Issue #982) (Wednesday, 4 January)
• Re: [WICG/webcomponents] FireFox ::part styles its own shadowRoot, which it should not? (Issue #982) (Wednesday, 4 January)

Sam Gammon

• Re: [whatwg/fetch] String representations for Fetch API objects (Issue #1575) (Monday, 23 January)

sam goto

• Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Monday, 9 January)

Sami

• Re: [w3c/ServiceWorker] Service-Worker-Allowed can be cross-origin to the script URL. (#1307) (Tuesday, 10 January)

Samuel Williams

• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Sunday, 29 January)
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Sunday, 29 January)
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Thursday, 5 January)
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Wednesday, 4 January)
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Wednesday, 4 January)
• Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732) (Wednesday, 4 January)
• Re: [whatwg/url] Allow encoding of null values. (Issue #732) (Wednesday, 4 January)
• Re: [whatwg/url] Allow encoding of null values. (Issue #732) (Wednesday, 4 January)
• [whatwg/url] Allow encoding of null values. (Issue #732) (Wednesday, 4 January)

Sasha Firsov

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Thursday, 26 January)
• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Thursday, 19 January)

Satyam Kharote

• Re: [whatwg/fetch] Rename "extract-value flag" to "extract-value" and define it as a boolean (Issue #1567) (Tuesday, 17 January)
• Re: [whatwg/fetch] Rename "extract-value flag" to "extract-value" and define it as a boolean (Issue #1567) (Tuesday, 17 January)

sheribyrne

• [w3c/permissions] No references to accessibility (Issue #411) (Wednesday, 25 January)

Simon Pieters

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Monday, 30 January)
• Re: [w3c/uievents] Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) (#181) (Tuesday, 3 January)

Sira Thampitak

• Re: [whatwg/fetch] administrator (Issue #1589) (Wednesday, 11 January)
• [whatwg/fetch] administrator (Issue #1589) (Wednesday, 11 January)

smaug----

• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Monday, 30 January)
• Re: [whatwg/dom] Allow custom "get the parent" algorithms for EventTargets (#583) (Monday, 30 January)
• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Thursday, 26 January)

snianu

• Re: [w3c/editing] The Web Custom formats specification does not appropriately use the macOS API (Issue #412) (Thursday, 12 January)
• Re: [w3c/editing] Change the types used on macOS (PR #416) (Thursday, 12 January)
• Re: [w3c/editing] Change the types used on macOS (PR #416) (Thursday, 12 January)
• Re: [w3c/editing] Change the types used on macOS (PR #416) (Thursday, 12 January)

Spiritaine

• [whatwg/xhr] Real (Issue #365) (Wednesday, 11 January)

Steven

• Re: [whatwg/url] URL.relative proposal (#421) (Wednesday, 4 January)

Tab Atkins Jr.

• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Friday, 13 January)
• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Friday, 13 January)

Thomas Deinhamer

• Re: [w3c/uievents] Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) (#181) (Tuesday, 17 January)

Timothy Harvath

• Re: [whatwg/webidl] WEBNTRACK108 (Issue #1250) (Monday, 2 January)
• Re: [whatwg/webidl] WEBNTRACK108 (Issue #1250) (Monday, 2 January)
• Re: [whatwg/webidl] WEBNTRACK108 (Issue #1250) (Monday, 2 January)
• [whatwg/webidl] WEBNTRACK108 (Issue #1250) (Monday, 2 January)

timscharfenort11

• [whatwg/url] J (Issue #748) (Tuesday, 31 January)

Titouan Rigoudy

• Re: [whatwg/fetch] COEP:credentialless and the HTTP cache. (#1253) (Thursday, 12 January)

Tomasz Pluskiewicz

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

Toni Williams

• Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. #1536 (PR #1536) (Friday, 27 January)
• Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. #1536 (PR #1536) (Friday, 27 January)
• Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. #1536 (PR #1536) (Friday, 27 January)

Trevor Rowbotham

• Re: [whatwg/url] Named validation errors (#502) (Saturday, 28 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 24 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 24 January)
• Re: [whatwg/url] Named validation errors (#502) (Tuesday, 24 January)
• Re: [whatwg/url] Named validation errors (#502) (Sunday, 22 January)
• Re: [whatwg/url] Named validation errors (#502) (Sunday, 22 January)
• Re: [whatwg/url] Named validation errors (#502) (Sunday, 22 January)
• Re: [whatwg/url] Redo validation errors in the IPv4 parser (PR #739) (Tuesday, 17 January)

Valentin Gosu

• Re: [whatwg/url] Should we ignore IPv6 zone identifiers when parsing a URL? (Issue #742) (Monday, 23 January)
• [whatwg/url] Should we ignore IPv6 zone identifiers when parsing a URL? (Issue #742) (Thursday, 19 January)
• Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Thursday, 19 January)

Westbrook Johnson

• Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Thursday, 26 January)

WORMSS

• Re: [whatwg/url] size (or length) for URLSearchParams (#163) (Friday, 13 January)

Xiaocheng Hu

• Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969) (Thursday, 19 January)
• Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969) (Wednesday, 11 January)
• Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969) (Wednesday, 11 January)

Xidorn Quan

• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 31 January)

XOXO045

• [whatwg/webidl] B (Issue #1258) (Tuesday, 31 January)

yks-ny

• Re: [w3c/push-api] chore(tidy.yml): flip title and commit-message (629bb64) (Monday, 23 January)
• Re: [w3c/push-api] chore(tidy.yml): flip title and commit-message (629bb64) (Monday, 23 January)
• Re: [w3c/push-api] chore(tidy.yml): flip title and commit-message (629bb64) (Monday, 23 January)

youennf

• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Thursday, 26 January)

Yutaka Hirano

• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Tuesday, 24 January)

Yves Lafon

• Re: [w3ctag/design-reviews] UI Events Keyboard Events Code Values review request (Issue #790) (Tuesday, 10 January)
• Re: [w3ctag/design-reviews] UI Events Keyboard Events Code Values review request (Issue #790) (Tuesday, 10 January)

Zack Weinberg

• Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543) (Thursday, 12 January)

Zipdox2

• [w3c/FileAPI] createObjectURL with ReadableStream (Issue #189) (Thursday, 19 January)

Last message date: Tuesday, 31 January 2023 23:37:24 UTC