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

Adam Roben

• [selection-api] Fix capitalization of GitHub (#44) (Thursday, 5 February)

Alex Russell

• Re: [ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) (Friday, 27 February)
• Re: [ServiceWorker] client.focus() should reject if tab failed to focus (#640) (Friday, 27 February)
• Re: [ServiceWorker] caching of importScripts()-scripts (#106) (Thursday, 26 February)
• Re: [ServiceWorker] FetchEvent.forwardTo is completely unspecced (#637) (Wednesday, 25 February)
• Re: [ServiceWorker] `waitUntil()` for FetchEvent? (#584) (Thursday, 12 February)
• Re: [ServiceWorker] `waitUntil()` for FetchEvent? (#584) (Thursday, 12 February)
• Re: [ServiceWorker] `waitUntil()` for FetchEvent? (#584) (Thursday, 12 February)
• Re: [manifest] Integration with service workers (#161) (Monday, 9 February)
• Re: [manifest] Integration with service workers (#161) (Friday, 6 February)
• Re: [manifest] Integration with service workers (#161) (Thursday, 5 February)

alxlu

• Re: [manifest] Add recommended width and height (#310) (Wednesday, 25 February)

Amir E. Aharoni

• [editing-explainer] Correct a spelling mistake (#46) (Saturday, 21 February)

Anne van Kesteren

• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Friday, 27 February)
• Re: [ServiceWorker] caching of importScripts()-scripts (#106) (Friday, 27 February)
• Re: [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Friday, 27 February)
• Re: [ServiceWorker] Change "doesn't not" to "doesn't" in README file (#641) (Friday, 27 February)
• Re: [ServiceWorker] importScripts() should throw? (#642) (Friday, 27 February)
• [ServiceWorker] importScripts() should throw? (#642) (Friday, 27 February)
• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Friday, 27 February)
• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Friday, 27 February)
• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Thursday, 26 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Thursday, 26 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Thursday, 26 February)
• Re: [fetch] Add timeout option (#20) (Thursday, 26 February)
• Re: [fetch] Add timeout option (#20) (Thursday, 26 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 25 February)
• Re: [ServiceWorker] FetchEvent.forwardTo is completely unspecced (#637) (Wednesday, 25 February)
• Re: [ServiceWorker] How to set the client for the requests initiated from within user agent's internal context? (#615) (Tuesday, 24 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Tuesday, 24 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Tuesday, 24 February)
• Re: [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Tuesday, 24 February)
• Re: [ServiceWorker] Capture Window Client cannot use attributes/methods directly (#633) (Tuesday, 24 February)
• Re: [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Tuesday, 24 February)
• Re: [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Tuesday, 24 February)
• [ServiceWorker] Capture Window Client cannot use attributes/methods directly (#633) (Tuesday, 24 February)
• [ServiceWorker] Why would `WindowClient` ever have `frameType` of `none`? (#632) (Tuesday, 24 February)
• Re: [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Tuesday, 24 February)
• Re: [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Tuesday, 24 February)
• Re: [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Monday, 23 February)
• [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Monday, 23 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Monday, 23 February)
• Re: [ServiceWorker] Passing a scope or scriptURL to register() with escaped '/' or '\ should fail (#630) (Friday, 20 February)
• Re: [fetch] upload progress? (#21) (Friday, 20 February)
• Re: [fetch] upload progress? (#21) (Friday, 20 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Thursday, 19 February)
• Re: [ServiceWorker] Should Request constructor be less destructive when it fails? (#629) (Thursday, 19 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 18 February)
• Re: [ServiceWorker] Consider producing distinct objects for the same entity to enable garbage collection (#416) (Wednesday, 18 February)
• Re: [streams] Define "tee"ing a stream (#271) (Wednesday, 18 February)
• Re: [streams] Define "tee"ing a stream (#271) (Wednesday, 18 February)
• Re: [ServiceWorker] Use SyntaxError when an URL can't be parsed in Clients.openWindow() (#619) (Wednesday, 18 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Wednesday, 18 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Wednesday, 18 February)
• Re: [ServiceWorker] Cache and Request objects (#624) (Wednesday, 18 February)
• [ServiceWorker] Should Request constructor be less destructive when it fails? (#629) (Wednesday, 18 February)
• Re: [streams] Define "tee"ing a stream (#271) (Wednesday, 18 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 18 February)
• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Tuesday, 17 February)
• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Tuesday, 17 February)
• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Tuesday, 17 February)
• Re: [ServiceWorker] Changing Request and fetch() (#625) (Tuesday, 17 February)
• Re: [ServiceWorker] Changing Request and fetch() (#625) (Monday, 16 February)
• Re: [ServiceWorker] Changing Request and fetch() (#625) (Monday, 16 February)
• Re: [ServiceWorker] Changing Request and fetch() (#625) (Monday, 16 February)
• Re: [ServiceWorker] Cache and Request objects (#624) (Monday, 16 February)
• Re: [ServiceWorker] Changing Request and fetch() (#625) (Monday, 16 February)
• Re: [ServiceWorker] Changing Request and fetch() (#625) (Monday, 16 February)
• [ServiceWorker] Changing Request and fetch() (#625) (Monday, 16 February)
• [ServiceWorker] Cache and Request objects (#624) (Monday, 16 February)
• Re: [ServiceWorker] fix typo (#623) (Sunday, 15 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Thursday, 12 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Thursday, 12 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Thursday, 12 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Thursday, 12 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Thursday, 12 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Thursday, 12 February)
• Re: [ServiceWorker] Update explainer.md (#620) (Wednesday, 11 February)
• Re: [ServiceWorker] Use SyntaxError when an URL can't be parsed in Clients.openWindow() (#619) (Wednesday, 11 February)
• Re: [ServiceWorker] Use SyntaxError when an URL can't be parsed in Clients.openWindow() (#619) (Wednesday, 11 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Wednesday, 11 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Wednesday, 11 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Wednesday, 11 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Tuesday, 10 February)
• Re: [ServiceWorker] A header/something to kill SWs (#614) (Tuesday, 10 February)
• [ServiceWorker] Update algorithm and redirects (#618) (Tuesday, 10 February)
• Re: [ServiceWorker] A header/something to kill SWs (#614) (Monday, 9 February)
• Re: [ServiceWorker] What's the interaction with referrer policy (#404) (Wednesday, 4 February)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Tuesday, 3 February)
• Re: [ServiceWorker] window.caches and window.fetch should be [Replaceable] (#535) (Tuesday, 3 February)
• Re: [ServiceWorker] window.caches and window.fetch should be [Replaceable] (#535) (Tuesday, 3 February)
• Re: [ServiceWorker] window.caches and window.fetch should be [Replaceable] (#535) (Tuesday, 3 February)
• Re: [ServiceWorker] Reliable ordering of fetch event handlers (#613) (Monday, 2 February)
• Re: [ServiceWorker] Reliable ordering of fetch event handlers (#613) (Monday, 2 February)
• Re: [ServiceWorker] Should an IFRAME without src be controlled by SW when its parent is controlled? (#612) (Monday, 2 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Monday, 2 February)
• Re: [ServiceWorker] Should an IFRAME without src be controlled by SW when its parent is controlled? (#612) (Monday, 2 February)
• Re: [ServiceWorker] Hints in beforeevicted to let the SW of a web app pick among several house cleaning options? (#611) (Sunday, 1 February)

Anssi Kostiainen

• Re: [manifest] Move to using Echidna (#315) (Tuesday, 17 February)

Arthur Stolyar

• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Wednesday, 25 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Wednesday, 25 February)

B

• Re: [screen-orientation] The orientation type 'Natural' should only lock to x-primary (#83) (Thursday, 12 February)

Ben Francis

• Re: [manifest] Integration with service workers (#161) (Friday, 6 February)

Ben Kelly

• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Friday, 27 February)
• Re: [ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) (Friday, 27 February)
• Re: [ServiceWorker] Relationship to Caches & ScriptCache in ServiceWorkerGlobalScope (#473) (Wednesday, 25 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Friday, 20 February)
• Re: [ServiceWorker] Should Request constructor be less destructive when it fails? (#629) (Thursday, 19 February)
• Re: [streams] Define "tee"ing a stream (#271) (Wednesday, 18 February)
• Re: [streams] Define "tee"ing a stream (#271) (Wednesday, 18 February)
• Re: [streams] Define "tee"ing a stream (#271) (Wednesday, 18 February)
• Re: [ServiceWorker] Should Request constructor be less destructive when it fails? (#629) (Wednesday, 18 February)
• Re: [streams] Define "tee"ing a stream (#271) (Wednesday, 18 February)
• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Tuesday, 17 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Monday, 16 February)
• Re: [ServiceWorker] Changing Request and fetch() (#625) (Monday, 16 February)
• Re: [ServiceWorker] Cache and Request objects (#624) (Monday, 16 February)
• Re: [ServiceWorker] Changing Request and fetch() (#625) (Monday, 16 February)
• Re: [ServiceWorker] Cache and Request objects (#624) (Monday, 16 February)
• Re: [ServiceWorker] `waitUntil()` for FetchEvent? (#584) (Thursday, 12 February)
• Re: [ServiceWorker] `waitUntil()` for FetchEvent? (#584) (Thursday, 12 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 10 February)
• Re: [ServiceWorker] `waitUntil()` for FetchEvent? (#584) (Tuesday, 10 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Tuesday, 10 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Monday, 9 February)
• Re: [ServiceWorker] Is the ServiceWorker also a client? (#603) (Saturday, 7 February)
• Re: [ServiceWorker] Specify .focus() and .openWindow() behaviour (#602) (Saturday, 7 February)
• Re: [ServiceWorker] Rename clients.getAll() (#610) (Saturday, 7 February)
• Re: [ServiceWorker] clients.getAll -> clients.matchAll. Fixes #610 (ee62cfc) (Saturday, 7 February)
• Re: [ServiceWorker] Service-Worker-Allowed header (#604) (Saturday, 7 February)
• Re: [ServiceWorker] Add an API to take over uncontrolled pages (or pages controlled by another service worker) (#586) (Saturday, 7 February)
• Re: [ServiceWorker] Remove prefixMatch from CacheQueryOptions (#617) (Friday, 6 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Friday, 6 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Friday, 6 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Friday, 6 February)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Thursday, 5 February)
• Re: [streams] can streams be transferred via postMessage()? (#276) (Thursday, 5 February)
• Re: [ServiceWorker] How to set the client for the requests initiated from within user agent's internal context? (#615) (Thursday, 5 February)
• [streams] can streams be transferred via postMessage()? (#276) (Wednesday, 4 February)

Ben Peters

• Re: [editing-explainer] Should Device-Specific Input Events say what Responsive Input Event they will cause? (#25) (Monday, 23 February)
• Re: [editing-explainer] Should the term be Device Independent Events? (#7) (Monday, 23 February)
• Re: [editing-explainer] Where can text be inserted? (and how? can UA create text nodes?) (#21) (Monday, 23 February)
• Re: [editing-explainer] Where can text be inserted? (and how? can UA create text nodes?) (#21) (Monday, 23 February)
• Re: [editing-explainer] Should Device-Specific Input Events say what Responsive Input Event they will cause? (#25) (Monday, 23 February)
• Re: [editing-explainer] Need to spec the data in beforeInput event (#29) (Monday, 23 February)
• Re: [editing-explainer] Need to spec the data in beforeInput event (#29) (Monday, 23 February)
• Re: [editing-explainer] Target range in device independent events (#39) (Monday, 23 February)
• Re: [editing-explainer] Correct a spelling mistake (#46) (Sunday, 22 February)
• Re: [editing-explainer] Should sites be able to control Responsive Input Language? (#31) (Friday, 20 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)

Bert Belder

• Re: [streams] Maybe giving async readInto (and read?) another shot (#290) (Saturday, 28 February)
• Re: [streams] Maybe giving async readInto (and read?) another shot (#290) (Saturday, 28 February)
• Re: [streams] Maybe giving async readInto (and read?) another shot (#290) (Saturday, 28 February)

Boris Zbarsky

• Re: [webidl] Update index.xml (#30) (Thursday, 26 February)
• Re: [webidl] Update index.xml (#30) (Thursday, 26 February)
• Re: [webidl] Update index.xml (#31) (Thursday, 26 February)
• Re: [webidl] Update index.xml (#31) (Thursday, 26 February)
• Re: [webidl] Update index.xml (#32) (Thursday, 26 February)
• Re: [webidl] Update index.xml (#32) (Thursday, 26 February)
• Re: [webidl] Followup for https://www.w3.org/Bugs/Public/show_bug.cgi?id=23133 to make sure we don't have to deal with defining prototype chains for interface objects when [NoInterfaceObject] is involved. (#38) (Wednesday, 11 February)
• [webidl] Fix https://www.w3.org/Bugs/Public/show_bug.cgi?id=27988 by removing the separate concept of indexed/named creators; setters are always also creators. (#44) (Tuesday, 10 February)

Brad Hill

• Re: [manifest] starring is giving/being a star, staring is looking at something intently (#311) (Friday, 13 February)
• [manifest] starring is giving/being a star, staring is looking at something intently (#311) (Friday, 13 February)

Cameron McCormack

• Re: [webidl] Fix https://www.w3.org/Bugs/Public/show_bug.cgi?id=27988 by removing the separate concept of indexed/named creators; setters are always also creators. (#44) (Friday, 27 February)
• Re: [webidl] Followup for https://www.w3.org/Bugs/Public/show_bug.cgi?id=23133 to make sure we don't have to deal with defining prototype chains for interface objects when [NoInterfaceObject] is involved. (#38) (Monday, 16 February)
• Re: [webidl] Followup for https://www.w3.org/Bugs/Public/show_bug.cgi?id=23133 to make sure we don't have to deal with defining prototype chains for interface objects when [NoInterfaceObject] is involved. (#38) (Monday, 16 February)
• Re: [webidl] Numeric type reform strawperson (#33) (Tuesday, 3 February)
• Re: [webidl] Numeric type reform strawperson (#33) (Tuesday, 3 February)
• Re: [webidl] Dead links to "consequential interface" (#43) (Tuesday, 3 February)
• Re: [webidl] Dead links to "consequential interface" (#43) (Tuesday, 3 February)
• Re: [webidl] Numeric type reform strawperson (#33) (Tuesday, 3 February)
• [webidl] explicitly invoke [[HasOwnProperty]], [[GetProperyOf]], etc. more often (#42) (Tuesday, 3 February)

Cătălin Badea

• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 25 February)

David Pursehouse

• [ServiceWorker] Change "doesn't not" to "doesn't" in README file (#641) (Thursday, 26 February)

Domenic Denicola

• Re: [streams] Maybe giving async readInto (and read?) another shot (#290) (Saturday, 28 February)
• Re: [streams] Maybe giving async readInto (and read?) another shot (#290) (Saturday, 28 February)
• Re: [streams] Operation stream (#287) (Saturday, 28 February)
• Re: [streams] Operation stream (#287) (Saturday, 28 February)
• [streams] Maybe giving async readInto (and read?) another shot (#290) (Saturday, 28 February)
• Re: [streams] New proposal for byte stream uses cases (#289) (Friday, 27 February)
• Re: [streams] New proposal for byte stream uses cases (#289) (Friday, 27 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Friday, 27 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Friday, 27 February)
• Re: [streams] Operation stream (#287) (Friday, 27 February)
• Re: [streams] New proposal for byte stream uses cases (#289) (Friday, 27 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Friday, 27 February)
• [streams] New proposal for byte stream uses cases (#289) (Thursday, 26 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Thursday, 26 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Thursday, 26 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Thursday, 26 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Wednesday, 25 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 25 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 25 February)
• Re: [streams] Operation stream (#287) (Tuesday, 24 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Tuesday, 24 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Tuesday, 24 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Tuesday, 24 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Tuesday, 24 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Tuesday, 24 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Tuesday, 24 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Tuesday, 24 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Tuesday, 24 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Saturday, 21 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Saturday, 21 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Saturday, 21 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Saturday, 21 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Saturday, 21 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Friday, 20 February)
• Re: [streams] readable-stream-cancel.js "ReadableStream canceling an infinite stream" is flaky (#286) (Friday, 20 February)
• [streams] Change the model for ReadableStream to have async read() (#288) (Friday, 20 February)
• Re: [streams] Fixed typo in readable-stream tests (#285) (Wednesday, 18 February)
• Re: [streams] Fixed typo in readable-stream tests (#285) (Wednesday, 18 February)
• Re: [streams] readable-stream-cancel.js "ReadableStream canceling an infinite stream" is flaky (#286) (Wednesday, 18 February)
• Re: [streams] Define "tee"ing a stream (#271) (Wednesday, 18 February)
• Re: [streams] Define "tee"ing a stream (#271) (Wednesday, 18 February)
• Re: [streams] Uses of "upon fulfillment/rejection" contain unused returns and throws (#284) (Tuesday, 17 February)
• Re: [streams] Uses of "upon fulfillment/rejection" contain unused returns and throws (#284) (Tuesday, 17 February)
• Re: [streams] Uses of "upon fulfillment/rejection" contain unused returns and throws (#284) (Tuesday, 17 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Tuesday, 17 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Tuesday, 17 February)
• Re: [ServiceWorker] Changing Request and fetch() (#625) (Monday, 16 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Friday, 13 February)
• Re: [ServiceWorker] Confusing use of `transforming with` and `Upon fulfillment`. (#621) (Friday, 13 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Thursday, 12 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Thursday, 12 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Thursday, 12 February)
• Re: [webidl] Followup for https://www.w3.org/Bugs/Public/show_bug.cgi?id=23133 to make sure we don't have to deal with defining prototype chains for interface objects when [NoInterfaceObject] is involved. (#38) (Thursday, 12 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [ServiceWorker] Use SyntaxError when an URL can't be parsed in Clients.openWindow() (#619) (Wednesday, 11 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Tuesday, 10 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 10 February)
• Re: [streams] Update ReadableByteStream to follow the style rule employed for the main... (#283) (Tuesday, 10 February)
• Re: [streams] Update ReadableByteStream to follow the style rule employed for the main... (#283) (Tuesday, 10 February)
• Re: [streams] Add readableAmount getter to ReadableByteStream (#279) (Tuesday, 10 February)
• Re: [streams] Use angle quotes for lists (#281) (Tuesday, 10 February)
• Re: [streams] Use angle quotes for lists (#281) (Tuesday, 10 February)
• Re: [streams] Use angle quotes for lists (#281) (Tuesday, 10 February)
• Re: [streams] Use angle quotes for lists (#281) (Tuesday, 10 February)
• Re: [streams] Use angle quotes for lists (#281) (Tuesday, 10 February)
• Re: [streams] Use angle quotes for lists (#281) (Tuesday, 10 February)
• Re: [streams] Byte stream promises update (#280) (Tuesday, 10 February)
• Re: [streams] Byte stream promises update (#280) (Tuesday, 10 February)
• Re: [streams] Add readableAmount getter to ReadableByteStream (#279) (Tuesday, 10 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 10 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 10 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Tuesday, 10 February)
• Re: [streams] I can not find the copyright of the reference implementation. (#278) (Monday, 9 February)
• Re: [streams] Add IsReadableStreamLocked abstract operation (#259) (Monday, 9 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Monday, 9 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Monday, 9 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Monday, 9 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Monday, 9 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Monday, 9 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Friday, 6 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Friday, 6 February)
• Re: [streams] Is Node's "unshift" necessary? (#3) (Friday, 6 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Friday, 6 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Thursday, 5 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Thursday, 5 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Thursday, 5 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Thursday, 5 February)
• Re: [streams] can streams be transferred via postMessage()? (#276) (Thursday, 5 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Wednesday, 4 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Wednesday, 4 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Wednesday, 4 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Wednesday, 4 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Wednesday, 4 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Wednesday, 4 February)
• Re: [streams] Requirement on promises equality (#266) (Wednesday, 4 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 3 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 3 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 3 February)
• Re: [webidl] Numeric type reform strawperson (#33) (Tuesday, 3 February)
• [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Tuesday, 3 February)
• Re: [streams] Requirement on promises equality (#266) (Monday, 2 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Monday, 2 February)

Erik Wilde

• Re: [manifest] Removed JSON-LD text (closes #313) (9a7f626) (Monday, 16 February)
• Re: [manifest] JSON-LD view (#313) (Monday, 16 February)
• [manifest] adding link relation registration with IANA (#314) (Sunday, 15 February)
• [manifest] JSON-LD view (#313) (Sunday, 15 February)
• Re: [manifest] "manifest" link relation type should be registered per RFC 5988 (#312) (Friday, 13 February)
• [manifest] "manifest" link relation type should be registered per RFC 5988 (#312) (Friday, 13 February)

Fedor Indutny

• Re: [streams] Maybe giving async readInto (and read?) another shot (#290) (Saturday, 28 February)
• Re: [streams] Maybe giving async readInto (and read?) another shot (#290) (Saturday, 28 February)

Gray Zhang

• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Friday, 27 February)

Harald Kirschner

• [manifest] Desktop web apps should be able to declare their viewport size (#317) (Tuesday, 17 February)

Honza Bambas

• Re: [ServiceWorker] Privacy consideration about the "cache" parameter of the Request object (#585) (Monday, 9 February)
• Re: [ServiceWorker] 304 handling for fetch() (#412) (Monday, 9 February)
• Re: [ServiceWorker] 304 handling for fetch() (#412) (Monday, 9 February)

Ilya Grigorik

• [packaging-on-the-web] Consider manifest~like approach instead of SPF (#23) (Saturday, 14 February)
• Re: [ServiceWorker] SW spec should expose Resource Timing and User Timing (#553) (Monday, 9 February)

iOnline247

• [ServiceWorker] Update explainer.md (#620) (Wednesday, 11 February)

Jake Archibald

• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Friday, 27 February)
• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Thursday, 26 February)
• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Thursday, 26 February)
• Re: [ServiceWorker] Minor edit: add "the" (#638) (Thursday, 26 February)
• Re: [ServiceWorker] Why would `WindowClient` ever have `frameType` of `none`? (#632) (Thursday, 26 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Thursday, 26 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Thursday, 26 February)
• Re: [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Thursday, 26 February)
• [ServiceWorker] client.focus() should reject if tab failed to focus (#640) (Thursday, 26 February)
• Re: [ServiceWorker] Relationship to Caches & ScriptCache in ServiceWorkerGlobalScope (#473) (Thursday, 26 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Thursday, 26 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Thursday, 26 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Thursday, 26 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Thursday, 26 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Thursday, 26 February)
• Re: [ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) (Thursday, 26 February)
• Re: [ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) (Thursday, 26 February)
• Re: [ServiceWorker] When exactly during unload does "Handle Service Worker Client Unload" run (#636) (Thursday, 26 February)
• Re: [ServiceWorker] FetchEvent.forwardTo is completely unspecced (#637) (Thursday, 26 February)
• Re: [ServiceWorker] FetchEvent.forwardTo is completely unspecced (#637) (Thursday, 26 February)
• Re: [ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) (Thursday, 26 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 25 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Tuesday, 24 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Tuesday, 24 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Tuesday, 24 February)
• Re: [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Tuesday, 24 February)
• Re: [ServiceWorker] ServiceWorker objects should have an .id (#635) (Tuesday, 24 February)
• [ServiceWorker] ServiceWorker objects should have an .id (#635) (Tuesday, 24 February)
• [ServiceWorker] client objects should have an .id (#634) (Tuesday, 24 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Friday, 20 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Friday, 20 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Wednesday, 18 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 18 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 18 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Wednesday, 18 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Wednesday, 18 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 18 February)
• Re: [ServiceWorker] Should Request constructor be less destructive when it fails? (#629) (Wednesday, 18 February)
• Re: [ServiceWorker] Consider producing distinct objects for the same entity to enable garbage collection (#416) (Wednesday, 18 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Tuesday, 17 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Monday, 16 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Monday, 16 February)
• [ServiceWorker] How are unloaded tabs represented? (#626) (Monday, 16 February)
• Re: [ServiceWorker] Cache and Request objects (#624) (Monday, 16 February)
• Re: [ServiceWorker] Cache and Request objects (#624) (Monday, 16 February)
• Re: [ServiceWorker] Changing Request and fetch() (#625) (Monday, 16 February)
• Re: [ServiceWorker] Changing Request and fetch() (#625) (Monday, 16 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Thursday, 12 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Thursday, 12 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Thursday, 12 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Thursday, 12 February)
• Re: [ServiceWorker] SW spec should expose Resource Timing and User Timing (#553) (Monday, 9 February)
• Re: [ServiceWorker] A header/something to kill SWs (#614) (Monday, 9 February)
• Re: [ServiceWorker] Option bag for .unregister, including immediate (#236) (Monday, 9 February)
• Re: [ServiceWorker] Option bag for .unregister, including immediate (#236) (Monday, 9 February)
• Re: [ServiceWorker] clients.getAll -> clients.matchAll. Fixes #610 (ee62cfc) (Monday, 9 February)
• Re: [ServiceWorker] Add an API to take over uncontrolled pages (or pages controlled by another service worker) (#586) (Monday, 9 February)
• Re: [manifest] Integration with service workers (#161) (Monday, 9 February)
• Re: [ServiceWorker] consider exposing size for cache entries (#587) (Monday, 9 February)
• [ServiceWorker] Remove prefixMatch from CacheQueryOptions (#617) (Friday, 6 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Friday, 6 February)
• Re: [manifest] Integration with service workers (#161) (Friday, 6 February)
• Re: [manifest] Integration with service workers (#161) (Friday, 6 February)
• Re: [manifest] Integration with service workers (#161) (Friday, 6 February)
• Re: [ServiceWorker] Expanded on the update() Note: (#616) (Wednesday, 4 February)
• Re: [ServiceWorker] How to set the client for the requests initiated from within user agent's internal context? (#615) (Wednesday, 4 February)
• Re: [ServiceWorker] Hints in beforeevicted to let the SW of a web app pick among several house cleaning options? (#611) (Wednesday, 4 February)
• Re: [ServiceWorker] Rename clients.getAll() (#610) (Wednesday, 4 February)
• Re: [ServiceWorker] Specify .focus() and .openWindow() behaviour (#602) (Wednesday, 4 February)
• Re: [ServiceWorker] Add an API to take over uncontrolled pages (or pages controlled by another service worker) (#586) (Monday, 2 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Monday, 2 February)
• Re: [ServiceWorker] Rename clients.getAll() (#610) (Monday, 2 February)
• Re: [ServiceWorker] Should an IFRAME without src be controlled by SW when its parent is controlled? (#612) (Monday, 2 February)

James Hartig

• Re: [streams] Requirement on promises equality (#266) (Tuesday, 10 February)

Jeffrey Posnick

• [ServiceWorker] Expanded on the update() Note: (#616) (Wednesday, 4 February)

Jeffrey Yasskin

• [permissions] Is `Permissions.get` the right name? (#5) (Wednesday, 25 February)
• Re: [ServiceWorker] Use of Upon fulfillment/rejection in CacheStorage.match is incorrect (#627) (Tuesday, 24 February)
• Re: [ServiceWorker] Use of Upon fulfillment/rejection in CacheStorage.match is incorrect (#627) (Tuesday, 24 February)
• Re: [ServiceWorker] Use of Upon fulfillment/rejection in CacheStorage.match is incorrect (#627) (Monday, 23 February)
• [packaging-on-the-web] What's the origin of a signed package? (#24) (Thursday, 19 February)
• [ServiceWorker] Activate uses "Wait for X to settle" inside a synchronous task. (#628) (Wednesday, 18 February)
• [ServiceWorker] Use of Upon fulfillment/rejection in CacheStorage.match is incorrect (#627) (Tuesday, 17 February)
• Re: [streams] Uses of "upon fulfillment/rejection" contain unused returns and throws (#284) (Tuesday, 17 February)
• Re: [streams] Uses of "upon fulfillment/rejection" contain unused returns and throws (#284) (Tuesday, 17 February)
• Re: [streams] Uses of "upon fulfillment/rejection" contain unused returns and throws (#284) (Tuesday, 17 February)
• [streams] Uses of "upon fulfillment/rejection" contain unused returns and throws (#284) (Tuesday, 17 February)
• Re: [ServiceWorker] Sort out promises' chained reaction text (5aa0ca2) (Friday, 13 February)
• Re: [ServiceWorker] Sort out promises' chained reaction text (5aa0ca2) (Friday, 13 February)
• Re: [ServiceWorker] Sort out promises' chained reaction text (5aa0ca2) (Friday, 13 February)
• Re: [ServiceWorker] Sort out promises' chained reaction text (5aa0ca2) (Friday, 13 February)
• Re: [ServiceWorker] Confusing use of `transforming with` and `Upon fulfillment`. (#621) (Friday, 13 February)
• [ServiceWorker] Confusing use of `transforming with` and `Upon fulfillment`. (#621) (Thursday, 12 February)

Joel Weinberger

• Re: [packaging-on-the-web] What's the origin of a signed package? (#24) (Thursday, 19 February)
• Re: [ServiceWorker] A header/something to kill SWs (#614) (Tuesday, 10 February)
• Re: [ServiceWorker] A header/something to kill SWs (#614) (Saturday, 7 February)

Johan Sörlin

• Re: [editing-explainer] Should sites be able to control Responsive Input Language? (#31) (Sunday, 22 February)
• Re: [editing-explainer] Should sites be able to control Responsive Input Language? (#31) (Friday, 20 February)

John Mellor

• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Thursday, 26 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 25 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Tuesday, 24 February)
• [push-api] Fire pushsubscriptionchange when user revokes permission (#116) (Tuesday, 24 February)
• Re: [push-api] Push events should Soft Update service worker (#115) (Thursday, 19 February)
• [push-api] Push events should Soft Update service worker (#115) (Thursday, 19 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Wednesday, 18 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Monday, 16 February)
• Re: [ServiceWorker] How are unloaded tabs represented? (#626) (Monday, 16 February)
• Re: [push-api] Add optional userVisibleOnly parameter to register & hasPermission (#87) (Thursday, 5 February)

Josh Matthews

• [ServiceWorker] FetchEvent.forwardTo is completely unspecced (#637) (Tuesday, 24 February)

Joshua Bell

• Re: [ServiceWorker] Clients & postMessage (#609) (Tuesday, 17 February)

Jungkee Song

• Re: [ServiceWorker] Why would `WindowClient` ever have `frameType` of `none`? (#632) (Friday, 27 February)
• Re: [ServiceWorker] Why would `WindowClient` ever have `frameType` of `none`? (#632) (Friday, 27 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Friday, 27 February)
• Re: [ServiceWorker] caching of importScripts()-scripts (#106) (Friday, 27 February)
• Re: [ServiceWorker] caching of importScripts()-scripts (#106) (Friday, 27 February)
• Re: [ServiceWorker] Why would `WindowClient` ever have `frameType` of `none`? (#632) (Thursday, 26 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 25 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 25 February)
• Re: [ServiceWorker] Capture Window Client cannot use attributes/methods directly (#633) (Tuesday, 24 February)
• Re: [ServiceWorker] Capture Window Client cannot use attributes/methods directly (#633) (Tuesday, 24 February)
• Re: [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Tuesday, 24 February)
• Re: [ServiceWorker] Make FetchEvent.prototype.client nullable (#631) (Tuesday, 24 February)
• Re: [ServiceWorker] Use of Upon fulfillment/rejection in CacheStorage.match is incorrect (#627) (Tuesday, 24 February)
• Re: [ServiceWorker] Confusing use of `transforming with` and `Upon fulfillment`. (#621) (Monday, 23 February)
• Re: [ServiceWorker] Confusing use of `transforming with` and `Upon fulfillment`. (#621) (Monday, 23 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Monday, 23 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Monday, 23 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Monday, 23 February)
• Re: [ServiceWorker] Use of Upon fulfillment/rejection in CacheStorage.match is incorrect (#627) (Monday, 23 February)
• Re: [ServiceWorker] Activate uses "Wait for X to settle" inside a synchronous task. (#628) (Monday, 23 February)
• Re: [ServiceWorker] Activate uses "Wait for X to settle" inside a synchronous task. (#628) (Monday, 23 February)
• Re: [ServiceWorker] Sort out promises' chained reaction text (5aa0ca2) (Monday, 16 February)
• Re: [ServiceWorker] Sort out promises' chained reaction text (5aa0ca2) (Monday, 16 February)
• Re: [ServiceWorker] Sort out promises' chained reaction text (5aa0ca2) (Monday, 16 February)
• Re: [ServiceWorker] Sort out promises' chained reaction text (5aa0ca2) (Monday, 16 February)
• Re: [ServiceWorker] Confusing use of `transforming with` and `Upon fulfillment`. (#621) (Friday, 13 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Friday, 13 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Thursday, 12 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Thursday, 12 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Thursday, 12 February)
• Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396) (Wednesday, 11 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Wednesday, 11 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Wednesday, 11 February)
• Re: [ServiceWorker] Update algorithm and redirects (#618) (Wednesday, 11 February)
• Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396) (Wednesday, 11 February)
• Re: [ServiceWorker] Remove prefixMatch from CacheQueryOptions (#617) (Tuesday, 10 February)
• Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396) (Tuesday, 10 February)
• Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396) (Tuesday, 10 February)
• Re: [ServiceWorker] Correct the atomic operation section in Update; allow new worker to get installed while an active worker is still effective (5f9b752) (Tuesday, 10 February)
• Re: [ServiceWorker] How to set the client for the requests initiated from within user agent's internal context? (#615) (Thursday, 5 February)
• Re: [ServiceWorker] How to set the client for the requests initiated from within user agent's internal context? (#615) (Thursday, 5 February)
• Re: [ServiceWorker] What's the interaction with referrer policy (#404) (Wednesday, 4 February)
• [ServiceWorker] How to set the client for the requests initiated from within user agent's internal context? (#615) (Wednesday, 4 February)
• Re: [ServiceWorker] What's the interaction with referrer policy (#404) (Wednesday, 4 February)
• Re: [ServiceWorker] What's the interaction with referrer policy (#404) (Wednesday, 4 February)
• Re: [ServiceWorker] Add an API to take over uncontrolled pages (or pages controlled by another service worker) (#586) (Monday, 2 February)
• Re: [ServiceWorker] Add an API to take over uncontrolled pages (or pages controlled by another service worker) (#586) (Monday, 2 February)

Jxck

• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Thursday, 26 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Thursday, 26 February)
• Re: [fetch] Add timeout option (#20) (Thursday, 26 February)

Jérémie Astori

• Re: [echidna] Generate unique id to identify the job (#60) (Friday, 6 February)

Kenji Baheux

• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 25 February)
• Re: [ServiceWorker] ServiceWorker to "service worker" mapping and stability (#622) (Tuesday, 17 February)
• Re: [ServiceWorker] consider exposing size for cache entries (#587) (Thursday, 5 February)
• Re: [ServiceWorker] A header/something to kill SWs (#614) (Monday, 2 February)
• Re: [ServiceWorker] Service-Worker-Allowed header (#604) (Monday, 2 February)
• Re: [ServiceWorker] Service-Worker-Allowed header (#604) (Monday, 2 February)
• [ServiceWorker] A header/something to kill SWs (#614) (Monday, 2 February)
• Re: [ServiceWorker] Add an API to take over uncontrolled pages (or pages controlled by another service worker) (#586) (Monday, 2 February)

Kenneth Rohde Christiansen

• Re: [manifest] Add recommended width and height (#310) (Wednesday, 25 February)
• Re: [manifest] Add recommended width and height (#310) (Wednesday, 25 February)
• Re: [manifest] Add recommended width and height (#310) (Wednesday, 25 February)
• Re: [manifest] clarify display-mode and UAs and iframes (closes #309) (ea9ac72) (Monday, 23 February)
• Re: [manifest] Desktop web apps should be able to declare their viewport size (#317) (Tuesday, 17 February)
• Re: [manifest] Move to using Echidna (#315) (Tuesday, 17 February)
• Re: [manifest] Removed JSON-LD text (closes #313) (#316) (Monday, 16 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Clarify display-mode relationship to iframes and legacy content (#309) (Monday, 9 February)
• Re: [manifest] Clarify display-mode relationship to iframes and legacy content (#309) (Monday, 9 February)

Kinuko Yasuda

• Re: [ServiceWorker] A header/something to kill SWs (#614) (Tuesday, 24 February)
• Re: [ServiceWorker] Hints in beforeevicted to let the SW of a web app pick among several house cleaning options? (#611) (Wednesday, 4 February)
• Re: [ServiceWorker] Hints in beforeevicted to let the SW of a web app pick among several house cleaning options? (#611) (Sunday, 1 February)

Long Xiang

• Re: [ServiceWorker] Add an API to take over uncontrolled pages (or pages controlled by another service worker) (#586) (Monday, 2 February)
• Re: [ServiceWorker] Add an API to take over uncontrolled pages (or pages controlled by another service worker) (#586) (Monday, 2 February)

Marcos Caceres

• Re: [manifest] Add recommended width and height (#310) (Thursday, 26 February)
• Re: [permissions] A "dismissed" state (#4) (Wednesday, 25 February)
• Re: [manifest] Add recommended width and height (#310) (Wednesday, 25 February)
• Re: [permissions] Is `Permissions.get` the right name? (#5) (Wednesday, 25 February)
• Re: [manifest] Add recommended width and height (#310) (Wednesday, 25 February)
• Re: [manifest] Add recommended width and height (#310) (Wednesday, 25 February)
• Re: [manifest] clarify display-mode and UAs and iframes (closes #309) (ea9ac72) (Monday, 23 February)
• [manifest] clarify display-mode and UAs and iframes (closes #309) (#318) (Monday, 23 February)
• Re: [manifest] Move to using Echidna (#315) (Friday, 20 February)
• Re: [manifest] Add recommended width and height (#310) (Friday, 20 February)
• Re: [manifest] Add recommended width and height (#310) (Friday, 20 February)
• Re: [manifest] Desktop web apps should be able to declare their viewport size (#317) (Wednesday, 18 February)
• Re: [manifest] Desktop web apps should be able to declare their viewport size (#317) (Wednesday, 18 February)
• Re: [manifest] Move to using Echidna (#315) (Tuesday, 17 February)
• Re: [manifest] Move to using Echidna (#315) (Tuesday, 17 February)
• Re: [manifest] JSON-LD view (#313) (Tuesday, 17 February)
• Re: [manifest] Removed JSON-LD text (closes #313) (#316) (Tuesday, 17 February)
• Re: [manifest] Removed JSON-LD text (closes #313) (9a7f626) (Monday, 16 February)
• [manifest] Removed JSON-LD text (closes #313) (#316) (Monday, 16 February)
• [manifest] Move to using Echidna (#315) (Monday, 16 February)
• Re: [manifest] [meta] transition doc. to CR at W3C (#308) (Monday, 16 February)
• Re: [manifest] [meta] transition doc. to CR at W3C (#308) (Monday, 16 February)
• Re: [manifest] JSON-LD view (#313) (Monday, 16 February)
• Re: [manifest] "manifest" link relation type should be registered per RFC 5988 (#312) (Monday, 16 February)
• Re: [manifest] "manifest" link relation type should be registered per RFC 5988 (#312) (Monday, 16 February)
• Re: [manifest] "manifest" link relation type should be registered per RFC 5988 (#312) (Monday, 16 February)
• Re: [manifest] adding link relation registration with IANA (#314) (Monday, 16 February)
• Re: [manifest] adding link relation registration with IANA (#314) (Monday, 16 February)
• Re: [manifest] "manifest" link relation type should be registered per RFC 5988 (#312) (Saturday, 14 February)
• Re: [manifest] "manifest" link relation type should be registered per RFC 5988 (#312) (Friday, 13 February)
• Re: [manifest] starring is giving/being a star, staring is looking at something intently (#311) (Friday, 13 February)
• Re: [manifest] starring is giving/being a star, staring is looking at something intently (#311) (Friday, 13 February)
• Re: [manifest] starring is giving/being a star, staring is looking at something intently (#311) (Friday, 13 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Clarify display-mode relationship to iframes and legacy content (#309) (Monday, 9 February)
• Re: [manifest] Clarify display-mode relationship to iframes and legacy content (#309) (Monday, 9 February)
• Re: [manifest] A means to control the color of the status bar (#225) (Sunday, 8 February)
• Re: [manifest] A means to control the color of the status bar (#225) (Sunday, 8 February)
• Re: [manifest] Integration with service workers (#161) (Friday, 6 February)
• Re: [manifest] Integration with service workers (#161) (Friday, 6 February)
• Re: [manifest] check against security/privacy questions (#305) (Tuesday, 3 February)
• [packaging-on-the-web] Icon container as use case (#22) (Tuesday, 3 February)

Mark Nottingham

• Re: [ServiceWorker] 304 handling for fetch() (#412) (Tuesday, 10 February)

Mat Scales

• [ServiceWorker] Reliable ordering of fetch event handlers (#613) (Monday, 2 February)

Mathieu Rochette

• [ServiceWorker] fix typo (#623) (Sunday, 15 February)

Matt Falkenhagen

• Re: [ServiceWorker] A header/something to kill SWs (#614) (Tuesday, 24 February)
• Re: [ServiceWorker] A header/something to kill SWs (#614) (Tuesday, 24 February)
• Re: [ServiceWorker] A header/something to kill SWs (#614) (Monday, 23 February)
• Re: [ServiceWorker] A header/something to kill SWs (#614) (Monday, 23 February)
• Re: [ServiceWorker] Passing a scope or scriptURL to register() with escaped '/' or '\ should fail (#630) (Friday, 20 February)
• [ServiceWorker] Passing a scope or scriptURL to register() with escaped '/' or '\ should fail (#630) (Friday, 20 February)
• Re: [ServiceWorker] Consider producing distinct objects for the same entity to enable garbage collection (#416) (Wednesday, 18 February)
• Re: [ServiceWorker] ServiceWorker to "service worker" mapping and stability (#622) (Wednesday, 18 February)
• Re: [ServiceWorker] ServiceWorker to "service worker" mapping and stability (#622) (Wednesday, 18 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Wednesday, 18 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Monday, 16 February)
• Re: [ServiceWorker] ServiceWorker to "service worker" mapping and stability (#622) (Saturday, 14 February)
• Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396) (Wednesday, 11 February)
• Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396) (Tuesday, 10 February)

Matthew Gaunt

• Re: [push-api] Fire pushsubscriptionchange when user revokes permission (#116) (Tuesday, 24 February)

Michael Stillwell

• [ServiceWorker] Minor edit: add "the" (#638) (Wednesday, 25 February)

Michael van Ouwerkerk

• Re: [push-api] Clean up "webapp server" terminology (#53) (Thursday, 26 February)
• Re: [push-api] Replace "webapp server" with "appplication server". (#117) (Thursday, 26 February)
• [push-api] Replace "webapp server" with "appplication server". (#117) (Thursday, 26 February)
• Re: [permissions] Is `Permissions.get` the right name? (#5) (Thursday, 26 February)
• Re: [push-api] Sequence diagram notes (#80) (Thursday, 12 February)
• Re: [push-api] Align "push client", "push server", and "push service" with protocol (#113) (Thursday, 12 February)
• Re: [push-api] Clean up push service terminology. (#114) (Thursday, 12 February)
• [push-api] Clean up push service terminology. (#114) (Thursday, 12 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Thursday, 5 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Wednesday, 4 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Wednesday, 4 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Wednesday, 4 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Wednesday, 4 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Wednesday, 4 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Wednesday, 4 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Wednesday, 4 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Wednesday, 4 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Wednesday, 4 February)
• [push-api] Align "push client", "push server", and "push service" with protocol (#113) (Wednesday, 4 February)
• [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Tuesday, 3 February)

Mike West

• Re: [ServiceWorker] Can we replace event.default() with something less magic? (#607) (Tuesday, 17 February)
• Re: [ServiceWorker] Should an IFRAME without src be controlled by SW when its parent is controlled? (#612) (Tuesday, 3 February)
• Re: [ServiceWorker] Should an IFRAME without src be controlled by SW when its parent is controlled? (#612) (Monday, 2 February)
• Re: [ServiceWorker] Should an IFRAME without src be controlled by SW when its parent is controlled? (#612) (Monday, 2 February)

Mounir Lamouri

• Re: [screen-orientation] The orientation type 'Natural' should only lock to x-primary (#83) (Monday, 23 February)
• [screen-orientation] Natural shouldn't be equivalent to *-secondary. Fixes #83 (#84) (Monday, 23 February)
• Re: [ServiceWorker] Clients & postMessage (#609) (Saturday, 21 February)
• Re: [manifest] Move to using Echidna (#315) (Wednesday, 18 February)
• [ServiceWorker] Use SyntaxError when an URL can't be parsed in Clients.openWindow() (#619) (Wednesday, 11 February)

Nikhil Marathe

• Re: [ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) (Friday, 27 February)
• Re: [ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) (Thursday, 26 February)
• Re: [ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) (Thursday, 26 February)
• Re: [ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) (Wednesday, 25 February)
• [ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) (Wednesday, 25 February)
• [ServiceWorker] When exactly during unload does "Handle Service Worker Client Unload (#636) (Tuesday, 24 February)
• Re: [ServiceWorker] ServiceWorker to "service worker" mapping and stability (#622) (Friday, 13 February)
• [ServiceWorker] ServiceWorker to "service worker" mapping and stability (#622) (Friday, 13 February)
• Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396) (Tuesday, 10 February)
• Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396) (Tuesday, 10 February)
• Re: [ServiceWorker] Correct the atomic operation section in Update; allow new worker to get installed while an active worker is still effective (5f9b752) (Saturday, 7 February)
• Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396) (Saturday, 7 February)
• Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396) (Friday, 6 February)

Norbert Lindenberg

• Re: [editing-explainer] Should sites be able to control Responsive Input Language? (#31) (Wednesday, 18 February)
• Re: [editing-explainer] Should execCommand be spec'd to do nothing in cE=typing? (#33) (Wednesday, 18 February)

Olivier Forget

• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)

Owen Campbell-Moore

• Re: [ServiceWorker] ServiceWorker's postMessage method is not defined (#479) (Saturday, 14 February)

Patrick H. Lauke

• Re: [touch-events] Repo organisation (#9) (Saturday, 21 February)
• [touch-events] Repo organisation (#9) (Saturday, 21 February)

Peter Beverloo

• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Wednesday, 4 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Wednesday, 4 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Tuesday, 3 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Tuesday, 3 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Tuesday, 3 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Tuesday, 3 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Tuesday, 3 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Tuesday, 3 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Tuesday, 3 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Tuesday, 3 February)
• Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112) (Tuesday, 3 February)

Quentin

• [permissions] Could we ask for several permissions at a time ? (#6) (Thursday, 26 February)
• Re: [permissions] A "dismissed" state (#4) (Wednesday, 25 February)
• Re: [permissions] A "dismissed" state (#4) (Tuesday, 24 February)

Radu Brehar

• [fetch] upload progress? (#21) (Friday, 20 February)

Rick Byers

• Re: [touch-events] Errata suggestions October - December 2014 (#3) (Tuesday, 17 February)
• Re: [touch-events] Errata suggestions October - December 2014 (#3) (Tuesday, 17 February)

robrbecker

• Re: [ServiceWorker] consider exposing size for cache entries (#587) (Thursday, 5 February)

Ryo Maruyama

• [streams] I can not find the copyright of the reference implementation. (#278) (Saturday, 7 February)

Ryosuke Niwa

• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [editing-explainer] How does cE=typing support IME text replacement? (#34) (Friday, 6 February)
• Re: [selection-api] Fix capitalization of GitHub (#44) (Thursday, 5 February)

Sebastian Kippe

• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• Re: [manifest] Integration with service workers (#161) (Friday, 6 February)
• Re: [manifest] Integration with service workers (#161) (Thursday, 5 February)
• Re: [manifest] Integration with service workers (#161) (Thursday, 5 February)

Sergey Konstantinov

• Re: [spec-reviews] CSS Regions (#35) (Friday, 27 February)
• [spec-reviews] CSS Regions Review Draft (#44) (Tuesday, 24 February)

Spencer Tom Tafadzwa Chirume

• Re: [ServiceWorker] Sync Application History & Cache (#425) (Tuesday, 3 February)
• Re: [ServiceWorker] Sync Application History & Cache (#425) (Tuesday, 3 February)

Tab Atkins Jr.

• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Thursday, 26 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Wednesday, 25 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Saturday, 21 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Saturday, 21 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Saturday, 21 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Saturday, 21 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Saturday, 21 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Saturday, 21 February)
• Re: [ServiceWorker] Returning a FetchPromise from fetch() (#625) (Friday, 20 February)

Takayoshi Kochi

• [webcomponents] Describe focus navigation order for the case with tabindex=-1 (#35) (Monday, 9 February)

Takeshi Yoshino

• Re: [streams] Operation stream (#287) (Saturday, 28 February)
• Re: [streams] Operation stream (#287) (Saturday, 28 February)
• Re: [streams] Operation stream (#287) (Saturday, 28 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Friday, 27 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Friday, 27 February)
• Re: [streams] New proposal for byte stream uses cases (#289) (Friday, 27 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Thursday, 26 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Thursday, 26 February)
• Re: [streams] Use angle quotes for lists (#281) (Wednesday, 25 February)
• Re: [streams] Use angle quotes for lists (#281) (Wednesday, 25 February)
• Re: [streams] Use angle quotes for lists (#281) (Wednesday, 25 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 25 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 25 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 25 February)
• Re: [streams] Operation stream (#287) (Wednesday, 25 February)
• Re: [streams] Operation stream (#287) (Wednesday, 25 February)
• Re: [streams] Operation stream (#287) (Wednesday, 25 February)
• Re: [streams] Operation stream (#287) (Wednesday, 25 February)
• Re: [streams] Operation stream (#287) (Wednesday, 25 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Tuesday, 24 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Tuesday, 24 February)
• Re: [streams] Operation stream (#287) (Tuesday, 24 February)
• Re: [streams] Operation stream (#287) (Thursday, 19 February)
• Re: [streams] Operation stream (#287) (Thursday, 19 February)
• Re: [streams] Operation stream (#287) (Thursday, 19 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Thursday, 19 February)
• [streams] Operation stream (#287) (Thursday, 19 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Thursday, 19 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 18 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 18 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 18 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 18 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Monday, 16 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Friday, 13 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Thursday, 12 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Thursday, 12 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Thursday, 12 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Wednesday, 11 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 10 February)
• [streams] Update ReadableByteStream to follow the style rule employed for the main... (#283) (Tuesday, 10 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Tuesday, 10 February)
• [streams] Add BufferFeedableReadableByteStream (#282) (Tuesday, 10 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Tuesday, 10 February)
• [streams] Use angle quotes for lists (#281) (Tuesday, 10 February)
• Re: [streams] Add readableAmount getter to ReadableByteStream (#279) (Tuesday, 10 February)
• Re: [streams] Byte stream promises update (#280) (Tuesday, 10 February)
• [streams] Byte stream promises update (#280) (Tuesday, 10 February)
• Re: [streams] Add readableAmount getter to ReadableByteStream (#279) (Tuesday, 10 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Tuesday, 10 February)
• [streams] Add readableAmount getter to ReadableByteStream (#279) (Tuesday, 10 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 10 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Tuesday, 10 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Monday, 9 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Monday, 9 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Monday, 9 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Monday, 9 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Monday, 9 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Monday, 9 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Monday, 9 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] Have each of the stream and reader hold promises (#277) (Friday, 6 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Friday, 6 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Friday, 6 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Friday, 6 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Friday, 6 February)
• Re: [streams] [WIP] Putting a chunk back in the readable stream queue (#275) (Thursday, 5 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Thursday, 5 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Thursday, 5 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Thursday, 5 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Thursday, 5 February)
• Re: [streams] Convert readable stream pull() to promise-returning (#272) (Thursday, 5 February)
• Re: [streams] Requirement on promises equality (#266) (Wednesday, 4 February)
• [streams] Have each of the stream and reader hold promises (#277) (Wednesday, 4 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 3 February)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Tuesday, 3 February)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Tuesday, 3 February)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Tuesday, 3 February)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Tuesday, 3 February)
• Re: [ServiceWorker] window.caches and window.fetch should be [Replaceable] (#535) (Tuesday, 3 February)
• Re: [ServiceWorker] window.caches and window.fetch should be [Replaceable] (#535) (Tuesday, 3 February)
• [webidl] Dead links to "consequential interface" (#43) (Tuesday, 3 February)

Tobias Buschor

• Re: [manifest] Integration with service workers (#161) (Friday, 6 February)

Tomás Aparicio

• Re: [ServiceWorker] importScripts() should throw? (#642) (Saturday, 28 February)
• Re: [ServiceWorker] A programmatic and reliable way to unregister all ports (even it's used from others tabs) (#579) (Saturday, 28 February)

Volker E.

• Re: [manifest] A means to control the color of the status bar (#225) (Sunday, 8 February)

Xabier Rodríguez

• Re: [streams] readable-stream-cancel.js "ReadableStream canceling an infinite stream" is flaky (#286) (Thursday, 19 February)
• Re: [streams] readable-stream-cancel.js "ReadableStream canceling an infinite stream" is flaky (#286) (Thursday, 19 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Thursday, 19 February)
• [streams] readable-stream-cancel.js "ReadableStream canceling an infinite stream" is flaky (#286) (Wednesday, 18 February)
• [streams] Fixed typo in readable-stream tests (#285) (Wednesday, 18 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 10 February)

yejingfu

• Re: [manifest] Add recommended width and height (#310) (Thursday, 26 February)
• Re: [manifest] Add recommended width and height (#310) (Thursday, 26 February)
• Re: [manifest] Add recommended width and height (#310) (Wednesday, 25 February)
• Re: [manifest] Add recommended width and height (#310) (Wednesday, 25 February)
• Re: [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)
• [manifest] Idea about supporting window attributes (#310) (Wednesday, 11 February)

Yutaka Hirano

• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Friday, 27 February)
• Re: [streams] New proposal for byte stream uses cases (#289) (Friday, 27 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Friday, 27 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Friday, 27 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Thursday, 26 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Thursday, 26 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Tuesday, 24 February)
• Re: [streams] Change the model for ReadableStream to have async read() (#288) (Tuesday, 24 February)
• Re: [streams] Define "tee"ing a stream (#271) (Monday, 23 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Friday, 20 February)
• Re: [streams] How will ReadableByteStream work with seekable resources? (#253) (Tuesday, 17 February)
• Re: [streams] Add IsReadableStreamLocked abstract operation (#259) (Monday, 9 February)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Thursday, 5 February)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Wednesday, 4 February)
• Re: [streams] Requirement on promises equality (#266) (Wednesday, 4 February)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Tuesday, 3 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 3 February)
• Re: [streams] Requirement on promises equality (#266) (Tuesday, 3 February)

Yves Lafon

• Re: [packaging-on-the-web] Icon container as use case (#22) (Monday, 9 February)
• Re: [packaging-on-the-web] Vary header use (#16) (Monday, 9 February)
• Re: [packaging-on-the-web] When is the SPF stream finished? Is Content-Length enough? (#18) (Monday, 9 February)
• Re: [packaging-on-the-web] Is it safe to deploy over plain-text HTTP? (#19) (Monday, 9 February)
• Re: [packaging-on-the-web] Is it safe to deploy over plain-text HTTP? (#19) (Monday, 9 February)
• Re: [packaging-on-the-web] Streaming Packaging Format (#12) (Monday, 9 February)
• Re: [packaging-on-the-web] fixing typo (#20) (Monday, 9 February)
• Re: [echidna] Generate unique id to identify the job (#60) (Friday, 6 February)

ZhuoyuQian

• Re: [ServiceWorker] Rename clients.getAll() (#610) (Friday, 13 February)

Last message date: Saturday, 28 February 2015 19:05:38 UTC