CSS :where() to replace complex multi-selectors

As humans we think in silos. Scrum Masters often don’t know what an Engineering Manager is, Engineering Managers don’t care about Scrum Masters. But both have their own focus, their very own strengths to create a resilient team. See how important it is to stay open minded enough to see the benefits of other roles, no matter the job title. The...

The fun part of being someone with two jobs in completely different areas. Nearly all of the algorithms of these fancy platforms backed with billions of money don’t work. LinkedIn for example is smart enough to realize both of my work categories (web development, agriculture/gardening) but fails to provide a proper feed, a mixture of network...

Today I learned that the CSS readonly attribute for form fields does only work with input modes that allow variable user input that’s not “type-safe”: The attribute is not supported or relevant to or types that are already not mutable, such as checkbox and radio or cannot, by definition, start with a value, such as the file input type. range...

Today I learned that the CSS :empty selector is implemented to look for child content (think of innerText/innerHTML). This means it reports empty for filled form elements which are self-closing elements. Findings :empty reports empty for all form input elements because they have their values as attributes, not as inner content :empty works for ...

I’ve recently wrote about the usage of the universal :where() selector. Now let’s clear up when to use :where() and when :is(). For a quick repetition to what we’re talking about, see these selectors: .text :where(h2, h3, h4) {} /* vs. */ .text :is(h2, h3, h4) {} First of all, :where() and :is() both are forgiving selectors. This means that even...