Open Bug 1991357 Opened 4 months ago Updated 4 months ago

s.tabelog.com: Firefox for Android is not recommended

Categories

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

Product:
Web Compatibility
Component:
Site Reports
Type:
defect

Tracking

(Webcompat Priority:P3, Webcompat Score:4)

Project Flags:
Webcompat Priority P3
Webcompat Score 4

People

(Reporter: canalun, Unassigned)

References

(Depends on 1 open bug,
URL
)

Details

(Keywords: webcompat:contact-in-progress, webcompat:site-report, Whiteboard: [webcompat:sightline][webcompat:japan])

User Story

outreach-assignee:canalun
outreach-contact-date:2025-09-29
user-impact-score:60
platform:android,ios
impact:unsupported-warning
configuration:general
affects:few
branch:release

Environment
145.0a1 (Build #2016116295), e0c3190130f
GV: 145.0a1-20250923215832
AS: 145.20250919050351
OS: Android 16

STR
Open https://s.tabelog.com/smartphone/help/support_device

AR
For Android, it says the latest Google Chrome is recommended and doesn't mention any other browsers.

ER
Firefox for Android is recommended.

User Story: (updated)
Keywords: webcompat:contact-in-progress, webcompat:site-report

It's not about any banner or warning prompt, but about just recommended environment information.
Additionally, the site seems working on Firefox for Android.
So basically users can use this site and wouldn't notice that Firefox for Android is not recommended unless see the info page.

User Story: (updated)
Webcompat Score: --- → 1
URL: https://s.tabelog.com/smartphone/help...
Severity: -- → S3
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: 1 → 6
Depends on: firefox-not-supported-warning
Priority: -- → P2
Whiteboard: [webcompat:sightline][webcompat:japan]
User Story: (updated)
Webcompat Score: 6 → 7

I'm dropping affected to "few" because the warning doesn't show up during the regular workflow.

Severity: S3 → S4
User Story: (updated)
Webcompat Priority: P2 → P3
Webcompat Score: 7 → 3
Priority: P2 → P3
User Story: (updated)
Webcompat Score: 3 → 4
You need to log in before you can comment on or make changes to this bug.