Open Bug 1899057 Opened 1 year ago Updated 1 month ago

mobile.onvue.com - Browser unsupported

Categories

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

Product:
Web Compatibility
Component:
Site Reports
Type:
defect

Tracking

(Webcompat Priority:P2, Webcompat Score:1)

Project Flags:
Webcompat Priority P2
Webcompat Score 1

People

(Reporter: ksenia, Unassigned)

References

(Depends on 1 open bug,
URL
)

Details

(Keywords: webcompat:needs-contact, webcompat:site-report, webcompat:sitepatch-applied, Whiteboard: [webcompat-source:web-bugs])

User Story

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

Environment:
Operating system: Windows 10
Originally reported Firefox version: Firefox 86.0
Last reproduced with the following UA: Mozilla/5.0 (Android 14; Mobile; rv:126.0) Gecko/126.0 Firefox/126.0
Platforms reproduced on: android

Steps to reproduce:
Tried this site on Firefox on Android and on FF on Windows. On Android the site tells me to use Chrome instead (this works) and on Windows it tells me to use Safari instead (works in Edge Chromium).

Actual Behavior:
Browser unsupported

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

User Story: (updated)
Keywords: webcompat:sitepatch-applied
Priority: P3 → P2

The site also doesn't support Firefox desktop but on a different subdomain - https://proctor.onvue.com

Keywords: webcompat:sitepatch-applied

    Again...
    https://bugzilla.mozilla.org/show_bug.cgi?id=1860417#c29

    And this one is abusive. (unreasonably rejecting Firefox outright)

Webcompat Priority: --- → P3
User Story: (updated)
Webcompat Priority: P3 → P2
Webcompat Score: --- → 6
Keywords: webcompat:site-report
Webcompat Score: 6 → 3
Webcompat Score: 3 → 2
Webcompat Score: 2 → 1

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)
You need to log in before you can comment on or make changes to this bug.