- From: Ryosuke Niwa <notifications@github.com>
- Date: Thu, 12 Dec 2019 20:04:39 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 13 December 2019 04:04:41 UTC
> Because UI is not spec-ed, it's a moving thing, a browser can change its UI as much as it wants, it can chose to make it visible (an icon in the address bar) or very hidden (a non-obvious label at the end of the three dot menu), but as a developer, I shouldn't be concerned about the browser UI, I don't want to educate my users to access a web plateform feature on a specific browser. It should be the browser's charge. Right, and I'm saying that leave it to the browser to provide such an UI. > `beforeinstallprompt` event offers a consistent way to manually trigger a web [platform] feature despite browser UI & its potential changes over time and that's all I need. Since this is a browser UI issue as you've just stated, I see no reason why there needs to be a Web API which *triggers* it. FWIW, there might be nothing to be triggered because some browsers would rely fully on users to trigger it like Safari on iOS currently does. -- 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/issues/835#issuecomment-565291615
Received on Friday, 13 December 2019 04:04:41 UTC