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

Abin K Paul

• Re: [whatwg/fetch] Pass in response status to mark resource timing (PR #1468) (Tuesday, 27 September)
• Re: [whatwg/fetch] Pass in response status to mark resource timing (PR #1468) (Tuesday, 27 September)
• Re: [whatwg/fetch] Pass in response status to mark resource timing (PR #1468) (Monday, 26 September)
• Re: [whatwg/fetch] [draft] Pass in content type to resource-timing (PR #1481) (Sunday, 11 September)
• Re: [whatwg/fetch] [draft] Pass in content type to resource-timing (PR #1481) (Sunday, 11 September)
• Re: [whatwg/fetch] [draft] Pass in content type to resource-timing (PR #1481) (Friday, 2 September)
• Re: [whatwg/fetch] [draft] Pass in content type to resource-timing (PR #1481) (Friday, 2 September)

Ada Rose Cannon

• Re: [w3ctag/design-reviews] CORS Requirement for 3rd party sources in <model> tag (Issue #775) (Friday, 16 September)
• [w3ctag/design-reviews] CORS Requirement for 3rd party sources in <model> tag (Issue #775) (Friday, 16 September)

Adam Rice

• Re: [whatwg/fetch] aborting locked request body (#1286) (Thursday, 29 September)

Adrian Hope-Bailie

• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 29 September)

Adriano

• Re: [whatwg/webidl] Intent to use Constants (Issue #1207) (Friday, 30 September)
• [whatwg/webidl] Intent to use Constants (Issue #1207) (Friday, 30 September)

alancutter

• Re: [w3c/manifest] About update icon in web app manifest (Issue #1049) (Friday, 16 September)

Alastair Coote

• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Wednesday, 28 September)

Alexis Hunt

• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Friday, 2 September)
• Re: [whatwg/url] Named validation errors (#406) (Friday, 2 September)
• Re: [whatwg/url] It is unlikely that the spec's two definitions of valid URL strings are equal (Issue #704) (Friday, 2 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)

Alwin Blok

• Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703) (Thursday, 22 September)
• Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703) (Monday, 12 September)
• Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703) (Sunday, 11 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Wednesday, 7 September)
• Re: [whatwg/url] It is unlikely that the spec's two definitions of valid URL strings are equal (Issue #704) (Friday, 2 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Friday, 2 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)

Andreu Botella

• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)

Andy Valencia

• Re: [whatwg/xhr] Remove XMLHttpRequest from ServiceWorkerGlobalScope (#19) (Monday, 12 September)

Anne van Kesteren

• Re: [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Friday, 30 September)
• Re: [whatwg/fetch] Explain the use-URL-credentials flag (PR #1498) (Friday, 30 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Friday, 30 September)
• Re: [whatwg/fetch] Pass in response status to mark resource timing (PR #1468) (Friday, 30 September)
• Re: [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Friday, 30 September)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Friday, 30 September)
• Re: [WICG/webcomponents] Interaction between imperative slotting and declarative shadow DOM (Issue #967) (Friday, 30 September)
• Re: [whatwg/webidl] PaintOptions example should not have nullable optional fields (Issue #1204) (Friday, 30 September)
• Re: [whatwg/webidl] Make PaintOptions example a better role model. (PR #1205) (Friday, 30 September)
• Re: [whatwg/fetch] aborting locked request body (#1286) (Thursday, 29 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Thursday, 29 September)
• Re: [whatwg/fetch] Pass in response status to mark resource timing (PR #1468) (Thursday, 29 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Thursday, 29 September)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 29 September)
• Re: [whatwg/encoding] Consider adding windows-936-2000 as a label for GBK (Issue #295) (Thursday, 29 September)
• Re: [whatwg/encoding] gb18030 encoder using index gb18030 ranges pointer (#258) (Thursday, 29 September)
• [whatwg/encoding] Consider adding windows-936-2000 as a label for GBK (Issue #295) (Thursday, 29 September)
• Re: [whatwg/webidl] Make PaintOptions example a better role model. (PR #1205) (Thursday, 29 September)
• Re: [whatwg/webidl] Make PaintOptions example a better role model. (PR #1205) (Thursday, 29 September)
• Re: [whatwg/webidl] DOMException needs Exposed=* (Issue #1136) (Thursday, 29 September)
• Re: [whatwg/webidl] Expose DOMException everywhere. (PR #1137) (Thursday, 29 September)
• Re: [whatwg/webidl] Make setlike/maplike generated properties enumerable (PR #1166) (Wednesday, 28 September)
• Re: [whatwg/webidl] Expose DOMException everywhere. (PR #1137) (Wednesday, 28 September)
• Re: [whatwg/webidl] Review Draft Publication: September 2022 (PR #1194) (Wednesday, 28 September)
• Re: [whatwg/webidl] Review Draft Publication: September 2022 (PR #1194) (Wednesday, 28 September)
• [whatwg/webidl] Future of webidl-grammar-post-processor (Issue #1203) (Wednesday, 28 September)
• Re: [whatwg/webidl] Annotations for what may throw (#603) (Tuesday, 27 September)
• Re: [whatwg/webidl] Improvements to DOMException error names table (PR #1202) (Tuesday, 27 September)
• Re: [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Tuesday, 27 September)
• Re: [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Tuesday, 27 September)
• Re: [whatwg/webidl] Meta: assume the browser supports CSS transforms (PR #1201) (Tuesday, 27 September)
• Re: [whatwg/webidl] Meta: fix the grammar post processor on Review Drafts (PR #1200) (Tuesday, 27 September)
• Re: [whatwg/webidl] Meta: fix the grammar post processor on Review Drafts (PR #1200) (Tuesday, 27 September)
• Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Tuesday, 27 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Monday, 26 September)
• Re: [whatwg/fetch] Pass in response status to mark resource timing (PR #1468) (Monday, 26 September)
• Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Monday, 26 September)
• Re: [whatwg/dom] "Element" has no method signature for "getElementById" (Issue #1114) (Monday, 26 September)
• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) (Monday, 26 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Monday, 26 September)
• Re: [whatwg/fetch] Ensure that a Request object can be used as RequestInit (Issue #1486) (Monday, 26 September)
• Re: [whatwg/fetch] Add duplex property to Request (PR #1493) (Monday, 26 September)
• Re: [whatwg/webidl] Does requiring a dictionary type implicitly allow passing dictionaries that inherit from it? (Issue #1199) (Monday, 26 September)
• Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483) (Monday, 26 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Monday, 26 September)
• Re: [whatwg/fetch] Termination's aborted flag (#703) (Monday, 26 September)
• Re: [whatwg/fetch] Termination's aborted flag (#703) (Monday, 26 September)
• Re: [whatwg/fetch] cleanup signal listener (#1287) (Monday, 26 September)
• Re: [whatwg/fetch] aborting locked request body (#1286) (Monday, 26 September)
• Re: [whatwg/fetch] "aborted flag" for non-network errors (#938) (Monday, 26 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Monday, 26 September)
• Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483) (Monday, 26 September)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Monday, 26 September)
• Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Monday, 26 September)
• Re: [whatwg/fetch] Pass in response status to mark resource timing (PR #1468) (Monday, 26 September)
• Re: [whatwg/fetch] Prevent cross-origin sensitive header probing (PR #1434) (Monday, 26 September)
• Re: [whatwg/fetch] Prevent cross-origin sensitive header probing (PR #1434) (Monday, 26 September)
• Re: [whatwg/fetch] Add duplex property to Request (PR #1493) (Monday, 26 September)
• Re: [whatwg/fetch] Add duplex property to Request (PR #1493) (Monday, 26 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Monday, 26 September)
• Re: [whatwg/webidl] Does requiring a dictionary type implicitly allow passing dictionaries that inherit from it? (Issue #1199) (Monday, 26 September)
• Re: [whatwg/fetch] Add duplex property to Request (PR #1493) (Monday, 26 September)
• Re: [whatwg/fetch] Ensure that a Request object can be used as RequestInit (Issue #1486) (Monday, 26 September)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Monday, 26 September)
• Re: [whatwg/fetch] Editorial: Fix incorrect variable name in 'create a Request object' (PR #1494) (Monday, 26 September)
• Re: [whatwg/fetch] Editorial: Fix incorrect variable name in 'create a Request object' (PR #1494) (Monday, 26 September)
• Re: [whatwg/fetch] Out-of-place words: "This is used to ensure to prevent a partial res..." (Issue #1477) (Monday, 26 September)
• Re: [whatwg/fetch] Editorial: correct some minor wording issues (PR #1490) (Monday, 26 September)
• Re: [whatwg/fetch] Typo: "unprivilaged API" (Issue #1476) (Monday, 26 September)
• Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Monday, 26 September)
• Re: [whatwg/fetch] Only break for 101 in "websocket" mode (PR #1491) (Monday, 26 September)
• Re: [whatwg/fetch] Consider if redirect tainting should apply to `Timing-Allow-Origin` (Issue #1484) (Monday, 26 September)
• Re: [whatwg/fetch] Prevent fetching from IPv4-mapped IPv6 addresses (Issue #1492) (Monday, 26 September)
• Re: [whatwg/fetch] Update Note on Request Destination / CSP directive (Issue #1466) (Saturday, 24 September)
• Re: [whatwg/fetch] Integrate early hints https://tools.ietf.org/html/rfc8297 (#1225) (Friday, 23 September)
• Re: [whatwg/fetch] Consider if redirect tainting should apply to `Timing-Allow-Origin` (Issue #1484) (Friday, 23 September)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Friday, 23 September)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Friday, 23 September)
• Re: [whatwg/fetch] blob url fetch with no mime type set is undefined (Issue #1436) (Friday, 23 September)
• Re: [whatwg/fetch] Allow more flexibility in how 401s/407s are handled? (#1132) (Friday, 23 September)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Friday, 23 September)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Friday, 23 September)
• Re: [whatwg/fetch] Always send Origin header for (non HEAD/GET) CORS requests (PR #1463) (Friday, 23 September)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Friday, 23 September)
• Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703) (Friday, 23 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Friday, 23 September)
• Re: [whatwg/fetch] Prevent fetching from IPv4-mapped IPv6 addresses (Issue #1492) (Thursday, 22 September)
• Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Thursday, 22 September)
• [whatwg/fetch] Only break for 101 in "websocket" mode (PR #1491) (Thursday, 22 September)
• Re: [whatwg/fetch] Editorial: correct some minor wording issues (PR #1490) (Thursday, 22 September)
• Re: [whatwg/fetch] Fix the reference to "generate and queue a report". (PR #1487) (Thursday, 22 September)
• Re: [whatwg/fetch] Fix the reference to "generate and queue a report". (PR #1487) (Thursday, 22 September)
• Re: [whatwg/fetch] Fix the reference to "generate and queue a report". (PR #1487) (Thursday, 22 September)
• Re: [whatwg/fetch] Expose decoded/encoded size for constructed responses (PR #1456) (Thursday, 22 September)
• Re: [whatwg/webidl] pp-webidl fails on Review Drafts (Issue #1195) (Thursday, 22 September)
• [whatwg/fetch] Editorial: correct some minor wording issues (PR #1490) (Thursday, 22 September)
• Re: [whatwg/fetch] Remove res.json() requirement (do it by default) when content-type application/json (Issue #1489) (Thursday, 22 September)
• Re: [whatwg/fetch] Remove res.json() requirement (do it by default) when content-type application/json (Issue #1489) (Thursday, 22 September)
• Re: [whatwg/fetch] Ensure that a Request object can be used as RequestInit (Issue #1486) (Wednesday, 21 September)
• Re: [whatwg/fetch] Behavior when consuming a body with for await (Issue #1488) (Wednesday, 21 September)
• [whatwg/webidl] pp-webidl fails on Review Drafts (Issue #1195) (Wednesday, 21 September)
• Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703) (Wednesday, 21 September)
• Re: [whatwg/fetch] Ensure that a Request object can be used as RequestInit (Issue #1486) (Wednesday, 21 September)
• Re: [whatwg/fetch] Behavior when consuming a body with for await (Issue #1488) (Wednesday, 21 September)
• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) (Wednesday, 21 September)
• Re: [whatwg/webidl] Allow dictionaries and callbacks to be distinguishable (Issue #1191) (Tuesday, 20 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Monday, 19 September)
• [whatwg/webidl] Review Draft Publication: September 2022 (PR #1194) (Monday, 19 September)
• Re: [w3c/editing] Edit text outside of <body> (Issue #405) (Thursday, 15 September)
• Re: [whatwg/fetch] Ensure that a Request object can be used as RequestInit (Issue #1486) (Thursday, 15 September)
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) (Thursday, 15 September)
• Re: [whatwg/dom] Disconnect single target instead of all (#126) (Thursday, 15 September)
• Re: [whatwg/dom] Requirement for AbortSignal argument to be named 'signal' can be confusing for some APIs. (Issue #1112) (Monday, 12 September)
• Re: [whatwg/xhr] Remove XMLHttpRequest from ServiceWorkerGlobalScope (#19) (Monday, 12 September)
• Re: [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110) (Saturday, 10 September)
• Re: [whatwg/webidl] Remove the word "instances" from DOMException custom bindings (PR #1187) (Saturday, 10 September)
• Re: [whatwg/url] Defered validation error reporting in IPv4 parser (Issue #706) (Saturday, 10 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Saturday, 10 September)
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) (Friday, 2 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Friday, 2 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Friday, 2 September)
• Re: [whatwg/url] It is unlikely that the spec's two definitions of valid URL strings are equal (Issue #704) (Friday, 2 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 1 September)
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) (Thursday, 1 September)

Anssi Kostiainen

• Re: [w3ctag/design-reviews] Delta review (to CR) of Web Neural Network API (Issue #771) (Monday, 26 September)
• [w3ctag/design-reviews] Delta review (to CR) of Web Neural Network API (Issue #771) (Friday, 9 September)

Ari Chivukula

• Re: [w3ctag/design-reviews] Wildcards in Permissions Policy Origins (Issue #765) (Wednesday, 14 September)

Ashbri4

• [whatwg/encoding] https://github.com/whatwg/html/issues/8302#issue-1381510657 #8301 (Issue #294) (Wednesday, 21 September)

Austin Sullivan

• [w3ctag/design-reviews] FileSystemHandle::remove() for the File System Access API (Issue #773) (Friday, 9 September)

Bahigac

• [whatwg/webidl] Apple account data (Issue #1192) (Sunday, 18 September)

bashi

• Re: [whatwg/fetch] Integrate early hints https://tools.ietf.org/html/rfc8297 (#1225) (Wednesday, 14 September)

Ben Kelly

• Re: [w3ctag/design-reviews] Service Worker Scope Pattern Matching explainer (#417) (Wednesday, 28 September)
• Re: [whatwg/storage] Compute storage keys to be stored on environments. (#142) (PR #143) (Wednesday, 14 September)
• Re: [whatwg/storage] Compute storage keys to be stored on environments. (#142) (PR #143) (Wednesday, 14 September)

Binyamin Laukstein

• [whatwg/fetch] Remove res.json() requirement (do it by default) when content-type application/json (Issue #1489) (Thursday, 22 September)

Brian E Carpenter

• Re: [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Tuesday, 13 September)
• Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Monday, 12 September)
• Re: [whatwg/url] Support IPv6 zone identifiers (#392) (Friday, 2 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Friday, 2 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)

Chengzhong Wu

• Re: [whatwg/webidl] Replaceable attribute `window.performance` (Issue #1193) (Monday, 19 September)
• [whatwg/webidl] Replaceable attribute `window.performance` (Issue #1193) (Sunday, 18 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Wednesday, 7 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Wednesday, 7 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Wednesday, 7 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Wednesday, 7 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Monday, 5 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Monday, 5 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Friday, 2 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Friday, 2 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Friday, 2 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 1 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 1 September)

Chris Lilley

• Re: [w3ctag/design-reviews] Output Device Selection in Web Audio API: AudioContext.setSinkId() (Issue #766) (Friday, 9 September)
• Re: [w3ctag/design-reviews] Output Device Selection in Web Audio API: AudioContext.setSinkId() (Issue #766) (Friday, 9 September)

Chris Rollins

• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Tuesday, 6 September)

Christian Biesinger

• Re: [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Friday, 30 September)
• Re: [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Friday, 30 September)
• Re: [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Thursday, 29 September)
• Re: [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Thursday, 29 September)
• Re: [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Thursday, 29 September)
• Re: [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Tuesday, 27 September)
• [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Tuesday, 27 September)

Christian Liebel

• Re: [w3c/manifest] Security Updates Scope | Samsung Mobile Security (Issue #1052) (Wednesday, 28 September)
• Re: [w3c/manifest] Nativejet (Issue #1051) (Wednesday, 28 September)
• Re: [w3c/manifest] w3cman (Issue #1050) (Sunday, 25 September)
• Re: [w3c/manifest] Display mode "standalone" inconsistently handled by browsers (#673) (Tuesday, 13 September)
• Re: [w3c/manifest] Display mode "standalone" inconsistently handled by browsers (#673) (Tuesday, 13 September)
• Re: [w3c/manifest] meta: see web almanac for any insights about manifest usage (#987) (Tuesday, 13 September)

Code Hangen

• Re: [WICG/webcomponents] without .html in link rel="import" and href in web component (Issue #971) (Thursday, 29 September)
• [WICG/webcomponents] link rel="import" href= without .html in web component (Issue #971) (Monday, 26 September)

Cohen Erickson

• Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529) (Thursday, 1 September)

CyrilCommando

• Re: [whatwg/xhr] Remove XMLHttpRequest from ServiceWorkerGlobalScope (#19) (Sunday, 11 September)

Dan Robertson

• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Friday, 23 September)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Friday, 23 September)
• Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Friday, 23 September)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Fetch streaming upload (Issue #754) (Thursday, 29 September)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation (heading to Candidate Recommendation) (Issue #763) (Thursday, 29 September)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation (heading to Candidate Recommendation) (Issue #763) (Thursday, 29 September)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation (heading to Candidate Recommendation) (Issue #763) (Tuesday, 27 September)

Daniel Ethridge

• Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891) (Sunday, 25 September)

Daniel Murphy

• Re: [w3c/manifest] About update icon in web app manifest (Issue #1049) (Friday, 16 September)

Daniel Stenberg

• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)

Darien Maillet Valentine

• Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891) (Monday, 26 September)
• Re: [whatwg/dom] "Element" has no method signature for "getElementById" (Issue #1114) (Saturday, 24 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Friday, 23 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Monday, 19 September)
• Re: [whatwg/webidl] Allow dictionaries and callbacks to be distinguishable (Issue #1191) (Saturday, 17 September)
• Re: [whatwg/webidl] Allow dictionaries and callbacks to be distinguishable (Issue #1191) (Saturday, 17 September)
• Re: [whatwg/webidl] draft: Interaction with the Stage 2 Record & Tuple proposal for ECMAScript (PR #1184) (Saturday, 17 September)
• Re: [whatwg/webidl] draft: Interaction with the Stage 2 Record & Tuple proposal for ECMAScript (PR #1184) (Saturday, 17 September)
• Re: [whatwg/webidl] Can a platform object’s associated Realm really change? (Issue #1189) (Tuesday, 13 September)
• [whatwg/webidl] Can a platform object’s associated Realm really change? (Issue #1189) (Tuesday, 13 September)
• Re: [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110) (Sunday, 11 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Saturday, 10 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Wednesday, 7 September)

Dave Batiste

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 21 September)

Dave Longley

• Re: [whatwg/fetch] Referrer policy of "no-referrer" sets Origin to null on same-origin "cors" requests (#1022) (Tuesday, 20 September)

David Barratt

• Re: [whatwg/fetch] Ensure that a Request object can be used as RequestInit (Issue #1486) (Wednesday, 21 September)
• Re: [whatwg/fetch] Ensure that a Request object can be used as RequestInit (Issue #1486) (Wednesday, 21 September)
• Re: [whatwg/fetch] Ensure that a Request object can be used as RequestInit (Issue #1486) (Saturday, 17 September)
• [whatwg/fetch] Enusre that a Request object can be used as RequestInit (Issue #1486) (Thursday, 8 September)

David Enrique Jara molina

• Re: [whatwg/streams] Add user benefits section to byte stream explainer (660d259) (Sunday, 4 September)

Deadlym

• [whatwg/webidl] Issue (Issue #1188) (Sunday, 11 September)

Domenic Denicola

• [whatwg/fetch] Explain the use-URL-credentials flag (PR #1498) (Friday, 30 September)
• Re: [whatwg/fetch] "set authorizationValue to authentication entry" is insufficiently precise (Issue #1497) (Friday, 30 September)
• [whatwg/fetch] "set authorizationValue to authentication entry" is insufficiently precise (Issue #1497) (Friday, 30 September)
• [whatwg/fetch] Chromium's implementation of use-URL-credentials probably does not match the spec (Issue #1496) (Friday, 30 September)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Friday, 30 September)
• Re: [whatwg/webidl] Inconsistent enumerability on keys/values/entries and friends (#738) (Wednesday, 28 September)
• Re: [whatwg/webidl] Expose DOMException everywhere. (PR #1137) (Wednesday, 28 September)
• Re: [whatwg/webidl] Future of webidl-grammar-post-processor (Issue #1203) (Wednesday, 28 September)
• Re: [whatwg/webidl] Meta: fix the grammar post processor on Review Drafts (PR #1200) (Wednesday, 28 September)
• Re: [whatwg/webidl] Incorrect rendering of decimal terminal as nonterminal in HTML (#815) (Wednesday, 28 September)
• Re: [whatwg/webidl] pp-webidl fails on Review Drafts (Issue #1195) (Wednesday, 28 September)
• Re: [whatwg/webidl] pp-webidl fails on Review Drafts (Issue #1195) (Wednesday, 28 September)
• Re: [whatwg/webidl] Meta: fix the grammar post processor on Review Drafts (PR #1200) (Wednesday, 28 September)
• Re: [whatwg/webidl] Meta: assume the browser supports CSS transforms (PR #1201) (Wednesday, 28 September)
• Re: [whatwg/webidl] Meta: assume the browser supports CSS transforms (PR #1201) (Wednesday, 28 September)
• Re: [whatwg/webidl] Improvements to DOMException error names table (PR #1202) (Wednesday, 28 September)
• [whatwg/webidl] Improvements to DOMException error names table (PR #1202) (Tuesday, 27 September)
• Re: [whatwg/fetch] Add a destination type for FedCM (PR #1495) (Tuesday, 27 September)
• [whatwg/webidl] Meta: assume the browser supports CSS transforms (PR #1201) (Tuesday, 27 September)
• [whatwg/webidl] Meta: fix the grammar post processor on Review Drafts (PR #1200) (Tuesday, 27 September)
• Re: [whatwg/webidl] pp-webidl fails on Review Drafts (Issue #1195) (Tuesday, 27 September)
• Re: [whatwg/dom] Delete README.md (PR #1108) (Tuesday, 27 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 22 September)
• Re: [whatwg/webidl] pp-webidl fails on Review Drafts (Issue #1195) (Wednesday, 21 September)
• Re: [whatwg/webidl] Review Draft Publication: September 2022 (PR #1194) (Tuesday, 20 September)
• Re: [whatwg/webidl] Replaceable attribute `window.performance` (Issue #1193) (Sunday, 18 September)
• Re: [whatwg/webidl] Can a platform object’s associated Realm really change? (Issue #1189) (Wednesday, 14 September)
• Re: [whatwg/webidl] Consider adding `[LegacyASCIICaseInsentiveEnum]` for `element.insertAdjacent*` APIs (#968) (Wednesday, 14 September)
• Re: [whatwg/fetch] Integrate early hints https://tools.ietf.org/html/rfc8297 (#1225) (Wednesday, 14 September)
• Re: [whatwg/dom] Requirement for AbortSignal argument to be named 'signal' can be confusing for some APIs. (Issue #1112) (Monday, 12 September)
• Re: [whatwg/streams] Add support for asynchronous TransformStreams (Issue #1242) (Sunday, 11 September)
• Re: [whatwg/streams] Add support for asynchronous TransformStreams (Issue #1242) (Sunday, 11 September)
• Re: [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110) (Saturday, 10 September)
• Re: [whatwg/webidl] Remove the word "instances" from DOMException custom bindings (PR #1187) (Friday, 9 September)
• Re: [whatwg/webidl] Should `DOMException#stack` be standardized? (Issue #1186) (Friday, 9 September)
• Re: [whatwg/webidl] Should `DOMException#stack` be standardized? (Issue #1186) (Friday, 9 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Friday, 9 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Wednesday, 7 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Wednesday, 7 September)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Wednesday, 7 September)
• Re: [whatwg/streams] Warn about async processing of written/transformed chunks (PR #1239) (Tuesday, 6 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Monday, 5 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Monday, 5 September)
• Re: [whatwg/streams] Warn about async processing of written/transformed chunks (PR #1239) (Monday, 5 September)
• Re: [whatwg/streams] Warn about async processing of written/transformed chunks (PR #1239) (Monday, 5 September)
• Re: [whatwg/streams] Warn about async processing of written/transformed chunks (PR #1239) (Monday, 5 September)
• Re: [whatwg/streams] Warn about async processing of written/transformed chunks (PR #1239) (Monday, 5 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Monday, 5 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Monday, 5 September)
• Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721) (Friday, 2 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Friday, 2 September)
• [whatwg/url] It is unlikely that the spec's two definitions of valid URL strings are equal (Issue #704) (Friday, 2 September)

Dominique Hazael-Massieux

• Re: [whatwg/webidl] Annotations for what may throw (#603) (Tuesday, 27 September)

dslee414

• [w3ctag/design-reviews] Sync Methods for FileSystemSyncAccessHandle in File System Access API (Issue #772) (Friday, 9 September)

duniataymi

• Re: [w3c/manifest] related_applications needs more settings (Issue #1047) (Friday, 23 September)

Edgar Chen

• Re: [w3c/clipboard-apis] Add Web Custom format (PR #175) (Tuesday, 20 September)
• [w3c/clipboard-apis] Undefined behaviour when handling data promise resolved value (Issue #185) (Friday, 2 September)

Emilio Cobos Álvarez

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Sunday, 18 September)

Erik Kline

• Re: [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Monday, 12 September)
• [w3ctag/design-reviews] updated URI syntax for IPv6 link-local zone identifiers (Issue #774) (Monday, 12 September)

Evan Stade

• Re: [w3c/clipboard-apis] Interoperability issue: `navigator.clipboard.write()` and `navigator.clipboard.writeText()` user gesture requirement (Issue #182) (Wednesday, 7 September)

Fabian Meyer

• Re: [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` & `Response` (Issue #1384) (Thursday, 8 September)

Fabrice Desré

• Re: [w3c/manifest] Remove beforeinstallprompt and appinstalled events. (#836) (Thursday, 1 September)

fergald

• Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Friday, 16 September)

freaki2

• [whatwg/dom] https://drive.google.com/file/d/1LGZlsWXsDrER_micKUFhUtW_GzZJWGAV/view?usp=drivesdk (Issue #1113) (Thursday, 15 September)

Gabriel Basilio

• [WICG/webcomponents] Easily provide the template Id to HTMLElement (Issue #968) (Saturday, 3 September)

Genericreqd

• [whatwg/webidl] . (Issue #1206) (Thursday, 29 September)

Georgi Mavridis

• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Friday, 9 September)

Gio Lucas

• Re: [whatwg/dom] "Element" has no method signature for "getElementById" (Issue #1114) (Saturday, 24 September)
• [whatwg/dom] "Element" has no method signature for "getElementById" (Issue #1114) (Saturday, 24 September)

gschadow

• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Friday, 23 September)

Guillaume RENARD

• [w3c/clipboard-apis] Why does the Clipboard interface extends EventTarget? (Issue #186) (Thursday, 22 September)

Gustavo

• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Saturday, 10 September)

Henri Sivonen

• Re: [whatwg/encoding] Consider adding windows-936-2000 as a label for GBK (Issue #295) (Thursday, 29 September)

himorin

• [w3ctag/design-reviews] Delta review (to CR) of WebXR Gamepads Module (Issue #770) (Wednesday, 7 September)
• [w3ctag/design-reviews] Delta review (to CR) of WebXR Augmented Reality Module (Issue #769) (Wednesday, 7 September)

hober

• Re: [w3ctag/design-reviews] review HTML event loop and how things fit into it (#489) (Monday, 26 September)
• Re: [w3ctag/design-reviews] review HTML event loop and how things fit into it (#489) (Monday, 26 September)

Holger Jeromin

• Re: [w3c/clipboard-apis] Interoperability issue: `navigator.clipboard.write()` and `navigator.clipboard.writeText()` user gesture requirement (Issue #182) (Thursday, 8 September)

Hongchan Choi

• Re: [w3ctag/design-reviews] Output Device Selection in Web Audio API: AudioContext.setSinkId() (Issue #766) (Monday, 12 September)
• Re: [w3ctag/design-reviews] Output Device Selection in Web Audio API: AudioContext.setSinkId() (Issue #766) (Wednesday, 7 September)

Honglin Yu

• Re: [w3ctag/design-reviews] Web Machine Learning Model Loader API (Issue #759) (Friday, 9 September)

Howard Edwards

• Re: [w3c/editing] Define `contenteditable=plaintext-only` (PR #407) (Thursday, 29 September)
• [w3c/editing] Define `contenteditable=plaintext-only` (PR #407) (Thursday, 15 September)

Huan Pham

• [whatwg/webidl] Intent to use Constants (Issue #1197) (Sunday, 25 September)

Ian Frost

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 17 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 16 September)

ianbjacobs

• Re: [w3ctag/design-reviews] Secure Payment Confirmation (heading to Candidate Recommendation) (Issue #763) (Tuesday, 27 September)

Iwan Aucamp

• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)

J. Kalyana Sundaram

• [w3ctag/design-reviews] Requesting TAG review for Trace Context Level 2 changes (Issue #777) (Thursday, 29 September)

Jacob Smith

• Re: [w3c/ServiceWorker] should FetchEvent.request.signal reflect abort status of outer request? (#1544) (Tuesday, 20 September)

Jake Archibald

• Re: [whatwg/fetch] Add duplex property to Request (PR #1493) (Monday, 26 September)
• Re: [whatwg/fetch] Add duplex property to Request (PR #1493) (Monday, 26 September)
• Re: [whatwg/fetch] Add duplex property to Request (PR #1493) (Friday, 23 September)
• [whatwg/fetch] Add duplex property to Request (PR #1493) (Friday, 23 September)
• Re: [whatwg/webidl] Allow dictionaries and callbacks to be distinguishable (Issue #1191) (Sunday, 18 September)
• Re: [whatwg/webidl] Allow dictionaries and callbacks to be distinguishable (Issue #1191) (Sunday, 18 September)
• [whatwg/webidl] Allow dictionaries and callbacks to be distinguishable (Issue #1191) (Friday, 16 September)

James Browning

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 20 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 19 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 19 September)
• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) (Friday, 16 September)

James M Snell

• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 22 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 22 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 22 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 22 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Tuesday, 6 September)

Jasper St. Pierre

• Re: [whatwg/fetch] Missing interface for uncompressed Content-Length when compression is used (Issue #1358) (Sunday, 4 September)

Javad Chamanara

• Re: [w3c/manifest] Relationship between nestedly scoped web app manifests? (#539) (Tuesday, 13 September)

Jeff Johnson

• Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52) (Saturday, 3 September)

Jeffrey Yasskin

• [whatwg/fetch] Fix the reference to "generate and queue a report". (PR #1487) (Thursday, 15 September)
• Re: [w3c/permissions] Can we extend the manifest file so that extensions can extend the permissions API? (Issue #383) (Wednesday, 7 September)
• Re: [w3c/permissions] Can we extend the manifest file so that extensions can extend the permissions API? (Issue #383) (Wednesday, 7 September)

Jeremy Roman

• Re: [whatwg/webidl] Allow dictionaries and callbacks to be distinguishable (Issue #1191) (Saturday, 17 September)

Jimmy Wärting

• Re: [w3c/ServiceWorker] Add cookie accessor/setter methods? (#707) (Tuesday, 13 September)

Joe Pea

• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) (Friday, 30 September)
• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) (Friday, 30 September)
• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) (Monday, 26 September)
• Re: [whatwg/dom] Disconnect single target instead of all (#126) (Sunday, 11 September)
• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) (Sunday, 11 September)
• [whatwg/dom] `MutationObserver` `childList` events fire in unexpected and grouped order, requiring complex workarounds. (Issue #1111) (Sunday, 11 September)

Joel Rodrigues

• Re: [w3c/ServiceWorker] Add cookie accessor/setter methods? (#707) (Tuesday, 13 September)

Johannes Wilm

• Re: [w3c/editing] Add 2022-09-15 minutes (PR #408) (Friday, 16 September)
• Re: [w3c/editing] Add 2022-09-15 minutes (PR #408) (Friday, 16 September)
• Re: [w3c/editing] Adding Aug 11, 2022 meeting minutes (PR #406) (Thursday, 15 September)
• Re: [w3c/editing] Adding Aug 11, 2022 meeting minutes (PR #406) (Thursday, 15 September)
• Re: [w3c/editing] TPAC 2022 (Issue #400) (Monday, 12 September)
• Re: [w3c/editing] TPAC 2022 (Issue #400) (Friday, 9 September)

John Cowan

• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)

John Gamble

• [WICG/webcomponents] We need the ability to deregister or undefine custom elements. (Issue #970) (Monday, 26 September)

Jordan Harband

• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Friday, 9 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Friday, 9 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Thursday, 8 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Wednesday, 7 September)

Joshua Bell

• Re: [w3c/IndexedDB] 627129262 (Issue #393) (Saturday, 24 September)
• Re: [whatwg/encoding] https://github.com/whatwg/html/issues/8302#issue-1381510657 #8301 (Issue #294) (Wednesday, 21 September)
• Re: [whatwg/encoding] https://github.com/whatwg/html/issues/8302#issue-1381510657 #8301 (Issue #294) (Wednesday, 21 September)
• Re: [w3c/IndexedDB] TPAC 2022 status report (Issue #389) (Thursday, 15 September)

JR Conlin

• Re: [w3c/push-api] A javascript api for sending push notifications to others (#303) (Thursday, 29 September)

jub0bs

• Re: [whatwg/fetch] Editorial: correct some minor wording issues (PR #1490) (Saturday, 24 September)

Justin Fagnani

• Re: [WICG/webcomponents] Interaction between imperative slotting and declarative shadow DOM (Issue #967) (Wednesday, 28 September)
• Re: [WICG/webcomponents] Interaction between imperative slotting and declarative shadow DOM (Issue #967) (Wednesday, 28 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Wednesday, 21 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 19 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Monday, 19 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Sunday, 18 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 17 September)
• Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969) (Wednesday, 7 September)

Kagami Sascha Rosylight

• Re: [whatwg/webidl] Inconsistent enumerability on keys/values/entries and friends (#738) (Sunday, 18 September)
• Re: [whatwg/webidl] Remove the word "instances" from DOMException custom bindings (PR #1187) (Saturday, 10 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Friday, 9 September)
• [whatwg/webidl] Remove the word "instances" from DOMException custom bindings (PR #1187) (Friday, 9 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Friday, 9 September)
• Re: [whatwg/webidl] Should `DOMException#stack` be standardized? (Issue #1186) (Friday, 9 September)
• [whatwg/webidl] Should `DOMException#stack` be standardized? (Issue #1186) (Friday, 9 September)

karam

• Re: [whatwg/dom] ###### GitHub whatwg/dom participation (Issue #1109) (Friday, 9 September)
• [whatwg/dom] ###### GitHub whatwg/dom participation (Issue #1109) (Friday, 9 September)

Karl

• Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703) (Sunday, 11 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)

kaybrazy

• [whatwg/webidl] Snapchat (Issue #1198) (Monday, 26 September)

Keith Cirkel

• Re: [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110) (Friday, 9 September)

Khafra

• [whatwg/fetch] Behavior when consuming a body with for await (Issue #1488) (Sunday, 18 September)

Khushal Sagar

• Re: [w3ctag/design-reviews] Shared Element Transitions API (Issue #748) (Tuesday, 13 September)
• Re: [w3ctag/design-reviews] Shared Element Transitions API (Issue #748) (Thursday, 8 September)

KOLANICH

• Re: [w3c/permissions] Can we extend the manifest file so that extensions can extend the permissions API? (Issue #383) (Wednesday, 7 September)

Kyle Den Hartog

• Re: [w3c/permissions] Can we extend the manifest file so that extensions can extend the permissions API? (Issue #383) (Sunday, 11 September)
• [w3c/permissions] Can we extend the manifest file so that extensions can extend the permissions API? (Issue #383) (Wednesday, 7 September)

Larry Masinter

• Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703) (Thursday, 22 September)
• Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703) (Sunday, 11 September)
• Re: [whatwg/url] Provide a succinct grammar for valid URL strings (#479) (Thursday, 1 September)

Lea Verou

• Re: [w3ctag/design-reviews] Early design review of CSS Container Queries proposal (#592) (Wednesday, 7 September)

Linus Groh

• [whatwg/fetch] Editorial: Fix incorrect variable name in 'create a Request object' (PR #1494) (Saturday, 24 September)

ll0295478

• Re: [whatwg/dom] Define XSLTProcessor (#181) (Monday, 5 September)

Luca Casonato

• Re: [whatwg/fetch] Add duplex property to Request (PR #1493) (Monday, 26 September)

Léonie Watson

• Re: [w3c/uievents-key] Get horizontal review for UIEvents KeyboardEvent Key (Issue #56) (Tuesday, 13 September)
• Re: [w3c/uievents-key] Get horizontal review for UIEvents KeyboardEvent Key (Issue #56) (Tuesday, 13 September)
• [w3c/uievents-key] Tasks for wide review (Issue #57) (Tuesday, 13 September)
• [w3c/uievents-code] Tasks for wide review (Issue #35) (Tuesday, 13 September)

Madmonkey215

• [whatwg/dom] Delete README.md (PR #1108) (Wednesday, 7 September)
• [whatwg/dom] Manage slot manipulation centrally and special case replace operations (PR #1107) (Tuesday, 6 September)

Maks Orlovich

• [whatwg/dom] Requirement for AbortSignal argument to be named 'signal' can be confusing for some APIs. (Issue #1112) (Monday, 12 September)

Marcos Cáceres

• Re: [whatwg/webidl] Should 'undefined' be disallowed as an attribute type? (Issue #1112) (Wednesday, 21 September)
• Re: [whatwg/webidl] Should 'undefined' be disallowed as an attribute type? (Issue #1112) (Wednesday, 21 September)
• Re: [w3c/manifest] Remove beforeinstallprompt and appinstalled events. (#836) (Thursday, 1 September)

Marijn Kruisselbrink

• Re: [w3c/FileAPI] TPAC 2022 status report (Issue #178) (Monday, 12 September)

Marino Simic

• Re: [w3c/manifest] Remove beforeinstallprompt and appinstalled events. (#836) (Thursday, 1 September)
• Re: [w3c/manifest] Remove beforeinstallprompt and appinstalled events. (#836) (Thursday, 1 September)
• Re: [w3c/manifest] Remove beforeinstallprompt and appinstalled events. (#836) (Thursday, 1 September)
• Re: [w3c/manifest] Remove beforeinstallprompt and appinstalled events. (#836) (Thursday, 1 September)
• Re: [w3c/manifest] Remove beforeinstallprompt and appinstalled events. (#836) (Thursday, 1 September)

Masayuki Nakano

• Re: [w3c/editing] Edit text outside of <body> (Issue #405) (Wednesday, 21 September)

Mason Freed

• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Friday, 30 September)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Friday, 30 September)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Friday, 30 September)
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) (Friday, 9 September)
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) (Tuesday, 6 September)
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) (Friday, 2 September)
• Re: [whatwg/fullscreen] Change fullscreen CSS from `top`/`bottom`/`left`/`right` to `inset` (Issue #201) (Friday, 2 September)
• Re: [w3ctag/design-reviews] The Popup API (Issue #743) (Friday, 2 September)
• Re: [WICG/webcomponents] TPAC 2022 Web Components Meeting(s) (Issue #966) (Thursday, 1 September)

Matt Giuca

• Re: [whatwg/webidl] Make PaintOptions example a better role model. (PR #1205) (Friday, 30 September)
• Re: [whatwg/webidl] Make PaintOptions example a better role model. (PR #1205) (Friday, 30 September)
• [whatwg/webidl] Make PaintOptions example a better role model. (PR #1205) (Thursday, 29 September)
• [whatwg/webidl] PaintOptions example should not have nullable optional fields (Issue #1204) (Thursday, 29 September)
• Re: [w3c/manifest] TPAC 2022 status report (Issue #1046) (Thursday, 8 September)
• Re: [w3c/manifest] TPAC 2022 status report (Issue #1046) (Thursday, 8 September)
• Re: [w3c/manifest] Remove beforeinstallprompt and appinstalled events. (#836) (Thursday, 1 September)
• Re: [w3c/manifest] Remove beforeinstallprompt and appinstalled events. (#836) (Thursday, 1 September)

Matt Reynolds

• [w3c/gamepad] Replace "current settings object's relevant global object" (PR #171) (Wednesday, 14 September)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Saturday, 10 September)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Saturday, 10 September)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Friday, 9 September)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Friday, 9 September)
• Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163) (Friday, 9 September)
• Re: [w3c/gamepad] TPAC 2022 status report (Issue #169) (Friday, 9 September)

Mattias Buelens

• Re: [whatwg/fetch] Behavior when consuming a body with for await (Issue #1488) (Wednesday, 21 September)
• Re: [whatwg/streams] Warn about async processing of written/transformed chunks (PR #1239) (Monday, 5 September)

minfrin

• [whatwg/streams] Add support for asynchronous TransformStreams (Issue #1242) (Sunday, 11 September)

Ming-Ying Chung

• [w3ctag/design-reviews] Early Design Review: Page Unload Beacon API (Issue #776) (Tuesday, 27 September)

Ms2ger

• Re: [whatwg/webidl] Expose DOMException everywhere. (PR #1137) (Wednesday, 28 September)
• Re: [w3c/gamepad] Replace "current settings object's relevant global object" (PR #171) (Thursday, 15 September)
• [w3c/gamepad] "current settings object's relevant global object" is not defined (Issue #170) (Wednesday, 14 September)

Mustaq Ahmed

• Re: [w3c/uievents] Click event is not fired when the node is removed and then added back (#141) (Friday, 30 September)
• Re: [w3c/pointerlock] Option needed to disable OS-level adjustment for mouse acceleration (#36) (Monday, 12 September)
• Re: [w3c/pointerlock] TPAC 2022 status report (Issue #80) (Monday, 12 September)
• Re: [w3c/pointerlock] TPAC 2022 status report (Issue #80) (Monday, 12 September)
• Re: [w3c/pointerlock] Clarify how requestPointerLock relies on user activation (#67) (Monday, 12 September)
• Re: [w3c/pointerlock] Clarify how requestPointerLock relies on user activation (#67) (Monday, 12 September)

Nabi KaramAliZadeh

• Re: [w3c/clipboard-apis] Interoperability issue: `navigator.clipboard.write()` and `navigator.clipboard.writeText()` user gesture requirement (Issue #182) (Thursday, 1 September)

Nidhi Jaju

• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Friday, 30 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Friday, 30 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Friday, 30 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Friday, 30 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Thursday, 29 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Wednesday, 28 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Wednesday, 28 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Wednesday, 28 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Wednesday, 28 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Friday, 16 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Wednesday, 7 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Wednesday, 7 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Wednesday, 7 September)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Wednesday, 7 September)

nin-jin

• Re: [w3c/ServiceWorker] Create service worker from Blob/String URL (#578) (Thursday, 22 September)

Noam Rosenthal

• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Tuesday, 27 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Monday, 26 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Monday, 26 September)
• Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483) (Monday, 26 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Monday, 26 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Monday, 26 September)
• Re: [whatwg/fetch] Expose decoded/encoded size for constructed responses (PR #1456) (Sunday, 25 September)
• Re: [whatwg/fetch] Consider if redirect tainting should apply to `Timing-Allow-Origin` (Issue #1484) (Sunday, 25 September)
• Re: [whatwg/fetch] Only break for 101 in "websocket" mode (PR #1491) (Sunday, 25 September)
• Re: [whatwg/fetch] Accept header for prefetch (PR #1485) (Wednesday, 7 September)
• [whatwg/fetch] Accept header for prefetch (PR #1485) (Tuesday, 6 September)
• [whatwg/fetch] Consider if redirect tainting should apply to `Timing-Allow-Origin` (Issue #1484) (Monday, 5 September)
• Re: [whatwg/fetch] [draft] Pass in content type to resource-timing (PR #1481) (Monday, 5 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Friday, 2 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Friday, 2 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Friday, 2 September)
• Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Friday, 2 September)
• Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483) (Friday, 2 September)
• [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483) (Friday, 2 September)

Nolan Lawson

• Re: [WICG/webcomponents] TPAC 2022 Web Components Meeting(s) (Issue #966) (Thursday, 22 September)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Thursday, 22 September)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Monday, 19 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Sunday, 18 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 17 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 17 September)

Owen Buckley

• Re: [WICG/webcomponents] TPAC 2022 Web Components Meeting(s) (Issue #966) (Sunday, 4 September)

palibodatanja

• [w3c/IndexedDB] 627129262 (Issue #393) (Saturday, 24 September)

Peter Van der Beken

• Re: [whatwg/webidl] Make setlike/maplike generated properties enumerable (PR #1166) (Wednesday, 28 September)
• Re: [whatwg/webidl] Inconsistent enumerability on keys/values/entries and friends (#738) (Wednesday, 28 September)
• Re: [whatwg/webidl] Replaceable attribute `window.performance` (Issue #1193) (Sunday, 18 September)
• Re: [whatwg/webidl] Can a platform object’s associated Realm really change? (Issue #1189) (Tuesday, 13 September)
• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Monday, 5 September)

Philip Ceralde

• [w3c/manifest] Security Updates Scope | Samsung Mobile Security (Issue #1052) (Wednesday, 28 September)
• [w3c/manifest] Nativejet (Issue #1051) (Wednesday, 28 September)
• [w3c/manifest] w3cman (Issue #1050) (Sunday, 25 September)

Philippe Le Hegaret

• Re: [w3ctag/design-reviews] Personalization Semantics Explainer and  Module 1 (#476) (Friday, 23 September)

Rakina Zata Amni

• Re: [w3ctag/design-reviews] Back/Forward Cache (#628) (Thursday, 29 September)

Raphael Kubo da Costa

• Re: [whatwg/webidl] Does requiring a dictionary type implicitly allow passing dictionaries that inherit from it? (Issue #1199) (Monday, 26 September)
• Re: [whatwg/webidl] Does requiring a dictionary type implicitly allow passing dictionaries that inherit from it? (Issue #1199) (Monday, 26 September)
• Re: [whatwg/webidl] Does requiring a dictionary type implicitly allow passing dictionaries that inherit from it? (Issue #1199) (Monday, 26 September)
• [whatwg/webidl] Does requiring a dictionary type implicitly allow passing dictionaries that inherit from it? (Issue #1199) (Monday, 26 September)

Rasmus Schultz

• Re: [whatwg/dom] Proposal: New method to reorder child nodes (#891) (Monday, 26 September)

Raymond D. Lee, M. Sc.

• Re: [w3c/clipboard-apis] Interoperability issue: `navigator.clipboard.write()` and `navigator.clipboard.writeText()` user gesture requirement (Issue #182) (Thursday, 1 September)

Reilly Grant

• Re: [whatwg/streams] Warn about async processing of written/transformed chunks (PR #1239) (Monday, 5 September)

Robert Knight

• Re: [w3c/uievents] "keyCode" is the only way to work with KeyboardEvents now (#267) (Tuesday, 6 September)
• Re: [w3c/uievents] "keyCode" is the only way to work with KeyboardEvents now (#267) (Tuesday, 6 September)

Robin Ricard

• Re: [whatwg/webidl] draft: Interaction with the Stage 2 Record & Tuple proposal for ECMAScript (PR #1184) (Tuesday, 20 September)

Rune Lillesveen

• Re: [w3ctag/design-reviews] Early design review of CSS Container Queries proposal (#592) (Tuesday, 6 September)

Ryosuke Niwa

• Re: [WICG/webcomponents] Interaction between ElementInternals (e.g. default ARIA) and declarative shadow DOM (Issue #972) (Friday, 30 September)
• Re: [WICG/webcomponents] Interaction between imperative slotting and declarative shadow DOM (Issue #967) (Friday, 30 September)
• Re: [WICG/webcomponents] Interaction between imperative slotting and declarative shadow DOM (Issue #967) (Wednesday, 28 September)
• Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914) (Wednesday, 28 September)
• Re: [WICG/webcomponents] Interaction between imperative slotting and declarative shadow DOM (Issue #967) (Wednesday, 28 September)
• Re: [WICG/webcomponents] Interaction between ElementInternals (e.g. default ARIA) and declarative shadow DOM (Issue #972) (Wednesday, 28 September)
• [WICG/webcomponents] Interaction between ElementInternals (e.g. default ARIA) and declarative shadow DOM (Issue #972) (Wednesday, 28 September)
• Re: [WICG/webcomponents] Interaction between imperative slotting and declarative shadow DOM (Issue #967) (Wednesday, 28 September)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Wednesday, 28 September)
• Re: [WICG/webcomponents] We need the ability to deregister or undefine custom elements. (Issue #970) (Monday, 26 September)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Friday, 23 September)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Friday, 23 September)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Thursday, 22 September)
• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) (Sunday, 11 September)
• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) (Sunday, 11 September)
• Re: [whatwg/dom] `childList` across different `MutationObserver`s can reverse orders (Issue #1111) (Sunday, 11 September)
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) (Tuesday, 6 September)
• Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106) (Tuesday, 6 September)

S.A.N

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Sunday, 18 September)

sahilm-10

• Re: [whatwg/fetch] Update Note on Request Destination / CSP directive (Issue #1466) (Wednesday, 21 September)

Samuel David De La Cruz

• Re: [WICG/webcomponents] Easily provide the template Id to HTMLElement (Issue #968) (Saturday, 3 September)

Sasha Firsov

• Re: [WICG/webcomponents] [declarative-custom-elements] how would SSR work? (#886) (Friday, 30 September)
• Re: [WICG/webcomponents] without .html in link rel="import" and href in web component (Issue #971) (Thursday, 29 September)
• Re: [WICG/webcomponents] without .html in link rel="import" and href in web component (Issue #971) (Thursday, 29 September)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Friday, 23 September)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Friday, 23 September)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Wednesday, 21 September)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Tuesday, 20 September)

Scott Haseley

• Re: [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110) (Friday, 9 September)
• Re: [w3ctag/design-reviews] AbortSignal.timeout() (Issue #711) (Friday, 9 September)
• [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110) (Friday, 9 September)

Shiino Yuki

• Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179) (Tuesday, 6 September)

silverwind

• Re: [whatwg/url] Consider adding a constructor to make a URL from parts (#354) (Friday, 23 September)

Simeon Vincent

• Re: [w3c/manifest] Web Manifest Overrides (Issue #1045) (Monday, 12 September)

Simon Pieters

• Re: [w3c/editing] TPAC 2022 (Issue #400) (Monday, 12 September)
• Re: [w3c/editing] TPAC 2022 (Issue #400) (Thursday, 8 September)

smaug----

• Re: [w3c/pointerlock] Option needed to disable OS-level adjustment for mouse acceleration (#36) (Monday, 12 September)

snianu

• Re: [w3c/clipboard-apis] Add Web Custom format (PR #175) (Tuesday, 20 September)
• Re: [w3c/clipboard-apis] Support for reading custom MIME types from the clipboard (#46) (Thursday, 1 September)
• Re: [w3c/clipboard-apis] Support for reading custom MIME types from the clipboard (#46) (Thursday, 1 September)

Tab Atkins Jr.

• Re: [whatwg/webidl] pp-webidl fails on Review Drafts (Issue #1195) (Wednesday, 21 September)

Thomas Steiner

• Re: [w3c/clipboard-apis] Interoperability issue: `navigator.clipboard.write()` and `navigator.clipboard.writeText()` user gesture requirement (Issue #182) (Thursday, 8 September)

Timothy Gu

• Re: [whatwg/webidl] Can a platform object’s associated Realm really change? (Issue #1189) (Tuesday, 13 September)

Titouan Rigoudy

• [whatwg/fetch] Prevent fetching from IPv4-mapped IPv6 addresses (Issue #1492) (Thursday, 22 September)

Tobie Langel

• Re: [whatwg/webidl] pp-webidl fails on Review Drafts (Issue #1195) (Thursday, 22 September)

Tom Wilkinson

• Re: [whatwg/dom] Consider adding a timeout parameter to the AbortController constructor (Issue #1110) (Friday, 9 September)

transformsen

• Re: [w3c/ServiceWorker] [Question] How to get replacesClientId? (Issue #1623) (Tuesday, 13 September)

Trevor Rowbotham

• Re: [whatwg/url] Defered validation error reporting in IPv4 parser (Issue #706) (Saturday, 10 September)
• [whatwg/url] Defered validation error reporting in IPv4 parser (Issue #706) (Saturday, 10 September)

Vitali Lovich

• Re: [whatwg/fetch] Trailer support in the API (#981) (Thursday, 15 September)

Wiktor

• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Thursday, 22 September)

Xiaocheng Hu

• [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969) (Wednesday, 7 September)

Xiaoqian Wu

• [w3c/editing] Add 2022-09-15 minutes (PR #408) (Friday, 16 September)
• Re: [w3c/editing] Define `contenteditable=plaintext-only` (PR #407) (Friday, 16 September)

Yoav Weiss

• Re: [whatwg/fetch] Pass in response status to mark resource timing (PR #1468) (Friday, 30 September)
• Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481) (Tuesday, 27 September)
• Re: [whatwg/fetch] [draft] Pass in content type to resource-timing (PR #1481) (Monday, 5 September)

Yutaka Hirano

• Re: [w3ctag/design-reviews] Fetch streaming upload (Issue #754) (Friday, 30 September)
• Re: [w3ctag/design-reviews] Fetch streaming upload (Issue #754) (Tuesday, 6 September)

Yves Lafon

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

Šime Vidas

• Re: [w3c/clipboard-apis] Interoperability issue: `navigator.clipboard.write()` and `navigator.clipboard.writeText()` user gesture requirement (Issue #182) (Friday, 2 September)
• Re: [w3c/clipboard-apis] Interoperability issue: `navigator.clipboard.write()` and `navigator.clipboard.writeText()` user gesture requirement (Issue #182) (Friday, 2 September)

林耕宇

• Re: [whatwg/dom] Document.defaultCharset (#58) (Thursday, 1 September)
• Re: [whatwg/dom] Document.defaultCharset (#58) (Thursday, 1 September)

Last message date: Friday, 30 September 2022 23:57:34 UTC