Because I haven't published anything to it since August 31. And no one else has either. That's not a super long time to go silent but it is for a site that

Safari TP 252 trials named-feature() and user-select.

Firefox 157 (Nightly) ships overscroll-behavior: chain.

Chrome 153 becomes the first to implement scroll-axis-lock, , and .

Chrome 155 (Dev) implements random() (also available in Safari) as well as symbols() (in Firefox).

Chrome 155 (Dev) implements margin-trim, following Safari.

Firefox 155 implements progress(), now Baseline.

Firefox 155 ships alpha() and advanced attr(), which Chrome also supports (Safari to follow soon).

The journey to create a polyfill for the upcoming CSS random() function that works in all browsers.

Well, that’s a wrap. No, not a flex-wrap, but rather today marks a new day, week, month, season, aaaand new edition of What’s important (#18), bringing you the best content that developers have produced over the last couple of weeks or so.

Safari TP 251 trials comma-separated @container queries in addition to popover=hint.

Safari TP 251 trials corner-shape, object-view-box, at-rule(), ident(), inherit(), random(), and random-item().

The general idea is that we create a Document Picture-in-Picture window (DPIP window), and then we put HTML, CSS, and JavaScript into it.

Chrome 152 ships the autocorrect HTML attribute, making it Baseline, and the alpha() CSS function (Safari and Firefox are to follow shortly).

Syntax highlighting for code blocks without the complicated markup, spans, classes, and bloated JavaScript, courtesy of Uncle Dave.

A newly resolved proposal would allow us to select classes that are a prefix for variations with a wildcard, like .prefix-*.

As someone who teaches beginning web development, I find that building a WordPress site makes for a great final project to demonstrate the myriad skills covered over the course of a semester — HTML, CSS, design, hosting, etc. Hosting those projects has always been a roadblock though.

Apply a style when someone navigates from one specific page to another. The idea being it'd make the sources for cross-document view transitions declarative in CSS rather than managing that stuff in JavaScript.

Firefox 154 ships sibling-count(), sibling-index(), text-box-trim, text-box-edge, and text-box, which are now Baseline.

Lea's pushing back on light/dark mode implementations that display three state options for visitors: light, dark, and system.

Plus, how to style skeleton UIs, how to enable diagonal scrolling, how images can overflow themselves, and yet, still more. Basically, how to do a lot of really cool (CSS) stuff.

Chrome 154 (Dev) trials frame-sizing (for responsive iframes).

The warning is correct. And the recommended fixes you've probably seen are wrong. Here's what you can do instead to properly fix the issue.

There's a lot of nuance to the <dialog> element, a seemingly little piece of web architecture. I've got some notes from digging into it.

I’m Wilto, from websites.

Today, with CSS gap decorations fully supported in Chrome and Edge, starting with version 149, you can now very easily style gaps, and with a lot of control.

Similar to last time, What’s !important #15 is pretty stacked — read all about boundary-aware CSS, making grid lanes accessible, creating time-based web designs, fixing full-bleed CSS, improving customizable select, new web platform features, and more.

We recently got the shape() function and corner-shape property. What else could we possibly need as far as making shapes in CSS? Let me tell you: the border-shape property!

Firefox 154 (Nightly) will ship text-box, text-box-trim, and text-box-edge, making them Baseline.

Safari TP 247 becomes the first to trial calc-mix(), which returns a progress point between two values.

Chrome 150 becomes the first to ship animatable zoom, flex-wrap: balance, overscroll-behavior: chain (chaining with no overscroll), named-feature(), corner rounding for polygon(), and finally, the focusgroup attribute.