Re: [w3c/manifest] BREAKING CHANGE: remove beforeinstallprompt event (#836)

@aarongustafson 
> I personally think it’s (potentially) useful, but I’m not sure it needs to be explicitly part of this spec.

It doesn't *need* to be part of any spec in particular (it could, for instance, be its own spec document, which is where I'll put it if it gets removed from Manifest, though I'm not sure where to host it). But being part of Manifest seems like the most appropriate place for it, if it's going to be standard.

> That said, I don’t have an objection to including a note in the spec about UAs being free to implement some form of prompting event, perhaps even with a specific callout of the existing (in this event "non-standard") beforeinstallprompt event name.

That doesn't sound good. That would mean different UAs could implement different, incompatible events, with different names, or with the same name but different methods, or with the same `prompt()` method but different semantics. That's precisely why we have standards, to establish a contract between developers and the web platform, so they don't have to write code specific to each browser.

If there is only one implementation (in Chromium), then it doesn't need to be (/ isn't allowed to be) in a W3C standard, because there aren't going to be several divergent implementations. But if ever a second independent implementation happens (say Mozilla changes their mind, or Microsoft rips out our code and writes their own implementation of `beforeinstallprompt`), then at that point, we will want an agreed standard. It doesn't make sense for the spec to non-normatively suggest `beforeinstallprompt`. It is either part of the standard (developers code against the standard), or it is not (developers can code against Chromium's implementation).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/836#issuecomment-567719730