Chrome 108 beta - Chrome Developers
I think this might be the most excited I’ve been in quite some time about an update to browser support, which probably says a lot about my priorities:
Support for the
avoidvalue of the CSS fragmentation propertiesbreak-before,break-after, andbreak-insidewhen printing.
Finally!
Related links
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.
Better typography with text-wrap pretty | WebKit
Everything you ever wanted to know about text-wrap: pretty in CSS.
Building WebSites With LLMS - Jim Nielsen’s Blog
And by LLMS I mean: (L)ots of (L)ittle ht(M)l page(S).
I really like this approach: using separate pages instead of in-page interactions. I remember Simon talking about how great this works, and that was a few years back, before we had view transitions.
I build separate, small HTML pages for each “interaction” I want, then I let CSS transitions take over and I get something that feels better than its JS counterpart for way less work.
Why I Like Designing in the Browser – Cloud Four
This describes how I like to work too.
Related posts
Making the website for Research By The Sea
Having fun with view transitions and scroll-driven animations.
content-visibility in Safari
Safari 18 supports `content-visibility: auto` …but there’s a very niche little bug in the implementation.
Workaround
Browsers and bugs.
Control
Trying to understand a different mindset to mine.
CSS Day 2022
Excellent as always.