public-webapps-github@w3.org from November 2022 by author

11122670

Re: [whatwg/dom] Meta: my employer changed (6b3f055) (Wednesday, 2 November)

Abin K Paul

Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Wednesday, 30 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Monday, 14 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Monday, 14 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Monday, 14 November)
[w3ctag/design-reviews] Content-type in Resource Timing (Issue #785) (Monday, 14 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Saturday, 12 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Saturday, 12 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Saturday, 12 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Saturday, 12 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Monday, 7 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Monday, 7 November)

Adam Rice

Re: [whatwg/url] javascript: URL parsing (#307) (Wednesday, 30 November)
Re: [whatwg/fetch] Remove Authorization header upon cross-origin redirect (PR #1544) (Friday, 25 November)
Re: [whatwg/streams] Examine interaction of resizable array buffers with Streams (Issue #1248) (Tuesday, 22 November)
Re: [whatwg/streams] Examine interaction of resizable array buffers with Streams (Issue #1248) (Monday, 21 November)
[whatwg/streams] Examine interaction of resizable array buffers with Streams (Issue #1248) (Monday, 21 November)

Adrian Roselli

Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [whatwg/storage] Add a diagram for the storage model? (Issue #151) (Monday, 21 November)
Re: [whatwg/storage] Add a diagram for the storage model? (Issue #151) (Monday, 21 November)
Re: [whatwg/storage] Add a diagram for the storage model? (Issue #151) (Monday, 21 November)

Adrián Chaves

Re: [whatwg/url] Editorial: clarify the types of strings algorithms take and return (PR #719) (Friday, 25 November)

alancutter

[w3c/ServiceWorker] Add auto claim option to register() (Issue #1661) (Monday, 14 November)
Re: [w3c/manifest] Export processed manifest and application context definitions (PR #1062) (Wednesday, 9 November)
Re: [w3c/manifest] Export processed manifest and application context definitions (PR #1062) (Wednesday, 9 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Tuesday, 8 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Tuesday, 8 November)
Re: [w3c/manifest] Fix broken active-document reference (PR #1063) (Tuesday, 8 November)
[w3c/manifest] Fix broken active-document reference (PR #1063) (Tuesday, 8 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Tuesday, 8 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
[w3c/manifest] Export processed manifest and application context definitions (PR #1062) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Sunday, 6 November)
Re: [w3c/manifest] Define an algorithm for launching web app (PR #1056) (Sunday, 6 November)
Re: [w3c/manifest] Define an algorithm for launching web app (PR #1056) (Friday, 4 November)
Re: [w3c/manifest] Define an algorithm for launching web app (PR #1056) (Thursday, 3 November)
Re: [w3c/manifest] Define an algorithm for launching web app (PR #1056) (Thursday, 3 November)
Re: [w3c/manifest] Define an algorithm for launching web app (PR #1056) (Wednesday, 2 November)
Re: [w3c/manifest] Define an algorithm for launching web app (PR #1056) (Wednesday, 2 November)
Re: [w3c/manifest] Define an algorithm for launching web app (PR #1056) (Wednesday, 2 November)
Re: [w3c/manifest] Define an algorithm for launching web app (PR #1056) (Wednesday, 2 November)
[w3c/manifest] ReSpec errors for navigate and origin references (Issue #1061) (Wednesday, 2 November)

Alex Kempton

[w3c/uievents] Wheel event: determine difference between trackpad and mouse events (Issue #337) (Wednesday, 30 November)

Alex Keng

Re: [w3ctag/design-reviews] EditContext API (#416) (Wednesday, 30 November)

Amy Guy

Re: [w3ctag/design-reviews] Cookies Having Independent Partitioned State (CHIPS) specification review (Issue #779) (Tuesday, 29 November)
Re: [w3ctag/design-reviews] Cookies Having Independent Partitioned State (CHIPS) specification review (Issue #779) (Tuesday, 15 November)

Andreu Botella

Re: [whatwg/url] Editorial: adopt Infra for URLSearchParams (PR #717) (Tuesday, 22 November)

Anne van Kesteren

Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Wednesday, 30 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 30 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Wednesday, 30 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Wednesday, 30 November)
Re: [whatwg/storage] Export storage model definitions (Issue #153) (Wednesday, 30 November)
Re: [whatwg/url] javascript: URL parsing (#307) (Wednesday, 30 November)
Re: [w3c/permissions] "permission query algorithm" run on string (Issue #395) (Wednesday, 30 November)
Re: [w3c/permissions] Task queueing (Issue #393) (Wednesday, 30 November)
Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Wednesday, 30 November)
Re: [w3c/permissions] Task queueing (Issue #393) (Wednesday, 30 November)
Re: [w3c/permissions] Consider removing "lifetime" (Issue #391) (Tuesday, 29 November)
Re: [w3c/permissions] Align internal states with enums (Issue #392) (Tuesday, 29 November)
Re: [w3c/permissions] Consider removing "lifetime" (Issue #391) (Tuesday, 29 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 28 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 28 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 28 November)
Re: [whatwg/fetch] Specify exception to redirect-tainting: Upgrade-Insecure-Requests (UIR) and HSTS scheme upgrades (Issue #1551) (Monday, 28 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 28 November)
Re: [whatwg/fetch] Specify exception to redirect-tainting: Upgrade-Insecure-Requests (UIR) and HSTS scheme upgrades (Issue #1551) (Monday, 28 November)
Re: [whatwg/fetch] Editorial: add algorithm wrapper to header algorithms (PR #1549) (Monday, 28 November)
Re: [whatwg/dom] Add the ability for an EventTarget to provide an algorithm to override (#366) (Monday, 28 November)
Re: [whatwg/dom] Add the ability for an EventTarget to provide an algorithm to override (#366) (Monday, 28 November)
Re: [whatwg/dom] Patch HTML's base URL stuff to be in terms of DOM (#61) (Monday, 28 November)
Re: [w3c/FileAPI] Editorial: slice blob should use nullable args (PR #184) (Monday, 28 November)
Re: [w3c/FileAPI] Editorial: slice blob should use nullable args (PR #184) (Monday, 28 November)
Re: [whatwg/fetch] Editorial: rely more on Infra in the data: URL processor (PR #1548) (Friday, 25 November)
Re: [whatwg/fetch] Editorial: rely more on Infra in the data: URL processor (PR #1548) (Friday, 25 November)
Re: [whatwg/fetch] Editorial: add algorithm wrapper to header algorithms (PR #1549) (Friday, 25 November)
Re: [whatwg/fetch] Share logic of Headers append/delete/set (Issue #1543) (Friday, 25 November)
Re: [whatwg/fetch] Editorial: share validation logic in the Headers class (PR #1545) (Friday, 25 November)
Re: [whatwg/fullscreen] Allow fullscreen on already fullscreen elements without user activation (#193) (Friday, 25 November)
Re: [whatwg/url] Editorial: clarify the types of strings algorithms take and return (PR #719) (Friday, 25 November)
Re: [whatwg/fetch] Does Server-Timing work when not exposed through Access-Control-Expose-Headers? (Issue #1511) (Friday, 25 November)
Re: [whatwg/url] Editorial: clarify the types of strings algorithms take and return (PR #719) (Friday, 25 November)
[whatwg/url] Editorial: clarify the types of strings algorithms take and return (PR #719) (Friday, 25 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Friday, 25 November)
Re: [whatwg/fetch] Editorial: add algorithm wrapper to header algorithms (PR #1549) (Friday, 25 November)
Re: [whatwg/xhr] Align with Fetch's forbidden request-header refactor (PR #362) (Friday, 25 November)
Re: [whatwg/fetch] Drop developer-controlled Authorization header on cross-origin redirects (#944) (Friday, 25 November)
Re: [whatwg/fetch] Remove Authorization header upon cross-origin redirect (PR #1544) (Friday, 25 November)
Re: [whatwg/fetch] Remove Authorization header upon cross-origin redirect (PR #1544) (Friday, 25 November)
Re: [w3c/permissions] Consider removing "lifetime" (Issue #391) (Friday, 25 November)
Re: [w3c/permissions] Remove use of realms (PR #397) (Friday, 25 November)
Re: [w3c/permissions] Integrate "request permission to use" with user activation (PR #401) (Friday, 25 November)
Re: [w3c/permissions] Integrate "request permission to use" with user activation (PR #401) (Friday, 25 November)
Re: [whatwg/fullscreen] Allow fullscreen on already fullscreen elements without user activation (#193) (Friday, 25 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 25 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 25 November)
Re: [whatwg/xhr] Align with Fetch's forbidden request-header refactor (PR #362) (Friday, 25 November)
Re: [whatwg/dom] Broken references in DOM Standard (Issue #1130) (Thursday, 24 November)
Re: [whatwg/dom] Meta: correct createContextualFragment() link (PR #1131) (Thursday, 24 November)
Re: [whatwg/dom] Meta: correct createContextualFragment() link (PR #1131) (Thursday, 24 November)
Re: [whatwg/xhr] Wrong upload progress when network interrupts (Issue #361) (Thursday, 24 November)
Re: [whatwg/fullscreen] Use inset property in the UA style sheet (PR #210) (Thursday, 24 November)
Re: [whatwg/fullscreen] Use inset property in the UA style sheet (PR #210) (Thursday, 24 November)
Re: [whatwg/webidl] Add discussion of unexposed interfaces? (Issue #1236) (Thursday, 24 November)
Re: [whatwg/fullscreen] Use inset property in the UA style sheet (PR #210) (Thursday, 24 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Thursday, 24 November)
[w3c/permissions] PermissionDescriptor equality is not defined (Issue #396) (Thursday, 24 November)
[w3c/permissions] "permission query algorithm" run on string (Issue #395) (Thursday, 24 November)
[w3c/permissions] "permission query algorithm" is passed a redundant argument (Issue #394) (Thursday, 24 November)
[w3c/permissions] Task queueing (Issue #393) (Thursday, 24 November)
[w3c/permissions] Align internal states with enums (Issue #392) (Thursday, 24 November)
Re: [w3c/permissions] Consider removing "lifetime" (Issue #391) (Thursday, 24 November)
[w3c/permissions] Consider removing "lifetime" (Issue #391) (Thursday, 24 November)
Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Thursday, 24 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Thursday, 24 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Thursday, 24 November)
Re: [whatwg/fetch] Editorial: rely more on Infra in the data: URL processor (PR #1548) (Thursday, 24 November)
[whatwg/fetch] Editorial: rely more on Infra in the data: URL processor (PR #1548) (Thursday, 24 November)
Re: [whatwg/webidl] Add discussion of unexposed interfaces? (Issue #1236) (Thursday, 24 November)
Re: [whatwg/fetch] Editorial: minor nits, mainly around headers (PR #1546) (Thursday, 24 November)
Re: [whatwg/fetch] Parse a MIME type expects a string (PR #1547) (Thursday, 24 November)
[whatwg/fetch] Parse a MIME type expects a string (PR #1547) (Wednesday, 23 November)
[whatwg/fetch] Editorial: minor nits, mainly around headers (PR #1546) (Wednesday, 23 November)
[whatwg/fetch] Editorial: share validation logic in the Headers class (PR #1545) (Wednesday, 23 November)
Re: [whatwg/fetch] Refactor forbidden request-headers (PR #1541) (Wednesday, 23 November)
Re: [whatwg/fetch] Refactor forbidden request-headers (PR #1541) (Wednesday, 23 November)
Re: [whatwg/fetch] Refactor forbidden request-headers (PR #1541) (Wednesday, 23 November)
Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Wednesday, 23 November)
Re: [whatwg/url] Editorial: adopt Infra for URLSearchParams (PR #717) (Wednesday, 23 November)
Re: [whatwg/url] Editorial: address a couple minor nits (PR #718) (Wednesday, 23 November)
Re: [whatwg/url] Editorial: adopt Infra for URLSearchParams (PR #717) (Wednesday, 23 November)
Re: [whatwg/url] Editorial: address a couple minor nits (PR #718) (Wednesday, 23 November)
Re: [whatwg/url] Editorial: address a couple minor nits (PR #718) (Wednesday, 23 November)
[whatwg/url] Editorial: address a couple minor nits (PR #718) (Tuesday, 22 November)
[whatwg/url] Editorial: adopt Infra for URLSearchParams (PR #717) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [w3c/permissions] Allow returning "prompt" rather than "denied" (Issue #388) (Tuesday, 22 November)
Re: [whatwg/webidl] Editorial: align code point formatting with Infra (PR #1235) (Tuesday, 22 November)
[whatwg/webidl] Editorial: align code point formatting with Infra (PR #1235) (Tuesday, 22 November)
Re: [whatwg/webidl] Use the term scalar value from Infra (PR #1234) (Tuesday, 22 November)
Re: [whatwg/webidl] “Unicode character” should likely say “Unicode scalar value” in intro to lexical grammar (Issue #1080) (Tuesday, 22 November)
Re: [whatwg/webidl] Use the term scalar value from Infra (PR #1234) (Tuesday, 22 November)
Re: [w3c/permissions] Allow returning "prompt" rather than "denied" (Issue #388) (Tuesday, 22 November)
[whatwg/dom] Meta: correct createContextualFragment() link (PR #1131) (Tuesday, 22 November)
Re: [whatwg/dom] Broken references in DOM Standard (Issue #1130) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [w3c/screen-orientation] Editorial: relocate page visibility change step to HTML (PR #240) (Tuesday, 22 November)
Re: [whatwg/fetch] Editorial: use tuple syntax (PR #1542) (Tuesday, 22 November)
Re: [whatwg/fetch] Refactor forbidden request-headers (PR #1541) (Monday, 21 November)
Re: [whatwg/fetch] Remove Authorization header upon cross-origin redirect (PR #1544) (Monday, 21 November)
[whatwg/fetch] Remove Authorization header upon cross-origin redirect (PR #1544) (Monday, 21 November)
Re: [whatwg/webidl] 'this' and nested steps (Issue #1175) (Monday, 21 November)
[whatwg/fetch] Share logic of Headers append/delete/set (Issue #1543) (Monday, 21 November)
Re: [whatwg/storage] Add a diagram for the storage model? (Issue #151) (Monday, 21 November)
Re: [whatwg/storage] Add a diagram for the storage model? (Issue #151) (Monday, 21 November)
[whatwg/fetch] Editorial: use tuple syntax (PR #1542) (Monday, 21 November)
[whatwg/xhr] Align with Fetch's forbidden request-header refactor (PR #362) (Monday, 21 November)
Re: [whatwg/fetch] Refactor forbidden request-headers (PR #1541) (Monday, 21 November)
Re: [whatwg/fetch] Refactor forbidden request-headers (PR #1541) (Monday, 21 November)
[whatwg/fetch] Refactor forbidden request-headers (PR #1541) (Monday, 21 November)
Re: [whatwg/xhr] Wrong upload progress when network interrupts (Issue #361) (Monday, 21 November)
Re: [whatwg/storage] Add a diagram for the storage model? (Issue #151) (Monday, 21 November)
Re: [WICG/webcomponents] Custom pseudo-classes for host elements via shadow roots (:state) (#738) (Friday, 18 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Tuesday, 15 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. #1536 (PR #1536) (Tuesday, 15 November)
Re: [w3c/screen-orientation] Feature detection of orientation.lock (Issue #206) (Tuesday, 15 November)
Re: [whatwg/webidl] Fix getter name for maplike/setlike size (PR #1232) (Tuesday, 15 November)
Re: [whatwg/webidl] Fix getter name for maplike/setlike size (PR #1232) (Tuesday, 15 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. #1536 (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. #1536 (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Monday, 14 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Remove slash in ACAO example value (PR #1537) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204) (Monday, 14 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Monday, 14 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
Re: [whatwg/webidl] Add OptOutError to the error names list (PR #1231) (Monday, 14 November)
Re: [whatwg/dom] Add pop-up light dismiss logic to event dispatching (PR #1117) (Friday, 11 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Friday, 11 November)
Re: [whatwg/dom] Add pop-up light dismiss logic to event dispatching (PR #1117) (Friday, 11 November)
Re: [w3c/FileAPI] editorial: make Blob.slice a separate algorithm (PR #183) (Friday, 11 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Thursday, 10 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Thursday, 10 November)
Re: [whatwg/url] Proposal: allow none network related urls (Issue #715) (Wednesday, 9 November)
Re: [whatwg/url] Proposal: allow none network related urls (Issue #715) (Wednesday, 9 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Wednesday, 9 November)
Re: [whatwg/fetch] Proposal: None network related Url Specifier Handling (Issue #1535) (Wednesday, 9 November)
Re: [whatwg/fetch] Proposal: None network related Url Specifier Handling (Issue #1535) (Wednesday, 9 November)
Re: [whatwg/fetch] I found a interristing issue that maybe needs our attention. (Issue #1535) (Wednesday, 9 November)
Re: [whatwg/dom] Contradicting text regarding Document.ownerDocument? (Issue #1126) (Tuesday, 8 November)
Re: [whatwg/fetch] Editorial: Remove a duplicate "in" (PR #1529) (Tuesday, 8 November)
Re: [whatwg/dom] Contradicting text regarding Document.ownerDocument? (Issue #1126) (Monday, 7 November)
Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Monday, 7 November)
Re: [whatwg/url] Consider adding non-throwing URL.parse(input, base) (#372) (Monday, 7 November)
Re: [whatwg/url] Consider adding non-throwing URL.parse(input, base) (#372) (Monday, 7 November)
Re: [whatwg/storage] storage key origin can be changed by document.domain (Issue #150) (Saturday, 5 November)
Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Saturday, 5 November)
Re: [whatwg/fetch] Editorial: Remove a duplicate "in" (PR #1529) (Thursday, 3 November)
Re: [whatwg/fetch] Editorial: Remove a duplicate "in" (PR #1528) (Thursday, 3 November)
Re: [whatwg/fetch] Editorial: Remove a duplicate "in" (PR #1528) (Thursday, 3 November)
Re: [whatwg/fetch] Add `<div algorithm>` wrappers around algorithms (Issue #1526) (Thursday, 3 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Thursday, 3 November)
Re: [whatwg/fetch] Support Structured Field Values in the Headers API (#930) (Thursday, 3 November)
Re: [whatwg/url] Introduce a variant of url.searchParams that operates according to URL rules instead of <form> rules (#491) (Thursday, 3 November)
Re: [whatwg/webidl] New error name: OptOutError (Issue #1168) (Wednesday, 2 November)
Re: [whatwg/storage] Swap browsing session for traversable (PR #148) (Wednesday, 2 November)
Re: [whatwg/storage] Swap browsing session for traversable (PR #148) (Wednesday, 2 November)
Re: [whatwg/storage] Swap browsing session for traversable (PR #148) (Wednesday, 2 November)
Re: [whatwg/fetch] Update to use navigables instead of browsing contexts (PR #1525) (Wednesday, 2 November)
Re: [whatwg/fetch] Update to use navigables instead of browsing contexts (PR #1525) (Wednesday, 2 November)
Re: [whatwg/fetch] Option to fetch raw byte as is. (without decompressing) (Issue #1524) (Wednesday, 2 November)
Re: [whatwg/fetch] Option to fetch raw byte as is. (without decompressing) (Issue #1524) (Tuesday, 1 November)
Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Tuesday, 1 November)
Re: [whatwg/fullscreen] Meta: my employer changed (PR #205) (Tuesday, 1 November)

Anssi Kostiainen

Re: [w3ctag/design-reviews] Delta review (to CR) of Web Neural Network API (Issue #771) (Wednesday, 30 November)

Aphek

[w3c/uievents] New `contextmenu` event definition missing bypass (Issue #336) (Thursday, 24 November)

Ari Chivukula

Re: [w3ctag/design-reviews] Wildcards in Permissions Policy Origins (Issue #765) (Tuesday, 29 November)

Arthur Hemery

Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Thursday, 17 November)

ArthurSonzogni

Re: [w3ctag/design-reviews] COEP reflection (Issue #742) (Monday, 14 November)
Re: [w3ctag/design-reviews] COEP reflection (Issue #742) (Monday, 14 November)

Asher Gomez

Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { min }) (#1145) (Tuesday, 8 November)

BamaBeauty86

[whatwg/webidl] Messaging (Issue #1238) (Tuesday, 29 November)

Ben Kelly

Re: [whatwg/storage] storage key origin can be changed by document.domain (Issue #150) (Monday, 7 November)
Re: [whatwg/storage] storage key origin can be changed by document.domain (Issue #150) (Monday, 7 November)
[whatwg/storage] storage key origin can be changed by document.domain (Issue #150) (Friday, 4 November)
Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Tuesday, 1 November)

Brian E Carpenter

Re: [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Thursday, 24 November)
Re: [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Wednesday, 9 November)
Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Monday, 7 November)
Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Monday, 7 November)
Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Sunday, 6 November)
Re: [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Sunday, 6 November)
Re: [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Friday, 4 November)
Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Wednesday, 2 November)
Re: [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Tuesday, 1 November)
Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Tuesday, 1 November)
Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Tuesday, 1 November)

bvandersloot-mozilla

Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Wednesday, 30 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Wednesday, 30 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Wednesday, 30 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Wednesday, 30 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Tuesday, 22 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Tuesday, 22 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Tuesday, 22 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Tuesday, 22 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Tuesday, 22 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Monday, 14 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Monday, 14 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Monday, 14 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Friday, 11 November)
[whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Monday, 7 November)

Caridy Patiño

Re: [WICG/webcomponents] We need the ability to deregister or undefine custom elements. (Issue #970) (Friday, 18 November)
Re: [WICG/webcomponents] Can ElementInternals have ARIA properties pointing inside the shadow root? (Issue #974) (Friday, 18 November)
Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Friday, 4 November)

Carlos Lopez

Re: [WICG/webcomponents] HTML Modules (#645) (Thursday, 10 November)

Chris Harrelson

Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743) (Friday, 18 November)
Re: [w3ctag/design-reviews] The Popup API (Issue #743) (Thursday, 17 November)

Christian Bewernitz

Re: [whatwg/dom] Contradicting text regarding Document.ownerDocument? (Issue #1126) (Tuesday, 8 November)
Re: [whatwg/dom] Contradicting text regarding Document.ownerDocument? (Issue #1126) (Tuesday, 8 November)
Re: [whatwg/dom] Contradicting text regarding Document.ownerDocument? (Issue #1126) (Monday, 7 November)
[whatwg/dom] Contradicting text regarding Document.ownerDocument (Issue #1126) (Sunday, 6 November)

Christian Liebel

Re: [w3c/manifest] Ability to override the back button behavior (Issue #1064) (Wednesday, 30 November)
Re: [w3c/manifest] Transparent Bottom Navigation Bar (#804) (Wednesday, 30 November)
[w3c/manifest] Ability to override the back button behavior (Issue #1064) (Wednesday, 30 November)

Cladis

[w3c/selection-api] fixing typo Secruity -> Security (PR #160) (Saturday, 19 November)

Code Hangen

Re: [WICG/webcomponents] A simple conceptual way to create web components with js (Issue #973) (Thursday, 3 November)
Re: [WICG/webcomponents] without .html in link rel="import" and href in web component (Issue #971) (Thursday, 3 November)
Re: [WICG/webcomponents] without .html in link rel="import" and href in web component (Issue #971) (Wednesday, 2 November)
Re: [WICG/webcomponents] without .html in link rel="import" and href in web component (Issue #971) (Tuesday, 1 November)
Re: [WICG/webcomponents] without .html in link rel="import" and href in web component (Issue #971) (Tuesday, 1 November)

cynthia

Re: [w3ctag/design-reviews] Delta review (to CR) of Web Neural Network API (Issue #771) (Wednesday, 30 November)
Re: [w3ctag/design-reviews] Delta review (to CR) of Web Neural Network API (Issue #771) (Wednesday, 30 November)

DAIDAOXING

[whatwg/fetch] DAI GLOBAL SA (Issue #1539) (Friday, 18 November)

Dan Dumont

Re: [w3ctag/design-reviews] Sync Methods for FileSystemSyncAccessHandle in File System Access API (Issue #772) (Wednesday, 30 November)

Dan Robertson

Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Tuesday, 29 November)
Re: [w3c/FileAPI] Editorial: slice blob should use nullable args (PR #184) (Monday, 28 November)
Re: [w3c/FileAPI] Editorial: slice blob should use nullable args (PR #184) (Monday, 28 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Sunday, 27 November)
[whatwg/fetch] Create Rage header section in HTTP extensions section (Issue #1553) (Sunday, 27 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Sunday, 27 November)
[whatwg/fetch] Move Content-Range header builder to separate algorithm (Issue #1552) (Sunday, 27 November)
Re: [w3c/FileAPI] Editorial: slice blob should use nullable args (PR #184) (Saturday, 26 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Saturday, 26 November)
[w3c/FileAPI] Editorial: slice blob should use nullable args (PR #184) (Saturday, 26 November)
Re: [whatwg/fetch] Editorial: add algorithm wrapper to header algorithms (PR #1549) (Friday, 25 November)
[whatwg/fetch] Editorial: add algorithm wrapper to header algorithms (PR #1549) (Thursday, 24 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Thursday, 24 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Wednesday, 23 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Wednesday, 23 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Wednesday, 23 November)
Re: [w3c/FileAPI] editorial: make Blob.slice a separate algorithm (PR #183) (Sunday, 13 November)
Re: [w3c/FileAPI] editorial: make Blob.slice a separate algorithm (PR #183) (Sunday, 13 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Thursday, 10 November)
Re: [w3c/FileAPI] editorial: make Blob.slice a separate algorithm (PR #183) (Thursday, 10 November)
Re: [w3c/FileAPI] editorial: make Blob.slice a separate algorithm (PR #183) (Thursday, 10 November)
[w3c/FileAPI] editorial: make Blob.slice a separate algorithm (PR #183) (Thursday, 10 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Friday, 4 November)
Re: [whatwg/fetch] Add support for blob range requests (PR #1520) (Friday, 4 November)

Daniel Appelquist

Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Tuesday, 29 November)
Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721) (Monday, 28 November)
Re: [w3ctag/design-reviews] Multi-Screen Window Placement on the Web - Initiating Multi-Screen Experiences (Issue #767) (Monday, 28 November)
Re: [w3ctag/design-reviews] Early design review of the **updated** Multi-Screen Window Placement API (#602) (Monday, 28 November)
Re: [w3ctag/design-reviews] Early design review of the **updated** Multi-Screen Window Placement API (#602) (Monday, 28 November)
Re: [w3ctag/design-reviews] EditContext API (#416) (Monday, 28 November)
Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743) (Friday, 18 November)
Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Tuesday, 15 November)
Re: [w3ctag/design-reviews] FYI review of Writable directory prompts for the File System Access API (Issue #749) (Tuesday, 15 November)
Re: [w3ctag/design-reviews] FYI review of Writable directory prompts for the File System Access API (Issue #749) (Tuesday, 15 November)
Re: [w3ctag/design-reviews] The Popup API (Issue #743) (Monday, 14 November)
Re: [w3ctag/design-reviews] COEP reflection (Issue #742) (Monday, 14 November)
Re: [w3ctag/design-reviews] Early design review: CSS Toggles (Issue #730) (Monday, 14 November)
Re: [w3ctag/design-reviews] Early design review: CSS Toggles (Issue #730) (Monday, 14 November)
Re: [w3ctag/design-reviews] Cookies Having Independent Partitioned State (CHIPS) specification review (Issue #779) (Tuesday, 1 November)
Re: [w3ctag/design-reviews] Cookies Having Independent Partitioned State (CHIPS) specification review (Issue #779) (Tuesday, 1 November)

Daniel Murphy

Re: [w3c/manifest] `id` member reuse in MiniApps Manifest (no `document URL`) (Issue #1048) (Tuesday, 29 November)

Darien Maillet Valentine

Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902) (Wednesday, 30 November)
Re: [whatwg/webidl] Add discussion of unexposed interfaces? (Issue #1236) (Thursday, 24 November)
Re: [whatwg/webidl] Add discussion of unexposed interfaces? (Issue #1236) (Wednesday, 23 November)

Demi Marie Obenour

Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Monday, 7 November)
Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Monday, 7 November)
Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Monday, 7 November)
Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Tuesday, 1 November)
Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Tuesday, 1 November)

DENG, XIAOFU

[w3c/ServiceWorker] How to get correct connectStart/End values of a proxied http request inside service worker? (Issue #1663) (Friday, 25 November)

Domenic Denicola

Re: [w3c/permissions] Task queueing (Issue #393) (Wednesday, 30 November)
Re: [w3c/permissions] Task queueing (Issue #393) (Wednesday, 30 November)
Re: [whatwg/fetch] Editorial: share validation logic in the Headers class (PR #1545) (Friday, 25 November)
Re: [whatwg/fetch] Editorial: rely more on Infra in the data: URL processor (PR #1548) (Friday, 25 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/streams] Examine interaction of resizable array buffers with Streams (Issue #1248) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/url] Editorial: address a couple minor nits (PR #718) (Wednesday, 23 November)
Re: [whatwg/webidl] Allow DOMException subclasses to be used as exceptions (PR #1211) (Wednesday, 23 November)
Re: [whatwg/webidl] Allow DOMException subclasses to be used as exceptions (PR #1211) (Wednesday, 23 November)
Re: [whatwg/webidl] Allow DOMException subclasses to be used as exceptions (PR #1211) (Wednesday, 23 November)
Re: [whatwg/streams] Examine interaction of resizable array buffers with Streams (Issue #1248) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [whatwg/fetch] Editorial: use tuple syntax (PR #1542) (Tuesday, 22 November)
Re: [whatwg/webidl] Add OptOutError to the error names list (PR #1231) (Wednesday, 16 November)
Re: [whatwg/webidl] New error name: OptOutError (Issue #1168) (Wednesday, 16 November)
Re: [whatwg/webidl] Add OptOutError to the error names list (PR #1231) (Wednesday, 16 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Wednesday, 16 November)
[whatwg/webidl] Fix getter name for maplike/setlike size (PR #1232) (Tuesday, 15 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Monday, 14 November)
Re: [whatwg/webidl] Add OptOutError to the error names list (PR #1231) (Monday, 14 November)
Re: [whatwg/dom] Add pop-up light dismiss logic to event dispatching (PR #1117) (Friday, 11 November)
Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Tuesday, 8 November)
Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Monday, 7 November)
Re: [whatwg/dom] Nu HTML checker latest version updated, Running Nu HTML checker error on build result (Issue #1125) (Friday, 4 November)
Re: [whatwg/dom] Nu HTML checker latest version updated, Running Nu HTML checker error on build result (Issue #1125) (Friday, 4 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Thursday, 3 November)
[whatwg/fetch] Update to use navigables instead of browsing contexts (PR #1525) (Wednesday, 2 November)
Re: [whatwg/fullscreen] Update to use navigables instead of browsing contexts (PR #208) (Wednesday, 2 November)
Re: [whatwg/fullscreen] Meta: my employer changed (PR #205) (Tuesday, 1 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Tuesday, 1 November)
[whatwg/fullscreen] Update to use navigables instead of browsing contexts (PR #208) (Tuesday, 1 November)
Re: [whatwg/webidl] What's the idiomatic way to reject a promise with structured data? (Issue #1223) (Tuesday, 1 November)
Re: [whatwg/webidl] What's the idiomatic way to reject a promise with structured data? (Issue #1223) (Tuesday, 1 November)

Dominic Farolino

Re: [whatwg/dom] Patch HTML's base URL stuff to be in terms of DOM (#61) (Sunday, 27 November)
Re: [whatwg/dom] Add the ability for an EventTarget to provide an algorithm to override (#366) (Sunday, 27 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Wednesday, 23 November)

Dominique Martinet

Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Monday, 7 November)

dontcallmedom-bot

[w3c/DOM-Parsing] Broken references in DOM Parsing and Serialization (Issue #74) (Monday, 21 November)
[whatwg/dom] Broken references in DOM Standard (Issue #1130) (Monday, 21 November)

Dylan Cutler

Re: [w3ctag/design-reviews] Cookies Having Independent Partitioned State (CHIPS) specification review (Issue #779) (Monday, 21 November)

Edgar Chen

Re: [whatwg/webidl] Add discussion of unexposed interfaces? (Issue #1236) (Thursday, 24 November)
Re: [whatwg/webidl] Editorial: align code point formatting with Infra (PR #1235) (Tuesday, 22 November)
Re: [whatwg/fullscreen] Consume user gestures in requestFullscreen (#152) (Tuesday, 8 November)
Re: [whatwg/fullscreen] Consume user gestures in requestFullscreen (#152) (Tuesday, 8 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Thursday, 3 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Wednesday, 2 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Wednesday, 2 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Tuesday, 1 November)

Emilio Cobos Álvarez

Re: [whatwg/fullscreen] Use inset property in the UA style sheet (PR #210) (Thursday, 24 November)
Re: [whatwg/fullscreen] Use inset property in the UA style sheet (PR #210) (Thursday, 24 November)
Re: [whatwg/fullscreen] Use inset property in the UA style sheet (PR #210) (Thursday, 24 November)

Eric Willigers

Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039) (Wednesday, 16 November)

Erik Kline

Re: [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Tuesday, 1 November)

Ethan Arrowood

Re: [whatwg/fetch] Initial modifications to whatwg/fetch fork (PR #1534) (Tuesday, 8 November)
Re: [whatwg/fetch] Initial modifications to whatwg/fetch fork (PR #1534) (Tuesday, 8 November)
[whatwg/fetch] Initial modifications to whatwg/fetch fork (PR #1534) (Tuesday, 8 November)

favonia

Re: [whatwg/url] Unicode normalization could change the structure of a URL (#626) (Sunday, 27 November)
Re: [whatwg/url] Unicode normalization could change the structure of a URL (#626) (Sunday, 27 November)

Fbird6006n

[whatwg/fetch] The guy thats been stalking me (hacking into everything i own) wrote this. I just wish i could get some help tracking this stalker down... (Issue #1530) (Saturday, 5 November)

fergald

[w3ctag/design-reviews] early design review: bfcache/prerendering eviction APIs (Issue #786) (Friday, 18 November)

Frank Lemanschik

[whatwg/url] Proposal: allow none network related urls (Issue #715) (Wednesday, 9 November)
Re: [whatwg/fetch] Proposal: None network related Url Specifier Handling (Issue #1535) (Wednesday, 9 November)
Re: [whatwg/fetch] Proposal: consider url parsing to be more flexible about colons in the protocol part of a url (Issue #1535) (Wednesday, 9 November)
Re: [whatwg/fetch] Proposal: consider url parsing to be more flexible about colons in the protocol part of a url (Issue #1535) (Wednesday, 9 November)
Re: [whatwg/fetch] Proposal: consider url parsing to be more flexible about colons in the protocol part of a url (Issue #1535) (Wednesday, 9 November)
Re: [whatwg/fetch] Proposal: consider url parsing to be more flexible about colons in the protocol part of a url (Issue #1535) (Wednesday, 9 November)
Re: [whatwg/fetch] Proposal: consider url parsing to be more flexible about colons in the protocol part of a url (Issue #1535) (Wednesday, 9 November)
[whatwg/fetch] I found a interristing issue that maybe needs our attention. (Issue #1535) (Wednesday, 9 November)

Fuqiao Xue

Re: [w3ctag/design-reviews] MiniApp Packaging (Issue #762) (Monday, 28 November)

Gary Kacmarcik

Re: [w3c/uievents-code] Tasks for wide review (Issue #35) (Wednesday, 2 November)
Re: [w3c/uievents-code] Tasks for wide review (Issue #35) (Wednesday, 2 November)
Re: [w3c/uievents-code] Tasks for wide review (Issue #35) (Wednesday, 2 November)
Re: [w3c/uievents-code] Tasks for wide review (Issue #35) (Wednesday, 2 November)
Re: [w3c/uievents-key] Tasks for wide review (Issue #57) (Wednesday, 2 November)
Re: [w3c/uievents-key] Tasks for wide review (Issue #57) (Wednesday, 2 November)
Re: [w3c/uievents-key] Tasks for wide review (Issue #57) (Wednesday, 2 November)
Re: [w3c/uievents-key] Tasks for wide review (Issue #57) (Wednesday, 2 November)

hemanth.hm

Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Saturday, 5 November)
Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Friday, 4 November)

Henri Sivonen

[whatwg/webidl] Use the term scalar value from Infra (PR #1234) (Monday, 21 November)
Re: [w3c/editing] JS API to invoke native desktop emoji picker (#350) (Tuesday, 8 November)

Ivan Artemiev

Re: [w3c/IndexedDB] Clarify expected index key generation behavior when extracting a key from a value using a key path list (Issue #394) (Saturday, 5 November)
Re: [w3c/IndexedDB] Clarify expected index key generation behavior when extracting a key from a value using a key path list (Issue #394) (Thursday, 3 November)
Re: [w3c/IndexedDB] Clarify expected index key generation behavior when extracting a key from a value using a key path list (Issue #394) (Thursday, 3 November)
Re: [w3c/IndexedDB] Clarify expected index key generation behavior when extracting a key from a value using a key path list (Issue #394) (Thursday, 3 November)
Re: [w3c/IndexedDB] Clarify expected index key generation behavior when extracting a key from a value using a key path list (Issue #394) (Thursday, 3 November)
[w3c/IndexedDB] Clarify expected index key generation behavior when extracting a key from a value using a key path list (Issue #394) (Thursday, 3 November)

Jacob Smith

[w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662) (Tuesday, 15 November)

Jake Archibald

Re: [w3c/ServiceWorker] Increment encoded/decoded body size for constructed responses (PR #1664) (Monday, 28 November)
Re: [w3c/ServiceWorker] Increment encoded/decoded body size for constructed responses (PR #1664) (Monday, 28 November)
Re: [whatwg/webidl] 'this' and nested steps (Issue #1175) (Monday, 21 November)
Re: [w3ctag/design-reviews] View Transitions API (Issue #748) (Thursday, 17 November)
Re: [w3c/ServiceWorker] Abort with fetch controller's error in Handle Fetch (PR #1655) (Monday, 14 November)
Re: [w3c/ServiceWorker] Abort with fetch controller's error in Handle Fetch (PR #1655) (Monday, 14 November)
Re: [whatwg/fetch] Add `<div algorithm>` wrappers around algorithms (Issue #1526) (Thursday, 3 November)
Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Tuesday, 1 November)

James Bromwell

Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Wednesday, 23 November)

James M Snell

Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Tuesday, 8 November)
Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Saturday, 5 November)

jded76

Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819) (Saturday, 5 November)

Jeffrey Yasskin

Re: [w3c/permissions] "permission query algorithm" run on string (Issue #395) (Wednesday, 30 November)
Re: [w3c/permissions] Task queueing (Issue #393) (Wednesday, 30 November)
Re: [w3c/permissions] "permission query algorithm" is passed a redundant argument (Issue #394) (Wednesday, 30 November)
Re: [w3c/permissions] "permission query algorithm" run on string (Issue #395) (Wednesday, 30 November)
Re: [w3c/permissions] PermissionDescriptor equality is not defined (Issue #396) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Tuesday, 29 November)
Re: [w3c/permissions] Remove use of realms (PR #397) (Monday, 28 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Monday, 28 November)
Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533) (Thursday, 17 November)

Jesús Leganés-Combarro

Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Tuesday, 1 November)

jgraham

[whatwg/fetch] Add WebDriver BiDi network request logging (PR #1540) (Friday, 18 November)
[whatwg/fetch] Add `<div algorithm>` wrappers around algorithms (Issue #1526) (Thursday, 3 November)

Jimmy Wärting

Re: [whatwg/fetch] Option to fetch raw byte as is. (without decompressing) (Issue #1524) (Tuesday, 1 November)
[whatwg/fetch] Option to fetch raw byte as is. (without decompressing) (Issue #1524) (Tuesday, 1 November)
Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Tuesday, 1 November)

Jochen Kühner

Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 29 November)

Joey Arhar

Re: [whatwg/dom] Add pop-up light dismiss logic to event dispatching (PR #1117) (Tuesday, 22 November)
Re: [whatwg/dom] Add pop-up light dismiss logic to event dispatching (PR #1117) (Tuesday, 22 November)
Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204) (Friday, 18 November)
Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204) (Friday, 11 November)
Re: [whatwg/dom] Add pop-up light dismiss logic to event dispatching (PR #1117) (Friday, 11 November)
Re: [whatwg/dom] Add pop-up light dismiss logic to event dispatching (PR #1117) (Wednesday, 2 November)

Johann Hofmann

Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Consider removing "lifetime" (Issue #391) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Tuesday, 29 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Tuesday, 29 November)
Re: [w3c/permissions] Consider removing "lifetime" (Issue #391) (Tuesday, 29 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Tuesday, 29 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Tuesday, 29 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Tuesday, 29 November)
Re: [w3c/permissions] Remove use of realms (PR #397) (Monday, 28 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Thursday, 24 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Wednesday, 23 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Wednesday, 23 November)
Re: [w3c/permissions] Allow returning "prompt" rather than "denied" (Issue #388) (Tuesday, 22 November)
Re: [w3c/permissions] Allow returning "prompt" rather than "denied" (Issue #388) (Tuesday, 22 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 18 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 18 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 18 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 18 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 18 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 18 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 18 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 18 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 18 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 18 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 18 November)
[w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 11 November)
Re: [w3ctag/design-reviews] Cookies Having Independent Partitioned State (CHIPS) specification review (Issue #779) (Friday, 4 November)

Johannes Wilm

[w3c/editing] Remove Nov 10th meeting (suspended) (PR #411) (Tuesday, 8 November)
Re: [w3c/editing] Extend the list of scheduled meetings in 2023 (PR #410) (Tuesday, 8 November)
Re: [w3c/editing] Extend the list of scheduled meetings in 2023 (PR #410) (Tuesday, 8 November)

John Gamble

Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Sunday, 20 November)
Re: [WICG/webcomponents] We need the ability to deregister or undefine custom elements. (Issue #970) (Friday, 18 November)

Jonathan Neal

Re: [w3c/uievents] Proposal: Way to determine if any modifier key is pressed (#151) (Tuesday, 8 November)
Re: [w3c/uievents] Proposal: Way to determine if any modifier key is pressed (#151) (Monday, 7 November)

Jordan Harband

Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Tuesday, 8 November)
Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Tuesday, 8 November)
Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Monday, 7 November)

Joshua Bell

Re: [whatwg/storage] Find a better approach to incorporate with other specs; remove export hacks (Issue #153) (Wednesday, 30 November)
Re: [whatwg/storage] Export storage model definitions (Issue #153) (Wednesday, 30 November)
Re: [whatwg/storage] Export storage model definitions (Issue #153) (Wednesday, 30 November)
Re: [w3c/IndexedDB] Clarify expected index key generation behavior when extracting a key from a value using a key path list (Issue #394) (Thursday, 3 November)
Re: [w3c/IndexedDB] Clarify expected index key generation behavior when extracting a key from a value using a key path list (Issue #394) (Thursday, 3 November)
Re: [w3c/IndexedDB] Clarify expected index key generation behavior when extracting a key from a value using a key path list (Issue #394) (Thursday, 3 November)
Re: [w3c/IndexedDB] Clarify expected index key generation behavior when extracting a key from a value using a key path list (Issue #394) (Thursday, 3 November)

JunLiangWang

Re: [whatwg/dom] Nu HTML checker latest version updated, Running Nu HTML checker error on build result (Issue #1125) (Friday, 4 November)
Re: [whatwg/dom] Nu HTML checker latest version updated, Running Nu HTML checker error on build result (Issue #1125) (Friday, 4 November)
[whatwg/dom] Nu HTML checker latest version updated, Running Nu HTML checker error on build result (Issue #1125) (Friday, 4 November)

Justin Fagnani

Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902) (Thursday, 24 November)

Kagami Sascha Rosylight

[whatwg/storage] Export storage model definitions (Issue #153) (Tuesday, 29 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Thursday, 24 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Wednesday, 23 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Tuesday, 22 November)
Re: [whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Monday, 21 November)
[whatwg/storage] Editorial: Add a diagram for storage model (PR #152) (Monday, 21 November)
Re: [whatwg/storage] Add a diagram for the storage model? (Issue #151) (Monday, 21 November)
Re: [whatwg/storage] Add a diagram for the storage model? (Issue #151) (Monday, 21 November)
Re: [whatwg/storage] Add a diagram for the storage model? (Issue #151) (Monday, 21 November)
[whatwg/storage] Add a diagram for the storage model? (Issue #151) (Saturday, 19 November)
Re: [w3c/editing] JS API to invoke native desktop emoji picker (#350) (Tuesday, 8 November)

Kai Ninomiya

Re: [whatwg/webidl] Allow DOMException subclasses to be used as exceptions (PR #1211) (Thursday, 24 November)
Re: [whatwg/webidl] Allow DOMException subclasses to be used as exceptions (PR #1211) (Wednesday, 23 November)

Karl

Re: [whatwg/url] Proposal: URL.isValid (Issue #713) (Tuesday, 8 November)
Re: [whatwg/url] Introduce a variant of url.searchParams that operates according to URL rules instead of <form> rules (#491) (Thursday, 3 November)
Re: [whatwg/url] Introduce a variant of url.searchParams that operates according to URL rules instead of <form> rules (#491) (Wednesday, 2 November)
Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Tuesday, 1 November)

Kenneth Rohde Christiansen

Re: [w3c/manifest] Ability to override the back button behavior (Issue #1064) (Wednesday, 30 November)
Re: [w3c/manifest] Ability to override the back button behavior (Issue #1064) (Wednesday, 30 November)
Re: [w3c/manifest] Ability to override the back button behavior (Issue #1064) (Wednesday, 30 November)

Kenta Sato

[whatwg/fetch] Accessibility/vogue (Issue #1538) (Tuesday, 15 November)

Khushal Sagar

Re: [w3ctag/design-reviews] View Transitions API (Issue #748) (Saturday, 19 November)
Re: [w3ctag/design-reviews] View Transitions API (Issue #748) (Wednesday, 16 November)

Lea Verou

Re: [w3ctag/design-reviews] UI Events Keyboard Events Key Values review request (Issue #789) (Tuesday, 29 November)
Re: [w3ctag/design-reviews] Design and specification review of CSS Container Queries Style Features (Issue #787) (Tuesday, 29 November)
Re: [w3ctag/design-reviews] View Transitions API (Issue #748) (Wednesday, 16 November)
Re: [w3ctag/design-reviews] Early design review for Range API improvements (Issue #725) (Monday, 14 November)
Re: [w3ctag/design-reviews] AbortSignal.timeout() (Issue #711) (Monday, 14 November)
Re: [w3c/editing] JS API to invoke native desktop emoji picker (#350) (Tuesday, 8 November)

Linus Groh

[whatwg/fetch] Editorial: Remove a duplicate "in" (PR #1529) (Thursday, 3 November)

Louise Brett

Re: [w3c/manifest] Web Manifest Overrides (Issue #1045) (Wednesday, 23 November)

Luca Casonato

Re: [whatwg/fetch] Remove Authorization header upon cross-origin redirect (PR #1544) (Monday, 21 November)

Lukasz Olejnik

Re: [w3ctag/design-reviews] Wildcards in Permissions Policy Origins (Issue #765) (Friday, 4 November)

Léonie Watson

Re: [w3ctag/design-reviews] UI Events Keyboard Events Key Values review request (Issue #789) (Wednesday, 30 November)
Re: [w3c/uievents-code] Tasks for wide review (Issue #35) (Tuesday, 29 November)
[w3ctag/design-reviews] UI Events Keyboard Events Code Values review request (Issue #790) (Tuesday, 29 November)
Re: [w3c/uievents-key] Tasks for wide review (Issue #57) (Tuesday, 29 November)
[w3ctag/design-reviews] UI Events Keyboard Events Key Values review request (Issue #789) (Tuesday, 29 November)
Re: [w3c/screen-orientation] Consume user activation (PR #218) (Tuesday, 29 November)
Re: [whatwg/storage] Add a diagram for the storage model? (Issue #151) (Monday, 21 November)

Makoto Kato

Re: [w3c/screen-orientation] Add can-lock-orientation media feature to detect if locking is possible (Issue #206) (Monday, 28 November)
Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Monday, 28 November)

mangelozzi

Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Saturday, 19 November)

Marcos Cáceres

Re: [w3c/clipboard-apis] Web Platform tests using "clipboard-read" (Issue #188) (Wednesday, 30 November)
Re: [whatwg/fullscreen] Fullscreen tests are manual? (Issue #211) (Wednesday, 30 November)
Re: [whatwg/fullscreen] Fullscreen tests are manual? (Issue #211) (Wednesday, 30 November)
Re: [whatwg/fullscreen] Fullscreen tests are manual? (Issue #211) (Tuesday, 29 November)
Re: [w3c/permissions] Potentially revisit oneRealm (Issue #387) (Tuesday, 29 November)
Re: [w3c/permissions] Remove use of realms (PR #397) (Tuesday, 29 November)
Re: [w3c/permissions] Remove use of realms (PR #397) (Tuesday, 29 November)
Re: [w3c/permissions] Remove use of realms (PR #397) (Monday, 28 November)
Re: [w3c/permissions] Remove use of realms (PR #397) (Monday, 28 November)
[whatwg/fullscreen] Fullscreen tests are manual? (Issue #211) (Monday, 28 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Monday, 28 November)
Re: [whatwg/fullscreen] Rely solely on transient activation for orientation events (PR #209) (Monday, 28 November)
Re: [whatwg/fullscreen] Rely solely on transient activation for orientation events (PR #209) (Monday, 28 November)
[w3c/clipboard-apis] Web Platform tests using "clipboard-read" (Issue #188) (Monday, 28 November)
Re: [w3c/screen-orientation] Allow unlock() to return a promise (PR #231) (Monday, 28 November)
Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Monday, 28 November)
Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Monday, 28 November)
Re: [w3c/screen-orientation] Consume user activation (PR #218) (Monday, 28 November)
Re: [w3c/screen-orientation] Consume user activation (PR #218) (Monday, 28 November)
Re: [w3c/screen-orientation] Feature detection of orientation.lock (Issue #206) (Monday, 28 November)
Re: [w3c/permissions] Consider removing "lifetime" (Issue #391) (Friday, 25 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 25 November)
Re: [w3c/permissions] Automation: "set permission" granularity (#348) (Friday, 25 November)
[w3c/permissions] Add additional automation error checks (PR #402) (Friday, 25 November)
Re: [w3c/permissions] Integrate "request permission to use" with user activation (PR #401) (Friday, 25 November)
Re: [w3c/permissions] Integrate "request permission to use" with user activation (PR #401) (Friday, 25 November)
Re: [w3c/permissions] Consider making `request-permission-to-use` aware of user activation (#194) (Friday, 25 November)
[w3c/permissions] Integrate "request permission to use" with user activation (PR #401) (Friday, 25 November)
Re: [w3c/permissions] Consider making `request-permission-to-use` aware of user activation (#194) (Friday, 25 November)
Re: [w3c/permissions] Align internal states with enums (Issue #392) (Friday, 25 November)
[w3c/permissions] Editorial: define permission states consistently (PR #400) (Friday, 25 November)
[w3c/permissions] Editorial: user enum values for permission concept (PR #399) (Friday, 25 November)
Re: [w3c/permissions] Align internal states with enums (Issue #392) (Friday, 25 November)
Re: [w3c/permissions] Editorial: define and improve use of permissions task source (PR #398) (Friday, 25 November)
[w3c/permissions] Editorial: define and improve use of permissions task source (PR #398) (Friday, 25 November)
Re: [w3c/permissions] Consider removing "lifetime" (Issue #391) (Friday, 25 November)
Re: [w3c/permissions] Remove use of realms (PR #397) (Friday, 25 November)
[w3c/permissions] Remove use of realms (PR #397) (Friday, 25 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 25 November)
Re: [w3c/permissions] WIP: Define a permission store (closes #384) (PR #390) (Friday, 25 November)
Re: [w3c/gamepad] Please don't restrict to a secure context (#145) (Thursday, 24 November)
Re: [w3c/screen-orientation] Editorial: relocate page visibility change step to HTML (PR #240) (Tuesday, 22 November)
Re: [w3c/screen-orientation] Editorial: relocate page visibility change step to HTML (PR #240) (Tuesday, 22 November)
Re: [w3c/screen-orientation] Editorial: relocate page visibility change step to HTML (PR #240) (Tuesday, 22 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Tuesday, 22 November)
Re: [w3c/screen-orientation] Editorial: relocate page visibility change step to HTML (PR #240) (Tuesday, 22 November)
Re: [w3c/screen-orientation] Feature detection of orientation.lock (Issue #206) (Wednesday, 16 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Tuesday, 15 November)
Re: [w3c/screen-orientation] Feature detection of orientation.lock (Issue #206) (Tuesday, 15 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Monday, 14 November)
Re: [w3c/screen-orientation] Feature detection of orientation.lock (Issue #206) (Monday, 14 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Monday, 14 November)
Re: [w3c/screen-orientation] Editorial: relocate page visibility change step to HTML (PR #240) (Monday, 14 November)
[w3c/screen-orientation] Editorial: relocate page visibility change step to HTML (PR #240) (Monday, 14 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Friday, 11 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Thursday, 10 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Thursday, 10 November)
Re: [w3c/screen-orientation] Consume user activation (PR #218) (Thursday, 10 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Thursday, 10 November)
[whatwg/fullscreen] Rely solely on transient activation for orientation events (PR #209) (Thursday, 10 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Thursday, 10 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Thursday, 10 November)
Re: [w3c/screen-orientation] Consume user activation (PR #218) (Wednesday, 9 November)
Re: [w3c/screen-orientation] Allow unlock() to return a promise (PR #231) (Wednesday, 9 November)
Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Wednesday, 9 November)
Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Wednesday, 9 November)
Re: [w3c/screen-orientation] Switch to "navigables" instead of browsing contexts (Issue #238) (Wednesday, 9 November)
Re: [w3c/screen-orientation] Editorial: switch to navigables (PR #239) (Wednesday, 9 November)
Re: [w3c/screen-orientation] Restrict locking to visible documents (PR #230) (Wednesday, 9 November)
Re: [w3c/screen-orientation] Restrict locking to visible documents (PR #230) (Wednesday, 9 November)
Re: [w3c/screen-orientation] Allow unlock() to return a promise (PR #231) (Wednesday, 9 November)
[w3c/screen-orientation] Editorial: switch to navigables (PR #239) (Wednesday, 9 November)
Re: [w3c/screen-orientation] Prevent hidden documents from locking orientation (PR #232) (Wednesday, 9 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Tuesday, 8 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Tuesday, 8 November)
Re: [w3c/manifest] Fix broken active-document reference (PR #1063) (Tuesday, 8 November)
Re: [w3c/manifest] Fix broken active-document reference (PR #1063) (Tuesday, 8 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Wednesday, 2 November)
Re: [whatwg/fullscreen] DRAFT PROPOSAL: Pre-apply orientation lock via FullscreenOptions (PR #207) (Wednesday, 2 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Wednesday, 2 November)
[w3c/screen-orientation] Switch to "navigables" instead of browsing contexts (Issue #238) (Wednesday, 2 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Tuesday, 1 November)
Re: [w3c/screen-orientation] Editorial: rewrite parallel steps (PR #236) (Tuesday, 1 November)
Re: [w3c/screen-orientation] "reject and nullify the current lock promise" and tasks (Issue #234) (Tuesday, 1 November)
Re: [w3c/screen-orientation] Editorial: rewrite parallel steps (PR #236) (Tuesday, 1 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Tuesday, 1 November)
[whatwg/fullscreen] DRAFT PROPOSAL: Pre-apply orientation lock via FullscreenOptions (PR #207) (Tuesday, 1 November)
Re: [whatwg/fullscreen] Exiting full screen should unlock screen orientation (Issue #202) (Tuesday, 1 November)

Marijn Kruisselbrink

Re: [w3c/FileAPI] Editorial: slice blob should use nullable args (PR #184) (Wednesday, 30 November)
Re: [w3c/FileAPI] Editorial: slice blob should use nullable args (PR #184) (Wednesday, 30 November)
Re: [w3c/FileAPI] editorial: make Blob.slice a separate algorithm (PR #183) (Monday, 14 November)
Re: [w3c/FileAPI] editorial: make Blob.slice a separate algorithm (PR #183) (Monday, 14 November)
Re: [w3c/FileAPI] editorial: make Blob.slice a separate algorithm (PR #183) (Friday, 11 November)

Martin

Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Wednesday, 23 November)
Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Tuesday, 22 November)

Martin Alvarez-Espinar

Re: [w3c/manifest] `id` member reuse in MiniApps Manifest (no `document URL`) (Issue #1048) (Thursday, 24 November)

Martin Thomson

Re: [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Friday, 4 November)

Masayuki Nakano

Re: [w3c/uievents] Proposal: Way to determine if any modifier key is pressed (#151) (Wednesday, 9 November)
Re: [w3c/uievents] Proposal: Way to determine if any modifier key is pressed (#151) (Tuesday, 8 November)

Mason Freed

Re: [w3ctag/design-reviews] The Popup API (Issue #743) (Wednesday, 16 November)
Re: [w3ctag/design-reviews] The Popup API (Issue #743) (Tuesday, 1 November)

Matt Giuca

Re: [w3c/manifest] Export processed manifest and application context definitions (PR #1062) (Wednesday, 9 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] Define an algorithm for launching a web app (PR #1056) (Monday, 7 November)
Re: [w3c/manifest] editorial: Move the definition of display-mode back to APPMANIFEST. (PR #1039) (Friday, 4 November)

Mattias Buelens

Re: [whatwg/streams] Examine interaction of resizable array buffers with Streams (Issue #1248) (Monday, 21 November)

Michael Wasserman

Re: [w3c/screen-orientation] Consume user activation (PR #218) (Monday, 28 November)
Re: [whatwg/fullscreen] Allow fullscreen on already fullscreen elements without user activation (#193) (Tuesday, 15 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Tuesday, 8 November)

Mike Taylor

Re: [w3c/permissions] Allow returning "prompt" rather than "denied" (Issue #388) (Wednesday, 30 November)
Re: [w3c/permissions] Define a permission store (closes #384) (PR #390) (Wednesday, 30 November)
Re: [w3c/permissions] Remove use of realms (PR #397) (Monday, 28 November)

Mike West

Re: [whatwg/fetch] Remove Authorization header upon cross-origin redirect (PR #1544) (Wednesday, 23 November)

Miriam Suzanne

[w3ctag/design-reviews] Design and specification review of CSS Container Queries Style Features (Issue #787) (Monday, 21 November)

Mr. Nattapon Makchoo

[whatwg/fetch] I’m (Issue #1531) (Saturday, 5 November)

Mustaq Ahmed

Re: [whatwg/fullscreen] Allow fullscreen on already fullscreen elements without user activation (#193) (Thursday, 24 November)
Re: [whatwg/fullscreen] Allow fullscreen on already fullscreen elements without user activation (#193) (Tuesday, 15 November)
Re: [whatwg/fullscreen] Consume user gestures in requestFullscreen (#152) (Tuesday, 8 November)
Re: [whatwg/fullscreen] Consume user gestures in requestFullscreen (#152) (Thursday, 3 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Wednesday, 2 November)

Nano Miratus

Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Thursday, 17 November)

Nick Burris

Re: [whatwg/webidl] Add OptOutError to the error names list (PR #1231) (Friday, 11 November)
[whatwg/webidl] Add OptOutError to the error names list (PR #1231) (Friday, 11 November)
Re: [whatwg/webidl] New error name: OptOutError (Issue #1168) (Wednesday, 2 November)

Nico Weber

Re: [whatwg/fetch] Editorial: Remove a duplicate "in" (PR #1528) (Thursday, 3 November)
Re: [whatwg/fetch] Editorial: Remove a duplicate "in" (PR #1528) (Thursday, 3 November)
Re: [whatwg/fetch] Editorial: Remove a duplicate "in" (PR #1528) (Thursday, 3 November)
Re: [whatwg/fetch] Editorial: Remove a duplicate "in" (PR #1528) (Thursday, 3 November)
[whatwg/fetch] Editorial: Remove a duplicate "in" (PR #1528) (Thursday, 3 November)

Nidhi Jaju

Re: [w3c/ServiceWorker] Abort with fetch controller's error in Handle Fetch (PR #1655) (Monday, 14 November)

Nigel Megitt

[w3ctag/design-reviews] Review of IMSC-HRM (Issue #788) (Tuesday, 22 November)

Noam Rosenthal

Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Wednesday, 30 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Wednesday, 30 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Tuesday, 29 November)
Re: [whatwg/fetch] Expose decoded/encoded size for constructed responses (PR #1456) (Monday, 28 November)
Re: [whatwg/fetch] Expose decoded/encoded size for constructed responses (PR #1456) (Monday, 28 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 28 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 28 November)
[w3c/ServiceWorker] Increment encoded/decoded body size for constructed responses (PR #1664) (Monday, 28 November)
Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483) (Monday, 28 November)
Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483) (Monday, 28 November)
Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483) (Monday, 28 November)
Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483) (Monday, 28 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 28 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 28 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 28 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 28 November)
Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 28 November)

Nolan Lawson

Re: [WICG/webcomponents] Can ElementInternals have ARIA properties pointing inside the shadow root? (Issue #974) (Tuesday, 29 November)
Re: [WICG/webcomponents] Can ElementInternals have ARIA properties pointing inside the shadow root? (Issue #974) (Monday, 21 November)
Re: [WICG/webcomponents] Can ElementInternals have ARIA IDREFs pointing inside the shadow root? (Issue #974) (Thursday, 17 November)

orvillelawrence72

Re: [whatwg/url] IDNA: avoid defining valid domain string in terms of the parser (#245) (Saturday, 19 November)

Patrick Meenan

Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Wednesday, 30 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Wednesday, 30 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Wednesday, 30 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Monday, 28 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Monday, 28 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Monday, 28 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Monday, 28 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Monday, 28 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Monday, 28 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Monday, 28 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Monday, 28 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Tuesday, 22 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Tuesday, 22 November)
Re: [whatwg/fetch] Standardize Priority Hints (#1319) (Monday, 21 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Friday, 11 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Friday, 11 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Friday, 11 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Friday, 11 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Friday, 11 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Friday, 11 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Friday, 11 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Wednesday, 2 November)
Re: [whatwg/fetch] Standardize Priority Hints (#1319) (Tuesday, 1 November)

Paul Libbrecht

Re: [w3c/clipboard-apis] Add Web Custom format (PR #175) (Tuesday, 15 November)

Paul van Dinther

Re: [w3c/gamepad] Please don't restrict to a secure context (#145) (Friday, 11 November)

Peter Batory-Bernardin

Re: [w3c/manifest] Add option to disable built-in navigation gestures (Issue #1041) (Tuesday, 1 November)

Peter Linss

Re: [whatwg/xhr] Align with Fetch's forbidden request-header refactor (PR #362) (Friday, 25 November)

Philip Jägenstedt

Re: [whatwg/fullscreen] Fullscreen tests are manual? (Issue #211) (Wednesday, 30 November)
Re: [whatwg/fullscreen] Allow fullscreen on already fullscreen elements without user activation (#193) (Friday, 25 November)
Re: [whatwg/fullscreen] Allow fullscreen on already fullscreen elements without user activation (#193) (Friday, 25 November)
Re: [whatwg/fullscreen] Allow fullscreen on already fullscreen elements without user activation (#193) (Thursday, 24 November)
Re: [whatwg/fullscreen] Change fullscreen CSS from `top`/`bottom`/`left`/`right` to `inset` (Issue #201) (Thursday, 24 November)
Re: [whatwg/fullscreen] Editorial: use inset property in the UA style sheet (PR #210) (Thursday, 24 November)
Re: [whatwg/fullscreen] Editorial: use inset property in the UA style sheet (PR #210) (Thursday, 24 November)
Re: [whatwg/fullscreen] Use inset property in the UA style sheet (PR #210) (Thursday, 24 November)
Re: [whatwg/fullscreen] Use inset property in the UA style sheet (PR #210) (Thursday, 24 November)
[whatwg/fullscreen] Use inset property in the UA style sheet (PR #210) (Thursday, 24 November)
Re: [whatwg/fullscreen] Exiting full screen should unlock screen orientation (Issue #202) (Thursday, 24 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Thursday, 24 November)
Re: [whatwg/fullscreen] Unlock the screen orientation when exiting fullscreen (PR #206) (Thursday, 24 November)
Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204) (Thursday, 24 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Tuesday, 15 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Tuesday, 15 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Monday, 14 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Monday, 14 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Monday, 14 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Wednesday, 2 November)
Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Wednesday, 2 November)
Re: [whatwg/fullscreen] Update to use navigables instead of browsing contexts (PR #208) (Wednesday, 2 November)
Re: [whatwg/fullscreen] Update to use navigables instead of browsing contexts (PR #208) (Wednesday, 2 November)

Podaru Dragos

Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Tuesday, 1 November)

pweis88

Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721) (Wednesday, 2 November)

Rick Byers

Re: [whatwg/webidl] Add discussion of unexposed interfaces? (Issue #1236) (Thursday, 24 November)
[whatwg/webidl] Add discussion of unexposed interfaces? (Issue #1236) (Wednesday, 23 November)

Rob Wu

Re: [whatwg/fetch] Specify exception to redirect-tainting: Upgrade-Insecure-Requests (UIR) and HSTS scheme upgrades (Issue #1551) (Monday, 28 November)
Re: [whatwg/fetch] Specify exception to redirect-tainting: Upgrade-Insecure-Requests (UIR) and HSTS scheme upgrades (Issue #1551) (Monday, 28 November)
[whatwg/fetch] Specify exception to redirect-tainting: Upgrade-Insecure-Requests (UIR) and HSTS scheme upgrades (Issue #1551) (Saturday, 26 November)

Robert Flack

Re: [whatwg/fullscreen] Consume user gestures in requestFullscreen (#152) (Thursday, 3 November)

Roderick Gadellaa

Re: [w3c/manifest] Transparent Bottom Navigation Bar (#804) (Wednesday, 30 November)

Rossen Atanassov

Re: [w3ctag/design-reviews] The Popup API (Issue #743) (Thursday, 17 November)

Rouslan Solomakhin

Re: [whatwg/webidl] Add OptOutError to the error names list (PR #1231) (Friday, 11 November)

Ryosuke Niwa

Re: [WICG/webcomponents] We need the ability to deregister or undefine custom elements. (Issue #970) (Sunday, 20 November)
Re: [w3c/selection-api] fixing typo Secruity -> Security (PR #160) (Sunday, 20 November)
Re: [w3c/selection-api] fixing typo Secruity -> Security (PR #160) (Sunday, 20 November)
Re: [WICG/webcomponents] We need the ability to deregister or undefine custom elements. (Issue #970) (Friday, 18 November)
Re: [WICG/webcomponents] We need the ability to deregister or undefine custom elements. (Issue #970) (Friday, 18 November)

Sadiq512

Re: [whatwg/dom] Hamza (Issue #1124) (Tuesday, 1 November)
[whatwg/dom] Hamza (Issue #1124) (Tuesday, 1 November)

Sam Sneddon

Re: [w3c/clipboard-apis] Web Platform tests using "clipboard-read" (Issue #188) (Wednesday, 30 November)
Re: [w3c/clipboard-apis] Interoperability issue: `navigator.clipboard.write()` and `navigator.clipboard.writeText()` user gesture requirement (Issue #182) (Tuesday, 1 November)

Sarven Capadisli

Re: [whatwg/fetch] Remove slash in ACAO example value (PR #1537) (Monday, 14 November)
Re: [whatwg/fetch] Remove slash in ACAO example value (PR #1537) (Monday, 14 November)
[whatwg/fetch] Remove slash in ACAO example value (PR #1537) (Monday, 14 November)

Sasha Firsov

Re: [WICG/webcomponents] We need the ability to deregister or undefine custom elements. (Issue #970) (Sunday, 20 November)
Re: [WICG/webcomponents] [scoped-registries] CustomElementRegistry to support SDLC of generic browser entities (Issue #976) (Monday, 7 November)
[WICG/webcomponents] [scoped-registries] CustomElementRegistry to support SDLC of generic browser entities (Issue #976) (Monday, 7 November)
Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Monday, 7 November)
Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Friday, 4 November)
Re: [WICG/webcomponents] without .html in link rel="import" and href in web component (Issue #971) (Thursday, 3 November)
Re: [WICG/webcomponents] We need the ability to deregister or undefine custom elements. (Issue #970) (Wednesday, 2 November)
Re: [WICG/webcomponents] without .html in link rel="import" and href in web component (Issue #971) (Wednesday, 2 November)
Re: [WICG/webcomponents] without .html in link rel="import" and href in web component (Issue #971) (Tuesday, 1 November)

shamsdevo

[whatwg/fetch] Whatwg (Issue #1550) (Friday, 25 November)

Shane Hudson

Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Wednesday, 23 November)

smaug----

Re: [whatwg/webidl] 'this' and nested steps (Issue #1175) (Monday, 21 November)

Sunil Mayya

Re: [whatwg/fetch] Refactor forbidden request-headers (PR #1541) (Tuesday, 22 November)
Re: [whatwg/fetch] Refactor forbidden request-headers (PR #1541) (Monday, 21 November)

Tab Atkins Jr.

Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Wednesday, 30 November)
Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Tuesday, 29 November)
Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Wednesday, 23 November)
Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Wednesday, 23 November)
Re: [whatwg/dom] Broken references in DOM Standard (Issue #1130) (Tuesday, 22 November)

tguild

Re: [w3ctag/design-reviews] VISS (Vehicle Information Service Specification) 2 Core and VISS 2 Transport (Issue #768) (Tuesday, 29 November)

theaolsen

[whatwg/webidl] Intent to use Constants (Issue #1237) (Friday, 25 November)

Thomas Steiner

Re: [w3ctag/design-reviews] Sync Methods for FileSystemSyncAccessHandle in File System Access API (Issue #772) (Wednesday, 30 November)
Re: [w3c/manifest] Web Manifest Overrides (Issue #1045) (Wednesday, 23 November)

Tim Nguyen

Re: [w3ctag/design-reviews] The Popup API (Issue #743) (Monday, 14 November)

Tom Schuster

Re: [whatwg/fetch] Specify exception to redirect-tainting: Upgrade-Insecure-Requests (UIR) and HSTS scheme upgrades (Issue #1551) (Monday, 28 November)

Toni Williams

Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. #1536 (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. #1536 (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. #1536 (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
Re: [whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Monday, 14 November)
[whatwg/fetch] Update CSM destinations to CSP Level 3. (PR #1536) (Saturday, 12 November)

tungnh

Re: [w3c/permissions] Consider removing "lifetime" (Issue #391) (Tuesday, 29 November)
Re: [w3c/permissions] Consider removing "lifetime" (Issue #391) (Tuesday, 29 November)

Valentin Gosu

Re: [whatwg/fetch] Remove Authorization header upon cross-origin redirect (PR #1544) (Wednesday, 23 November)
Re: [whatwg/fetch] Proposal: consider url parsing to be more flexible about colons in the protocol part of a url (Issue #1535) (Wednesday, 9 November)
Re: [whatwg/fetch] Standardize Priority Hints (#1319) (Wednesday, 2 November)
Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523) (Tuesday, 1 November)

W3C Bot

Re: [w3c/FileAPI] Editorial: slice blob should use nullable args (PR #184) (Sunday, 27 November)
Re: [w3c/selection-api] fixing typo Secruity -> Security (PR #160) (Sunday, 20 November)
Re: [w3c/FileAPI] editorial: make Blob.slice a separate algorithm (PR #183) (Monday, 14 November)

Weihong Guan

Re: [w3c/gamepad] Please don't restrict to a secure context (#145) (Thursday, 24 November)

weihongliang233

Re: [whatwg/xhr] Wrong upload progress when network interrupts (Issue #361) (Tuesday, 22 November)
[whatwg/xhr] Wrong upload progress when network interrupts (Issue #361) (Friday, 18 November)

Wesley Luyten

Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902) (Wednesday, 30 November)
Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902) (Thursday, 24 November)

Xidorn Quan

Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153) (Tuesday, 15 November)

Yoav Weiss

Re: [whatwg/fetch] Does Server-Timing work when not exposed through Access-Control-Expose-Headers? (Issue #1511) (Friday, 25 November)
Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Tuesday, 8 November)

Yves Lafon

Re: [w3ctag/design-reviews] Wildcards in Permissions Policy Origins (Issue #765) (Tuesday, 29 November)
Re: [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Thursday, 24 November)
Re: [w3ctag/design-reviews] FileSystemHandle Unique ID (Issue #764) (Wednesday, 16 November)
Re: [w3ctag/design-reviews] FileSystemHandle Unique ID (Issue #764) (Wednesday, 16 November)
Re: [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Wednesday, 9 November)

Last message date: Wednesday, 30 November 2022 23:50:31 UTC