for people who want to go deeper on stuff like the box model and specificity and selectors, i highly highly recommend Una Kravets and Adam Argyle's The CSS podcast https://pod.link/thecsspodcast - they are the two CSS devrels from google and they really break it down in depth while explaining things in an accessible way. no vested relationship, just a fan.
Things I wish I’d known about CSS
11–20 of 340 posts
Re: Things I wish I’d known about CSS
#12- One of the biggest traps for smart engineers is optimizing a thing that shouldn't exist.
(c) Elon Musk, speaking about CSS (maybe)
Re: Things I wish I’d known about CSS
#13> Using pixels (px) is tempting because they’re simple to understand: declare font-size: 24px and the text will be 24px. But that won’t provide a great user experience, particularly for users who resize content at the browser level or zoom into content.
Pixels (px) in CSS are relative as well, and scale with zoom. What is the benefit of em/rem?
Re: Things I wish I’d known about CSS
#14Cached URL since the server is apparently over capacity: https://webcache.googleusercontent.com/search?q=cache:jcSTVF...
Now on http://archive.is/AiECQ
Re: Things I wish I’d known about CSS
#15This is actually really nice. I've worked with CSS for a long while with the "Stackoverflow it until it works" philosophy, so some of these things (e.g. margin collapses) I had no idea about.
Re: Things I wish I’d known about CSS
#16> Using pixels (px) is tempting because they’re simple to understand: declare font-size: 24px and the text will be 24px. But that won’t provide a great user experience, particularly for users who resize content at the browser level or zoom into content. Pixels (px) in CSS are relative as well, and scale with zoom. What is the benefit of em/rem?
>What is the benefit of em/rem?
They (em*) scale with the element's font size, and if you set an elements font-size itself in em, that will be relative to the parent element's font size.
For example:
body { font-size: 18px }
.something { border: 0.1em solid black; }
.something > .inner { font-size: 1.5em }
The biggest limitation to this approach is that you can easily end up with computed values that are weird fractions of pixels, so you have to be a bit smart and pick an easily divisible number for your base font-size if you're aiming for something pixel-perfect.
Re: Things I wish I’d known about CSS
#17Useful article.
Getting started with CSS must be harder these days than it was 15-20 years ago. Not only for mobile-friendliness, but also because of the coexistence of flexbox/grid/traditional layouts. I'm wondering if the standard will ever been simplified, instead of being added more and more features.
Re: Things I wish I’d known about CSS
#18I wish the author had gone a bit further into em vs rem. I'm reading other articles on the topic but they're simply technical explanations and I'm still not clear on what features of the page are best designed using em or rem.
Re: Things I wish I’d known about CSS
#19Anybody knows a good book on CSS for ppl with a solid programming background? Every couple of years I try something and fail. Somehow the tutorial rave about the cascading on and on, and when it comes how to strategically design a good SAP working on different devices the stuff gets mute quickly.
Re: Things I wish I’d known about CSS
#20This is content marketing done right. I really don't mind that this article is there to promote the book when it actually offers some value to the reader (I actually learned a new thing, nth-child and nth-of-type)