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.

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

[Web Install] Separating naming of same-document and cross-document install #801

Open
dmurph opened this issue Apr 24, 2024 · 0 comments
Open
Assignees
Labels
Web Install API Declarative install for web apps from a web app.

Comments

@dmurph
Copy link

dmurph commented Apr 24, 2024

It seems difficult and possibly buggy to combine these apis into one method call

  • If the same-site can accept a manifest_id, then how will the cross-origin behavior work of defaulting the install_url as the manifest_id?
    • There could be some complex logic around "check if a manifest exists now, and if so, then use that & verify it with the manifest id. Otherwise load the manifest_id as a url in the background and try to install from there"
    • this is a tricky edge case that isn't obvious if the manifest wasn't properly added.

Instead can we separate these APIs into two calls, maybe

  • navigator.installSelf - always installs this document. optional manifest_id argument.
  • navigator.install - always is installing via a background web contents, loading the install url. Required manifest_id, optional install_url

(there can probably be better naming)

@reillyeon

@dmurph dmurph added the Web Install API Declarative install for web apps from a web app. label Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Web Install API Declarative install for web apps from a web app.
Projects
None yet
Development

No branches or pull requests

2 participants