una.im | Updates to the customizable select API
It’s great to see the evolution of HTML happening in response to real use-cases—the turbo-charging of the select
element just gets better and better!
A thorough and compelling demonstration of why it makes sense to size all the properties of your components—font size, margins, borders, etc.—in ems or rems rather than mixing in pixels for some properties. It’s all about the scalability, innit?
It’s great to see the evolution of HTML happening in response to real use-cases—the turbo-charging of the select
element just gets better and better!
CSS wants you to build a system with it. It wants styles to build up, not flatten down.
Truth!
Trys describes exactly the situation where you really do need to use the Shadow DOM in a web component—as opposed to just sticking to HTML web components—, and that’s when the component is going to be distributed and you have no idea where:
This component needed to be incredibly portable, looking great on any third-party website, in any position, at any viewport, with any amount of content. It had to be a “hyper-responsive” component.
Laying out sheet music with CSS grid—sounds extreme until you see it abstracted into a web component.
We need fluid and responsive music rendering for the web!
Another terrific interactive tutorial from Ahmad, this time on container queries.
You might want to use `display: contents` …maybe.
The joy of getting hands-on with HTML and CSS.
Trying to understand a different mindset to mine.
I’m trying to understand why developers would trust third-party code more than a native browser feature.
An exception to my general rule that ARIA attributes should be added with JavaScript.