TPAC 2023 - Call for topics

[marcoscaceres]

TPAC 2023 will be held from 11 to 15 September 2023, with a main in-person hub at Melia Sevilla Hotel, in Sevilla, Spain.

tl;dr: please leave a comment below on your topic and how long you need (90 minute or 2-hour slot).

As last year, we are adapting our format to a hybrid mode and planning to build a dynamic meeting.

Here is the projected schedule (still to be confirmed):

The schedule of the week should be as follows:

• Monday 11 September
• Tuesday 12 September.

In order to build a dynamic meeting to bring more cross participation and interactions, we will work this year with set slots. Each group will be able to ask for 90 minute and/or 2-hour slots.

[marcoscaceres]

For Web Manifest, a few of us would like to discuss:

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

Cc @b1tr0t, @dmurph

[marcoscaceres]

Gamepad API folks would like to meet for 1-2 hours to chat about:

• haptics
• finishing the model for the spec
• folding in more of the extension
• Possibly other topics

[cabanier]

Gamepad API folks would like to meet for 1-2 hours to chat about:

• haptics
• finishing the model for the spec
• folding in more of the extension
• Possibly other topics

The Immersive group will meet Monday, Tuesday and Friday according to the schedule. We can do a joint meeting any of those days.

[tomayac]

While we all agree on the OPFS, the vendors have differing opinions on dealing with files in the user-visible file system, like File Handling, drag and drop integration, and the various picker methods. Would it be worthwhile to discuss this again, especially in the light of macOS Sonoma's support for web apps?

[dmurph]

(copying from post in w3c/manifest#1093)

@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 / url handling / link 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?
• 30-60 mins Isolation
  • @mgiuca and @reillyeon
  • 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).
  • WebKit's experience with implementing isolation as part of web app installation.

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?

[marcoscaceres]

We should chat generally about the "Expectations of Editors" and what that means, and when those expectations are not met.

[marcoscaceres]

We should have a joint meeting with the i18n Folks about web manifest.

[marcoscaceres]

WebKit folks would like to again discuss a more efficient solution for Push notifications. This would be a follow up to what we discussed at last year's TPAC.

[marcoscaceres]

We should set set time aside for status on joint deliverables with DAS. Maybe @reillyeon and I could a quick presentation about what we plan on collaborating on?

@reillyeon, will you be around Monday afternoon from 1-2pm?

[marcoscaceres]

@cabanier, hey, let's book in 20 minutes on Tuesday late afternoon. That way Ben from Microsoft can join.

[marcoscaceres]

@tomayac, let's discuss your proposal on Tuesday and mix it in generally with the stuff that @dmurph listed above. Can you coordinate with him to make sure it's covered?

[LJWatson]

Everyone, last call for meeting topic/time for TPAC. If you haven't already, please post a comment here by end of day on Friday 4 August. Thanks.

[tomayac]

@dmurph, based on #91 (comment), what do you think of this plan, which builds upon your bullets from #91 (comment):

• 1 hour - launch events / url handling / link 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.
    • Can we get at least directional alignment on dealing with files in the user-visible file system, focusing the discussion on the following APIs:
      • File Handling
      • Drag and drop integration
      • Picker methods

1 hour may be a stretch given the complexity of some of the topics.

[reillyeon]

We should set set time aside for status on joint deliverables with DAS. Maybe @reillyeon and I could a quick presentation about what we plan on collaborating on?

@reillyeon, will you be around Monday afternoon from 1-2pm?

Yes, that works for me.

[dmurph]

@tomayac I agree 1 hour might be a stretch. Hopefully I can help with prework here. Maybe we expect possible overflow of this one?

[AdaRoseCannon]

30-45 minutes to chat about haptics with Immersive Web WG would be great.

[marcoscaceres]

Ok, locking in 5pm on Tuesday to talk about haptics across both groups.

[a-sully]

• Can we get at least directional alignment on dealing with files in the user-visible file system, focusing the discussion on the following APIs:
  • File Handling
  • Drag and drop integration
  • Picker methods

@tomayac shall we split this discussion off into a separate session on file system? There's enough material on that topic alone to cover an hour or more. And that would give the rest of your proposed agenda room to breath :)

[a-sully]

....though where exactly to talk about file system is up for discussion... Last year we didn't talk about it with the WAWG, but had separate whatwg and WICG discussions for the respective whatwg and WICG halves of the spec... but the WAWG is arguably the place this should be discussed anyways (as @tomayac mentioned in #91 (comment))

Open to suggestions from the organizers!

[diekus]

30-45 minutes to chat about Web Install API, declarative way of installing web apps. Also adding AttributionInfo to the mix since it is related.

[LJWatson]

@Dikis this the same as @tomayac mentioned in #91 (reference)?

[LJWatson]

We've posted the WebApps TPAC 2023 agenda.

We have a crammed schedule for both days. We may be able to fit one or two more things in, but it'll mean running a really tight schedule the whole time.

Looking forward to catching up with everyone then 😊

[tomayac]

@Dikis this the same as @tomayac mentioned in #91 (reference)?

(Correcting @Dikis to @diekus.)

[LJWatson]

(Correcting...

Oops! I'm sorry. My bad. Thanks for catching that.

[diekus]

Hola @LJWatson! Yes, I believe it is the declarative install topic mentioned above. I'd like to add Attribution Info API to the chat, shouldn't take much longer!

[a-sully]

Following up on #91 (comment) - I'd like to discuss the APIs @tomayac listed in that comment (relating to File System) with this working group. 30 minutes should be sufficient if we limit the scope to just these few topics. Any chance we can make room on the agenda? Thanks!

[marcoscaceres]

closing in prep to start planning for 2024