Create F2F agenda - 16 September 2019

[mfalken]

Where

Location: TPAC, Fukuoka, Japan
When: 9 AM, 16 September 2019
IRC: #serviceworker on irc.w3.org.

Shared doc

• https://docs.google.com/document/d/1q090ovJ4gd8wSfVtvuoZLMZ51YkiFDsEZ0Jiqi41Iys/edit?usp=sharing

Attendance

Please register at the TPAC registration page. Members can access the registration list.

Agenda

HELLO EVERYONE

Find out who everyone is and why.

Implementer update

Share implementation recent progress, priorities, plans, problems, etc.

CFAM (that's "Call for agenda modification". I'm making it a thing – Jake)

• Anything folks want to cover that isn't part of the agenda?
• Any items that should be done at a certain time, or depend on particular people?

Interesting new feature requests

• Support efficient offline redirects: support efficient offline redirects #1457 - Need Anne
• A way to specify a pattern of destination URLs to hit/skip SW A way to specify a pattern of destination URLs to hit/skip SW #1454 - Need N8, Anne
  • Related Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime #1195, Consider mechanisms to bypass the service worker for things that we know won't be in it's cache #1026
• Scope Pattern Matching scope pattern matching #1468 - Need Anne
• DONE Client lifecycle with bfcache, frozen tabs
  • Add an option to include frozen documents. Add an option to include frozen documents. #1442
  • Consider how Client API should behave with bfcache: consider how Client API should behave with bfcache #1038.
  • Related How are unloaded tabs represented? #626
• bg fetch & bg sync privacy stuff
• (Heads up): Periodic Background Sync https://github.com/beverloo/periodic-background-sync
• (Heads up): Content Index https://github.com/rknoll/content-index
• (Heads up): Launch event https://github.com/WICG/sw-launch/blob/master/explainer.md
• (Update): Declarative routes Declarative routing #1373 (comment)
  • Needs implementer interest
  • What next? Would a polyfill or spec help?
• SW lifetime:
  • A way to immediately unregister a service worker A way to immediately unregister a service worker #614
  • Allow active worker to immediately evict itself Allow active worker to immediately evict itself #1296
  • Clear-Site-Data problems?
• Spec/design notes for double-keyed service workers
  • What do browsers do/plan to do
  • Should there be spec changes and how. Tests?
  • Proposal: Storage Access API whatwg/html#3338 is the only thing I can find. So it feels too early for us to do anything – Jake
• Top-level await integration for ServiceWorkers running modules Top-level await integration for ServiceWorkers running modules #1407
• Fetch streaming upload: Uploading a Request made from a ReadableStream body whatwg/fetch#425
  • New interest from Chrome
  • But not bi-directional (getting response object will be gated on request end)
  • Is that a step in the right direction? If we do the full thing later, it's kinda difficult to feature detect.
• Registering service workers for unique origins? Registering service workers for unique origins? #1437
• provide a way to execute work after browser has consumed a response provide a way to execute work after browser has consumed a response #1397
• Linking data to a service worker Add a script version property to the ServiceWorker object #1387
• Expose display mode (e.g. standalone) on client Expose display mode (e.g. standalone) on client #1370
• Replay POST requests (add request to IDB) Replaying POST requests #693
• Do we want to do something about the single tab 'refresh' case? Provide a way to skipWaiting when the last tab refreshes #1238

V1 & W3C living spec

• Double check everyone is happy with v1 going to CR.
  • Do we stop updating v1 now?
• Rechartering, and which specs we bring in.
  • Background sync (including periodic).
  • Background fetch.
  • Where should cache go?
• How will "living standard" work going forward, and are we happy with it?

Plh will be around 14:30 to chat about this.

Changes & bugs

Feel free to add to this list.

• "no-cors" CSS SOP violation "no-cors" CSS SOP violation #719
• spec says cache should return responses with immutable headers, but no browser does that spec says cache should return responses with immutable headers, but no browser does that #1456
• Add registeringClientId to the ServiceWorker object Add registeringClientId to the ServiceWorker object #1379
• Clarification on what happens during a terminated activation Clarification on what happens during a terminated activation #1372
• Update order of service worker properties Should the worker be removed from the registration *before* its state is set to "redundant"? #1273 (comment)
• Should the order of registrations returned by getRegistrations() be sorted by scope? Should the order of registrations returned by getRegistrations() be sorted by scope? #1465
• Issue with progress and uploads Service Worker makes AJAX Progress Listener not Working #1141
• Status update for Sort out settings object for service worker module scripts #1013
• Set request origin in update Request's origin needs to be set for [[Update]] algorithm #1447
• Calling update when there's an installing worker Should update() always reject if there is an installing worker? #1429

Dinner

Unfortunately, dinner registration is closed. If you registered (see below list), here are the details:

• Location: Yohira (https://goo.gl/maps/aNyJhFui45FJVKBj6)
• Time: 7pm
• Registered people: acomminos, asa.kusuma, asuth, bashi, beverloo, dharani, dom, domenic, dpc, falken, hayato, jakearchibald, jungkee.song, mek, n8s, nhiroki, rayankanso, shimazu, (slightlyoff), stevebe, tsteiner, wanderview, yhirano, youenn, yutakasai

It's a 30-45 min walk (3 km) from the hotel or 10 minute taxi. Meet at 6:30 at the hotel front lobby (4F) if you want to taxi over.

[wanderview]

I'm working on a proposal giving sites more control over how scopes match that I'd like to discuss. I'm hoping to post as an issue later this week or early next week.

[asakusuma]

Thanks for putting this together @mattto. Regarding the SW Lifetime item, another possible sub-item would be the "abortable algorithms" proposal #1443 (cc @jakearchibald). That proposal may be part of the puzzle to landing an algorithm for killing a service worker #1440, which would also be a good sub-item for the SW Lifetime discussion.

[mfalken]

Thanks, @wanderview and @asakusuma. Incorporated into the issue.

[mfalken]

Would people be interested in a group dinner after the meeting? If you're interested in joining, can you thumbs up this? EDIT: please fill out this form: https://forms.gle/wcGRxDtsBwQokRRS9

[wanderview]

FYI, I've filed #1468 with my service worker scope proposal.

[mfalken]

I made a dinner reservation at a nearby place for after the meeting. It will be a course meal of recommended seasonal food (kaiseki). If you want to attend, please fill out this form by Thursday, Sept 12 at 5pm (in your timezone): https://forms.gle/wcGRxDtsBwQokRRS9

I'll have to confirm the number of people by then. Thanks!

[mfalken]

Final reminder for dinner: If you want to attend, please fill out the form asap!

EDIT: The form is closed. If you want to make a change, please contact falken@chromium.org.

The following people are registered: acomminos, asa.kusuma, asuth, bashi, beverloo, dharani, dom, domenic, dpc, falken, hayato, jakearchibald, jungkee.song, kenjibaheux, mek, n8s, nhiroki, shimazu, slightlyoff, tsteiner, wanderview, yhirano, youenn, yutakasai

[yutakahirano]

Can we talk about fetch streaming upload (whatwg/fetch#425)?

[mfalken]

@yutakahirano: Added it to the agenda.

[jakearchibald]

Note we're now starting at 9am rather than 8:30am, because we're not monsters.