Open Bug 1899871 Opened 2 years ago Updated 1 month ago

knowledge.smarthr.jp - Chrome and Edge are recommended browser

Categories

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

Tracking

(Webcompat Priority:P3, Webcompat Score:3)

Webcompat Priority P3
Webcompat Score 3

People

(Reporter: ksenia, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: webcompat:needs-contact, Whiteboard: [webcompat-source:web-bugs][autowebcompat:processed][autowebcompat:repro-failed])

User Story

platform:windows,mac,linux,android
impact:unsupported-warning
configuration:general
affects:all
diagnosis-team:webcompat
user-impact-score:40
autowebcompat-repro-status:failed
autowebcompat-repro-reason:not_web_platform
autowebcompat-repro-report-os:all

Environment:
Operating system: Windows 10
Originally reported Firefox version: Firefox 102.0
Last reproduced with the following UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0
Platforms reproduced on: windows,mac,linux,android

Steps to reproduce:
SmartHR does not support Firefox.

Actual Behavior:
Browser unsupported

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

Webcompat Priority: --- → P3
Webcompat Score: --- → 2
Webcompat Score: 2 → 1
Webcompat Score: 1 → 3

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)

I don't think we'll ship a site-patch here, since there is no known breakage or even a "browser unsupported" nag, just a mention on their proper support page.

User Story: (updated)
User Story: (updated)
See Also: → 2040371
Whiteboard: [webcompat-source:web-bugs] → [webcompat-source:web-bugs][autowebcompat:processed]
User Story: (updated)
Whiteboard: [webcompat-source:web-bugs][autowebcompat:processed] → [webcompat-source:web-bugs][autowebcompat:processed][autowebcompat:repro-failed]
You need to log in before you can comment on or make changes to this bug.