Different UI for scrollbars on sites compared to Chrome
Categories
(Web Compatibility :: Knowledge Base, defect)
Tracking
(firefox118 affected)
| Tracking | Status | |
|---|---|---|
| firefox118 | --- | affected |
People
(Reporter: rbucata, Unassigned)
References
(Blocks 8 open bugs)
Details
User Story
url:www.etsy.com/* url:www.expedia.com/* url:www.southwest.com/* url:www.bilibili.com/* url:world.taobao.com/* url:www.bing.com/* url:www.instagram.com/* url:www.facebook.com/*
Attachments
(1 file)
|
146.06 KB,
image/png
|
Details |
stackoverflow.png
This is a meta bug to track the differences in the UI of scrollbars present on different pages.
|
Reporter | |
Updated•11 months ago
|
|
|
Reporter | |
Updated•10 months ago
|
|
||
Comment 1•10 months ago
|
||
Reproducible on stackoverflow.com as well.
|
|
Reporter | |
Comment 2•9 months ago
|
||
Reproducible on vk.com
Tested with:
Browser / Version: Firefox Nightly 120.0a1 (2023-10-03) (64-bit) Chrome Version 117.0.5938.150 (Official Build) (64-bit)
Operating System: Windows 10 PRO x64
|
|
Reporter | |
Comment 3•9 months ago
|
||
Reproducible on joom.com
Tested with:
Browser / Version: Firefox Nightly 120.0a1 (2023-10-03) (64-bit) / Chrome Version 117.0.5938.150 (Official Build) (64-bit)
Operating System: Windows 10 PRO x64
|
||
Updated•4 months ago
|
|
|
||
Updated•4 months ago
|
|
|
||
Updated•4 months ago
|
|
||
Comment 10•3 months ago
|
||
Ksenia, can you update the priorities of the new bugs, please?
|
||
Updated•3 months ago
|
|
|
||
Updated•3 months ago
|
|
|
||
Updated•3 months ago
|
|
|
||
Updated•3 months ago
|
|
||
Comment 11•3 months ago
•
|
||
I don't understand what is this bug (and dependencies) about. Why does our scrollbar UI have to be exactly same as Chrome? Do we have any WHATWG specs about the scrollbar UI that we do not comply with? Do those differences cause actual usability problem?
https://github.com/webcompat/web-bugs/issues/125737 says bugs.mojang.com is unusable. But same for all other dependencies? That is, are Instagram, Facebook, Netflix, Discord, and Bing really unusable due to the scrollbar UI difference? Moreover, https://github.com/webcompat/web-bugs/issues/125737 is reported on Linux according to the reporter, but the Platform of this bug is "Windows 10".
If you want the exact clone of Chrome UI, just use Chrome.
|
|
Reporter | |
Updated•3 months ago
|
|
|
||
Updated•3 months ago
|
|
|
||
Updated•3 months ago
|
|
|
||
Updated•3 months ago
|
|
|
||
Comment 14•3 months ago
|
||
(In reply to Masatoshi Kimura [:emk] from comment #11)
I don't understand what is this bug (and dependencies) about. Why does our scrollbar UI have to be exactly same as Chrome? Do we have any WHATWG specs about the scrollbar UI that we do not comply with? Do those differences cause actual usability problem?
https://github.com/webcompat/web-bugs/issues/125737 says bugs.mojang.com is unusable. But same for all other dependencies? That is, are Instagram, Facebook, Netflix, Discord, and Bing really unusable due to the scrollbar UI difference? Moreover, https://github.com/webcompat/web-bugs/issues/125737 is reported on Linux according to the reporter, but the Platform of this bug is "Windows 10".
Hi Masatoshi. These bugs were collected during an exploratory QA testing on top sites. The purpose is to track all differences, but we're mainly interested in -webkit-scrollbar related ones (for example bug1841831, bug1885157, bug1885131). It's hard to pinpoint an exact root cause during QA testing, so we try to collect them all for further investigation. As for minor visual difference in scrollbars it is indeed a product choice and doesn't affect usability of the site, so those bugs are not actionable for now, unless we get reports from real users. Hope that answers your question.
As for the issue described in https://github.com/webcompat/web-bugs/issues/125737, I can't seem to reproduce it, so perhaps something has changed on the site, i.e. they've moved platforms for tracking bugs.
Description
•