Web development Blog

In all previous posts about cascade layers I’ve used named layers in the demos, but it’s actually not required to name them.

Support for a CSS property isn’t the only thing you can check with @supports(), you can also check support for a selector.

On day 47, I introduced you to the overscroll-behavior property, and I showed you how to use it to disable scroll-chaining. There’s another feature we can disable using this property.

On day 46, I’ve explained how you can order layers by defining them in a comma-separated list first. The first layer in the list has the lowest priority and the last layer the highest.

Most elements have no preferred aspect ratio. On day 42 I’ve explained how you can use the aspect-ratio property to define a ratio for these elements. Replaced elements like <iframe>, <video>, <embed>, or <img>, on the other hand, have an intrinsic aspect ratio. This means that you don’t have to define one using the aspect-ratio property and they will scale naturally.

Something I was tripping over when I began learning about :has() was the combination with :not().

You can use @import to load entire style sheets into a cascade layer.

On day 9 I’ve talked about the inset shorthand properties inset, inset-inline, and inset-block. I don’t believe that I will need those often, but inset can come in handy when you want one element to fill another element entirely.

You can use the overscroll-behavior property to disable scroll-chaining.

By default, cascade layers are stacked in the order they are defined, but you don’t have to rely on it. You can determine the order in one place.