CSS or BS?
We show you a CSS property name. You tell us if it’s real or if we made it up. That’s it. It starts easy. It does not stay easy.
Harry demonstrates a really good use for CSS custom properties—allowing users to theme an interface.
We show you a CSS property name. You tell us if it’s real or if we made it up. That’s it. It starts easy. It does not stay easy.
I’m slapping my forehead—progressive web components is a perfect name for what I’ve been calling HTML web components. Why didn’t I think of that?
A Progressive Web Component is a native Custom Element designed in two layers: a base layer of HTML and CSS that renders immediately, without JavaScript, and an enhancement layer of JavaScript that adds reactivity, event handling, and more advanced templating.
An excellent example of an HTML web component from Eric:
Extend HTML to do things automatically!
He layers on the functionality and styling, considering potential gotchas at every stage. This is resilient web design in action.
This looks like a really interesting proposal for allowing developers more control over styling inputs. Based on the work being done the customisable select element, it starts with a declaration of appearance: base.
This is a great little helper in understanding anchor positioning in CSS.
Make your links beautiful and accessible.
You might want to use `display: contents` …maybe.
Had you heard of these bits of CSS? Me too/neither!
Using the CSS trinity of feature queries, logical properties, and unset.
Let me hear your blocky talk.