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

=JeffH

• Re: [whatwg/dom] Request for a different type of example of abort steps (Issue #1031) (Thursday, 11 November)
• Re: [whatwg/dom] Request for a different type of example of abort steps (Issue #1031) (Thursday, 11 November)
• Re: [whatwg/dom] AbortSignal's abort reason downstream integration (Issue #1030) (Thursday, 11 November)

Aaron Gustafson

• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Friday, 19 November)
• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Thursday, 18 November)
• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Thursday, 11 November)
• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Thursday, 11 November)
• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Wednesday, 10 November)
• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Tuesday, 9 November)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Wednesday, 3 November)
• Re: [w3c/manifest] editorial: Making URL processing DRY (PR #1018) (Wednesday, 3 November)

achristensen07

• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Monday, 29 November)
• Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674) (Wednesday, 24 November)
• Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674) (Tuesday, 23 November)
• [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674) (Tuesday, 23 November)
• Re: [whatwg/url] Setters can cause failure to roundtrip (#651) (Tuesday, 23 November)
• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Wednesday, 17 November)

Adam Langley

• [w3ctag/design-reviews] WebAuthn minPinLength (Issue #687) (Friday, 5 November)
• [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Monday, 1 November)

Adam Rice

• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Tuesday, 30 November)
• Re: [whatwg/fetch] Additions to "bad port list" for UDP due to HTTP/3 (#1268) (Tuesday, 23 November)
• Re: [whatwg/streams] cocurrent steam (Issue #1188) (Friday, 19 November)
• Re: [whatwg/streams] cocurrent steam (Issue #1188) (Friday, 19 November)
• Re: [whatwg/streams] Add a realtime mode to ReadableStream.tee (Issue #1186) (Thursday, 18 November)
• Re: [whatwg/streams] Transferable streams: the double transfer problem (#1063) (Tuesday, 16 November)
• Re: [whatwg/streams] Piping to writable streams with HWM 0? (#1158) (Tuesday, 16 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Monday, 1 November)

alancutter

• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Friday, 26 November)
• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Thursday, 25 November)
• Re: [w3c/manifest] Add a manifest option for the declaration of the web application running pattern (Issue #1019) (Wednesday, 10 November)
• Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005) (Monday, 8 November)

Alex Gough

• Re: [w3c/editing] Security Review (#315) (Monday, 1 November)

Alex Keng

• Re: [w3c/editing] EditContext: update the Canvas example and fix video link in the Explainer (PR #361) (Monday, 15 November)
• Re: [w3c/editing] EditContext: update the Canvas example and fix video link in the Explainer (PR #361) (Wednesday, 10 November)
• Re: [w3c/editing] EditContext: update the Canvas example and fix video link in the Explainer (PR #361) (Wednesday, 10 November)
• Re: [w3c/editing] EditContext: Are the events for `EditContext` propagated in the DOM tree? (#341) (Wednesday, 10 November)
• Re: [w3c/editing] EditContext: Do IME see the plaintext in `EditContext`? (#342) (Wednesday, 10 November)
• Re: [w3c/editing] EditContext: Should `selectionStart` and `selectionEnd` be upadeted when `updateText()` is called? (#343) (Wednesday, 10 November)
• [w3c/editing] EditContext: update the Canvas example and fix video link in the Explainer (PR #361) (Tuesday, 9 November)
• Re: [w3c/editing] Expose keyboard language? (#351) (Tuesday, 2 November)
• Re: [w3c/editing] Expose keyboard language? (#351) (Tuesday, 2 November)

Alex Russell

• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Wednesday, 24 November)

alex2snikers

• Re: [w3c/ServiceWorker] Capturing Audio and Webcam within Service Worker (Issue #1613) (Tuesday, 16 November)
• Re: [w3c/ServiceWorker] Capturing Audio and Webcam within Service Worker (Issue #1613) (Tuesday, 9 November)
• Re: [w3c/ServiceWorker] Capturing Audio and Webcam within Service Worker (Issue #1613) (Tuesday, 9 November)
• [w3c/ServiceWorker] Capturing Audio and Webcam within Service Worker (Issue #1613) (Tuesday, 9 November)

Alwin Blok

• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Sunday, 28 November)
• [whatwg/url] Disallow all C0 control and DEL codepoints in hosts (PR #673) (Monday, 22 November)
• Re: [whatwg/url] Setters can cause failure to roundtrip (#651) (Monday, 22 November)
• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Wednesday, 17 November)
• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Monday, 15 November)
• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Monday, 15 November)
• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Sunday, 14 November)
• Re: [whatwg/url] "Forbidden host code point" should be defined without U+0025 (#319) (Sunday, 14 November)

amirouche

• Re: [w3c/IndexedDB] Range bytes counts and keys count (Issue #368) (Thursday, 25 November)
• Re: [w3c/IndexedDB] Clarify that IndexedDB's consistency model is strict serializability (#355) (Thursday, 25 November)
• Re: [w3c/IndexedDB] Clarify that IndexedDB's consistency model is strict serializability (#355) (Thursday, 25 November)
• [w3c/IndexedDB] Range bytes counts and keys count (Issue #368) (Thursday, 25 November)

Amy Guy

• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Tuesday, 16 November)
• Re: [w3ctag/design-reviews] WebXR Raw Camera Access API (#652) (Monday, 8 November)

Anders Rundgren

• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Sunday, 14 November)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Tuesday, 9 November)

Andreu Botella

• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Monday, 29 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Monday, 29 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Monday, 29 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Friday, 26 November)
• [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Friday, 26 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)

Andrew Sutherland

• Re: [w3c/ServiceWorker] consider using navigation preload response when respondWith() is not called (Issue #1611) (Thursday, 4 November)
• Re: [w3c/ServiceWorker] consider using navigation preload response when respondWith() is not called (Issue #1611) (Wednesday, 3 November)

André Cipriani Bandarra

• Re: [w3c/manifest] Icon purpose "splashscreen" and splashscreen text (#844) (Friday, 12 November)
• Re: [w3c/manifest] Icon purpose "splashscreen" and splashscreen text (#844) (Friday, 12 November)

Anne van Kesteren

• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Tuesday, 30 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Tuesday, 30 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Tuesday, 30 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Tuesday, 30 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Tuesday, 30 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Tuesday, 30 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Tuesday, 30 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Tuesday, 30 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Tuesday, 30 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Tuesday, 30 November)
• Re: [whatwg/url] Should we escape \ in non-special non-opaque paths? (Issue #675) (Tuesday, 30 November)
• Re: [whatwg/dom] "(use public-script-coord@w3.org for discussion)" (Issue #1036) (Monday, 29 November)
• Re: [whatwg/dom] Editorial: update some links (PR #1037) (Monday, 29 November)
• Re: [whatwg/fetch] Editorial: scheme is not a standalone type (PR #1361) (Monday, 29 November)
• [whatwg/dom] Editorial: update some links (PR #1037) (Monday, 29 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Monday, 29 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Friday, 26 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Friday, 26 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Friday, 26 November)
• [whatwg/fetch] Editorial: scheme is not a standalone type (PR #1361) (Friday, 26 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Friday, 26 November)
• Re: [whatwg/xhr] Editorial: Use HTML's definitions of "entry list" and "entry" (PR #338) (Friday, 26 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Friday, 26 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Thursday, 25 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Thursday, 25 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Thursday, 25 November)
• Re: [whatwg/fetch] Expand on processResponseEndOfBody values (PR #1360) (Thursday, 25 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Thursday, 25 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Thursday, 25 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Wednesday, 24 November)
• Re: [whatwg/webidl] Constructing DOMException with causes (#969) (Wednesday, 24 November)
• Re: [whatwg/storage] Editorial: fix {{PermissionState/granted}} enum value quotes (PR #130) (Wednesday, 24 November)
• Re: [whatwg/storage] Editorial: fix {{PermissionState/granted}} enum value quotes (PR #130) (Wednesday, 24 November)
• Re: [whatwg/storage] Update Persistence permission section (Issue #128) (Wednesday, 24 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Wednesday, 24 November)
• Re: [whatwg/storage] Update Persistence permission section (Issue #128) (Wednesday, 24 November)
• Re: [whatwg/storage] Editorial: Minor Permissions-related edits (PR #129) (Wednesday, 24 November)
• Re: [whatwg/storage] Editorial: Minor Permissions-related edits (PR #129) (Wednesday, 24 November)
• Re: [whatwg/storage] Editorial: Minor Permissions-related edits (PR #129) (Wednesday, 24 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Wednesday, 24 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Wednesday, 24 November)
• Re: [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Wednesday, 24 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Wednesday, 24 November)
• Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674) (Tuesday, 23 November)
• Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674) (Tuesday, 23 November)
• Re: [whatwg/dom] Encourage use of AbortError for cancellation? (#927) (Tuesday, 23 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Tuesday, 23 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Tuesday, 23 November)
• Re: [whatwg/webidl] Proposal: DOMException.ignoreAborts(promise) (#933) (Tuesday, 23 November)
• Re: [whatwg/fetch] Send "null" Origin headers on cross-origin requests from an RFC7686 address (Issue #1350) (Tuesday, 23 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Tuesday, 23 November)
• Re: [w3c/push-api] base64 (#280) (Tuesday, 23 November)
• Re: [whatwg/webidl] Proposal: DOMException.ignoreAborts(promise) (#933) (Tuesday, 23 November)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Monday, 22 November)
• Re: [whatwg/url] Disallow all C0 control and DEL codepoints in hosts (PR #673) (Monday, 22 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 22 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Monday, 22 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Saturday, 20 November)
• Re: [whatwg/webidl] IDL-level support for permission checks? (Issue #1066) (Friday, 19 November)
• Re: [w3c/ServiceWorker] Pass controller from fetch, and abort SW fetch when it's canceled (PR #1620) (Friday, 19 November)
• Re: [w3c/ServiceWorker] should FetchEvent.request.signal reflect abort status of outer request? (#1544) (Friday, 19 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 19 November)
• Re: [whatwg/fetch] track "site for cookies" on requests and propagate in passthrough service workers (#1332) (Friday, 19 November)
• Re: [whatwg/fetch] track "site for cookies" on requests and propagate in passthrough service workers (#1332) (Friday, 19 November)
• Re: [whatwg/webidl] IDL-level support for permission checks? (Issue #1066) (Friday, 19 November)
• Re: [whatwg/fetch] Remove 'tainted origin flag'. (#1335) (PR #1357) (Thursday, 18 November)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Thursday, 18 November)
• Re: [whatwg/fetch] Remove 'tainted origin flag'. (#1335) (PR #1357) (Thursday, 18 November)
• Re: [whatwg/fetch] Remove 'tainted origin flag'. (#1335) (PR #1357) (Thursday, 18 November)
• Re: [whatwg/fetch] Remove 'tainted origin flag'. (#1335) (PR #1357) (Thursday, 18 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Thursday, 18 November)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 18 November)
• Re: [whatwg/fetch] Missing interface for uncompressed Content-Length when compression is used (Issue #1358) (Wednesday, 17 November)
• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Wednesday, 17 November)
• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Tuesday, 16 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Tuesday, 16 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Tuesday, 16 November)
• Re: [w3c/ServiceWorker] Specify how "terminate" works (PR #1612) (Tuesday, 16 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Tuesday, 16 November)
• Re: [whatwg/fetch] propagate request tainted origin flag and/or URL list through service workers (#1335) (Tuesday, 16 November)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Tuesday, 16 November)
• Re: [whatwg/streams] Use abort reason in ReadableStreamPipeTo (PR #1182) (Tuesday, 16 November)
• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Monday, 15 November)
• Re: [whatwg/fetch] propagate request tainted origin flag and/or URL list through service workers (#1335) (Monday, 15 November)
• Re: [whatwg/fetch] Fetch not sending cookies ? SameSite=none Secure credentials include cors (Issue #1354) (Monday, 15 November)
• Re: [whatwg/fetch] Fetch not sending cookies ? SameSite=none Secure credentials include cors (Issue #1354) (Monday, 15 November)
• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Monday, 15 November)
• Re: [whatwg/dom] Symbols should be allowed as Event types. (#331) (Monday, 15 November)
• Re: [whatwg/dom] Symbols should be allowed as Event types. (#331) (Monday, 15 November)
• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Monday, 15 November)
• Re: [whatwg/url] "Forbidden host code point" should be defined without U+0025 (#319) (Monday, 15 November)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Saturday, 13 November)
• Re: [w3c/ServiceWorker] Service workers allow for more responses to be executed as script (#1509) (Wednesday, 10 November)
• Re: [w3c/ServiceWorker] Service workers allow for more responses to be executed as script (#1509) (Wednesday, 10 November)
• Re: [w3c/ServiceWorker] Service workers allow for more responses to be executed as script (#1509) (Wednesday, 10 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Wednesday, 10 November)
• Re: [whatwg/dom] AbortSignal's abort reason downstream integration (Issue #1030) (Wednesday, 10 November)
• Re: [whatwg/fetch] Send "null" Origin headers on cross-origin requests from an RFC7686 address (Issue #1350) (Wednesday, 10 November)
• Re: [whatwg/dom] Add abort reason to AbortSignal (PR #1027) (Wednesday, 10 November)
• [whatwg/dom] AbortSignal's abort reason downstream integration (Issue #1030) (Wednesday, 10 November)
• Re: [whatwg/fetch] Bikeshed (remote) returns an error on main branch (Issue #1349) (Tuesday, 9 November)
• Re: [whatwg/fetch] Editorial: Add myself to acknowledgements list after several contributions (PR #1352) (Tuesday, 9 November)
• Re: [whatwg/fetch] Editorial: Add myself to acknowledgements list after several contributions (PR #1352) (Tuesday, 9 November)
• Re: [whatwg/fetch] Editorial: Add myself to acknowledgements list after several contributions (PR #1352) (Tuesday, 9 November)
• Re: [whatwg/fetch] Editorial: use AbortSignal's aborted predicate (PR #1353) (Tuesday, 9 November)
• Re: [whatwg/fetch] Bikeshed (remote) returns an error on main branch (Issue #1349) (Tuesday, 9 November)
• [whatwg/fetch] Editorial: use AbortSignal's aborted predicate (PR #1353) (Tuesday, 9 November)
• Re: [whatwg/fetch] Bikeshed (remote) returns an error on main branch (Issue #1349) (Tuesday, 9 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Tuesday, 9 November)
• Re: [whatwg/fetch] Send "null" Origin headers on cross-origin requests from an RFC7686 address (Issue #1350) (Tuesday, 9 November)
• Re: [whatwg/dom] Add abort reason to AbortSignal (PR #1027) (Monday, 8 November)
• Re: [whatwg/dom] Add abort reason to AbortSignal (PR #1027) (Monday, 8 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Friday, 5 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Friday, 5 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 4 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 4 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Thursday, 4 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Thursday, 4 November)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Thursday, 4 November)
• Re: [whatwg/dom] Add abort reason to AbortSignal (PR #1027) (Wednesday, 3 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Wednesday, 3 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Wednesday, 3 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Wednesday, 3 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Wednesday, 3 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Wednesday, 3 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Wednesday, 3 November)
• Re: [whatwg/dom] Add abort reason to AbortSignal (PR #1027) (Wednesday, 3 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Wednesday, 3 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Wednesday, 3 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Wednesday, 3 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Tuesday, 2 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Tuesday, 2 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Tuesday, 2 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Tuesday, 2 November)
• Re: [whatwg/xhr] Why do we need to remove synchronous XHR? (Issue #336) (Tuesday, 2 November)
• Re: [whatwg/fetch] Access-Control fields should be registered with IANA (#1052) (Tuesday, 2 November)
• Re: [whatwg/xhr] Why do we need to remove synchronous XHR? (Issue #336) (Tuesday, 2 November)
• Re: [whatwg/xhr] Why do we need to remove synchronous XHR? (Issue #336) (Tuesday, 2 November)
• Re: [whatwg/fetch] Propagate origin through the request constructor. (Fixes #1321) (PR #1345) (Monday, 1 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Monday, 1 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 1 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 1 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Monday, 1 November)
• Re: [whatwg/fetch] Fix typo (PR #1347) (Monday, 1 November)
• Re: [whatwg/fetch] Fix typo (PR #1347) (Monday, 1 November)
• Re: [whatwg/fetch] Propagate origin through the request constructor. (Fixes #1321) (PR #1345) (Monday, 1 November)
• Re: [whatwg/fetch] propagate request tainted origin flag and/or URL list through service workers (#1335) (Monday, 1 November)

Artem Zakharchenko

• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Monday, 29 November)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Friday, 26 November)

Arthur Sonzogni

• Re: [w3ctag/design-reviews] Anonymous iframes (#639) (Monday, 15 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Wednesday, 3 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Monday, 1 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Monday, 1 November)

Ashley (Scirra)

• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Tuesday, 9 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 8 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 1 November)

Ben Kelly

• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Tuesday, 30 November)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Monday, 29 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Monday, 29 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Wednesday, 24 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Wednesday, 24 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Wednesday, 24 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Wednesday, 24 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Wednesday, 24 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Wednesday, 24 November)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Wednesday, 24 November)
• Re: [whatwg/fetch] Propagate origin and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Monday, 22 November)
• Re: [whatwg/fetch] Propagate origin, tainted origin flag, and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Monday, 22 November)
• Re: [whatwg/fetch] track "site for cookies" on requests and propagate in passthrough service workers (#1332) (Friday, 19 November)
• Re: [whatwg/fetch] track "site for cookies" on requests and propagate in passthrough service workers (#1332) (Thursday, 18 November)
• Re: [whatwg/fetch] track "site for cookies" on requests and propagate in passthrough service workers (#1332) (Thursday, 18 November)
• Re: [whatwg/fetch] Remove 'tainted origin flag'. (#1335) (PR #1357) (Thursday, 18 November)
• Re: [whatwg/fetch] Propagate origin, tainted origin flag, and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Tuesday, 16 November)
• Re: [whatwg/fetch] Remove 'tainted origin flag'. (#1335) (PR #1357) (Tuesday, 16 November)
• [whatwg/fetch] Remove 'tainted origin flag'. (#1335) (PR #1357) (Tuesday, 16 November)
• Re: [whatwg/fetch] propagate request tainted origin flag and/or URL list through service workers (#1335) (Monday, 15 November)
• Re: [whatwg/fetch] propagate request tainted origin flag and/or URL list through service workers (#1335) (Monday, 15 November)
• Re: [whatwg/fetch] Propagate origin, tainted origin flag, and URL list through the request constructor. (Fixes #1321, #1335) (PR #1345) (Thursday, 11 November)
• Re: [whatwg/fetch] Propagate origin through the request constructor. (Fixes #1321) (PR #1345) (Thursday, 11 November)
• Re: [whatwg/fetch] propagate request tainted origin flag and/or URL list through service workers (#1335) (Thursday, 11 November)
• Re: [w3c/ServiceWorker] Make cache.put() drain the internal response body. (Fixes #1617) (PR #1619) (Wednesday, 10 November)
• [w3c/ServiceWorker] Make cache.put() drain the internal response body. (Fixes #1617) (PR #1619) (Wednesday, 10 November)
• Re: [w3c/ServiceWorker] Use fetch algorithms when getting VARY header values. (Fixes #1609) (PR #1618) (Wednesday, 10 November)
• [w3c/ServiceWorker] Use fetch algorithms when getting VARY header values. (Fixes #1609) (PR #1618) (Wednesday, 10 November)
• [w3c/ServiceWorker] cache API put should read internal response body of filtered responses (Issue #1617) (Wednesday, 10 November)
• Re: [w3c/ServiceWorker] Service workers allow for more responses to be executed as script (#1509) (Wednesday, 10 November)
• Re: [w3c/ServiceWorker] Service workers allow for more responses to be executed as script (#1509) (Wednesday, 10 November)
• Re: [w3c/ServiceWorker] Service workers allow for more responses to be executed as script (#1509) (Wednesday, 10 November)
• Re: [w3c/ServiceWorker] Cache API stores internal responses and does not recreate filtered responses (Issue #1614) (Tuesday, 9 November)
• Re: [w3c/ServiceWorker] Cache API stores internal responses and does not recreate filtered responses (Issue #1614) (Tuesday, 9 November)
• Re: [w3c/ServiceWorker] Service workers allow for more responses to be executed as script (#1509) (Tuesday, 9 November)
• Re: [w3c/ServiceWorker] Refactor filtered/internal responses in Cache API. (Fixes #1609, #1614) (PR #1615) (Tuesday, 9 November)
• Re: [w3c/ServiceWorker] Refactor filtered/internal responses in Cache API. (Fixes #1609, #1614) (PR #1615) (Tuesday, 9 November)
• Re: [w3c/ServiceWorker] Refactor filtered/internal responses in Cache API. (Fixes #1609, #1614) (PR #1615) (Tuesday, 9 November)
• [w3c/ServiceWorker] Refactor filtered/internal responses in Cache API. (Fixes #1609, #1614) (PR #1615) (Tuesday, 9 November)
• [w3c/ServiceWorker] Cache API stores internal responses and does not recreate filtered responses (Issue #1614) (Tuesday, 9 November)
• Re: [w3c/ServiceWorker] Capturing Audio and Webcam within Service Worker (Issue #1613) (Tuesday, 9 November)
• Re: [w3c/ServiceWorker] Capturing Audio and Webcam within Service Worker (Issue #1613) (Tuesday, 9 November)
• Re: [w3c/ServiceWorker] consider using navigation preload response when respondWith() is not called (Issue #1611) (Thursday, 4 November)
• Re: [w3c/ServiceWorker] consider using navigation preload response when respondWith() is not called (Issue #1611) (Thursday, 4 November)
• Re: [w3c/ServiceWorker] consider using navigation preload response when respondWith() is not called (Issue #1611) (Wednesday, 3 November)
• [w3c/ServiceWorker] consider using navigation preload response when respondWith() is not called (Issue #1611) (Wednesday, 3 November)
• Re: [whatwg/fetch] Propagate origin through the request constructor. (Fixes #1321) (PR #1345) (Monday, 1 November)
• Re: [whatwg/fetch] Propagate origin through the request constructor. (Fixes #1321) (PR #1345) (Monday, 1 November)

Ben Lesh

• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)

Benjamin Gruenbaum

• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 28 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 28 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 28 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/webidl] Proposal: DOMException.ignoreAborts(promise) (#933) (Wednesday, 24 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Wednesday, 24 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Tuesday, 23 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 21 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 21 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 21 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 21 November)
• [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 21 November)
• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Thursday, 18 November)
• Re: [whatwg/dom] Symbols should be allowed as Event types. (#331) (Monday, 15 November)
• Re: [whatwg/dom] Symbols should be allowed as Event types. (#331) (Friday, 12 November)

Bo Cupp

• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Monday, 1 November)

Boris Zbarsky

• Re: [whatwg/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Wednesday, 24 November)

Chris Dumez

• Re: [whatwg/dom] Add abort reason to AbortSignal (PR #1027) (Wednesday, 3 November)
• Re: [whatwg/dom] Add abort reason to AbortSignal (PR #1027) (Wednesday, 3 November)

Chris Harrelson

• Re: [w3ctag/design-reviews] WebAuthn minPinLength (Issue #687) (Monday, 15 November)

Christian Biesinger

• Re: [w3ctag/design-reviews] CSS: contain-intrinsic-size: auto, and converting to a shorthand property (#624) (Monday, 1 November)

Claudia Meadows

• Re: [whatwg/streams] Make read requests abortable (#1103) (Wednesday, 24 November)
• Re: [whatwg/streams] ReadableStreamBYOBReader.prototype.readFully(view) (#1143) (Tuesday, 23 November)

cogel26

• [whatwg/xhr] TES WEBSITE (Issue #337) (Monday, 8 November)

Corentin Wallez

• Re: [w3ctag/design-reviews] WebGPU and WGSL (#626) (Tuesday, 16 November)

Cory Mawhorter

• Re: [w3c/uievents] A way to determine what the value of an input will be if `beforeinput` is not prevented (#289) (Tuesday, 23 November)

CSS Meeting Bot

• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Friday, 12 November)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Friday, 12 November)

Cyan Ogilvie

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Saturday, 13 November)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Thursday, 4 November)

d066z

• [whatwg/webidl] change (Issue #1069) (Tuesday, 30 November)
• [whatwg/webidl] change (Issue #1068) (Tuesday, 30 November)

Dan Abramov

• Re: [whatwg/streams] Idiomatic Way to Explicitly Tell an Underlying Transform Stream to Flush to the Sink (#960) (Thursday, 18 November)

Daniel Appelquist

• Re: [w3ctag/design-reviews] WebAuthn minPinLength (Issue #687) (Wednesday, 24 November)
• Re: [w3ctag/design-reviews] WebAuthn minPinLength (Issue #687) (Wednesday, 24 November)
• Re: [w3ctag/design-reviews] Same-origin prerendering triggered by speculationrules (#667) (Wednesday, 24 November)
• Re: [w3ctag/design-reviews] Same-origin prerendering triggered by speculationrules (#667) (Tuesday, 23 November)
• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Monday, 22 November)
• Re: [w3ctag/design-reviews] Trust Token API (#414) (Monday, 22 November)
• Re: [w3ctag/design-reviews] Trust Token API (#414) (Monday, 22 November)
• Re: [w3ctag/design-reviews] WebTransport review request (#669) (Wednesday, 17 November)
• Re: [w3ctag/design-reviews] Anonymous iframes (#639) (Wednesday, 17 November)
• Re: [w3ctag/design-reviews] Anonymous iframes (#639) (Wednesday, 17 November)
• Re: [w3ctag/design-reviews] Trust Token API (#414) (Wednesday, 17 November)
• Re: [w3ctag/design-reviews] Same-origin prerendering triggered by speculationrules (#667) (Monday, 15 November)
• Re: [w3ctag/design-reviews] Anonymous iframes (#639) (Monday, 15 November)
• Re: [w3ctag/design-reviews] Distributed Tracing WG: Baggage specification (#650) (Monday, 15 November)
• Re: [w3ctag/design-reviews] Feature policy for Keyboard API (Issue #685) (Wednesday, 10 November)
• Re: [w3ctag/design-reviews] Keyboard Map (#238) (Wednesday, 10 November)
• Re: [w3ctag/design-reviews] WebXR Raw Camera Access API (#652) (Tuesday, 9 November)
• Re: [w3ctag/design-reviews] Compute Pressure API (#621) (Tuesday, 9 November)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Monday, 8 November)
• Re: [w3ctag/design-reviews] Anonymous iframes (#639) (Monday, 8 November)
• Re: [w3ctag/design-reviews] Trust Token API (#414) (Monday, 8 November)
• Re: [w3ctag/design-reviews] WebXR Raw Camera Access API (#652) (Wednesday, 3 November)
• Re: [w3ctag/design-reviews] WebXR Raw Camera Access API (#652) (Tuesday, 2 November)

Daniel Dyla

• Re: [w3ctag/design-reviews] Distributed Tracing WG: Baggage specification (#650) (Tuesday, 9 November)

Daniel Murphy

• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Tuesday, 30 November)
• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Tuesday, 30 November)
• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Tuesday, 9 November)
• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Monday, 8 November)
• Re: [w3c/manifest] Example suggests that `icons` `sizes` mean a minimum size, but normative text doesn't support that (#925) (Friday, 5 November)
• Re: [w3c/manifest] Shortcut_items uses manifest_url when it should use start_url (#1003) (Friday, 5 November)
• Re: [w3c/manifest] Relationship between nestedly scoped web app manifests? (#539) (Thursday, 4 November)
• Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005) (Thursday, 4 November)

Daniel Veditz

• Re: [w3c/permissions] Proposals: Drop "Powerful features registry" and PermissionName enum (Issue #314) (Monday, 8 November)

Darien Maillet Valentine

• Re: [whatwg/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Wednesday, 24 November)
• Re: [whatwg/webidl] Proposal: DOMException.ignoreAborts(promise) (#933) (Tuesday, 23 November)
• Re: [whatwg/webidl] Normative: Rename integer types to match ECMAScript typed arrays (#1030) (Sunday, 7 November)
• Re: [whatwg/webidl] Normative: Rename integer types to match ECMAScript typed arrays (#1030) (Sunday, 7 November)
• Re: [whatwg/webidl] Normative: Rename integer types to match ECMAScript typed arrays (#1030) (Sunday, 7 November)
• Re: [whatwg/webidl] Normative: Rename integer types to match ECMAScript typed arrays (#1030) (Sunday, 7 November)
• Re: [whatwg/webidl] Absence of "record" token from Other production (#694) (Sunday, 7 November)
• Re: [whatwg/webidl] BREAKING: Convert the `unrestricted` keyword into an extended attribute (#857) (Saturday, 6 November)

David

• [whatwg/url] My (Issue #671) (Friday, 12 November)

DelphineXL6

• Re: [whatwg/fetch] track "site for cookies" on requests and propagate in passthrough service workers (#1332) (Thursday, 11 November)
• Re: [whatwg/fetch] track "site for cookies" on requests and propagate in passthrough service workers (#1332) (Thursday, 11 November)

Denmaing

• Re: [whatwg/fetch] <dd><span>Parse error</span>. Create a new DOCTYPE token. Set its <i data-x="force-quirks flag">force-quirks flag</i> to … (Issue #1356) (Monday, 15 November)
• Re: [whatwg/fetch] <dd><span>Parse error</span>. Create a new DOCTYPE token. Set its <i data-x="force-quirks flag">force-quirks flag</i> to … (Issue #1356) (Monday, 15 November)
• Re: [whatwg/fetch] <dd><span>Parse error</span>. Create a new DOCTYPE token. Set its <i data-x="force-quirks flag">force-quirks flag</i> to … (Issue #1356) (Monday, 15 November)
• [whatwg/fetch] <dd><span>Parse error</span>. Create a new DOCTYPE token. Set its <i data-x="force-quirks flag">force-quirks flag</i> to … (Issue #1356) (Monday, 15 November)
• Re: [whatwg/fetch] Fetch not sending cookies ? SameSite=none Secure credentials include cors (Issue #1354) (Monday, 15 November)
• Re: [whatwg/fetch] Fetch not sending cookies ? SameSite=none Secure credentials include cors (Issue #1354) (Monday, 15 November)

Domenic Denicola

• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Monday, 29 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Monday, 29 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Monday, 29 November)
• Re: [whatwg/dom] Editorial: update some links (PR #1037) (Monday, 29 November)
• Re: [whatwg/fetch] Editorial: scheme is not a standalone type (PR #1361) (Monday, 29 November)
• Re: [whatwg/fetch] Expand on processResponseEndOfBody values (PR #1360) (Monday, 29 November)
• Re: [whatwg/fetch] Expand on processResponseEndOfBody values (PR #1360) (Monday, 29 November)
• Re: [whatwg/fetch] Expand on processResponseEndOfBody values (PR #1360) (Monday, 29 November)
• [whatwg/dom] "(use public-script-coord@w3.org for discussion)" (Issue #1036) (Monday, 29 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 28 November)
• Re: [whatwg/fetch] Editorial: scheme is not a standalone type (PR #1361) (Saturday, 27 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Thursday, 25 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Thursday, 25 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Wednesday, 24 November)
• Re: [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• Re: [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• Re: [whatwg/streams] Roll WPT for abort reason (#1189) (Wednesday, 24 November)
• Re: [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• Re: [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• [whatwg/fetch] Expand on processResponseEndOfBody values (PR #1360) (Wednesday, 24 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Wednesday, 24 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Wednesday, 24 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Wednesday, 24 November)
• Re: [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Wednesday, 24 November)
• [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Tuesday, 23 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Tuesday, 23 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Tuesday, 23 November)
• Re: [whatwg/webidl] Proposal: DOMException.ignoreAborts(promise) (#933) (Tuesday, 23 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 21 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 21 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 21 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 19 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Friday, 19 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Friday, 19 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Friday, 19 November)
• [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Friday, 19 November)
• Re: [whatwg/webidl] IDL-level support for permission checks? (Issue #1066) (Friday, 19 November)
• Re: [whatwg/streams] Use abort reason in ReadableStreamPipeTo (PR #1182) (Friday, 19 November)
• Re: [whatwg/streams] WritableStreamDefaultController.abortReason (#1165) (Friday, 19 November)
• Re: [whatwg/streams] Use abort reason in ReadableStreamPipeTo (PR #1182) (Friday, 19 November)
• Re: [whatwg/webidl] IDL-level support for permission checks? (Issue #1066) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 18 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 18 November)
• Re: [w3ctag/design-reviews] Early design review of modal close signals/ModalCloseWatcher (#594) (Tuesday, 16 November)
• Re: [whatwg/streams] Use abort reason in ReadableStreamPipeTo (PR #1182) (Monday, 15 November)
• Re: [w3c/pointerlock] Remove redundant user activation text from PointerLock spec. (PR #76) (Monday, 15 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 15 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 11 November)
• Re: [whatwg/dom] Request for a different type of example of abort steps (Issue #1031) (Thursday, 11 November)
• Re: [whatwg/dom] Request for a different type of example of abort steps (Issue #1031) (Thursday, 11 November)
• Re: [whatwg/dom] AbortSignal's abort reason downstream integration (Issue #1030) (Thursday, 11 November)
• Re: [whatwg/dom] Request for a different type of example of abort steps (Issue #1031) (Thursday, 11 November)
• [whatwg/dom] Request for a different type of example of abort steps (Issue #1031) (Thursday, 11 November)
• Re: [whatwg/webidl] ObservableArray without assignment (#1027) (Wednesday, 10 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Wednesday, 10 November)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Tuesday, 9 November)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Tuesday, 9 November)
• [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Monday, 8 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [whatwg/webidl] Web IDL best practices for platform object construction/initialization (Issue #1060) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 4 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 4 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 4 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 4 November)
• Re: [whatwg/webidl] Use [=tuple=] instead of [=pair=] (PR #1058) (Tuesday, 2 November)
• Re: [whatwg/webidl] Deploy failure (Issue #1057) (Tuesday, 2 November)
• Re: [whatwg/webidl] Use [=tuple=] instead of [=pair=] (PR #1058) (Tuesday, 2 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Monday, 1 November)

Dominick Ng

• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Thursday, 25 November)
• Re: [w3c/manifest] Example suggests that `icons` `sizes` mean a minimum size, but normative text doesn't support that (#925) (Thursday, 11 November)

Dominique Hazael-Massieux

• Re: [whatwg/streams] Should there be dedicated VideoFrame ReadableStream/WritableStream constructs (Issue #1187) (Thursday, 18 November)

dpuga1

• [whatwg/fetch] If the fetch can actually be null, then this bit is fragile. (Issue #1348) (Tuesday, 2 November)

dubiousjim

• Re: [whatwg/streams] Fix readable/writable file stream examples (PR #1191) (Sunday, 28 November)
• [whatwg/streams] Fix readable/writable file stream examples (PR #1191) (Sunday, 28 November)

Edgar Chen

• Re: [whatwg/webidl] MGB-web-ID (Issue #1065) (Tuesday, 16 November)
• Re: [whatwg/webidl] owner (Issue #1062) (Monday, 8 November)
• Re: [whatwg/webidl] Bugged (Issue #1056) (Tuesday, 2 November)
• Re: [whatwg/webidl] Exposing an interface "on all globals" (#468) (Tuesday, 2 November)
• Re: [whatwg/webidl] Add [Exposed=*] to expose on all globals (#526) (Tuesday, 2 November)
• Re: [whatwg/webidl] Add [Exposed=*] to expose on all globals (#526) (Monday, 1 November)

Emilio Cobos Álvarez

• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Monday, 29 November)

Erik Jensen

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

ExE Boss

• Re: [whatwg/webidl] Normative: Rename integer types to match ECMAScript typed arrays (#1030) (Tuesday, 9 November)
• Re: [whatwg/webidl] Normative source of truth for extended attribute applicability and constraints (#1045) (Monday, 8 November)
• Re: [whatwg/webidl] Normative: Rename integer types to match ECMAScript typed arrays (#1030) (Monday, 8 November)
• Re: [whatwg/webidl] Normative: Rename integer types to match ECMAScript typed arrays (#1030) (Sunday, 7 November)

Francois Marier

• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Wednesday, 24 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Tuesday, 23 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Saturday, 20 November)
• Re: [whatwg/fetch] Send "null" Origin headers on cross-origin requests from an RFC7686 address (Issue #1350) (Thursday, 18 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Wednesday, 10 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Wednesday, 10 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Wednesday, 10 November)
• Re: [whatwg/fetch] Send "null" Origin headers on cross-origin requests from an RFC7686 address (Issue #1350) (Wednesday, 10 November)
• Re: [whatwg/fetch] Send "null" Origin headers on cross-origin requests from an RFC7686 address (Issue #1350) (Wednesday, 10 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Wednesday, 10 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Wednesday, 10 November)
• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Wednesday, 10 November)
• [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Tuesday, 9 November)
• [whatwg/fetch] Send "null" Origin headers on cross-origin requests from an RFC7686 address (Issue #1350) (Tuesday, 9 November)
• [whatwg/fetch] Bikeshed returns an error on main branch (Issue #1349) (Tuesday, 9 November)

François Daoust

• [w3c/ServiceWorker] Update Page Visibility refs and IDL (Issue #1616) (Wednesday, 10 November)

Fuqiao Xue

• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Friday, 19 November)
• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Wednesday, 10 November)
• Re: [w3c/editing] EditContext: update the Canvas example and fix video link in the Explainer (PR #361) (Wednesday, 10 November)
• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Wednesday, 10 November)
• Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968) (Wednesday, 10 November)

Gary Kacmarcik

• Re: [w3c/uievents-key] Key mapping specification for Mac JIS Kana / Eisu, Windows ImeOn / ImeOff, Android KANA (virtual) keys (Issue #55) (Friday, 19 November)

Gil Pedersen

• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 28 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Friday, 26 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 21 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 21 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 21 November)

github-actions[bot]

• Re: [w3c/pointerlock] Tidied up document using tidy-html5 (PR #77) (Wednesday, 17 November)
• Re: [w3c/pointerlock] Tidied up document using tidy-html5 (PR #77) (Wednesday, 17 November)
• Re: [w3c/pointerlock] chore(tidy): tidy up document (PR #77) (Wednesday, 17 November)
• Re: [w3c/pointerlock] chore(tidy): tidy up document (PR #77) (Tuesday, 16 November)
• [w3c/pointerlock] chore(tidy): tidy up document (PR #77) (Monday, 15 November)

gopakumarce

• Re: [w3c/ServiceWorker] Implementations are missing navigator.serviceWorker in workers (#1552) (Monday, 29 November)
• Re: [w3c/ServiceWorker] Implementations are missing navigator.serviceWorker in workers (#1552) (Monday, 29 November)

greg9762

• Re: [whatwg/xhr] Clarify allowed behavior when response is "too big" to "fit" in memory/on disk? (#244) (Saturday, 20 November)

gsittyz

• [w3c/uievents-key] Key specification for Mac JIS Kana / Eisu, Windows ImeOn / ImeOff, Android KANA (virtual) keys (Issue #55) (Wednesday, 3 November)

Hadley Beeman

• Re: [w3ctag/design-reviews] Distributed Tracing WG: Baggage specification (#650) (Monday, 15 November)
• Re: [w3ctag/design-reviews] WebAuthn minPinLength (Issue #687) (Wednesday, 10 November)

Heang pov

• [whatwg/webidl] HeangpovMoney (Issue #1067) (Tuesday, 23 November)

Hiroki Nakagawa

• Re: [w3ctag/design-reviews] Same-origin prerendering triggered by speculationrules (#667) (Monday, 29 November)
• Re: [w3ctag/design-reviews] Same-origin prerendering triggered by speculationrules (#667) (Wednesday, 24 November)

hober

• Re: [w3ctag/design-reviews] Early design review of modal close signals/ModalCloseWatcher (#594) (Tuesday, 16 November)
• Re: [w3ctag/design-reviews] Early design review of modal close signals/ModalCloseWatcher (#594) (Tuesday, 16 November)
• Re: [w3ctag/design-reviews] Early design review of modal close signals/ModalCloseWatcher (#594) (Tuesday, 16 November)
• Re: [w3ctag/design-reviews] Scroll-linked Animations (#521) (Monday, 8 November)
• Re: [w3ctag/design-reviews] Trust Token API (#414) (Monday, 8 November)

Ian Clelland

• Re: [w3c/permissions] Editorial: Relationship to the Permissions Policy specification (#264) (Friday, 26 November)

ianbjacobs

• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Monday, 15 November)
• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Monday, 8 November)

Jake Archibald

• Re: [w3c/ServiceWorker] consider using navigation preload response when respondWith() is not called (Issue #1611) (Thursday, 4 November)
• Re: [w3c/ServiceWorker] consider using navigation preload response when respondWith() is not called (Issue #1611) (Thursday, 4 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Tuesday, 2 November)

James Browning

• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Tuesday, 30 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 28 November)
• Re: [whatwg/webidl] Proposal: DOMException.ignoreAborts(promise) (#933) (Tuesday, 23 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Tuesday, 23 November)
• Re: [whatwg/dom] Encourage use of AbortError for cancellation? (#927) (Tuesday, 23 November)

James M Snell

• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Tuesday, 30 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Monday, 29 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 28 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Thursday, 25 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Thursday, 25 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Thursday, 25 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Thursday, 25 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Thursday, 25 November)
• Re: [whatwg/webidl] Constructing DOMException with causes (#969) (Wednesday, 24 November)
• Re: [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Wednesday, 24 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Wednesday, 24 November)
• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Wednesday, 24 November)
• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Tuesday, 16 November)
• [whatwg/streams] ReadableStream.prototype.pipeline(...) (Issue #1184) (Tuesday, 9 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 4 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Thursday, 4 November)
• Re: [whatwg/streams] ReadableStreamBYOBReader.prototype.readFully(view) (#1143) (Monday, 1 November)

Jan-Ivar Bruaroey

• Re: [whatwg/streams] Add a realtime mode to ReadableStream.tee (Issue #1186) (Monday, 22 November)
• Re: [w3ctag/design-reviews] WebTransport review request (#669) (Thursday, 18 November)
• Re: [whatwg/streams] Use abort reason in ReadableStreamPipeTo (PR #1182) (Monday, 15 November)

Jdoe20

• [whatwg/webidl] Intent to use bigint/numeric union (Issue #1063) (Tuesday, 9 November)

Jeevan Shikaram

• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Tuesday, 30 November)

Jeffrey Posnick

• Re: [w3c/ServiceWorker] consider using navigation preload response when respondWith() is not called (Issue #1611) (Wednesday, 3 November)

Jeffrey Yasskin

• Re: [w3c/permissions] Editorial: Add 'getting the current permission state' steps (PR #325) (Monday, 22 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Thursday, 11 November)
• Re: [whatwg/dom] AbortSignal's abort reason downstream integration (Issue #1030) (Wednesday, 10 November)
• Re: [whatwg/dom] Add abort reason to AbortSignal (PR #1027) (Tuesday, 9 November)
• Re: [w3c/permissions] Proposals: Drop "Powerful features registry" and PermissionName enum (Issue #314) (Thursday, 4 November)

Jeremy Roman

• Re: [w3ctag/design-reviews] Same-origin prerendering triggered by speculationrules (#667) (Tuesday, 23 November)

Jikku Jose

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

Jimmy Wärting

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

Joe Eagar

• [w3c/touch-events] 8. Interaction with Mouse Events and click (Issue #110) (Monday, 22 November)

Joey Arhar

• Re: [whatwg/dom] Introduce abortSignal.throwIfAborted() (PR #1034) (Wednesday, 24 November)

Johannes Wilm

• Re: [w3c/editing] Add Nov 12 minutes (PR #363) (Tuesday, 30 November)
• Re: [w3c/editing] Add Nov 12 minutes (PR #363) (Tuesday, 30 November)
• Re: [w3c/editing] Agenda+ shield links now reflect total issue + PR (PR #362) (Friday, 12 November)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Monday, 1 November)

Kagami Sascha Rosylight

• Re: [w3c/WebPlatformWG] Update index.html (PR #130) (Saturday, 13 November)
• Re: [w3c/screen-orientation] Heads up: refs to `pagevisibility` (external now visibile) about to be removed (#205) (Thursday, 11 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Wednesday, 10 November)
• Re: [whatwg/webidl] Normative: Rename integer types to match ECMAScript typed arrays (#1030) (Tuesday, 9 November)
• Re: [whatwg/webidl] Normative: Rename integer types to match ECMAScript typed arrays (#1030) (Sunday, 7 November)
• Re: [whatwg/webidl] Use [=tuple=] instead of [=pair=] (PR #1058) (Tuesday, 2 November)
• [whatwg/webidl] Use [=tuple=] instead of [=pair=] (PR #1058) (Tuesday, 2 November)
• Re: [whatwg/webidl] Deploy failure (Issue #1057) (Tuesday, 2 November)
• [whatwg/webidl] Deploy failure (Issue #1057) (Tuesday, 2 November)

Karl

• Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674) (Monday, 29 November)
• Re: [whatwg/url] Setters can cause failure to roundtrip (#651) (Monday, 22 November)
• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Thursday, 18 November)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Friday, 12 November)
• Re: [whatwg/url] Encode ^ in pathname (#607) (Friday, 12 November)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Friday, 12 November)

Kenneth Rohde Christiansen

• Re: [w3ctag/design-reviews] Distributed Tracing WG: Baggage specification (#650) (Monday, 15 November)
• Re: [w3c/manifest] Icon purpose "splashscreen" and splashscreen text (#844) (Friday, 12 November)
• Re: [w3ctag/design-reviews] Foldable Device CSS Primitives (Issue #690) (Thursday, 11 November)
• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Thursday, 11 November)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Monday, 8 November)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Monday, 8 November)

Kenton Varda

• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Thursday, 4 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 4 November)

Kershaw

• Re: [whatwg/fetch] Send "null" Origin header on cross-origin .onion requests (PR #1351) (Wednesday, 24 November)

krgovind

• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Thursday, 18 November)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Thursday, 18 November)

Lea Verou

• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Monday, 22 November)
• Re: [w3ctag/design-reviews] HTMLInputElement showPicker() (Issue #688) (Tuesday, 9 November)

loubrett

• Re: [w3c/manifest] Add optional `translations` member (#676) (Wednesday, 3 November)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Wednesday, 3 November)

Louise Brett

• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Thursday, 4 November)

Luca Casonato

• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 4 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Thursday, 4 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 4 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Thursday, 4 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 4 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Thursday, 4 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Monday, 1 November)

Maciej Stachowiak

• Re: [whatwg/webidl] ObservableArray without assignment (#1027) (Tuesday, 9 November)

mandie0532

• [whatwg/webidl] What is this (Issue #1064) (Saturday, 13 November)

Marcel Pursche

• [whatwg/fetch] Missing interface for uncompressed Content-Length when compression is used (Issue #1358) (Wednesday, 17 November)

Marcos Cáceres

• Re: [w3c/permissions] Direct Connection Permission (#196) (Thursday, 25 November)
• Re: [w3c/permissions] Direct Connection Permission (#196) (Thursday, 25 November)
• Re: [w3c/permissions] Ensure "persistent-storage" is integrated into parent spec (Issue #329) (Wednesday, 24 November)
• Re: [w3c/permissions] Editorial: relocate "persistent-storage" powerful feature (PR #333) (Wednesday, 24 November)
• Re: [w3c/permissions] Editorial: relocate "persistent-storage" powerful feature (PR #333) (Wednesday, 24 November)
• [w3c/permissions] Interaction between browser and system permissions (Issue #332) (Tuesday, 23 November)
• Re: [w3c/permissions] Permission lifetimes (#233) (Tuesday, 23 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Tuesday, 23 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Tuesday, 23 November)
• Re: [w3c/permissions] Editorial: link <a>express permission</a> inside <a>request permission to use</a>. (PR #331) (Tuesday, 23 November)
• Re: [w3c/permissions] Editorial: Add 'getting the current permission state' steps (PR #325) (Tuesday, 23 November)
• Re: [w3c/push-api] base64 (#280) (Tuesday, 23 November)
• Re: [w3c/permissions] Ensure "xr-spatial-tracking" is integrated into parent spec (Issue #330) (Monday, 22 November)
• Re: [w3c/permissions] Ensure "xr-spatial-tracking" is integrated into parent spec (Issue #330) (Monday, 22 November)
• Re: [w3c/permissions] Ensure "accelerometer" is integrated into parent spec (#296) (Monday, 22 November)
• Re: [w3c/permissions] Remove the allowed in non-secure contexts flag (PR #327) (Sunday, 21 November)
• Re: [w3c/permissions] Can we drop the allowed in non-secure contexts flag? (Issue #315) (Sunday, 21 November)
• Re: [w3c/permissions] Remove the allowed in non-secure contexts flag (PR #327) (Sunday, 21 November)
• Re: [w3c/permissions] Remove the allowed in non-secure contexts flag (PR #327) (Sunday, 21 November)
• Re: [w3c/permissions] Editorial: Relocate "camera", "microphone", "notifications", "speaker-selection". (PR #324) (Friday, 19 November)
• Re: [w3c/permissions] Editorial: Relocate "camera", "microphone", "notifications", "speaker-selection". (PR #324) (Friday, 19 November)
• [w3c/permissions] Editorial: Add 'getting the current permission state' steps (PR #325) (Friday, 19 November)
• [whatwg/webidl] IDL-level support for permission checks? (Issue #1066) (Thursday, 18 November)
• Re: [w3c/uievents-key] Status report and planning for TPAC 2021 (#54) (Thursday, 18 November)
• Re: [w3c/uievents-key] Key mapping specification for Mac JIS Kana / Eisu, Windows ImeOn / ImeOff, Android KANA (virtual) keys (Issue #55) (Thursday, 18 November)
• Re: [w3c/uievents-key] Implementation report (#45) (Thursday, 18 November)
• Re: [w3c/uievents-key] Implementation report (#45) (Thursday, 18 November)
• Re: [w3c/uievents-code] Needs clearer definition of virtual keyboard's KeyboardEvent.code value if it doesn't emulate physical key event completely (#2) (Thursday, 18 November)
• Re: [w3c/uievents-code] Status report and planning for TPAC 2021 (#31) (Thursday, 18 November)
• Re: [w3c/uievents-code] Need an implementation report (#20) (Thursday, 18 November)
• Re: [w3c/uievents-code] Need an implementation report (#20) (Thursday, 18 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Thursday, 18 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Thursday, 18 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Thursday, 18 November)
• Re: [w3c/pointerlock] Update the Acknowledgments section (PR #78) (Wednesday, 17 November)
• Re: [w3c/pointerlock] chore(tidy): tidy up document (PR #77) (Wednesday, 17 November)
• Re: [w3c/pointerlock] Update the Acknowledgments section (PR #78) (Tuesday, 16 November)
• Re: [w3c/gamepad] getGamepad() check if doc is fully active (PR #157) (Tuesday, 16 November)
• Re: [w3c/permissions] Editorial: relocate background-sync and bluetooth (PR #318) (Monday, 15 November)
• Re: [w3c/permissions] Editorial: relocate background-sync and bluetooth (PR #318) (Monday, 15 November)
• [w3c/gamepad] getGamepad() check if doc is fully active (PR #157) (Monday, 15 November)
• Re: [w3c/WebPlatformWG] Update index.html (PR #130) (Sunday, 14 November)
• Re: [w3c/WebPlatformWG] Update index.html (PR #130) (Sunday, 14 November)
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Friday, 12 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Friday, 12 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Friday, 12 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Friday, 12 November)
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Friday, 12 November)
• Re: [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Friday, 12 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Thursday, 11 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Thursday, 11 November)
• Re: [w3c/permissions] Ensure "bluetooth" is integrated into Web Bluetooth spec (Issue #317) (Thursday, 11 November)
• Re: [w3c/permissions] Ensure "bluetooth" is integrated into Web Bluetooth spec (Issue #317) (Thursday, 11 November)
• Re: [w3c/permissions] Proposals: Drop "Powerful features registry" and PermissionName enum (Issue #314) (Wednesday, 10 November)
• Re: [w3c/permissions] Relocate screen-capture (PR #312) (Monday, 8 November)
• Re: [w3c/permissions] Editorial: relocate midi & ambient-light-sensor powerful features (PR #316) (Monday, 8 November)
• Re: [w3c/permissions] Editorial: relocate midi & ambient-light-sensor powerful features (PR #316) (Monday, 8 November)
• Re: [w3c/permissions] Editorial: relocate midi & ambient-light-sensor powerful features (PR #316) (Monday, 8 November)
• Re: [w3c/permissions] Editorial: relocate midi & ambient-light-sensor powerful features (PR #316) (Monday, 8 November)
• Re: [w3c/permissions] Can we drop the allowed in non-secure contexts flag? (Issue #315) (Monday, 8 November)
• Re: [w3c/manifest] Add a manifest option for the declaration of the web application running pattern (Issue #1019) (Monday, 8 November)
• Re: [w3c/manifest] Add a manifest option for the declaration of the web application running pattern (Issue #1019) (Monday, 8 November)
• Re: [w3c/permissions] Proposals: Drop "Powerful features registry" and PermissionName enum (Issue #314) (Thursday, 4 November)
• [w3c/permissions] Proposals: Drop "Powerful features registry" and PermissionName enum (Issue #314) (Thursday, 4 November)
• [w3c/permissions] Editorial: relocate PermissionName/push definition (PR #313) (Thursday, 4 November)
• [w3c/permissions] Relocate screen-capture (PR #312) (Thursday, 4 November)
• [w3c/permissions] Editorial: soft identify geolocation powerful feature (PR #311) (Thursday, 4 November)
• Re: [w3c/push-api] Status report and planning for TPAC 2021 (#336) (Thursday, 4 November)
• Re: [w3c/manifest] editorial: Making URL processing DRY (PR #1018) (Thursday, 4 November)
• Re: [w3c/permissions] Remove ambient-light-sensor details defined in [[ambient-light]] (PR #310) (Thursday, 4 November)

mark blackburn

• [whatwg/fetch] 908801137916915773 (Issue #1355) (Friday, 12 November)

Mark Nottingham

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

Masayuki Nakano

• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Wednesday, 17 November)

Mason Freed

• [w3ctag/design-reviews] "FYI" Review of new window.open() behavior (Issue #691) (Friday, 19 November)
• Re: [whatwg/dom] Symbols should be allowed as Event types. (#331) (Wednesday, 17 November)
• Re: [whatwg/dom] Symbols should be allowed as Event types. (#331) (Thursday, 11 November)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 11 November)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 11 November)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Saturday, 6 November)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Friday, 5 November)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Friday, 5 November)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Friday, 5 November)

Matt Giuca

• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Friday, 26 November)
• [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Thursday, 25 November)
• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Thursday, 25 November)
• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Thursday, 25 November)
• Re: [w3c/manifest] Add a way to query whether there is a UA-provided back button (#693) (Monday, 1 November)
• Re: [w3c/manifest] Add a way to query whether there is a UA-provided back button (#693) (Monday, 1 November)

Matt Reynolds

• [w3c/gamepad] Change default allowlist to 'all' (PR #156) (Thursday, 11 November)

Mattias Buelens

• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Tuesday, 30 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Tuesday, 30 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Tuesday, 30 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Tuesday, 30 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Tuesday, 30 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Tuesday, 30 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Tuesday, 30 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Monday, 29 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Monday, 29 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Monday, 29 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Monday, 29 November)
• Re: [whatwg/streams] Fix readable/writable file stream examples (PR #1191) (Monday, 29 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• Re: [whatwg/streams] Fix readable/writable file stream examples (PR #1191) (Sunday, 28 November)
• Re: [whatwg/streams] Fix readable/writable file stream examples (PR #1191) (Sunday, 28 November)
• Re: [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Thursday, 25 November)
• [whatwg/streams] Add WritableStreamDefaultController.releaseBackpressure() (PR #1190) (Thursday, 25 November)
• Re: [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• Re: [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• Re: [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• Re: [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• Re: [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• Re: [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• Re: [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• [whatwg/streams] Roll WPT for abort reason (PR #1189) (Wednesday, 24 November)
• Re: [whatwg/streams] ReadableStreamBYOBReader.prototype.readFully(view) (#1143) (Tuesday, 23 November)
• Re: [whatwg/webidl] Proposal: DOMException.ignoreAborts(promise) (#933) (Tuesday, 23 November)
• Re: [whatwg/streams] Add a realtime mode to ReadableStream.tee (Issue #1186) (Monday, 22 November)
• Re: [whatwg/streams] Should there be dedicated VideoFrame ReadableStream/WritableStream constructs (Issue #1187) (Thursday, 18 November)
• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Wednesday, 17 November)
• Re: [whatwg/streams] Add a realtime mode to ReadableStream.tee (Issue #1186) (Tuesday, 16 November)
• Re: [whatwg/streams] Transferable streams: the double transfer problem (#1063) (Tuesday, 16 November)
• Re: [whatwg/streams] Use abort reason in ReadableStreamPipeTo (PR #1182) (Friday, 12 November)
• Re: [whatwg/streams] Use abort reason in ReadableStreamPipeTo (PR #1182) (Friday, 12 November)
• Re: [whatwg/streams] ReadableStream.prototype.pipeline(...) (Issue #1184) (Tuesday, 9 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Monday, 1 November)

mbrodesser

• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 29 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 15 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 15 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 15 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 15 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 15 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 11 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Wednesday, 10 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Tuesday, 9 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Tuesday, 9 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Tuesday, 9 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 8 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 8 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 8 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Friday, 5 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 1 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 1 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 1 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 1 November)

Mgendy

• [whatwg/webidl] MGB-web-ID (Issue #1065) (Tuesday, 16 November)

Michael Osipov

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

Mike Taylor

• [w3c/permissions] Editorial: relocate "background-fetch", "display-capture", "xr" (PR #334) (Monday, 29 November)
• Re: [w3c/permissions] Ensure "background-fetch" permission is integrated in Background Sync spec (#295) (Monday, 29 November)
• Re: [w3c/permissions] Ensure "background-fetch" permission is integrated in Background Sync spec (#295) (Monday, 29 November)
• Re: [w3c/permissions] Ensure "display-capture" is integrated into Screen Capture API spec (Issue #322) (Monday, 29 November)
• Re: [whatwg/storage] Update Persistence permission section (Issue #128) (Monday, 29 November)
• Re: [whatwg/storage] Update Persistence permission section (Issue #128) (Monday, 29 November)
• [whatwg/storage] Editorial: fix {{PermissionState/granted}} enum value quotes (PR #130) (Wednesday, 24 November)
• Re: [whatwg/storage] Update Persistence permission section (Issue #128) (Wednesday, 24 November)
• Re: [w3c/permissions] Ensure "persistent-storage" is integrated into parent spec (Issue #329) (Wednesday, 24 November)
• Re: [w3c/permissions] Ensure "persistent-storage" is integrated into parent spec (Issue #329) (Wednesday, 24 November)
• Re: [whatwg/dom] AbortSignal's abort reason downstream integration (Issue #1030) (Wednesday, 24 November)
• [w3c/permissions] Editorial: relocate "persistent-storage" powerful feature (PR #333) (Tuesday, 23 November)
• Re: [w3c/permissions] Ensure "persistent-storage" is integrated into parent spec (Issue #329) (Tuesday, 23 November)
• [whatwg/storage] Editorial: Minor Permissions-related edits (PR #129) (Tuesday, 23 November)
• [whatwg/storage] Update Persistence permission section (Issue #128) (Tuesday, 23 November)
• Re: [w3c/permissions] Editorial: link <a>express permission</a> inside <a>request permission to use</a>. (PR #331) (Tuesday, 23 November)
• [w3c/permissions] Editorial: link <a>express permission</a> inside <a>request permission to use</a>. (PR #331) (Monday, 22 November)
• Re: [w3c/permissions] Ensure "xr-spatial-tracking" is integrated into parent spec (Issue #330) (Friday, 19 November)
• Re: [w3c/permissions] "persistent-storage", (Issue #329) (Friday, 19 November)
• Re: [w3c/permissions] Ensure "nfc" is integrated into parent spec (Issue #328) (Friday, 19 November)
• [w3c/permissions] "xr-spatial-tracking", (Issue #330) (Friday, 19 November)
• [w3c/permissions] "persistent-storage", (Issue #329) (Friday, 19 November)
• [w3c/permissions] "nfc", (Issue #328) (Friday, 19 November)
• [w3c/permissions] Remove the allowed in non-secure contexts flag (PR #327) (Friday, 19 November)
• Re: [w3c/permissions] Ensure "accelerometer" is integrated into parent spec (#296) (Friday, 19 November)
• Re: [w3c/permissions] Ensure "accelerometer" is integrated into parent spec (#296) (Friday, 19 November)
• Re: [w3c/permissions] Ensure "magnetometer" is integrated into parent spec (Issue #326) (Friday, 19 November)
• [w3c/permissions] "magnetometer", (Issue #326) (Friday, 19 November)
• Re: [w3c/permissions] Ensure "gyroscope" is integrated into Gyroscope API (Issue #321) (Friday, 19 November)
• Re: [w3c/permissions] Editorial: Add 'getting the current permission state' steps (PR #325) (Friday, 19 November)
• Re: [w3c/permissions] Editorial: Add 'getting the current permission state' steps (PR #325) (Friday, 19 November)
• Re: [w3c/permissions] Editorial: Relocate "camera", "microphone", "notifications", "speaker-selection". (PR #324) (Thursday, 18 November)
• Re: [w3c/permissions] Editorial: Relocate "bluetooth", "camera", "microphone", "notifications", "speaker-selection". (PR #324) (Thursday, 18 November)
• Re: [w3c/permissions] Editorial: Relocate "bluetooth", "camera", "microphone", "notifications", "speaker-selection". (PR #324) (Thursday, 18 November)
• Re: [w3c/permissions] Editorial: Relocate "bluetooth", "camera", "microphone", "notifications", "speaker-selection". (PR #324) (Thursday, 18 November)
• [w3c/permissions] Editorial: Relocate "bluetooth", "camera", "microphone", "notifications", "speaker-selection". (PR #324) (Thursday, 18 November)
• Re: [w3c/permissions] Ensure "camera" & "microphone" are defined in their parent spec (Issue #323) (Thursday, 18 November)
• [w3c/permissions] Ensure "camera" & "microphone" are defined in their parent spec (Issue #323) (Thursday, 18 November)
• Re: [w3c/permissions] Ensure "display-capture" is integrated into Screen Capture API spec (Issue #322) (Tuesday, 16 November)
• Re: [w3c/permissions] Ensure "display-capture" is integrated into Screen Capture API spec (Issue #322) (Monday, 15 November)
• Re: [w3c/permissions] Ensure "screen-capture" is integrated into Screen Capture API spec (Issue #322) (Monday, 15 November)
• [w3c/permissions] "screen-capture" (Issue #322) (Monday, 15 November)
• Re: [w3c/permissions] "gyroscope", (Issue #321) (Monday, 15 November)
• [w3c/permissions] "gyroscope", (Issue #321) (Monday, 15 November)
• Re: [w3c/permissions] Can we drop the allowed in non-secure contexts flag? (Issue #315) (Monday, 15 November)
• Re: [w3c/permissions] Ensure "notifications" permission is properly integrated into parent spec (#291) (Monday, 15 November)
• Re: [w3c/permissions] Ensure "notifications" permission is properly integrated into parent spec (#291) (Monday, 15 November)
• Re: [whatwg/dom] AbortSignal's abort reason downstream integration (Issue #1030) (Monday, 15 November)
• [w3c/permissions] "speaker-selection" (Issue #320) (Saturday, 13 November)
• Re: [w3c/permissions] Ensure "screen-wake-lock" permission is integrated in Screen Wake Lock API (Issue #319) (Saturday, 13 November)
• [w3c/permissions] "screen-wake-lock", (Issue #319) (Saturday, 13 November)
• Re: [w3c/permissions] Ensure "background-sync" is integrated into Web Background Synchronization spec (Issue #308) (Saturday, 13 November)
• Re: [w3c/permissions] Ensure "background-sync" is integrated into Web Background Synchronization spec (Issue #308) (Saturday, 13 November)
• Re: [w3c/permissions] Ensure "bluetooth" is integrated into Web Bluetooth spec (Issue #317) (Saturday, 13 November)
• Re: [w3c/permissions] Ensure "bluetooth" is integrated into Web Bluetooth spec (Issue #317) (Saturday, 13 November)
• Re: [w3c/permissions] Define permission lifetimes (#287) (Friday, 12 November)
• [w3c/permissions] Editorial: relocate background-sync and bluetooth (PR #318) (Friday, 12 November)
• Re: [w3c/permissions] Ensure "bluetooth" is integrated into Web Bluetooth spec (Issue #317) (Friday, 12 November)
• Re: [w3c/permissions] Ensure "bluetooth" is integrated into Web Bluetooth spec (Issue #317) (Thursday, 11 November)
• [w3c/permissions] "bluetooth", (Issue #317) (Thursday, 11 November)
• Re: [w3c/permissions] Editorial: relocate midi & ambient-light-sensor powerful features (PR #316) (Monday, 8 November)
• [w3c/permissions] Editorial: relocate midi & ambient-light-sensor powerful features (PR #316) (Monday, 8 November)
• Re: [w3c/permissions] Ensure "background-sync" is integrated into Web Background Synchronization spec (Issue #308) (Monday, 8 November)
• Re: [w3c/permissions] Proposals: Drop "Powerful features registry" and PermissionName enum (Issue #314) (Monday, 8 November)
• [w3c/permissions] Can we drop the allowed in non-secure contexts flag? (Issue #315) (Friday, 5 November)
• Re: [w3c/permissions] Editorial: relocate PermissionName/push definition (PR #313) (Thursday, 4 November)
• Re: [w3c/permissions] Editorial: relocate PermissionName/push definition (PR #313) (Thursday, 4 November)
• Re: [w3c/permissions] Editorial: relocate PermissionName/push definition (PR #313) (Thursday, 4 November)
• Re: [w3c/permissions] Ensure "ambient-light-sensor" is integrated into Ambient Light Sensor spec (Issue #307) (Thursday, 4 November)
• Re: [w3c/permissions] Ensure "ambient-light-sensor" is integrated into Ambient Light Sensor spec (Issue #307) (Thursday, 4 November)
• Re: [w3c/permissions] Editorial: soft identify geolocation powerful feature (PR #311) (Thursday, 4 November)
• Re: [w3c/permissions] Editorial: soft identify geolocation powerful feature (PR #311) (Thursday, 4 November)
• Re: [w3c/permissions] Remove extra "ambient-light-sensor" bits (Issue #309) (Thursday, 4 November)
• Re: [w3c/permissions] Remove ambient-light-sensor details defined in [[ambient-light]] (PR #310) (Thursday, 4 November)
• Re: [w3c/permissions] Remove ambient-light-sensor details defined in [[ambient-light]] (PR #310) (Thursday, 4 November)
• Re: [w3c/permissions] Relocate screen-capture (PR #312) (Thursday, 4 November)
• [w3c/permissions] Remove ambient-light-sensor details defined in [[ambient-light]] (PR #310) (Thursday, 4 November)
• Re: [w3c/permissions] Ensure "ambient-light-sensor" is integrated into Ambient Light Sensor spec (Issue #307) (Thursday, 4 November)
• [w3c/permissions] Remove "ambient-light-sensor" bits (Issue #309) (Thursday, 4 November)
• [w3c/permissions] "background-sync", (Issue #308) (Monday, 1 November)
• [w3c/permissions] Ensure "ambient-light-sensor" is integrated into Ambient Light Sensor spec (Issue #307) (Monday, 1 November)
• Re: [w3c/permissions] Ensure "midi" permission is integrated in Web Midi API spec (#294) (Monday, 1 November)
• Re: [w3c/permissions] Ensure "midi" permission is integrated in Web Midi API spec (#294) (Monday, 1 November)

Mike West

• Re: [whatwg/fetch] Send "null" Origin headers on cross-origin requests from an RFC7686 address (Issue #1350) (Wednesday, 10 November)

mondjunge

• Re: [w3c/push-api] A subscription with a different application server key already exists. (#296) (Monday, 22 November)

Ms2ger

• Re: [whatwg/webidl] Add [Exposed=*] to expose on all globals (#526) (Tuesday, 2 November)

Mustaq Ahmed

• Re: [w3c/pointerlock] Update the Acknowledgments section (PR #78) (Tuesday, 16 November)
• Re: [w3c/pointerlock] Update the Acknowledgments section (PR #78) (Tuesday, 16 November)
• Re: [w3c/pointerlock] Update the Acknowledgments section (PR #78) (Tuesday, 16 November)
• Re: [w3c/pointerlock] Update the Acknowledgments section (PR #78) (Tuesday, 16 November)
• [w3c/pointerlock] Update the list of acknowledgments (PR #78) (Monday, 15 November)
• Re: [w3c/pointerlock] Don't monkey patch HTML's list of activation triggering input event (#70) (Monday, 15 November)
• Re: [w3c/pointerlock] Remove redundant user activation text from PointerLock spec. (PR #76) (Monday, 15 November)
• Re: [w3c/pointerlock] Remove redundant user activation text from PointerLock spec. (PR #76) (Monday, 15 November)
• Re: [w3c/pointerlock] Remove redundant user activation text from PointerLock spec. (PR #76) (Monday, 15 November)
• Re: [w3c/pointerlock] Remove redundant user activation text from PointerLock spec. (PR #76) (Monday, 15 November)
• Re: [w3c/pointerlock] Remove redundant user activation text from PointerLock spec. (PR #76) (Monday, 15 November)
• Re: [w3c/pointerlock] Remove redundant user activation text from PointerLock spec. (PR #76) (Tuesday, 9 November)
• Re: [w3c/pointerlock] Remove redundant user activation text from PointerLock spec. (PR #76) (Friday, 5 November)
• Re: [w3c/pointerlock] Remove redundant user activation text from PointerLock spec. (PR #76) (Friday, 5 November)
• Re: [w3c/pointerlock] Remove redundant user activation text from PointerLock spec. (PR #76) (Friday, 5 November)
• [w3c/pointerlock] Remove redundant user activation text from PointerLock spec. (PR #76) (Friday, 5 November)
• Re: [w3c/pointerlock] Status report and planning for TPAC 2021 (#75) (Monday, 1 November)

Myridium

• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Sunday, 21 November)

needLovemow70

• [whatwg/webidl] owner (Issue #1062) (Monday, 8 November)

Nicholas Gulachek

• Re: [whatwg/xhr] Why do we need to remove synchronous XHR? (Issue #336) (Tuesday, 2 November)
• Re: [whatwg/xhr] Why do we need to remove synchronous XHR? (Issue #336) (Tuesday, 2 November)
• [whatwg/xhr] Why do we need to remove synchronous XHR? (Issue #336) (Monday, 1 November)

Nicolas Gouwy

• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Wednesday, 24 November)

Nidhi Jaju

• Re: [whatwg/streams] Use abort reason in ReadableStreamPipeTo (PR #1182) (Friday, 19 November)
• Re: [whatwg/streams] Use abort reason in ReadableStreamPipeTo (PR #1182) (Tuesday, 9 November)
• Re: [whatwg/dom] Add abort reason to AbortSignal (PR #1027) (Tuesday, 9 November)
• Re: [whatwg/dom] Add abort reason to AbortSignal (PR #1027) (Monday, 8 November)
• Re: [whatwg/dom] Add abort reason to AbortSignal (PR #1027) (Thursday, 4 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Monday, 1 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Monday, 1 November)
• Re: [whatwg/streams] Use abort reason in ReadableStreamPipeTo (PR #1182) (Monday, 1 November)

Nifzz1

• [whatwg/webidl] Nifz (Issue #1061) (Sunday, 7 November)

NilsBaumgartner1994

• Re: [whatwg/fetch] Fetch not sending cookies ? SameSite=none Secure credentials include cors (Issue #1354) (Friday, 12 November)
• [whatwg/fetch] Fetch not sending cookies ? SameSite=none Secure credentials include cors (Issue #1354) (Friday, 12 November)

Nina Satragno

• [w3ctag/design-reviews] Credential Management: Conditional Mediation (Issue #692) (Thursday, 25 November)
• Re: [whatwg/dom] AbortSignal's abort reason downstream integration (Issue #1030) (Monday, 22 November)

Noam Rosenthal

• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 29 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• [w3c/ServiceWorker] Define the time origin for service workers (PR #1621) (Wednesday, 24 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 22 November)
• Re: [whatwg/fetch] Time origin adjustment for navigation (Issue #1359) (Monday, 22 November)
• Re: [whatwg/fetch] Time origin adjustment for navigation (Issue #1359) (Monday, 22 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 22 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 22 November)
• [whatwg/fetch] Time origin adjustment for navigation (Issue #1359) (Sunday, 21 November)
• Re: [w3c/ServiceWorker] Pass controller from fetch, and abort SW fetch when it's canceled (PR #1620) (Friday, 19 November)
• Re: [w3c/ServiceWorker] Pass controller from fetch, and abort SW fetch when it's canceled (PR #1620) (Friday, 19 November)
• Re: [w3c/ServiceWorker] Pass controller from fetch, and abort SW fetch when it's canceled (PR #1620) (Friday, 19 November)
• Re: [w3c/ServiceWorker] Pass controller from fetch, and abort SW fetch when it's canceled (PR #1620) (Friday, 19 November)
• Re: [w3c/ServiceWorker] Pass controller from fetch, and abort SW fetch when it's canceled (PR #1620) (Friday, 19 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Friday, 19 November)
• [w3c/ServiceWorker] Pass controller from fetch, and abort SW fetch when it's canceled (PR #1620) (Friday, 19 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Friday, 19 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Friday, 19 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Friday, 19 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Thursday, 18 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Wednesday, 17 November)
• Re: [w3c/ServiceWorker] Specify how "terminate" works (PR #1612) (Wednesday, 17 November)
• Re: [w3c/ServiceWorker] Specify how "terminate" works (PR #1612) (Wednesday, 17 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Tuesday, 16 November)
• Re: [w3c/ServiceWorker] Specify how "terminate" works (PR #1612) (Tuesday, 16 November)
• Re: [w3c/ServiceWorker] Specify how "terminate" works (PR #1612) (Tuesday, 16 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Tuesday, 16 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Saturday, 13 November)
• Re: [w3c/screen-orientation] Heads up: refs to `pagevisibility` (external now visibile) about to be removed (#205) (Friday, 12 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Wednesday, 10 November)
• [whatwg/fetch] Editorial: Add myself to acknowledgements list after several contributions (PR #1352) (Tuesday, 9 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Tuesday, 9 November)
• Re: [w3c/ServiceWorker] Specify how "terminate" works (PR #1612) (Monday, 8 November)
• Re: [w3c/ServiceWorker] Specify how "terminate" works (PR #1612) (Monday, 8 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 8 November)
• [w3c/ServiceWorker] Specify how "terminate" works (PR #1612) (Monday, 8 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 8 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 8 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 8 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 8 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 8 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 8 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 8 November)
• Re: [whatwg/fetch] When response comes from a worker, some of the timing-info should pass through (#1208) (Monday, 8 November)
• Re: [whatwg/fetch] Expose `transfer size` for resource timing (#1203) (Monday, 8 November)
• Re: [whatwg/fetch] Expose `transfer size` for resource timing (#1203) (Monday, 8 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 8 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 8 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Sunday, 7 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Sunday, 7 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Sunday, 7 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Thursday, 4 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Thursday, 4 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Thursday, 4 November)
• Re: [w3c/screen-orientation] Heads up: refs to `pagevisibility` (external now visibile) about to be removed (#205) (Wednesday, 3 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Wednesday, 3 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Wednesday, 3 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Wednesday, 3 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Tuesday, 2 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Tuesday, 2 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 1 November)
• Re: [whatwg/fetch] Return a "controller" instance from fetch (#1329) (Monday, 1 November)

npm1

• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Wednesday, 10 November)

Patrick H. Lauke

• Re: [w3c/touch-events] 8. Interaction with Mouse Events and click (Issue #110) (Monday, 22 November)
• Re: [w3c/touch-events] 8. Interaction with Mouse Events and click (Issue #110) (Monday, 22 November)

Paul Jensen

• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Tuesday, 16 November)
• Re: [w3ctag/design-reviews] Foldable Device CSS Primitives (Issue #690) (Tuesday, 16 November)

Peter Linss

• Re: [w3ctag/design-reviews] User Preference Media Features Client Hints Headers (#632) (Wednesday, 24 November)
• Re: [w3ctag/design-reviews] User Preference Media Features Client Hints Headers (#632) (Sunday, 21 November)
• Re: [w3ctag/design-reviews] EditContext API (#416) (Wednesday, 17 November)
• Re: [w3ctag/design-reviews] User Preference Media Features Client Hints Headers (#632) (Wednesday, 17 November)
• Re: [w3ctag/design-reviews] Distributed Tracing WG: Baggage specification (#650) (Tuesday, 9 November)
• Re: [w3ctag/design-reviews] Trust Token API (#414) (Monday, 8 November)
• Re: [whatwg/fetch] Specify the behavior of `COEP: credentialless`, (#1229) (Wednesday, 3 November)

Piotr Bialecki

• Re: [w3ctag/design-reviews] WebXR Raw Camera Access API (#652) (Tuesday, 9 November)

Pressure Techs

• [whatwg/webidl] IT (Issue #1059) (Wednesday, 3 November)
• [whatwg/webidl] Bugged (Issue #1056) (Tuesday, 2 November)

prolapza

• [whatwg/dom] securitypolicyviolationโดย (Issue #1035) (Sunday, 28 November)

Qinglin Song

• Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020) (Thursday, 25 November)
• Re: [w3c/manifest] Add a manifest option for the declaration of the web application running pattern (Issue #1019) (Wednesday, 10 November)
• Re: [w3c/manifest] Add a manifest option for the declaration of the web application running pattern (Issue #1019) (Tuesday, 9 November)
• Re: [w3c/manifest] Add a manifest option for the declaration of the web application running pattern (Issue #1019) (Monday, 8 November)

Raphael Kubo da Costa

• Re: [w3c/permissions] Ensure "gyroscope" is integrated into Gyroscope API (Issue #321) (Friday, 19 November)
• [whatwg/webidl] Web IDL best practices for platform object construction/initialization (Issue #1060) (Friday, 5 November)

Reilly Grant

• Re: [w3c/gamepad] getGamepad() check if doc is fully active (PR #157) (Monday, 15 November)

Robert Flack

• Re: [w3ctag/design-reviews] CSS: contain-intrinsic-size: auto, and converting to a shorthand property (#624) (Monday, 1 November)

Robert Nagy

• Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Sunday, 28 November)

robert.edgar

• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Wednesday, 24 November)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Wednesday, 24 November)
• Re: [w3c/ServiceWorker] Spec how extendable events are given time to execute (#1566) (Tuesday, 2 November)

Rossen Atanassov

• Re: [w3ctag/design-reviews] Preserve-parent-color value of forced-color-adjust CSS property (Issue #681) (Wednesday, 10 November)
• Re: [w3ctag/design-reviews] Preserve-parent-color value of forced-color-adjust CSS property (Issue #681) (Wednesday, 10 November)
• Re: [w3ctag/design-reviews] CSS: contain-intrinsic-size: auto, and converting to a shorthand property (#624) (Wednesday, 10 November)
• Re: [w3ctag/design-reviews] CSS: contain-intrinsic-size: auto, and converting to a shorthand property (#624) (Wednesday, 10 November)
• Re: [w3ctag/design-reviews] CSS: contain-intrinsic-size: auto, and converting to a shorthand property (#624) (Monday, 8 November)

Ryosuke Niwa

• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Saturday, 20 November)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Saturday, 20 November)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Thursday, 18 November)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Thursday, 18 November)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Friday, 12 November)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Friday, 5 November)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Friday, 5 November)

Scott Haseley

• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Tuesday, 23 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Friday, 19 November)

Scott Low

• Re: [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Friday, 19 November)
• [w3ctag/design-reviews] Foldable Device CSS Primitives (Issue #690) (Tuesday, 9 November)
• [w3ctag/design-reviews] Viewport Segments Property (Issue #689) (Tuesday, 9 November)

smaug----

• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Sunday, 28 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Thursday, 25 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Wednesday, 24 November)
• Re: [whatwg/dom] Introduce AbortSignal.timeout() (PR #1032) (Wednesday, 24 November)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Tuesday, 23 November)

snianu

• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 29 November)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Monday, 29 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Saturday, 20 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Saturday, 20 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Thursday, 18 November)
• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Thursday, 18 November)
• Re: [w3ctag/design-reviews] EditContext API (#416) (Wednesday, 17 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 16 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 15 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 15 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 15 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Saturday, 13 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 12 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 12 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 12 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 12 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 12 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 12 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 12 November)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Friday, 12 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 11 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 11 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 11 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 10 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Tuesday, 9 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Should we remove `lastModified`, `ClipboardItemDelayedCallback`, `createDelayed` and `delayed`? (#160) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Friday, 5 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 4 November)
• Re: [w3c/editing] Add Pickling API to the clipboard spec. (#340) (Thursday, 4 November)
• Re: [w3c/editing] Add Pickling API to the clipboard spec. (#340) (Thursday, 4 November)
• Re: [w3c/editing] Fix minor issues (PR #360) (Thursday, 4 November)
• Re: [w3c/editing] Fix minor issues (PR #360) (Thursday, 4 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 4 November)
• Re: [w3c/clipboard-apis] Add Pickling API to async clipboard. (PR #162) (Thursday, 4 November)
• Re: [w3c/clipboard-apis] Add Pickling API to async clipboard. (PR #162) (Thursday, 4 November)
• [w3c/clipboard-apis] Add Pickling API to async clipboard. (PR #162) (Thursday, 4 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 3 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 3 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Wednesday, 3 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 3 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 3 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 3 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 2 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 1 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 1 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 1 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 1 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 1 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 1 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 1 November)
• Re: [w3c/clipboard-apis] Should we remove `lastModified`, `ClipboardItemDelayedCallback`, `createDelayed` and `delayed`? (#160) (Monday, 1 November)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 1 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 1 November)

spocke

• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 11 November)
• Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 11 November)

sspi

• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Thursday, 18 November)

Stephen McGruer

• Re: [w3ctag/design-reviews] Secure Payment Confirmation - Part 2 (#675) (Monday, 15 November)

Steven Valdez

• Re: [w3ctag/design-reviews] Trust Token API (#414) (Monday, 22 November)
• Re: [w3ctag/design-reviews] Trust Token API (#414) (Monday, 8 November)

Thomas Allmer

• Re: [w3c/clipboard-apis] Make it possible to read image/svg+xml from the clipboard (#92) (Thursday, 11 November)
• Re: [w3c/clipboard-apis] Make it possible to read image/svg+xml from the clipboard (#92) (Wednesday, 10 November)

Thomas Steiner

• Re: [w3ctag/design-reviews] User Preference Media Features Client Hints Headers (#632) (Tuesday, 23 November)
• Re: [w3ctag/design-reviews] User Preference Media Features Client Hints Headers (#632) (Thursday, 18 November)
• Re: [w3c/clipboard-apis] Make it possible to read image/svg+xml from the clipboard (#92) (Thursday, 11 November)
• Re: [w3c/editing] Fix minor issues (PR #360) (Thursday, 4 November)
• [w3c/editing] Fix minor issues (PR #360) (Thursday, 4 November)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Thursday, 4 November)
• Re: [w3c/clipboard-apis] Add Pickling API to async clipboard. (PR #162) (Thursday, 4 November)
• Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Wednesday, 3 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Tuesday, 2 November)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Monday, 1 November)

Tiger Oakes

• Re: [w3c/manifest] Example suggests that `icons` `sizes` mean a minimum size, but normative text doesn't support that (#925) (Saturday, 6 November)

Timothy Gu

• Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674) (Tuesday, 30 November)
• [whatwg/url] Should we escape \ in non-special non-opaque paths? (Issue #675) (Tuesday, 30 November)
• Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674) (Tuesday, 23 November)
• Re: [whatwg/url] Setters can cause failure to roundtrip (#651) (Tuesday, 23 November)
• Re: [whatwg/url] Setters can cause failure to roundtrip (#651) (Tuesday, 23 November)
• Re: [whatwg/url] Setters can cause failure to roundtrip (#651) (Monday, 22 November)
• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Wednesday, 17 November)
• Re: [whatwg/url] My (Issue #671) (Friday, 12 November)
• Re: [whatwg/webidl] Nifz (Issue #1061) (Sunday, 7 November)
• Re: [whatwg/webidl] Absence of "record" token from Other production (#694) (Sunday, 7 November)
• Re: [whatwg/webidl] Add [Exposed=*] to expose on all globals (#526) (Monday, 1 November)

TinTin Love CL

• [whatwg/url] On (Issue #670) (Thursday, 11 November)

Titouan Rigoudy

• Re: [w3ctag/design-reviews] Private Network Access (aka CORS-RFC1918) (#572) (Friday, 26 November)

Tomasz Jakut

• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Monday, 1 November)

Travis Leithead

• Re: [w3c/editing] Add Nov 12 minutes (PR #363) (Tuesday, 30 November)
• Re: [w3c/editing] EditContext: update the Canvas example and fix video link in the Explainer (PR #361) (Saturday, 13 November)
• Re: [w3c/editing] Agenda+ shield links now reflect total issue + PR (PR #362) (Friday, 12 November)
• [w3c/editing] Add Nov 12 minutes (PR #363) (Friday, 12 November)
• [w3c/editing] Agenda+ shield links now reflect total issue + PR (PR #362) (Friday, 12 November)

unbyte

• [w3c/ServiceWorker] Is it possible to intercept preflight requests from cors requests? (Issue #1610) (Tuesday, 2 November)

Vitali Lovich

• Re: [whatwg/streams] ReadableStreamBYOBReader.prototype.readFully(view) (#1143) (Monday, 1 November)

W3C Bot

• Re: [w3c/pointerlock] chore(tidy): tidy up document (PR #77) (Wednesday, 17 November)

Wenson Hsieh

• Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150) (Thursday, 18 November)

Xiaoqian Wu

• [w3c/uievents-code] Get horizontal review for UIEvents KeyboardEvent Code (Issue #32) (Thursday, 18 November)
• [w3c/uievents-key] Get horizontal review for UIEvents KeyboardEvent Key (Issue #56) (Thursday, 18 November)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Thursday, 4 November)

Yajing Tang

• Re: [w3c/manifest] use url equivalence excluding fragments for id comparison (#1013) (Friday, 5 November)
• Re: [w3c/manifest] use url equivalence excluding fragments for id comparison (#1013) (Friday, 5 November)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Tuesday, 2 November)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Tuesday, 2 November)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Tuesday, 2 November)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Tuesday, 2 November)
• Re: [w3c/manifest] Describe manifest update behavior (#1011) (Tuesday, 2 November)

Yoav Weiss

• Re: [w3ctag/design-reviews] User Preference Media Features Client Hints Headers (#632) (Thursday, 25 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 8 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 8 November)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 8 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 8 November)
• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 8 November)

youennf

• Re: [whatwg/streams] Should there be dedicated VideoFrame ReadableStream/WritableStream constructs (Issue #1187) (Thursday, 18 November)
• Re: [whatwg/streams] Add a realtime mode to ReadableStream.tee (Issue #1186) (Thursday, 18 November)
• [whatwg/streams] Should there be dedicated VideoFrame ReadableStream/WritableStream constructs (Issue #1187) (Tuesday, 16 November)
• [whatwg/streams] Add a realtime mode to ReadableStream.tee (Issue #1186) (Tuesday, 16 November)
• Re: [whatwg/streams] Transferable streams: the double transfer problem (#1063) (Tuesday, 16 November)
• Re: [whatwg/streams] Make the internal queue observable (#1167) (Tuesday, 16 November)
• [whatwg/streams] Life-time management of VideoFrame when used with streams (Issue #1185) (Tuesday, 16 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Friday, 5 November)
• Re: [w3c/ServiceWorker] consider using navigation preload response when respondWith() is not called (Issue #1611) (Thursday, 4 November)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Thursday, 4 November)

Yuriy Kravets

• Re: [WICG/webcomponents] Adding support for ShadowDOM features in SVG (#942) (Monday, 29 November)

Yutaka Hirano

• Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311) (Monday, 29 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Friday, 26 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Friday, 26 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Thursday, 25 November)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Thursday, 25 November)
• Re: [w3ctag/design-reviews] WebTransport review request (#669) (Thursday, 18 November)
• Re: [whatwg/dom] AbortSignal's abort reason downstream integration (Issue #1030) (Wednesday, 10 November)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Thursday, 4 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Thursday, 4 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Tuesday, 2 November)
• Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Tuesday, 2 November)

Yves Lafon

• Re: [w3ctag/design-reviews] Distributed Tracing WG: Baggage specification (#650) (Monday, 15 November)

zbyte-king

• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Saturday, 20 November)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 19 November)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 19 November)

伊撒尔

• [whatwg/streams] cocurrent steam (Issue #1188) (Friday, 19 November)

Last message date: Tuesday, 30 November 2021 22:56:19 UTC