Replies

• 

  Firefox for Web Developersfirefoxwebdevs@mastodon.social

  Jul 21, 2026, 1:35 PM

  @chriskirknielsen It's just for the main selector, although we avoid throwing errors on parsing the others with JS. Unfortunately we had to do this for compat. Here's some of the ugly details https://bugzilla.mozilla.org/show_bug.cgi?id=1977511

  As for messing with scrollbars, we support the web standard ways https://developer.mozilla.org/en-US/docs/Web/CSS/Guides/Scrollbars_styling

  💬 1🔄 0⭐ 0
• 

  Christopher Kirk-Nielsenchriskirknielsen@front-end.social

  Jul 21, 2026, 2:34 PM

  @firefoxwebdevs Hate to see it, but glad to see there's an escape hatch at least!

  The standard way is what I prefer, definitely! Though sometimes I'm given a design where I really have to mess with scrollbars like making them extra large (scrollbar-width: large, I yearn for thee) or inset into the element (crossing my fingers for `scrollbar-offset` to get implemented) so I cannot go the standard way, as much as I want to. 🫠

  💬 0🔄 0⭐ 0