public-webapps-github@w3.org from November 2014 by author

Anne van Kesteren

• Re: [ServiceWorker] Merge service worker client into "environment settings object" (#516) (Thursday, 27 November)
• Re: [ServiceWorker] Merge service worker client into "environment settings object" (#516) (Thursday, 27 November)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Thursday, 27 November)
• Re: [ServiceWorker] Merge service worker client into "environment settings object" (#516) (Thursday, 27 November)
• Re: [ServiceWorker] Merge service worker client into "environment settings object" (#516) (Wednesday, 26 November)
• Re: [ServiceWorker] 304 handling for fetch() (#412) (Tuesday, 25 November)
• Re: [ServiceWorker] What should happen when we call response.text() and response.clone()? (#568) (Tuesday, 25 November)
• Re: [ServiceWorker] What should happen when we call response.text() and response.clone()? (#568) (Tuesday, 25 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Tuesday, 25 November)
• Re: [ServiceWorker] 304 handling for fetch() (#412) (Monday, 24 November)

Ben Kelly

• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Sunday, 30 November)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Saturday, 29 November)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Saturday, 29 November)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Friday, 28 November)
• Re: [ServiceWorker] Make it clear that Cache and caches are to be available on page (#297) (Wednesday, 26 November)
• Re: [ServiceWorker] Batch Cache Operations does not use QueryCache correctly after #545 (#565) (Wednesday, 26 November)
• Re: [ServiceWorker] Batch Cache Operations does not use QueryCache correctly after #545 (#565) (Wednesday, 26 November)
• Re: [ServiceWorker] What should happen when we call response.text() and response.clone()? (#568) (Tuesday, 25 November)

Craig Francis

• Re: [manifest] Cookies and data collection policies (#281) (Wednesday, 26 November)
• [manifest] Cookies and data collection policies (#281) (Wednesday, 26 November)

Domenic Denicola

• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Sunday, 30 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Saturday, 29 November)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Saturday, 29 November)
• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Thursday, 27 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Wednesday, 26 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Wednesday, 26 November)
• [streams] Make .ready fulfill-only (#248) (Wednesday, 26 November)
• Re: [streams] Remove special handling for empty queue case in SyncWritableStreamStateW... (#247) (Wednesday, 26 November)
• Re: [streams] Remove special handling for empty queue case in SyncWritableStreamStateW... (#247) (Wednesday, 26 November)
• Re: [streams] Make .ready fulfill-only? (#245) (Wednesday, 26 November)
• Re: [streams] Allow filing an issue from the spec directly (#222) (Wednesday, 26 November)
• Re: [streams] Initial state of WritableStream (#242) (Tuesday, 25 November)
• Re: [streams] Initial state of WritableStream (#242) (Tuesday, 25 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Tuesday, 25 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Tuesday, 25 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Tuesday, 25 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Tuesday, 25 November)
• Re: [streams] Rename .wait() to .ready step 2 (#246) (Tuesday, 25 November)
• Re: [streams] Rename .wait() to .ready step 2 (#246) (Tuesday, 25 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Monday, 24 November)
• [streams] Make .ready fulfill-only? (#245) (Monday, 24 November)
• Re: [streams] Move from .wait() to .ready (#243) (Monday, 24 November)
• Re: [streams] Move from .wait() to .ready (#243) (Monday, 24 November)
• Re: [webidl] Make the DOMException constructor accept a name (#22) (Monday, 24 November)

Honza Bambas

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

Jake Archibald

• Re: [ServiceWorker] Allowing multiple scopes (& should scopes be primary key?) (#566) (Wednesday, 26 November)

John Mellor

• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Wednesday, 26 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Wednesday, 26 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Wednesday, 26 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Wednesday, 26 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Wednesday, 26 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Wednesday, 26 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Monday, 24 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Monday, 24 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Monday, 24 November)

Jungkee Song

• Re: [ServiceWorker] Controlling documents (#475) (Friday, 28 November)
• Re: [ServiceWorker] Controlling documents (#475) (Friday, 28 November)
• Re: [ServiceWorker] ServiceWorkerGlobalScope and service worker (#485) (Friday, 28 November)
• Re: [ServiceWorker] ServiceWorkerGlobalScope and service worker (#485) (Friday, 28 November)
• Re: [ServiceWorker] Worker navigator.serviceWorker and serviceWorkerGlobal.registration (#562) (Friday, 28 November)
• Re: [ServiceWorker] Worker navigator.serviceWorker and serviceWorkerGlobal.registration (#562) (Friday, 28 November)
• Re: [ServiceWorker] Expose ServiceWorkerContainer to Worker; Define service worker client as an environment settings object; Adding registration as a global; Moving .update() onto the registration object (ed665ba) (Friday, 28 November)
• Re: [ServiceWorker] Changing ServiceWorkerClient.hidden to visibilityState (#498) (Friday, 28 November)
• Re: [ServiceWorker] Merge service worker client into "environment settings object" (#516) (Thursday, 27 November)
• Re: [ServiceWorker] Merge service worker client into "environment settings object" (#516) (Thursday, 27 November)
• Re: [ServiceWorker] Merge service worker client into "environment settings object" (#516) (Thursday, 27 November)
• Re: [ServiceWorker] Should skipWaiting() wait for an "in-progress request" to finish? (#569) (Thursday, 27 November)
• Re: [ServiceWorker] Should skipWaiting() wait for an "in-progress request" to finish? (#569) (Thursday, 27 November)
• Re: [ServiceWorker] Changing ServiceWorkerClient.hidden to visibilityState (#498) (Thursday, 27 November)
• Re: [ServiceWorker] Merge service worker client into "environment settings object" (#516) (Thursday, 27 November)
• Re: [ServiceWorker] Spec'ing the "secure origin" restriction (#385) (Wednesday, 26 November)
• Re: [ServiceWorker] Spec'ing the "secure origin" restriction (#385) (Wednesday, 26 November)
• Re: [ServiceWorker] Merge service worker client into "environment settings object" (#516) (Wednesday, 26 November)
• Re: [ServiceWorker] IDL: Define Promise type for ServiceWorkerClient's ready attribute (#563) (Wednesday, 26 November)
• Re: [ServiceWorker] IDL: Define Promise type for ServiceWorkerClient's ready attribute (#563) (Wednesday, 26 November)
• Re: [ServiceWorker] Batch Cache Operations does not use QueryCache correctly after #545 (#565) (Wednesday, 26 November)
• Re: [ServiceWorker] FetchEvent.respondWith() should check the used flag of the response (#567) (Wednesday, 26 November)

Kenji Baheux

• Re: [ServiceWorker] Changing ServiceWorkerClient.hidden to visibilityState (#498) (Friday, 28 November)
• Re: [ServiceWorker] Multi-author sites (#468) (Wednesday, 26 November)

Kenneth Rohde Christiansen

• Re: [manifest] Manifest icon's 'type' should be a valid IMAGE mime type, not a valid mime type (#287) (Thursday, 27 November)
• Re: [manifest] Issue a developer warning if density is present but invalid. (#285) (Thursday, 27 November)
• Re: [manifest] Issue a developer warning if the display mode is not a known value. (#286) (Thursday, 27 November)
• Re: [manifest] Unknown display value should produce a developer warning (#283) (Thursday, 27 November)

Kunihiko Sakamoto

• Re: [ServiceWorker] Changing ServiceWorkerClient.hidden to visibilityState (#498) (Wednesday, 26 November)

Marcos Caceres

• [permissions] A "dismissed" state (#4) (Friday, 28 November)
• [permissions] Permission states (#3) (Friday, 28 November)
• [permissions] Redundant assertion (#2) (Friday, 28 November)
• Re: [manifest] Unknown display value should produce a developer warning (#283) (Thursday, 27 November)
• Re: [manifest] Unknown display value should produce a developer warning (#283) (Thursday, 27 November)
• Re: [manifest] Manifest icon's 'type' should be a valid IMAGE mime type, not a valid mime type (#287) (Thursday, 27 November)
• Re: [manifest] Manifest icon's 'type' should be a valid IMAGE mime type, not a valid mime type (#287) (Thursday, 27 November)
• Re: [permissions] Add link to Moz's bugzilla bug to track this (#1) (Thursday, 27 November)
• [permissions] Add link to Moz's bugzilla bug to track this (#1) (Thursday, 27 November)
• Re: [webidl] Grammar issues (#29) (Wednesday, 26 November)
• Re: [manifest] Cookies and data collection policies (#281) (Wednesday, 26 November)
• Re: [manifest] HTTP-based solution for loading manifests (#98) (Monday, 24 November)
• Re: [manifest] HTTP-based solution for loading manifests (#98) (Monday, 24 November)
• Re: [manifest] Capability to check already installed web app (#280) (Monday, 24 November)
• Re: [manifest] Capability to check already installed web app (#280) (Monday, 24 November)
• Re: [manifest] Capability to check already installed web app (#280) (Monday, 24 November)

Mark Nottingham

• Re: [ServiceWorker] 304 handling for fetch() (#412) (Tuesday, 25 November)
• Re: [manifest] HTTP-based solution for loading manifests (#98) (Tuesday, 25 November)
• Re: [ServiceWorker] 304 handling for fetch() (#412) (Tuesday, 25 November)

Martin Thomson

• Re: [push-api] Add and Encryption Key array to the PushRegistration interface (#89) (Tuesday, 25 November)
• Re: [push-api] Add and Encryption Key array to the PushRegistration interface (#89) (Tuesday, 25 November)

Matt Falkenhagen

• Re: [ServiceWorker] Should skipWaiting() wait for an "in-progress request" to finish? (#569) (Friday, 28 November)
• Re: [ServiceWorker] Should skipWaiting() wait for an "in-progress request" to finish? (#569) (Thursday, 27 November)
• Re: [ServiceWorker] Should skipWaiting() wait for an "in-progress request" to finish? (#569) (Thursday, 27 November)
• [ServiceWorker] Should skipWaiting() wait for an "in-progress request" to finish? (#569) (Thursday, 27 November)

Matthew Gaunt

• Re: [manifest] Expose the display mode in Javascript (#273) (Wednesday, 26 November)

Michael van Ouwerkerk

• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Wednesday, 26 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Wednesday, 26 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Tuesday, 25 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Tuesday, 25 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Tuesday, 25 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Tuesday, 25 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Tuesday, 25 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Tuesday, 25 November)

Mike West

• Re: [ServiceWorker] Spec'ing the "secure origin" restriction (#385) (Tuesday, 25 November)

Mikeal Rogers

• Re: [streams] Should we "lock" readable streams while piping? (#241) (Tuesday, 25 November)

Mounir Lamouri

• [manifest] Manifest icon's 'type' should be a valid IMAGE mime type, not a valid mime type (#287) (Thursday, 27 November)
• [manifest] Issue a developer warning if the display mode is not a known value. (#286) (Thursday, 27 November)
• Re: [manifest] Issue a developer warning if density is present but invalid. (#285) (Thursday, 27 November)
• [manifest] Issue a developer warning if density is present but invalid. (#285) (Thursday, 27 November)
• Re: [manifest] Explicitely use https for respec link. (#284) (Thursday, 27 November)
• [manifest] Explicitely use https for respec link. (#284) (Thursday, 27 November)
• [manifest] Unknown display value should produce a developer warning (#283) (Thursday, 27 November)
• [manifest] Icon density parsing should have a developer warning (#282) (Thursday, 27 November)
• Re: [manifest] Expose the display mode in Javascript (#273) (Wednesday, 26 November)

Peter Beverloo

• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Monday, 24 November)
• Re: [push-api] Make PushEvent's data payload binary instead of just a string (#88) (Monday, 24 November)

Philip Jägenstedt

• Re: [dom] Link Element.setAttributeNodeNS() to the correct definition (#13) (Tuesday, 25 November)

rainerschuster

• Re: [webidl] Grammar issues (#29) (Wednesday, 26 November)
• [webidl] Update index.xml (#32) (Wednesday, 26 November)
• [webidl] Update index.xml (#31) (Wednesday, 26 November)
• [webidl] Update index.xml (#30) (Wednesday, 26 November)
• [webidl] Grammar issues (#29) (Wednesday, 26 November)

ShijunS

• Re: [push-api] Add and Encryption Key array to the PushRegistration interface (#89) (Monday, 24 November)

Takeshi Yoshino

• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Thursday, 27 November)
• Re: [streams] Make initial state of writable stream consult the strategy (06a0302) (Wednesday, 26 November)
• [streams] Remove special handling for empty queue case in SyncWritableStreamStateW... (#247) (Wednesday, 26 November)
• Re: [streams] Make .ready fulfill-only? (#245) (Wednesday, 26 November)
• Re: [streams] Make .ready fulfill-only? (#245) (Wednesday, 26 November)
• [streams] Rename .wait() to .ready step 2 (#246) (Tuesday, 25 November)
• Re: [streams] Rename .wait() to .ready (6eb872b) (Tuesday, 25 November)

Tsuyoshi Horo

• [ServiceWorker] What should happen when we call response.text() and response.clone()? (#568) (Tuesday, 25 November)
• [ServiceWorker] FetchEvent.respondWith() should check the used flag of the response (#567) (Tuesday, 25 November)

Yutaka Hirano

• Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452) (Friday, 28 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Friday, 28 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Friday, 28 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Wednesday, 26 November)
• Re: [streams] Should we "lock" readable streams while piping? (#241) (Tuesday, 25 November)

Last message date: Sunday, 30 November 2014 14:41:19 UTC