wms.sso.biglobe.ne.jp - Firefox is not supported
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P3, Webcompat Score:3, firefox137 wontfix, firefox138 wontfix, firefox139 wontfix, firefox152 fixed)
People
(Reporter: rbucata, Assigned: twisniewski)
References
(Depends on 1 open bug, )
Details
(4 keywords, Whiteboard: [webcompat-source:web-bugs])
User Story
platform:windows,mac,linux impact:blocked configuration:general affects:all branch:release user-impact-score:50 diagnosis-team:webcompat
Attachments
(3 files)
Environment:
Operating system: Android 14 and Windows 10
Firefox version: Firefox 137.0
Steps to reproduce:
- Navigate to: https://wms.sso.biglobe.ne.jp/webmail/index-tui.jsp?v=0.30-0
- Observe
Expected Behavior:
The page loads
Actual Behavior:
Unsupported browser message displayed
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/152790
| Reporter | ||
Comment 1•1 year ago
|
||
| Reporter | ||
Updated•1 year ago
|
Comment 2•1 year ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
This works with Chrome Mask (I see a login screen, at least), so let's try shipping an override.
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 4•1 year ago
|
||
Oddly, unlike on desktop, Firefox isn't being rejected on Android (though I don't have a login with which to verify whether there is a post-login rejection).
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 5•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 7•1 year ago
|
||
| bugherder | ||
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•11 months ago
|
Updated•6 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
| Assignee | ||
Comment 8•3 months ago
|
||
They seem to no longer block Firefox, though I don't have a login to confirm whether they only do so after one logins in. Still, we might as well remove our webcompat intervention for now and see what happens.
| Assignee | ||
Updated•3 months ago
|
| Assignee | ||
Comment 9•3 months ago
|
||
Comment 10•3 months ago
|
||
Comment 11•3 months ago
|
||
| bugherder | ||
Updated•3 months ago
|
Description
•