Create F2F agenda - 3-4 April 2017

[jakearchibald]

Location

Facebook
Ark Hills
Sengokuyama Mori Tower, 30F
1-9-10 Roppongi,
Minato-ku, Tokyo 106-0032

Map: https://goo.gl/maps/CmhEgvmPM3o

Note that there is an old Ark Hills and new Ark Hills in the Roppongi area. Facebook's Tokyo office is at the new Ark Hills. To make sure your cab driver drives you to the correct Ark Hills, please mention "the one next to the Swedish embassy".

Show this to the cab driver if they look confused:
東京都港区六本木1-9-10
アークヒルズ仙石山森タワー
(スウェーデン大使館の隣です。)

Expected attendees

• Facebook: Nathan Schloss, Pieter Vanderwerff.
• Mozilla: Andrew Sutherland, Catalin Badea, Ben Kelly, Szmozsánszky István (Flaki), Salvador de la Puente González.
• Microsoft: Ali Alabbas, Jatinder Mann.
• Apple: Brady Eidson, Theresa O'Connor.
• Google: Jake Archibald, Alex Russell, Surma, Takeshi Yoshino, Tsuyoshi Horo, Kenji Baheux, Matt Falkenhagen, Marijn Kruisselbrink, Kinuko Yasuda, Makoto Shimazu, Yutaka Hirano, Domenic Denicola, Yi Xu.
• Samsung: Jungkee Song.
• W3C: Yves Lafon, Michael[tm] Smith.
• Yandex: Chaals McCathie Nevile

Minutes

• Day 1
• Day 2

Agenda

Starting 9am.

Intros

• Update from the browser vendors & Facebook. What they've been doing in the past 6 months & what the next priorities are.

Then, the plan is to tackle V1 stuff in the mornings, then V2 stuff in the afternoon.

The following is in no particular order, and I may cut it down a bit.

V1

Security & privacy

#1094 Should we implement MIX passthrough
#1075 Track ancestorOrigins privacy issues
#1033 Why are only a subset of JS mime types allowed?
#719 "no-cors" CSS SOP violation

Clients API

#1093 consider how clients.claim() should work with srcdoc iframes
#1091 consider Client behavior for windows where initial about:blank is replaced with a loaded document
#1090 should clients.claim() control reserved Clients?
#1080 clarify Clients.matchAll() focus order for nested frames
#1078 clarify that Client "creation order" means when reserved Client created
#1038 consider how Client API should behave with bfcache
#1035 postMessage() to a reserved client throws
#1034 what should Client.url return for a reserved Worker Client?
#1031 reserved Client objects and redirected navigations
#1030 Client.reserved references wrong context state?

Spec fixing

• #1073 Update to reference HTML for link rel=serviceworker
• #1063 Handle UA shutdown algorithm always invokes clear reg if we have installing worker
• #1055 respondWith uses the wrong targetRealm
• #1046 service worker client definition is redundant
• #1045 "if client is an environment" is always true
• #1013 Sort out settings object for service worker module scripts
• #1011 .ready promise should be resolved after updating registration.state properties
• #951 Handle Fetch creates JavaScript objects too early (and other feedback)
• #829 Resolve Job Promise can resolve jobs with an incorrect value

Lifecycle

#1040 clarify that manually constructed ExtendableEvent objects may not extend lifetime via waitUntil() - granting time
#980 postMessage keeps service workers alive indefinitely

#893 consider fetching service worker scripts with no-cache by default
#839 importScript no-cache by default

• #777 spec behavior when ServiceWorkerContainer parent client is dead
• #1021 When should "imported scripts updated flag" be unset?
• #1004 Behavior of the onfetch setter regarding no-fetch service workers & Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd whatwg/dom#371

Misc

Fix or drop appcache
#882 ServiceWorker lifetime and respondWith() with a user-constructed ReadableStream
#1087 Safety versus simplicity in specification tests

• #991 should Cache API Vary matching use combined header values?
• #952 Handle Fetch "shift+reload"
• #947 Should EventSource and WebSocket be exposed in service workers?
• #875 should FetchEvent.request.cache reflect non-fetch browser cache controls?

V2

Foreign fetch

#878 Foreign fetch vs non-credentialed requests
#1024 consider allowing static routing only for "foreign fetch" for anonymous requests
#1092 Is there any way for a web page to see if their requests will be intercepted by a foreign fetch handler?
#1085 Allow overlapping scopes
#1017 clientId on ForeignFetchEvents
#982 registerForeignFetch({ origins, scope }) optional
#979 Define procedure to convert options object of sw.register() to Link header
#910 Expose fragments cross-origin for subresources
#899 Foreign fetch and no-referrer Referrer Policy
#880 CORS pre-flight for foreign fetch
#825 Installing a foreign SW as part of a subresource request
"Nav" preload for Foreign Fetch

Fetch & streams

Setting mode whatwg/fetch#492
#1026 Consider mechanisms to bypass the service worker for things that we know won't be in it's cache
Upload streams
Transferrable streams
Fetch cancellation/control/observing - brief overview & next steps

• Background fetch - brief overview and initial feedback

SW object enhancements

