However, there are big questions still being asked about how CSS should handle masonry-style layouts. Some people remain skeptical that this capability should be part of CSS Grid, and want it to instead be its own separate display type. Others are questioning whether or not this kind of layout is needed on the web at all — they aren’t sure that well-known websites will use it. With such fundamental disagreements at play, no browser can ship. We must first come to consensus in the CSS Working Group.

This is where we need your help. We’d like real-world web designers and developers to weigh into the discussion, and express what it is that you want. Your input really can make a difference.

To link different elements in columns, my component relies on heavy JavaScript calculation. Here’s that example. While I love solving a math problem here and there, I prefer browsers doing these kinds of calculations for me! Let’s take a look at CSS Anchor Positioning and see how it might have a solution for us.

Being reminded of the visually hidden debate hasn’t been the only thing that happened to me on this year’s CSS Naked Day. I’ve observed that on pretty much all the sites I’ve visited, dark mode was rather absent after the styles had been removed. This got me thinking, maybe it’s time to talk about the six levels of dark mode.

Campfire was built with vanilla CSS, fully #nobuild without compiling or preprocessors, and uses the latest web platform features available in evergreen browsers—CSS nesting, :has(), :is(), and :where(); wide-gamut colors, View Transitions and more. In this post we’ll take a look at how we’re using some of these features and share some helpful patterns discovered along the way.

But things can go wrong, leaving an element that appears to not respect the aspect-ratio. For example, by setting both width and height, or if a flex layout causes the element to stretch, or if the contents are too large for the aspect ratio.