Call of topics for TPAC

[marcoscaceres]

TPAC is coming up in September 2023, and we are looking for topics to discuss. Editors met and we are considering the following

• Launch events
• Declarative install solution (or BIP again)
• navigator.standalone and some CSS things to compliment that
• Updates

Anything else folks would like to prioritize for face to face discussion?

[mgiuca]

• Isolation
  • Particularly, the problems that arise if user agents create an isolated environment for installed apps, with regards to external navigation, Oauth being the biggest problem.
  • And the possibility of creating standards around (and possibly APIs around) which storage partition to open certain URLs in (rather than relying on unspecified heuristics).

[dmurph]

@marcoscaceres confirmation on the list you wrote, those are all important for us to talk about. Can we get those topics on the schedule? I'm thinking:

• 1 hour - launch events / handling / data handling / file handling / etc
  • I expect we will bring use-cases here and API proposals, and discuss about API shape, use-cases, etc.
  • Goal: Come to tentative agreement on what the following would look like
    • declarative API (currently implemented as launch handling & file handling in Chromium, but could be changed) and
    • JS API (not implemented in Chromium yet), like the existing service worker launch event proposal, or something different.
• 1 hour - install, imperative install, BIP, etc
  • I expect we will bring use-cases and partner requests, and outline existing solutions & new proposals like navigator.install.
  • Goal: Come to direction agreement (or acknowledged disagreement) on where we want installation & developer controls on installation to go in the future.
• 15-30 min: detecting install / navigator.standalone
  • Goal: Determine if this is acceptable for the platform, and if so, what the API shape might be
  • initial doc I created
• 30-60 mins Updates: Recap on last TPAC algorithm, re-alignment of goals
  • How is safari thinking about updating security sensitive members & spoofing risk?
• ?? mins Isolation
  • @mgiuca and @reillyeon what time do you think we would need to chat about this? Goal of toipcs?
  • Discuss problems that arise if user agents create an isolated environment for installed apps, with regards to external navigation, Oauth being the biggest problem.
  • Discuss the possibility of creating standards around (and possibly APIs around) which storage partition to open certain URLs in (rather than relying on unspecified heuristics).

Minor topics (15 mins each, if needed)

• Window controls overlay - Any interest / questions from other user agents?
• protocol handlers
• Why did Safari gate notifications on installation?
• notifications - Issues that chromium is currently seeing (although Peter won't be around, so not sure if we can talk about solutions)
• Menu bar API for mac menu bar.

What do you think about those topics and goals? Any changes?

[reillyeon]

I think the isolation conversation could easily be 30-60 minutes. I'm looking forward to hearing about WebKit's experience with implementing isolation as part of web app installation.

[marcoscaceres]

We should talk about #1090 ... and related i18n issues. But adopting a hybrid of what @aphillips proposes and what I proposed for i18n would be great (they are mostly the same thing, but mine is backwards compatible because it uses a different members).

[marcoscaceres]

Let's have a joint meeting with the i18n folks.