#1077 Find a way for service workers to get their current state
#1076 Service worker ID - remove?
#1016 serviceworker.skipWaiting
#842 consider exposing install time on ServiceWorker DOM object

Cache API

• #1066 Pagination in cache.keys()
• #977 Allow Caching of POST requests
• #823 Cache transactions & fixing addAll

Clients

• #955 consider exposing self.clients on window and other worker globals
• #1036 Support returning ServiceWorker Client environments from Clients.matchAll()
• #1037 Clients.matchAll() should exclude the current environment
• #886 consider firing a "clientcontrolled" event on ServiceWorkerGlobalScope
• Updating title & favicon of a window client

Nav preload

#920 Making a concurrent request for navigations
#1000 NavigationPreloadManager.setHeaderValue should reject invalid HTTP header field values

Storage eviction

• #611 Hints in beforeevicted to let the SW of a web app pick among several house cleaning options?
• #971 Handle the quota exceeded error globally

Dealing with fetch failures & tab crashes

#939 Recovering from fetch failures
#877 Reporting URL for SW update failures

JS Modules

• #908 Auto-cache imported scripts
• #849 Spec uses incorrect settings object when fetching a module worker

Misc

#614 A way to immediately unregister a service worker
#756 consider allowing multiple worker thread instances for a single registration

• #1028 Consider providing navigation event
• #962 allow service worker produced resources to be marked as "cachable"
• #975 Using BroadcastChannel to wake up a service worker - also what's happening with shared worker?
• #913 cache.match should create partial responses if given a range request
  Handling Partial Content / 206 whatwg/fetch#144
• #798 Add ServiceWorker.prototype.registration
• #770 registration.ready promise
• #707 Add cookie accessor/setter methods?
• Content indexing API?
• What's happening with shared worker?

[jakearchibald]

Let me know here or via email if you expect to attend.

[mkruisselbrink]

I'm also tentatively planning to attend (although I guess we'll likely have plenty of google presence already anyway).

[mfalken]

I'll be there.

[KenjiBaheux]

I should be there as well.

…

On Wed, Jan 11, 2017 at 10:24 AM Matt Falkenhagen ***@***.***> wrote: I'll be there. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1053 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGD3CqQBrh7e4flFxv_HM-Xni-8MGdhdks5rRC9AgaJpZM4LfkCE> .

[horo-t]

I'll be there too.

[delapuente]

I'll be there also.

[hober]

Apple: @beidson and @hober

[n8schloss]

@pieterv will be attending from Facebook as well

[jakearchibald]

If anyone is worried about travel due to recent events, feel free to reach out. I don't have a grand plan, but if there's anything I can do, let me know - [email protected]

[ylafon]

I'll be there

[kinu]

I plan to be there too!

[chaals]

I'll be there…

[n8schloss]

Hey everyone,

If you're attending the meeting please fill out https://www.surveymonkey.com/r/6NLCJ9G asap.

We (Facebook) are planning on providing lunch both days of the meeting and are planning taking everyone out to dinner on the first day (April 3th). We need a headcount for the dinner and even if you're not coming to the dinner please fill out the survey so we can get your email address registered in our visitor system.

Thanks, I can't wait to see you all!

[yutakahirano]

I'll be there.

[n8schloss]

We're still missing 6 responses to https://www.surveymonkey.com/r/6NLCJ9G, if you're planning on coming please fill out the survey asap!

[makotoshimazu]

I'll be there.

[jakearchibald]

If you're expecting to attend & your name isn't in the list at the top of the page, speak up! We're using the list to ensure everyone can get into the building & we have space etc.

[annevk]

Topic suggestion: whatwg/html#151.

[isonmad]

Re: fetch & streams: trying to make a stream (e.g.) downloadable using service workers isn't very ergonomic.

And for transferable streams, there's the discussions in whatwg/streams#623 (comment) and whatwg/streams#629

[jakearchibald]

I've updated the original post with issues we can look at. We're going to start at 9am - looking forward to it!

[mfalken]

Meeting notes are being taken in #serviceworker on freenode.

[jakearchibald]

F2F: background SW (push, notification, sync, bg fetch) vs foreground SW (fetch, postMessage) - MS & Apple want this for service workers to exist when the browser is closed. Should we spec this? Fetches for notification icons go through the background SW in Edge, since there isn't a foreground SW.

What happens to the clients API? How do we represent multiple instances.

Facebook global state case:

• Notification click
• Post to client "navigate"
• Client navigates (may be real nav, or pushstate)
• Client posts back to SW, please focus me

How does the client message the correct service worker?

Edge can work around this by still ensuring there's only one SW at a time. Either using the bg SW, or fg SW.

We need to think more about use cases that require speaking to a particular SW, or otherwise depend on global state.

[NekR]

Fetches for notification icons go through the background SW in Edge, since there isn't a foreground SW.

What about notification happening when where is already foreground SW (i.e. webpage is opened)? Also, what about fetches originated from push event to synchronize additional data?

[jakearchibald]

Next meeting:

• Teleconferences in the mean time
• Monthly heartbeat VC to catch up
• Potential F2F in August (CSS are in Paris 1st week, so maybe Europe?)
• F2F in November TPAC