Open Bug 1914565 Opened 1 year ago Updated 4 months ago

myassurity.com - Browser unsupported

Categories

(Web Compatibility :: Site Reports, defect, P2)

Desktop
Windows 10

Tracking

(Webcompat Priority:P3, Webcompat Score:2)

ASSIGNED
Webcompat Priority P3
Webcompat Score 2

People

(Reporter: railioaie, Assigned: twisniewski)

References

(Depends on 1 open bug, )

Details

(5 keywords, Whiteboard: [webcompat-source:web-bugs])

User Story

platform:windows,mac,linux,android
impact:blocked
configuration:general
affects:all
branch:release
diagnosis-team:webcompat
user-impact-score:20

Attachments

(2 files)

Environment:
Operating system: Windows 10
Firefox version: Firefox 129.0

Preconditions:
Clean profile

Steps to reproduce:

  1. Click on https://myassurity.com/Account/UnsupportedBrowser
  2. Observe the page

Expected Behavior:
The page is loading

Actual Behavior:
Browser unsupported

Notes:

  • Reproduces regardless of the status of ETP
  • Reproduces in Firefox Nightly, and Firefox Release
  • Does not reproduce in Chrome

Created from https://github.com/webcompat/web-bugs/issues/140733

Note, the steps-to-reproduce in comment 0 don't seem to be correct. The URL in comment 0 is the explicit URL of the browser-not-supported page, which renders the same "your browser is not supported" message in all browsers (or at least in Firefox and Chrome on my system).

In the original github issue, the reporter said:

Assurity's website design fully locks out firefox without attempting to allow.
This is the landing page with an automatic redirect from https://myassurity.com/
In Chrome, https://myassurity.com/ redirects to the login page with no issue.

i.e. the real issue is that https://myassurity.com/ automatically redirected to https://myassurity.com/Account/UnsupportedBrowser if you were using Firefox.

I can confirm that that's still the case in Firefox release 134 and Nightly 136. However, if I activate Chrome Mask on the unsupported-browser page, then from that point on, https://myassurity.com/ will redirect to the login page as-expected.

So: this is just https://myassurity.com/ doing UA-sniffing, and we could theoretically work around that with UA-spoofing if we wanted to (matching what Chrome Mask does when activated).

Webcompat Priority: --- → P2
Webcompat Score: --- → 6
Webcompat Score: 6 → 5
User Story: (updated)
Webcompat Score: 5 → 6
Keywords: leave-open
Priority: P3 → P2
Assignee: nobody → twisniewski
Status: NEW → ASSIGNED
Webcompat Score: 6 → 5
Webcompat Score: 5 → 1
User Story: (updated)

Our UA override isn't sufficient anymore. I'll update it.

Webcompat Priority: P2 → P3
User Story: (updated)
Webcompat Score: 1 → 2
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: