Create F2F agenda

[jakearchibald]

I'll convert this to a wiki page once we have something more concrete, but an issue seems easier for discussion.

Things I'd like to cover (in priority order)

• Outstanding V1 issues, as we did in Sapporo, but hopefully won't take as long
• Cache API enhancements (since we're likely to have @wanderview around), especially transactions & making addAll more useful
• Foreign fetch
• Navigation handling (how to launch as-homescreen from openWindow & native apps, and how to manage "single" vs "multi" window sessions)

Agenda

• V1 issues (see below)
• Cache transactions & saving cache.addAll
• Foreign fetch
• A header-based installation
• Who's hosting the next meeting & when?

V1 Issues need discussion

• should subresource FetchEvents trigger an update if 24-hours since last check? #814
• Should mixed content always be blocked? #813
• What is FetchEvent.clientId for navigation requests #808
• should update() during top level script evaluation be ignored? #800
• should update on navigation or the subsequent updatefound event be delayed until document DOM is loaded? #788
• what should the document base URI for an intercepted navigation #787
• Race when registering multiple service workers for the same scope #783
• Allow waitUntil to be called multiple times, async #771
• passthrough service worker can break sites using redirected stylesheets #757
• Make the Cache API deal with request's redirect mode not being "follow" #737
• When does the openWindow promise resolve? #728
• Proposal: Optimized No-Fetch Service Workers #718
• How to deal with cookie bombing #704
• Receivers of ranged responses must ensure all ranges come from the same underlying resource #703
• Restrict openWindow() to http(s) schemes? #699
• Define the lifetime of a blob URL created inside a service worker #688
• Client.postMessage should return a Promise #677
• Issues deferring to [SecureContext] IDL proposal (Add a [SecureContext] operator attribute whatwg/webidl#65)
  • ServiceWorkerContainer.controller prose says to return undefined, but the IDL doesn't allow that #769
  • Make secure context requirements more explicit #754
  • self.caches should spec what to do for "untrusted" origins #687

Attendees:

• Ali Alabbas (Microsoft)
• Jake Archibald (Google)
• Ilya Grigorik (Google)
• Conrad Irwin
• Anne van Kesteren (Mozilla)
• Marijn Kruisselbrink (Google)
• Jatinder Mann (Microsoft)
• Edward O'Connor (Apple) - unconfirmed
• Alex Russell (Google)
• Jungkee Song (Samsung)
• Kinuko Yasuda (Google)

We'll also post updates to #serviceworker on freenode, for anyone wanting to follow along remotely.

[annevk]

Perhaps @jungkees could round up the v1 issues he thinks need discussing so we can have a go at the simpler ones now.

[jakearchibald]

I'm up for that. Eat our greens ahead of the meeting so we can concentrate on the fun stuff. I'll also put together a rough proposal for the cache API stuff, so we're starting from somewhere.

[wanderview]

I would like to review the recent changes to the lifecycle job queue stuff. In particular, I'd like to walk through some test cases and get agreement on what should actually happen. I'll try to send the list of tests in advance so people can look at them.

[wanderview]

Also, I'd like to make sure we answer the base URI question in #787.

[jungkees]

Perhaps @jungkees could round up the v1 issues he thinks need discussing so we can have a go at the simpler ones now.

Alright. Good idea. I'll do so although most of the remaining V1 issues here seem not trivial.

[jungkees]

I added "V1 Issues need discussion" in the OP. Those are basically the issues that I don't have any concrete answer yet. I may add a few more but other issues not listed are just in my TODO.

Hope we can tackle as many issues as we can here so we can spend more time on non-V1 issues this time.

[wanderview]

Might be a low priority at this point, but there are some questions about allowing some mixed content in #813.

[mfalken]

I added "V1 Issues need discussion" in the OP.

Where is this list?

[jungkees]

I noticed the list that I added in the OP has gone. I'll add it again with some more updates.

[jungkees]

I updated the OP with the list of V1 issues to discuss. Some of them may be easy ones that one can answer. If so, please give comments.

@annevk, here are two more issues that I want to discuss with you:

• Should the active worker move to environment settings object? #811
  • A common definition for the client concept seems needed for sw and fetch
  • Fetch may need a target client internal slot on a request? (for a navigation)
• matchAll() runs Request constructor off the main thread #672 (Algorithm review for the part)