-
Notifications
You must be signed in to change notification settings - Fork 55
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 API - Same Origin #888
Comments
I got a few questions:
|
Hi @diekus we discussed briefly in today's TAG session and someone from TAG will be at the breakout session you're holding at TPAC next week so we hope to progress then. |
Hi @diekus - thanks for this and thanks also for the TPAC session on this topic which was really interesting! Some initial feedback form our TAG breakout today: We're concerned about potential abuse of the "Web app installation from associated domain" use case, especially in a world where installed webapps might be auto-granted additional permissions. We're generally happy with the same-origin-bound use case of We think the expected venue should probably be Web Applications working group (after this graduates from WICG) and/or the WHATWG HTML workstream. |
Hi @diekus any update on this from your PoV? Thanks! |
Hola TAG. I've missed you ✨. So getting back to business. We've completely reworked the shape of the API. Both explainers (for same and cross-origin) have been updated and I am pleased to inform you of the following: (cc @iVanlIsh)
(cc @torgo)
We've got several store partners in line to try it, including 3P developers that are very excited about the possibilities to democratise application distribution! I whole heartly agree with you that WebApps WG is the right place for this work 💖. |
Given that the request has split into same-origin and cross-origin versions, we split the review accordingly (as we feel one may be able to proceed faster than the other). This review is now about the same-origin behavior, the cross-origin behavior issue is here |
This generally looked good to us. Our only comment relates to "related applications". We did not understand what this is for, but it seems to require the Cross-origin version of the API to work. If that assumption is correct, it should be moved there. It is also unclear how |
Hola @LeaVerou, thanks for your valuable feedback. The Regarding multiple apps on a same origin, they can be installed as they can have different manifest |
Hi @diekus, after reading your comment both @plinss were still confused about several aspects of this API: Wrt
Wrt installing multiple PWAs from the same origin and When separating the API into a same-origin and a cross-origin version, it’s important that the separation is "clean", i.e. that the same origin version can be implemented independently and no parts of it should require the cross-origin version of the API. With that in mind:
Also, given the text in the explainer, it is still unclear to use what the author flow is for e.g. having a website that includes multiple apps ( We also don’t quite understand the signature of Also please note that TAG principle around preferring a dictionary for optional arguments. |
Hola TAG!
I'm requesting an early TAG review of the Web Install API.
The Web Install API allows a web site to install a web app (same domain). This functionality allows the creation of web based catalogues that can install PWAs directly from the web and into multiple platforms.
Further details:
You should also know that...
there's plenty of positive developer feedback for an API like this one!
We'd prefer the TAG provide feedback as (please delete all but the desired option):
🐛 open issues in our GitHub repo for each point of feedback
The text was updated successfully, but these errors were encountered: