Better typography with text-wrap pretty | WebKit
Everything you ever wanted to know about text-wrap: pretty in CSS.
Once Upon a Browser
Browse through some truly web-native artwork by Eric, and read all about it:
There is a lot, and I mean a lot, of room for variability in web technologies. We work very hard to tame it, to deny it, to shun it.
Related links
Item Flow, Part 1: A new unified concept for layout | WebKit
I really like the idea of unifying some layout values in CSS. If you’ve got any feedback, please chip in!
Justified Text: Better Than Expected? – Cloud Four
Some interesting experiments in web typography here.
You can use Web Components without the shadow DOM
So what are the advantages of the Custom Elements API if you’re not going to use the Shadow DOM alongside it?
- Obvious Markup
- Instantiation is More Consistent
- They’re Progressive Enhancement Friendly
Hyper-responsive web components | Trys Mudford
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.
Related posts
content-visibility in Safari
Safari 18 supports `content-visibility: auto` …but there’s a very niche little bug in the implementation.
Making the Patterns Day website
The joy of getting hands-on with HTML and CSS.
Bugblogging
Also, tipblogging.
Suspicion
Responses to my thoughts on why developers would trust third-party code more than a native browser feature.
Trust
I’m trying to understand why developers would trust third-party code more than a native browser feature.