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

Aaron Gustafson

• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Friday, 26 February)
• Re: [w3c/manifest] Honor media attribute (#955) (Friday, 26 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Friday, 26 February)
• Re: [w3c/manifest] Honor media attribute (#955) (Thursday, 25 February)
• Re: [w3c/manifest] Honor media attribute (#955) (Wednesday, 24 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Tuesday, 23 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Tuesday, 23 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Tuesday, 23 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 4 February)
• Re: [w3c/manifest] manifest (#951) (Thursday, 4 February)
• [w3c/manifest] Add `related_applications` and `prefer_related_applications` to WPT (#950) (Wednesday, 3 February)
• Re: [w3c/manifest] badge purpose "monochrome" is only supported by Firefox (#905) (Wednesday, 3 February)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Wednesday, 3 February)

Adam Rice

• Re: [whatwg/encoding] Document gb18030 decoder end-of-queue oddity (#254) (Friday, 26 February)
• Re: [whatwg/fetch] Add port blocking for tftp, netbios-ns, snmp, rtsp, h323gatestat, h32… (#1148) (Friday, 19 February)
• Re: [whatwg/fetch] Add port blocking for tftp, netbios-ns, snmp, rtsp, h323gatestat, h32… (#1148) (Wednesday, 17 February)
• Re: [whatwg/encoding] Corner cases arising from Big5 encoder not excluding HKSCS codes with lead bytes 0xFA–FE (#252) (Tuesday, 16 February)
• Re: [whatwg/encoding] Corner cases arising from Big5 encoder not excluding HKSCS codes with lead bytes 0xFA–FE (#252) (Tuesday, 16 February)
• Re: [whatwg/fetch] Editorial: correct markup (#1169) (Monday, 15 February)
• Re: [whatwg/fetch] Add port blocking for tftp, netbios-ns, snmp, rtsp, h323gatestat, h32… (#1148) (Friday, 12 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 10 February)
• Re: [whatwg/streams] Typo fix (#1099) (Tuesday, 9 February)
• Re: [whatwg/streams] Typo fix (#1099) (Tuesday, 9 February)
• Re: [whatwg/streams] Typo fix (#1099) (Tuesday, 9 February)
• Re: [whatwg/streams] Typo fix (#1099) (Tuesday, 9 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Monday, 8 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Monday, 8 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Friday, 5 February)
• Re: [whatwg/streams] Using streams from other specs: define a byte-counting strategy (#1085) (Thursday, 4 February)
• Re: [whatwg/streams] Make read requests abortable (#1103) (Thursday, 4 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Thursday, 4 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Thursday, 4 February)
• Re: [whatwg/fetch] Response body stream from SW has wrong realm (#731) (Thursday, 4 February)
• Re: [whatwg/fetch] Add port blocking for tftp, netbios-ns, snmp, rtsp, h323gatestat, h32… (#1148) (Thursday, 4 February)
• Re: [whatwg/fetch] Add remaining domintro boxes (#1161) (Thursday, 4 February)
• Re: [whatwg/fetch] Add port blocking for tftp, netbios-ns, snmp, rtsp, h323gatestat, h32… (#1148) (Thursday, 4 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Monday, 1 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Monday, 1 February)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Monday, 1 February)
• Re: [whatwg/fetch] Fetch and SharedArrayBuffer (#897) (Monday, 1 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Monday, 1 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Monday, 1 February)

Agagamand

• Re: [w3c/manifest] SVG icon sizes="any" (or without property "sizes") (#407) (Wednesday, 24 February)

alancutter

• Re: [w3c/manifest] Add a "tabbed application" mode (#737) (Tuesday, 23 February)
• Re: [w3c/manifest] Add a "tabbed application" mode (#737) (Monday, 22 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Friday, 5 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 4 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Tuesday, 2 February)

Alex Cooper

• Re: [w3ctag/design-reviews] WebXR Lighting Estimation (#574) (Thursday, 18 February)
• Re: [w3ctag/design-reviews] WebXR Lighting Estimation (#574) (Thursday, 11 February)

Alexis Menard

• Re: [w3ctag/design-reviews] Screen Fold API (#575) (Tuesday, 23 February)

Alice

• Re: [w3ctag/design-reviews] inert attribute (#610) (Tuesday, 23 February)
• [w3ctag/design-reviews] inert attribute (#610) (Tuesday, 16 February)

Alwin Blok

• Re: [whatwg/url] Parser generates invalid URLs (#379) (Tuesday, 23 February)
• Re: [whatwg/url] Valid IPv4 address string (#583) (Tuesday, 23 February)
• [whatwg/url] Valid IPv4 address string (#583) (Tuesday, 23 February)
• Re: [whatwg/url] Base URL Windows drive sometimes favoured over input string drive (#574) (Monday, 1 February)

Amy Guy

• Re: [w3ctag/design-reviews] Early design review for the FLoC API (#601) (Tuesday, 23 February)

Ananubis

• [w3ctag/design-reviews] Managed Device Web API (#606) (Friday, 5 February)

Anatoli Babenia

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

Andreu Botella

• Re: [whatwg/url] Editorial: remove support for files in the urlencoded serialization (#585) (Saturday, 27 February)
• [whatwg/url] Editorial: remove support for files in the urlencoded serialization (#585) (Saturday, 27 February)

Andrew Sutherland

• Re: [whatwg/storage] Session storage and changing browsing contexts (#119) (Thursday, 25 February)
• Re: [whatwg/storage] Session storage and changing browsing contexts (#119) (Thursday, 25 February)
• Re: [whatwg/storage] Session storage and changing browsing contexts (#119) (Wednesday, 24 February)
• Re: [whatwg/storage] Session storage and changing browsing contexts (#119) (Tuesday, 23 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)

andruud

• Re: [heycam/webidl] Browsers do not consistently seem to check this? (#958) (Thursday, 25 February)
• Re: [heycam/webidl] Browsers do not consistently seem to check this? (#958) (Tuesday, 23 February)

Andy r

• Re: [whatwg/dom] Add new mutation observer init options elementFilterByAttribute and elementLocalNameFilter (#885) (Saturday, 6 February)

Anne van Kesteren

• Re: [whatwg/dom] Editorial: Restore necessary comma (#954) (Sunday, 28 February)
• Re: [whatwg/dom] Editorial: Restore necessary comma (#954) (Sunday, 28 February)
• Re: [whatwg/url] Editorial: remove support for files in the urlencoded serialization (#585) (Saturday, 27 February)
• Re: [whatwg/url] Editorial: remove support for files in the urlencoded serialization (#585) (Saturday, 27 February)
• Re: [whatwg/fetch] Request's total bytes isn't set (#604) (Saturday, 27 February)
• Re: [whatwg/fetch] Promp for/send TLS client certificates for CORS preflights (#1181) (Saturday, 27 February)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Saturday, 27 February)
• Re: [whatwg/fetch] Promp for/send TLS client certificates for CORS preflights (#1181) (Saturday, 27 February)
• Re: [whatwg/encoding] End-of-queue during decoding of GB18030 should not mask ASCII characters. (#253) (Saturday, 27 February)
• Re: [whatwg/encoding] Document gb18030 decoder end-of-queue oddity (#254) (Saturday, 27 February)
• Re: [whatwg/fetch] Request's total bytes isn't set (#604) (Friday, 26 February)
• Re: [whatwg/storage] Editorial: Remove the <pre class=link-defaults> block. (#123) (Friday, 26 February)
• Re: [whatwg/storage] Editorial: Remove the <pre class=link-defaults> block. (#123) (Friday, 26 February)
• Re: [whatwg/fetch] Correct location URL algorithm fragment handling (#1180) (Friday, 26 February)
• Re: [whatwg/fetch] Correct location URL algorithm fragment handling (#1180) (Friday, 26 February)
• Re: [whatwg/xhr] Handle errors in response bodies (#315) (Friday, 26 February)
• [whatwg/xhr] Handle errors in response bodies (#315) (Friday, 26 February)
• Re: [whatwg/encoding] End-of-queue during decoding of GB18030 should not mask ASCII characters. (#253) (Friday, 26 February)
• [whatwg/encoding] Document gb18030 decoder end-of-queue oddity (#254) (Friday, 26 February)
• Re: [whatwg/xhr] Use Fetch's body read algorithms (#313) (Friday, 26 February)
• Re: [whatwg/fetch] Align redirect fragment handling with HTTP (#696) (Friday, 26 February)
• [whatwg/fetch] Correct location URL algorithm fragment handling (#1180) (Friday, 26 February)
• Re: [whatwg/storage] Editorial: Fix the reference to "persistent-storage". (#122) (Friday, 26 February)
• Re: [whatwg/storage] Editorial: Fix the reference to "persistent-storage". (#122) (Friday, 26 February)
• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Friday, 26 February)
• Re: [whatwg/encoding] End-of-queue during decoding of GB18030 should not mask ASCII characters. (#253) (Thursday, 25 February)
• Re: [whatwg/xhr] Handle error while reading response body in synchronous XHR (#314) (Thursday, 25 February)
• Re: [whatwg/fetch] Add timeout option (#20) (Thursday, 25 February)
• Re: [whatwg/fetch] Add timeout option (#20) (Thursday, 25 February)
• Re: [whatwg/fetch] Add timeout option (#20) (Thursday, 25 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 25 February)
• Re: [whatwg/fetch] Align redirect fragment handling with HTTP (#696) (Thursday, 25 February)
• Re: [whatwg/fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179) (Thursday, 25 February)
• [whatwg/dom] document.createEvent() should maybe not be conditional upon exposure (#952) (Thursday, 25 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Thursday, 25 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Thursday, 25 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Thursday, 25 February)
• Re: [whatwg/fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179) (Thursday, 25 February)
• Re: [whatwg/streams] Make read requests abortable (#1103) (Thursday, 25 February)
• Re: [whatwg/fetch] Add timeout option (#20) (Thursday, 25 February)
• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Thursday, 25 February)
• Re: [whatwg/url] [Editorial] Guarantee that strings encoded with the component encode-set are valid opaque host strings. (#584) (Thursday, 25 February)
• Re: [heycam/webidl] Intent to use bigint/numeric union (#959) (Thursday, 25 February)
• Re: [whatwg/xhr] Use Fetch's body read algorithms (#313) (Thursday, 25 February)
• Re: [whatwg/url] [Editorial] Guarantee that strings encoded with the component encode-set are valid opaque host strings. (#584) (Wednesday, 24 February)
• Re: [whatwg/fetch] Editorial: remove a reference to "responsible document" (#1179) (Wednesday, 24 February)
• Re: [whatwg/fetch] Editorial: remove a reference to "responsible document" (#1179) (Wednesday, 24 February)
• Re: [whatwg/storage] Editorial: Fix the reference to "persistent-storage". (#122) (Wednesday, 24 February)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Wednesday, 24 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Wednesday, 24 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Wednesday, 24 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Wednesday, 24 February)
• Re: [whatwg/fetch] HTTP-network-or-cache fetch request cloning (#1176) (Wednesday, 24 February)
• Re: [whatwg/fetch] Give all bodies a stream (#1177) (Wednesday, 24 February)
• Re: [whatwg/fetch] Give all bodies a stream (#1177) (Wednesday, 24 February)
• Re: [whatwg/fetch] Align redirect fragment handling with HTTP (#696) (Wednesday, 24 February)
• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Wednesday, 24 February)
• Re: [whatwg/url] Prevent the pathname setter from erasing the path of path-only URLs, … (#582) (Wednesday, 24 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Wednesday, 24 February)
• Re: [whatwg/storage] Editorial: Fix the reference to "persistent-storage". (#122) (Wednesday, 24 February)
• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Wednesday, 24 February)
• Re: [heycam/webidl] Browsers do not consistently seem to check this? (#958) (Tuesday, 23 February)
• Re: [heycam/webidl] Browsers do not consistently seem to check this? (#958) (Tuesday, 23 February)
• Re: [whatwg/url] Valid IPv4 address string (#583) (Tuesday, 23 February)
• Re: [whatwg/url] Valid IPv4 address string (#583) (Tuesday, 23 February)
• [heycam/webidl] Browsers do not consistently seem to check this? (#958) (Tuesday, 23 February)
• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Monday, 22 February)
• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Monday, 22 February)
• Re: [whatwg/fetch] Give all bodies a stream (#1177) (Monday, 22 February)
• Re: [whatwg/url] Prevent the pathname setter from erasing the path of path-only URLs, … (#582) (Monday, 22 February)
• Re: [whatwg/fetch] Clarify RequestInit/credentials affects response (#1178) (Monday, 22 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Saturday, 20 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Saturday, 20 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Saturday, 20 February)
• Re: [whatwg/fetch] How should the ReadableStream from response.body work when it's multipart? (#1021) (Friday, 19 February)
• Re: [whatwg/fetch] Request's total bytes isn't set (#604) (Friday, 19 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Friday, 19 February)
• Re: [whatwg/xhr] Use Fetch's body read algorithms (#313) (Friday, 19 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 19 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Friday, 19 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Friday, 19 February)
• [whatwg/fetch] Give all bodies a stream (#1177) (Friday, 19 February)
• Re: [whatwg/fetch] HTTP-network-or-cache fetch request cloning (#1176) (Friday, 19 February)
• Re: [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• Re: [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• Re: [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• Re: [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• Re: [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Friday, 19 February)
• [whatwg/fetch] HTTP-network-or-cache fetch request cloning (#1176) (Friday, 19 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Friday, 19 February)
• Re: [heycam/webidl] Normative: Match ECMA‑262 function property enumeration order (#914) (Friday, 19 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Friday, 19 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Friday, 19 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Friday, 19 February)
• Re: [whatwg/xhr] Use Fetch's body read algorithms (#313) (Friday, 19 February)
• [whatwg/xhr] Use Fetch's body read algorithms (#313) (Friday, 19 February)
• Re: [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• Re: [whatwg/fetch] Align redirect fragment handling with HTTP (#696) (Friday, 19 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Friday, 19 February)
• Re: [w3c/ServiceWorker] URL fragments and service workers (#1564) (Friday, 19 February)
• [whatwg/fetch] Service workers and URL fragments (#1175) (Friday, 19 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 19 February)
• Re: [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Friday, 19 February)
• Re: [w3c/ServiceWorker] URL fragments and service workers (#1564) (Friday, 19 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Thursday, 18 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Thursday, 18 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Thursday, 18 February)
• Re: [whatwg/fetch] Tee request body on ServiceWorker interception (#1144) (Thursday, 18 February)
• Re: [w3c/ServiceWorker] The network fallback should be rejected when the request body is locked or disturbed (#1560) (Thursday, 18 February)
• Re: [whatwg/fetch] Body should not be transmitted if service worker intercepts request (#572) (Thursday, 18 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Thursday, 18 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Wednesday, 17 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Wednesday, 17 February)
• [whatwg/fetch] Formalize reading bodies (#1172) (Wednesday, 17 February)
• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Wednesday, 17 February)
• Re: [whatwg/fetch] Clarify cors requests need cors response tainting (#1170) (Wednesday, 17 February)
• Re: [whatwg/fetch] Clarify cors requests need cors response tainting (#1170) (Wednesday, 17 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Wednesday, 17 February)
• Re: [whatwg/fetch] Clarify cors requests need cors response tainting (#1170) (Wednesday, 17 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Wednesday, 17 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return error when request's streaming body is unusable (#1563) (Wednesday, 17 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 17 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 17 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 17 February)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Wednesday, 17 February)
• Re: [w3c/FileAPI] "Null"ing out the Origin of a BLOB (#74) (Wednesday, 17 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Tuesday, 16 February)
• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Tuesday, 16 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 16 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 16 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Tuesday, 16 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 16 February)
• Re: [whatwg/encoding] Corner cases arising from Big5 encoder not excluding HKSCS codes with lead bytes 0xFA–FE (#252) (Tuesday, 16 February)
• Re: [whatwg/encoding] Corner cases arising from Big5 encoder not excluding HKSCS codes with lead bytes 0xFA–FE (#252) (Tuesday, 16 February)
• Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546) (Tuesday, 16 February)
• Re: [whatwg/encoding] Corner cases arising from Big5 encoder not excluding HKSCS codes with lead bytes 0xFA–FE (#252) (Tuesday, 16 February)
• [heycam/webidl] Promises: resolve algorithm should accept a promise (#957) (Monday, 15 February)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Monday, 15 February)
• Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546) (Monday, 15 February)
• Re: [whatwg/fetch] Body should not be transmitted if service worker intercepts request (#572) (Monday, 15 February)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Monday, 15 February)
• Re: [whatwg/streams] Review Draft Publication: February 2021 (#1108) (Monday, 15 February)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Monday, 15 February)
• Re: [whatwg/xhr] Review Draft Publication: February 2021 (#312) (Monday, 15 February)
• Re: [whatwg/url] Review Draft Publication: February 2021 (#580) (Monday, 15 February)
• Re: [whatwg/storage] Review Draft Publication: February 2021 (#121) (Monday, 15 February)
• Re: [whatwg/storage] Review Draft Publication: February 2021 (#121) (Monday, 15 February)
• [whatwg/xhr] Review Draft Publication: February 2021 (#312) (Monday, 15 February)
• [whatwg/url] Review Draft Publication: February 2021 (#580) (Monday, 15 February)
• [whatwg/streams] Review Draft Publication: February 2021 (#1108) (Monday, 15 February)
• [whatwg/storage] Review Draft Publication: February 2021 (#121) (Monday, 15 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Monday, 15 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Monday, 15 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Monday, 15 February)
• Re: [whatwg/fetch] Editorial: correct markup (#1169) (Monday, 15 February)
• Re: [whatwg/fetch] "Append record to request’s a for=request>client..." (#1168) (Monday, 15 February)
• [whatwg/fetch] Editorial: correct markup (#1169) (Monday, 15 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Monday, 15 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Monday, 15 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Monday, 15 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Monday, 15 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Friday, 12 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Friday, 12 February)
• Re: [whatwg/fetch] "Return a network error" doesn't seem to go through "process response" (#1164) (Friday, 12 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Friday, 12 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Friday, 12 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Friday, 12 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Thursday, 11 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 11 February)
• [w3c/ServiceWorker] URL fragments and service workers (#1564) (Thursday, 11 February)
• Re: [whatwg/url] Consider adding support for fragment parameters (#389) (Thursday, 11 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Thursday, 11 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 11 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 11 February)
• Re: [whatwg/dom] Define criteria for StaticRange validation (#947) (Thursday, 11 February)
• Re: [whatwg/dom] Define criteria for StaticRange validation (#947) (Thursday, 11 February)
• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Thursday, 11 February)
• [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) (Thursday, 11 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Thursday, 11 February)
• Re: [whatwg/url] Editorial: Fix notation for empty path (#579) (Thursday, 11 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Thursday, 11 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Thursday, 11 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Thursday, 11 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Thursday, 11 February)
• Re: [whatwg/fetch] Stop censoring fragments (#696) (Wednesday, 10 February)
• Re: [whatwg/xhr] Stop censoring responseURL's fragment (#200) (Wednesday, 10 February)
• Re: [whatwg/xhr] Stop censoring responseURL's fragment (#200) (Wednesday, 10 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Wednesday, 10 February)
• Re: [whatwg/fetch] Remove FTP support (#1009) (Wednesday, 10 February)
• Re: [whatwg/fetch] Remove FTP support (#1166) (Wednesday, 10 February)
• Re: [whatwg/fetch] Remove FTP support (#1166) (Wednesday, 10 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Wednesday, 10 February)
• [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Wednesday, 10 February)
• [whatwg/fetch] Remove FTP support (#1166) (Wednesday, 10 February)
• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Wednesday, 10 February)
• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Wednesday, 10 February)
• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Wednesday, 10 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 10 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Tuesday, 9 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Tuesday, 9 February)
• [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Tuesday, 9 February)
• Re: [whatwg/fetch] "Return a network error" doesn't seem to go through "process response" (#1164) (Tuesday, 9 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 9 February)
• Re: [whatwg/fetch] "Return a network error" doesn't seem to go through "process response" (#1164) (Tuesday, 9 February)
• Re: [whatwg/fetch] Reinvestigate redirects to data URLs (#393) (Tuesday, 9 February)
• Re: [whatwg/fetch] Reinvestigate redirects to data URLs (#393) (Tuesday, 9 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Tuesday, 9 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 9 February)
• Re: [whatwg/fetch] fetch() does not need in parallel as fetch already does so (#1163) (Monday, 8 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Monday, 8 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Monday, 8 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Monday, 8 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Monday, 8 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Monday, 8 February)
• [whatwg/fetch] fetch() does not need in parallel as fetch already does so (#1163) (Monday, 8 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Monday, 8 February)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Monday, 8 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Monday, 8 February)
• Re: [heycam/webidl] fix: Escape space in issue link template URL (#956) (Sunday, 7 February)
• Re: [heycam/webidl] fix: Escape space in issue link template URL (#956) (Sunday, 7 February)
• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Saturday, 6 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Friday, 5 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Thursday, 4 February)
• Re: [whatwg/fetch] Handle blob URLs without a backing blob (#1077) (Thursday, 4 February)
• Re: [whatwg/fetch] Add remaining domintro boxes (#1161) (Thursday, 4 February)
• Re: [whatwg/fetch] Add domintro explanations for web developers (#543) (Thursday, 4 February)
• Re: [whatwg/fetch] Add remaining domintro boxes (#1161) (Thursday, 4 February)
• Re: [whatwg/fetch] Add remaining domintro boxes (#1161) (Thursday, 4 February)
• Re: [whatwg/fetch] Response body stream from SW has wrong realm (#731) (Thursday, 4 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Thursday, 4 February)
• Re: [whatwg/fetch] Reinvestigate redirects to data URLs (#393) (Wednesday, 3 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 3 February)
• Re: [whatwg/fetch] Acting on incomplete headers (#472) (Wednesday, 3 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 3 February)
• Re: [heycam/webidl] Making methods more future-proof (#954) (Wednesday, 3 February)
• Re: [whatwg/fetch] Acting on incomplete headers (#472) (Wednesday, 3 February)
• Re: [whatwg/fetch] Acting on incomplete headers (#472) (Wednesday, 3 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Wednesday, 3 February)
• Re: [WICG/webcomponents] Spring 2021 Virtual Meeting (#911) (Wednesday, 3 February)
• Re: [whatwg/fetch] It is hard read this section because of 4 "body"s and reassigning each other. (#954) (Wednesday, 3 February)
• Re: [whatwg/fetch] A new Request(input, init) constructor step sounds weird. (#1061) (Wednesday, 3 February)
• Re: [whatwg/fetch] Editorial: rename keepalive flag to keepalive (#1152) (Wednesday, 3 February)
• Re: [heycam/webidl] Cannot resolve/reject a promise in parallel (#953) (Wednesday, 3 February)
• Re: [whatwg/fetch] Editorial: URL dropped flag language (#1160) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: URL dropped flag language (#1160) (Tuesday, 2 February)
• Re: [heycam/webidl] Cannot resolve/reject a promise in parallel (#953) (Tuesday, 2 February)
• Re: [heycam/webidl] Cannot resolve/reject a promise in parallel (#953) (Tuesday, 2 February)
• Re: [heycam/webidl] Cannot resolve/reject a promise in parallel (#953) (Tuesday, 2 February)
• Re: [heycam/webidl] Cannot resolve/reject a promise in parallel (#953) (Tuesday, 2 February)
• [heycam/webidl] Cannot resolve/reject a promise in parallel (#953) (Tuesday, 2 February)
• Re: [whatwg/fetch] Response body stream from SW has wrong realm (#731) (Tuesday, 2 February)
• [whatwg/streams] Cannot set Realm for ReadableStream (#1106) (Tuesday, 2 February)
• [whatwg/fetch] Add remaining domintro boxes (#1161) (Tuesday, 2 February)
• Re: [whatwg/fetch] fetch+CSP end up touching globals in a parallel section on redirect (#832) (Tuesday, 2 February)
• Re: [whatwg/fetch] Add port blocking for tftp, netbios-ns, snmp, rtsp, h323gatestat, h32… (#1148) (Tuesday, 2 February)
• Re: [whatwg/fetch] Clarify response's url list state when parsing a 3xx response's Location header value (#631) (Tuesday, 2 February)
• Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Tuesday, 2 February)
• Re: [whatwg/fetch] Script-created redirects responses have no location URL (#1146) (Tuesday, 2 February)
• Re: [whatwg/fetch] Remove location URL as field on responses (#1149) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: refactor response's location URL so it's always present (#958) (Tuesday, 2 February)
• Re: [whatwg/fetch] Creating new request & response objects could be easier (#771) (Tuesday, 2 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Tuesday, 2 February)
• Re: [whatwg/url] Editorial: go all in on booleans (#576) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: Fix CORS legal and illegal combinations table (#1115) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: Fix CORS legal and illegal combinations table (#1115) (Tuesday, 2 February)
• [whatwg/fetch] Editorial: URL dropped flag language (#1160) (Tuesday, 2 February)
• Re: [whatwg/fetch] Change default of request's credentials mode (#1153) (Tuesday, 2 February)
• Re: [whatwg/fetch] "Set fallbackCredentials to "same-origin"." (#804) (Tuesday, 2 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Tuesday, 2 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Tuesday, 2 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: rename keepalive flag to keepalive (#1152) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: en-US is sanitize (#1151) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: rename keepalive flag to keepalive (#1152) (Tuesday, 2 February)
• Re: [whatwg/fetch] Remove location URL as field on responses (#1149) (Tuesday, 2 February)
• Re: [WICG/webcomponents] Spring 2021 Virtual Meeting (#911) (Tuesday, 2 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: rename keepalive flag to keepalive (#1152) (Tuesday, 2 February)
• Re: [whatwg/fetch] Define behavior in the presence of TLS Early Data (#888) (Tuesday, 2 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Tuesday, 2 February)
• Re: [whatwg/url] Editorial: go all in on booleans (#576) (Monday, 1 February)
• Re: [whatwg/url] Editorial: algorithms can now have default argument values (#575) (Monday, 1 February)
• Re: [whatwg/url] Editorial: algorithms can now have default argument values (#575) (Monday, 1 February)
• Re: [whatwg/url] Editorial: algorithms can now have default argument values (#575) (Monday, 1 February)
• Re: [whatwg/url] Editorial: algorithms can now have default argument values (#575) (Monday, 1 February)
• Re: [whatwg/url] Editorial: algorithms can now have default argument values (#575) (Monday, 1 February)
• Re: [whatwg/url] Editorial: algorithms can now have default argument values (#575) (Monday, 1 February)
• Re: [whatwg/url] Editorial: algorithms can now have default argument values (#575) (Monday, 1 February)
• Re: [whatwg/fetch] Change default of request's credentials mode (#1153) (Monday, 1 February)
• Re: [whatwg/fetch] Change default of request's credentials mode (#1153) (Monday, 1 February)
• Re: [whatwg/fetch] Clarify what a status is (#1159) (Monday, 1 February)
• Re: [whatwg/fetch] "A status is a code" doesn't actually mean anything (#1142) (Monday, 1 February)
• Re: [whatwg/fetch] Clarify what a status is (#1159) (Monday, 1 February)
• Re: [whatwg/fetch] Change default of request's credentials mode (#1153) (Monday, 1 February)
• Re: [whatwg/fetch] Consider "extract a MIME type and compare its essence" (#856) (Monday, 1 February)
• Re: [whatwg/fetch] ResourceTiming integration question: how to handle iframes (#968) (Monday, 1 February)
• [whatwg/fetch] Clarify what a status is (#1159) (Monday, 1 February)
• Re: [whatwg/fetch] Meta: internal response belongs to filtered response (#1158) (Monday, 1 February)
• Re: [whatwg/fetch] "Internal response" for "internal"? (#695) (Monday, 1 February)
• [whatwg/fetch] Meta: internal response belongs to filtered response (#1158) (Monday, 1 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• Re: [whatwg/fetch] Request.headers is shared across Requests. Is it OK? (#1075) (Monday, 1 February)
• Re: [whatwg/fetch] Remove location URL as field on responses (#1149) (Monday, 1 February)
• Re: [whatwg/fetch] Editorial: cleanup Body interface mixin (#802) (Monday, 1 February)
• Re: [whatwg/fetch] Editorial: Body mixin cleanup (#1155) (Monday, 1 February)
• Re: [whatwg/fetch] "A status is a code" doesn't actually mean anything (#1142) (Monday, 1 February)
• [whatwg/fetch] HTTP/1 parsing (#1156) (Monday, 1 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Monday, 1 February)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Monday, 1 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Monday, 1 February)
• Re: [whatwg/url] Editorial: go all in on booleans (#576) (Monday, 1 February)
• [whatwg/url] Editorial: go all in on booleans (#576) (Monday, 1 February)
• Re: [whatwg/url] Editorial: algorithms can now have default argument values (#575) (Monday, 1 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Monday, 1 February)
• Re: [whatwg/fetch] Define RST_STREAM's error code (#637) (Monday, 1 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Monday, 1 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Monday, 1 February)

Anssi Kostiainen

• Re: [w3ctag/design-reviews] Screen Fold API (#575) (Friday, 5 February)
• Re: [w3ctag/design-reviews] Web Neural Network API (#570) (Thursday, 4 February)
• Re: [whatwg/fetch] Editorial: Fix CORS legal and illegal combinations table (#1115) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: Fix CORS legal and illegal combinations table (#1115) (Tuesday, 2 February)

Antonio Sartori

• Re: [whatwg/fetch] fetch+CSP end up touching globals in a parallel section on redirect (#832) (Wednesday, 3 February)

Arthur Sonzogni

• Re: [w3ctag/design-reviews] "credentialless" embedder policy. (#582) (Tuesday, 9 February)
• Re: [w3ctag/design-reviews] "credentialless" embedder policy. (#582) (Monday, 8 February)

arturjanc

• Re: [w3ctag/design-reviews] "credentialless" embedder policy. (#582) (Monday, 8 February)
• Re: [w3ctag/design-reviews] "credentialless" embedder policy. (#582) (Monday, 8 February)
• Re: [w3ctag/design-reviews] "credentialless" embedder policy. (#582) (Monday, 8 February)

Ben

• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Wednesday, 3 February)

Ben Francis

• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Friday, 19 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 18 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 18 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Wednesday, 17 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Wednesday, 17 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Monday, 15 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Monday, 8 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Friday, 5 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 4 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 4 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Wednesday, 3 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Tuesday, 2 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Tuesday, 2 February)

Ben Kelly

• Re: [w3c/ServiceWorker] Cache API: Cache-Control headers and Opaque Responses (#1299) (Wednesday, 24 February)
• Re: [whatwg/fetch] Service workers and URL fragments (#1175) (Friday, 19 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 19 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 19 February)
• Re: [w3c/ServiceWorker] URL fragments and service workers (#1564) (Friday, 19 February)
• Re: [w3c/ServiceWorker] URL fragments and service workers (#1564) (Friday, 19 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 18 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 18 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Wednesday, 17 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Wednesday, 17 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Friday, 12 February)
• Re: [whatwg/fetch] Allow more flexibility in how 401s/407s are handled? (#1132) (Thursday, 11 February)
• Re: [whatwg/fetch] Allow more flexibility in how 401s/407s are handled? (#1132) (Thursday, 11 February)
• Re: [w3c/ServiceWorker] How can we intercept network requests comes from iframe (#1565) (Thursday, 11 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 11 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 11 February)
• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) (Thursday, 11 February)
• Re: [whatwg/fetch] Why doesn't the "body" member of RequestInit have a default value? (#933) (Monday, 1 February)

Benjamin Gruenbaum

• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Friday, 5 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Friday, 5 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920) (Thursday, 4 February)
• Re: [whatwg/dom] Encourage use of AbortError for cancellation? (#927) (Wednesday, 3 February)
• Re: [whatwg/dom] Encourage use of AbortError for cancellation? (#927) (Wednesday, 3 February)
• Re: [whatwg/dom] Encourage use of AbortError for cancellation? (#927) (Wednesday, 3 February)

Bernard Aboba

• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Thursday, 18 February)

Boris Zbarsky

• Re: [heycam/webidl] State that by default all objects are created in the relevant realm of `this` (#135) (Wednesday, 3 February)
• Re: [heycam/webidl] State that by default all objects are created in the relevant realm of `this` (#135) (Wednesday, 3 February)

Brian

• Re: [w3c/gamepad] Add permission policy integration (#112) (Wednesday, 10 February)
• Re: [w3c/gamepad] Add permission policy integration (#112) (Tuesday, 9 February)

Caleb Williams

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 27 February)

Chai Chaoweeraprasit

• Re: [w3ctag/design-reviews] Web Neural Network API (#570) (Saturday, 6 February)

chcunningham

• Re: [w3ctag/design-reviews] WebCodecs (again!) (#612) (Tuesday, 23 February)
• Re: [w3ctag/design-reviews] WebCodecs (again!) (#612) (Tuesday, 23 February)
• Re: [w3ctag/design-reviews] WebCodecs (again!) (#612) (Friday, 19 February)
• [w3ctag/design-reviews] WebCodecs (again!) (#612) (Thursday, 18 February)

Chris Harrelson

• Re: [w3ctag/design-reviews] Web page settings to save battery (#546) (Monday, 8 February)
• Re: [w3ctag/design-reviews] Web page settings to save battery (#546) (Monday, 8 February)
• Re: [w3ctag/design-reviews] Web page settings to save battery (#546) (Monday, 8 February)

Christian Biesinger

• Re: [w3ctag/design-reviews] Review for CSS property "aspect-ratio" (#559) (Friday, 12 February)

Chulki Lee

• [whatwg/url] Editorial: Fix notation for empty path (#579) (Thursday, 11 February)

cynthia

• Re: [w3ctag/design-reviews] Media Source Extensions for WebCodecs (#576) (Wednesday, 24 February)
• Re: [w3ctag/design-reviews] Media Source Extensions for WebCodecs (#576) (Tuesday, 23 February)
• Re: [w3ctag/design-reviews] Media Session: video conferencing actions (#608) (Tuesday, 23 February)
• Re: [w3ctag/design-reviews] WebCodecs (again!) (#612) (Saturday, 20 February)
• Re: [w3ctag/design-reviews] Web Neural Network API (#570) (Monday, 8 February)

Dale Curtis

• Re: [w3ctag/design-reviews] Media Source Extensions for WebCodecs (#576) (Tuesday, 23 February)

Daniel Appelquist

• Re: [w3ctag/design-reviews] WebXR Lighting Estimation (#574) (Wednesday, 24 February)
• Re: [w3ctag/design-reviews] WebXR Lighting Estimation (#574) (Wednesday, 24 February)
• Re: [w3ctag/design-reviews] MediaStreamTrack Insertable Media Processing using Streams (#603) (Tuesday, 23 February)
• Re: [w3ctag/design-reviews] Media Session: video conferencing actions (#608) (Tuesday, 23 February)
• Re: [w3ctag/design-reviews] inert attribute (#610) (Monday, 22 February)
• Re: [w3ctag/design-reviews] Early design review for the FLoC API (#601) (Monday, 22 February)
• Re: [w3ctag/design-reviews] WebXR Dynamic Viewport Scaling (#588) (Monday, 22 February)
• Re: [w3ctag/design-reviews] WebXR Lighting Estimation (#574) (Monday, 22 February)
• Re: [w3ctag/design-reviews] CSS Scrollbars: scrollbar-color, scrollbar-width (#563) (Monday, 22 February)
• Re: [w3ctag/design-reviews] Support seeking past the end of a file in the File System Access API (#600) (Wednesday, 17 February)
• Re: [w3ctag/design-reviews] Support seeking past the end of a file in the File System Access API (#600) (Wednesday, 17 February)
• Re: [w3ctag/design-reviews] Support seeking past the end of a file in the File System Access API (#600) (Tuesday, 16 February)
• Re: [w3ctag/design-reviews] Reporting (#585) (Monday, 15 February)
• Re: [w3ctag/design-reviews] DOM Review Draft — Published 15 June 2020 (#573) (Wednesday, 10 February)
• Re: [w3ctag/design-reviews] DOM Review Draft — Published 15 June 2020 (#573) (Wednesday, 10 February)
• Re: [w3ctag/design-reviews] hasDroppedEntry in PerformanceObserverCallback (#547) (Wednesday, 10 February)
• Re: [w3ctag/design-reviews] hasDroppedEntry in PerformanceObserverCallback (#547) (Wednesday, 10 February)
• Re: [w3ctag/design-reviews] Web page settings to save battery (#546) (Wednesday, 10 February)
• Re: [w3ctag/design-reviews] Web page settings to save battery (#546) (Wednesday, 10 February)
• Re: [w3ctag/design-reviews] Design review of SameParty cookie attribute (#595) (Monday, 8 February)

Daniel Ehrenberg

• Re: [heycam/webidl] Making methods more future-proof (#954) (Wednesday, 3 February)

Daniel Murphy

• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Friday, 26 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Friday, 26 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Thursday, 25 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Wednesday, 24 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Tuesday, 23 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Tuesday, 23 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Monday, 22 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Monday, 22 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Monday, 22 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 18 February)
• Re: [w3c/manifest] The current PWA id (app_id) is used for system integration (tile, taskbar) (#953) (Thursday, 18 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 18 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 18 February)
• Re: [w3c/manifest] `display-mode` CSS media feature should include `"display_override"` values (#952) (Thursday, 18 February)
• Re: [w3c/manifest] `display-mode` CSS media feature should include `"display_override"` values (#952) (Thursday, 18 February)
• Re: [w3c/manifest] `display-mode` CSS media feature should include `"display_override"` values (#952) (Thursday, 18 February)
• Re: [w3c/manifest] Editorial: Created explicit algorithm for choosing display mode, and add extension point for the display_override incubation. (#949) (Thursday, 18 February)
• Re: [w3c/manifest] Editorial: Created explicit algorithm for choosing display mode, and add extension point for the display_override incubation. (#949) (Thursday, 18 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Wednesday, 17 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Wednesday, 17 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Tuesday, 16 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Wednesday, 10 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 4 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 4 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 4 February)
• Re: [w3c/manifest] Editorial: Created explicit algorithm for choosing display mode, and add extension point for the display_override incubation. (#949) (Wednesday, 3 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Wednesday, 3 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Tuesday, 2 February)

Danny Engelman

• Re: [WICG/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Sunday, 7 February)
• [WICG/webcomponents] Why is Chrome Platform Status reporting 70% usage for HTMLSlotElement? (#912) (Thursday, 4 February)

David Benjamin

• Re: [whatwg/fetch] Correct location URL algorithm fragment handling (#1180) (Friday, 26 February)
• Re: [whatwg/fetch] Align redirect fragment handling with HTTP (#696) (Thursday, 25 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Thursday, 18 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Wednesday, 17 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Wednesday, 17 February)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 11 February)
• Re: [whatwg/fetch] Remove location URL as field on responses (#1149) (Tuesday, 2 February)
• Re: [whatwg/fetch] Remove location URL as field on responses (#1149) (Tuesday, 2 February)

David Byers

• Re: [w3c/gamepad] Add permission policy integration (#112) (Sunday, 28 February)

Diogo Eichert

• Re: [w3c/gamepad] `navigator.getGamepads()` should return a `Promise` (#23) (Tuesday, 2 February)

Domenic Denicola

• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Sunday, 28 February)
• Re: [w3c/FileAPI] Remove the / -> : replacement from the File constructor (#41) (Sunday, 28 February)
• Re: [whatwg/dom] [idea] Node.empty() (#955) (Sunday, 28 February)
• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Thursday, 25 February)
• Re: [whatwg/streams] Make read requests abortable (#1103) (Wednesday, 24 February)
• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Wednesday, 24 February)
• Re: [whatwg/streams] Make read requests abortable (#1103) (Wednesday, 24 February)
• [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Wednesday, 24 February)
• Re: [whatwg/fetch] Editorial: remove a reference to "responsible document" (#1179) (Wednesday, 24 February)
• [whatwg/fetch] Editorial: remove a reference to "responsible document" (#1179) (Wednesday, 24 February)
• Re: [whatwg/dom] Add Imperative Slot API (#860) (Tuesday, 23 February)
• Re: [whatwg/url] Prevent the pathname setter from erasing the path of path-only URLs, … (#582) (Tuesday, 23 February)
• Re: [heycam/webidl] Browsers do not consistently seem to check this? (#958) (Tuesday, 23 February)
• Re: [whatwg/xhr] Use Fetch's body read algorithms (#313) (Monday, 22 February)
• Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52) (Friday, 19 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Friday, 19 February)
• Re: [whatwg/fetch] Give all bodies a stream (#1177) (Friday, 19 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Thursday, 18 February)
• Re: [w3ctag/design-reviews] inert attribute (#610) (Thursday, 18 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Wednesday, 17 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Wednesday, 17 February)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Tuesday, 16 February)
• Re: [whatwg/fetch] Propagate URL fragments (#696) (Tuesday, 16 February)
• Re: [whatwg/streams] Review Draft Publication: February 2021 (#1108) (Monday, 15 February)
• [whatwg/fetch] "Append record to request’s a for=request>client..." (#1168) (Saturday, 13 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Thursday, 11 February)
• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Thursday, 11 February)
• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Thursday, 11 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Thursday, 11 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Thursday, 11 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Thursday, 11 February)
• Re: [whatwg/xhr] Editorial: adopt Fetch's new approach to callbacks (#311) (Wednesday, 10 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Wednesday, 10 February)
• Re: [whatwg/fetch] Remove FTP support (#1166) (Wednesday, 10 February)
• Re: [whatwg/streams] ReadableStreamClose with async iterator and pending read requests errors (#1100) (Monday, 8 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Monday, 8 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Monday, 8 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Monday, 8 February)
• [whatwg/fetch] "Return a network error" doesn't seem to go through "process response" (#1164) (Monday, 8 February)
• Re: [whatwg/fetch] fetch() does not need in parallel as fetch already does so (#1163) (Monday, 8 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Friday, 5 February)
• Re: [whatwg/streams] Using streams from other specs: define a byte-counting strategy (#1085) (Thursday, 4 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [heycam/webidl] State that by default all objects are created in the relevant realm of `this` (#135) (Wednesday, 3 February)
• Re: [heycam/webidl] State that by default all objects are created in the relevant realm of `this` (#135) (Wednesday, 3 February)
• Re: [whatwg/dom] Encourage use of AbortError for cancellation? (#927) (Wednesday, 3 February)
• Re: [whatwg/streams] Does `ReadableStream.values()` need a proper definition? (#1107) (Wednesday, 3 February)
• Re: [whatwg/streams] Does `ReadableStream.values()` need a proper definition? (#1107) (Wednesday, 3 February)
• Re: [heycam/webidl] Cannot resolve/reject a promise in parallel (#953) (Tuesday, 2 February)
• Re: [heycam/webidl] Cannot resolve/reject a promise in parallel (#953) (Tuesday, 2 February)
• [w3ctag/design-reviews] App history API (#605) (Tuesday, 2 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Monday, 1 February)
• Re: [whatwg/url] Editorial: algorithms can now have default argument values (#575) (Monday, 1 February)
• Re: [whatwg/url] Editorial: algorithms can now have default argument values (#575) (Monday, 1 February)
• Re: [whatwg/url] Editorial: algorithms can now have default argument values (#575) (Monday, 1 February)
• Re: [whatwg/fetch] Change default of request's credentials mode (#1153) (Monday, 1 February)
• Re: [whatwg/fetch] Change default of request's credentials mode (#1153) (Monday, 1 February)
• Re: [whatwg/fetch] consider exposing and allowing script to set Request priority (#436) (Monday, 1 February)
• Re: [whatwg/fetch] Remove location URL as field on responses (#1149) (Monday, 1 February)
• Re: [whatwg/streams] The link text for creating a new readable stream is awkward. (#1104) (Monday, 1 February)
• Re: [whatwg/streams] The link text for creating a new readable stream is awkward. (#1104) (Monday, 1 February)
• Re: [whatwg/fetch] Change default of request's credentials mode (#1153) (Monday, 1 February)
• Re: [whatwg/fetch] Clarify what a status is (#1159) (Monday, 1 February)

Dominick Ng

• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Tuesday, 2 February)

Dominique Hazael-Massieux

• [w3ctag/design-reviews] Early TAG design review for captureTab (#609) (Friday, 12 February)

Dylan Barrell

• Re: [w3ctag/design-reviews] inert attribute (#610) (Thursday, 18 February)

Electrovia

• [w3c/manifest] manifest (#951) (Thursday, 4 February)

Emily Stark

• Re: [whatwg/fetch] Allow more flexibility in how 401s/407s are handled? (#1132) (Thursday, 11 February)
• Re: [whatwg/fetch] Allow more flexibility in how 401s/407s are handled? (#1132) (Thursday, 11 February)
• Re: [whatwg/fetch] Allow more flexibility in how 401s/407s are handled? (#1132) (Monday, 1 February)

Erik Jensen

• Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Saturday, 6 February)
• [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577) (Saturday, 6 February)

ExE Boss

• Re: [heycam/webidl] Normative: Match ECMA‑262 function property enumeration order (#914) (Friday, 19 February)
• Re: [heycam/webidl] Normative: Match ECMA‑262 function property enumeration order (#914) (Friday, 19 February)

eyeinsky

• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Sunday, 28 February)
• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Sunday, 28 February)
• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Sunday, 28 February)
• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Sunday, 28 February)
• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Saturday, 27 February)
• [whatwg/fetch] Promp for/send TLS client certificates for CORS preflights (#1181) (Saturday, 27 February)

Fabrice Desré

• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Friday, 26 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Wednesday, 24 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 18 February)

Felipe Erias

• Re: [w3ctag/design-reviews] CSS Scrollbars: scrollbar-color, scrollbar-width (#563) (Monday, 22 February)
• Re: [w3ctag/design-reviews] CSS Scrollbars: scrollbar-color, scrollbar-width (#563) (Friday, 5 February)

François Beaufort

• [w3c/manifest] Honor media attribute (#955) (Wednesday, 24 February)

Frederik Braun

• Re: [whatwg/fetch] Add port blocking for tftp, netbios-ns, snmp, rtsp, h323gatestat, h32… (#1148) (Friday, 19 February)
• Re: [whatwg/fetch] Add port blocking for tftp, netbios-ns, snmp, rtsp, h323gatestat, h32… (#1148) (Friday, 12 February)
• Re: [whatwg/fetch] Add port blocking for tftp, netbios-ns, snmp, rtsp, h323gatestat, h32… (#1148) (Wednesday, 10 February)

Gary Kacmarcik

• Re: [w3c/uievents] Add default value {} to optional eventInitDict arguments (#292) (Wednesday, 17 February)
• Re: [w3c/uievents] Add default value {} to optional eventInitDict arguments (#292) (Wednesday, 17 February)

Gopalakrishna Palem

• Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Friday, 19 February)
• Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Friday, 19 February)

Greggman

• Re: [w3c/gamepad] Add permission policy integration (#112) (Tuesday, 9 February)

h110m

• [whatwg/fetch] Firefox deletes all cookies from fetch request! (#1182) (Sunday, 28 February)

Hadley Beeman

• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Monday, 8 February)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Monday, 8 February)

HarJIT

• [whatwg/encoding] Corner cases arising from Big5 encoder not excluding HKSCS codes with lead bytes 0xFA–FE (#252) (Monday, 15 February)

Hendrik Mans

• Re: [WICG/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Sunday, 7 February)
• Re: [WICG/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Friday, 5 February)

Henri Sivonen

• Re: [whatwg/encoding] Corner cases arising from Big5 encoder not excluding HKSCS codes with lead bytes 0xFA–FE (#252) (Tuesday, 16 February)

hober

• Re: [w3ctag/design-reviews] Pointer Events Azimuth Angle and Altitude Angle (#537) (Monday, 15 February)
• Re: [w3ctag/design-reviews] Pointer Events Azimuth Angle and Altitude Angle (#537) (Monday, 15 February)
• Re: [w3ctag/design-reviews] Beforematch event and content-visibility: hidden-matchable (#511) (Tuesday, 9 February)

hrantabelyan

• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Thursday, 25 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Tuesday, 23 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Monday, 22 February)
• [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Sunday, 21 February)

hugo306

• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Thursday, 25 February)

Ihor Bodnarchuk

• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Saturday, 20 February)

Jake Archibald

• Re: [whatwg/storage] Session storage and changing browsing contexts (#119) (Thursday, 25 February)
• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Thursday, 25 February)
• Re: [whatwg/storage] Session storage and changing browsing contexts (#119) (Thursday, 25 February)
• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Thursday, 25 February)
• Re: [whatwg/storage] Session storage and changing browsing contexts (#119) (Wednesday, 24 February)
• Re: [whatwg/storage] Session storage and changing browsing contexts (#119) (Wednesday, 24 February)
• Re: [whatwg/storage] Session storage and changing browsing contexts (#119) (Wednesday, 24 February)
• Re: [whatwg/storage] Session storage and changing browsing contexts (#119) (Tuesday, 23 February)
• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Monday, 22 February)
• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Monday, 22 February)
• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Friday, 19 February)
• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Friday, 19 February)
• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Friday, 19 February)
• [w3c/ServiceWorker] Spec how extendable events are given time to execute (#1566) (Friday, 19 February)
• Re: [w3c/ServiceWorker] Replaying POST requests (#693) (Friday, 19 February)
• Re: [w3c/ServiceWorker] Replaying POST requests (#693) (Friday, 19 February)
• Re: [w3c/ServiceWorker] Detecting service worker termination (#1550) (Friday, 19 February)
• Re: [w3c/ServiceWorker] Service worker & Blocked cookies (#1551) (Friday, 19 February)
• Re: [w3c/ServiceWorker] Service worker & Blocked cookies (#1551) (Friday, 19 February)
• Re: [w3c/ServiceWorker] ServiceWorkerContainer: Web Workers and Service Workers (#1552) (Friday, 19 February)
• Re: [w3c/ServiceWorker] ServiceWorkerContainer: Web Workers and Service Workers (#1552) (Friday, 19 February)
• Re: [w3c/ServiceWorker] ServiceWorkerContainer: Web Workers and Service Workers (#1552) (Friday, 19 February)
• Re: [w3c/ServiceWorker] get importScripts to work offline (#1555) (Friday, 19 February)
• Re: [w3c/ServiceWorker] URL fragments and service workers (#1564) (Friday, 19 February)
• Re: [w3c/ServiceWorker] How can we intercept network requests comes from iframe (#1565) (Friday, 19 February)
• Re: [w3c/ServiceWorker] How can we intercept network requests comes from iframe (#1565) (Friday, 19 February)
• Re: [w3c/ServiceWorker] Use undefined union for getRegistration()/match()/get() (#1559) (Friday, 19 February)
• Re: [w3c/ServiceWorker] Use undefined union for getRegistration()/match()/get() (#1559) (Friday, 19 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return error when request's streaming body is unusable (#1563) (Thursday, 18 February)
• Re: [whatwg/fetch] Tee request body on ServiceWorker interception (#1144) (Thursday, 18 February)
• Re: [whatwg/fetch] Tee request body on ServiceWorker interception (#1144) (Thursday, 18 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return error when request's streaming body is unusable (#1563) (Thursday, 18 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return error when request's streaming body is unusable (#1563) (Thursday, 18 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 10 February)
• Re: [whatwg/fetch] "Return a network error" doesn't seem to go through "process response" (#1164) (Tuesday, 9 February)
• Re: [whatwg/fetch] "Return a network error" doesn't seem to go through "process response" (#1164) (Tuesday, 9 February)
• Re: [whatwg/fetch] "Return a network error" doesn't seem to go through "process response" (#1164) (Tuesday, 9 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Monday, 8 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Monday, 8 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Monday, 8 February)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Monday, 8 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Monday, 8 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Monday, 8 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Monday, 8 February)
• Re: [whatwg/fetch] fetch (#1162) (Sunday, 7 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Sunday, 7 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Sunday, 7 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Saturday, 6 February)
• Re: [w3c/ServiceWorker] [Feature request] Clients should know their own IDs (#1557) (Friday, 5 February)
• Re: [w3c/ServiceWorker] [Feature request] Expose parent client ID for iframe navigations (#1556) (Friday, 5 February)
• Re: [w3c/ServiceWorker] [Feature request] Allow keeping service worker alive (#1558) (Friday, 5 February)
• Re: [w3c/ServiceWorker] [Feature request] Allow keeping service worker alive (#1558) (Friday, 5 February)
• Re: [w3c/ServiceWorker] ephemeral fingerprinting (#1561) (Friday, 5 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Friday, 5 February)
• Re: [heycam/webidl] Making methods more future-proof (#954) (Friday, 5 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Friday, 5 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Friday, 5 February)
• Re: [w3c/ServiceWorker] Clarification on what happens during a terminated activation (#1372) (Friday, 5 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [heycam/webidl] Making methods more future-proof (#954) (Wednesday, 3 February)
• Re: [heycam/webidl] Making methods more future-proof (#954) (Wednesday, 3 February)
• Re: [heycam/webidl] Making methods more future-proof (#954) (Wednesday, 3 February)
• [heycam/webidl] Making methods more future-proof (#954) (Wednesday, 3 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Tuesday, 2 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: en-US is sanitize (#1151) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: en-US is sanitize (#1151) (Tuesday, 2 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)
• Re: [whatwg/fetch] Add abstractions for creating Request and Response objects (#1157) (Monday, 1 February)

James

• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Sunday, 21 February)

James Bromwell

• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Monday, 1 February)

James Browning

• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Sunday, 28 February)
• Re: [w3c/ServiceWorker] Top-level await integration for ServiceWorkers running modules (#1407) (Tuesday, 23 February)
• Re: [w3c/ServiceWorker] Top-level await integration for ServiceWorkers running modules (#1407) (Tuesday, 23 February)
• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Thursday, 11 February)
• Re: [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Thursday, 11 February)
• [whatwg/dom] Allow postMessage-ing AbortSignal (#948) (Thursday, 11 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Monday, 8 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Monday, 8 February)
• Re: [whatwg/dom] Encourage use of AbortError for cancellation? (#927) (Sunday, 7 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Sunday, 7 February)
• Re: [WICG/webcomponents] Scoped Custom Element Registry: Moving elements with shadow roots between documents (#907) (Saturday, 6 February)
• Re: [whatwg/dom] Encourage use of AbortError for cancellation? (#927) (Wednesday, 3 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Wednesday, 3 February)
• Re: [whatwg/dom] Encourage use of AbortError for cancellation? (#927) (Wednesday, 3 February)

James M Snell

• Re: [whatwg/streams] Make read requests abortable (#1103) (Wednesday, 24 February)

Jan Miksovsky

• Re: [WICG/webcomponents] Spring 2021 Virtual Meeting (#911) (Wednesday, 24 February)
• Re: [WICG/webcomponents] 2020 Spring Virtual F2F (#855) (Monday, 1 February)
• [WICG/webcomponents] Spring 2021 Virtual Meeting (#911) (Monday, 1 February)

Jeffrey Yasskin

• [whatwg/storage] Editorial: Remove the <pre class=link-defaults> block. (#123) (Friday, 26 February)
• Re: [whatwg/storage] Editorial: Fix the reference to "persistent-storage". (#122) (Friday, 26 February)
• Re: [whatwg/storage] Editorial: Fix the reference to "persistent-storage". (#122) (Friday, 26 February)
• Re: [w3c/permissions] PermissionName not defined as proper IDL block (#205) (Wednesday, 24 February)
• Re: [w3c/permissions] PermissionName not defined as proper IDL block (#205) (Wednesday, 24 February)
• Re: [whatwg/storage] Editorial: Fix the reference to "persistent-storage". (#122) (Wednesday, 24 February)
• [whatwg/storage] Editorial: Fix the reference to "persistent-storage". (#122) (Wednesday, 24 February)
• Re: [w3c/permissions] Expose PermissionName as IDL (#229) (Wednesday, 17 February)
• Re: [w3c/permissions] Expose PermissionName as IDL (#229) (Wednesday, 17 February)

Jeremy Roman

• [w3ctag/design-reviews] Early Design Review: Speculation Rules (#611) (Tuesday, 16 February)

Jimmy Wärting

• Re: [w3c/ServiceWorker] Make WebRTC usable as a backend for Service Workers to fulfill requests from a peer-to-peer network (#1522) (Saturday, 20 February)
• [w3c/ServiceWorker] A WindowClient close or terminate method perhaps? (#1567) (Saturday, 20 February)
• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Saturday, 20 February)
• Re: [whatwg/dom] Support `AbortSignal`s in `addEventListener`s options to unsubscribe from events? (#911) (Saturday, 6 February)

Joey Arhar

• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Wednesday, 24 February)

Johannes Wilm

• Re: [w3c/editing] [charter] writing systems (#282) (Wednesday, 24 February)
• Re: [w3c/editing] [charter] Define the Success Criteria (#281) (Wednesday, 24 February)
• Re: [w3c/editing] [charter] Propose separating background from scope (#279) (Tuesday, 23 February)
• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Thursday, 11 February)

john carrascal

• Re: [whatwg/url] https://static.xx.fbcdn.net/rsrc.php/v3/yC/l/0,cross/-fkZISYLPQVNi795R-Cp70.css?_nc_x=0vk8E-6IEAK (#578) (Wednesday, 10 February)
• Re: [whatwg/url] https://static.xx.fbcdn.net/rsrc.php/v3/yC/l/0,cross/-fkZISYLPQVNi795R-Cp70.css?_nc_x=0vk8E-6IEAK (#578) (Wednesday, 10 February)
• Re: [whatwg/url] https://static.xx.fbcdn.net/rsrc.php/v3/yC/l/0,cross/-fkZISYLPQVNi795R-Cp70.css?_nc_x=0vk8E-6IEAK (#578) (Wednesday, 10 February)
• [whatwg/url] https://static.xx.fbcdn.net/rsrc.php/v3/yC/l/0,cross/-fkZISYLPQVNi795R-Cp70.css?_nc_x=0vk8E-6IEAK (#578) (Wednesday, 10 February)

John Liu

• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 2 February)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 2 February)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 2 February)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 2 February)

johnrommelcarrascal

• [whatwg/fetch] fetch (#1162) (Sunday, 7 February)

Jonas Sicking

• Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Saturday, 13 February)

Joshua Bell

• Re: [w3c/ServiceWorker] Cache API: Cache-Control headers and Opaque Responses (#1299) (Wednesday, 24 February)
• Re: [w3c/ServiceWorker] Cache API: Cache-Control headers and Opaque Responses (#1299) (Wednesday, 24 February)
• Re: [w3c/IndexedDB] CFC to publish FPWD (#348) (Wednesday, 24 February)
• Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280) (Monday, 1 February)
• Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280) (Monday, 1 February)
• Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280) (Monday, 1 February)
• Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280) (Monday, 1 February)

Jun

• Re: [w3c/FileAPI] "Null"ing out the Origin of a BLOB (#74) (Wednesday, 17 February)

Justin Fagnani

• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 27 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 27 February)
• Re: [WICG/webcomponents] Spring 2021 Virtual Meeting (#911) (Friday, 26 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Friday, 26 February)
• Re: [WICG/webcomponents] Using attributes as properties (#913) (Friday, 26 February)
• Re: [WICG/webcomponents] Why is Chrome Platform Status reporting 70% usage for HTMLSlotElement? (#912) (Thursday, 4 February)
• Re: [WICG/webcomponents] Spring 2021 Virtual Meeting (#911) (Wednesday, 3 February)

Kagami Sascha Rosylight

• Re: [w3c/permissions] Remove clipboard-read from PermissionName (#228) (Wednesday, 17 February)
• Re: [w3c/permissions] Expose PermissionName as IDL (#229) (Wednesday, 17 February)
• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Wednesday, 10 February)
• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Tuesday, 9 February)

Karl

• Re: [whatwg/url] [Editorial] Guarantee that strings encoded with the component encode-set are valid opaque host strings. (#584) (Wednesday, 24 February)
• Re: [whatwg/url] Prevent the pathname setter from erasing the path of path-only URLs, … (#582) (Wednesday, 24 February)
• Re: [whatwg/url] [Editorial] Guarantee that strings encoded with the component encode-set are valid opaque host strings. (#584) (Wednesday, 24 February)
• [whatwg/url] [Editorial] Guarantee that strings encoded with the component encode-set are valid opaque host strings. (#584) (Wednesday, 24 February)
• Re: [whatwg/url] Prevent the pathname setter from erasing the path of path-only URLs, … (#582) (Monday, 22 February)
• Re: [whatwg/url] Prevent the pathname setter from erasing the path of path-only URLs, … (#582) (Monday, 22 February)
• Re: [whatwg/url] Prevent the pathname setter from erasing the path of path-only URLs, … (#582) (Sunday, 21 February)
• [whatwg/url] Prevent the pathname setter from erasing the path of path-only URLs, … (#582) (Sunday, 21 February)
• [whatwg/url] Path setter allows cannot-be-a-base URL to be created without the flag (#581) (Sunday, 21 February)

Keith Cirkel

• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Thursday, 25 February)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] Honor media attribute (#955) (Friday, 26 February)
• Re: [w3c/manifest] `display-mode` CSS media feature should include `"display_override"` values (#952) (Thursday, 18 February)
• Re: [w3c/manifest] `display-mode` CSS media feature should include `"display_override"` values (#952) (Thursday, 18 February)
• Re: [w3c/manifest] Add a "tabbed application" mode (#737) (Thursday, 18 February)
• Re: [w3c/manifest] `display-mode` CSS media feature should include `"display_override"` values (#952) (Thursday, 18 February)
• Re: [w3c/manifest] `display-mode` CSS media feature should include `"display_override"` values (#952) (Thursday, 18 February)
• Re: [w3c/manifest] `display-mode` CSS media feature should include `"display_override"` values (#952) (Thursday, 18 February)
• Re: [w3c/manifest] `display-mode` CSS media feature should include `"display_override"` values (#952) (Thursday, 18 February)
• Re: [w3c/manifest] Add a "tabbed application" mode (#737) (Tuesday, 16 February)
• Re: [w3c/manifest] Add a "tabbed application" mode (#737) (Tuesday, 16 February)
• Re: [w3ctag/design-reviews] Media Session: video conferencing actions (#608) (Tuesday, 16 February)
• Re: [w3ctag/design-reviews] Support seeking past the end of a file in the File System Access API (#600) (Tuesday, 16 February)
• Re: [w3ctag/design-reviews] CSS Scrollbars: scrollbar-color, scrollbar-width (#563) (Tuesday, 16 February)
• Re: [w3ctag/design-reviews] Reporting (#585) (Monday, 15 February)
• Re: [w3ctag/design-reviews] hasDroppedEntry in PerformanceObserverCallback (#547) (Tuesday, 9 February)
• Re: [w3ctag/design-reviews] Periodic Background Sync (#367) (Tuesday, 9 February)

kheldorn

• Re: [whatwg/fetch] Allow more flexibility in how 401s/407s are handled? (#1132) (Monday, 1 February)

Kornel

• Re: [whatwg/fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179) (Thursday, 25 February)

Kyle Simpson

• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Sunday, 7 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Sunday, 7 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Saturday, 6 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Saturday, 6 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)
• Re: [whatwg/dom] Expose an `aborted` promise on AbortSignal? (#946) (Thursday, 4 February)

L. David Baron

• Re: [w3ctag/design-reviews] VisibilityStateEntry (#534) (Tuesday, 2 February)

Lea Verou

• Re: [w3ctag/design-reviews] Early design review of Cascade Layers (#597) (Monday, 22 February)
• Re: [w3ctag/design-reviews] Early design review of Cascade Layers (#597) (Monday, 22 February)
• Re: [w3ctag/design-reviews] HTMLPopupElement - <popup> (#599) (Thursday, 18 February)
• Re: [w3ctag/design-reviews] inert attribute (#610) (Tuesday, 16 February)
• Re: [w3ctag/design-reviews] Early TAG design review for captureTab (#609) (Tuesday, 16 February)
• Re: [w3ctag/design-reviews] Early design review of CSS Container Queries proposal (#592) (Monday, 15 February)
• Re: [w3ctag/design-reviews] Early design review of CSS Container Queries proposal (#592) (Monday, 15 February)
• Re: [w3ctag/design-reviews] Review for CSS property "aspect-ratio" (#559) (Monday, 15 February)
• Re: [w3ctag/design-reviews] Review for CSS property "aspect-ratio" (#559) (Monday, 15 February)
• [w3ctag/design-reviews] "API Design Principles" to "Web Platform Design Principles" (#607) (Tuesday, 9 February)
• Re: [w3ctag/design-reviews] hasDroppedEntry in PerformanceObserverCallback (#547) (Tuesday, 9 February)
• Re: [w3ctag/design-reviews] HTMLPopupElement - <popup> (#599) (Wednesday, 3 February)
• Re: [w3ctag/design-reviews] Early design review of light-DOM CSS Scope proposal (#593) (Monday, 1 February)

Leo Balter

• Re: [WICG/webcomponents] Spring 2021 Virtual Meeting (#911) (Monday, 1 February)

Marc G.

• Re: [whatwg/fetch] Add timeout option (#20) (Thursday, 25 February)
• Re: [whatwg/fetch] Add timeout option (#20) (Thursday, 25 February)
• Re: [whatwg/fetch] Add timeout option (#20) (Thursday, 25 February)
• Re: [whatwg/fetch] Add timeout option (#20) (Thursday, 25 February)

Marcos Cáceres

• Re: [w3c/manifest] Honor media attribute (#955) (Friday, 26 February)
• Re: [w3c/manifest] auto value of the dir member (#923) (Wednesday, 24 February)
• Re: [w3c/manifest] Editorial: clarify when/how 'auto' is applied (#926) (Wednesday, 24 February)
• Re: [w3c/manifest] Honor media attribute (#955) (Wednesday, 24 February)
• Re: [w3c/FileAPI] TPAC planning and specification status report (#156) (Wednesday, 24 February)
• Re: [w3c/selection-api] TPAC planning and specification status report (#122) (Wednesday, 24 February)
• Re: [w3ctag/design-reviews] Web Share API review (#554) (Wednesday, 24 February)
• Re: [w3c/push-api] TPAC planning and specification status report (#326) (Wednesday, 24 February)
• Re: [w3c/IndexedDB] CFC to publish FPWD (#348) (Wednesday, 24 February)
• Re: [w3c/IndexedDB] Specification status report for TPAC 2020 (#338) (Wednesday, 24 February)
• Re: [w3c/IndexedDB] Specification status report for TPAC 2020 (#338) (Wednesday, 24 February)
• Re: [w3c/IndexedDB] TPAC planning and specification status report (#337) (Wednesday, 24 February)
• Re: [w3c/IndexedDB] CFC to publish FPWD (#348) (Wednesday, 24 February)
• [w3c/IndexedDB] CFC to publish FPWD (#348) (Tuesday, 23 February)
• Re: [w3c/manifest] TPAC planning and specification status report (#906) (Monday, 22 February)
• Re: [w3c/manifest] Spec Metadata Lists Incorrect Values for Chrome (#939) (Wednesday, 17 February)

Marijn Kruisselbrink

• Re: [w3ctag/design-reviews] Support seeking past the end of a file in the File System Access API (#600) (Tuesday, 16 February)
• Re: [w3ctag/design-reviews] Support seeking past the end of a file in the File System Access API (#600) (Tuesday, 16 February)

Mark Nottingham

• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Tuesday, 2 February)
• Re: [whatwg/fetch] Define RST_STREAM's error code (#637) (Monday, 1 February)

Masayuki Nakano

• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Wednesday, 10 February)
• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Wednesday, 10 February)
• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Monday, 1 February)

Mason Freed

• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Wednesday, 24 February)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Friday, 19 February)
• Re: [WICG/webcomponents] Why is Chrome Platform Status reporting 70% usage for HTMLSlotElement? (#912) (Thursday, 18 February)
• Re: [w3ctag/design-reviews] HTMLPopupElement - <popup> (#599) (Thursday, 18 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#831) (Thursday, 4 February)

Mathias Bynens

• Re: [heycam/webidl] fix: Remove raw percentage character from ID (#955) (Tuesday, 9 February)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] Clarification on what happens during a terminated activation (#1372) (Friday, 19 February)
• Re: [w3c/ServiceWorker] How can we intercept network requests comes from iframe (#1565) (Sunday, 14 February)

Matt Giuca

• Re: [w3ctag/design-reviews] Declarative Link Capturing (#589) (Friday, 26 February)
• Re: [w3c/manifest] Editorial: Created explicit algorithm for choosing display mode, and add extension point for the display_override incubation. (#949) (Monday, 8 February)

Matt Menke

• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Saturday, 27 February)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Saturday, 27 February)
• Re: [whatwg/fetch] HTTP/1 parsing (#1156) (Wednesday, 3 February)
• Re: [whatwg/fetch] Acting on incomplete headers (#472) (Wednesday, 3 February)
• Re: [whatwg/fetch] Clarify what a status is (#1159) (Monday, 1 February)
• Re: [whatwg/fetch] HTTP/1 parsing (#1156) (Monday, 1 February)

Mattias Buelens

• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Thursday, 25 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return error when request's streaming body is unusable (#1563) (Wednesday, 17 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Friday, 12 February)
• Re: [whatwg/fetch] Use a ReadableStream with byte source (formerly called ReadableByteStream) for .body (#267) (Friday, 12 February)
• Re: [whatwg/streams] ReadableStream.from(asyncIterable) (#1083) (Monday, 8 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Monday, 8 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Monday, 8 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Monday, 8 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Sunday, 7 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Sunday, 7 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Sunday, 7 February)
• Re: [whatwg/streams] Settle reader.[[closedPromise]] before performing close/error steps of read requests (#1102) (Thursday, 4 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Tuesday, 2 February)
• Re: [whatwg/streams] Introspection: disturbed or locked (#1105) (Monday, 1 February)

mbrodesser

• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Thursday, 25 February)
• [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Tuesday, 16 February)
• Re: [w3c/uievents] mousemove and preventDefault() (#278) (Thursday, 11 February)

Md_ZubairAhmed

• Re: [whatwg/fetch] Handle blob URLs without a backing blob (#1077) (Thursday, 4 February)

Melanie Richards

• Re: [w3ctag/design-reviews] HTMLPopupElement - <popup> (#599) (Thursday, 25 February)

Michael Puckett

• Re: [w3c/DOM-Parsing] Serializing DOM as rendered, including Shadow DOM (#58) (Friday, 26 February)

Michael[tm] Smith

• Re: [whatwg/dom] Support `AbortSignal`s in `addEventListener`s options to unsubscribe from events? (#911) (Sunday, 28 February)
• [whatwg/dom] Editorial: Restore necessary comma (#954) (Sunday, 28 February)
• Re: [whatwg/fetch] Clarify RequestInit/credentials affects response (#1178) (Saturday, 27 February)
• Re: [whatwg/fetch] Clarify RequestInit/credentials affects response (#1178) (Saturday, 27 February)
• [whatwg/fetch] Clarify RequestInit/credentials affects response (#1178) (Saturday, 20 February)
• Re: [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• Re: [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• Re: [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• Re: [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• [whatwg/fetch] Clarify: credentials param affect response too (#1174) (Friday, 19 February)
• Re: [whatwg/fetch] Clarify cors requests need cors response tainting (#1170) (Wednesday, 17 February)
• Re: [whatwg/fetch] Clarify cors requests need cors response tainting (#1170) (Wednesday, 17 February)
• Re: [whatwg/fetch] Clarify cors requests need cors response tainting (#1170) (Wednesday, 17 February)
• Re: [whatwg/fetch] Clarify cors requests need cors response tainting (#1170) (Wednesday, 17 February)
• [whatwg/fetch] Clarify cors requests need cors response tainting (#1170) (Tuesday, 16 February)
• Re: [whatwg/fetch] Overhaul how standards integrate with fetch (#1165) (Friday, 12 February)
• Re: [WICG/webcomponents] 2020 Spring Virtual F2F (#855) (Tuesday, 2 February)
• Re: [WICG/webcomponents] 2020 Spring Virtual F2F (#855) (Tuesday, 2 February)

Mike West

• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Tuesday, 16 February)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Tuesday, 16 February)
• Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546) (Tuesday, 16 February)
• Re: [w3ctag/design-reviews] "credentialless" embedder policy. (#582) (Monday, 8 February)

mircerlancerous

• Re: [w3c/ServiceWorker] Remove foreign fetch (#1188) (Tuesday, 16 February)

Miriam Suzanne

• Re: [w3ctag/design-reviews] Early design review of Cascade Layers (#597) (Monday, 22 February)
• Re: [w3ctag/design-reviews] Early design review of light-DOM CSS Scope proposal (#593) (Monday, 1 February)

Mork8888

• Re: [WICG/webcomponents] Spring 2021 Virtual Meeting (#911) (Wednesday, 24 February)

Mounir Lamouri

• Re: [w3ctag/design-reviews] Media Session: video conferencing actions (#608) (Thursday, 25 February)
• Re: [w3ctag/design-reviews] Media Session: video conferencing actions (#608) (Tuesday, 16 February)
• Re: [w3ctag/design-reviews] Media Session: video conferencing actions (#608) (Tuesday, 16 February)
• [w3ctag/design-reviews] Media Session: video conferencing actions (#608) (Friday, 12 February)

mseddon

• Re: [w3c/manifest] Confusing use of MAY and SHOULD (#948) (Wednesday, 3 February)

mugdhalakhani

• Re: [w3ctag/design-reviews] Periodic Background Sync (#367) (Tuesday, 9 February)
• Re: [w3ctag/design-reviews] Periodic Background Sync (#367) (Tuesday, 9 February)

Mаартен - Maarten

• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Monday, 22 February)
• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Monday, 22 February)

Naheulf

• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Thursday, 11 February)
• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Wednesday, 10 February)

natyuiop009

• Re: [w3c/push-api] chore(CONTRIBUTING.md): update text for WebAppsWG (eda4fe0) (Saturday, 20 February)
• Re: [w3c/push-api] chore(CONTRIBUTING.md): update text for WebAppsWG (eda4fe0) (Saturday, 20 February)
• Re: [w3c/push-api] chore(CONTRIBUTING.md): update text for WebAppsWG (eda4fe0) (Saturday, 20 February)

Nick Schonning

• [heycam/webidl] fix: Escape space in issue link template URL (#956) (Sunday, 7 February)
• Re: [heycam/webidl] fix: Remove raw percentage character from ID (#955) (Saturday, 6 February)
• [heycam/webidl] fix: Remove raw percentage character from ID (#955) (Saturday, 6 February)

nightpool

• Re: [w3ctag/design-reviews] Managed Device Web API (#606) (Sunday, 7 February)

npm1

• Re: [w3ctag/design-reviews] hasDroppedEntry in PerformanceObserverCallback (#547) (Tuesday, 9 February)
• Re: [w3ctag/design-reviews] VisibilityStateEntry (#534) (Tuesday, 2 February)
• Re: [w3ctag/design-reviews] VisibilityStateEntry (#534) (Tuesday, 2 February)
• Re: [whatwg/fetch] ResourceTiming integration question: how to handle iframes (#968) (Monday, 1 February)
• Re: [whatwg/fetch] ResourceTiming integration question: how to handle iframes (#968) (Monday, 1 February)
• Re: [whatwg/fetch] ResourceTiming integration question: how to handle iframes (#968) (Monday, 1 February)
• Re: [whatwg/fetch] ResourceTiming integration question: how to handle iframes (#968) (Monday, 1 February)
• Re: [whatwg/fetch] ResourceTiming integration question: how to handle iframes (#968) (Monday, 1 February)

OstraMrN

• Re: [heycam/webidl] Intent to use Constants (#960) (Sunday, 28 February)
• [heycam/webidl] Intent to use Constants (#960) (Sunday, 28 February)

Patrick H. Lauke

• Re: [w3c/uievents] [feature request] Standardize long press touch event (#291) (Tuesday, 16 February)
• Re: [w3c/touch-events] [feature request] Standardize long press touch event (#109) (Tuesday, 16 February)
• Re: [w3c/touch-events] [feature request] Standardize long press touch event (#109) (Tuesday, 16 February)

Pauan

• Re: [whatwg/dom] Add AbortSignal.timeout(ms) (#951) (Thursday, 25 February)

Paul Adenot

• Re: [w3ctag/design-reviews] WebCodecs (again!) (#612) (Friday, 19 February)

Peter Linss

• Re: [w3ctag/design-reviews] Screen Fold API (#575) (Tuesday, 23 February)
• Re: [w3ctag/design-reviews] Screen Fold API (#575) (Tuesday, 23 February)
• Re: [w3ctag/design-reviews] Screen Fold API (#575) (Tuesday, 23 February)
• Re: [w3ctag/design-reviews] CSS overflow: clip and overflow-clip-margin (#579) (Tuesday, 16 February)
• Re: [w3ctag/design-reviews] "API Design Principles" to "Web Platform Design Principles" (#607) (Wednesday, 10 February)
• Re: [w3ctag/design-reviews] "API Design Principles" to "Web Platform Design Principles" (#607) (Wednesday, 10 February)

Philip Jägenstedt

• [w3c/uievents] Add default value {} to optional eventInitDict arguments (#292) (Wednesday, 17 February)
• Re: [w3c/permissions] Expose PermissionName as IDL (#229) (Wednesday, 3 February)

Piotr Perzyna

• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Tuesday, 2 February)

r12a

• Re: [w3c/editing] [charter] Define the Success Criteria (#281) (Wednesday, 24 February)

ralphch0

• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Friday, 12 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Friday, 5 February)

Raphael Kubo da Costa

• Re: [heycam/webidl] Cannot resolve/reject a promise in parallel (#953) (Tuesday, 2 February)

Reilly Grant

• Re: [w3c/gamepad] Add permission policy integration (#112) (Tuesday, 9 February)
• Re: [w3ctag/design-reviews] Serial API (#431) (Tuesday, 9 February)

restspace

• Re: [w3c/ServiceWorker] Remove foreign fetch (#1188) (Thursday, 11 February)

Rob Dodson

• Re: [w3ctag/design-reviews] inert attribute (#610) (Wednesday, 17 February)

Ron Buckton

• Re: [heycam/webidl] Making methods more future-proof (#954) (Wednesday, 3 February)

Rossen Atanassov

• Re: [w3ctag/design-reviews] WebXR Layers (#528) (Monday, 15 February)
• Re: [w3ctag/design-reviews] WebXR Layers (#528) (Monday, 15 February)
• Re: [w3ctag/design-reviews] WebXR Hit Test Module (#463) (Monday, 8 February)

Ruben Vreeken

• Re: [w3ctag/design-reviews] CSS Scrollbars: scrollbar-color, scrollbar-width (#563) (Thursday, 25 February)
• Re: [w3ctag/design-reviews] CSS Scrollbars: scrollbar-color, scrollbar-width (#563) (Wednesday, 24 February)
• Re: [w3ctag/design-reviews] CSS Scrollbars: scrollbar-color, scrollbar-width (#563) (Wednesday, 24 February)
• Re: [w3ctag/design-reviews] CSS Scrollbars: scrollbar-color, scrollbar-width (#563) (Wednesday, 24 February)

Ryosuke Niwa

• Re: [WICG/webcomponents] Using attributes as properties (#913) (Saturday, 27 February)
• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Saturday, 27 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 27 February)
• Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909) (Saturday, 27 February)
• Re: [WICG/webcomponents] Spring 2021 Virtual Meeting (#911) (Thursday, 25 February)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Wednesday, 24 February)
• Re: [whatwg/dom] Add Imperative Slot API (#860) (Tuesday, 23 February)
• Re: [whatwg/dom] Add Imperative Slot API (#860) (Tuesday, 23 February)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Saturday, 20 February)
• Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Friday, 19 February)
• Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754) (Friday, 19 February)
• Re: [whatwg/dom] Add declarative Shadow DOM features (#892) (Friday, 19 February)
• Re: [WICG/webcomponents] Why is Chrome Platform Status reporting 70% usage for HTMLSlotElement? (#912) (Thursday, 18 February)
• Re: [WICG/webcomponents] Why is Chrome Platform Status reporting 70% usage for HTMLSlotElement? (#912) (Thursday, 18 February)
• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Tuesday, 16 February)
• Re: [w3c/clipboard-apis] Specify order of flavors exported to macOS's pasteboard (#137) (Tuesday, 16 February)
• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Friday, 5 February)

Sanket Joshi

• Re: [whatwg/dom] Define criteria for StaticRange validation (#947) (Thursday, 11 February)
• Re: [whatwg/dom] Define criteria for StaticRange validation (#947) (Thursday, 11 February)
• Re: [whatwg/dom] Define criteria for StaticRange validation (#947) (Thursday, 11 February)
• [whatwg/dom] Define criteria for StaticRange validation (#947) (Thursday, 11 February)

sky2

• Re: [w3ctag/design-reviews] CSS overflow: clip and overflow-clip-margin (#579) (Tuesday, 16 February)

slaneyrw

• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Wednesday, 24 February)
• Re: [whatwg/fetch] Header to opt out of opaque redirect (#601) (Wednesday, 24 February)

sleevi

• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Sunday, 28 February)
• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Sunday, 28 February)
• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Sunday, 28 February)
• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Saturday, 27 February)
• Re: [whatwg/fetch] Promp for/send TLS client certificates for CORS preflights (#1181) (Saturday, 27 February)

smaug----

• Re: [whatwg/dom] Define criteria for StaticRange validation (#947) (Thursday, 11 February)

snianu

• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Thursday, 11 February)

Stephen Checkoway

• Re: [whatwg/encoding] End-of-queue during decoding of GB18030 should not mask ASCII characters. (#253) (Thursday, 25 February)
• Re: [whatwg/encoding] End-of-queue during decoding of GB18030 should not mask ASCII characters. (#253) (Wednesday, 24 February)
• [whatwg/encoding] End-of-queue during decoding of GB18030 should not mask ASCII characters. (#253) (Wednesday, 24 February)

Steve Agoston

• Re: [w3c/gamepad] Add gamepad light indicator extension (#143) (Friday, 26 February)

Steven Luscher

• Re: [w3c/editing] Different browser behaviors when moving the caret by one word. (#278) (Tuesday, 9 February)

sunggook

• [w3c/manifest] The current PWA id (app_id) is used for system integration (tile, taskbar) (#953) (Thursday, 18 February)

Suriya2540

• [heycam/webidl] Intent to use bigint/numeric union (#959) (Thursday, 25 February)

suryadevelope

• Re: [w3c/ServiceWorker] How can we intercept network requests comes from iframe (#1565) (Saturday, 13 February)
• [w3c/ServiceWorker] How can we intercept network requests comes from iframe (#1565) (Thursday, 11 February)

Tab Atkins Jr.

• Re: [whatwg/fetch] "A status is a code" doesn't actually mean anything (#1142) (Monday, 1 February)
• Re: [whatwg/fetch] Clarify what a status is (#1159) (Monday, 1 February)
• Re: [whatwg/fetch] Clarify what a status is (#1159) (Monday, 1 February)

TaTaRsKiY059

• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Wednesday, 3 February)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Wednesday, 3 February)

Thaina Yu

• [w3c/uievents] [feature request] Standardize long press touch event (#291) (Tuesday, 16 February)
• Re: [w3c/touch-events] [feature request] Standardize long press touch event (#109) (Tuesday, 16 February)
• [w3c/touch-events] [feature request] Standardize long press touch event (#109) (Tuesday, 16 February)

Thomas Steiner

• Re: [w3c/manifest] Honor media attribute (#955) (Friday, 26 February)
• Re: [w3c/manifest] Honor media attribute (#955) (Friday, 26 February)
• Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954) (Tuesday, 23 February)
• Re: [w3c/manifest] Add a "tabbed application" mode (#737) (Tuesday, 23 February)
• Re: [w3c/manifest] Add a "tabbed application" mode (#737) (Monday, 22 February)
• [w3c/manifest] `display-mode` CSS media feature should include `"display_override"` values (#952) (Thursday, 18 February)
• Re: [w3c/manifest] Add a "tabbed application" mode (#737) (Tuesday, 16 February)
• Re: [w3c/manifest] Add a "tabbed application" mode (#737) (Tuesday, 16 February)
• Re: [whatwg/streams] Typo fix (#1099) (Tuesday, 9 February)
• Re: [whatwg/streams] Does `ReadableStream.values()` need a proper definition? (#1107) (Wednesday, 3 February)
• [whatwg/streams] Does `ReadableStream.values()` need a proper definition? (#1107) (Wednesday, 3 February)

Timothy Gu

• Re: [heycam/webidl] Cannot resolve/reject a promise in parallel (#953) (Tuesday, 2 February)

Titouan Rigoudy

• Re: [w3ctag/design-reviews] CORS-RFC1918 (#572) (Wednesday, 24 February)

triple-underscore

• Re: [whatwg/fetch] Align redirect fragment handling with HTTP (#696) (Friday, 26 February)

vrugtehagel

• Re: [whatwg/dom] [idea] Node.empty() (#955) (Sunday, 28 February)
• Re: [whatwg/dom] [idea] Node.empty() (#955) (Sunday, 28 February)
• [whatwg/dom] [idea] HTMLElement.empty() (#955) (Sunday, 28 February)
• Re: [WICG/webcomponents] Using attributes as properties (#913) (Saturday, 27 February)
• [WICG/webcomponents] Using attributes as properties (#913) (Friday, 26 February)

Wendy Seltzer

• Re: [w3c/editing] [charter] writing systems (#282) (Wednesday, 24 February)
• [w3c/editing] [charter] writing systems (#282) (Wednesday, 24 February)
• [w3c/editing] [charter] Propose separating background from scope (#279) (Tuesday, 23 February)

Xiaoqian Wu

• Re: [w3c/editing] [charter] writing systems (#282) (Wednesday, 24 February)
• Re: [w3c/editing] [charter] Define the Success Criteria (#281) (Wednesday, 24 February)
• [w3c/editing] [charter] Define the Success Criteria (#281) (Wednesday, 24 February)
• [w3c/editing] [Charter]Information about Timeline and Expected Completion is missing (#280) (Wednesday, 24 February)
• Re: [w3c/editing] [charter] Propose separating background from scope (#279) (Tuesday, 23 February)
• Re: [w3c/editing] add draft charter for the future Editing WG (#276) (Tuesday, 23 February)
• Re: [w3c/editing] add draft charter for the future Editing WG (#276) (Tuesday, 23 February)
• Re: [w3c/editing] add draft charter for the future Editing WG (#276) (Tuesday, 23 February)

Yajing Tang

• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 18 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 18 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 18 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Tuesday, 16 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Tuesday, 9 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Friday, 5 February)
• Re: [w3c/manifest] Add a unique identifier for a PWA (#586) (Thursday, 4 February)
• Re: [w3c/manifest] Change the default value for start_url (#670) (Wednesday, 3 February)
• Re: [w3c/manifest] Relationship between nestedly scoped web app manifests? (#539) (Tuesday, 2 February)

Yoichi Osato

• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Friday, 26 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Thursday, 25 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Thursday, 25 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Wednesday, 24 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Wednesday, 24 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Wednesday, 24 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Wednesday, 24 February)
• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Thursday, 18 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Wednesday, 17 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Monday, 15 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Tuesday, 9 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Tuesday, 9 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Tuesday, 9 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Monday, 8 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Monday, 8 February)
• Re: [whatwg/fetch] Editorial: rename keepalive flag to keepalive (#1152) (Wednesday, 3 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Wednesday, 3 February)
• Re: [whatwg/fetch] Editorial: rename keepalive flag to keepalive (#1152) (Tuesday, 2 February)
• Re: [whatwg/fetch] Streams based uploading with Content-Length (not chunked encoding) (#95) (Tuesday, 2 February)
• Re: [whatwg/fetch] Editorial: rename keepalive flag to keepalive (#1152) (Tuesday, 2 February)
• Re: [whatwg/fetch] Define behavior in the presence of TLS Early Data (#888) (Tuesday, 2 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Tuesday, 2 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Tuesday, 2 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Tuesday, 2 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Monday, 1 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Monday, 1 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Monday, 1 February)
• Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141) (Monday, 1 February)

youennf

• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Saturday, 27 February)
• Re: [whatwg/fetch] Add port blocking for tftp, netbios-ns, snmp, rtsp, h323gatestat, h32… (#1148) (Thursday, 4 February)

Yutaka Hirano

• Re: [whatwg/xhr] Use Fetch's body read algorithms (#313) (Thursday, 25 February)
• [whatwg/xhr] Handle error while reading response body in synchronous XHR (#314) (Thursday, 25 February)
• Re: [whatwg/xhr] Use Fetch's body read algorithms (#313) (Thursday, 25 February)
• Re: [whatwg/fetch] Give all bodies a stream (#1177) (Wednesday, 24 February)
• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Wednesday, 24 February)
• Re: [whatwg/fetch] Formalize reading bodies (#1172) (Friday, 19 February)
• Re: [whatwg/fetch] Tee request body on ServiceWorker interception (#1144) (Thursday, 18 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return error when request's streaming body is unusable (#1563) (Thursday, 18 February)
• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Thursday, 18 February)
• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Thursday, 18 February)
• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Thursday, 18 February)
• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Thursday, 18 February)
• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Thursday, 18 February)
• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Thursday, 18 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return error when request's streaming body is unusable (#1563) (Thursday, 18 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return error when request's streaming body is unusable (#1563) (Thursday, 18 February)
• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Wednesday, 17 February)
• Re: [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Wednesday, 17 February)
• [whatwg/fetch] Add more parameters to "obtain a connection" (#1171) (Wednesday, 17 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return error when request's streaming body is unusable (#1563) (Wednesday, 17 February)
• Re: [whatwg/fetch] Body should not be transmitted if service worker intercepts request (#572) (Wednesday, 17 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 17 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 17 February)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Wednesday, 17 February)
• Re: [whatwg/fetch] Body should not be transmitted if service worker intercepts request (#572) (Wednesday, 17 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 16 February)
• Re: [whatwg/fetch] Body should not be transmitted if service worker intercepts request (#572) (Tuesday, 16 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Tuesday, 16 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 16 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Tuesday, 16 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Tuesday, 16 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Tuesday, 16 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Tuesday, 16 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 16 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 16 February)
• Re: [whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167) (Friday, 12 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Friday, 12 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 9 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 9 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Tuesday, 9 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• Re: [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• [w3c/ServiceWorker] Have "Handle Fetch" return the request body in addition to response (#1563) (Monday, 8 February)
• Re: [w3c/ServiceWorker] Define settings object's cross-origin isolated capability for SW (#1545) (Monday, 8 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Friday, 5 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Friday, 5 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Thursday, 4 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Thursday, 4 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 3 February)
• Re: [whatwg/fetch] Fail request when its streaming body is used in ServiceWorker (#1144) (Wednesday, 3 February)
• Re: [whatwg/fetch] Request.headers is shared across Requests. Is it OK? (#1075) (Monday, 1 February)
• Re: [whatwg/fetch] Request.headers is shared across Requests. Is it OK? (#1075) (Monday, 1 February)
• Re: [whatwg/fetch] Editorial: Body mixin cleanup (#1155) (Monday, 1 February)

Yves Lafon

• Re: [w3ctag/design-reviews] Storage Buckets API (#562) (Tuesday, 16 February)
• Re: [w3c/ServiceWorker] Create gentlejack (#1081) (Thursday, 4 February)

zamfofex

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

Борис Верховский

• Re: [whatwg/url] Proposal of .toString({ concise: true }) for nicer output with empty values (#469) (Friday, 12 February)

Last message date: Sunday, 28 February 2021 22:27:09 UTC