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

0839829821

• [whatwg/fetch] 0839329821 (Issue #1386) (Tuesday, 25 January)

Aaron Gustafson

• Re: [w3c/manifest] Address privacy issue with start_url (PR #1029) (Thursday, 20 January)

Adam Argyle

• [w3ctag/design-reviews] `prefers-reduced-data` CSS Media Query (Issue #705) (Thursday, 6 January)

Adam Rice

• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Thursday, 27 January)
• Re: [whatwg/streams] Specify realm for object creation (Issue #1213) (Tuesday, 25 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Tuesday, 25 January)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { atLeast }) (#1145) (Wednesday, 19 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Thursday, 13 January)

Addison Phillips

• Re: [w3c/push-api] Should there be a UTF-8 health warning? (#335) (Tuesday, 18 January)

Adrian

• Re: [WICG/webcomponents] [idea] HTML Modules: Allow exporting without a script (#863) (Saturday, 22 January)
• Re: [WICG/webcomponents] [idea] HTML Modules: Allow exporting without a script (#863) (Saturday, 22 January)
• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Friday, 14 January)

Alex Keng

• Re: [w3c/editing] EditContext: how is bold represented? (Issue #368) (Friday, 14 January)
• Re: [w3c/editing] EditContext: processing model (Issue #375) (Friday, 14 January)
• Re: [w3c/editing] EditContext.isInComposition should be renamed to `isComposing` (Issue #377) (Friday, 14 January)
• Re: [w3c/editing] It might help to write clearer code, if EditContext would have some attributes (Issue #378) (Friday, 14 January)
• Re: [w3c/editing] EditContext has compositionRange(Start|End) but TextUpdateEvent has composition(Start|End) (Issue #380) (Friday, 14 January)
• Re: [w3c/editing] "Squiggle" should be "Wavy" as a value of underlineStyle of TextFormat (Issue #382) (Friday, 14 January)

Alwin Blok

• Re: [whatwg/url] Disallow all C0 control and DEL codepoints in hosts (PR #673) (Tuesday, 25 January)
• Re: [whatwg/url] Disallow all C0 control and DEL codepoints in hosts (PR #673) (Tuesday, 25 January)
• Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674) (Tuesday, 25 January)
• Re: [whatwg/url] Should we escape \ in non-special non-opaque paths? (Issue #675) (Tuesday, 25 January)
• Re: [whatwg/url] Disallow all C0 control and DEL codepoints in hosts (PR #673) (Tuesday, 25 January)
• Re: [whatwg/url] Are drive letters always invalid? (#612) (Friday, 14 January)
• Re: [whatwg/url] Allow protocol setter to switch between special and non-special schemes (Issue #674) (Wednesday, 5 January)

Andreu Botella

• Re: [whatwg/fetch] Add `Response.json` static method (PR #1392) (Sunday, 30 January)
• Re: [w3c/selection-api] Clarify how text selection in <input> and <textarea> work with Selection interface (#83) (Thursday, 27 January)
• [w3c/uievents] Specify the field values for non-pointer `contextmenu` event (Issue #323) (Wednesday, 19 January)

Andrew Sutherland

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

andruud

• [w3ctag/design-reviews] [mediaqueries-4] Range contexts (Issue #707) (Friday, 7 January)
• [w3ctag/design-reviews] [css-values-4] The Large, Small, and Dynamic Viewport Sizes (Issue #706) (Friday, 7 January)

Anne van Kesteren

• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 28 January)
• [w3c/clipboard-apis] Arbitrary clipboard types (Issue #165) (Friday, 28 January)
• Re: [whatwg/url] [Editorial] Correct the note about the IDNA fast-path for ASCII domains (PR #678) (Friday, 28 January)
• Re: [whatwg/url] [Editorial] Correct the note about the IDNA fast-path for ASCII domains (PR #678) (Friday, 28 January)
• Re: [whatwg/url] [Editorial] Correct the note about the IDNA fast-path for ASCII domains (PR #678) (Friday, 28 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Friday, 28 January)
• Re: [whatwg/url] "Forbidden host code point" should be defined without U+0025 (#319) (Friday, 28 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Friday, 28 January)
• Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627) (Friday, 28 January)
• Re: [whatwg/webidl] Introduce "mark as handled" for promises (PR #1090) (Friday, 28 January)
• Re: [whatwg/fetch] Interested in expanding my mind (Issue #1390) (Friday, 28 January)
• Re: [whatwg/fetch] Interested in expanding my mind (Issue #1390) (Friday, 28 January)
• Re: [whatwg/fetch] TAO support for iframes (Issue #1387) (Thursday, 27 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Wednesday, 26 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Wednesday, 26 January)
• Re: [whatwg/url] Disallow all C0 control and DEL codepoints in hosts (PR #673) (Tuesday, 25 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Tuesday, 25 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Tuesday, 25 January)
• Re: [whatwg/url] Meta: Add Node.js bug link to PR template (#525) (Tuesday, 25 January)
• Re: [whatwg/fetch] CORS-safelisting particular client hints (Issue #1383) (Monday, 24 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Monday, 24 January)
• Re: [whatwg/streams] Expose everywhere (#1176) (Monday, 24 January)
• Re: [whatwg/streams] Expose everywhere (#1176) (Monday, 24 January)
• Re: [whatwg/url] Expose URL/URLSearchParams everywhere (#657) (Monday, 24 January)
• Re: [whatwg/encoding] Expose everywhere (PR #274) (Monday, 24 January)
• Re: [whatwg/dom] Expose events/aborts everywhere (#1024) (Monday, 24 January)
• Re: [whatwg/streams] Meta: update repository files (PR #1211) (Monday, 24 January)
• Re: [whatwg/webidl] Meta: update repository files (PR #1089) (Monday, 24 January)
• Re: [whatwg/url] Meta: update repository files (PR #684) (Monday, 24 January)
• Re: [whatwg/fetch] Meta: update repository files (PR #1385) (Monday, 24 January)
• Re: [whatwg/encoding] Meta: update repository files (PR #280) (Monday, 24 January)
• Re: [whatwg/dom] Meta: update repository files (PR #1050) (Monday, 24 January)
• Re: [whatwg/streams] Meta: update repository files (PR #1211) (Monday, 24 January)
• Re: [whatwg/streams] Meta: update repository files (PR #1211) (Monday, 24 January)
• [whatwg/webidl] Meta: update repository files (PR #1089) (Monday, 24 January)
• [whatwg/url] Meta: update repository files (PR #684) (Monday, 24 January)
• [whatwg/streams] Meta: update repository files (PR #1211) (Monday, 24 January)
• [whatwg/fetch] Meta: update repository files (PR #1385) (Monday, 24 January)
• [whatwg/dom] Meta: update repository files (PR #1050) (Monday, 24 January)
• [whatwg/encoding] Meta: update repository files (PR #280) (Monday, 24 January)
• [whatwg/webidl] Correct [Global] example (PR #1088) (Monday, 24 January)
• Re: [whatwg/fetch] Access-Control-Max-Age not effective in preflight request caching when Authorization header is programatically defined (#1278) (Friday, 21 January)
• Re: [whatwg/webidl] Force `[NewObject]` for Promise returning functions? (Issue #1084) (Friday, 21 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2022 (PR #199) (Monday, 17 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2022 (PR #199) (Monday, 17 January)
• [whatwg/fullscreen] Editorial: pairs are tuples now (PR #200) (Monday, 17 January)
• [whatwg/fullscreen] Review Draft Publication: January 2022 (PR #199) (Monday, 17 January)
• Re: [whatwg/dom] feature: `element.getShadow(opts)` (Issue #1046) (Monday, 17 January)
• Re: [whatwg/dom] replaceChildren can not replace a Document's documentElement (Issue #1045) (Friday, 14 January)
• Re: [w3c/editing] EditContext: how is bold represented? (Issue #368) (Friday, 14 January)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Friday, 14 January)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Friday, 14 January)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Wednesday, 12 January)
• Re: [whatwg/fetch] Flag for "Terminate on Response Body"? (Issue #1382) (Wednesday, 12 January)
• Re: [whatwg/fetch] Create SECURITY.mdsimsek0707 (PR #1381) (Saturday, 8 January)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 7 January)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Thursday, 6 January)
• Re: [whatwg/url] Clarify whether "host state" does nothing or is an alias of "hostname state" (Issue #681) (Tuesday, 4 January)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Tuesday, 4 January)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Tuesday, 4 January)
• Re: [whatwg/url] [proposal] Enhanced the ability for multiple same-name-parameters to the URLSearchParams: .has() and .delete() (Issue #680) (Tuesday, 4 January)
• Re: [whatwg/fetch] The upload file process not working with readable streams (I need tracking the upload progress). (Issue #1380) (Monday, 3 January)
• Re: [whatwg/fetch] The upload file process not working with readable streams (I need tracking the upload progress). (Issue #1380) (Monday, 3 January)
• Re: [whatwg/url] [Editorial] Correct the note about the IDNA fast-path for ASCII domains (PR #678) (Monday, 3 January)
• Re: [whatwg/webidl] “Unicode character” should likely say “Unicode scalar value” in intro to lexical grammar (Issue #1080) (Monday, 3 January)
• Re: [whatwg/url] Expand which hostnames are considered IPv4 addresses (Issue #679) (Monday, 3 January)

Arman Bilge

• Re: [whatwg/url] Remove URL.domainToASCII and URL.domainToUnicode (#63) (Sunday, 2 January)

arpitjindal

• Re: [w3c/ServiceWorker] [Question] How to get replacesClientId? (Issue #1623) (Monday, 10 January)
• [w3c/ServiceWorker] [Question] How to get replacesClientId? (Issue #1623) (Friday, 7 January)

Ashley (Scirra)

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

Banou

• Re: [w3c/ServiceWorker] consider adding a note that response body may be re-buffered in browser (#1573) (Sunday, 30 January)

Ben Kelly

• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Friday, 21 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Thursday, 20 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Thursday, 20 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Thursday, 20 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Thursday, 20 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Thursday, 20 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Thursday, 20 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Friday, 14 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Friday, 14 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Friday, 14 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Friday, 14 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Friday, 14 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Friday, 14 January)
• Re: [w3c/ServiceWorker] Add `ServiceWorkerRegistration.id` and supporting algorithm changes. (Fixes #1512) (#1526) (Friday, 14 January)
• Re: [w3c/ServiceWorker] consider allowing a non-scope identifier for registrations (#1512) (Tuesday, 11 January)
• Re: [w3c/ServiceWorker] [Question] How to get replacesClientId? (Issue #1623) (Friday, 7 January)
• Re: [w3c/ServiceWorker] Is it possible to manipulate the initial page request (which seems to be automatically) handled by the service worker? (Issue #1622) (Tuesday, 4 January)
• Re: [w3c/ServiceWorker] Is it possible to manipulate the initial page request (which seems to be automatically) handled by the service worker? (Issue #1622) (Tuesday, 4 January)

Ben Lesh

• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Wednesday, 5 January)
• Re: [whatwg/dom] once() and on() async utilities for EventTarget (Issue #1038) (Wednesday, 5 January)

Bo Cupp

• Re: [w3c/editing] EditContext: Are the events for `EditContext` propagated in the DOM tree? (#341) (Wednesday, 26 January)
• Re: [w3c/editing] Should EditContext be associated with a Node representing the "view"? (#300) (Wednesday, 26 January)
• Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Tuesday, 25 January)
• Re: [w3c/editing] add meeting details for 220127 (PR #386) (Monday, 24 January)
• Re: [w3c/editing] Move to Jitsi for meetings? (Issue #385) (Friday, 21 January)
• Re: [w3c/editing] Move to Jitsi for meetings? (Issue #385) (Friday, 14 January)
• Re: [w3c/editing] Move to Jitsi for meetings? (Issue #385) (Friday, 14 January)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Friday, 14 January)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Friday, 14 January)
• Re: [w3c/editing] Clarify PII concerns in the explainer. (PR #365) (Thursday, 6 January)

caraitto

• Re: [w3c/editing] Clarify PII concerns in the explainer. (PR #365) (Tuesday, 4 January)

Caridy Patiño

• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Thursday, 13 January)

Charlie mitchell

• [whatwg/url] Messed up (Issue #682) (Tuesday, 11 January)

Chris Harrelson

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

Chris Lilley

• [w3ctag/design-reviews] Review request before CR: CSS `selector()` (Issue #709) (Saturday, 15 January)
• Re: [w3ctag/design-reviews] EyeDropper API (#587) (Wednesday, 12 January)
• Re: [w3ctag/design-reviews] EyeDropper API (#587) (Wednesday, 12 January)

Claudia Meadows

• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Saturday, 15 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Saturday, 15 January)

Corentin Wallez

• Re: [w3ctag/design-reviews] WebGPU and WGSL (#626) (Friday, 28 January)
• Re: [w3ctag/design-reviews] WebGPU and WGSL (#626) (Tuesday, 4 January)

CSS Meeting Bot

• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Friday, 14 January)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 14 January)
• Re: [w3c/clipboard-apis] Option to specify ClipboardItem is sensitive in .write() and .writeText() (#154) (Friday, 14 January)

Dan Dumont

• Re: [whatwg/storage] StorageEstimate.quota + Storage Pressure (#73) (Monday, 17 January)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Foldable Device CSS Primitives (Issue #690) (Monday, 31 January)
• Re: [w3ctag/design-reviews] Deprecating `document.domain` setter. (#564) (Sunday, 30 January)
• Re: [w3ctag/design-reviews] Gamepad API input events (#662) (Sunday, 30 January)

Daniel Murphy

• Re: [w3c/manifest] Privacy Review: handle start_url tracking (#399) (Thursday, 20 January)

Darien Maillet Valentine

• Re: [whatwg/dom] Model -> View (DOM el) reactivity (Issue #1049) (Monday, 31 January)
• Re: [whatwg/dom] Basic DOM reactivity (Issue #1049) (Friday, 28 January)
• Re: [whatwg/dom] Basic DOM reactivity (Issue #1049) (Monday, 24 January)
• Re: [whatwg/dom] Basic DOM reactivity (Issue #1049) (Monday, 24 January)
• Re: [WICG/webcomponents] Observable Properties (Issue #951) (Sunday, 9 January)
• Re: [WICG/webcomponents] Observable Properties (Issue #951) (Sunday, 9 January)
• Re: [whatwg/webidl] “Unicode character” should likely say “Unicode scalar value” in intro to lexical grammar (Issue #1080) (Monday, 3 January)

David Alberto Adler

• Re: [whatwg/fetch] Access-Control-Max-Age not effective in preflight request caching when Authorization header is programatically defined (#1278) (Thursday, 20 January)

David Singer

• Re: [whatwg/dom] Privacy/Security considerations section (#1013) (Tuesday, 25 January)

demansanaa

• [whatwg/dom] word (Issue #1047) (Sunday, 16 January)

Dexter Esajas

• Re: [w3c/ServiceWorker] Is it possible to manipulate the initial page request (which seems to be automatically) handled by the service worker? (Issue #1622) (Wednesday, 5 January)

Dmitry Iv.

• [WICG/webcomponents] Template Parts parsing: nested braces case (Issue #953) (Saturday, 15 January)
• [WICG/webcomponents] Templates Parts: SVG error with fields (Issue #952) (Saturday, 15 January)
• Re: [WICG/webcomponents] [templates] How to handle expressions in tables (#703) (Saturday, 15 January)
• Re: [WICG/webcomponents] Template instantiation: Fix typo (PR #948) (Thursday, 6 January)
• Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902) (Tuesday, 4 January)
• Re: [WICG/webcomponents] DOM Parts / Template Parts: conflicting name with CSS parts (Issue #950) (Tuesday, 4 January)
• Re: [WICG/webcomponents] DOM Parts / Template Parts: conflicting name with CSS parts (Issue #950) (Tuesday, 4 January)
• [WICG/webcomponents] DOM Parts / Template Parts: conflicting name with CSS parts (Issue #950) (Tuesday, 4 January)
• [WICG/webcomponents] Fix typo (PR #948) (Monday, 3 January)

Domenic Denicola

• Re: [whatwg/fetch] Add `Response.json` static method (PR #1392) (Monday, 31 January)
• Re: [whatwg/webidl] Introduce "mark as handled" for promises (PR #1090) (Friday, 28 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Thursday, 27 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Wednesday, 26 January)
• [whatwg/webidl] Introduce "mark as handled" for promises (PR #1090) (Wednesday, 26 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Tuesday, 25 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Tuesday, 25 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Tuesday, 25 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Tuesday, 25 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Tuesday, 25 January)
• Re: [whatwg/streams] Handling stream errors in a TransformStream transformer (Issue #1212) (Monday, 24 January)
• [whatwg/streams] Specify realm for object creation (Issue #1213) (Monday, 24 January)
• Re: [whatwg/streams] Handling stream errors in a TransformStream transformer (Issue #1212) (Monday, 24 January)
• Re: [whatwg/webidl] Force `[NewObject]` for Promise returning functions? (Issue #1084) (Friday, 21 January)
• Re: [whatwg/webidl] Fix distinguishability for bigint and numeric types (PR #1082) (Wednesday, 19 January)
• Re: [whatwg/webidl] Editorial: Fix typo in `bigint` column in distinguishability table (#1043) (Wednesday, 19 January)
• Re: [whatwg/webidl] Typo in distinguishability table (says bigint + bigint are distinguishable) (#1010) (Wednesday, 19 January)
• Re: [whatwg/streams] Editorial: call correct Release() depending on chosen reader in pipeTo() (PR #1209) (Tuesday, 18 January)
• Re: [whatwg/streams] Editorial: call correct Release() depending on chosen reader in pipeTo() (PR #1209) (Tuesday, 18 January)
• [whatwg/webidl] Fix distinguishability for bigint and numeric types (PR #1082) (Tuesday, 18 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Tuesday, 18 January)
• Re: [whatwg/streams] pipeTo: Read fulfilled after shutdown started (Issue #1207) (Tuesday, 18 January)
• Re: [WICG/webcomponents] RfC: API design for aria delegation mechanism (#917) (Saturday, 15 January)
• Re: [whatwg/streams] add missing controller argument for ReadableByteStreamControllerError in ReadableByteStreamControllerEnqueueClonedChunkToQueue (PR #1206) (Friday, 14 January)
• Re: [WICG/webcomponents] RfC: API design for aria delegation mechanism (#917) (Thursday, 13 January)
• Re: [whatwg/streams] Replace IRC link with Matrix (PR #1181) (Thursday, 13 January)
• Re: [whatwg/streams] Replace IRC link with Matrix (PR #1181) (Thursday, 13 January)
• Re: [whatwg/streams] Replace IRC link with Matrix (PR #1181) (Thursday, 13 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Thursday, 13 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 12 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 12 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 12 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Monday, 10 January)
• Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849) (Friday, 7 January)
• Re: [whatwg/dom] Valid/Invalid characters in document.createElement() (#849) (Friday, 7 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Thursday, 6 January)
• Re: [whatwg/streams] Should the abort result reflect the close result? (Issue #1203) (Thursday, 6 January)
• Re: [whatwg/streams] Fix documentation for underlying source cancel() errors (PR #1202) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Wednesday, 5 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Wednesday, 5 January)
• [whatwg/streams] Fix documentation for underlying source cancel() errors (PR #1202) (Tuesday, 4 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Tuesday, 4 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Tuesday, 4 January)
• Re: [whatwg/webidl] “Unicode character” should likely say “Unicode scalar value” in intro to lexical grammar (Issue #1080) (Monday, 3 January)

Dominique Hazael-Massieux

• [whatwg/webidl] Constructors should be excluded from inheritance (Issue #1086) (Friday, 21 January)

Ebarg69

• [whatwg/fetch] Interested in expanding my mind (Issue #1390) (Friday, 28 January)

Elad Alon

• Re: [w3ctag/design-reviews] Capture Handle (#645) (Friday, 21 January)
• [w3ctag/design-reviews] Region Capture (Issue #710) (Thursday, 20 January)

Elizabeth Mitchell

• Re: [WICG/webcomponents] RfC: API design for aria delegation mechanism (#917) (Tuesday, 18 January)

Emilio Cobos Álvarez

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

Eric Portis

• [whatwg/fetch] CORS-safelisting particular client hints (Issue #1383) (Wednesday, 19 January)

Evan Stade

• Re: [w3ctag/design-reviews] File Handling (#371) (Wednesday, 26 January)
• Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005) (Wednesday, 19 January)
• Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005) (Wednesday, 19 January)
• Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005) (Thursday, 13 January)

Evgeny Kapun

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

Fabian Cook

• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Saturday, 29 January)
• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Friday, 28 January)

fahmiizzuddinn6

• [whatwg/fetch] form stuck (Issue #1391) (Friday, 28 January)

figroc

• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Thursday, 27 January)

Florian Bösch

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

François Daoust

• [whatwg/webidl] Invalid [Global] example? (Issue #1087) (Sunday, 23 January)

Glandos

• [WICG/webcomponents] SVG <use> tag with CSS ::part selector (Issue #955) (Tuesday, 25 January)

Glen

• Re: [w3ctag/design-reviews] Digital Goods API (#571) (Tuesday, 25 January)

Guilherme Dellagustin

• Re: [whatwg/fetch] Please add support for an indicator as to whether the page was resolved via a temporary redirect or a permanent one (#892) (Saturday, 1 January)

Hadley Beeman

• Re: [w3ctag/design-reviews] Broadening the user base of WebAuthn (Issue #686) (Monday, 31 January)

Hal Blackburn

• Re: [whatwg/streams] Handling stream errors in a TransformStream transformer (Issue #1212) (Monday, 24 January)
• [whatwg/streams] Handling stream errors in a TransformStream transformer (Issue #1212) (Monday, 24 January)

Horacio Rivero

• [whatwg/fetch] upload file progress traking not working (Issue #1380) (Monday, 3 January)

imdat07

• [whatwg/fetch] Create SECURITY.mdsimsek0707 (PR #1381) (Saturday, 8 January)

Ionel Popescu

• Re: [w3ctag/design-reviews] EyeDropper API (#587) (Wednesday, 12 January)

Jake Archibald

• Re: [w3c/ServiceWorker] Define the time origin for service workers (PR #1621) (Tuesday, 25 January)
• Re: [w3c/ServiceWorker] Define the time origin for service workers (PR #1621) (Tuesday, 25 January)
• Re: [w3c/ServiceWorker] Question: Does ServiceWorker reflects to Web Performance when store cache? (Issue #1625) (Monday, 24 January)
• Re: [w3c/ServiceWorker] Question: Does ServiceWorker reflects to Web Performance when store cache? (Issue #1625) (Monday, 24 January)
• Re: [w3c/ServiceWorker] Define the time origin for service workers (PR #1621) (Monday, 17 January)
• Re: [w3c/ServiceWorker] Define the time origin for service workers (PR #1621) (Monday, 17 January)
• Re: [w3c/ServiceWorker] Pass controller from fetch, and abort SW fetch when it's canceled (PR #1620) (Monday, 17 January)
• Re: [w3c/ServiceWorker] Pass controller from fetch, and abort SW fetch when it's canceled (PR #1620) (Monday, 17 January)
• Re: [w3c/ServiceWorker] [FEATURE REQUEST] Persistent ServiceWorker to run setInterval() (Issue #1624) (Monday, 17 January)
• Re: [w3c/ServiceWorker] [FEATURE REQUEST] Persistent ServiceWorker to run setInterval() (Issue #1624) (Monday, 17 January)

James Browning

• Re: [whatwg/dom] feature: `element.getShadow(opts)` (Issue #1046) (Monday, 31 January)
• Re: [whatwg/dom] Basic DOM reactivity (Issue #1049) (Monday, 31 January)

James M Snell

• Re: [whatwg/dom] Symbols should be allowed as Event types. (#331) (Thursday, 27 January)
• Re: [whatwg/dom] Add abortController.close / abortSignal.closed (PR #1042) (Thursday, 27 January)
• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Thursday, 27 January)
• Re: [whatwg/streams] Fix documentation for underlying source cancel() errors (PR #1202) (Wednesday, 5 January)

James May

• Re: [whatwg/fetch] Flag for "Terminate on Response Body"? (Issue #1382) (Saturday, 8 January)
• [whatwg/fetch] Flag for "Terminate on Response Body"? (Issue #1382) (Saturday, 8 January)

Jarred Sumner

• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Friday, 28 January)

Jeff Hykin

• Re: [WICG/webcomponents] Observable Properties (Issue #951) (Sunday, 9 January)
• Re: [WICG/webcomponents] Observable Properties (Issue #951) (Sunday, 9 January)
• [WICG/webcomponents] Observable Properties (Issue #951) (Sunday, 9 January)

jesus medina

• Re: [whatwg/fetch] Meta: fix breakage due to WebSockets (a176ee5) (Thursday, 6 January)

Jim (JR)

• Re: [w3c/gamepad] Please don't restrict to a secure context (#145) (Thursday, 13 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Thursday, 13 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Thursday, 13 January)
• Re: [w3c/gamepad] Add gamepad input events (#152) (Wednesday, 12 January)
• Re: [w3c/gamepad] Add gamepad input events (#152) (Saturday, 8 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Saturday, 8 January)
• Re: [w3c/gamepad] Please don't restrict to a secure context (#145) (Saturday, 8 January)

Jimmy Wärting

• [whatwg/fetch] [Feature request] Add a `CookieStore` option to `Request` (Issue #1384) (Sunday, 23 January)

Joe Pea

• Re: [whatwg/dom] feature: `element.getShadow(opts)` (Issue #1046) (Friday, 14 January)
• [whatwg/dom] feature: `element.getShadow(opts)` (Issue #1046) (Friday, 14 January)

Johannes Wilm

• Re: [w3c/editing] Linking meeting minutes 1/27 (PR #388) (Thursday, 27 January)
• Re: [w3c/editing] Linking meeting minutes 1/27 (PR #388) (Thursday, 27 January)
• Re: [w3c/editing] add meeting details for 220127 (PR #386) (Tuesday, 25 January)
• [w3c/editing] add meeting details for 220127 (PR #386) (Sunday, 23 January)
• Re: [w3c/editing] Move to Jitsi for meetings? (Issue #385) (Friday, 21 January)
• Re: [w3c/editing] Move to Jitsi for meetings? (Issue #385) (Saturday, 15 January)
• Re: [w3c/editing] EditContext: how is bold represented? (Issue #368) (Friday, 14 January)
• [w3c/editing] Move to Jitsi for meetings? (Issue #385) (Friday, 14 January)
• Re: [w3c/editing] Schedule updates (PR #384) (Friday, 14 January)
• Re: [w3c/editing] Schedule updates (PR #384) (Friday, 14 January)
• Re: [w3c/editing] Schedule updates (PR #384) (Friday, 14 January)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Friday, 14 January)
• Re: [w3c/editing] EditContext: how is bold represented? (Issue #368) (Friday, 14 January)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Friday, 14 January)

Jonathan Tran

• Re: [w3c/uievents] Expose 'direction-inversion' in wheel events (#57) (Monday, 10 January)

Joshua Bell

• Re: [w3c/IndexedDB] Clarify the handling of +0 and -0 in keys (Issue #375) (Tuesday, 25 January)
• Re: [w3c/IndexedDB] Need to specify what happens if you call `continuePrimaryKey()` on a cursor where the source is an object store. Throw? (Issue #374) (Thursday, 20 January)
• Re: [w3c/IndexedDB] Thanks for explaining! I missed that first part. (Issue #373) (Thursday, 20 January)
• Re: [w3c/IndexedDB] In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ? (Issue #371) (Thursday, 20 January)
• Re: [w3c/IndexedDB] In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ? (Issue #371) (Thursday, 20 January)
• Re: [w3c/IndexedDB] Sites i been to (Issue #370) (Thursday, 20 January)
• Re: [w3c/IndexedDB] Sites i been to (Issue #370) (Thursday, 20 January)
• Re: [w3c/IndexedDB] In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ? (Issue #372) (Thursday, 20 January)
• Re: [w3c/IndexedDB] In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ? (Issue #372) (Thursday, 20 January)
• Re: [w3c/IndexedDB] Thanks for explaining! I missed that first part. (Issue #373) (Thursday, 20 January)
• Re: [w3c/IndexedDB] Need to specify what happens if you call `continuePrimaryKey()` on a cursor where the source is an object store. Throw? (Issue #374) (Thursday, 20 January)

Justin Fagnani

• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Friday, 28 January)
• Re: [WICG/webcomponents] RfC: API design for aria delegation mechanism (#917) (Saturday, 15 January)

Kagami Sascha Rosylight

• Re: [whatwg/webidl] Meta: update repository files (PR #1089) (Monday, 24 January)
• Re: [whatwg/webidl] Force `[NewObject]` for Promise returning functions? (Issue #1084) (Friday, 21 January)
• Re: [whatwg/webidl] Force `[NewObject]` for Promise returning functions? (Issue #1084) (Friday, 21 January)
• [whatwg/webidl] Force `[NewObject]` for Promise returning functions? (Issue #1084) (Friday, 21 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Tuesday, 18 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Tuesday, 18 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Sunday, 16 January)
• [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Sunday, 16 January)
• Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Sunday, 16 January)
• [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163) (Sunday, 16 January)

Karl

• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Thursday, 27 January)
• Re: [whatwg/url] Disallow all C0 control and DEL codepoints in hosts (PR #673) (Tuesday, 25 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Tuesday, 25 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Tuesday, 25 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Tuesday, 25 January)
• Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Tuesday, 25 January)
• [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685) (Tuesday, 25 January)
• Re: [whatwg/url] Should we unescape characters in path? (#606) (Sunday, 23 January)
• Re: [whatwg/url] [Editorial] Correct the note about the IDNA fast-path for ASCII domains (PR #678) (Friday, 14 January)
• Re: [whatwg/url] [Editorial] Correct the note about the IDNA fast-path for ASCII domains (PR #678) (Friday, 14 January)
• Re: [whatwg/url] Expand which hostnames are considered IPv4 addresses (Issue #679) (Monday, 3 January)
• [whatwg/url] Expand which hostnames are considered IPv4 addresses (Issue #679) (Monday, 3 January)

Karl Dubost

• Re: [w3c/editing] Should contenteditable have break-word behavior by default? (#145) (Sunday, 9 January)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] Address privacy issue with start_url (PR #1029) (Thursday, 20 January)

Kevin Gibbons

• Re: [whatwg/streams] Replace IRC link with Matrix (PR #1181) (Thursday, 13 January)

krgovind

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

Lana R. Jaeger

• [whatwg/webidl] devtools://devtools/bundled/devtools_app.html?remoteBase=https://chrome-devtools-frontend.appspot.com/serve_file/@da06c01444312c5ef07ff055278578120cc12c7f/&panel=elements&dockSide=undocked#:~:text=rs%3D-,AA2YrTvxIxBuWtAIKOA5N8P3pOjUMiMvmw,-%3A956 (Issue #1085) (Friday, 21 January)

Lea Verou

• Re: [w3ctag/design-reviews] EyeDropper API (#587) (Wednesday, 12 January)
• Re: [w3ctag/design-reviews] EyeDropper API (#587) (Wednesday, 12 January)

Lee Robinson

• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Friday, 28 January)

Leo Balter

• Re: [WICG/webcomponents] RfC: API design for aria delegation mechanism (#917) (Saturday, 15 January)
• Re: [WICG/webcomponents] RfC: API design for aria delegation mechanism (#917) (Saturday, 15 January)
• Re: [WICG/webcomponents] Add delegatesLabel and a content attribute to specify the label element within a shadow tree (#916) (Thursday, 13 January)
• Re: [WICG/webcomponents] RfC: API design for aria delegation mechanism (#917) (Thursday, 13 January)

Leo Kettmeir

• [whatwg/streams] add missing controller argument for ReadableByteStreamControllerError in ReadableByteStreamControllerEnqueueClonedChunkToQueue (PR #1206) (Friday, 14 January)

LeoPsidom

• Re: [w3c/manifest] Support window preferred/initial (minimal?) sizes (#436) (Sunday, 23 January)

LI XiangChen

• [whatwg/url] [proposal] Enhanced the ability for multiple same-name-parameters to the URLSearchParams: .has() and .delete() (Issue #680) (Tuesday, 4 January)

Lu

• Re: [w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695) (Friday, 14 January)

Luca Casonato

• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Monday, 31 January)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Sunday, 30 January)
• Re: [whatwg/fetch] Use case for Headers getAll (#973) (Sunday, 30 January)
• Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Sunday, 30 January)
• Re: [whatwg/fetch] Add `Response.json` static method (PR #1392) (Sunday, 30 January)
• Re: [whatwg/fetch] Add `Response.json` static method (PR #1392) (Sunday, 30 January)
• [whatwg/fetch] Add `Response.json` static method (PR #1392) (Sunday, 30 January)
• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Saturday, 29 January)
• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Friday, 28 January)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { atLeast }) (#1145) (Thursday, 27 January)
• [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Thursday, 27 January)

Lukasz Olejnik

• Re: [w3c/manifest] Privacy Review: handle start_url tracking (#399) (Thursday, 20 January)
• Re: [w3c/manifest] Address privacy issue with start_url (PR #1029) (Thursday, 20 January)

m-sk84

• [whatwg/streams] ابتكار جديد في مجال الطاقة المتجددة التي كانت لها تاثير مباشر جدا على الاقتصاد العالمي في مجال الطاقة المتجددة التي اعطيتني الضوء الاخضر على =?UTF-8?Q?_=D8=A7=D9=84=D8=A7=D9=82=D8=AA=D8=B5 (Friday, 7 January)
• [whatwg/streams] شكرا (Issue #1204) (Friday, 7 January)

Makoto Kato

• Re: [w3c/screen-orientation] Feature detection of orientation.lock (Issue #206) (Monday, 31 January)
• [w3c/screen-orientation] Feature detection of orientation.lock (Issue #206) (Monday, 31 January)

mangelozzi

• Re: [w3c/ServiceWorker] Clarification on what happens during a terminated activation (#1372) (Friday, 21 January)

Manish Goregaokar

• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Tuesday, 11 January)
• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Tuesday, 11 January)
• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Tuesday, 4 January)
• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Tuesday, 4 January)
• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Tuesday, 4 January)
• Re: [w3c/gamepad] Add -1 to the set of allowed indices (PR #158) (Tuesday, 4 January)

Marcos Cáceres

• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Saturday, 29 January)
• Re: [whatwg/webidl] IDL-level support for permission checks? (Issue #1066) (Thursday, 27 January)
• Re: [w3c/IndexedDB] Sites i been to (Issue #370) (Monday, 24 January)
• Re: [w3c/permissions] Interaction between browser and system permissions (Issue #332) (Monday, 24 January)
• Re: [w3c/manifest] Privacy Review: handle start_url tracking (#399) (Monday, 24 January)
• Re: [w3c/manifest] Address privacy issue with start_url (PR #1029) (Monday, 24 January)
• Re: [w3c/manifest] Address privacy issue with start_url (PR #1029) (Monday, 24 January)
• Re: [w3c/manifest] Privacy Review: handle start_url tracking (#399) (Thursday, 20 January)
• Re: [w3c/manifest] Address privacy issue with start_url (PR #1029) (Thursday, 20 January)
• [w3c/manifest] Address privacy issue with start_url (PR #1029) (Thursday, 20 January)
• Re: [w3c/permissions] Editorial: relocate nfc powerful feature. (PR #336) (Tuesday, 18 January)
• Re: [w3c/permissions] Editorial: relocate nfc powerful feature. (PR #336) (Tuesday, 18 January)
• Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005) (Tuesday, 18 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Tuesday, 18 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Tuesday, 18 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Tuesday, 18 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Tuesday, 18 January)

Marcos Dantas

• Re: [WICG/webcomponents] Editor support for WebComponents (#776) (Thursday, 13 January)

Martin Janecke

• [whatwg/url] Clarify whether "host state" does nothing or is an alias of "hostname state" (Issue #681) (Tuesday, 4 January)

Martin Thomson

• Re: [w3c/editing] application/web (Issue #387) (Thursday, 27 January)
• [w3c/editing] application/web (Issue #387) (Thursday, 27 January)

Matt Menke

• Re: [whatwg/url] Expand which hostnames are considered IPv4 addresses (Issue #679) (Monday, 3 January)

Mattias Buelens

• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Thursday, 27 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Thursday, 27 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Thursday, 27 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Thursday, 27 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Wednesday, 26 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Wednesday, 26 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Wednesday, 26 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Tuesday, 25 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Tuesday, 25 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Tuesday, 25 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Tuesday, 25 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Tuesday, 25 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Tuesday, 25 January)
• Re: [whatwg/streams] Handling stream errors in a TransformStream transformer (Issue #1212) (Monday, 24 January)
• Re: [whatwg/streams] Meta: file bugs for non-browser implementations? (#1141) (Monday, 24 January)
• Re: [whatwg/streams] Meta: file bugs for non-browser implementations? (#1141) (Monday, 24 January)
• Re: [whatwg/streams] Meta: update repository files (PR #1211) (Monday, 24 January)
• Re: [whatwg/streams] Meta: update repository files (PR #1211) (Monday, 24 January)
• Re: [whatwg/streams] Meta: update repository files (PR #1211) (Monday, 24 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Thursday, 20 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Thursday, 20 January)
• Re: [whatwg/streams] pipeTo: Read fulfilled after shutdown started (Issue #1207) (Thursday, 20 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Wednesday, 19 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Wednesday, 19 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Wednesday, 19 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Wednesday, 19 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Tuesday, 18 January)
• [whatwg/streams] Editorial: call correct Release() depending on chosen reader in pipeTo() (PR #1209) (Tuesday, 18 January)
• Re: [whatwg/streams] pipeTo: Read fulfilled after shutdown started (Issue #1207) (Tuesday, 18 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Tuesday, 18 January)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { atLeast }) (#1145) (Tuesday, 18 January)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { atLeast }) (#1145) (Tuesday, 18 January)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { atLeast }) (#1145) (Tuesday, 18 January)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { atLeast }) (#1145) (Tuesday, 18 January)
• Re: [whatwg/streams] Add ReadableStreamBYOBReader.read(view, { atLeast }) (#1145) (Tuesday, 18 January)
• Re: [whatwg/streams] pipeTo: Read fulfilled after shutdown started (Issue #1207) (Sunday, 16 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Sunday, 16 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Sunday, 16 January)
• Re: [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Sunday, 16 January)
• Re: [whatwg/streams] pipeTo: Read fulfilled after shutdown started (Issue #1207) (Sunday, 16 January)
• [whatwg/streams] Release reader immediately when shutting down a pipe (PR #1208) (Sunday, 16 January)
• Re: [whatwg/streams] pipeTo: Read fulfilled after shutdown started (Issue #1207) (Saturday, 15 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Saturday, 15 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Saturday, 15 January)
• Re: [whatwg/streams] add missing controller argument for ReadableByteStreamControllerError in ReadableByteStreamControllerEnqueueClonedChunkToQueue (PR #1206) (Friday, 14 January)
• Re: [whatwg/streams] ReadableStreamBYOBReader.prototype.readFully(view) (#1143) (Friday, 14 January)
• Re: [whatwg/streams] Make read requests abortable (#1103) (Friday, 14 January)
• Re: [whatwg/streams] Make read requests abortable (#1103) (Friday, 14 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Thursday, 13 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Thursday, 13 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Tuesday, 11 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Tuesday, 11 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Friday, 7 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Friday, 7 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Friday, 7 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Friday, 7 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Friday, 7 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Friday, 7 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Friday, 7 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Thursday, 6 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Thursday, 6 January)
• Re: [whatwg/streams] Fix documentation for underlying source cancel() errors (PR #1202) (Thursday, 6 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Wednesday, 5 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Wednesday, 5 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Wednesday, 5 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Wednesday, 5 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Wednesday, 5 January)
• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Wednesday, 5 January)

mbrodesser

• Re: [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166) (Monday, 31 January)
• [w3c/clipboard-apis] What should `clipboard.readText()` return when the clipboard contains multiple clipboard items? (Issue #166) (Monday, 31 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 26 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 26 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 26 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 18 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 17 January)

Mguiteria

• [w3c/IndexedDB] Need to specify what happens if you call `continuePrimaryKey()` on a cursor where the source is an object store. Throw? (Issue #374) (Thursday, 20 January)
• [w3c/IndexedDB] Thanks for explaining! I missed that first part. (Issue #373) (Thursday, 20 January)
• [w3c/IndexedDB] In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ? (Issue #372) (Thursday, 20 January)
• [w3c/IndexedDB] In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ? (Issue #371) (Thursday, 20 January)
• [w3c/IndexedDB] Sites i been to (Issue #370) (Thursday, 20 January)

Michael Jackson

• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Saturday, 29 January)

Mike Taylor

• Re: [w3c/permissions] Ensure "speaker-selection" is integrated into Audio Output Devices API spec (Issue #320) (Friday, 21 January)
• Re: [w3c/permissions] Ensure "speaker-selection" is integrated into Audio Output Devices API spec (Issue #320) (Friday, 21 January)

Ms2ger

• Re: [whatwg/url] Expose URL/URLSearchParams everywhere (#657) (Tuesday, 18 January)
• Re: [whatwg/streams] Expose everywhere (#1176) (Tuesday, 18 January)
• Re: [whatwg/encoding] Expose everywhere (PR #274) (Tuesday, 18 January)

nangayeform@gmail.com

• [whatwg/webidl] wavemoney.com.mm (Issue #1091) (Thursday, 27 January)

natedoggg239

• Re: [w3c/manifest] chore(auto-publish): enable VALIDATE_LINKS (#983) (Friday, 28 January)

Nidhi Jaju

• Re: [whatwg/streams] Reject pending reads when releasing reader (#1168) (Tuesday, 11 January)

Noah Lemen

• Re: [w3c/ServiceWorker] Service Worker Subresource Filter (#1584) (Wednesday, 5 January)
• Re: [w3c/ServiceWorker] Service Worker Subresource Filter (#1584) (Wednesday, 5 January)

Noam Rosenthal

• Re: [whatwg/fetch] (WIP) Export TAO origin check (PR #1388) (Sunday, 30 January)
• Re: [whatwg/fetch] (WIP) Export TAO origin check (PR #1388) (Sunday, 30 January)
• [whatwg/fetch] Editorial: Export TAO origin check (PR #1388) (Thursday, 27 January)
• Re: [whatwg/fetch] TAO support for iframes (Issue #1387) (Thursday, 27 January)
• [whatwg/fetch] TAO support for iframes (Issue #1387) (Thursday, 27 January)
• Re: [w3c/ServiceWorker] Define the time origin for service workers (PR #1621) (Tuesday, 25 January)
• Re: [w3c/ServiceWorker] Define the time origin for service workers (PR #1621) (Tuesday, 25 January)
• Re: [w3c/ServiceWorker] Define the time origin for service workers (PR #1621) (Monday, 17 January)
• Re: [whatwg/fetch] Add colorprofile destination (#1331) (Monday, 17 January)
• Re: [whatwg/fetch] Add colorprofile destination (#1331) (Monday, 17 January)
• Re: [whatwg/fetch] Integration with preload (PR #1342) (Monday, 17 January)
• Re: [whatwg/xhr] Resource Timing integration (#319) (Monday, 17 January)

Patrick Meenan

• Re: [w3ctag/design-reviews] Priority Hints API (Issue #704) (Monday, 31 January)
• Re: [w3ctag/design-reviews] Priority Hints API (Issue #704) (Monday, 31 January)

Peter Linss

• Re: [w3ctag/design-reviews] Digital Goods API (#571) (Sunday, 30 January)

Philip Jägenstedt

• Re: [whatwg/fullscreen] Review Draft Publication: January 2022 (PR #199) (Monday, 17 January)
• Re: [whatwg/fullscreen] Editorial: pairs are tuples now (PR #200) (Monday, 17 January)
• Re: [whatwg/fullscreen] Editorial: pairs are tuples now (PR #200) (Monday, 17 January)

Piotr Tomiak

• Re: [WICG/webcomponents] Editor support for WebComponents (#776) (Saturday, 15 January)

pshaughn

• Re: [whatwg/dom] Basic DOM reactivity (Issue #1049) (Friday, 28 January)

Reilly Grant

• Re: [whatwg/streams] Make read requests abortable (#1103) (Friday, 14 January)
• Re: [w3c/gamepad] Add gamepad input events (#152) (Wednesday, 12 January)
• Re: [w3c/gamepad] Add gamepad input events (#152) (Monday, 10 January)

Rob Resendez

• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Thursday, 13 January)
• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Thursday, 13 January)

Russell Bicknell

• Re: [WICG/webcomponents] Declarative CSS Module Scripts (#939) (Friday, 28 January)
• Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Thursday, 13 January)

Ryan Pivovar

• Re: [WICG/webcomponents] HTMLSlotElement.assign() does not work as expected (Issue #954) (Friday, 21 January)
• Re: [WICG/webcomponents] `CustomElementRegistry.define()` should return the new custom element (#927) (Thursday, 20 January)
• [WICG/webcomponents] HTMLSlotElement.assign() does not work as expected (Issue #954) (Thursday, 20 January)

Ryosuke Niwa

• Re: [WICG/webcomponents] HTMLSlotElement.assign() does not work as expected (Issue #954) (Saturday, 22 January)
• Re: [WICG/webcomponents] HTMLSlotElement.assign() does not work as expected (Issue #954) (Thursday, 20 January)
• Re: [WICG/webcomponents] HTMLSlotElement.assign() does not work as expected (Issue #954) (Thursday, 20 January)
• Re: [WICG/webcomponents] Template instantiation: Fix typo (PR #948) (Thursday, 6 January)

Scott Haseley

• [w3ctag/design-reviews] AbortSignal.timeout() (Issue #711) (Friday, 28 January)

Seokho Song

• [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708) (Tuesday, 11 January)

snianu

• Re: [w3c/clipboard-apis] supported type should include MathML types (#141) (Thursday, 27 January)
• Re: [w3c/editing] application/web (Issue #387) (Thursday, 27 January)
• Re: [w3c/editing] application/web (Issue #387) (Thursday, 27 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Wednesday, 26 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Tuesday, 25 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Monday, 24 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Saturday, 22 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Saturday, 22 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Saturday, 22 January)
• Re: [w3c/clipboard-apis] Remove clipboard-write permission (PR #164) (Saturday, 22 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Saturday, 22 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Saturday, 22 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 19 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 12 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 12 January)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Wednesday, 12 January)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Friday, 7 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/editing] Draft spec for custom clipboard format. (PR #383) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Thursday, 6 January)
• [w3c/editing] Draft spec for custom clipboard format. (PR #383) (Thursday, 6 January)
• Re: [w3c/editing] Clarify PII concerns in the explainer. (PR #365) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Thursday, 6 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Update README.md (#157) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162) (Wednesday, 5 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 4 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 4 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 4 January)
• Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161) (Tuesday, 4 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 4 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 4 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Tuesday, 4 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)
• Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 3 January)

Stef Busking

• [whatwg/dom] replaceChildren can not replace a Document's documentElement (Issue #1045) (Friday, 14 January)

sudokzt

• [w3c/ServiceWorker] Question: Does ServiceWorker reflects to Web Performance when store cache? (Issue #1625) (Monday, 24 January)

Sukka

• Re: [whatwg/fetch] Proposal: `Response.json` helper (Issue #1389) (Saturday, 29 January)

Thomas Steiner

• Re: [w3c/screen-orientation] Feature detection of orientation.lock (Issue #206) (Monday, 31 January)
• Re: [w3c/screen-orientation] Feature detection of orientation.lock (Issue #206) (Monday, 31 January)

Tim McCormack

• Re: [whatwg/url] why are backslashes accepted for slashes? (#346) (Sunday, 2 January)

Timothy Gu

• Re: [whatwg/webidl] Fix distinguishability for bigint and numeric types (PR #1082) (Wednesday, 19 January)
• Re: [whatwg/url] [proposal] Enhanced the ability for multiple same-name-parameters to the URLSearchParams: .has() and .delete() (Issue #680) (Wednesday, 5 January)
• Re: [whatwg/url] URLSearchParams delete all vs delete one (#335) (Wednesday, 5 January)

Tom Schuster

• Re: [whatwg/streams] pipeTo: Read fulfilled after shutdown started (Issue #1207) (Sunday, 16 January)
• [whatwg/streams] pipeTo: Read fullfilled after shutdown started (Issue #1207) (Saturday, 15 January)

transformsen

• Re: [w3c/ServiceWorker] What is FetchEvent.clientId for navigation requests (#808) (Monday, 3 January)

Travis Leithead

• [w3c/editing] Linking meeting minutes 1/27 (PR #388) (Thursday, 27 January)
• Re: [w3c/editing] Schedule updates (PR #384) (Friday, 14 January)
• Re: [w3c/editing] Schedule updates (PR #384) (Friday, 14 January)
• Re: [w3c/editing] Schedule updates (PR #384) (Friday, 14 January)
• [w3c/editing] Schedule updates (PR #384) (Friday, 14 January)
• Re: [w3c/editing] Explore if there are better meeting times for the Web Editing WG (Issue #359) (Friday, 14 January)

tywonwilliams

• Re: [whatwg/fetch] Connect TWO-- (Issue #1378) (Saturday, 1 January)
• Re: [whatwg/fetch] Connect TWO-- (Issue #1378) (Saturday, 1 January)
• Re: [whatwg/fetch] Connect TWO-- (Issue #1378) (Saturday, 1 January)
• [whatwg/fetch] Connect TWO-- (Issue #1378) (Saturday, 1 January)

UberKluger

• Re: [w3c/uievents] Different click event order behavior between Firefox , ie , edge and Chrome/Safari (#303) (Thursday, 13 January)

Warren Benedetto

• [w3c/ServiceWorker] [FEATURE REQUEST] Persistent ServiceWorker to run setInterval() (Issue #1624) (Saturday, 15 January)

Xiaoqian Wu

• [WICG/webcomponents] update repo type (PR #949) (Monday, 3 January)

Yoav Weiss

• Re: [w3ctag/design-reviews] Same-origin prerendering triggered by speculationrules (#667) (Wednesday, 19 January)
• Re: [w3ctag/design-reviews] Same-origin prerendering triggered by speculationrules (#667) (Tuesday, 18 January)

Yonatan

• Re: [whatwg/dom] Basic DOM reactivity (Issue #1049) (Monday, 31 January)
• Re: [whatwg/dom] Basic DOM reactivity (Issue #1049) (Wednesday, 26 January)
• Re: [whatwg/dom] Basic DOM reactivity (Issue #1049) (Monday, 24 January)
• [whatwg/dom] Basic DOM reactivity (Issue #1049) (Sunday, 23 January)

Yutaka Hirano

• Re: [whatwg/fetch] Access-Control-Max-Age not effective in preflight request caching when Authorization header is programatically defined (#1278) (Thursday, 20 January)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Wednesday, 19 January)
• [whatwg/streams] Should the abort result reflect the close result? (Issue #1203) (Thursday, 6 January)

Yves Lafon

• Re: [w3c/ServiceWorker] Define the time origin for service workers (PR #1621) (Wednesday, 26 January)
• Re: [w3c/ServiceWorker] Define the time origin for service workers (PR #1621) (Tuesday, 25 January)

zbyte-king

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

Last message date: Monday, 31 January 2022 21:39:14 UTC