My take: yes, just use logical properties all the time. If you need an answer with zero nuance, there it is. You’ll be better off and make better websites for people if you just entirely switch as often as you can. There is some nuance, though, and plenty of pushback.

When I tried setting my browser font-size preferences, I found it broke more sites than it improved, and I quickly moved back to the default. So what went wrong, and how can we fix it?

Now, to be clear, I’m not suggesting some kind of long-running mass hallucination. I’m suggesting CSS resets don’t do what the name says. The word “reset” implies an objective default state that you’re restoring to, but the only objective default state is what browsers ship. You cannot “reset” browser styles by addition. Resets are inherently subjective, which means in practice, you are not so much resetting as you are defining default element styles for a website.

JavaScript bros would be shocked how far custom elements can take you at a fraction of the cost. But they’re too busy gaslighting themselves into believing a VC funded nightmare is essential. We know better!

Did you know that there’s a new CSS feature that lets you very easily create trackable table of contents? This “scroll-spy” effect can be achieved with a new CSS property called scroll-target-group combined with the :target-current pseudo class.