public-webapps-github@w3.org from April 2018 by author

Adam Barth

• Re: [whatwg/fetch] From-Origin (#687) (Tuesday, 3 April)

Adam Rice

• Re: [whatwg/streams] Revise property access order (#922) (Tuesday, 24 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Tuesday, 24 April)
• [whatwg/streams] Fix internal links for class ReadableStreamBYOBRequest (#923) (Tuesday, 24 April)
• Re: [whatwg/streams] Revise property access order (#922) (Tuesday, 24 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Tuesday, 24 April)
• Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Tuesday, 24 April)
• Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Tuesday, 24 April)
• Re: [whatwg/streams] Add two demos using streams for PNG manipulation (#911) (Monday, 23 April)
• Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Monday, 23 April)
• Re: [whatwg/streams] Could a byte stream read directly into and out of a SAB (w/o transfer)? (#757) (Monday, 23 April)
• Re: [whatwg/streams] Add two demos using streams for PNG manipulation (#911) (Friday, 20 April)
• Re: [whatwg/streams] Revise property access order (#922) (Friday, 13 April)
• Re: [whatwg/streams] Revise property access order (#922) (Friday, 13 April)
• [whatwg/streams] Revise property access order (#922) (Friday, 13 April)
• [whatwg/streams] Numeric conversion is not done on autoAllocateChunkSize (#921) (Thursday, 12 April)
• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 10 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Monday, 9 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Monday, 9 April)
• Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Friday, 6 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Friday, 6 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Thursday, 5 April)
• Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Thursday, 5 April)
• Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Thursday, 5 April)
• Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Thursday, 5 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Wednesday, 4 April)
• [whatwg/streams] What are the preconditions for ReadableStreamDefaultControllerError? (#920) (Wednesday, 4 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Tuesday, 3 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• [whatwg/streams] Assert that desiredSize is non-null in ReadableStreamDefaultControllerShouldCallPull (#919) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• [whatwg/streams] Fix a reference to [[queueSize]] (#918) (Monday, 2 April)

Alex Russell

• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Tuesday, 17 April)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Transform Streams (#211) (Thursday, 5 April)
• Re: [w3ctag/design-reviews] Transform Streams (#211) (Thursday, 5 April)
• Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Thursday, 5 April)
• Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Thursday, 5 April)
• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Thursday, 5 April)

Alfred Myers

• [w3c/manifest] Minor text tweaks (#664) (Tuesday, 3 April)

Anatoli Babenia

• Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Monday, 30 April)
• Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Monday, 30 April)
• Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Monday, 30 April)

Andrea Giammarchi

• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Friday, 27 April)
• Re: [w3c/uievents] Standardizing event.layerX and event.layerY (#193) (Thursday, 5 April)
• Re: [w3c/uievents] Standardizing event.layerX and event.layerY (#193) (Thursday, 5 April)
• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Thursday, 5 April)
• [w3c/uievents] Standardizing event.layerX and event.layerY (#193) (Thursday, 5 April)

Andrea Puddu

• [w3c/uievents] [Question] select change + mousedown behavior (#201) (Tuesday, 10 April)

Andrew Betts

• Re: [w3ctag/design-reviews] Clear Site Data (#62) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Web Locks API (#217) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Web Locks API (#217) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Payment Handler (#231) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Payment Handler (#231) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Saturday, 7 April)

Andrew Sutherland

• Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234) (Monday, 16 April)

Anne van Kesteren

• Re: [whatwg/dom] Introduce "remove all event listeners" primitive (#641) (Monday, 30 April)
• Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Monday, 30 April)
• Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Monday, 30 April)
• Re: [whatwg/url] UrlSearchParams.set stringifier clarification (#383) (Monday, 30 April)
• Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643) (Monday, 30 April)
• Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624) (Monday, 30 April)
• Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643) (Monday, 30 April)
• Re: [whatwg/dom] "Otherwise, if hasSeenCurrentTarget is true and ..." (#642) (Sunday, 29 April)
• Re: [whatwg/dom] "Otherwise, if hasSeenCurrentTarget is true and ..." (#642) (Sunday, 29 April)
• Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552) (Saturday, 28 April)
• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Friday, 27 April)
• Re: [whatwg/fetch] From-Origin (#687) (Friday, 27 April)
• Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226) (Friday, 27 April)
• Re: [whatwg/dom] Introduce "remove an event listener" primitive (#641) (Friday, 27 April)
• [whatwg/dom] Introduce "remove an event listener" primitive (#641) (Friday, 27 April)
• [whatwg/dom] document.open()'s mutation event suprression (#640) (Friday, 27 April)
• Re: [whatwg/fetch] WindowOrWorkerGlobalScope is a mixin (#719) (Friday, 27 April)
• Re: [w3c/ServiceWorker] Allowing multiple scopes (& should scopes be primary key?) (#566) (Friday, 27 April)
• Re: [whatwg/fetch] WindowOrWorkerGlobalScope is a mixin (#719) (Friday, 27 April)
• Re: [whatwg/fetch] WindowOrWorkerGlobalScope is a mixin (#719) (Friday, 27 April)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#551) (Friday, 27 April)
• [heycam/webidl] Remove [LegacyArrayClass] (#551) (Friday, 27 April)
• Re: [whatwg/fetch] Add Request's isHistoryNavigation (#718) (Friday, 27 April)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Friday, 27 April)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Friday, 27 April)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Friday, 27 April)
• Re: [whatwg/url] Remove _charset_ handling. (#382) (Friday, 27 April)
• Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Friday, 27 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Friday, 27 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Friday, 27 April)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Thursday, 26 April)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Thursday, 26 April)
• Re: [whatwg/encoding] Identity encoding? (#138) (Thursday, 26 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Thursday, 26 April)
• Re: [whatwg/encoding] When encoding U+301C to legacy Japanese encodings, consider encoding as U+FF5E (#114) (Thursday, 26 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Thursday, 26 April)
• Re: [whatwg/fetch] Use Infra's abort when (#702) (Thursday, 26 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Thursday, 26 April)
• Re: [whatwg/fetch] Use Infra's abort when (#702) (Thursday, 26 April)
• Re: [whatwg/fetch] Use Infra's abort when (#702) (Thursday, 26 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Thursday, 26 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Thursday, 26 April)
• Re: [whatwg/fetch] From-Origin (#687) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 25 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Wednesday, 25 April)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 25 April)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 25 April)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Wednesday, 25 April)
• Re: [heycam/webidl] Disallow [LegacyArrayClass] on globals (#545) (Wednesday, 25 April)
• [whatwg/encoding] Give clearer advice on hooks for standards (#137) (Wednesday, 25 April)
• Re: [whatwg/encoding] Be clearer on which user agents the API applies to (#136) (Wednesday, 25 April)
• [whatwg/encoding] Be clearer on which user agents the API applies to (#136) (Wednesday, 25 April)
• Re: [whatwg/encoding] Editorial: Charset alias matching link (#134) (Wednesday, 25 April)
• Re: [whatwg/encoding] Need more changes for common deploy (#126) (Wednesday, 25 April)
• Re: [whatwg/encoding] Need more changes for common deploy (#126) (Wednesday, 25 April)
• Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) (Wednesday, 25 April)
• Re: [whatwg/encoding] When encoding U+301C to legacy Japanese encodings, consider encoding as U+FF5E (#114) (Wednesday, 25 April)
• Re: [whatwg/encoding] Meta: TF-8 decode without BOM or fail is used at least once (#124) (Wednesday, 25 April)
• Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377) (Wednesday, 25 April)
• Re: [whatwg/encoding] Meta: TF-8 decode without BOM or fail is used at least once (#124) (Wednesday, 25 April)
• Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Wednesday, 25 April)
• Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377) (Wednesday, 25 April)
• Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377) (Wednesday, 25 April)
• Re: [whatwg/url] Remove _charset_ handling. (#382) (Wednesday, 25 April)
• Re: [whatwg/url] Remove _charset_ handling. (#382) (Wednesday, 25 April)
• Re: [whatwg/fetch] Response.redirect() results in status message still being OK? (#664) (Tuesday, 24 April)
• Re: [whatwg/fetch] Make status message default the empty byte sequence (#600) (Tuesday, 24 April)
• Re: [whatwg/fetch] Response `statusText` is ambiguous and unclear for HTTP/2 (#599) (Tuesday, 24 April)
• Re: [w3ctag/design-reviews] HTML General Review (#174) (Tuesday, 24 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Tuesday, 24 April)
• Re: [w3ctag/design-reviews] HTML General Review (#174) (Tuesday, 24 April)
• Re: [whatwg/url] Remove mention of MediaStream (#380) (Tuesday, 24 April)
• Re: [whatwg/url] URL's object can no longer be a MediaStream (#381) (Tuesday, 24 April)
• Re: [whatwg/fetch] Content codings (Content-Encoding) (#716) (Tuesday, 24 April)
• Re: [whatwg/fetch] Use Infra for header list (#711) (Tuesday, 24 April)
• Re: [whatwg/fetch] Editorial: use Infra to define header list (#713) (Tuesday, 24 April)
• Re: [whatwg/fetch] Editorial: use Infra to define header list (#713) (Tuesday, 24 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Tuesday, 24 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Tuesday, 24 April)
• Re: [whatwg/fetch] Client hints difference between navigation and subresources (#707) (Tuesday, 24 April)
• Re: [whatwg/xhr] The logic in the WPT send-authentication-competing-names-passwords.htm does not match the spec. (#191) (Tuesday, 24 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Tuesday, 24 April)
• Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550) (Tuesday, 24 April)
• Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550) (Tuesday, 24 April)
• Re: [whatwg/dom] downloads (#639) (Tuesday, 24 April)
• Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550) (Tuesday, 24 April)
• Re: [whatwg/fetch] Make status message default the empty byte sequence (#600) (Monday, 23 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Monday, 23 April)
• Re: [whatwg/fetch] Use of response's cache state (#376) (Monday, 23 April)
• Re: [whatwg/fetch] Add response's cache state back (#705) (Monday, 23 April)
• [w3c/ServiceWorker] Response's cache state is back (#1308) (Monday, 23 April)
• Re: [whatwg/fetch] Editorial: remove most substep usage (#709) (Monday, 23 April)
• Re: [whatwg/fetch] Editorial: remove most substep usage (#709) (Monday, 23 April)
• Re: [whatwg/fetch] Editorial: remove most substep usage (#709) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: move feature policy integration section (#204) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: move Feature Policy Integration section (#199) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: move feature policy integration section (#204) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: move feature policy integration section (#204) (Monday, 23 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Monday, 23 April)
• Re: [whatwg/fetch] Content codings (Content-Encoding) (#716) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: less-confusing content-type manipulation algorithm for send() (#197) (Monday, 23 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Monday, 23 April)
• Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Monday, 23 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Monday, 23 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/fetch] Define how to handle bad content encoding (#657) (Monday, 23 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Monday, 23 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Monday, 23 April)
• Re: [whatwg/fetch] Content codings (Content-Encoding) (#716) (Monday, 23 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Monday, 23 April)
• Re: [whatwg/fetch] Content codings (Content-Encoding) (#716) (Monday, 23 April)
• [whatwg/fetch] Content codings (Content-Encoding) (#716) (Monday, 23 April)
• Re: [whatwg/fetch] Make status message default the empty byte sequence (#600) (Monday, 23 April)
• Re: [whatwg/fetch] Preventing some CRLF header injection attacks (#375) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/fetch] From-Origin (#687) (Monday, 23 April)
• Re: [whatwg/dom] Meta: fix service worker reference (#634) (Saturday, 21 April)
• Re: [whatwg/fetch] Use Infra's abort when (#702) (Saturday, 21 April)
• Re: [whatwg/fetch] Use Infra's abort when (#702) (Saturday, 21 April)
• Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585) (Saturday, 21 April)
• [whatwg/url] URL's object can no longer be a MediaStream (#381) (Friday, 20 April)
• Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585) (Friday, 20 April)
• Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585) (Friday, 20 April)
• Re: [whatwg/fetch] Preventing some CRLF header injection attacks (#375) (Friday, 20 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Friday, 20 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Friday, 20 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Friday, 20 April)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Thursday, 19 April)
• Re: [whatwg/storage] Issue (#61) (Thursday, 19 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Thursday, 19 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Thursday, 19 April)
• Re: [whatwg/fetch] The comma-delimited combined value definition does not support Set-Cookie headers (#345) (Thursday, 19 April)
• [whatwg/fetch] Clarify how Headers does not support Set-Cookie (#714) (Thursday, 19 April)
• [whatwg/fetch] Editorial: use Infra to define header list (#713) (Thursday, 19 April)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Thursday, 19 April)
• Re: [whatwg/xhr] Editorial: move feature policy integration section (#204) (Thursday, 19 April)
• [whatwg/xhr] Editorial: move feature policy integration section (#204) (Thursday, 19 April)
• Re: [whatwg/xhr] responseXML should maybe drop HTML support (#203) (Thursday, 19 April)
• Re: [whatwg/xhr] responseXML should maybe drop HTML support (#203) (Thursday, 19 April)
• Re: [whatwg/fetch] "Extract a MIME type" algorithm should pick the first entry? (#529) (Thursday, 19 April)
• Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Thursday, 19 April)
• [whatwg/xhr] responseXML should maybe drop HTML support (#203) (Thursday, 19 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Thursday, 19 April)
• Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Thursday, 19 April)
• Re: [w3c/ServiceWorker] consult document CSP in Register algorithm (#755) (Thursday, 19 April)
• Re: [whatwg/fetch] Client hints difference between navigation and subresources (#707) (Wednesday, 18 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Wednesday, 18 April)
• [whatwg/fetch] Use forgiving base64-encode for WebSocket (#712) (Wednesday, 18 April)
• Re: [whatwg/fetch] Return network error for scheme-fetch for ftp/file (#699) (Wednesday, 18 April)
• Re: [whatwg/fetch] Return network error for scheme-fetch for ftp/file (#699) (Wednesday, 18 April)
• [whatwg/fetch] Use Infra for header list (#711) (Wednesday, 18 April)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Wednesday, 18 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Wednesday, 18 April)
• Re: [whatwg/fetch] fetch assumes a url's object is always a Blob (#457) (Wednesday, 18 April)
• Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708) (Wednesday, 18 April)
• Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708) (Wednesday, 18 April)
• Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708) (Wednesday, 18 April)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Wednesday, 18 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Wednesday, 18 April)
• [whatwg/fetch] Handle failure while handling content codings (#710) (Wednesday, 18 April)
• Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708) (Wednesday, 18 April)
• [whatwg/url] Remove mention of MediaStream (#380) (Wednesday, 18 April)
• Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708) (Wednesday, 18 April)
• Re: [whatwg/fetch] Termination's aborted flag (#703) (Wednesday, 18 April)
• [whatwg/fetch] Editorial: remove most substep usage (#709) (Wednesday, 18 April)
• Re: [whatwg/fetch] Use Infra's abort when (#702) (Wednesday, 18 April)
• Re: [whatwg/fetch] Termination's aborted flag (#703) (Tuesday, 17 April)
• Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708) (Tuesday, 17 April)
• [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708) (Tuesday, 17 April)
• Re: [whatwg/fetch] fetch assumes a url's object is always a Blob (#457) (Tuesday, 17 April)
• Re: [w3c/ServiceWorker] should prefetch loads trigger FetchEvents? (#1302) (Tuesday, 17 April)
• Re: [whatwg/fetch] Add response's cache mode back (#705) (Tuesday, 17 April)
• Re: [whatwg/fetch] Add response's cache mode back (#705) (Tuesday, 17 April)
• Re: [whatwg/fetch] Add response's cache mode back (#705) (Tuesday, 17 April)
• Re: [whatwg/fetch] Editorial: client hints are sometimes strings; should always be byte sequences (#561) (Tuesday, 17 April)
• Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475) (Tuesday, 17 April)
• Re: [whatwg/fetch] Adjust casing of client hints (#704) (Tuesday, 17 April)
• [whatwg/fetch] Client hints difference between navigation and subresources (#707) (Tuesday, 17 April)
• Re: [whatwg/fetch] Adjust casing of client hints (#704) (Tuesday, 17 April)
• [whatwg/fetch] Abort refactoring led to variable errors (#706) (Tuesday, 17 April)
• Re: [whatwg/fetch] Add response's cache mode back (#705) (Tuesday, 17 April)
• [whatwg/fetch] Add response's cache mode back (#705) (Tuesday, 17 April)
• Re: [whatwg/fetch] Use of response's cache state (#376) (Tuesday, 17 April)
• Re: [whatwg/fetch] Use of response's cache state (#376) (Tuesday, 17 April)
• Re: [whatwg/fetch] Allowing user provided CORS exceptions? (#644) (Tuesday, 17 April)
• Re: [whatwg/fetch] Allowing user provided CORS exceptions? (#644) (Tuesday, 17 April)
• Re: [whatwg/fetch] Adjust casing of client hints (#704) (Tuesday, 17 April)
• Re: [whatwg/fetch] Adjust casing of client hints (#704) (Tuesday, 17 April)
• [whatwg/fetch] Adjust casing of client hints (#704) (Tuesday, 17 April)
• Re: [whatwg/fetch] fetch assumes a url's object is always a Blob (#457) (Tuesday, 17 April)
• Re: [whatwg/fetch] consider exposing and allowing script to set Request priority (#436) (Tuesday, 17 April)
• Re: [whatwg/fetch] Add { 548, 'afp' } to the blocked bad ports (#694) (Tuesday, 17 April)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Tuesday, 17 April)
• [whatwg/fetch] Termination's aborted flag (#703) (Tuesday, 17 April)
• [whatwg/fetch] Use Infra's abort when (#702) (Tuesday, 17 April)
• Re: [whatwg/fetch] Set response's CSP list once (#701) (Tuesday, 17 April)
• Re: [whatwg/fetch] Should "set response's CSP list" be in Main fetch? (#364) (Tuesday, 17 April)
• Re: [whatwg/fetch] Does terminating a fetch before headers come back reject the promise? (#416) (Tuesday, 17 April)
• Re: [whatwg/fetch] Does terminating a fetch before headers come back reject the promise? (#416) (Tuesday, 17 April)
• Re: [whatwg/fetch] Use of response's cache state (#376) (Tuesday, 17 April)
• Re: [whatwg/fetch] Set response's CSP list once (#701) (Tuesday, 17 April)
• [whatwg/fetch] Set response's CSP list once (#701) (Tuesday, 17 April)
• Re: [whatwg/xhr] Editorial: uppercase UTF-8 (and other encodings, if any) (#196) (Tuesday, 17 April)
• [whatwg/xhr] overrideMIMEType and XML (#201) (Tuesday, 17 April)
• Re: [whatwg/xhr] Clean up remaining MIME type usage (#175) (Tuesday, 17 April)
• Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb) (Tuesday, 17 April)
• Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb) (Tuesday, 17 April)
• Re: [whatwg/xhr] Look at overrideMimeType() again (#157) (Tuesday, 17 April)
• Re: [whatwg/xhr] Fix overrideMimeType() again (#174) (Tuesday, 17 April)
• Re: [whatwg/xhr] Fix overrideMimeType() again (#174) (Tuesday, 17 April)
• Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb) (Tuesday, 17 April)
• Re: [whatwg/fetch] From-Origin (#687) (Tuesday, 17 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 17 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)
• Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Monday, 16 April)
• Re: [whatwg/dom] "Set an existing attribute value" not cross-linking correctly (#637) (Monday, 16 April)
• Re: [whatwg/dom] Editorial: reference "set an existing attribute value" (#638) (Monday, 16 April)
• Re: [whatwg/xhr] Fix send() charset overriding to use new MIME type infrastructure (#188) (Monday, 16 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Monday, 16 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Monday, 16 April)
• Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Monday, 16 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)
• Re: [whatwg/dom] Editorial: reference "set an existing attribute value" (#638) (Monday, 16 April)
• [whatwg/dom] Editorial: reference "set an existing attribute value" (#638) (Monday, 16 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)
• Re: [whatwg/xhr] How is the about:blank case in send-non-same-origin supported by the spec? (#194) (Monday, 16 April)
• Re: [whatwg/dom] Editorial: note that CDATASections are Texts inside switches (#636) (Monday, 16 April)
• Re: [whatwg/dom] Editorial: note that CDATASections are Texts inside switches (#636) (Monday, 16 April)
• Re: [whatwg/dom] `cloneNode` should preserve element prototype (#565) (Monday, 16 April)
• Re: [whatwg/fetch] upload progress? (#21) (Sunday, 15 April)
• Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Sunday, 15 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Sunday, 15 April)
• Re: [whatwg/fetch] Return network error for scheme-fetch for ftp/file (#699) (Friday, 13 April)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Friday, 13 April)
• Re: [whatwg/fetch] From-Origin (#687) (Friday, 13 April)
• Re: [whatwg/fetch] From-Origin (#687) (Friday, 13 April)
• Re: [whatwg/dom] Dom (#635) (Friday, 13 April)
• Re: [whatwg/fetch] Change new Response() statusText default? (#698) (Thursday, 12 April)
• Re: [whatwg/fetch] Safelist Last-Event-ID (#568) (Thursday, 12 April)
• Re: [whatwg/fetch] Use auto-linking for CSP3. (#410) (Thursday, 12 April)
• Re: [whatwg/fetch] Use auto-linking for CSP3. (#410) (Thursday, 12 April)
• Re: [whatwg/fetch] Response.redirect() results in status message still being OK? (#664) (Thursday, 12 April)
• Re: [whatwg/fetch] Make status message default the empty byte sequence (#600) (Thursday, 12 April)
• Re: [whatwg/fetch] Make status message default the empty byte sequence (#600) (Thursday, 12 April)
• [whatwg/fetch] Change new Response() statusText default? (#698) (Thursday, 12 April)
• Re: [whatwg/fetch] Make status message default the empty byte sequence (#600) (Thursday, 12 April)
• Re: [whatwg/fetch] Response.redirect() results in status message still being OK? (#664) (Thursday, 12 April)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 12 April)
• Re: [whatwg/fetch] More informative error types (#526) (Thursday, 12 April)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 12 April)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 12 April)
• [whatwg/xhr] Stop censoring responseURL's fragment (#200) (Thursday, 12 April)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 12 April)
• [whatwg/fetch] Editorial: spell URL concepts uppercase (#697) (Thursday, 12 April)
• Re: [whatwg/fetch] Stop censoring fragments (#696) (Thursday, 12 April)
• [whatwg/fetch] Stop censoring fragments (#696) (Thursday, 12 April)
• Re: [whatwg/fetch] Requests cant "live" longer than 5 minutes? (#647) (Thursday, 12 April)
• Re: [whatwg/fetch] Requests cant "live" longer than 5 minutes? (#647) (Thursday, 12 April)
• Re: [whatwg/fetch] Provide ability to encode content from browser/runtime in fetch API. (#653) (Thursday, 12 April)
• Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475) (Thursday, 12 April)
• Re: [whatwg/fetch] More informative error types (#526) (Thursday, 12 April)
• Re: [whatwg/fetch] More informative error types (#526) (Thursday, 12 April)
• Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475) (Thursday, 12 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475) (Thursday, 12 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• Re: [whatwg/fetch] Make status message default the empty byte sequence (#600) (Wednesday, 11 April)
• Re: [whatwg/fetch] Make status message default the empty byte sequence (#600) (Wednesday, 11 April)
• Re: [whatwg/fetch] Linkify "present" for dictionaries (#513) (Wednesday, 11 April)
• Re: [whatwg/fetch] Fetching with a particular destination (#521) (Wednesday, 11 April)
• Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475) (Wednesday, 11 April)
• Re: [whatwg/fetch] Exempt HSTS-upgraded resources from mixed content blocking (#150) (Wednesday, 11 April)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Wednesday, 11 April)
• Re: [whatwg/fetch] Allowing user provided CORS exceptions? (#644) (Wednesday, 11 April)
• [whatwg/xhr] Editorial: move Feature Policy Integration section (#199) (Wednesday, 11 April)
• Re: [whatwg/xhr] Editorial: use Infra for FormData (#198) (Wednesday, 11 April)
• Re: [whatwg/xhr] Editorial: use Infra for FormData (#198) (Wednesday, 11 April)
• [whatwg/dom] Meta: fix service worker reference (#634) (Wednesday, 11 April)
• [whatwg/xhr] Editorial: use Infra for FormData (#198) (Wednesday, 11 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)
• Re: [whatwg/xhr] How is the about:blank case in send-non-same-origin supported by the spec? (#194) (Wednesday, 11 April)
• Re: [whatwg/xhr] How is the about:blank case in send-non-same-origin supported by the spec? (#194) (Wednesday, 11 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Wednesday, 11 April)
• Re: [whatwg/xhr] Editorial: less-confusing content-type manipulation algorithm for send() (#197) (Wednesday, 11 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Wednesday, 11 April)
• Re: [whatwg/xhr] Fix overrideMimeType() again (#174) (Wednesday, 11 April)
• Re: [whatwg/xhr] Fix overrideMimeType() again (#174) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Wednesday, 11 April)
• Re: [whatwg/dom] Meta: export event listener's fields (#632) (Wednesday, 11 April)
• Re: [whatwg/dom] Meta: export event listener's fields (#632) (Wednesday, 11 April)
• Re: [whatwg/dom] "Let capture, passive, and once be the result of flattening more options" (#633) (Wednesday, 11 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• [whatwg/xhr] Editorial: uppercase UTF-8 (and other encodings, if any) (#196) (Tuesday, 10 April)
• Re: [whatwg/xhr] Fix overrideMimeType() again (#174) (Tuesday, 10 April)
• Re: [whatwg/url] "The fragment percent-encode set is the C0 contr..." (#378) (Tuesday, 10 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• Re: [whatwg/xhr] Editorial: use "{{ExceptionType!!exception}}" {{DOMException}} throughout (#173) (Tuesday, 10 April)
• Re: [whatwg/xhr] Editorial: cleanup exception terminology (#195) (Tuesday, 10 April)
• Re: [whatwg/xhr] Editorial: cleanup exception terminology (#195) (Tuesday, 10 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Tuesday, 10 April)
• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 10 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Tuesday, 10 April)
• [whatwg/xhr] Editorial: cleanup exception terminology (#195) (Tuesday, 10 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• Re: [whatwg/xhr] Fix overrideMimeType() again (#174) (Tuesday, 10 April)
• Re: [whatwg/fetch] "Internal response" for "internal"? (#695) (Tuesday, 10 April)
• Re: [whatwg/fetch] "Internal response" for "internal"? (#695) (Tuesday, 10 April)
• [whatwg/dom] Editorial: make traverser object associations more explicit (#631) (Tuesday, 10 April)
• Re: [whatwg/fetch] Add { 548, 'afp' } to the blocked bad ports (#694) (Tuesday, 10 April)
• Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615) (Tuesday, 10 April)
• Re: [whatwg/dom] NodeIterator pre-removing steps seem incorrect (#496) (Tuesday, 10 April)
• Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615) (Tuesday, 10 April)
• Re: [whatwg/dom] Note retargeting usage in Fullscreen (#630) (Tuesday, 10 April)
• Re: [whatwg/dom] Consider moving "retargeting" to the dispatch section (#620) (Tuesday, 10 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Tuesday, 10 April)
• Re: [whatwg/fetch] From-Origin (#687) (Tuesday, 10 April)
• Re: [whatwg/url] "The fragment percent-encode set is the C0 contr..." (#378) (Tuesday, 10 April)
• [whatwg/dom] Note retargeting usage in Fullscreen (#630) (Monday, 9 April)
• Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Monday, 9 April)
• Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Monday, 9 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Monday, 9 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Monday, 9 April)
• Re: [whatwg/dom] Editorial: cleanup TreeWalker (#616) (Monday, 9 April)
• Re: [whatwg/dom] Fix TreeWalker's nextNode() (#612) (Monday, 9 April)
• Re: [whatwg/dom] setAttribute is missing a domintro? (#448) (Monday, 9 April)
• Re: [whatwg/dom] Add more domintro boxes (#601) (Monday, 9 April)
• [whatwg/dom] Add NonDocumentFragmentParentNode (#629) (Monday, 9 April)
• Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615) (Monday, 9 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Monday, 9 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Monday, 9 April)
• Re: [whatwg/dom] Editorial: add range's common ancestor (#608) (Monday, 9 April)
• Re: [whatwg/dom] Editorial: add range's common ancestor (#608) (Monday, 9 April)
• Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626) (Monday, 9 April)
• Re: [whatwg/dom] Flag refs in preventDefault()'s description missing "context object’s" qualifier (#627) (Monday, 9 April)
• Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#625) (Monday, 9 April)
• Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626) (Monday, 9 April)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Monday, 9 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Monday, 9 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Monday, 9 April)
• Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626) (Monday, 9 April)
• Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626) (Monday, 9 April)
• Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626) (Monday, 9 April)
• Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626) (Monday, 9 April)
• Re: [whatwg/dom] "Use these attribute change steps to update an element's ID" (#628) (Monday, 9 April)
• Re: [whatwg/fetch] From-Origin (#687) (Saturday, 7 April)
• Re: [whatwg/fetch] From-Origin (#687) (Saturday, 7 April)
• Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414) (Friday, 6 April)
• Re: [whatwg/dom] Define event constructing steps (#614) (Friday, 6 April)
• Re: [w3c/uievents] Define "event constructing steps" for complicated events (#194) (Friday, 6 April)
• [w3c/touch-events] Define "event constructing steps" (#94) (Friday, 6 April)
• [w3c/uievents] Define "event constructing steps" for complicated events (#194) (Friday, 6 April)
• Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407) (Friday, 6 April)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 6 April)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 6 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Friday, 6 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Friday, 6 April)
• Re: [whatwg/dom] Flag refs in preventDefault()'s description missing "context object’s" qualifier (#627) (Friday, 6 April)
• Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626) (Friday, 6 April)
• Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626) (Friday, 6 April)
• Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407) (Thursday, 5 April)
• Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407) (Thursday, 5 April)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Thursday, 5 April)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Thursday, 5 April)
• [heycam/webidl] Is a subclass still a platform object? (#540) (Thursday, 5 April)
• Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407) (Thursday, 5 April)
• Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407) (Thursday, 5 April)
• Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407) (Thursday, 5 April)
• Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407) (Thursday, 5 April)
• Re: [whatwg/fetch] Document same-origin policy more centrally (#691) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• [whatwg/fetch] Document same-origin policy more centrally (#691) (Thursday, 5 April)
• Re: [whatwg/fetch] From-Origin (#687) (Thursday, 5 April)
• Re: [w3c/uievents] Standardizing event.layerX and event.layerY (#193) (Thursday, 5 April)
• Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585) (Thursday, 5 April)
• Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Wednesday, 4 April)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 4 April)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 4 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Wednesday, 4 April)
• Re: [whatwg/fetch] Typo2018 (#690) (Tuesday, 3 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 3 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 3 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Tuesday, 3 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Tuesday, 3 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 3 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 3 April)
• Re: [w3c/ServiceWorker] Track ancestorOrigins privacy issues (#1075) (Tuesday, 3 April)
• Re: [whatwg/url] "Let pointer be a pointer to first code point in..." (#373) (Tuesday, 3 April)
• Re: [whatwg/fetch] From-Origin (#687) (Tuesday, 3 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 3 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 3 April)
• Re: [whatwg/dom] Issue #625. Define Event.srcElement and Event.returnValue for compat. (#626) (Tuesday, 3 April)
• Re: [whatwg/fetch] From-Origin (#687) (Tuesday, 3 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 3 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 3 April)
• Re: [whatwg/dom] `cloneNode` should preserve element prototype (#565) (Tuesday, 3 April)

arturjanc

• Re: [whatwg/fetch] From-Origin (#687) (Friday, 27 April)
• Re: [whatwg/fetch] From-Origin (#687) (Friday, 27 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Thursday, 19 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Wednesday, 18 April)
• Re: [whatwg/fetch] From-Origin (#687) (Tuesday, 17 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Sunday, 15 April)
• [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Saturday, 14 April)
• Re: [whatwg/fetch] From-Origin (#687) (Saturday, 14 April)
• Re: [whatwg/fetch] From-Origin (#687) (Thursday, 12 April)
• Re: [whatwg/fetch] From-Origin (#687) (Thursday, 12 April)
• Re: [whatwg/fetch] From-Origin (#687) (Sunday, 8 April)
• Re: [whatwg/fetch] From-Origin (#687) (Sunday, 8 April)
• Re: [whatwg/fetch] From-Origin (#687) (Saturday, 7 April)

Asa Kusuma

• Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292) (Friday, 6 April)

autisticgeniushk

• Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575) (Monday, 9 April)
• Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575) (Monday, 9 April)

Ben Kelly

• Re: [w3c/ServiceWorker] Replaying POST requests (#693) (Friday, 27 April)
• Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304) (Friday, 27 April)
• Re: [w3c/ServiceWorker] There should be no such thing as "fail to activate" (#659) (Friday, 27 April)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Thursday, 26 April)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Wednesday, 25 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Wednesday, 25 April)
• Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304) (Wednesday, 25 April)
• Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304) (Tuesday, 24 April)
• Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304) (Tuesday, 24 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Monday, 23 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Monday, 23 April)
• [w3c/ServiceWorker] how can unregister()'s same-origin check ever fail? (#1305) (Friday, 20 April)
• Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304) (Friday, 20 April)
• [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers resolve to undefined (#1304) (Friday, 20 April)
• Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585) (Friday, 20 April)
• Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585) (Friday, 20 April)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Friday, 20 April)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Friday, 20 April)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Thursday, 19 April)
• Re: [w3c/ServiceWorker] consult document CSP in Register algorithm (#755) (Thursday, 19 April)
• Re: [w3c/ServiceWorker] consult document CSP in Register algorithm (#755) (Wednesday, 18 April)
• Re: [w3c/ServiceWorker] should prefetch loads trigger FetchEvents? (#1302) (Tuesday, 17 April)
• Re: [whatwg/fetch] Add response's cache mode back (#705) (Tuesday, 17 April)
• Re: [whatwg/fetch] Use of response's cache state (#376) (Tuesday, 17 April)
• Re: [whatwg/fetch] Use of response's cache state (#376) (Tuesday, 17 April)
• [w3c/ServiceWorker] should prefetch loads trigger FetchEvents? (#1302) (Tuesday, 17 April)
• Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633) (Monday, 16 April)
• Re: [w3c/ServiceWorker] PUT request payload is lost (#1300) (Friday, 13 April)
• Re: [whatwg/fetch] Stop censoring fragments (#696) (Thursday, 12 April)
• Re: [whatwg/fetch] Stop censoring fragments (#696) (Thursday, 12 April)
• Re: [whatwg/fetch] Stop censoring fragments (#696) (Thursday, 12 April)
• Re: [whatwg/fetch] Stop censoring fragments (#696) (Thursday, 12 April)
• Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189) (Thursday, 12 April)
• Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234) (Wednesday, 11 April)
• Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189) (Wednesday, 11 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Tuesday, 10 April)
• Re: [w3c/ServiceWorker] Cache API: Cache-Control headers and Opaque Responses (#1299) (Monday, 9 April)
• Re: [w3c/ServiceWorker] if a worker script redirects from an in-scope URL to an out-of-scope URL, what is the worker's final controller? (#1239) (Monday, 9 April)
• Re: [w3c/ServiceWorker] if a worker script redirects from an in-scope URL to an out-of-scope URL, what is the worker's final controller? (#1239) (Monday, 9 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Friday, 6 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Friday, 6 April)
• Re: [w3c/ServiceWorker] Cache API: Cache-Control headers and Opaque Responses (#1299) (Thursday, 5 April)
• Re: [w3c/ServiceWorker] Intecepts progress event of AJAX calls (#1298) (Thursday, 5 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Wednesday, 4 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Tuesday, 3 April)

Bence Béky

• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Thursday, 12 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)

Benjamin Gruenbaum

• Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377) (Wednesday, 25 April)
• Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377) (Wednesday, 25 April)
• Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377) (Wednesday, 25 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Sunday, 8 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• [whatwg/fetch] Expose Stream Watermarks (#689) (Monday, 2 April)

BigBlueHat

• Re: [w3ctag/packaging-on-the-web] Ungutted (#36) (Wednesday, 11 April)

bigopon

• Re: [whatwg/dom] `cloneNode` should preserve element prototype (#565) (Friday, 13 April)
• Re: [whatwg/dom] `cloneNode` should preserve element prototype (#565) (Tuesday, 3 April)

Bitcollage

• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 11 April)

Boris Zbarsky

• Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548) (Wednesday, 25 April)
• Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548) (Wednesday, 25 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Thursday, 19 April)
• Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548) (Friday, 13 April)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Friday, 13 April)
• Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541) (Monday, 9 April)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Thursday, 5 April)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Thursday, 5 April)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Thursday, 5 April)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Thursday, 5 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 3 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 3 April)

Brett Zamir

• Re: [w3c/ServiceWorker] There should be no such thing as "fail to activate" (#659) (Friday, 27 April)
• Re: [w3c/ServiceWorker] There should be no such thing as "fail to activate" (#659) (Friday, 27 April)

Brian Grinstead

• [w3c/webcomponents] Customized Autonomous Elements (#750) (Wednesday, 18 April)

Brian Kardell

• Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233) (Tuesday, 17 April)

Caleb Williams

• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 25 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Monday, 23 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 19 April)

chaals

• Re: [w3c/WebPlatformWG] Add Job van Achterberg to Observers for 18-06-2018 meeting (#118) (Thursday, 26 April)
• Re: [w3c/push-api] Update privacy and server choice... (#294) (Friday, 13 April)
• Re: [w3c/push-api] Update privacy and server choice... (#294) (Friday, 13 April)
• Re: [w3c/push-api] Update privacy and server choice... (#294) (Friday, 13 April)
• Re: [w3c/push-api] Update privacy and server choice... (#294) (Friday, 13 April)
• Re: [w3c/push-api] Update privacy and server choice... (#294) (Friday, 13 April)
• Re: [w3c/push-api] Rephrase the bit about the UA chosing the push service (#287) (Thursday, 12 April)
• [w3c/push-api] Update privacy and server choice... (#294) (Thursday, 12 April)
• Re: [w3c/push-api] Issue: Change Source of Push Service and Privacy Issues (#258) (Sunday, 1 April)

Charles Reis

• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Friday, 20 April)
• Re: [whatwg/fetch] From-Origin (#687) (Tuesday, 17 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Saturday, 14 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Saturday, 14 April)
• Re: [whatwg/fetch] From-Origin (#687) (Saturday, 14 April)
• Re: [whatwg/fetch] From-Origin (#687) (Friday, 13 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Friday, 13 April)
• Re: [whatwg/fetch] From-Origin (#687) (Friday, 13 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Tuesday, 3 April)

Chris Kruining

• Re: [w3c/ServiceWorker] PUT request payload is lost (#1300) (Friday, 13 April)
• Re: [w3c/ServiceWorker] PUT request payload is lost (#1300) (Friday, 13 April)
• [w3c/ServiceWorker] PUT request payload is lost (#1300) (Friday, 13 April)

Chris Needham

• Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105) (Tuesday, 10 April)
• Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105) (Tuesday, 10 April)
• Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105) (Saturday, 7 April)

Chris Pearce

• Re: [w3c/permissions] autoplay permission (#172) (Tuesday, 3 April)

Chris Rebert

• Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407) (Sunday, 15 April)
• Re: [w3c/uievents] Add a note about inheritance of UIEvent. (#178) (Saturday, 14 April)
• Re: [w3c/uievents] MouseEvent.fromElement/toElement (#84) (Saturday, 14 April)
• Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626) (Monday, 9 April)
• Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626) (Friday, 6 April)
• [whatwg/dom] Flag refs in preventDefault()'s description missing "context object’s" qualifier (#627) (Friday, 6 April)
• Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626) (Friday, 6 April)
• Re: [whatwg/dom] Issue #625. Define Event.srcElement and Event.returnValue for compat. (#626) (Monday, 2 April)
• Re: [whatwg/dom] Issue #625. Define Event.srcElement and Event.returnValue for compat. (#626) (Monday, 2 April)

Chris Talman

• Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659) (Tuesday, 17 April)

cynthia

• Re: [w3ctag/design-reviews] BCP56bis (#232) (Tuesday, 24 April)
• Re: [w3ctag/design-reviews] BCP56bis (#232) (Sunday, 8 April)
• Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] BCP56bis (#232) (Saturday, 7 April)
• [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Keyboard Map (#238) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Friday, 6 April)
• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Thursday, 5 April)
• Re: [w3ctag/design-reviews] Should WebRTC be [SecureContext] (#228) (Thursday, 5 April)

Cyril Auburtin

• Re: [whatwg/fetch] upload progress? (#21) (Sunday, 15 April)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Keyboard Map (#238) (Tuesday, 24 April)
• Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233) (Tuesday, 24 April)
• Re: [w3ctag/design-reviews] HTML General Review (#174) (Tuesday, 24 April)
• Re: [w3ctag/design-reviews] HTML General Review (#174) (Tuesday, 24 April)
• Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239) (Tuesday, 17 April)
• Re: [w3ctag/design-reviews] Web Components Guidelines Doc? (#227) (Tuesday, 17 April)
• Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] CSS Layout API (#224) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] BCP56bis (#232) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Changing requirements for Well-Known URIs (#237) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Keyboard Map (#238) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Request review for Keyboard Map (#238) (Friday, 6 April)
• Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Friday, 6 April)
• Re: [w3ctag/design-reviews] CSS Layout API (#224) (Thursday, 5 April)
• Re: [w3ctag/design-reviews] Web Components Guidelines Doc? (#227) (Thursday, 5 April)
• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Thursday, 5 April)
• Re: [w3ctag/design-reviews] Should WebRTC be [SecureContext] (#228) (Thursday, 5 April)
• Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233) (Thursday, 5 April)

Daniel Ehrenberg

• Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231) (Tuesday, 3 April)

Daniel Veditz

• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)

danielpeintner

• [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541) (Friday, 6 April)

Dave Methvin

• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Friday, 6 April)

Dave Tapuska

• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Thursday, 12 April)
• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Wednesday, 4 April)

David Bruant

• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Sunday, 8 April)

Diogo Franco

• Re: [w3c/uievents] Event order between "compositionend" and "input" (#202) (Monday, 23 April)

domain-user

• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Thursday, 5 April)

Domenic Denicola

• Re: [whatwg/dom] Introduce "remove all event listeners" primitive (#641) (Monday, 30 April)
• Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552) (Monday, 30 April)
• Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643) (Monday, 30 April)
• Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643) (Monday, 30 April)
• Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643) (Monday, 30 April)
• Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643) (Monday, 30 April)
• [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643) (Sunday, 29 April)
• [whatwg/dom] "Otherwise, if hasSeenCurrentTarget is true and ..." (#642) (Saturday, 28 April)
• Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552) (Friday, 27 April)
• [w3ctag/design-reviews] Layered APIs (#276) (Thursday, 26 April)
• Re: [w3c/webcomponents] Customized Autonomous Elements (#750) (Thursday, 26 April)
• Re: [w3c/webcomponents] Customized Autonomous Elements (#750) (Thursday, 26 April)
• Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Wednesday, 25 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Tuesday, 24 April)
• Re: [whatwg/streams] Fix internal links for class ReadableStreamBYOBRequest (#923) (Tuesday, 24 April)
• Re: [whatwg/streams] Fix internal links for class ReadableStreamBYOBRequest (#923) (Tuesday, 24 April)
• Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Tuesday, 24 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Monday, 23 April)
• Re: [whatwg/streams] Revise property access order (#922) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Monday, 23 April)
• [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Saturday, 21 April)
• Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585) (Friday, 20 April)
• Re: [w3c/permissions] Using Web IDL to describe WebDriver JSON is a bit unusual (#174) (Thursday, 19 April)
• Re: [whatwg/fetch] From-Origin (#687) (Monday, 16 April)
• Re: [whatwg/dom] Editorial: reference "set an existing attribute value" (#638) (Monday, 16 April)
• Re: [whatwg/dom] Editorial: note that CDATASections are Texts inside switches (#636) (Monday, 16 April)
• [whatwg/dom] "Set an existing attribute value" not cross-linking correctly (#637) (Monday, 16 April)
• [whatwg/dom] Editorial: note that CDATASections are Texts inside switches (#636) (Monday, 16 April)
• Re: [whatwg/streams] Numeric conversion is not done on autoAllocateChunkSize (#921) (Thursday, 12 April)
• Re: [whatwg/fetch] Change new Response() statusText default? (#698) (Thursday, 12 April)
• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Thursday, 12 April)
• Re: [whatwg/fetch] More informative error types (#526) (Thursday, 12 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• Re: [w3c/ServiceWorker] need AsyncLocalStorage (was #904) (#906) (Wednesday, 11 April)
• Re: [w3c/IndexedDB] Async LocalStorage (transactionless key-value API over IDB) (#91) (Wednesday, 11 April)
• Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Wednesday, 11 April)
• Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Wednesday, 11 April)
• Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Wednesday, 11 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Wednesday, 11 April)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 11 April)
• Re: [whatwg/xhr] Fix overrideMimeType() again (#174) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Wednesday, 11 April)
• Re: [whatwg/dom] Meta: export event listener's fields (#632) (Wednesday, 11 April)
• Re: [whatwg/dom] Meta: export event listener's fields (#632) (Wednesday, 11 April)
• Re: [whatwg/dom] Meta: export event listener's fields (#632) (Wednesday, 11 April)
• Re: [whatwg/dom] "Let capture, passive, and once be the result of flattening more options" (#633) (Wednesday, 11 April)
• Re: [whatwg/dom] "Let capture, passive, and once be the result of flattening more options" (#633) (Wednesday, 11 April)
• [whatwg/dom] "Let capture, passive, and once be the result of flattening more options" (#633) (Wednesday, 11 April)
• [whatwg/dom] Meta: export event listener's fields (#632) (Tuesday, 10 April)
• Re: [w3c/uievents] Need procedural algorithms for all events (#200) (Tuesday, 10 April)
• Re: [whatwg/xhr] Fix overrideMimeType() again (#174) (Tuesday, 10 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• [whatwg/xhr] Editorial: less-confusing content-type manipulation algorithm for send() (#197) (Tuesday, 10 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176) (Tuesday, 10 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Tuesday, 10 April)
• Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615) (Tuesday, 10 April)
• Re: [w3c/uievents] Need algorithm for how events are fired for key presses (#142) (Tuesday, 10 April)
• Re: [w3c/uievents] Need algorithm for how mouse events are fired (#196) (Tuesday, 10 April)
• Re: [w3c/uievents] Need algorithm for how focus events are fired (#195) (Tuesday, 10 April)
• Re: [w3c/uievents] Need algorithm for how events are fired for key presses (#142) (Tuesday, 10 April)
• Re: [w3c/uievents] Need algorithm for how mouse click events are fired (#197) (Tuesday, 10 April)
• Re: [whatwg/streams] Linkify all class definitions (#913) (Monday, 9 April)
• Re: [whatwg/streams] Linkify all class definitions (#913) (Monday, 9 April)
• Re: [whatwg/streams] Linkify all class definitions (#913) (Monday, 9 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 9 April)
• [whatwg/dom] "Use these attribute change steps to update an element's ID" (#628) (Monday, 9 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Saturday, 7 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Saturday, 7 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Saturday, 7 April)
• Re: [w3c/ServiceWorker] Configure script's settings and realm for service workers (#1294) (Friday, 6 April)
• Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541) (Friday, 6 April)
• Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615) (Friday, 6 April)
• Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615) (Friday, 6 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 4 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Wednesday, 4 April)
• Re: [whatwg/streams] What are the preconditions for ReadableStreamDefaultControllerError? (#920) (Wednesday, 4 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Tuesday, 3 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• Re: [whatwg/streams] Fix a reference to [[queueSize]] (#918) (Monday, 2 April)
• Re: [whatwg/streams] Constructor: replace _readableStrategy_ with _strategy_ (#916) (Monday, 2 April)
• Re: [whatwg/streams] Fix a reference to [[queueSize]] (#918) (Monday, 2 April)
• Re: [whatwg/streams] Constructor: replace _readableStrategy_ with _strategy_ (#916) (Monday, 2 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Monday, 2 April)

Dominic Farolino

• [w3ctag/design-reviews] Review Request: Priority Hints API (#241) (Sunday, 15 April)

Dominick Ng

• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)

Dominique Hazael-Massieux

• Re: [w3ctag/design-reviews] Review request for WebVR (#185) (Wednesday, 25 April)

Ella Ge

• Re: [w3c/touch-events] Add note to mention UA might adjusting touch target (#95) (Friday, 27 April)
• Re: [w3c/touch-events] Should spec mention “touch adjustment" behavior? (#93) (Friday, 27 April)
• Re: [w3c/touch-events] Add note to mention UA might adjusting touch target (#95) (Friday, 27 April)
• Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80) (Thursday, 26 April)
• [w3c/touch-events] Remove createTouch and createTouch list (#96) (Thursday, 26 April)
• Re: [w3c/touch-events] Should spec mention “touch adjustment" behavior? (#93) (Thursday, 26 April)
• [w3c/touch-events] Add note to mention UI might adjusting touch target (#95) (Thursday, 26 April)

Emilio Cobos Álvarez

• Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550) (Tuesday, 24 April)
• Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550) (Tuesday, 24 April)
• [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550) (Monday, 23 April)

Eric Portis

• Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187) (Tuesday, 3 April)

fantasai

• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Monday, 9 April)

Firdaus89

• [whatwg/dom] Dom (#635) (Friday, 13 April)

firtman

• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 16 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 16 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 16 April)

Frederik

• [whatwg/fetch] Return network error for scheme-fetch for ftp/file (#699) (Friday, 13 April)

Fredrik Sundqvist

• Re: [w3c/manifest] Allow for multiple scopes (#449) (Wednesday, 18 April)

freshp86

• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 3 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Monday, 2 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Monday, 2 April)

Fuqiao Xue

• Re: [w3c/screen-orientation] Link Screen Orientation with Fullscreen more cleanly (#62) (Friday, 20 April)
• Re: [w3c/screen-orientation] Test suite (#95) (Wednesday, 18 April)
• Re: [w3c/screen-orientation] Link Screen Orientation with Fullscreen more cleanly (#62) (Tuesday, 17 April)
• Re: [w3c/screen-orientation] Where are terms 'primary' and 'secondary' defined within spec? (#113) (Tuesday, 10 April)

Gary Kacmarcik

• Re: [w3ctag/design-reviews] Keyboard Map (#238) (Thursday, 26 April)
• Re: [w3c/uievents] Need algorithm for how input events are fired (#198) (Monday, 9 April)
• Re: [w3c/uievents] Need algorithm for how composition events are fired (#199) (Monday, 9 April)
• Re: [w3c/uievents] Need algorithm for how mouse click events are fired (#197) (Monday, 9 April)
• [w3c/uievents] Need algorithm for how focus events are fired (#195) (Monday, 9 April)
• [w3c/uievents] Need procedural algorithms for all events (#200) (Monday, 9 April)
• [w3c/uievents] Need algorithm for how composition events are fired (#199) (Monday, 9 April)
• [w3c/uievents] Need algorithm for how input events are fired (#198) (Monday, 9 April)
• [w3c/uievents] Need algorithm for how mouse click events are fired (#197) (Monday, 9 April)
• Re: [w3c/uievents] Need algorithm for how focus events are fired (#195) (Monday, 9 April)
• [w3c/uievents] Need algorithm for how mouse events are fired (#196) (Monday, 9 April)
• Re: [w3c/uievents] Support queryKeyCap (#156) (Friday, 6 April)
• [w3ctag/design-reviews] Request review for Keyboard Map (#238) (Friday, 6 April)
• Re: [w3c/clipboard-apis] Request TAG review for initial (text only) API (#59) (Thursday, 5 April)
• Re: [w3c/clipboard-apis] Request TAG review for initial (text only) API (#59) (Thursday, 5 April)

Geoffrey Sneddon

• Re: [whatwg/dom] Editorial: reference "set an existing attribute value" (#638) (Tuesday, 17 April)

Glen

• Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 21 April)
• Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Saturday, 14 April)
• Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705) (Saturday, 14 April)

Greggman

• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Sunday, 29 April)

guest271314

• Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214) (Thursday, 12 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Saturday, 7 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Saturday, 7 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Saturday, 7 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Saturday, 7 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Saturday, 7 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Saturday, 7 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Saturday, 7 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Saturday, 7 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 3 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 3 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 3 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 3 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 3 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 3 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Monday, 2 April)

Hadley Beeman

• Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Saturday, 7 April)

Hayato Ito

• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 24 April)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 24 April)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 24 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Friday, 6 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 4 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 4 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 3 April)

Henri Sivonen

• Re: [whatwg/encoding] When encoding U+301C to legacy Japanese encodings, consider encoding as U+FF5E (#114) (Thursday, 26 April)
• Re: [whatwg/encoding] When encoding U+301C to legacy Japanese encodings, consider encoding as U+FF5E (#114) (Thursday, 26 April)

hober

• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Wednesday, 11 April)

Ian Clelland

• Re: [whatwg/xhr] Editorial: move feature policy integration section (#204) (Monday, 23 April)

Ilya Grigorik

• Re: [whatwg/fetch] Client hints difference between navigation and subresources (#707) (Wednesday, 18 April)
• Re: [whatwg/fetch] Client hints difference between navigation and subresources (#707) (Wednesday, 18 April)
• Re: [whatwg/fetch] Adjust casing of client hints (#704) (Tuesday, 17 April)
• Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475) (Thursday, 12 April)
• Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475) (Wednesday, 11 April)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Thursday, 5 April)

Ingvar Stepanyan

• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Thursday, 19 April)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Thursday, 19 April)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Thursday, 19 April)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Thursday, 19 April)

Islam Sharabash

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Wednesday, 25 April)

Jacob Rossi

• Re: [w3c/touch-events] Should spec mention “touch adjustment" behavior? (#93) (Thursday, 26 April)

Jake Archibald

• Re: [w3c/ServiceWorker] There should be no such thing as "fail to activate" (#659) (Friday, 27 April)
• Re: [whatwg/fetch] just do it (048d10e) (Friday, 27 April)
• Re: [whatwg/fetch] Use Infra's abort when (#702) (Thursday, 26 April)
• Re: [whatwg/fetch] Use Infra's abort when (#702) (Thursday, 26 April)
• Re: [whatwg/fetch] Use Infra's abort when (#702) (Thursday, 26 April)
• Re: [whatwg/fetch] Fetching with a particular destination (#521) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Fetching with a particular destination (#521) (Thursday, 26 April)
• Re: [whatwg/fetch] Fetching with a particular destination (#521) (Thursday, 26 April)
• Re: [whatwg/fetch] Editorial: remove most substep usage (#709) (Monday, 23 April)
• Re: [whatwg/fetch] Make status message default the empty byte sequence (#600) (Monday, 23 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Friday, 20 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Friday, 20 April)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Thursday, 19 April)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Thursday, 19 April)
• Re: [whatwg/fetch] Termination's aborted flag (#703) (Tuesday, 17 April)
• Re: [whatwg/fetch] Termination's aborted flag (#703) (Tuesday, 17 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Sunday, 15 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Saturday, 14 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Friday, 13 April)
• Re: [whatwg/fetch] More informative error types (#526) (Friday, 13 April)
• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Thursday, 12 April)
• Re: [whatwg/fetch] More informative error types (#526) (Thursday, 12 April)
• Re: [whatwg/fetch] More informative error types (#526) (Thursday, 12 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Tuesday, 10 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Tuesday, 10 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Tuesday, 10 April)
• Re: [whatwg/fetch] "Internal response" for "internal"? (#695) (Tuesday, 10 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Tuesday, 10 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Tuesday, 10 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Tuesday, 10 April)
• [whatwg/fetch] "Internal response" for "internal"? (#695) (Tuesday, 10 April)
• Re: [whatwg/dom] Abort controller design (#438) (Monday, 9 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Monday, 9 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Monday, 9 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Monday, 9 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Friday, 6 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Friday, 6 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Friday, 6 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Thursday, 5 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Thursday, 5 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Thursday, 5 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Thursday, 5 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Thursday, 5 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Thursday, 5 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Thursday, 5 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Thursday, 5 April)
• Re: [whatwg/fetch] Document same-origin policy more centrally (#691) (Thursday, 5 April)
• Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Thursday, 5 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Wednesday, 4 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Wednesday, 4 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Wednesday, 4 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Wednesday, 4 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Wednesday, 4 April)
• Re: [whatwg/fetch] Allow range header to be set by APIs (#560) (Wednesday, 4 April)
• Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (4cc72bd) (Tuesday, 3 April)
• Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 3 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 3 April)
• Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)

James Bromwell

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 19 April)

James M Snell

• Re: [whatwg/encoding] Be clearer on which user agents the API applies to (#136) (Wednesday, 25 April)
• Re: [whatwg/encoding] Be clearer on which user agents the API applies to (#136) (Wednesday, 25 April)

Jason Rice

• Re: [whatwg/fetch] Add timeout option (#20) (Wednesday, 11 April)

Jatinder Mann

• [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303) (Friday, 20 April)

Javier Fernandez Garcia-Boente

• Re: [w3c/editing] Should backspace merge text with last cell's content of a table above ? (#164) (Sunday, 29 April)

Jeffrey Yasskin

• Re: [w3c/ServiceWorker] should prefetch loads trigger FetchEvents? (#1302) (Tuesday, 17 April)
• [whatwg/fetch] Pass site-for-cookies through Fetch (#693) (Monday, 9 April)
• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Saturday, 7 April)
• Re: [w3c/permissions] Add support for permissions that have an associated Feature Policy (#163) (Monday, 2 April)

Jer Noble

• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Thursday, 12 April)
• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Thursday, 12 April)
• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Thursday, 12 April)

Jimmy Wärting

• [whatwg/xhr] Allow FormData constructor to accept array or object too (#202) (Wednesday, 18 April)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 11 April)

Jinho Bang

• Re: [w3c/ServiceWorker] windowClients state change events - loaded/unloaded (#1269) (Monday, 23 April)

Job van Achterberg

• [w3c/WebPlatformWG] Add Job van Achterberg to Observers for 18-06-2018 meeting (#118) (Thursday, 26 April)

Joe Pea

• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Sunday, 15 April)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 11 April)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 4 April)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 4 April)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 4 April)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 4 April)

Johannes Wilm

• Re: [w3c/editing] Should backspace merge text with last cell's content of a table above ? (#164) (Monday, 30 April)
• Re: [w3c/editing] Should backspace merge text with last cell's content of a table above ? (#164) (Monday, 30 April)
• Re: [w3c/editing] insertParagraph definition is different from current browsers' behavior when selection is collapsed at end of inline element(s) (#172) (Saturday, 28 April)
• Re: [w3c/editing] Should backspace merge text with last cell's content of a table above ? (#164) (Saturday, 28 April)
• Re: [w3c/editing] Should backspace merge text with last cell's content of a table above ? (#164) (Saturday, 28 April)
• Re: [w3c/editing] Standardize execCommand("insertParagraph") in inline editing host (#175) (Saturday, 28 April)
• Re: [w3c/editing] make need of execCommand to hide table controls go away on FF (#171) (Saturday, 28 April)
• Re: [w3c/editing] input setSelection() method workflow, when text overflows input container (#173) (Saturday, 28 April)
• Re: [w3c/editing] input setSelection() method workflow, when text overflows input container (#173) (Saturday, 28 April)
• Re: [w3c/editing] Clarification of events to fire when gaining and losing focus (#174) (Saturday, 28 April)

John Wilander

• Re: [whatwg/fetch] From-Origin (#687) (Monday, 30 April)
• Re: [whatwg/fetch] From-Origin (#687) (Friday, 27 April)
• Re: [whatwg/fetch] From-Origin (#687) (Friday, 27 April)
• Re: [whatwg/fetch] From-Origin (#687) (Wednesday, 25 April)
• Re: [whatwg/fetch] From-Origin (#687) (Monday, 16 April)
• Re: [whatwg/fetch] From-Origin (#687) (Monday, 16 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)
• Re: [whatwg/fetch] From-Origin (#687) (Friday, 13 April)
• Re: [whatwg/fetch] From-Origin (#687) (Saturday, 7 April)
• Re: [whatwg/fetch] From-Origin (#687) (Friday, 6 April)

Jon Piesing

• Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105) (Tuesday, 10 April)
• Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105) (Tuesday, 10 April)
• Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105) (Monday, 9 April)

Jonas Sicking

• Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Friday, 6 April)
• Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Friday, 6 April)

Jordan Harband

• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)

Josh Matthews (away until April 30)

• Re: [whatwg/fetch] Java run bug report (#692) (Monday, 9 April)

Joshua Bell

• Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552) (Monday, 30 April)
• [heycam/webidl] Introduce new string type for names/keys with length limit (#552) (Friday, 27 April)
• Re: [w3c/ServiceWorker] Size constraints for cache names? (#1310) (Friday, 27 April)
• Re: [w3c/ServiceWorker] Size constraints for cache names? (#1310) (Friday, 27 April)
• Re: [w3c/IndexedDB] How should commit() failures be surfaced when freezing / unloading (#237) (Friday, 27 April)
• Re: [w3c/IndexedDB] How should commit() failures be surfaced when freezing / unloading (#237) (Friday, 27 April)
• Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234) (Tuesday, 17 April)
• [w3c/FileAPI] Refine StructuredSerializeForStorage behavior (#98) (Tuesday, 17 April)
• Re: [w3c/IndexedDB] Define storage operation of non-trivial StructuredSerializeForStorage records (e.g. Blob/File) (#203) (Tuesday, 17 April)
• Re: [w3c/IndexedDB] Define storage operation of non-trivial StructuredSerializeForStorage records (e.g. Blob/File) (#203) (Tuesday, 17 April)
• Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234) (Friday, 13 April)
• Re: [w3c/IndexedDB] Async LocalStorage (transactionless key-value API over IDB) (#91) (Wednesday, 11 April)
• Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234) (Wednesday, 11 April)
• Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235) (Wednesday, 11 April)
• Re: [w3c/IndexedDB] Use (DOMString or sequence<DOMString>) for keyPath (#236) (Wednesday, 11 April)
• Re: [w3c/IndexedDB] Use (DOMString or sequence<DOMString>) for keyPath (#236) (Wednesday, 11 April)
• Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235) (Wednesday, 11 April)
• Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235) (Wednesday, 11 April)
• Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234) (Tuesday, 10 April)
• [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234) (Tuesday, 10 April)
• [w3c/ServiceWorker] Cache API: Cache-Control headers and Opaque Responses (#1299) (Thursday, 5 April)

jugglinmike

• Re: [w3c/permissions] Using Web IDL to describe WebDriver JSON is a bit unusual (#174) (Wednesday, 25 April)

Julian Reschke

• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Thursday, 12 April)

Jungkee Song

• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 17 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Monday, 16 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Wednesday, 4 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 3 April)
• Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371) (Tuesday, 3 April)
• Re: [w3c/ServiceWorker] .ready promise should be resolved after updating registration.state properties (#1011) (Tuesday, 3 April)
• Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (Tuesday, 3 April)
• Re: [w3c/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Tuesday, 3 April)
• Re: [w3c/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Monday, 2 April)

Justin Fagnani

• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Wednesday, 25 April)
• Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682) (Sunday, 15 April)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Sunday, 15 April)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 4 April)

Jxck

• Re: [w3c/ServiceWorker] need AsyncLocalStorage (was #904) (#906) (Thursday, 12 April)

Kagami Sascha Rosylight

• [w3c/IndexedDB] WindowOrWorkerGlobalScope is a mixin (#238) (Friday, 27 April)
• [w3c/ServiceWorker] WindowOrWorkerGlobalScope is a mixin (#1309) (Friday, 27 April)
• [whatwg/fetch] WindowOrWorkerGlobalScope is a mixin (#719) (Friday, 27 April)
• [w3c/ServiceWorker] Does ServiceWorkerContainer.onmessage also get ExtendableMessageEvent object? (#1301) (Saturday, 14 April)
• Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235) (Wednesday, 11 April)
• Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235) (Wednesday, 11 April)
• Re: [w3c/IndexedDB] Use (DOMString or sequence<DOMString>) for keyPath (#236) (Wednesday, 11 April)
• [w3c/IndexedDB] Use (DOMString or sequence<DOMString>) for keyPath (#236) (Wednesday, 11 April)
• [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235) (Wednesday, 11 April)

kai zhu

• Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231) (Tuesday, 3 April)

Kenji Baheux

• Re: [w3c/ServiceWorker] Allowing multiple scopes (& should scopes be primary key?) (#566) (Friday, 27 April)
• Re: [w3c/ServiceWorker] Allowing multiple scopes (& should scopes be primary key?) (#566) (Friday, 27 April)

Kenneth Rohde Christiansen

• Re: [w3ctag/design-reviews] Review Request: WebUSB on Dedicated and Shared Workers (#277) (Monday, 30 April)
• Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541) (Wednesday, 18 April)
• Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659) (Tuesday, 17 April)
• Re: [w3c/manifest] Add support for "share_target" property (#665) (Tuesday, 17 April)
• Re: [w3c/manifest] Add support for "share_target" property (#665) (Monday, 16 April)
• Re: [w3c/manifest] Add support for "share_target" property (#665) (Monday, 16 April)
• Re: [w3c/manifest] Add support for "share_target" property (#665) (Monday, 16 April)
• Re: [w3c/manifest] Add support for "share_target" property (#665) (Monday, 16 April)
• Re: [w3ctag/design-reviews] Web Components Guidelines Doc? (#227) (Thursday, 5 April)

Kinuko Yasuda

• Re: [whatwg/fetch] Define the "Preload Cache" (#590) (Wednesday, 11 April)

Konstantin Simon Maria Möllers

• Re: [whatwg/streams] Add two demos using streams for PNG manipulation (#911) (Thursday, 19 April)

Kyle Machulis

• Re: [w3c/permissions] Possibly add 'vibration' to Permission Registry Enum? (#173) (Tuesday, 10 April)
• [w3c/permissions] Possibly add 'vibration' to Permission Registry Enum? (#173) (Tuesday, 10 April)

L. David Baron

• Re: [w3ctag/design-reviews] Review Request: WebUSB on Dedicated and Shared Workers (#277) (Friday, 27 April)
• Re: [w3ctag/design-reviews] HTML General Review (#174) (Tuesday, 24 April)
• Re: [w3ctag/design-reviews] HTML General Review (#174) (Tuesday, 24 April)
• Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233) (Tuesday, 17 April)
• Re: [w3ctag/design-reviews] CSS Layout API (#224) (Monday, 9 April)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Monday, 9 April)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Payment Handler (#231) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Payment Handler (#231) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233) (Saturday, 7 April)

Lea Verou

• Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Tuesday, 10 April)

Linus Lewandowski

• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Thursday, 12 April)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Wednesday, 11 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Tuesday, 10 April)
• Re: [whatwg/url] query state: Parser generates invalid URLs (#379) (Tuesday, 10 April)
• [whatwg/url] "For each byte in buffer: If byte is less than ..." (#379) (Tuesday, 10 April)

Linus Unnebäck

• [w3c/clipboard-apis] Clarify promise rejection value (#76) (Tuesday, 3 April)

LizzieontheBay

• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205) (Monday, 23 April)
• Re: [whatwg/xhr] Editorial: less-confusing content-type manipulation algorithm for send() (#197) (Tuesday, 17 April)

Lukasz Anforowicz

• Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686) (Monday, 30 April)
• Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686) (Monday, 30 April)
• Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686) (Monday, 30 April)
• Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686) (Monday, 30 April)
• Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686) (Monday, 30 April)
• Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686) (Monday, 30 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Wednesday, 25 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Wednesday, 25 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Wednesday, 25 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Wednesday, 25 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Wednesday, 25 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Tuesday, 24 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Tuesday, 24 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Monday, 23 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Monday, 23 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Wednesday, 18 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Wednesday, 18 April)
• Re: [whatwg/fetch] CORB: nosniff handling (#686) (Thursday, 12 April)
• Re: [whatwg/fetch] From-Origin (#687) (Saturday, 7 April)
• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Wednesday, 4 April)

Léonie Watson

• [w3ctag/design-reviews] Request TAG review of HTML5.3 (#275) (Thursday, 26 April)

Maciej Stachowiak

• Re: [whatwg/fetch] From-Origin (#687) (Monday, 16 April)

Malvoz

• [w3c/ServiceWorker] Correct link to nightly version (#1306) (Sunday, 22 April)

Marc G.

• Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb) (Tuesday, 17 April)
• Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb) (Tuesday, 17 April)
• Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb) (Tuesday, 17 April)
• Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb) (Tuesday, 17 April)

Marcin K

• Re: [whatwg/url] UrlSearchParams.set stringifier clarification (#383) (Monday, 30 April)
• Re: [whatwg/url] UrlSearchParams.set stringifier clarification (#383) (Monday, 30 April)
• [whatwg/url] UrlSearchParams.set stringifier clarification (#383) (Sunday, 29 April)

Marcos Cáceres

• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Tuesday, 24 April)
• Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550) (Tuesday, 24 April)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Monday, 23 April)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Monday, 23 April)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Monday, 23 April)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Monday, 23 April)
• Re: [w3c/manifest] Worried about IDL changes (#667) (Monday, 23 April)
• Re: [w3c/manifest] Worried about IDL changes (#667) (Monday, 23 April)
• [w3c/manifest] Worried about IDL changes (#667) (Monday, 23 April)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Monday, 23 April)
• Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659) (Tuesday, 17 April)
• Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659) (Tuesday, 17 April)
• Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659) (Tuesday, 17 April)
• Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 16 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 16 April)
• Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541) (Friday, 6 April)
• Re: [w3c/manifest] Minor text tweaks (#664) (Tuesday, 3 April)
• Re: [w3c/manifest] Minor text tweaks (#664) (Tuesday, 3 April)
• Re: [w3c/selection-api] fixup some ReSpec issues (#95) (Monday, 2 April)
• Re: [w3c/selection-api] fixup some ReSpec issues (#95) (Monday, 2 April)
• Re: [w3c/selection-api] fixup some ReSpec issues (#95) (Monday, 2 April)
• Re: [w3c/selection-api] fixup some ReSpec issues (#95) (Monday, 2 April)
• Re: [w3c/selection-api] fixup some ReSpec issues (#95) (Monday, 2 April)
• [w3c/selection-api] fixup some ReSpec issues (#95) (Monday, 2 April)

Marijn Kruisselbrink

• Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552) (Friday, 27 April)
• [w3c/ServiceWorker] Size constraints for cache names? (#1310) (Friday, 27 April)
• Re: [w3c/FileAPI] Refine StructuredSerializeForStorage behavior (#98) (Tuesday, 17 April)

Mark Nottingham

• Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475) (Thursday, 12 April)
• Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475) (Thursday, 12 April)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Thursday, 12 April)
• Re: [w3ctag/design-reviews] Changing requirements for Well-Known URIs (#237) (Sunday, 8 April)
• Re: [w3ctag/design-reviews] BCP56bis (#232) (Sunday, 8 April)
• Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] BCP56bis (#232) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Thursday, 5 April)
• Re: [w3ctag/design-reviews] BCP56bis (#232) (Thursday, 5 April)
• [w3ctag/design-reviews] Changing requirements for Well-Known URIs (#237) (Monday, 2 April)

Mark S. Everitt

• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)

Martin Thomson

• Re: [w3c/push-api] Update privacy and server choice... (#294) (Thursday, 12 April)
• Re: [w3c/push-api] Security policies WRT Push traffic (#270) (Thursday, 12 April)
• Re: [w3c/push-api] Rephrase the bit about the UA chosing the push service (#287) (Thursday, 12 April)
• Re: [w3c/push-api] Rephrase the bit about the UA chosing the push service (#287) (Thursday, 12 April)
• Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239) (Monday, 9 April)

Masayuki Nakano

• Re: [w3c/uievents] Event order between "compositionend" and "input" (#202) (Saturday, 21 April)
• [w3c/uievents] Event order between "compositionend" and "input" (#202) (Saturday, 21 April)
• Re: [w3c/editing] make need of execCommand to hide table controls go away on FF (#171) (Friday, 6 April)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304) (Wednesday, 25 April)
• Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304) (Wednesday, 25 April)
• [w3c/ServiceWorker] Service-Worker-Allowed can be cross-origin to the script URL. (#1307) (Monday, 23 April)
• Re: [whatwg/fetch] More informative error types (#526) (Thursday, 12 April)
• Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189) (Thursday, 12 April)
• Re: [whatwg/fetch] More informative error types (#526) (Thursday, 12 April)
• Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189) (Wednesday, 11 April)

Matt Giuca

• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Friday, 27 April)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Monday, 23 April)
• Re: [w3c/manifest] Support window preferred/initial (minimal?) sizes (#436) (Friday, 20 April)
• Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Thursday, 12 April)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Thursday, 12 April)
• Re: [w3c/manifest] New Boolean members to control interaction with related applications (#658) (Monday, 9 April)

Matt Menke

• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Monday, 23 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Monday, 23 April)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Wednesday, 11 April)

Matteo

• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 16 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 16 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Wednesday, 11 April)

Matteo Collina

• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Thursday, 12 April)
• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Thursday, 12 April)

Mike Amundsen

• Re: [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240) (Wednesday, 11 April)

Mike Taylor

• Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626) (Friday, 6 April)
• Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626) (Thursday, 5 April)
• Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626) (Thursday, 5 April)

Mike West

• Re: [whatwg/fetch] From-Origin (#687) (Monday, 23 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding (#715) (Monday, 23 April)
• Re: [whatwg/fetch] Set response's CSP list once (#701) (Tuesday, 17 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Tuesday, 17 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)
• Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700) (Monday, 16 April)
• Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239) (Monday, 9 April)
• Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239) (Saturday, 7 April)
• [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239) (Friday, 6 April)
• Re: [whatwg/fetch] From-Origin (#687) (Thursday, 5 April)
• Re: [whatwg/fetch] From-Origin (#687) (Wednesday, 4 April)
• Re: [whatwg/fetch] From-Origin (#687) (Tuesday, 3 April)
• Re: [whatwg/fetch] From-Origin (#687) (Tuesday, 3 April)

Moritz Kneilmann

• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Friday, 20 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Thursday, 19 April)

Mounir Lamouri

• Re: [w3c/screen-orientation] Link Screen Orientation with Fullscreen more cleanly (#62) (Friday, 20 April)
• Re: [w3c/screen-orientation] Test suite (#95) (Friday, 20 April)
• Re: [w3c/screen-orientation] Test suite (#95) (Friday, 20 April)
• Re: [w3c/permissions] autoplay permission (#172) (Sunday, 8 April)
• Re: [w3c/permissions] autoplay permission (#172) (Sunday, 8 April)

Ms2ger

• Re: [heycam/webidl] No location for constants on callback interface (#539) (Wednesday, 4 April)

MSI GP70 2QE

• Re: [whatwg/fetch] Typo2018 (#690) (Tuesday, 3 April)
• [whatwg/fetch] Typo2018 (#690) (Tuesday, 3 April)

Nick Harper

• Re: [whatwg/fetch] Update Fetch to support Token Binding (#715) (Wednesday, 25 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 5 April)

offirmo

• Re: [whatwg/fetch] Question — Why can I not read the stream again ? (#196) (Monday, 2 April)

ojan

• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 3 April)

oneacik

• Re: [whatwg/url] "The fragment percent-encode set is the C0 contr..." (#378) (Tuesday, 10 April)
• [whatwg/url] "The fragment percent-encode set is the C0 contr..." (#378) (Monday, 9 April)

Ovidio Henriquez

• Re: [w3ctag/design-reviews] Review Request: WebUSB on Dedicated and Shared Workers (#277) (Monday, 30 April)
• [w3ctag/design-reviews] Review Request: WebUSB on Dedicated and Shared Workers (#277) (Friday, 27 April)

Pat Mächler

• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Monday, 23 April)

Patrick H. Lauke

• Re: [w3c/touch-events] Should spec mention “touch adjustment" behavior? (#93) (Friday, 27 April)
• Re: [w3c/touch-events] Add note to mention UA might adjusting touch target (#95) (Friday, 27 April)
• Re: [w3c/touch-events] Add note to mention UA might adjusting touch target (#95) (Friday, 27 April)
• Re: [w3c/touch-events] Add note to mention UA might adjusting touch target (#95) (Friday, 27 April)
• Re: [w3c/touch-events] Should spec mention “touch adjustment" behavior? (#93) (Thursday, 26 April)
• Re: [w3c/touch-events] Remove createTouch and createTouch list (#96) (Thursday, 26 April)

patrick kettner

• Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659) (Tuesday, 17 April)

Peter Linss

• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Sunday, 8 April)
• Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Signed Exchanges (#235) (Saturday, 7 April)

Philip Jägenstedt

• Re: [w3c/permissions] Using Web IDL to describe WebDriver JSON is a bit unusual (#174) (Thursday, 26 April)
• Re: [whatwg/url] URL's object can no longer be a MediaStream (#381) (Tuesday, 24 April)
• Re: [whatwg/fetch] Editorial: use Infra to define header list (#713) (Tuesday, 24 April)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Wednesday, 18 April)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Wednesday, 18 April)
• Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708) (Wednesday, 18 April)
• Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708) (Wednesday, 18 April)
• Re: [w3c/permissions] Using Web IDL to describe WebDriver JSON is a bit unusual (#174) (Wednesday, 18 April)
• [w3c/permissions] Using Web IDL to describe WebDriver JSON is a bit unusual (#174) (Wednesday, 18 April)
• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Monday, 16 April)
• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Monday, 16 April)
• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Monday, 16 April)
• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Monday, 16 April)
• Re: [whatwg/dom] `cloneNode` should preserve element prototype (#565) (Sunday, 15 April)
• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Thursday, 12 April)
• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Thursday, 12 April)
• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Thursday, 12 April)
• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Thursday, 12 April)

Photopea

• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Tuesday, 17 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 16 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 16 April)
• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Monday, 16 April)

Rakina Zata Amni

• Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Monday, 9 April)

raymeskhoury

• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Monday, 9 April)

Rhy Moore

• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Saturday, 28 April)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Friday, 27 April)

Rikki Gibson

• Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Wednesday, 18 April)

Rimas Misevičius

• Re: [whatwg/url] "Let pointer be a pointer to first code point in..." (#373) (Monday, 2 April)

Rob Dodson

• Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233) (Wednesday, 25 April)
• Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233) (Tuesday, 17 April)

rolivo

• Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (4cc72bd) (Wednesday, 4 April)
• [w3c/ServiceWorker] Give a fine grade to the Service Worker's lifetime (#1297) (Wednesday, 4 April)
• Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (4cc72bd) (Tuesday, 3 April)

Rouslan Solomakhin

• Re: [w3ctag/design-reviews] Payment Handler (#231) (Thursday, 12 April)

Russell Bicknell

• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Wednesday, 25 April)

Ryosuke Niwa

• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 19 April)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Monday, 16 April)
• Re: [whatwg/fetch] From-Origin (#687) (Thursday, 12 April)
• Re: [whatwg/fetch] From-Origin (#687) (Thursday, 12 April)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Wednesday, 11 April)
• Re: [whatwg/fetch] From-Origin (#687) (Saturday, 7 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Saturday, 7 April)
• Re: [whatwg/fetch] From-Origin (#687) (Thursday, 5 April)
• Re: [whatwg/fetch] From-Origin (#687) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [whatwg/fetch] From-Origin (#687) (Thursday, 5 April)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 5 April)
• Re: [whatwg/fetch] From-Origin (#687) (Wednesday, 4 April)
• Re: [w3c/selection-api] fixup some ReSpec issues (#95) (Monday, 2 April)
• Re: [w3c/selection-api] fixup some ReSpec issues (#95) (Monday, 2 April)
• Re: [w3c/webcomponents] [Template Instantiation] Layering and additional use cases (#747) (Sunday, 1 April)

sanjida3

• [whatwg/fetch] Java run bug report (#692) (Sunday, 8 April)
• Re: [whatwg/fetch] Java run bug report (#692) (Sunday, 8 April)

Shiino Yuki

• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Tuesday, 10 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Tuesday, 10 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Monday, 9 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Friday, 6 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Friday, 6 April)
• Re: [heycam/webidl] No location for constants on callback interface (#539) (Wednesday, 4 April)
• Re: [heycam/webidl] No location for constants on callback interface (#539) (Wednesday, 4 April)
• [heycam/webidl] No location for constants on callback interface (#539) (Wednesday, 4 April)

sleevi

• Re: [whatwg/fetch] Define the "Preload Cache" (#590) (Thursday, 12 April)

smartha66

• [whatwg/dom] downloads (#639) (Monday, 23 April)

smaug----

• [w3c/touch-events] It is unclear how targetTouches should work with Shadow DOM (#97) (Monday, 30 April)
• Re: [w3c/touch-events] 'Retargeting steps' expose closed Shadow DOM to the outside world (#92) (Monday, 30 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Monday, 9 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Monday, 9 April)
• Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334) (Friday, 6 April)

Sotiris Kiritsis

• Re: [w3c/uievents] [Question] select change + mousedown behavior (#201) (Thursday, 12 April)

spanicker

• Re: [w3c/IndexedDB] How should commit() failures be surfaced when freezing / unloading (#237) (Monday, 30 April)
• [w3c/IndexedDB] How should commit() failures be surfaced when freezing / unloading (#237) (Thursday, 26 April)
• Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205) (Thursday, 12 April)
• Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205) (Monday, 9 April)
• Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205) (Friday, 6 April)

Stephanie Rewis

• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Friday, 27 April)

StitchNG

• [w3c/ServiceWorker] Intecepts progress event of AJAX calls (#1298) (Thursday, 5 April)

Suguru Inatomi

• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Wednesday, 25 April)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 24 April)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 24 April)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 24 April)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Monday, 23 April)

Sunny Ripert

• Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226) (Friday, 27 April)

Surma

• Re: [whatwg/streams] Linkify all class definitions (#913) (Monday, 9 April)

Tab Atkins Jr.

• Re: [whatwg/dom] Editorial: reference "set an existing attribute value" (#638) (Monday, 16 April)
• Re: [w3ctag/design-reviews] CSS Layout API (#224) (Monday, 9 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)

Takashi Toyoshima

• [whatwg/fetch] Add { 548, 'afp' } to the blocked bad ports (#694) (Tuesday, 10 April)

TAMURA, Kent

• Re: [whatwg/url] Remove _charset_ handling. (#382) (Friday, 27 April)
• Re: [whatwg/url] Remove _charset_ handling. (#382) (Friday, 27 April)
• [whatwg/url] Remove _charset_ handling. (#382) (Wednesday, 25 April)
• Re: [whatwg/url] Remove _charset_ handling. (#382) (Wednesday, 25 April)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Thursday, 12 April)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 4 April)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 4 April)

TanviHacks

• Re: [whatwg/fetch] From-Origin (#687) (Tuesday, 17 April)

Tejas Kumar

• Re: [whatwg/fetch] just do it (048d10e) (Friday, 27 April)
• Re: [whatwg/fetch] just do it (048d10e) (Friday, 27 April)

Thomas Steiner

• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Monday, 23 April)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Monday, 23 April)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Monday, 23 April)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Sunday, 22 April)
• [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Sunday, 22 April)
• Re: [w3c/ServiceWorker] should prefetch loads trigger FetchEvents? (#1302) (Tuesday, 17 April)
• Re: [w3c/manifest] Add support for "share_target" property (#665) (Monday, 16 April)
• Re: [w3c/manifest] Add support for "share_target" property (#665) (Monday, 16 April)
• [w3c/manifest] Add support for "share_target" property (#665) (Monday, 16 April)

Till Schneidereit

• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Friday, 6 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Thursday, 5 April)
• Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917) (Wednesday, 4 April)

Timo

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Wednesday, 18 April)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Wednesday, 18 April)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Wednesday, 18 April)

Timothy Gu

• Re: [heycam/webidl] Editorial: use SetFunctionLength abstract ops (#549) (Thursday, 19 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Wednesday, 18 April)
• Re: [whatwg/fetch] Handle failure while handling content codings (#710) (Wednesday, 18 April)
• Re: [whatwg/url] "The fragment percent-encode set is the C0 contr..." (#378) (Tuesday, 10 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 9 April)

Tobias Buschor

• Re: [whatwg/dom] Abort controller design (#438) (Monday, 9 April)

Tobie Langel

• Re: [heycam/webidl] Disallow [LegacyArrayClass] on globals (#545) (Sunday, 29 April)
• Re: [heycam/webidl] Disallow [LegacyArrayClass] on globals (#545) (Sunday, 29 April)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#291) (Sunday, 29 April)
• Re: [heycam/webidl] Remove [LegacyArrayClass] (#551) (Sunday, 29 April)
• Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548) (Wednesday, 25 April)
• Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548) (Wednesday, 25 April)
• Re: [heycam/webidl] Editorial: use SetFunctionLength abstract ops (#549) (Friday, 20 April)
• [heycam/webidl] Editorial: use SetFunctionLength abstract ops (#549) (Thursday, 19 April)
• Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548) (Friday, 13 April)
• Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548) (Friday, 13 April)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Friday, 13 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• Re: [heycam/webidl] Meta: remove label info from README (#546) (Tuesday, 10 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Tuesday, 10 April)
• Re: [heycam/webidl] Prototype of @@unscopable object (#496) (Tuesday, 10 April)
• [heycam/webidl] Meta: remove label info from README (#546) (Tuesday, 10 April)
• Re: [heycam/webidl] Fix broken labels (#543) (Tuesday, 10 April)
• Re: [heycam/webidl] Fix broken labels (#543) (Tuesday, 10 April)
• [heycam/webidl] Disallow [LegacyArrayClass] on globals (#545) (Tuesday, 10 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Tuesday, 10 April)
• [heycam/webidl] Should an {{@@unscopables}} property also be defined for globals? (#544) (Tuesday, 10 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Tuesday, 10 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Tuesday, 10 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Tuesday, 10 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Tuesday, 10 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Tuesday, 10 April)
• [heycam/webidl] Fix broken labels (#543) (Tuesday, 10 April)
• [heycam/webidl] Remove section numbers from ES references (#542) (Tuesday, 10 April)
• Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541) (Monday, 9 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Sunday, 8 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Sunday, 8 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Sunday, 8 April)
• Re: [heycam/webidl] Note regarding old vs new Mixin syntax (#536) (Sunday, 8 April)
• Re: [heycam/webidl] Note regarding old vs new Mixin syntax (#536) (Sunday, 8 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Sunday, 8 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Sunday, 8 April)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Sunday, 8 April)
• Re: [heycam/webidl] Editorial: minor copy editing (#538) (Saturday, 7 April)
• Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541) (Friday, 6 April)

Tom Schuster

• Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681) (Wednesday, 4 April)

Tomasz Jakut

• Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643) (Monday, 30 April)

Tomek Wytrębowicz

• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 4 April)

Travis Leithead

• Re: [w3ctag/design-reviews] Review request for WebVR (#185) (Tuesday, 24 April)
• Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52) (Tuesday, 24 April)
• Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52) (Tuesday, 24 April)
• Re: [w3ctag/design-reviews] HTML General Review (#174) (Tuesday, 24 April)
• Re: [w3ctag/design-reviews] Review request for WebVR (#185) (Tuesday, 24 April)
• Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52) (Tuesday, 24 April)
• Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548) (Wednesday, 18 April)
• Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: Cross-Document Messaging (#269) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: Web Storage (#271) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: Web Workers (#270) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: App Cache (#263) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Drawing (#260) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: XML Infrastructure (#272) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Templates (#259) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Timers and Timeslicing (#266) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: Navigation and Browsing History (#262) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Option Lists (#255) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: Browsing Contexts and Security (#250) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: Server-Sent Events (#267) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: Web Sockets (#268) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Obsolete Features (#273) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: IANA Registries (#274) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: Structured Serialize/Deserialize (#243) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Media (#251) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Images (#249) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Ruby (#248) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Utilities (#264) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Parsing (#265) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Scripting (#258) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: Microdata (#261) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Focus (#257) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Input (#254) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML User Interaction (#256) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Forms (#253) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Tables (#252) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: Custom Elements (#244) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Styling (#246) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Lists (#247) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Linking (#245) (Tuesday, 17 April)
• [w3ctag/design-reviews] HTML General Review: HTML Document and Elements (#242) (Tuesday, 17 April)
• Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205) (Tuesday, 17 April)
• Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205) (Tuesday, 17 April)
• Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233) (Tuesday, 17 April)
• Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205) (Tuesday, 17 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Monday, 16 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Monday, 16 April)
• [heycam/webidl] Poorly worded normative requirement could be improved (#548) (Thursday, 12 April)
• Re: [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• [heycam/webidl] Consider [LegacyStringClass] (#547) (Thursday, 12 April)
• Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Wednesday, 11 April)
• Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Wednesday, 11 April)
• Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Tuesday, 10 April)
• Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Tuesday, 10 April)
• Re: [w3c/permissions] autoplay permission (#172) (Saturday, 7 April)
• Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Friday, 6 April)
• Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Friday, 6 April)
• Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205) (Friday, 6 April)
• Re: [w3ctag/design-reviews] Find-in-page API(s) (#236) (Friday, 6 April)
• Re: [w3ctag/design-reviews] Request review for Keyboard Map (#238) (Friday, 6 April)
• Re: [w3ctag/design-reviews] HTML General Review (#174) (Friday, 6 April)
• Re: [w3ctag/design-reviews] CSS Layout API (#224) (Thursday, 5 April)
• Re: [w3ctag/design-reviews] Should WebRTC be [SecureContext] (#228) (Thursday, 5 April)

vanupam

• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 3 April)

Vinod Anupam

• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 19 April)
• [whatwg/fetch] Update Fetch to support Token Binding (#715) (Thursday, 19 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 19 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 19 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 14 April)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 5 April)

Wanming Lin

• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Monday, 23 April)
• Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666) (Monday, 23 April)

Winston Chen

• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Thursday, 12 April)
• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Thursday, 12 April)
• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Thursday, 12 April)

Xidorn Quan

• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Wednesday, 4 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 3 April)
• Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124) (Tuesday, 3 April)
• Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123) (Monday, 2 April)

Yayan Sinchan

• [whatwg/storage] Issue (#61) (Thursday, 19 April)

Yoav Weiss

• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Friday, 27 April)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Thursday, 26 April)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Thursday, 26 April)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Thursday, 26 April)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Thursday, 26 April)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Fetching with a particular destination (#521) (Thursday, 26 April)
• Re: [whatwg/fetch] Fetching with a particular destination (#521) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717) (Thursday, 26 April)
• Re: [whatwg/fetch] Define the "Preload Cache" (#590) (Tuesday, 24 April)
• Re: [whatwg/fetch] Define the "Preload Cache" (#590) (Tuesday, 24 April)
• Re: [whatwg/fetch] Client hints difference between navigation and subresources (#707) (Tuesday, 24 April)
• Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Tuesday, 24 April)

youennf

• Re: [whatwg/fetch] From-Origin (#687) (Friday, 13 April)
• Re: [whatwg/fetch] From-Origin (#687) (Saturday, 7 April)
• Re: [whatwg/fetch] From-Origin (#687) (Saturday, 7 April)
• Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Thursday, 5 April)

Yutaka Hirano

• [whatwg/fetch] Add Request's isHistoryNavigation (#718) (Friday, 27 April)
• Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Friday, 27 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Thursday, 26 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Wednesday, 25 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Tuesday, 24 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Tuesday, 24 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Tuesday, 24 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Monday, 23 April)
• Re: [whatwg/fetch] Introduce reload-navigation flag (#685) (Monday, 23 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Monday, 23 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Monday, 23 April)
• Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Monday, 23 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Thursday, 19 April)
• Re: [whatwg/fetch] More informative error types (#526) (Friday, 13 April)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 12 April)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 12 April)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Thursday, 12 April)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Tuesday, 10 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Friday, 6 April)
• Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Friday, 6 April)
• Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Friday, 6 April)
• Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679) (Thursday, 5 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Wednesday, 4 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Wednesday, 4 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Wednesday, 4 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Wednesday, 4 April)
• Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685) (Tuesday, 3 April)
• Re: [whatwg/fetch] Expose Stream Watermarks (#689) (Tuesday, 3 April)

Yves Lafon

• Re: [w3c/ServiceWorker] Correct link to nightly version (#1306) (Tuesday, 24 April)

zb3

• [whatwg/encoding] Identity encoding? (#138) (Thursday, 26 April)

Zirro

• Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552) (Friday, 27 April)

Zoltan Kis

• Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541) (Monday, 9 April)
• Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541) (Monday, 9 April)

Last message date: Monday, 30 April 2018 22:14:24 UTC