Better typography with text-wrap pretty | WebKit
Everything you ever wanted to know about text-wrap: pretty
in CSS.
So much ink spilled supposedly explaining what “the web platform” is …when the truth is you can just swap in the “the web” every time that phrase is used here or anywhere else.
Anyway, the gist of this piece is: the web is good, actually.
Everything you ever wanted to know about text-wrap: pretty
in CSS.
Some interesting experiments in web typography here.
It would be much harder for a 15-year-old today to View Source and understand the code structure that built the website they’re on. Every site is layered with analytics, code snippets, javascript plugins, CMS data, and more.
This is why the simplicity of HTML and CSS now feels like a radical act. To build a website with just these tools is a small protest against platform capitalism: a way to assert sustainability, independence, longevity.
It’s a shame that the newest Safari release is overshadowed by Apple’s shenanigans and subsequent U-turn because there’s some great stuff in there.
I really like what they’re doing with web apps added to the dock:
Safari adds support for the
shortcuts
manifest member on macOS Sonoma. This gives you a mechanism in the manifest file for defining custom menu commands that will appear in the File menu and the Dock context menu.
This is a good description of the appeal of HTML web components:
WC lifecycles are crazy simple: you register the component with
customElements.define
and it’s off to the races. Just write a class and the browser will take care of elements appearing and disappearing for you, regardless of whether they came from a full reload, a fetch request, or—god forbid—adocument.write
. The syntax looks great in markup, too: no more having to decorate withjs-something
classes or data attributes, you just wrap your shit in a custom element calledsomething-controller
and everyone can see what you’re up to. Since I’m firmly in camp “progressively enhance or go home” this fits me like a glove, and I also have great hopes for Web Components improving the poor state of pulling in epic dependencies like date pickers or text editors.
Safari 18 supports `content-visibility: auto` …but there’s a very niche little bug in the implementation.
Don’t replace. Augment.
Responses to my thoughts on why developers would trust third-party code more than a native browser feature.
I’m trying to understand why developers would trust third-party code more than a native browser feature.
2022 was once unimaginable to some web folks.