The “Promises” API is a surprisingly tricky part of modern JavaScript. Without the right context, it doesn’t make much sense at all! In this tutorial, you’ll build an intuition for how Promises work by getting a deeper understanding of JavaScript and its limitations.

Some developers say they want to use container queries now but think they can't because they still have to support older browsers. As you may have guessed from the title, we think it's possible for most developers to use container queries now—in production—even if you have to support older browsers. This post walks you through the approach we recommend to do that.

Today on Mastodon, Nils asked how to detect support for @property. While in theory you could use @supports at-rule() for this, in practice you can’t because it has no browser support. Thankfully, there’s a workaround … by trying to actively use registered custom properties and style things based on the outcome.

When you link to any resource on a domain you don’t control, it’s a risk. It’s entirely possible that a resource you link to from a third-party disappears or changes. Worst case: changed maliciously, like we’ve seen here.

How do people who cannot move their arms use your website? What about people who cannot see well or at all? Or people who have difficulty hearing, or understanding, or have other disabilities?