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 API (Same-origin) #322

Open
diekus opened this issue Feb 26, 2024 · 1 comment
Open

Web Install API (Same-origin) #322

diekus opened this issue Feb 26, 2024 · 1 comment
Assignees
Labels
from: Microsoft Proposed, edited, or co-edited by Microsoft. topic: app-like capabilities Spec relates to native app style capabilities (e.g. things under the "PWA" or "Fugu" brands)

Comments

@diekus
Copy link

diekus commented Feb 26, 2024

WebKittens

@marcoscaceres

Title of the spec

Web Install API

URL to the spec

https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/WebInstall/explainer_same_domain.md

URL to the spec's repository

https://github.com/MicrosoftEdge/MSEdgeExplainers/

Issue Tracker URL

No response

Explainer URL

No response

TAG Design Review URL

w3ctag/design-reviews#888

Mozilla standards-positions issue URL

mozilla/standards-positions#991

WebKit Bugzilla URL

No response

Radar URL

No response

Description

This API allows web content to be "installed" to a device (definition of "installation" varies with platform/device.... for example, "install" can mean being added to the user's apps (desktop) or added to the homescreen (mobile)).

@marcoscaceres marcoscaceres self-assigned this Feb 27, 2024
@lukewarlow lukewarlow added topic: app-like capabilities Spec relates to native app style capabilities (e.g. things under the "PWA" or "Fugu" brands) from: Microsoft Proposed, edited, or co-edited by Microsoft. labels May 6, 2024
@marcoscaceres
Copy link
Contributor

marcoscaceres commented Jun 6, 2024

Hi @diekus, I did a first round of review and would probably like to see a few things clarified before taking it internally for discussion.

Just echoing the feedback that the TAG gave about the arguments. I'm not sure they make much sense in the same-origin context.

The manifest ID being required doesn't seem to make much sense (to me) as it's already provided and automatically computed from the manifest (even when there is no manifest). Having multiple ids being defined seems duplicative, and doesn't have a clear use case.

Same with the related applications stuff, it might be good to separate that out into a separate explainer?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
from: Microsoft Proposed, edited, or co-edited by Microsoft. topic: app-like capabilities Spec relates to native app style capabilities (e.g. things under the "PWA" or "Fugu" brands)
Projects
None yet
Development

No branches or pull requests

3 participants