Adrian Roselli, pH0Where @eric is more direct in his scrollbar post than I was in my 2019 writing:
“Don’t use custom CSS scrollbars”
https://ericwbailey.website/published/dont-use-custom-css-scrollbars/
hörb@burnandtremble
The difference here is that scrollbars are a major built-in affordance that the OS typically handles. IE allowed styling and then it (thankfully) went the way of animated cursors shortly after the turn of the century.
Eric points out that even when best practices are available, devs are still breaking fundamental platform features.
So, to answer your question, no it is not.
@eric
@burnandtremble
The button element is included in automated checks, so at least linters, in-browser tools, etc. can catch it.
@eric
The button element is included in automated checks, so at least linters, in-browser tools, etc. can catch it.
@eric
Eric@burnandtremble I don't feel compelled to answer questions not asked in good faith. Sorry you got big mad.
@eric @aardrian I am not mad at anyone. I don't think the article is good guidance (but it's also not my article)—I believe a "think twice (or 3x, or 4x) if you think you want to style your scrollbars with CSS today" would be a lot more constructive. The web will move on either way, which I tried to give examples for.
@burnandtremble Maybe then you blog about it instead of harassing folks with your mediocre takes.
@eric @aardrian I don't blog, but I filed an internal bug against Chrome for broken hover styles on scrollbars five days ago. #iamdoingmypart I guess?
@eric @aardrian Thank you, that's very kind. What I am trying to say is: we likely care about the very same thing—an accessible web for everyone—but we have different opinions on whether that means more "regulation" on what you should even attempt to do visually or instead better tools to make it easier to do the right thing while still allowing an individual website to move on from the equivalent of <button> ca. 2003.
@burnandtremble
If you read my post you would see I made a list of things to consider. So if Eric’s title is too off-putting, read my less detailed four-year-old post.
@eric
If you read my post you would see I made a list of things to consider. So if Eric’s title is too off-putting, read my less detailed four-year-old post.
@eric
@aardrian @eric To clarify: my concern was also not with the majority of content in Eric's article, which highlights a lot of pitfalls in a helpful way. I think the conclusion and the headline detract from that, I gave that feedback through a pointed question (though not in "bad faith") and forgot that the internet and especially microblogging doesn't transport that super well.