News for hackers. Stuff that matters.
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by afiori on Sunday February 15, 2026 @04:39PM (#47027848)
Without a lot of discipline it is very easy to end up with a css with lots of unclear and hard to guess effects. Eg consider the case of <A type=1><B><A type=2></A></B></A> where A and B are complex templates. Any selector with the " " operator on A risk expanding to the inner A even if it was intended only for the outer. Similarly a :has selector might catch a descendant of the wrong element.

@scope fixes a lot of this, but it is a complex problem. With tailwind you mostly have to worry about inheritance

Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by robertoandred on Sunday February 15, 2026 @05:08PM (#47028161)
This problem was solved a long time ago with CSS Modules.
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by christophilus on Sunday February 15, 2026 @06:00PM (#47028643)
I prefer almost anything to CSS modules, so this bike shedding topic is probably very subjective.
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by the_other on Monday February 16, 2026 @04:37AM (#47032924)
> Any selector with the " " operator on A risk expanding to the inner A even if it was intended only for the outer.

Then <a type=b> is potentially a <c>. Consider a small refactor?