Open mirabilos opened 1 year ago
Willing to work on this issue , will raise a PR very soon
FWIW I've disabled "rc-scrollbars" by using this in Workspace -> Settings -> Layout -> Custom CSS
.rc-scrollbars-view { margin-right: 0px !important; }
.rc-scrollbars-track { display: none !important; }
jazztickets dixit:
FWIW I've disabled "rc-scrollbars" by using this in Workspace -> Settings -> Layout -> Custom CSS
.rc-scrollbars-view { margin-right: 0px !important; } .rc-scrollbars-track { display: none !important; }
OK, and how do I get the real scrollbars back?
Would fixing this help my issue at all? https://github.com/RocketChat/Rocket.Chat/issues/31717
On Mon, 28 Oct 2024, audouts wrote:
Would fixing this help my issue at all? https://github.com/RocketChat/Rocket.Chat/issues/31717
Possibly, but evidently rocketchat is actively disinterested in fixing basic accessibility issues and honouring standards.
On Mon, 28 Oct 2024, audouts wrote: Would fixing this help my issue at all? #31717 Possibly, but evidently rocketchat is actively disinterested in fixing basic accessibility issues and honouring standards.
That's frustrating. Our team really likes RocketChat but it's frustrating that we have to hunt for tiny pixels to use an essential UI element. Frankly, the scrollbar is already pretty narrow.
Description:
Rocket.Chat, which I am forced to use for work, does weird things to scrollbars. They are not visible until I attach an external mouse with wheel and move the wheel (making scrolling impossible for Thinkpad classic X-series, trackball or 2/3-button mouse users, which is severely broken UI); they are then almost invisible (almost black on almost black; bad for accessibility, I can barely see it as is) and react much too sluggishly. They are also missing the up and down arrows.
I do have a Firefox
userContent.css
that fixes scrollbars on almost all other sites, such as this GitHub issue entry form, to behave somewhat properly (dark rectangle on brighter track, with arrows that work, always visible), but somehow Rocket.Chat manages to override this despite the!important
in theuserContent.css
that’s supposed to prevent sites from doing just that.Steps to reproduce:
Expected behavior:
The standard browser scrollbar is used and visible by standard browser rules. Users who configure an accessible scrollbar can use them in the web application.
Actual behavior:
This… thing… seems to disable scrollbars, somehow, and draw its own. This is supposedly not possible, so it probably also overrides the
overflow
handling. Ugh. Major antifeature.Server Setup Information:
Client Setup Information