search

webcompat / web-bugs

A place to report bugs on websites.
https://webcompat.com
Mozilla Public License 2.0
733 stars 63 forks source link

www.moneygram.com - Microsoft Edge is unsupported browser #60151

Open d-fect opened 3 years ago

d-fect commented 3 years ago

URL: https://www.moneygram.com/mgo/no/en/

Browser / Version: Microsoft Edge 86.0.622.48 Operating System: Windows 10 Tested Another Browser: Yes Chrome

Problem type: Site is not usable Description: Browser unsupported Steps to Reproduce: Getting the following message: "Your browser is not supported on this site. We recommend using Chrome or Safari or using the mobile app. iOS Android"

View the screenshot Screenshot
Browser Configuration
  • None

From webcompat.com with ❤️

softvision-oana-arbuzov commented 3 years ago

Thanks for the report, but I'm not able to reproduce the issue. image

Tested with: Browser / Version: Chrome 86.0.4240.75 Operating System: Windows 10 Pro

@d-fect are you signed into your account, or you just receive the message when accessing the page.

d-fect commented 3 years ago

Sorry, I see that I chose the wrong browser when reporting this error. It should be Microsoft Edge Version 86.0.622.48 (Official build) (64-bit)

softvision-oana-arbuzov commented 3 years ago

No worries @d-fect. Indeed, I was able to reproduce the issue too on Microsoft Edge. image

Tested with: Browser / Version: Microsoft Edge 86.0.622.48 Operating System: Windows 10 Pro

Moving to Needsdiagnosis for further investigation.

reinhart1010 commented 3 years ago

Spoofing the Edge UA as Chrome (by removing Edg/*) and the website works as normal.

image

reinhart1010 commented 3 years ago

But Edge for Android users are also affected by this issue, and it seems because Microsoft adds their custom UA at the end of the UA string, such as

Mozilla/5.0 (Linux; Android 10; SM-XXXX) AppleWebKit/537.36 (KHTML, like Gecko) Chrome 79.0/3945/136 Mobile Safari/537.36 EdgA/45.09.4.5081

However, it is interesting to see that Samsung Internet users are not affected by this issue, since Samsung adds their custom UA at the middle of the UA string, such as

Mozilla/5.0 (Linux; Android 10; SAMSUNG SM-XXXX) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/12.1 Chrome 79.0/3945/136 Mobile Safari/537.36

Screenshot_20201029-142558_Edge.jpg

Edge for iOS users are also affected, while Safari and Firefox users are not. Their UA strings are:

// Edge
Mozilla/5.0 (iPhone; CPU iPhone OS 14_0_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0 EdgiOS/45.9.10 Mobile/15E148 Safari/605.1.15

// Safari
Mozilla/5.0 (iPhone; CPU iPhone OS 14_0_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0 Mobile/15E148 Safari/604.1

// Firefox
Mozilla/5.0 (iPhone; CPU iPhone OS 14_0_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) FxiOS/29.0 Mobile/15E148 Safari/604.1

image

My original Edge screenshot was taken in Linux (Ubuntu 20.04) is

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4287.0 Safari/537.36 Edg/88.0.673.0

which then I modified it to

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4287.0 Safari/537.36

So, I can conclude this issue is caused by UA string parsing on the website.