6 ms·

This is about CSS.

• mjevans 5y ago
  It is also about pixel-perfect madness. Please just don't. Make things that scale, make things that adjust, and tolerate end users that have different fonts and size preferences.
  • tudorw 5y ago
    quite, we've been travelling backwards in accessibility terms for a while.
  • jan_Inkepa 5y ago
    I don't know where you're coming from. It's not about pixel-perfect madness that I can see? It's about drawing a box? Wanting to draw a neat box around text is a reasonable thing to want to do. Know how fonts behave and being able make websites look how you want is a legit part of a designer's toolkit, I'd say. Is your problem that the designer didn't add an extra layer of pixel->some-other-unit conversion on top of everything else? (But in browser pixels are also abstract entities ('logical pixels') not related to screen pixels anymore for the most part, which are deeply hidden away and basically inaccessible last time I checked (3 or so months ago)). But for instance, towards the end the writer says: 'The next time somebody complains about paragraphs having inconsistent spacing when the font changes, I’ll know why and how to fix it.'. So, it looks like they care about h [ I can't check out his example on my current device, so I don't know if it's scale/custom-css compatible or not. ]
    • Kwpolska 5y ago
      The box is just an example, the real subject of the post is the list under “A few consequences with how CSS does its thing”. And all those examples really are pixel-perfectness (pixel-perfect text boxes, pixel-perfect alignment of different fonts, pixel-perfect vertical centering of text in a button).