Swizec Teller - a geek with a hatswizec.com

Senior Mindset Book

Get promoted, earn a bigger salary, work for top companies

Senior Engineer Mindset cover
Learn more

    CSS classes don't work the way you think they work

    This is some text

    Which color is this text going to be?

    No cheating, give it a think ??

    .

    .

    .

    .

    Blue. The answer is blue. ?

    Look. I’m not lying. It’s really blue.

    You can use any permutation of blue green red – the text is still blue. Try it! Edit the codepen. Play around :)

    Did you find the pattern?

    CSS classes apply in the order in which they are defined, not the order in which they are invoked. This is not intuitive.

    Look: if you switch around the CSS rules, the text becomes red.

    Same HTML, same CSS classes, different order of definitions. Try it; change the code.

    Maybe this is obvious to everyone but me, but I spent an embarrassing amount of time yesterday and today debugging some React components. It hits you when common components have default styling, and you want to override it in a specific instance.

    const P = ({ className, children }) => (
        <p class="{`italic" blue="" ${classname}`}="">{children}</p>
    ); // default P
    
    // ...
    
    const Error = ({ errorText }) => (
        <p class="red">Red error!</p>
    ); // doesn't become red
    

    The generic P component returns a <p> element with an italic and a blue class. You can expect text to be italic and blue by default.

    Please don’t do that in real life. This is just an example.

    It takes a className prop so you can extend classes used.

    But when you use the Error component, which produces <p class="italic blue red">Red error!</p>, it’s not red. It’s blue because your CSS defines .red first and .blue second.

    ?

    There is no workaround. This is expected behavior. The relevant part of W3C spec makes no mention of HTML attribute ordering.

    How did I go 15 years without ever noticing? ?

    Published on October 21st, 2016 in Front End, Technical

    Did you enjoy this article?

    Continue reading about CSS classes don't work the way you think they work

    Semantically similar articles hand-picked by GPT-4

    Senior Mindset Book

    Get promoted, earn a bigger salary, work for top companies

    Learn more

    Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.

    Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.

    Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help πŸ‘‰ swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.

    Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers πŸ‘‰ ServerlessHandbook.dev

    Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization

    Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections

    Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog

    Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❀️

    Created by Swizec with ❀️