Modern CSS Code Snippets: Stop writing CSS like it's 2015

Post by agos » Mon, Feb 16, 2026, 2:50 PM UTC

xnx wrote: post #217

IgorPartola wrote: post #61

Earlier quoted context omitted.

I was recently doing some very specific web scraping of some very public very static documents. About 25% of them use a soup of divs with hashes for class names. Not a or or in sight. I am fine with the idea of what tailwind does but like at least using semantic tags where appropriate could be a thing.

Wait until sites start rendering to canvas. You will yearn for the days of div soup.

Post by lovegrenoble » Mon, Feb 16, 2026, 2:57 PM UTC

Post by agos » Mon, Feb 16, 2026, 3:01 PM UTC

bobthepanda wrote: post #137

halfcat wrote: post #99

Earlier quoted context omitted.

Cognitive load of looking at 12 open files trying to understand what’s happening. Well, in fairness some of those 12 are the same file because we have one part for the default CSS and then one for the media query that’s 900 lines further down the file.

Css modules gets away from the larger sins of the massive global css files. If modules had existed much earlier it probably would’ve gotten rid of most of the awfulness.

Post by agos » Mon, Feb 16, 2026, 3:07 PM UTC

m-schuetz wrote: post #174

josephg wrote: post #82

Earlier quoted context omitted.

Yeah a lot of these demos say the features are widely available, but they don't actually work in my browser (Firefox on Macos). Makes me wonder if these demos (or the browser support tables) were made by LLMs. They clearly haven't tested the demos in firefox.

Firefox is pretty irrelevant nowadays. They've dragged their feet for years when it comes to implementing new stuff, and now web devs don't even bother checking Firefox. Because devs know it won't work on ancient browsers, no need to confirm. My personal trigger events were when Firefox didn't optimize DataView for the longest time, initially refused to implement import maps, and couldn't get WebGPU support done. At…

Post by zelphirkalt » Mon, Feb 16, 2026, 3:18 PM UTC

maxloh wrote: post #107

josephcsible wrote: post #87

I dislike the examples here where the "old" way works in all browsers, but the "new" way only works in Chrome/Edge. IMO, it's irresponsible to include such examples, since it makes the Blink monoculture worse.

This site shouldn't be the one to blame. Instead, we should probably ask Mozilla to be more standards-compliant.