CSS Nesting

I don't have any data to support it, but I would imagine one the most highly anticipated CSS features is now officially supported in all major browsers. Selector nesting is one of those features that made a preprocessor like SASS absolutely necessary a few years ago.

In case you're not familiar, CSS nesting allows you to write css like this example from Wes Bos:

I'm excited to these feature widely available, but it's kinda bittersweet because I rarely write raw CSS anymore 😆️. In any case, it's a huge plus and good to see CSS moving forward.

CSS nesting - CSS: Cascading Style Sheets | MDN

The CSS nesting module defines a syntax for nesting selectors, providing the ability to nest one style rule inside another, with the selector of the child rule relative to the selector of the parent rule.

MDN Web Docs

Observable API Proposal

Speaking of exciting features, this proposal for a native Observable API would certainly be one to celebrate. If you've ever used RxJS, this proposal is essentially the same idea. Native Observables would make it much easier to do complex event handling when compared to the addEventListener function used today. The README linked below has some excellent examples and explanations of how Observables would work. Check it out!

GitHub - domfarolino/observable: Observable API proposal

Observable API proposal. Contribute to domfarolino/observable development by creating an account on GitHub.

GitHubdomfarolino

Baseline

A couple phrases I've already used often in the first two issues of this newsletter is "wide support" or "supported in all major browsers". The Baseline initiative will make it easier to communicate scenarios like this were a feature is widely supported. In the future, I can simply write that a feature is "part of Baseline"

Introducing Baseline

At Google I/O 2023 we announced Baseline, learn more about this initiative and why we think it’s important.

web.devRachel Andrew

Web Components

I remember web components were initially released, I was surprised when teams actually adopted them instead of using a framework. They never felt like they were on solid footing to me, and that's a feeling that's stuck with me to this day. This article goes into some mistakes that were made in the early days of web components, and how things have improved and are continuing to improve today.

If Web Components are so great, why am I not using them?

Rem recently asked:

Dave RupertDave Rupert

Thanks for reading!

In case you missed it, I published a blog post this month about using the Adapter Pattern in React. Check that out here.

Lastly, if you enjoyed this issue, consider subscribing!