Earlier quoted context omitted.
I get that I'm critiquing you within your apparent wheelhouse, but this aesthetic also matters a lot to me. img[data-astro-cid-vnzlvqnm] { width: 48px; height: 48px; image-rendering: pixelated; object-fit: contain; margin-bottom: 0.5rem; } I understand the goal here, but it works really poorly IMO when the source images are generally 32x32 (and some of them are smaller to arbitrary degrees because the content has bee…
As I mentioned, images are the hardest to do because beyond the core icons, the available graphics vary massively in size. Displaying them at "actual size" makes them far too small to be usable on a modern screen. I think you're also probably misremembering the scale of the cursor. It's not perfect, but it's not meant to be 16x16. Take a look at https://hcsimulator.com/ The approach I took is the best I could manage…
Man, I have ancient (er, well, that's a bit awkward in context!) stuff, I know. But these things are still just fine at ~96dpi IMO.
> I think you're also probably misremembering the scale of the cursor. It's not perfect, but it's not meant to be 16x16.
I recall 16x16 cursors (System 6 CURS resource) and 32x32 icons, so I expect the cursor to be visually 1/2 the height/width of the icons. You have it effectively at 2/3.
> on a Mac retina display
These basically don't exist in my world. But again (or maybe I was unclear?), @media queries can check for dpi and not just viewport size.