Open Bug 1899933 Opened 2 years ago Updated 3 months ago

www.benefits.ml.com - Firefox is not a supported browser

Categories

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

Tracking

(Webcompat Priority:P3, Webcompat Score:1)

Webcompat Priority P3
Webcompat Score 1

People

(Reporter: ksenia, Unassigned)

References

(Depends on 1 open bug, )

Details

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

User Story

platform:windows,mac,linux
impact:unsupported-warning
configuration:general
affects:all
branch:release
user-impact-score:0
diagnosis-team:webcompat

Environment:
Operating system: Mac OS X 10.15
Originally reported Firefox version: Firefox 111.0
Last reproduced with the following UA: Mozilla/5.0 (Macintosh; Intel Mac OS X 13.4; rv:126.0) Gecko/20100101 Firefox/126.0
Platforms reproduced on: windows,mac,linux

Steps to reproduce:
Site warns me not to log in because I am not using a supported browser. I am still able to log in

Actual Behavior:
Says browser is not compatible

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

Webcompat Priority: --- → P3
Severity: S3 → S4
User Story: (updated)
Webcompat Score: --- → 5

I'm not sure how this bug got the webcompat:sitepatch-applied keyword, but I don't see any evidence that we've ever had a sitepatch in our webcompat addon for it, so I'm going to drop that flag for now.

Webcompat Score: 5 → 1
Webcompat Score: 1 → 4

Mass-assigning diagnosis-team to webcompat for "Firefox is not supported" bugs that don't already have a team assigned. This action is done by a script. For your convenience, feel free to filter your bugmail with 559a9604-41ec-11f0-9ec6-f3f21dcd7cf2.

User Story: (updated)

There's only so much I can do without a login, but I see signs that they still have the message in their source, and this logic (based on the useragent string):

                        if (b.mobile || b.tablet || b.crawler) {
                          userMsg = b.browserSupport.content.mobileBrowser
                        } else if (
                          b.msie &&
                          b.version <= VERSIONS.BLOCKED_IE ||
                          b.firefox &&
                          b.version <= VERSIONS.BLOCKED_FF
                        ) {
                          userMsg = b.browserSupport.content.unsupportedBlocked
                        } else if (
                          !(b.win && b.msie) &&
                          !b.chrome &&
                          !(b.win && b.firefox) &&
                          !(b.mac && b.safari)
                        ) {
                          userMsg = b.browserSupport.content.unsupportedBrowserType

So let's ship a UA override and hope someone can confirm for us whether it's working.

User Story: (updated)
Keywords: leave-open

Actually looking at this again today, we already do have an intervention applying to bypass their warning message's troublesome JS:

                        if (
                          !(b.win && b.msie) &&
                          !b.chrome &&
                          !(b.win && b.firefox) &&
                          !(b.mac && b.safari)
                        ) {

I just didn't realize it because I had forgotten marking it as such when writing that intervention long ago.

Webcompat Score: 4 → 1
User Story: (updated)

The leave-open keyword is there and there is no activity for 6 months.
:denschub, maybe it's time to close this bug?
For more information, please visit BugBot documentation.

Flags: needinfo?(dschubert)
User Story: (updated)
Flags: needinfo?(dschubert)
You need to log in before you can comment on or make changes to this bug.