Open Bug 1919242 Opened 2 months ago Updated 9 days ago

oneview.malwarebytes.com - Firefox is not supported

Categories

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

Product:
Web Compatibility
Component:
Site Reports
Platform:
Desktop
Windows 10
Type:
defect

Tracking

(firefox130 affected, firefox132 affected)

Tracking Flags:
Tracking Status
firefox130 --- affected
firefox132 --- affected

People

(Reporter: rbucata, Unassigned)

References

(Depends on 1 open bug,
URL
)

Details

(Keywords: webcompat:contact-in-progress, webcompat:needs-login, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])

User Story

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

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

Steps to reproduce:

  1. Navigate to: https://oneview.malwarebytes.com
  2. Observe

Expected Behavior:
Firefox is supported

Actual Behavior:
Says it only supports Chrome

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/141775

status-firefox130: --- → affected
status-firefox132: --- → affected

Freddy, do you know if we have contacts at Malwarebytes we could poke about this?

Severity: -- → S2
User Story: (updated)
Depends on: firefox-not-supported
Flags: needinfo?(fbraun)
Keywords: webcompat:needs-contact, webcompat:needs-diagnosis
Priority: -- → P1

This bug is being misprioritized because we're matching against malwarebytes.com instead of oneview.malwarebytes.com and malwarebytes.com is a lot higher in the tranco list (3525) than in CRUX (100000)

Priority: P1 → P2

I don't know anyone at Malwarebytes, but have asked on mastodon :-). Will keep you posted if I learn more, though it's rather unlikely at this point.

Flags: needinfo?(fbraun)

FWIW the page loads just fine (showing a very simple login form) if I use Chrome Mask to spoof a chrome user agent string. But I can't go further because I don't have a login.

I suspect we're blocked on investigating further (i.e. diagnosing what-possible-Firefox-bugs-they-might-be-trying-to-avoid, if any) until/unless someone's got a login for this site or a contact at Malwarebytes who can help. We probably can't proactively ship an intervention (to e.g. spoof another UA string) without being able to test and see whether the site actually works.

--> webcompat:blocked for now.

Keywords: webcompat:blocked

Thanks for the report the Malwarebytes Threatdown team is looking into it.

Thanks for letting us know! Looking forward to having the block lifted. If you know of any Firefox-specific behaviors that are causing you trouble that are (or were) motivating the block, please let us know.

Keywords: webcompat:blocked, webcompat:needs-contact, webcompat:needs-diagnosis → webcompat:contact-in-progress

Will let you know, thanks!

You need to log in before you can comment on or make changes to this bug.