You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's my first time posting an issue here so sorry if I'm doing something wrong.
In my opinion, scrollbars are pretty important and have been a really big issue for us developers for a long time. I just saw this spec for the 1st time and wondered: "Why is this spec related to container element properties? Isn't it better to push it as a new pseudo-element, following the ::-webkit-scrollbar non-standard spec?"
In that way, we could achieve cleaner code such as:
::scroll-bar{
...my style
}
instead of styling our scrollbars in every single element with the universal selector *.
As I see this spec is already in stage 1, I wonder if such a discussion has already taken place and, if it did, why did the csswg go in the properties direction.
The text was updated successfully, but these errors were encountered:
https://drafts.csswg.org/css-scrollbars-1/
It's my first time posting an issue here so sorry if I'm doing something wrong.
In my opinion, scrollbars are pretty important and have been a really big issue for us developers for a long time. I just saw this spec for the 1st time and wondered: "Why is this spec related to container element properties? Isn't it better to push it as a new pseudo-element, following the ::-webkit-scrollbar non-standard spec?"
In that way, we could achieve cleaner code such as:
instead of styling our scrollbars in every single element with the universal selector
*
.As I see this spec is already in stage 1, I wonder if such a discussion has already taken place and, if it did, why did the csswg go in the properties direction.
The text was updated successfully, but these errors were encountered: