Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"When launching a web app" feels handwavy #67

Closed
yoavweiss opened this issue Oct 19, 2022 · 4 comments · Fixed by WICG/manifest-incubations#63
Closed

"When launching a web app" feels handwavy #67

yoavweiss opened this issue Oct 19, 2022 · 4 comments · Fixed by WICG/manifest-incubations#63

Comments

@yoavweiss
Copy link

It seems like this is the entry point to the spec's algorithms, and it's not well defined when that happens.
This seems like a concept that should be defined in HTML, and which would then call this spec explicitly from there.

Such a concept may also be useful for w3c/navigation-timing#180

/cc @domenic
@alancutter
Copy link
Collaborator

This spec is essentially defining a LaunchWebApp(appId, launchParams) function for other specs/the user agent's OS integrations to use. Defining all the "callsites" is out of scope for this spec.

@yoavweiss
Copy link
Author

I'm not saying you need to define the callsites as part of this spec. But I do think you need to file PRs on other specs that should be hooking into this. Otherwise, it's unclear when this is triggered.

@alancutter
Copy link
Collaborator

Yes, absolutely.
Specs to update:

This was referenced Oct 25, 2022
Closed
Merged
Merged
@alancutter
Copy link
Collaborator

alancutter commented Oct 31, 2022 •
edited
Loading

Updating https://w3c.github.io/web-share-target/#launching-the-web-share-target requires resolving #62 so creating a new web app client has sufficient information to run a POST navigation.

@alancutter alancutter mentioned this issue Nov 2, 2022
Merged
alancutter added a commit that referenced this issue Nov 8, 2022
@alancutter
Replace appmanifest's launch algorithm with one that has launch_handl…
6860bf5 
…er behaviors (#79)

This builds on top of w3c/manifest#1056 which adds a launch web application algorithm to the manifest spec. This updates the launch handler spec to replace that algorithm with its own. This enables other webapp specs (not in WICG) to gain the launch_handler behaviour without directly referencing this WICG spec.

Additionally this replaces the concept of "web app launch client" with the existing "application context" concept from the manifest spec which is effectively the same thing.

#67 #69 #84
#79
alancutter added a commit to WICG/manifest-incubations that referenced this issue Nov 9, 2022
@alancutter
Rewrite web app launch procedures in terms of the web-app-launch spec…
76fed98 
… algorithm (#63)

Fixes: WICG/web-app-launch#67

This updates 3 launch sites in manifest-incubations (note taking, protocol handlers and file handlers) to make use of the [=launch a web application with handling=] algorithm being added by: https://github.com/WICG/web-app-launch/pull/79/files

Note that the removal of Launch queue and launch params from this spec is due to these concepts already existing in https://wicg.github.io/web-app-launch/#script-interfaces-to-app-launches.

#63
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@yoavweiss @alancutter