Nested tables and inline styling yeah. It works better. It's always worked better, unless you're handwriting your HTML, and virtually no-one does that anymore.

I still remember the star selector pattern to prevent IE6 from reading malformed css. So me old.

But having grown up in my early career during the transition from embedding styles into html to sites like css zen garden, I am extremely critical of modern "frameworks".

I still see so much bloat in poor performing pages and often when I dig deeper it's tailwind in addition to other inefficiencies adding repeated cruft that doesn't help with site rendering.

A proper 20 year old understanding of css class style inheritance isn't hard, and it negates 80-90% of the complexity of maintaining complex web apps (react components mainly).

CSS grids are cute and useful, but for a hell of a lot of web interfaces a simple float and clear:left still works wonders.

But yes you can have "bonkers" devicePixelRatio. Namely, when the browser is zoomed.

Logical pixels measure UI "size." And Physical pixels (logical pixels * devicePixelRatio) is the number of dots.

Your game layout should target logical pixels. And rasterization, textures, etc should target physical pixels.

If weird devicePixelRatio causes problems with a lot of pixel-exact UI, you may choose to use your own logical pixels that has a rounded devicePixelRatio.

---

I have a MacBook with a retina display. Versus a non-retina display, I would not expect that everything is 2x smaller, but rather 2x more detailed (or, if not that, the same level of detail but same size). That important distinction is reason for two different constants.