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

Sorry, I've had a hell of a week and haven't seen the thread #835 until just now. (I am sick now so I'm not going to try and figure out a rational position at this hour on a Friday night.)

Can we hold off on this until next week? Reading over the thread, there are reasonable arguments on both sides, so ultimately it should come down to whether there are enough browsers implementing the standard for it to remain in.

I'll make a couple of quick points:

- Unlike other APIs, where the existence or absence of a method causes potential compatibility issues between browsers that sites have to deal with, BIP is an event that is specified as firing at the UA's discretion, which could be never. Therefore, sites do not need to explicitly account for the possibility that a UA hasn't implemented BIP (e.g., by detecting the presence of a method). They can just hook an event listener and if it never fires, oh well.
- When we tried to modify BIP into a different API several years ago, we faced resistance from the fact that it wasn't just Chrome implementing. From memory, Samsung Internet and Opera and maybe other browsers had independently implemented this method. Now I suspect (but haven't confirmed) that Edge-on-Chromium will also include this feature. This may or may not be considered sufficient implementor interest, but it should give us pause before removing something from the standard. This isn't just a Chrome-proprietary feature.

-- 
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-565333387