Virtual calls around TPAC time

[jakearchibald]

I'd like to set up some calls to cover particular topics around TPAC time. I'll take a look through the issues and propose topics, but if there's a particular issue you'd like to bring up, please let me know.

@youennf, it feels like we should chat about background fetch and try to come to a consensus there.

@annevk @wanderview @asutherland @asakusuma @mfalken @yutakahirano @youennf @jungkees anything spring to mind?

20-21 Oct, 2020 14:00-16:00 UTC

See the TPAC group meeting schedule for your schedule management.

Meeting notes

Meetings are done! Thank you for your participation. Sorry that we couldn't cover all the topics in the agenda. See the meeting notes.

Agenda

20 Oct (Tue)

• Progress updates - A round-table of what we're up to service worker-wise, and what bandwidth/hunger we have for additional features.
  • Finding out current thinking from Mozilla and Apple on implementing navigation preload. The single most important performance win for service workers heard from devs.
• Declarative routing: Declarative routing #1373 (comment)
• Clear-Site-Data: Define Purge Service Worker Registrations #1506
• Background activity and privacy - Resolving the issues @youennf posted around background fetch, which may have implications for push notifications.

21 Oct (Wed)

• Cache metadata - Proposal.
• Client lifecycle with bfcache, frozen tabs - Revisit and close on the frozen document discussion: Add an option to include frozen documents., consider how client API should behave with bfcache, How are unloaded tabs represented?
• Testing to exit CR and recharter
• Service workers on opaque origins - Discuss VS Code's use case on Registering Service Workers for unique origins?
• The timing of header setting in fetch - Sometimes headers are set pretty late, is this something we should/could change?

Not covered

• Fix worker timing - Right now it isn't well described, can we salvage it?
• Determine expected parameter values in Navigation + Resource Timing APIs for responses that have been synthesized using a Service Worker: What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? navigation-timing#124
• Ye old CSS CORS issue - "no-cors" CSS SOP violation #719
• The proposal for ServiceWorkerRegistration.id in consider allowing a non-scope identifier for registrations #1512. There is a bit of contention on the issue. @wanderview would like to hear wider input to try to resolve things.
• whether cross-origin-isolated value can be platform dependent or not - Set correct embedder policy and cross-origin isolation mode  #1545

[asakusuma]

I'd love to see progress on #1373 (comment). Are we at a point where a discussion would help?

Not sure if a discussion is actually needed, or if someone just needs to execute, but we still haven't actually updated the spec to reflect the Clear-Site-Data changes that were made in Chromium:
#1506
#1440

[youennf]

@youennf, it feels like we should chat about background fetch and try to come to a consensus there.

Yes, this might also have potential implications for push notifications as well.

[wanderview]

@jungkees Do you think MS would like to discuss this cache API proposal at all?

https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/CacheAPIResponseMetadata/explainer.md

[jungkees]

Yes, @wanderview. Thanks for bring it up. We'd love to put it on the agenda if folks are interested. In addition to the feature details in the proposal, I wish to also hear feedback around whether it'd be useful for devs. @asakusuma @n8schloss @aarongustafson

[yoavweiss]

I'd love to discuss #1542 and potential solutions, if there's still room on the agenda

[mfalken]

Some issues that come to mind:

• spec what requestStart, responseStart, and responseEnd should represent when service worker is involved resource-timing#119
• "no-cors" CSS SOP violation #719

[jakearchibald]

I've captured the topics in the OP. Please let me know what topics you're interested in, and what timezone you're in, and I'll get schedulin'.

[makotoshimazu]

Thanks Jake for organizing!
I'm specifically interested in updates, background activity, header's timing, and fix worker timing. I'm in JST (UTC+9).

[annevk]

All, except for declarative routing/cache metadata. CET. Thanks Jake!

[asutherland]

All. EDT. Thank you kindly.

[wanderview]

All, EDT. Thanks.

[jungkees]

All, PDT. Thanks, @jakearchibald! Please add @erik-anderson and @SteveBeckerMSFT from MSFT to the invitee list (all PDT).

[mfalken]

I'm interested in at least updates & the two topics I proposed. I'm in JST.

[tomayac]

All, CET (CEST until Oct. 25). Thank you!

[jeffposnick]

👋 I'm specifically interested in the following, and am in EDT:

• Cache metadata
• Declarative routing
• clear-site-data