Chris Coyier

Imagine transitioning a bunch of items all set into ONE cell of a grid, then each having a unique animation when they move from that cell into where they would naturally fall on that same grid.

There are folks that think Safari is the worst current browser. Safari is the new IE, they say. You wouldn’t have to convince Alex Russell who regularly points to the fact that there isn’t browser choice on iOS, which is direct fuel for the app store, so keeping the web down is a business strategy. […]

I love those three little dots in JavaScript. Mat Marquis has a nice article covering them (“destructuring” as it were) nicely. And agreed there are plenty of times they can be confusing. What always gets me is that sometimes it is used to “pluck off” the remaining the values from an array or object (which […]

There is an entirely web-platform way of injecting scoped CSS styles into the DOM. It’s requires zero tooling. Will we see it being used more, once Firebox support is there?

Alvaro Montoro has a great thread (and blog post) of a bunch of CSS value functions in “the first public draft of the CSS Values and Units Level 5 Module”. It can’t be overstated how powerful some of this stuff is going to be. The attr() stuff enables much more a powerful realtime HTML<>CSS connection. […]

There is a meta conversation of “Web Components are very definitely going to be around 10 years from now while any JavaScript framework today will not” is worth considering, but pits the two directly against each other when we really don’t need to.

After the big shakeup with masonry layout recently (Apple: Make it part of display: grid;! / Google: Make it display: masonry;! / Me: I’ve got questions and I’d rather see tabbing order issues fixed first), I was very keen to hear where it would go. It took 5 months, but we’ve got movement. The CSS […]

I love the Interop project. We’re a couple of years into it, and each year it worked just like it was supposed to: features are chosen, those features are implemented (or fixed up) across all browsers. Choosing the features is somewhat democratic, and submissions are open for 2025. Remember last year I measured the positive […]

They are pretty similar in both look and functionality, but are have some important differences, slightly different APIs, and functionality. The use cases are also a bit different, so let’s have a look!

We just looked at how “animate to auto” (e.g. transition from a fixed value to a keyword like auto, max-content, etc.) is “opt-in” in a sense. You have to use interpolate-size: allow-keywords; to make it work or use a function like calc-size(), neither of which you accidentally do. This is because research showed that it […]