Better typography with text-wrap pretty | WebKit
Everything you ever wanted to know about text-wrap: pretty
in CSS.
Heydon does a very good job of explaining why throwing away the power of selectors makes no sense.
Utility-first detractors complain a lot about how verbose this is and, consequently, how ugly. And it is indeed. But you’d forgive it that if it actually solved a problem, which it doesn’t. It is unequivocally an inferior way of making things which are alike look alike, as you should. It is and can only be useful for reproducing inconsistent design, wherein all those repeated values would instead differ.
He’s also right on the nose in explaining why something as awful at Tailwind could get so popular:
But CSS isn’t new, it’s only good. And in this backwards, bullshit-optimized economy of garbage and nonsense, good isn’t bad enough.
Everything you ever wanted to know about text-wrap: pretty
in CSS.
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
.
- Springy easing with
linear()
- Typed custom properties
- View transitions for page navigation
- Transition animation for
dialog
andpopover
- Transition animation for
details
- Animated adaptive gradient text
Some interesting experiments in web typography here.
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 redesign with modern CSS.
You might want to use `display: contents` …maybe.
Separate your concerns.
Styling a document about The Culture novels of Iain M Banks.
Using the CSS trinity of feature queries, logical properties, and unset.