-
Notifications
You must be signed in to change notification settings - Fork 28
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
Controls the install and open icon in the address bar #23
Comments
I think we shouldn’t decide for the users: they should be free to open whatever page how they want. Also, we already have the Web Manifest scope that can be used to limit the URL scope of an installable app. In the use case you mention, if the help section is outside the Web Manifest scope, then the browser will threat it as an external website, if I’m correct. |
I considered the scope. But it is not sufficient for all cases. For example, the landing page of the app is |
Generally, users don't know which part of pages in the origin can be loaded into the app. Developers know it. |
Move this issue to w3c/manifest#996 . I listed more behaviors of the install icon and launch icon w3c/manifest#996 (comment) . But they are not clearly defined in the spec. |
As shown in the images above, the browser address bar has install icon and open icon for installing and launching the app. But not all web pages in the origin should be used for it. For example, help pages of the app should be opened as general web pages in the browser, rather than load them into the app.
So the website should controls whether the install and open icon is displayed for a page. For example control it by manifest or by javascript.
The text was updated successfully, but these errors were encountered: