Re: [w3c/manifest] Remove beforeinstallprompt and appinstalled events. (#836)

>  BIP is inherently tied to a particular install flow (showing a banner or
modal prompt), and not all browsers have that UI flow.

This is not true, every browser has HTML which does this.

And there are repercussions to excluding it because it prevents web sites
that host their own PWAs inside their own dialogs from installing their
PWAs, since browsers use the manifest if present from the url where the
site is hosted itself and not from sub-url. That makes it so you can only
install the website itself and not a useful standalone module of it.


On Thu, Sep 1, 2022 at 8:42 AM Marcos Cáceres ***@***.***>
wrote:

> Can I please respectfully ask we keep this on topic (BIP)? 🙏 I'm worried
> we will spin off into the nuances of standardization and add more walls of
> text to what's already a very lengthy topic.
>
> As @mgiuca <https://github.com/mgiuca> eluded to, the fact that it's not
> in the main spec doesn't mean that it's not specified. As @mgiuca
> <https://github.com/mgiuca> said, that it doesn't have an independent
> implementation means (*today*) that it's not in the spec. If *tomorrow*
> some other engine decides "oh! we need that!", then we would just revert
> this change.
>
> @msimic <https://github.com/msimic>, please understand that a lot of
> thought went into both the creation (and ultimate removal) of this feature.
> I was also involved in helping specify it and still believe it has merit.
> However, the rules of both the W3C Process and those working group
> membership agrees by signing up based on our Charter
> <https://www.w3.org/2022/04/webapps-wg-charter.html> justify its removal.
> To quote:
>
> In order to advance to Candidate Recommendation
> <https://www.w3.org/Consortium/Process/#RecsCR> and to add features after
> reaching Candidate Recommendation, each feature is expected to be supported
> by at least two implementations, which may be judged by factors including
> existing implementations, expressions of interest, and lack of opposition.
>
> Despite the Editors' best efforts (which includes me), we were not able to
> overcome the strong opposition and convince implemented this feature is
> critical. And as @mgiuca <https://github.com/mgiuca> said, even if we had
> it in the spec, there are well articulated reasons why BIP is not a good
> fit (and doesn't make any sense) for certain user agents.
>
> BIP is inherently tied to a particular install flow (showing a banner or
> modal prompt), and not all browsers have that UI flow.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/manifest/pull/836#issuecomment-1233815904>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AABHCCP5Q2CENKDWCDM5J7DV4BF5FANCNFSM4J2IVW4A>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/836#issuecomment-1233859044

You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/pull/836/c1233859044@github.com>