We can animate to `auto` now!


Hello Reader,

A day late with my newsletter this week, mostly because I completely forgot to write it last week!

I have a spot on my calendar for writing my newsletter, but I was really immersed in a project I’m working on and told myself that I’d do it later, and then I simply forgot 😅.

I’ll have some news on what that project is soon-ish, but since it’s Monday morning and I’ve got a few other things that need doing as well, let’s just jump into the main content!

📅 Mark your calendar

I’m going to be talking at JetBrains JavaScript Day 2024 edition this Thrusday.

It’s a remote conference and completely free!

As the name of the conference implies, it’ll be very JS heavy, with some really good talks lined up, but I’ll be there to play a bit of a spoiler with my talk You don’t need JavaScript for that.

Again, it’s a free event that you can register for here.

🙋‍♂️ What I’ve been up to this week

As I mentioned, a lot of my week was spent working on a project that I’m really excited about.

I almost started working on it again this morning because I’m so excited for it… but I have a lot of other things that need doing, so I’m doing my best to put it on pause for a little bit.

But I did have a regular video as well, and this one on interpolate-size: allow-keywords is one of the new CSS features that I’m so happy we finally have!

video preview

That’s right, we can animate to and from auto, and any other intrinsic size now.

Here's a CodePen with the code from the video if you want to play around with it (currently Chromium-only).

What I didn’t cover in the video was the also new calc-size() feature, which can take animating to and from auto to another level because we could use that to do calculations based on auto (and other intrinsic sizes).

Bramus’ article on the Chrome for Developers blog that introduced me to interpolate-size also goes into calc-size as well, if you’d like more info on both of them.

🏁

No stuff from around the web this week because I haven’t really been on the web much this past week.

It’ll be back next week though, when we’ll return to the regular Sunday schedule.

Until then, have a great week!
Kevin


Unsubscribe · Preferences
600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246

Hi! I'm Kevin

Weekly newsletter, where I talk about tangentially-related front-end development topics and share what I've been up to in the last week, plus any cool/fun/interesting/useful links I come across as well.

Read more from Hi! I'm Kevin

Hello Reader, Yesterday I told you about the mindset shift that changed everything for me, and how I started working with the browser instead of against it. I’ve spent a long time figuring out how to pass that same shift on to others, and that’s why I created CSS Demystified, which is now open for enrollment. Before I get into the details, I want to tell you why I built it the way I did. I spent five years teaching in a classroom before I moved to online education full-time. And the thing...

Hello Reader, Creating websites was a hobby of mine for a long time. I started making my first sites in the late 90s with Photoshop slicing, table layouts, and image maps. I never thought writing HTML and CSS would become such an important part of my life. After a wandering path of unrelated degrees, I ended up as a graphic designer at a small agency. I loved it, but the pay was terrible, so I started freelancing on the side as well, mostly designing websites. After a few jobs, I figured that...

Hello Reader, A couple of days ago, I talked about how CSS is designed for uncertainty, meant to adapt to unknowns. When we don’t think about it that way, we fight it. And when we fight it, things get messy fast. We add what seems like an innocent enough property, but it doesn't quite fix things the way we wanted, so we add another. Then another. Then another. By the end of it, somehow, everything is worse than when we started. Once again, there's a meme that does a good job of showing how...