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

achristensen07

• Re: [whatwg/fetch] Define data: URLs (#579) (Friday, 19 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Friday, 19 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Friday, 19 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 18 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 17 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 17 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 17 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 11 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 10 January)

Adam Rice

• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Monday, 29 January)
• [whatwg/streams] Add "was ever locked" flag for Encoding standard? (#873) (Monday, 29 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Monday, 29 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Friday, 26 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Friday, 26 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Friday, 26 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Friday, 26 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Friday, 26 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Friday, 26 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Friday, 26 January)
• Re: [whatwg/streams] Export "readable stream", "writable stream" and "chunk" (#871) (Friday, 26 January)
• Re: [whatwg/streams] Export "readable stream", "writable stream" and "chunk" (#871) (Friday, 26 January)
• [whatwg/streams] Export "readable stream", "writable stream" and "chunk" (#871) (Friday, 26 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Thursday, 25 January)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Wednesday, 24 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Tuesday, 23 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Tuesday, 23 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Tuesday, 23 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Tuesday, 23 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Tuesday, 23 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Monday, 22 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Monday, 22 January)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Monday, 22 January)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Monday, 22 January)
• Re: [w3ctag/design-reviews] Transform Streams (#211) (Wednesday, 10 January)
• Re: [whatwg/streams] rethrowAssertionErrorRejection is broken (#865) (Friday, 5 January)

Addison Phillips

• Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Tuesday, 23 January)

Agnel Vishal

• Re: [whatwg/fullscreen] Unable to zoom and scroll in mobile browsers when in full screen. (#110) (Friday, 26 January)
• Re: [whatwg/fullscreen] Unable to zoom and scroll in mobile browsers when in full screen. (#110) (Friday, 26 January)
• Re: [whatwg/fullscreen] The values of meta viewport attribute are not reflected when in full screen mode in android chrome browser. (#111) (Wednesday, 3 January)

Alex

• Re: [w3c/ServiceWorker] Why is it possible to register a service worker that you won't ever be able to remove? (#1258) (Wednesday, 10 January)
• Re: [w3c/ServiceWorker] Why is it possible to register a service worker that you won't ever be able to remove? (#1258) (Wednesday, 10 January)
• [w3c/ServiceWorker] Why is it possible to register a service worker that you won't ever be able to remove? (#1258) (Wednesday, 10 January)

Alex Russell

• Re: [w3ctag/design-reviews] Clear Site Data (#62) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] WebUSB (#108) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] WebUSB (#108) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Clear Site Data (#62) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Transform Streams (#211) (Wednesday, 10 January)

aliams

• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 19 January)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 19 January)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 5 January)
• Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Friday, 5 January)

anatoly techtonik

• Re: [w3c/gamepad] Mapping of HID Events to the Gamepad API (#56) (Tuesday, 2 January)
• Re: [w3c/gamepad] Mapping of HID Events to the Gamepad API (#56) (Monday, 1 January)

Andrea Giammarchi

• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Thursday, 25 January)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Thursday, 25 January)
• Re: [whatwg/dom] Proposal: RangeList (#543) (Thursday, 25 January)
• Re: [whatwg/dom] Proposal: RangeList (#543) (Thursday, 25 January)

Andrea Marchesini

• Re: [whatwg/url] URLSearchParams and URL [Serializable] (#370) (Monday, 29 January)
• [whatwg/url] URLSearchParams and URL [Serializable] (#370) (Tuesday, 23 January)

Andrew Betts

• Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Web payment method manifest (#162) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Web payment method manifest (#162) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] A spec style/structure checklist? (#136) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] A spec style/structure checklist? (#136) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Clear Site Data (#62) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Monday, 22 January)
• Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Friday, 19 January)
• Re: [w3ctag/design-reviews] Web Locks API (#217) (Friday, 19 January)

Angelk90

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

Angelo Liao

• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Tuesday, 16 January)

Anne van Kesteren

• Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186) (Wednesday, 31 January)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] HTML General Review (#174) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] should `ServiceWorker` interface implement `AbstractWorker` mixin? (#1268) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] should `ServiceWorker` interface implement `AbstractWorker` mixin? (#1268) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Should WebRTC be [SecureContext] (#228) (Wednesday, 31 January)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Wednesday, 31 January)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Wednesday, 31 January)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Wednesday, 31 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 31 January)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Wednesday, 31 January)
• Re: [heycam/webidl] More convenient way to refer to / use "map iterators" (#324) (Wednesday, 31 January)
• Re: [whatwg/fetch] data URLs: revised specification (#234) (Wednesday, 31 January)
• Re: [whatwg/fetch] data URLs: revised specification (#234) (Wednesday, 31 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 31 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 31 January)
• Re: [whatwg/fetch] Should fetches to blob URLs be more restricted? (#666) (Wednesday, 31 January)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 31 January)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 31 January)
• Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564) (Wednesday, 31 January)
• Re: [heycam/webidl] Definition of "is an array index" makes "-0" an array index (#516) (Wednesday, 31 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Tuesday, 30 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Tuesday, 30 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Tuesday, 30 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Tuesday, 30 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Tuesday, 30 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Tuesday, 30 January)
• Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564) (Tuesday, 30 January)
• Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564) (Tuesday, 30 January)
• Re: [whatwg/fullscreen] Meta: make Philip the editor (#121) (Tuesday, 30 January)
• Re: [whatwg/fullscreen] Investigate whether nested fullscreen element is necessary (#119) (Tuesday, 30 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fullscreen] Investigate whether nested fullscreen element is necessary (#119) (Monday, 29 January)
• Re: [whatwg/fullscreen] Editorial: fix grammar in notes about run the fullscreen steps (#118) (Monday, 29 January)
• Re: [whatwg/fullscreen] Editorial: fix grammar in notes about run the fullscreen steps (#118) (Monday, 29 January)
• Re: [whatwg/fullscreen] Editorial: remove a stray/double "tree order" in note (#117) (Monday, 29 January)
• Re: [whatwg/fullscreen] Editorial: remove a stray/double "tree order" in note (#117) (Monday, 29 January)
• Re: [heycam/webidl] add a type to represent the undefined value (#60) (Monday, 29 January)
• [w3c/push-api] "set its value to a BufferSource" (#290) (Sunday, 28 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Friday, 26 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Friday, 26 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Friday, 26 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 25 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Thursday, 25 January)
• Re: [w3c/webcomponents] Interfaces for web components (#725) (Thursday, 25 January)
• Re: [w3c/webcomponents] Interfaces for web components (#725) (Thursday, 25 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Wednesday, 24 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Wednesday, 24 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 24 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 24 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 24 January)
• Re: [whatwg/url] URLSearchParams and URL [Serializable] (#370) (Wednesday, 24 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 24 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Wednesday, 24 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Wednesday, 24 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Tuesday, 23 January)
• Re: [whatwg/xhr] Make FormData a cloneable object (#55) (Tuesday, 23 January)
• Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564) (Tuesday, 23 January)
• [whatwg/fetch] data: URL generator (#665) (Tuesday, 23 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Tuesday, 23 January)
• Re: [whatwg/fetch] Return a network error in case of no-cors mode and redirect being not follow (#663) (Tuesday, 23 January)
• Re: [whatwg/fetch] Return a network error in case of no-cors mode and redirect being not follow (#663) (Tuesday, 23 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 23 January)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Tuesday, 23 January)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Tuesday, 23 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 23 January)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Tuesday, 23 January)
• Re: [whatwg/dom] "A slotable has an associated name" should read slot instead of name (#563) (Tuesday, 23 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Tuesday, 23 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Monday, 22 January)
• Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Monday, 22 January)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Monday, 22 January)
• Re: [whatwg/dom] Specify [LegacyWindowAlias=HTMLDocument] on Document (#551) (Monday, 22 January)
• Re: [whatwg/fetch] Response.redirect() results in status message still being OK? (#664) (Saturday, 20 January)
• Re: [whatwg/fetch] Response.redirect() results in status message still being OK? (#664) (Saturday, 20 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Friday, 19 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Friday, 19 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 18 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Thursday, 18 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Thursday, 18 January)
• Re: [whatwg/url] "Let ipv4Host be the result of IPv4 parsing asci..." (#367) (Wednesday, 17 January)
• Re: [whatwg/url] "Let ipv4Host be the result of IPv4 parsing asci..." (#367) (Wednesday, 17 January)
• Re: [whatwg/url] "For each code point in input, UTF-8 percent enc..." (#368) (Wednesday, 17 January)
• Re: [whatwg/url] "For each code point in input, UTF-8 percent enc..." (#368) (Wednesday, 17 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Tuesday, 16 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 15 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 15 January)
• Re: [heycam/webidl] Add [InsecureContext] (#471) (Monday, 15 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Monday, 15 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 15 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 15 January)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Monday, 15 January)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Monday, 15 January)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Saturday, 13 January)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Saturday, 13 January)
• Re: [whatwg/encoding] Figure out if anything is needed for better HTML integration (#128) (Saturday, 13 January)
• Re: [whatwg/streams] Bikeshed warnings (#869) (Saturday, 13 January)
• [whatwg/streams] Bikeshed warnings (#869) (Saturday, 13 January)
• Re: [whatwg/fetch] Add RequestInit members to Request domintro (#620) (Saturday, 13 January)
• Re: [whatwg/fetch] Add RequestInit members to Request domintro (#620) (Saturday, 13 January)
• Re: [whatwg/fetch] Add RequestInit members to Request domintro (#620) (Saturday, 13 January)
• Re: [whatwg/fetch] Add RequestInit members to Request domintro (#620) (Saturday, 13 January)
• Re: [heycam/webidl] [wip] First pass at adding internal slots (#495) (Saturday, 13 January)
• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Saturday, 13 January)
• Re: [whatwg/xhr] Meta: remove mention of CC0 (#187) (Friday, 12 January)
• [whatwg/xhr] Meta: remove mention of CC0 (#187) (Friday, 12 January)
• Re: [w3c/webcomponents] [SHADOW] Sequential Focus Navigation uses undefined "For each node tree TREE in DOCUMENT" (#720) (Friday, 12 January)
• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Friday, 12 January)
• Re: [whatwg/dom] 'Retargeting steps' run at wrong time (#561) (Thursday, 11 January)
• Re: [whatwg/xhr] The xhr logo appears to be copied from AFC Ajax (Dutch soccer club) (#186) (Thursday, 11 January)
• Re: [w3c/touch-events] 'Retargeting steps' expose closed Shadow DOM to the outside world (#92) (Thursday, 11 January)
• Re: [whatwg/url] Meta: adopt more whatwg/meta guidelines (#365) (Wednesday, 10 January)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 10 January)
• Re: [whatwg/dom] Proposal: Storage Access API (#560) (Wednesday, 10 January)
• Re: [whatwg/fetch] Redirect and credential URLs (#660) (Wednesday, 10 January)
• Re: [whatwg/fetch] Redirect and credential URLs (#660) (Wednesday, 10 January)
• Re: [whatwg/dom] Using [Exposed=Window] (#89) (Wednesday, 10 January)
• Re: [whatwg/dom] Using [Exposed=Window] (#89) (Wednesday, 10 January)
• Re: [whatwg/dom] Proposal: Storage Access API (#560) (Wednesday, 10 January)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 10 January)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 10 January)
• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Wednesday, 10 January)
• Re: [whatwg/url] Editorial: fix port value in the origin's example (#366) (Tuesday, 9 January)
• Re: [whatwg/url] Editorial: fix port value in the origin's example (#366) (Tuesday, 9 January)
• Re: [whatwg/url] Editorial: fix port value in the origin's example (#366) (Tuesday, 9 January)
• Re: [whatwg/url] Editorial: fix port value in the origin's example (#366) (Tuesday, 9 January)
• Re: [whatwg/storage] Meta: reference whatwg/meta resources (#59) (Tuesday, 9 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Tuesday, 9 January)
• Re: [whatwg/dom] Inconsistency in execution of unclosed attribute selector for querySelector (#549) (Monday, 8 January)
• Re: [whatwg/dom] Inconsistency in execution of unclosed attribute selector for querySelector (#549) (Monday, 8 January)
• Re: [whatwg/fetch] Do not allow CORS responses to "same-origin" requests (#655) (Monday, 8 January)
• Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Monday, 8 January)
• Re: [whatwg/dom] Meta: define merge policy and add CONTRIBUTING.md (#559) (Monday, 8 January)
• Re: [whatwg/url] Meta: adopt more whatwg/meta guidelines (#365) (Monday, 8 January)
• Re: [whatwg/storage] Meta: reference whatwg/meta resources (#59) (Monday, 8 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Monday, 8 January)
• Re: [whatwg/dom] Meta: define merge policy and add CONTRIBUTING.md (#559) (Monday, 8 January)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Monday, 8 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Define how to handle bad content encoding (#657) (Monday, 8 January)
• Re: [whatwg/fetch] Define how to handle bad content encoding (#657) (Monday, 8 January)
• Re: [whatwg/dom] Meta: define merge policy and add CONTRIBUTING.md (#559) (Monday, 8 January)
• Re: [whatwg/dom] Meta: define merge policy and add CONTRIBUTING.md (#559) (Sunday, 7 January)
• Re: [whatwg/dom] Proposal: Spellcheck API (#547) (Sunday, 7 January)
• Re: [whatwg/fullscreen] Meta: align with whatwg/meta resources (#115) (Sunday, 7 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Sunday, 7 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Sunday, 7 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Sunday, 7 January)
• [whatwg/dom] Meta: define merge policy and add CONTRIBUTING.md (#559) (Sunday, 7 January)
• Re: [whatwg/fullscreen] Meta: align with whatwg/meta resources (#115) (Sunday, 7 January)
• Re: [whatwg/storage] estimate() steps need "Otherwise" (#57) (Sunday, 7 January)
• Re: [whatwg/storage] Correct branching in estimate() (#58) (Sunday, 7 January)
• Re: [whatwg/fullscreen] Meta: align with whatwg/meta resources (#115) (Saturday, 6 January)
• [whatwg/storage] Meta: reference whatwg/meta resources (#59) (Saturday, 6 January)
• [whatwg/fullscreen] Meta: align with whatwg/meta resources (#115) (Saturday, 6 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Saturday, 6 January)
• Re: [whatwg/url] Meta: adopt more whatwg/meta guidelines (#365) (Saturday, 6 January)
• Re: [whatwg/url] Meta: adopt more whatwg/meta guidelines (#365) (Saturday, 6 January)
• Re: [whatwg/url] Editorial: Update link to maintainer guidlines (#364) (Saturday, 6 January)
• Re: [whatwg/fetch] Meta: reference whatwg/meta resources (#656) (Saturday, 6 January)
• Re: [whatwg/xhr] Meta: reference whatwg/meta resources (#185) (Saturday, 6 January)
• Re: [whatwg/dom] Define concatenation (#555) (Saturday, 6 January)
• Re: [whatwg/dom] Use Infra's concatenation definition (#556) (Saturday, 6 January)
• Re: [whatwg/url] Meta: adopt more whatwg/meta guidelines (#365) (Saturday, 6 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Saturday, 6 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Saturday, 6 January)
• Re: [whatwg/xhr] Meta: reference whatwg/meta resources (#185) (Saturday, 6 January)
• [whatwg/xhr] Meta: reference whatwg/meta resources (#185) (Saturday, 6 January)
• Re: [whatwg/fetch] Meta: reference whatwg/meta resources (#656) (Saturday, 6 January)
• [whatwg/fetch] Meta: reference whatwg/meta resources (#656) (Saturday, 6 January)
• Re: [whatwg/url] Meta: adopt more whatwg/meta guidelines (#365) (Saturday, 6 January)
• [whatwg/url] Meta: adopt more whatwg/meta guidelines (#365) (Saturday, 6 January)
• Re: [whatwg/url] Editorial: Update link to maintainer guidlines (#364) (Saturday, 6 January)
• Re: [whatwg/url] Editorial: Update link to maintainer guidlines (#364) (Saturday, 6 January)
• Re: [whatwg/url] Editorial: Link to whatwg/meta documents (#363) (Saturday, 6 January)
• Re: [whatwg/dom] Editorial: Link to whatwg/meta COMMITING.md (#558) (Saturday, 6 January)
• Re: [whatwg/dom] Editorial: Link to whatwg/meta COMMITING.md (#558) (Saturday, 6 January)
• Re: [whatwg/fetch] Create gentlejack (#550) (Saturday, 6 January)
• Re: [whatwg/fetch] Safelist Content-Length header (#626) (Saturday, 6 January)
• Re: [whatwg/fetch] Make observability examples nitpick-proof (#642) (Saturday, 6 January)
• Re: [whatwg/fetch] Nitpick: The user agent can terminate the fetch ... "res => res.body.getReader().closed" (#625) (Saturday, 6 January)
• [whatwg/fetch] Do not allow CORS responses to "same-origin" requests (#655) (Saturday, 6 January)
• [whatwg/storage] Correct branching in estimate() (#58) (Saturday, 6 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Saturday, 6 January)
• Re: [whatwg/fullscreen] Link Japanese translation (#114) (Friday, 5 January)
• [whatwg/fullscreen] Link Japanese translation (#114) (Friday, 5 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Friday, 5 January)
• Re: [whatwg/fetch] The initiator/destination/CSP table is not exhaustive when it comes t… (#654) (Friday, 5 January)
• Re: [whatwg/fetch] what is the Request.destination for modules and es `import()`? (#652) (Friday, 5 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Friday, 5 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Friday, 5 January)
• Re: [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308) (Friday, 5 January)
• Re: [whatwg/fetch] The initiator/destination/CSP table is not exhaustive when it comes t… (#654) (Friday, 5 January)
• Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Friday, 5 January)
• Re: [whatwg/fetch] The initiator/destination/CSP table is not exhaustive when it comes t… (#654) (Friday, 5 January)
• [whatwg/fetch] The initiator/destination/CSP table is not exhaustive when it comes t… (#654) (Friday, 5 January)
• Re: [whatwg/dom] Use Infra's concatenation definition (#556) (Friday, 5 January)
• Re: [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308) (Friday, 5 January)
• Re: [whatwg/fetch] Provide ability to encode content from browser/runtime in fetch API. (#653) (Friday, 5 January)
• Re: [whatwg/storage] Meta: use new WHATWG boilerplate and license (#56) (Friday, 5 January)
• Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Friday, 5 January)
• Re: [whatwg/fetch] what is the Request.destination for modules and es `import()`? (#652) (Friday, 5 January)
• Re: [whatwg/fetch] Meta: use new WHATWG boilerplate and license (#651) (Friday, 5 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Friday, 5 January)
• Re: [whatwg/fullscreen] Meta: use new WHATWG boilerplate and license (#113) (Friday, 5 January)
• Re: [whatwg/dom] Use Infra's concatenation definition (#556) (Thursday, 4 January)
• Re: [whatwg/dom] Use Infra's concatenation definition (#556) (Thursday, 4 January)
• Re: [whatwg/dom] Define concatenation (#555) (Thursday, 4 January)
• Re: [whatwg/dom] Use Infra's concatenation definition (#556) (Thursday, 4 January)
• [whatwg/dom] Use Infra's concatenation definition (#556) (Thursday, 4 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 4 January)
• [whatwg/dom] Define concatenation (#555) (Thursday, 4 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 4 January)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Thursday, 4 January)
• Re: [whatwg/fullscreen] Meta: use new WHATWG boilerplate and license (#113) (Thursday, 4 January)
• Re: [whatwg/dom] Meta: use new WHATWG boilerplate and license (#553) (Thursday, 4 January)
• Re: [whatwg/fetch] Constructing a Response with Content-Encoding? (#589) (Thursday, 4 January)
• Re: [whatwg/fetch] Editorial: address Bikeshed and minor wording issues (#640) (Thursday, 4 January)
• Re: [whatwg/fetch] Editorial: address Bikeshed and minor wording issues (#640) (Thursday, 4 January)
• Re: [whatwg/fetch] Meta: use new WHATWG boilerplate and license (#651) (Thursday, 4 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Thursday, 4 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Thursday, 4 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Thursday, 4 January)
• Re: [whatwg/fullscreen] Consider forbidding <frame> element from entering fullscreen (#112) (Wednesday, 3 January)
• Re: [whatwg/fullscreen] The values of meta viewport attribute are not reflected when in full screen mode in android chrome browser. (#111) (Wednesday, 3 January)
• Re: [whatwg/fullscreen] The values of meta viewport attribute are not reflected when in full screen mode in android chrome browser. (#111) (Wednesday, 3 January)
• Re: [whatwg/dom] Specify [LegacyWindowAlias=HTMLDocument] on Document (#551) (Wednesday, 3 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Wednesday, 3 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Wednesday, 3 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Wednesday, 3 January)
• Re: [whatwg/xhr] localhost:8989 (#183) (Tuesday, 2 January)
• Re: [whatwg/xhr] localhost:7676 (#182) (Tuesday, 2 January)

Anssi Kostiainen

• Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Sensor APIs (#207) (Thursday, 18 January)
• Re: [w3ctag/design-reviews] Sensor APIs (#207) (Friday, 12 January)

Ashley (Scirra)

• Re: [w3c/webcomponents] HTML Modules (#645) (Wednesday, 17 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Wednesday, 3 January)

avidrissman

• Re: [whatwg/fullscreen] Ending fullscreen for popups (#116) (Saturday, 27 January)
• Re: [whatwg/fullscreen] Ending fullscreen for popups (#116) (Wednesday, 24 January)
• Re: [whatwg/fullscreen] Ending fullscreen for popups (#116) (Wednesday, 24 January)
• [whatwg/fullscreen] Ending fullscreen for popups (#116) (Wednesday, 24 January)

Ayumi Hamasaki

• [w3c/ServiceWorker] Turn off a service worker in parts of the website (#1257) (Tuesday, 9 January)

beidson

• Re: [w3c/gamepad] Mapping of HID Events to the Gamepad API (#56) (Tuesday, 2 January)

Ben Kelly

• Re: [whatwg/fetch] Should fetches to blob URLs be more restricted? (#666) (Wednesday, 31 January)
• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Wednesday, 31 January)
• Re: [whatwg/fetch] Should fetches to blob URLs be more restricted? (#666) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] should `ServiceWorker` interface implement `AbstractWorker` mixin? (#1268) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] should `ServiceWorker` interface implement `AbstractWorker` mixin? (#1268) (Wednesday, 31 January)
• [w3c/ServiceWorker] should `ServiceWorker` interface implement `AbstractWorker` mixin? (#1268) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267) (Wednesday, 31 January)
• [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Tuesday, 30 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Tuesday, 30 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Tuesday, 30 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Monday, 29 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Monday, 29 January)
• [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Monday, 29 January)
• [w3c/ServiceWorker] should blob URL clients have their controlled updated if their parent's controller is changed? (#1265) (Thursday, 25 January)
• Re: [w3c/ServiceWorker] should local URLs check origin before inheritting a controller? (#1262) (Tuesday, 23 January)
• Re: [whatwg/fetch] Stop using entry settings object (#367) (Monday, 22 January)
• Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Friday, 19 January)
• Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Friday, 19 January)
• Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Friday, 19 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should local URLs check origin before inheritting a controller? (#1262) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• [w3c/ServiceWorker] should local URLs check origin before inheritting a controller? (#1262) (Thursday, 18 January)
• [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Thursday, 18 January)
• Re: [whatwg/fetch] Define the "Preload Cache" (#590) (Tuesday, 16 January)
• Re: [w3c/ServiceWorker] Clean up Client API to not expose reserved clients (#1259) (Friday, 12 January)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Wednesday, 10 January)
• Re: [whatwg/fetch] Redirect and credential URLs (#660) (Wednesday, 10 January)
• Re: [whatwg/dom] Proposal: Storage Access API (#560) (Wednesday, 10 January)
• Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Tuesday, 9 January)
• Re: [whatwg/fetch] Do not allow CORS responses to "same-origin" requests (#655) (Monday, 8 January)
• Re: [whatwg/fetch] The initiator/destination/CSP table is not exhaustive when it comes t… (#654) (Friday, 5 January)
• Re: [whatwg/fetch] {cache: "no-cache"} vs Cache-Control: immutable (#308) (Friday, 5 January)
• Re: [whatwg/fetch] Provide ability to encode content from browser/runtime in fetch API. (#653) (Friday, 5 January)
• Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Friday, 5 January)
• Re: [whatwg/fetch] what is the Request.destination for modules and es `import()`? (#652) (Friday, 5 January)
• Re: [whatwg/fetch] what is the Request.destination for modules and es `import()`? (#652) (Thursday, 4 January)
• Re: [whatwg/fetch] what is the Request.destination for modules and es `import()`? (#652) (Thursday, 4 January)
• [whatwg/fetch] what is the Request.destination for modules and es `import()`? (#652) (Thursday, 4 January)
• Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Thursday, 4 January)

Ben Lesh

• Re: [whatwg/dom] Improving ergonomics of events with Observable (#544) (Monday, 29 January)

Benjamin C. Wiley Sittler

• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Monday, 22 January)

Benjamin Gruenbaum

• Re: [whatwg/fetch] Safelist Content-Length header (#626) (Saturday, 6 January)

Bevis Tseng

• Re: [w3c/IndexedDB] Integrate with window.onerror (#49) (Wednesday, 24 January)

bigopon

• [whatwg/dom] `cloneNode` should preserve element prototype (#565) (Saturday, 27 January)

Boris Zbarsky

• Re: [heycam/webidl] [Exposed] section unnecessarily restrictive about partial interface + members (#515) (Wednesday, 31 January)
• Re: [heycam/webidl] [Exposed] section unnecessarily restrictive about partial interface + members (#515) (Wednesday, 31 January)
• Re: [heycam/webidl] [Exposed] section unnecessarily restrictive about partial interface + members (#515) (Wednesday, 31 January)
• Re: [whatwg/dom] Improving ergonomics of events with Observable (#544) (Monday, 29 January)
• Re: [heycam/webidl] typeof operator and platform objects (#512) (Thursday, 18 January)
• Re: [heycam/webidl] typeof operator and platform objects (#512) (Thursday, 18 January)
• Re: [heycam/webidl] typeof operator and platform objects (#512) (Thursday, 18 January)
• Re: [heycam/webidl] Unexplained restrictions in operation bindings section (#511) (Thursday, 11 January)
• Re: [heycam/webidl] Prototype of @@unscopable object (#496) (Thursday, 11 January)
• Re: [heycam/webidl] Prototype of @@unscopable object (#496) (Thursday, 11 January)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 10 January)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 10 January)

C. Van Wiemeersch

• Re: [w3ctag/design-reviews] Sensor APIs (#207) (Thursday, 11 January)
• Re: [w3c/manifest] Deep linking - need proper use cases and requirements analysis (#363) (Thursday, 4 January)

CaptGrumpyPants

• [w3c/webcomponents] Named slots and the slot attribute requirement (#726) (Friday, 26 January)

Caridy Patiño

• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Wednesday, 24 January)
• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Wednesday, 17 January)
• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Wednesday, 17 January)
• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Wednesday, 17 January)
• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Wednesday, 17 January)
• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Wednesday, 17 January)

chaals

• Re: [w3c/WebPlatformWG] Add Jan Miksovsky to attendees (#100) (Wednesday, 31 January)
• Re: [w3c/WebPlatformWG] Olli Pettay attending (#99) (Wednesday, 31 January)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Wednesday, 31 January)

Chris Dumez

• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Friday, 12 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Monday, 8 January)

Christopher Joel

• [w3c/webcomponents] aggravate => aggregate (#724) (Thursday, 11 January)

coronadodominique7

• Re: [whatwg/dom] root = true [*] end_of_line = lf insert_final_newline = true charset = utf-8 indent_size = 1 indent_style = space trim_trailing_whitespace = true max_line_length = 100 [Makefile] indent_style = tab [.travis.yml] indent_size = 2 (#541) (Wednesday, 31 January)

cpacejo

• Re: [whatwg/url] "Let ipv4Host be the result of IPv4 parsing asci..." (#367) (Wednesday, 17 January)
• [whatwg/url] "For each code point in input, UTF-8 percent enc..." (#368) (Wednesday, 17 January)
• [whatwg/url] "Let ipv4Host be the result of IPv4 parsing asci..." (#367) (Wednesday, 17 January)

cybai

• Re: [w3c/ServiceWorker] Spec of Service Worker state (#1256) (Tuesday, 2 January)
• [w3c/ServiceWorker] Spec of Service Worker state (#1256) (Monday, 1 January)

cynthia

• Re: [w3ctag/design-reviews] Sensor APIs (#207) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Sensor APIs (#207) (Tuesday, 16 January)
• Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Wednesday, 10 January)

Da Real

• Re: [w3c/IndexedDB] Support full text indexes (#44) (Tuesday, 9 January)

Dan Abramov

• Re: [w3c/ServiceWorker] Soft Update seems way to aggressive (#1250) (Wednesday, 17 January)
• Re: [w3c/ServiceWorker] Soft Update seems way to aggressive (#1250) (Wednesday, 17 January)
• Re: [w3c/ServiceWorker] Soft Update seems way to aggressive (#1250) (Tuesday, 16 January)
• Re: [w3c/ServiceWorker] Soft Update seems way to aggressive (#1250) (Thursday, 11 January)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] WebUSB (#108) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Privacy Mode (#101) (Wednesday, 31 January)
• [w3ctag/design-reviews] Web Components Guidelines Doc? (#227) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] CSS Layout API (#224) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214) (Wednesday, 31 January)
• [w3ctag/design-reviews] Permission Delegation (#225) (Wednesday, 17 January)
• Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Tuesday, 16 January)
• Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Tuesday, 16 January)
• Re: [w3ctag/design-reviews] Web Locks API (#217) (Tuesday, 16 January)
• Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203) (Tuesday, 16 January)

Daniel Huigens

• Re: [w3c/ServiceWorker] should Client.navigate() reject on uncontrolled clients? (#1254) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] Feature request: Provide a way to delay execution of a new service worker (#1208) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should Client.navigate() reject on uncontrolled clients? (#1254) (Thursday, 18 January)

Darren Shen

• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Sunday, 28 January)

Dave Rupert

• Re: [w3c/webcomponents] HTML Modules (#645) (Wednesday, 17 January)

David Benjamin

• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Tuesday, 16 January)

David Bruant

• Re: [w3c/DOM-Parsing] No ProcessingInstruction in document from XML (#35) (Friday, 5 January)
• Re: [w3c/DOM-Parsing] No ProcessingInstruction in document from XML (#35) (Friday, 5 January)
• [w3c/DOM-Parsing] No ProcessingInstruction in document from XML (#35) (Friday, 5 January)
• [w3c/DOM-Parsing] Specify the relationship between the Text Declaration and document.characterSet (#34) (Friday, 5 January)

David Murdoch

• Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Wednesday, 24 January)

David Storey

• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Friday, 12 January)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Wednesday, 10 January)
• Re: [whatwg/dom] Using [Exposed=Window] (#89) (Wednesday, 10 January)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Wednesday, 10 January)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Saturday, 6 January)

Diego Ferreiro Val

• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Monday, 29 January)

Domenic Denicola

• [whatwg/streams] Provide a way for the underlying sink to signal write progress? (#876) (Wednesday, 31 January)
• [whatwg/streams] A variety of clarity and documentation improvements (#875) (Wednesday, 31 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Wednesday, 31 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Wednesday, 31 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] should `ServiceWorker` interface implement `AbstractWorker` mixin? (#1268) (Wednesday, 31 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Wednesday, 31 January)
• [whatwg/streams] "await writer.write(bytes);" in example seems wrong (#874) (Wednesday, 31 January)
• Re: [heycam/webidl] More convenient way to refer to / use "map iterators" (#324) (Wednesday, 31 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Saturday, 27 January)
• Re: [whatwg/streams] Export "readable stream", "writable stream" and "chunk" (#871) (Friday, 26 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 25 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 25 January)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Wednesday, 24 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 24 January)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Tuesday, 23 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Monday, 22 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Monday, 22 January)
• Re: [whatwg/dom] Specify [LegacyWindowAlias=HTMLDocument] on Document (#551) (Monday, 22 January)
• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Monday, 22 January)
• [whatwg/fetch] Response.redirect() results in status message still being OK? (#664) (Friday, 19 January)
• Re: [heycam/webidl] Specify PropertyDescriptor of @@toStringTag symbol (#513) (Friday, 19 January)
• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Saturday, 13 January)
• Re: [whatwg/fetch] Add RequestInit members to Request domintro (#620) (Friday, 12 January)
• Re: [whatwg/xhr] Meta: remove mention of CC0 (#187) (Friday, 12 January)
• Re: [whatwg/fetch] Getting all bytes in a body (#661) (Friday, 12 January)
• [whatwg/fetch] Getting all bytes in a body (#661) (Friday, 12 January)
• Re: [heycam/webidl] [wip] First pass at adding internal slots (#495) (Friday, 12 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Thursday, 11 January)
• Re: [whatwg/streams] Extract length and offset from TypedArray view before transferring its buffer (#868) (Wednesday, 10 January)
• Re: [whatwg/streams] Extract length and offset from TypedArray view before transferring its buffer (#868) (Wednesday, 10 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Wednesday, 10 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Wednesday, 10 January)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Wednesday, 10 January)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Wednesday, 10 January)
• Re: [whatwg/url] Editorial: fix port value in the origin's example (#366) (Tuesday, 9 January)
• Re: [whatwg/streams] Extract length and offset from TypedArray view before transferring its buffer (#868) (Tuesday, 9 January)
• Re: [whatwg/streams] Extract length and offset from TypedArray view before transferring its buffer (#868) (Tuesday, 9 January)
• Re: [whatwg/streams] Extract length and offset from TypedArray view before transferring its buffer (#868) (Monday, 8 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Monday, 8 January)
• Re: [whatwg/dom] Proposal: Spellcheck API (#547) (Sunday, 7 January)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Saturday, 6 January)
• Re: [whatwg/url] Meta: adopt more whatwg/meta guidelines (#365) (Saturday, 6 January)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Saturday, 6 January)
• Re: [whatwg/fetch] Provide ability to encode content from browser/runtime in fetch API. (#653) (Friday, 5 January)
• Re: [whatwg/xhr] Meta: use new WHATWG boilerplate and license (#184) (Friday, 5 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Friday, 5 January)
• Re: [whatwg/streams] Meta: use new WHATWG boilerplate and license (#866) (Friday, 5 January)
• Re: [whatwg/storage] Meta: use new WHATWG boilerplate and license (#56) (Friday, 5 January)
• Re: [whatwg/fullscreen] Meta: use new WHATWG boilerplate and license (#113) (Friday, 5 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Friday, 5 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Friday, 5 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Friday, 5 January)
• Re: [whatwg/fetch] Meta: use new WHATWG boilerplate and license (#651) (Friday, 5 January)
• Re: [whatwg/dom] Meta: use new WHATWG boilerplate and license (#553) (Friday, 5 January)
• Re: [whatwg/fullscreen] Meta: use new WHATWG boilerplate and license (#113) (Friday, 5 January)
• Re: [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Friday, 5 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Friday, 5 January)
• Re: [w3c/manifest] Add payment handler installation URL. (#634) (Thursday, 4 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Thursday, 4 January)
• Re: [whatwg/dom] Use Infra's concatenation definition (#556) (Thursday, 4 January)
• Re: [heycam/webidl] Add informative section on legacy constructs (#506) (Thursday, 4 January)
• [whatwg/xhr] Meta: use new WHATWG boilerplate and license (#184) (Thursday, 4 January)
• [whatwg/streams] Meta: use new WHATWG boilerplate and license (#866) (Thursday, 4 January)
• [whatwg/storage] Meta: use new WHATWG boilerplate and license (#56) (Thursday, 4 January)
• Re: [whatwg/dom] Meta: use new WHATWG boilerplate and license (#553) (Thursday, 4 January)
• Re: [whatwg/fetch] what is the Request.destination for modules and es `import()`? (#652) (Thursday, 4 January)
• Re: [whatwg/fetch] Meta: use new WHATWG boilerplate and license (#651) (Thursday, 4 January)
• Re: [whatwg/fetch] Editorial: address Bikeshed and minor wording issues (#640) (Thursday, 4 January)
• Re: [whatwg/fetch] linking errors upon building fetch? (#639) (Thursday, 4 January)
• Re: [whatwg/fetch] Editorial: address Bikeshed and minor wording issues (#640) (Thursday, 4 January)
• Re: [whatwg/dom] Meta: use new WHATWG boilerplate and license (#553) (Thursday, 4 January)
• Re: [heycam/webidl] Add informative section on legacy constructs (#506) (Thursday, 4 January)
• [whatwg/fullscreen] Meta: use new WHATWG boilerplate and license (#113) (Wednesday, 3 January)
• [whatwg/fetch] Meta: use new WHATWG boilerplate and license (#651) (Wednesday, 3 January)
• [whatwg/encoding] Meta: use new WHATWG boilerplate and license (#132) (Wednesday, 3 January)
• [whatwg/dom] Meta: use new WHATWG boilerplate and license (#553) (Wednesday, 3 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Wednesday, 3 January)
• Re: [heycam/webidl] Include typedefs in the JSON type definition (#505) (Tuesday, 2 January)
• Re: [heycam/webidl] Include typedefs in the JSON type definition (#505) (Tuesday, 2 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Tuesday, 2 January)
• [heycam/webidl] Is DOMHighResTimeStamp a "JSON type"? (#504) (Tuesday, 2 January)
• Re: [whatwg/fetch] Add RequestInit members to Request domintro (#620) (Tuesday, 2 January)

Dominic Farolino

• Re: [whatwg/fetch] Add RequestInit members to Request domintro (#620) (Thursday, 11 January)
• Re: [whatwg/fetch] Add RequestInit members to Request domintro (#620) (Thursday, 11 January)

Dominick Ng

• Re: [w3c/manifest] how to change app name text color on the splash screen? (#642) (Tuesday, 30 January)
• Re: [w3c/manifest] Explicitly block opaque origins from requesting manifests (#638) (Thursday, 18 January)
• Re: [w3c/manifest] Explicitly block opaque origins from requesting manifests (#638) (Thursday, 18 January)
• Re: [w3c/manifest] Explicitly block opaque origins from requesting manifests (#638) (Thursday, 18 January)
• Re: [w3c/manifest] Explicitly block opaque origins from requesting manifests (#638) (Wednesday, 17 January)
• [w3c/manifest] Explicitly block opaque origins from requesting manifests (#638) (Wednesday, 17 January)

Dominique Hazael-Massieux

• [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641) (Tuesday, 23 January)

drwez

• Re: [w3c/uievents] Add specification for AltGraph key & modifier behaviour (#147) (Wednesday, 31 January)
• Re: [w3c/uievents] Add specification for AltGraph key & modifier behaviour (#147) (Tuesday, 30 January)

Eduard Reñé Claramunt

• Re: [w3c/WebPlatformWG] [Feature Request] pause/resume webdriver (#98) (Thursday, 18 January)
• Re: [w3c/WebPlatformWG] [Feature Request] pause/resume webdriver (#98) (Thursday, 18 January)
• [w3c/WebPlatformWG] [Feature Request] pause/resume webdriver (#98) (Thursday, 18 January)

effulgentsia

• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Wednesday, 17 January)

Eli Grey

• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Tuesday, 16 January)

ewsizeit

• Re: [w3c/manifest] Richer splash screen backgrounds (#589) (Wednesday, 31 January)
• Re: [w3c/manifest] Support a way to update explicitly (#446) (Tuesday, 30 January)

fantasai

• Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Wednesday, 31 January)

faquino

• [w3c/FileAPI] Consider adding the hashed filesystem path (#95) (Monday, 22 January)

Florian Bösch

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

fmeawad

• [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Thursday, 18 January)

Focus3D

• Re: [w3c/manifest] how to change app name text color on the splash screen? (#642) (Friday, 26 January)
• [w3c/manifest] how to change app name text color on the splash screen? (#642) (Friday, 26 January)

François Beaufort

• Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226) (Wednesday, 31 January)
• [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226) (Monday, 29 January)

frlinw

• Re: [w3c/manifest] Support a way to update explicitly (#446) (Tuesday, 30 January)

Fuqiao Xue

• Re: [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Tuesday, 30 January)
• Re: [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Tuesday, 30 January)
• Re: [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Friday, 19 January)
• Re: [w3c/IndexedDB] Fix the link to the first edition (#228) (Thursday, 18 January)
• Re: [w3c/IndexedDB] Fix the link to the first edition (#228) (Thursday, 18 January)
• Re: [w3c/IndexedDB] Fix the link to the first edition (#228) (Wednesday, 17 January)
• Re: [w3c/IndexedDB] Web IDL syntax error? (#226) (Wednesday, 17 January)
• [w3c/IndexedDB] Fix the link to the first edition (#228) (Wednesday, 17 January)
• [w3c/uievents] Fix references to Web IDL (#176) (Monday, 15 January)
• [w3c/IndexedDB] Web IDL syntax error? (#226) (Monday, 15 January)

Garrett Smith

• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Wednesday, 31 January)

Gary Kacmarcik

• Re: [w3c/clipboard-apis] Nitpick terminology around events in explainer (#65) (Thursday, 25 January)
• Re: [w3c/uievents] Have MouseEventInit inherit from EventInit (#177) (Thursday, 25 January)
• Re: [w3c/uievents] Have MouseEventInit inherit from EventInit (#177) (Thursday, 25 January)
• [w3c/uievents] Have MouseEventInit inherit from EventInit (#177) (Thursday, 25 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 23 January)
• Re: [w3c/clipboard-apis] Request TAG review for initial (text only) API (#59) (Friday, 5 January)
• Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Friday, 5 January)
• [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222) (Friday, 5 January)
• [w3c/clipboard-apis] Request a TAG review for image/delayed-content-generation API (#60) (Friday, 5 January)
• [w3c/clipboard-apis] TAG review for initial (text only) API (#59) (Friday, 5 January)

gked

• Re: [w3c/editing] insertParagraph definition is different from current browsers' behavior when selection is collapsed at end of inline element(s) (#172) (Friday, 19 January)

guest271314

• Re: [whatwg/fetch] Should fetches to blob URLs be more restricted? (#666) (Wednesday, 31 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Friday, 26 January)

Hayato Ito

• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 30 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 23 January)
• Re: [whatwg/dom] Do not dispatch an UA event when target and relatedTarget are identical. (#337) (Wednesday, 17 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Monday, 15 January)
• Re: [w3c/webcomponents] [SHADOW] Sequential Focus Navigation uses undefined "For each node tree TREE in DOCUMENT" (#720) (Friday, 12 January)
• Re: [w3c/touch-events] 'Retargeting steps' expose closed Shadow DOM to the outside world (#92) (Friday, 12 January)
• Re: [w3c/touch-events] 'Retargeting steps' expose closed Shadow DOM to the outside world (#92) (Thursday, 11 January)

Heaven

• Re: [w3ctag/design-reviews] Request to review First Paint Timing (#177) (Thursday, 11 January)

henbos

• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Thursday, 11 January)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 10 January)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 10 January)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 10 January)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 10 January)
• Re: [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 10 January)
• [heycam/webidl] record with arbitrary value types as keys? (#509) (Wednesday, 10 January)

Henri Sivonen

• Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Thursday, 25 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Thursday, 25 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Tuesday, 23 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Monday, 22 January)

Henry Ing-Simmons

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

Ian Clelland

• Re: [whatwg/xhr] Integrate feature policy (#177) (Wednesday, 31 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Tuesday, 30 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Friday, 26 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Friday, 26 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Friday, 26 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Friday, 26 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Friday, 26 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Friday, 26 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Wednesday, 24 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Wednesday, 24 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Tuesday, 16 January)
• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Thursday, 11 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Thursday, 11 January)

Ian Kilpatrick

• [w3ctag/design-reviews] CSS Layout API (#224) (Thursday, 11 January)

Ifeora Okechukwu

• Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Friday, 19 January)

Ilya Grigorik

• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Monday, 29 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Thursday, 25 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Tuesday, 23 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Tuesday, 16 January)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Tuesday, 16 January)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Tuesday, 16 January)
• Re: [whatwg/fetch] Define the "Preload Cache" (#590) (Monday, 15 January)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Monday, 15 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 15 January)

Inian

• Re: [w3c/ServiceWorker] Turn off a service worker in parts of the website (#1257) (Thursday, 11 January)

Isiah Meadows

• Re: [whatwg/dom] Support live fragments (#554) (Thursday, 4 January)
• [whatwg/dom] Add a live DocumentFragment (#554) (Thursday, 4 January)

J. S. Choi

• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Saturday, 13 January)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Tuesday, 9 January)
• Re: [whatwg/dom] Proposal: Spellcheck API (#547) (Monday, 8 January)

Jake Archibald

• Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Friday, 19 January)
• Re: [w3c/ServiceWorker] should Client.navigate() reject on uncontrolled clients? (#1254) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] Soft Update seems way to aggressive (#1250) (Wednesday, 17 January)
• Re: [w3c/ServiceWorker] Clean up Client API to not expose reserved clients (#1259) (Friday, 12 January)
• Re: [w3c/ServiceWorker] Clean up Client API to not expose reserved clients (#1259) (Friday, 12 January)
• Re: [w3c/ServiceWorker] Turn off a service worker in parts of the website (#1257) (Friday, 12 January)
• Re: [w3c/ServiceWorker] Why is it possible to register a service worker that you won't ever be able to remove? (#1258) (Wednesday, 10 January)
• Re: [w3c/ServiceWorker] Why is it possible to register a service worker that you won't ever be able to remove? (#1258) (Wednesday, 10 January)
• Re: [w3c/ServiceWorker] Turn off a service worker in parts of the website (#1257) (Tuesday, 9 January)
• Re: [w3c/ServiceWorker] Turn off a service worker in parts of the website (#1257) (Tuesday, 9 January)
• Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Monday, 8 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Thursday, 4 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Thursday, 4 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Thursday, 4 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Thursday, 4 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Wednesday, 3 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Wednesday, 3 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Tuesday, 2 January)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Tuesday, 2 January)

Jan Miksovsky

• [w3c/WebPlatformWG] Add Jan Miksovsky to attendees (#100) (Wednesday, 31 January)

Jean-Philippe Paradis

• Re: [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Tuesday, 16 January)
• [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Monday, 15 January)

Jeffrey Posnick

• Re: [w3c/ServiceWorker] Soft Update seems way to aggressive (#1250) (Thursday, 11 January)

Jeffrey Yasskin

• Re: [w3c/permissions] The boolean permission query algorithm isn't Boolean (#167) (Monday, 15 January)

Joe Pea

• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Sunday, 28 January)
• Re: [w3c/webcomponents] How to wait for will-be custom elements to be upgraded? (#558) (Sunday, 28 January)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Sunday, 28 January)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Saturday, 27 January)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Thursday, 18 January)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Tuesday, 16 January)

John Wilander

• Re: [whatwg/dom] Proposal: Storage Access API (#560) (Wednesday, 10 January)
• Re: [whatwg/dom] Proposal: Storage Access API (#560) (Wednesday, 10 January)
• Re: [whatwg/dom] Proposal: Storage Access API (#560) (Wednesday, 10 January)
• Re: [whatwg/dom] Proposal: Storage Access API (#560) (Wednesday, 10 January)
• [whatwg/dom] Proposal: Storage Access API (#560) (Tuesday, 9 January)

Josh Matthews

• Re: [w3c/FileAPI] Remove readyState checks from FileReaderSync methods. (588597b) (Tuesday, 30 January)
• Re: [w3c/FileAPI] Remove readyState checks from FileReaderSync methods. (588597b) (Tuesday, 30 January)
• Re: [w3c/FileAPI] Remove readyState checks from FileReaderSync methods. (588597b) (Tuesday, 30 January)
• [w3c/FileAPI] readyState checks for FileReaderSync methods don't make sense (#96) (Monday, 29 January)

Joshua Bell

• Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Wednesday, 31 January)
• Re: [w3c/IndexedDB] Horizontal review… (#112) (Tuesday, 30 January)
• Re: [w3c/IndexedDB] Horizontal review… (#112) (Tuesday, 30 January)
• Re: [w3c/IndexedDB] Integrate with window.onerror (#49) (Tuesday, 23 January)
• Re: [w3c/IndexedDB] Integrate with window.onerror (#49) (Tuesday, 23 January)
• Re: [whatwg/xhr] Make FormData a cloneable object (#55) (Tuesday, 23 January)
• Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Friday, 19 January)
• Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Friday, 19 January)
• Re: [w3ctag/design-reviews] Web Locks API (#217) (Friday, 19 January)
• Re: [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Friday, 19 January)
• [w3c/clipboard-apis] Initialization of clipboardData by ClipboardEvent constructor (#64) (Friday, 19 January)
• Re: [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Thursday, 18 January)
• Re: [w3c/IndexedDB] Web IDL syntax error? (#226) (Thursday, 18 January)
• Re: [w3c/IndexedDB] Web IDL syntax error? (#226) (Thursday, 18 January)
• Re: [w3c/IndexedDB] Web IDL syntax error? (#226) (Thursday, 18 January)
• Re: [w3c/IndexedDB] Web IDL syntax error? (#226) (Thursday, 18 January)
• Re: [w3c/IndexedDB] Web IDL syntax error? (#226) (Thursday, 18 January)
• Re: [w3c/IndexedDB] Web IDL syntax error? (#226) (Thursday, 18 January)
• Re: [w3c/IndexedDB] Fix the link to the first edition (#228) (Wednesday, 17 January)
• Re: [w3c/IndexedDB] Fix the link to the first edition (#228) (Wednesday, 17 January)
• Re: [w3ctag/design-reviews] Web Locks API (#217) (Tuesday, 16 January)
• Re: [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Tuesday, 16 January)
• Re: [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Monday, 15 January)
• Re: [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Monday, 15 January)
• Re: [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Monday, 15 January)
• Re: [w3c/IndexedDB] Trying to access version 1 of the IndexedDB spec at W3C site, but version 2 is shown. (#227) (Monday, 15 January)
• Re: [whatwg/storage] Correct branching in estimate() (#58) (Saturday, 6 January)
• [whatwg/storage] estimate() steps need "Otherwise" (#57) (Friday, 5 January)

Jovan Gerodetti

• Re: [w3c/webcomponents] Interfaces for web components (#725) (Thursday, 25 January)
• [w3c/webcomponents] Interfaces for web components (#725) (Thursday, 25 January)

jugglinmike

• [w3c/permissions] Automation: simplify URI template (#168) (Monday, 15 January)

Julian Descottes

• Re: [whatwg/dom] "A slotable has an associated name" should read slot instead of name (#563) (Tuesday, 23 January)
• Re: [whatwg/dom] "A slotable has an associated name" should read slot instead of name (#563) (Tuesday, 23 January)
• [whatwg/dom] "A slotable has an associated name" should read slot instead of name (#563) (Monday, 22 January)

Jun

• Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Wednesday, 17 January)

Jungkee Song

• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167) (Tuesday, 30 January)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Monday, 22 January)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Wednesday, 17 January)
• Re: [w3c/ServiceWorker] Use Web IDL's new-ish interface mixins concept (#1252) (Saturday, 13 January)
• Re: [w3c/ServiceWorker] Use Web IDL's new-ish interface mixins concept (#1252) (Saturday, 13 January)
• Re: [w3c/ServiceWorker] Clean up Client API to not expose reserved clients (#1259) (Saturday, 13 January)
• Re: [w3c/ServiceWorker] clarify Clients.matchAll() focus order for nested frames (#1080) (Saturday, 13 January)
• Re: [w3c/ServiceWorker] Clean up Client API to not expose reserved clients (#1259) (Saturday, 13 January)
• Re: [w3c/ServiceWorker] clarify Clients.matchAll() focus order for nested frames (#1080) (Friday, 12 January)
• Re: [w3c/ServiceWorker] Clean up Client API to not expose reserved clients (#1259) (Friday, 12 January)
• [w3c/ServiceWorker] Clean up Client API to not expose reserved clients (#1259) (Friday, 12 January)
• Re: [w3c/ServiceWorker] Spec of Service Worker state (#1256) (Tuesday, 2 January)
• Re: [w3c/ServiceWorker] Spec of Service Worker state (#1256) (Tuesday, 2 January)

Junle Li

• Re: [whatwg/fetch] Constructing a Response with Content-Encoding? (#589) (Thursday, 4 January)
• [whatwg/fetch] Provide ability to encode content from browser/runtime in fetch API. (#653) (Thursday, 4 January)

Justin Fagnani

• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)

Kelvin Yong

• Re: [w3c/gamepad] Light Indicator (#67) (Monday, 22 January)
• Re: [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27) (Monday, 22 January)
• [w3c/gamepad] Light Indicator (#67) (Monday, 15 January)
• Re: [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27) (Sunday, 14 January)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646) (Tuesday, 30 January)
• Re: [w3c/manifest] "Navigation scope" and "within scope" are poorly defined/used (#643) (Tuesday, 30 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Tuesday, 30 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Tuesday, 30 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Monday, 29 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Monday, 29 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Monday, 29 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Monday, 29 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Monday, 29 January)
• Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641) (Tuesday, 23 January)
• Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641) (Tuesday, 23 January)
• Re: [w3c/manifest] Share from Gallery or Browser (#639) (Friday, 19 January)
• Re: [w3c/manifest] Explicitly block opaque origins from requesting manifests (#638) (Wednesday, 17 January)
• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Tuesday, 16 January)
• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Tuesday, 16 January)
• Re: [w3c/manifest] Update manifest example to be consistent (#635) (Tuesday, 9 January)
• Re: [w3c/manifest] Add payment handler installation URL. (#634) (Thursday, 4 January)

Kevin Schaaf

• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)

KOLANICH

• Re: [w3c/permissions] A new permission for canvas data (#165) (Friday, 5 January)
• Re: [w3c/permissions] A new permission for canvas data (#165) (Friday, 5 January)

L. David Baron

• Re: [w3ctag/design-reviews] HTML General Review (#174) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Tuesday, 30 January)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Sunday, 28 January)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Friday, 26 January)
• Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Tuesday, 23 January)
• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Tuesday, 16 January)
• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Tuesday, 16 January)
• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Tuesday, 16 January)

Lukasz Olejnik

• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Wednesday, 31 January)

Léonie Watson

• Re: [w3c/push-api] Wide review tracker (#265) (Tuesday, 30 January)
• Re: [w3c/IndexedDB] Add a note regarding addition of _ to includes keyword (#229) (Tuesday, 23 January)
• Re: [w3c/IndexedDB] Add a note regarding addition of _ to includes keyword (#229) (Tuesday, 23 January)
• [w3c/IndexedDB] Add a note regarding addition of _ to includes keyword (#229) (Monday, 22 January)
• Re: [w3c/WebPlatformWG] [Feature Request] pause/resume webdriver (#98) (Thursday, 18 January)
• Re: [w3c/screen-orientation] Wide review tracker (#102) (Tuesday, 9 January)
• Re: [w3c/push-api] Wide review tracker (#265) (Tuesday, 9 January)

Marco Colli

• [w3c/push-api] Make it clear that a push message does not require a payload (#289) (Friday, 19 January)

Marcos Cáceres

• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] testing pr preview - don't merge (#648) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• [w3c/manifest] testing pr preview - don't merge (#648) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Tuesday, 30 January)
• Re: [w3c/manifest] Fix up start_url and scope processing algorithm. (#645) (Tuesday, 30 January)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 23 January)
• [w3c/manifest] Clarify service worker member, and when it installs (#640) (Tuesday, 23 January)
• Re: [w3c/manifest] Share from Gallery or Browser (#639) (Monday, 22 January)
• Re: [w3c/manifest] Share from Gallery or Browser (#639) (Monday, 22 January)
• Re: [w3c/manifest] Explicitly block opaque origins from requesting manifests (#638) (Thursday, 18 January)
• Re: [w3c/manifest] Explicitly block opaque origins from requesting manifests (#638) (Thursday, 18 January)
• Re: [w3c/manifest] Explicitly block opaque origins from requesting manifests (#638) (Thursday, 18 January)
• Re: [w3c/manifest] Explicitly block opaque origins from requesting manifests (#638) (Thursday, 18 January)
• Re: [w3c/manifest] Explicitly block opaque origins from requesting manifests (#638) (Thursday, 18 January)
• Re: [w3c/manifest] Update manifest example to be consistent (#635) (Wednesday, 17 January)
• Re: [w3c/manifest] Update manifest example to be consistent (#635) (Wednesday, 17 January)
• Re: [w3c/screen-orientation] Wide review tracker (#102) (Tuesday, 16 January)
• Re: [w3c/manifest] Use case for appuninstall event (#636) (Tuesday, 16 January)
• Re: [w3c/manifest] Use case for appuninstall event (#636) (Tuesday, 16 January)
• Re: [w3c/manifest] Deep linking - need proper use cases and requirements analysis (#363) (Thursday, 11 January)
• Re: [w3c/manifest] Update manifest example to be consistent (#635) (Tuesday, 9 January)
• Re: [w3c/manifest] Add payment handler installation URL. (#634) (Tuesday, 9 January)

Marijn Kruisselbrink

• Re: [whatwg/fetch] Should fetches to blob URLs be more restricted? (#666) (Wednesday, 31 January)
• Re: [whatwg/fetch] Should fetches to blob URLs be more restricted? (#666) (Wednesday, 31 January)
• Re: [whatwg/fetch] Should fetches to blob URLs be more restricted? (#666) (Wednesday, 31 January)
• [whatwg/fetch] Should fetches to blob URLs be more restricted? (#666) (Wednesday, 31 January)
• Re: [w3c/FileAPI] Remove readyState checks from FileReaderSync methods. (588597b) (Tuesday, 30 January)
• Re: [w3c/FileAPI] readyState checks for FileReaderSync methods don't make sense (#96) (Tuesday, 30 January)
• Re: [w3c/FileAPI] readyState checks for FileReaderSync methods don't make sense (#96) (Tuesday, 30 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/ServiceWorker] should blob URLs inherit controller from parent environment or environment that called `createObjectURL()`? (#1261) (Thursday, 18 January)
• Re: [w3c/FileAPI] Refactor Blob URL Store definition. (#92) (Tuesday, 9 January)
• Re: [w3c/FileAPI] Clarify Lifetime of BlobStore (#89) (Tuesday, 9 January)
• Re: [w3c/FileAPI] Refactor Blob URL Store definition. (#92) (Tuesday, 9 January)

Mark Nottingham

• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Thursday, 11 January)

Martin Thomson

• Re: [w3c/push-api] Wide review tracker (#265) (Wednesday, 31 January)
• Re: [w3c/permissions] The boolean permission query algorithm isn't Boolean (#167) (Monday, 15 January)
• [w3c/permissions] The boolean permission query algorithm isn't Boolean (#167) (Monday, 15 January)
• Re: [whatwg/fetch] Provide ability to encode content from browser/runtime in fetch API. (#653) (Sunday, 7 January)
• Re: [w3ctag/design-reviews] Sensor APIs (#207) (Thursday, 4 January)

Masayuki Nakano

• Re: [w3c/uievents] Add specification for AltGraph key & modifier behaviour (#147) (Wednesday, 31 January)
• Re: [w3c/editing] insertParagraph definition is different from current browsers' behavior when selection is collapsed at end of inline element(s) (#172) (Tuesday, 23 January)
• [w3c/editing] insertParagraph definition is different from current browsers' behavior when selection is collapsed at end of inline element(s) (#172) (Friday, 19 January)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Tuesday, 30 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Tuesday, 30 January)
• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Tuesday, 30 January)
• Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Tuesday, 23 January)
• Re: [w3c/ServiceWorker] Clean up Client API to not expose reserved clients (#1259) (Monday, 15 January)
• Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Tuesday, 9 January)

Matt Giuca

• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647) (Wednesday, 31 January)
• Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646) (Tuesday, 30 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Tuesday, 30 January)
• Re: [w3c/manifest] Fix up start_url and scope processing algorithm. (#645) (Tuesday, 30 January)
• [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646) (Tuesday, 30 January)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Tuesday, 30 January)
• Re: [w3c/manifest] Fix up start_url and scope processing algorithm. (#645) (Tuesday, 30 January)
• [w3c/manifest] Fix up start_url and scope processing algorithm. (#645) (Tuesday, 30 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Tuesday, 30 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Tuesday, 30 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Tuesday, 30 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Tuesday, 30 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Tuesday, 30 January)
• Re: [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Tuesday, 30 January)
• [w3c/manifest] "Navigation scope" and "within scope" are poorly defined/used (#643) (Monday, 29 January)
• [w3c/manifest] Properly define "navigation scope" and "within scope". (#644) (Monday, 29 January)
• Re: [w3c/manifest] Make unbounded navigation scope less broad (#550) (Monday, 29 January)
• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Wednesday, 24 January)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Tuesday, 23 January)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Tuesday, 23 January)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Tuesday, 23 January)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Monday, 22 January)
• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Monday, 22 January)
• [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Friday, 19 January)
• Re: [w3c/manifest] Use case for appuninstall event (#636) (Tuesday, 16 January)
• Re: [w3c/manifest] Use case for appuninstall event (#636) (Tuesday, 16 January)

Michael[tm] Smith

• Re: [w3c/webcomponents] Copy edits for all remaining parts (#687) (Friday, 12 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Sunday, 7 January)

Michał Wadas

• Re: [whatwg/dom] Proposal: Spellcheck API (#547) (Sunday, 7 January)

Mike West

• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Wednesday, 17 January)
• Re: [whatwg/fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 11 January)
• Re: [whatwg/fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 11 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)

Moritz

• Re: [whatwg/fetch] Define how to handle bad content encoding (#657) (Monday, 8 January)
• [whatwg/fetch] Define how to handele bad content encoding (#657) (Sunday, 7 January)

Mounir Lamouri

• Re: [w3c/screen-orientation] Where are terms 'primary' and 'secondary' defined within spec? (#113) (Wednesday, 31 January)
• Re: [w3c/manifest] how to change app name text color on the splash screen? (#642) (Friday, 26 January)
• Re: [w3c/manifest] how to change app name text color on the splash screen? (#642) (Friday, 26 January)

Ms2ger

• [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564) (Tuesday, 23 January)

nainar

• [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Monday, 8 January)

Navid Zolghadr

• Re: [w3c/pointerlock] Update the editor (#30) (Friday, 19 January)
• [w3c/pointerlock] Update the editor (#30) (Friday, 19 January)

Nick Doty

• Re: [w3c/permissions] Discuss how query() makes abuse harder to detect. (#166) (Monday, 15 January)

Nick Dugger

• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Thursday, 18 January)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Monday, 8 January)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Saturday, 6 January)
• [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Saturday, 6 January)

Nigel Megitt

• Re: [w3ctag/design-reviews] HTML General Review (#174) (Wednesday, 31 January)

nondebug

• Re: [w3c/gamepad] Light Indicator (#67) (Thursday, 18 January)
• Re: [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27) (Thursday, 18 January)

nunoperalta

• [w3c/manifest] Share from Gallery or Browser (#639) (Friday, 19 January)

Owen Campbell-Moore

• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Thursday, 11 January)

Pat Mächler

• Re: [w3c/manifest] Use case for appuninstall event (#636) (Tuesday, 9 January)

Peter Linss

• Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Tuesday, 23 January)

Philip Jägenstedt

• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 31 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 31 January)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 31 January)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 31 January)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 31 January)
• Re: [heycam/webidl] Definition of "is an array index" makes "-0" an array index (#516) (Wednesday, 31 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 31 January)
• Re: [heycam/webidl] Definition of "is an array index" makes "-0" an array index (#516) (Wednesday, 31 January)
• [heycam/webidl] Definition of "is an array index" makes "-0" an array index (#516) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Tuesday, 30 January)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Tuesday, 30 January)
• Re: [whatwg/fullscreen] Meta: make Philip the editor (#121) (Tuesday, 30 January)
• [whatwg/fullscreen] Meta: make Philip the editor (#121) (Tuesday, 30 January)
• Re: [whatwg/fullscreen] Investigate whether nested fullscreen element is necessary (#119) (Tuesday, 30 January)
• Re: [whatwg/fullscreen] Demo for issue #119 (#120) (Tuesday, 30 January)
• Re: [whatwg/fullscreen] Demo for issue #119 (#120) (Tuesday, 30 January)
• [whatwg/fullscreen] Demo for issue #119 (#120) (Tuesday, 30 January)
• Re: [whatwg/fullscreen] Investigate whether nested fullscreen element is necessary (#119) (Monday, 29 January)
• Re: [whatwg/fullscreen] Investigate whether nested fullscreen element is necessary (#119) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/fullscreen] Investigate whether nested fullscreen element is necessary (#119) (Monday, 29 January)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Monday, 29 January)
• Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102) (Monday, 29 January)
• [whatwg/fullscreen] Editorial: fix grammar in notes about run the fullscreen steps (#118) (Monday, 29 January)
• [whatwg/fullscreen] Editorial: remove a stray/double "tree order" in note (#117) (Monday, 29 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Monday, 29 January)
• Re: [whatwg/dom] Specify [LegacyWindowAlias=HTMLDocument] on Document (#551) (Friday, 26 January)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Friday, 26 January)
• Re: [whatwg/fullscreen] Unable to zoom and scroll in mobile browsers when in full screen. (#110) (Thursday, 25 January)
• Re: [w3c/clipboard-apis] Nitpick terminology around events in explainer (#65) (Thursday, 25 January)
• [w3c/clipboard-apis] Nitpick terminology around events in explainer (#65) (Thursday, 25 January)
• Re: [whatwg/fullscreen] Ending fullscreen for popups (#116) (Wednesday, 24 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 24 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 24 January)
• Re: [whatwg/fetch] data: URL generator (#665) (Wednesday, 24 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Friday, 19 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Friday, 19 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Friday, 19 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 18 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 17 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 17 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 17 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 17 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Tuesday, 16 January)
• Re: [whatwg/xhr] Integrate feature policy (#177) (Tuesday, 16 January)
• [w3c/clipboard-apis] "check clipboard read permission" needs to be an async operation? (#63) (Tuesday, 16 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 10 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Monday, 8 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Monday, 8 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Friday, 5 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Friday, 5 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 4 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 4 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 4 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 4 January)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 4 January)
• Re: [whatwg/fullscreen] Consider forbidding <frame> element from entering fullscreen (#112) (Wednesday, 3 January)
• Re: [whatwg/fullscreen] Consider forbidding <frame> element from entering fullscreen (#112) (Wednesday, 3 January)

raymeskhoury

• Re: [w3ctag/design-reviews] Permission Delegation (#225) (Wednesday, 31 January)

Rick Byers

• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Wednesday, 17 January)
• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Tuesday, 16 January)
• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Friday, 12 January)
• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Wednesday, 10 January)

Rimas Misevičius

• Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) (Friday, 19 January)
• [whatwg/url] Editorial: fix port value in the origin's example (#366) (Tuesday, 9 January)

rmacklin

• Re: [w3c/manifest] Use case for appuninstall event (#636) (Tuesday, 9 January)
• Re: [w3c/manifest] Update manifest example to be consistent (#635) (Tuesday, 9 January)
• [w3c/manifest] Use case for appuninstall event (#636) (Tuesday, 9 January)
• [w3c/manifest] Update manifest example to be consistent (#635) (Tuesday, 9 January)

Rob Dodson

• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Thursday, 18 January)
• Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8) (Thursday, 18 January)

Rouslan Solomakhin

• Re: [w3c/manifest] Add payment handler installation URL. (#634) (Tuesday, 9 January)
• Re: [w3c/manifest] Add payment handler installation URL. (#634) (Tuesday, 9 January)
• Re: [w3c/manifest] Add payment handler installation URL. (#634) (Monday, 8 January)
• [w3c/manifest] Add payment handler installation URL. (#634) (Wednesday, 3 January)
• Re: [w3c/manifest] Add payment handler installation URL. (#634) (Wednesday, 3 January)

RuudZw

• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Friday, 19 January)
• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Friday, 19 January)
• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Saturday, 13 January)
• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Friday, 12 January)
• Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178) (Thursday, 11 January)

Ryosuke Niwa

• Re: [w3c/WebPlatformWG] Add Jan Miksovsky to attendees (#100) (Wednesday, 31 January)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Wednesday, 31 January)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Thursday, 25 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Wednesday, 17 January)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Tuesday, 9 January)
• Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723) (Monday, 8 January)

Samuel Horwitz

• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)

Sebastian Kippe

• Re: [w3c/manifest] Use case for appuninstall event (#636) (Tuesday, 9 January)

SelenIT

• Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Friday, 19 January)
• Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Wednesday, 17 January)

Shachar Zohar

• [w3c/ServiceWorker] windowClients state change events - loaded/unloaded (#1269) (Wednesday, 31 January)

Sindre Sorhus

• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Saturday, 13 January)

sleevi

• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Thursday, 25 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Wednesday, 24 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Wednesday, 24 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Tuesday, 23 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Tuesday, 23 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Tuesday, 16 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 15 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 15 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 15 January)
• Re: [whatwg/fetch] Provide ability to encode content from browser/runtime in fetch API. (#653) (Friday, 5 January)

smaug----

• [w3c/WebPlatformWG] Olli Pettay attending (#99) (Wednesday, 31 January)
• [whatwg/dom] Should "If target's root is a shadow root, then set event’s target attribute and event’s relatedTarget to null. " be based on target's root before dispatch (#562) (Monday, 15 January)
• [whatwg/dom] 'Retargeting steps' run at wrong time (#561) (Thursday, 11 January)
• Re: [w3c/touch-events] 'Retargeting steps' expose closed Shadow DOM to the outside world (#92) (Thursday, 11 January)
• Re: [w3c/touch-events] 'Retargeting steps' expose closed Shadow DOM to the outside world (#92) (Wednesday, 10 January)
• [w3c/touch-events] 'Retargeting steps' expose closed Shadow DOM to the outside world (#92) (Wednesday, 10 January)
• [w3c/webcomponents] [SHADOW] Sequential Focus Navigation step tree has 'for each' for a single scope (#721) (Wednesday, 3 January)
• [w3c/webcomponents] [SHADOW] Sequential Focus Navigation uses undefined "For each node tree TREE in DOCUMENT" (#720) (Wednesday, 3 January)

snuggs

• Re: [w3c/webcomponents] HTML Modules (#645) (Saturday, 20 January)
• Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69) (Thursday, 11 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Wednesday, 10 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Wednesday, 10 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Wednesday, 10 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Wednesday, 10 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Wednesday, 10 January)
• Re: [whatwg/url] Meta: adopt more whatwg/meta guidelines (#365) (Wednesday, 10 January)
• Re: [whatwg/dom] Meta: define merge policy and add CONTRIBUTING.md (#559) (Monday, 8 January)
• Re: [whatwg/dom] Meta: define merge policy and add CONTRIBUTING.md (#559) (Monday, 8 January)
• Re: [whatwg/dom] Meta: define merge policy and add CONTRIBUTING.md (#559) (Monday, 8 January)
• Re: [whatwg/fullscreen] Meta: align with whatwg/meta resources (#115) (Sunday, 7 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Sunday, 7 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Sunday, 7 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Sunday, 7 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Sunday, 7 January)
• Re: [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Sunday, 7 January)
• Re: [whatwg/fullscreen] Meta: align with whatwg/meta resources (#115) (Saturday, 6 January)
• Re: [whatwg/url] Editorial: Update link to maintainer guidlines (#364) (Saturday, 6 January)
• Re: [whatwg/url] Editorial: Update link to maintainer guidlines (#364) (Saturday, 6 January)
• Re: [whatwg/url] Editorial: Update link to maintainer guidlines (#364) (Saturday, 6 January)
• Re: [whatwg/url] Editorial: Update link to maintainer guidlines (#364) (Saturday, 6 January)
• Re: [whatwg/xhr] Meta: reference whatwg/meta resources (#185) (Saturday, 6 January)
• Re: [whatwg/fetch] Meta: reference whatwg/meta resources (#656) (Saturday, 6 January)
• Re: [whatwg/url] Editorial: Update link to maintainer guidlines (#364) (Saturday, 6 January)
• Re: [whatwg/url] Editorial: Update link to maintainer guidlines (#364) (Saturday, 6 January)
• [whatwg/url] Editorial: Update link to maintainer guidlines (#364) (Saturday, 6 January)
• [whatwg/streams] Editorial: Link to whatwg/meta COMMITING.md (#867) (Saturday, 6 January)
• Re: [whatwg/url] Editorial: Link to whatwg/meta COMMITING.md (#363) (Saturday, 6 January)
• [whatwg/url] Editorial: Link to whatwg/meta COMMITING.md (#363) (Saturday, 6 January)
• Re: [whatwg/dom] Editorial: Link to whatwg/meta COMMITING.md (#558) (Saturday, 6 January)
• [whatwg/dom] Editorial: Link to whatwg/meta COMMITING.md (#558) (Saturday, 6 January)

spanicker

• Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Wednesday, 31 January)
• Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Monday, 29 January)
• Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Friday, 19 January)
• Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263) (Friday, 19 January)

Surma

• Re: [whatwg/streams] A variety of clarity and documentation improvements (#875) (Wednesday, 31 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Wednesday, 31 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Wednesday, 31 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Wednesday, 31 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Saturday, 27 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Saturday, 27 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Saturday, 27 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Saturday, 27 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Saturday, 27 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Saturday, 27 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Saturday, 27 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Saturday, 27 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Saturday, 27 January)
• Re: [whatwg/streams] Add more cross-links (#872) (Friday, 26 January)
• [whatwg/streams] Add more cross-links (#872) (Friday, 26 January)

Tab Atkins Jr.

• Re: [heycam/webidl] More convenient way to refer to / use "map iterators" (#324) (Wednesday, 31 January)
• Re: [heycam/webidl] More convenient way to refer to / use "map iterators" (#324) (Wednesday, 31 January)
• Re: [heycam/webidl] More convenient way to refer to / use "map iterators" (#324) (Wednesday, 31 January)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Wednesday, 31 January)
• Re: [heycam/webidl] [Exposed] section unnecessarily restrictive about partial interface + members (#515) (Wednesday, 31 January)
• Re: [heycam/webidl] [Exposed] section unnecessarily restrictive about partial interface + members (#515) (Wednesday, 31 January)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Wednesday, 31 January)
• Re: [heycam/webidl] [Exposed] section unnecessarily restrictive about partial interface + members (#515) (Wednesday, 31 January)
• [heycam/webidl] [Exposed] section unnecessarily restrictive about partial interface + members (#515) (Wednesday, 31 January)
• Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564) (Wednesday, 31 January)
• Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564) (Tuesday, 30 January)
• Re: [whatwg/dom] "then increase hiddenSubtreeLevel by " (#564) (Tuesday, 30 January)
• Re: [heycam/webidl] Allow multimaps (or directly support them) (#514) (Monday, 29 January)
• [heycam/webidl] Allow multimaps (or directly support them) (#514) (Monday, 29 January)
• Re: [heycam/webidl] add a type to represent the undefined value (#60) (Monday, 29 January)
• Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223) (Sunday, 28 January)
• Re: [w3c/IndexedDB] Web IDL syntax error? (#226) (Thursday, 18 January)
• Re: [heycam/webidl] [wip] First pass at adding internal slots (#495) (Tuesday, 16 January)
• Re: [heycam/webidl] [wip] First pass at adding internal slots (#495) (Friday, 12 January)
• Re: [w3c/permissions] A new permission for canvas data (#165) (Friday, 5 January)
• Re: [w3c/permissions] A new permission for canvas data (#165) (Thursday, 4 January)
• Re: [whatwg/url] Meta: update copyright license and Bikeshed boilerplate (#360) (Tuesday, 2 January)

Takayoshi Kochi

• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 30 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 30 January)
• [w3c/uievents] Add a note about inheritance of UIEvent. (#178) (Tuesday, 30 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 23 January)
• Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62) (Wednesday, 17 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Wednesday, 17 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• [w3c/clipboard-apis] Make all clipboard events composed by default. (#62) (Tuesday, 16 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Monday, 15 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Monday, 15 January)
• [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Monday, 15 January)

Takeshi Yoshino

• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Tuesday, 9 January)

tdons

• Re: [whatwg/xhr] The xhr logo appears to be copied from AFC Ajax (Dutch soccer club) (#186) (Thursday, 11 January)
• Re: [whatwg/xhr] The xhr logo appears to be copied from AFC Ajax (Dutch soccer club) (#186) (Thursday, 11 January)
• [whatwg/xhr] The xhr logo appears to be copied from AFC Ajax (Dutch soccer club) (#186) (Thursday, 11 January)

Ted Mielczarek

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

Thomas Steiner

• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Thursday, 11 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)

Till Schneidereit

• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Thursday, 25 January)
• Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Tuesday, 23 January)
• [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870) (Monday, 22 January)
• Re: [whatwg/streams] Extract length and offset from TypedArray view before transferring its buffer (#868) (Tuesday, 9 January)
• Re: [whatwg/streams] Extract length and offset from TypedArray view before transferring its buffer (#868) (Tuesday, 9 January)
• [whatwg/streams] Extract length and offset from TypedArray view before transferring its buffer (#868) (Sunday, 7 January)

Tim van der Lippe

• Re: [whatwg/dom] Inconsistency in execution of unclosed attribute selector for querySelector (#549) (Monday, 8 January)

Timothy Gu

• [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 31 January)
• Re: [heycam/webidl] Definition of "is an array index" makes "-0" an array index (#516) (Wednesday, 31 January)
• Re: [heycam/webidl] typeof operator and platform objects (#512) (Thursday, 18 January)
• [heycam/webidl] typeof operator and platform objects (#512) (Thursday, 18 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 18 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Unexplained restrictions in operation bindings section (#511) (Thursday, 11 January)
• Re: [heycam/webidl] Unexplained restrictions in operation bindings section (#511) (Thursday, 11 January)
• Re: [heycam/webidl] Clarify what iterating over operations means (#510) (Thursday, 11 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Tuesday, 9 January)
• Re: [whatwg/fetch] Define how to handle bad content encoding (#657) (Monday, 8 January)
• Re: [whatwg/fetch] Define how to handle bad content encoding (#657) (Monday, 8 January)
• Re: [heycam/webidl] Editorial: remove the remaining subscript notation for argument lists (#508) (Sunday, 7 January)
• Re: [heycam/webidl] Include typedefs in the JSON type definition (#505) (Wednesday, 3 January)
• Re: [heycam/webidl] Include typedefs in the JSON type definition (#505) (Tuesday, 2 January)

Tobie Langel

• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 31 January)
• Re: [heycam/webidl] [Exposed] section unnecessarily restrictive about partial interface + members (#515) (Wednesday, 31 January)
• Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517) (Wednesday, 31 January)
• Re: [heycam/webidl] Specify PropertyDescriptor of @@toStringTag symbol (#513) (Friday, 19 January)
• Re: [heycam/webidl] Specify PropertyDescriptor of @@toStringTag symbol (#513) (Friday, 19 January)
• [heycam/webidl] Specify PropertyDescriptor of @@toStringTag symbol (#513) (Friday, 19 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 18 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 18 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 18 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 18 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 18 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Saturday, 13 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Saturday, 13 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Saturday, 13 January)
• Re: [heycam/webidl] Unexplained restrictions in operation bindings section (#511) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Friday, 12 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 11 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 11 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 11 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 11 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 11 January)
• Re: [heycam/webidl] Unexplained restrictions in operation bindings section (#511) (Thursday, 11 January)
• [heycam/webidl] Unexplained restrictions in operation bindings section (#511) (Thursday, 11 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 11 January)
• [heycam/webidl] Clarify what iterating over operations means (#510) (Thursday, 11 January)
• Re: [heycam/webidl] Prototype of @@unscopable object (#496) (Thursday, 11 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 11 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 11 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Thursday, 11 January)
• Re: [heycam/webidl] Prototype of @@unscopable object (#496) (Thursday, 11 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 8 January)
• Re: [heycam/webidl] Make interface prototype object creation imperative (#494) (Monday, 8 January)
• Re: [heycam/webidl] Editorial: remove the remaining subscript notation for argument lists (#508) (Sunday, 7 January)
• [heycam/webidl] Editorial: remove the remaining subscript notation for argument lists (#508) (Sunday, 7 January)
• Re: [heycam/webidl] Add informative section on legacy constructs (#506) (Thursday, 4 January)
• Re: [heycam/webidl] Add informative section on legacy constructs (#506) (Thursday, 4 January)
• Re: [heycam/webidl] Add informative section on legacy constructs (#506) (Thursday, 4 January)
• Re: [heycam/webidl] Add informative section on legacy constructs (#506) (Thursday, 4 January)
• [heycam/webidl] Add informative section on legacy constructs (#506) (Thursday, 4 January)
• Re: [heycam/webidl] Include typedefs in the JSON type definition (#505) (Wednesday, 3 January)
• Re: [heycam/webidl] Include typedefs in the JSON type definition (#505) (Tuesday, 2 January)
• Re: [heycam/webidl] Is DOMHighResTimeStamp a "JSON type"? (#504) (Tuesday, 2 January)
• [heycam/webidl] Include typedefs in the JSON type definition (#505) (Tuesday, 2 January)

Tom Ritter

• Re: [w3c/permissions] A new permission for canvas data (#165) (Thursday, 4 January)

Tom Shinnick

• [w3c/screen-orientation] Where are terms 'primary' and 'secondary' defined within spec? (#113) (Tuesday, 30 January)

Tomeyer

• [whatwg/xhr] localhost:8989 (#183) (Tuesday, 2 January)
• [whatwg/xhr] localhost:7676 (#182) (Tuesday, 2 January)

Travis Leithead

• Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Request for TAG review of Input events level 2 (#173) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Request for TAG review of Input events level 2 (#173) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Wednesday, 31 January)
• [w3ctag/design-reviews] Should WebRTC be [SecureContext] (#228) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Task Scheduling (#72) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Review request for WebVR (#185) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214) (Wednesday, 31 January)
• Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215) (Friday, 26 January)
• Re: [whatwg/url] URLSearchParams and URL [Serializable] (#370) (Friday, 26 January)
• Re: [w3ctag/design-reviews] Review request: Web Lifecycle for system initiated Discarding & Stopping (#205) (Friday, 19 January)
• Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61) (Tuesday, 16 January)
• Re: [whatwg/dom] Consider removing `document.origin` (#410) (Wednesday, 10 January)
• Re: [w3ctag/design-reviews] Consider general storage observer that works for cookies (#210) (Wednesday, 10 January)

Valentin Gosu

• Re: [whatwg/fetch] Define data: URLs (#579) (Saturday, 13 January)

victoriasu

• Re: [w3ctag/design-reviews] CSS Selectors 4 (#219) (Thursday, 18 January)

Walle Cyril

• [w3c/ServiceWorker] What is the correct way to notify the DOM thread about files that have been cached ? (#1260) (Thursday, 18 January)

Wanming Lin

• [w3c/manifest] PromptResponseObject definition is missing in "IDL Index" (#637) (Wednesday, 10 January)

Wenbo Zhu

• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Saturday, 20 January)

wy

• [w3c/ServiceWorker] Suggest a top level service worker or multiple service workers in one domain? (#1264) (Friday, 19 January)

Xidorn Quan

• Re: [whatwg/fullscreen] Investigate whether nested fullscreen element is necessary (#119) (Monday, 29 January)
• Re: [whatwg/fullscreen] Investigate whether nested fullscreen element is necessary (#119) (Monday, 29 January)
• [whatwg/fullscreen] Investigate whether nested fullscreen element is necessary (#119) (Monday, 29 January)
• Re: [whatwg/fullscreen] Ending fullscreen for popups (#116) (Saturday, 27 January)
• Re: [whatwg/fullscreen] Ending fullscreen for popups (#116) (Saturday, 27 January)
• Re: [whatwg/fullscreen] Consider forbidding <frame> element from entering fullscreen (#112) (Wednesday, 3 January)
• [whatwg/fullscreen] Consider forbidding <frame> element from entering fullscreen (#112) (Wednesday, 3 January)

Yoav Weiss

• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Monday, 15 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 15 January)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Monday, 15 January)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Monday, 15 January)
• Re: [whatwg/fetch] Add a `prefetch` initiator (#659) (Monday, 15 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• [whatwg/fetch] Add a `prefetch` initiator (#659) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)
• [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658) (Monday, 8 January)

youennf

• Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266) (Wednesday, 31 January)
• [whatwg/fetch] Return a network error in case of no-cors mode and redirect being not follow (#663) (Wednesday, 17 January)
• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Thursday, 11 January)
• Re: [whatwg/fetch] Redirect and credential URLs (#660) (Thursday, 11 January)
• Re: [whatwg/fetch] Redirect and credential URLs (#660) (Thursday, 11 January)
• [whatwg/fetch] Redirect and credential URLs (#660) (Wednesday, 10 January)
• Re: [whatwg/fetch] Redirect and credential URLs (#660) (Wednesday, 10 January)
• Re: [whatwg/fetch] consider failing same-origin fetch requests that get a cross-origin cors Response synthesized by a service worker (#629) (Saturday, 6 January)

Yutaka Hirano

• Re: [whatwg/streams] Add "was ever locked" flag for Encoding standard? (#873) (Tuesday, 30 January)
• Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127) (Monday, 29 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Wednesday, 24 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Tuesday, 23 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Thursday, 18 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Thursday, 18 January)
• Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Tuesday, 16 January)
• [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662) (Monday, 15 January)

Yves Lafon

• Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Monday, 22 January)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Monday, 22 January)

Zach Koch

• Re: [w3c/manifest] Add payment handler installation URL. (#634) (Thursday, 4 January)

Zirro

• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 3 January)

Last message date: Wednesday, 31 January 2018 23:50:54 UTC