Add to homescreen after requesting the desktop site requests the mobile site |
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. Go to web.whatsapp.com using your phone. 2. Tap on the browser ... button. 3. Tap on "Request desktop site". - Note that WhatsApp Web has loaded. 4. Tap on the browser ... button. 5. Tap on "Add to homescreen". 6. Call it "WhatsApp". 7. Tap on "Add" or "OK" or similar. 8. Get out of Chrome. 9. Go to the home screen. 10. Tap on the WhatsApp icon that "Add to homescreen" created. What is the expected behavior? WhatsApp Web. What went wrong? The mobile version of the WhatsApp Web URL, which is an introduction to WhatsApp Web instead of WhatsApp Web itself. Did this work before? No Chrome version: 59.0.3071.115 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Jul 10 2017
I suspect this is because we use whatever the manifest gives us, but I'll let Dom confirm.
,
Jul 10 2017
The desktop version of Whatsapp does not serve a web app manifest, so it can't be a WebAPK. The observed behaviour is due to how request desktop site works. It simply reloads the current page with a desktop user agent rather than a mobile user agent. When a shortcut is added to homescreen, we don't bake in the user agent, hence the new shortcut has no idea that it was to a site loaded with the desktop user agent. I'm not really sure we want to encourage users to add non-mobile optimised formats to their homescreen (or permit developers to get away without optimising their sites for mobile).
,
Jul 10 2017
#3 - so you prefer that users install a Cordova application per for-desktop website? That is an overkill...
,
Jul 12 2017
c#4: no, we prefer that developers create versions of their sites which work properly on mobile. I think it's an antipattern to create shortcuts on mobile which permanently open using a desktop user agent. It means that if the site becomes mobile friendly users will not see the improvements. |
||||
►
Sign in to add a comment |
||||
Comment 1 by phistuck@chromium.org
, Jul 8 2017Labels: -OS-Windows -Arch-x86_64 OS-Android
Status: Untriaged (was: Unconfirmed)