Re: [w3c/manifest] should we standardize navigator.standalone ? (Issue #1092)

Update here. Standardizing `navigator.standalone` creates a potential webcompat issue for people who want to detect iPad (or being iPad) and send links to the appropriate download/banner.

See https://github.com/mozilla/bedrock/pull/13328

## What happened?

Mozilla to detect the iPad Pro was using `(pf.indexOf('MacIntel') !== -1 && 'standalone' in navigator)`

So Safari 17 *Desktop* with `navigator.standalone` was identified as an iPad and instead to have a download link to a DMG file it was redirecting to the iOS Appstore. 

Mozilla fixed it. 
but a quick search online shows potential for more breakages.

* [GitHub Code](https://github.com/search?q=navigator.standalone+iPad&type=code)
* [Github Issues](https://github.com/search?q=navigator.standalone+iPad&type=issues)
* [StackOverflow](https://stackoverflow.com/search?q=navigator.standalone+ipad)

So this is to keep in mind in the solutions that needs to be evaluated. 

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

Message ID: <w3c/manifest/issues/1092/1616878673@github.com>