{"id":376858,"date":"2023-08-14T12:48:12","date_gmt":"2023-08-14T11:48:12","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=webstorm&p=376858"},"modified":"2023-08-14T13:48:15","modified_gmt":"2023-08-14T12:48:15","slug":"css-nesting","status":"publish","type":"webstorm","link":"https:\/\/blog.jetbrains.com\/webstorm\/2023\/08\/css-nesting\/","title":{"rendered":"Exploring the Power of CSS Nesting: Simplifying Styling and Enhancing Readability"},"content":{"rendered":"

Imagine you\u2019re making a navigation menu \u2013 a panel with some boxes. Some of the styling goes in the panel (the parent), while some goes in the menu item (the child.) As easy as it is to describe this parent-child relationship verbally, it\u2019s surprisingly difficult to describe it in CSS code.<\/span><\/p>\n

Well, not any more<\/span>! With CSS Nesting<\/a>, nested styling is now powerful, easy, and native. Let\u2019s take a look at this new capability and how you can use it in the latest version of WebStorm.<\/span><\/p>\n

Background<\/h1>\n

You might be wondering why CSS Nesting sounds familiar to you, and why you feel like you\u2019ve used it before.<\/span><\/p>\n

Indeed, popular CSS-preprocessor tools like SCSS and LESS have supported this feature for quite some time. Now, CSS Nesting is not only supported by separate tools, it is even an officially recognized feature in the <\/span>CSS Specification<\/a>. The specification was not only motivated by the popularity of this feature in tools like SCSS and LESS, but also because it vastly reduces duplication and heavily improves the readability and maintainability of CSS code.<\/span><\/p>\n

CSS Nesting support landed in Chrome Stable in March 2023, and WebStorm introduced support for it with its next major version, 2023.2. Since this feature is relatively new, we want to discuss the capabilities of CSS Nesting and what it lets you do as a developer.<\/span><\/p>\n

What is CSS Nesting?<\/h1>\n

As the name suggests, this feature lets you nest CSS selectors and, therefore, group related styling. Let\u2019s assume we want to style a button and we also want to style the hover effect of that button.<\/span><\/p>\n

Usually, you would write CSS rules as separate scoped definitions, based on a given selector. Adding a hover effect to the already-styled element requires you to reselect that given element and add the pseudo-class:<\/span><\/p>\n

\"CSS<\/p>\n

But CSS Nesting lets you repurpose the element selector and nest the hover selector. This enables you to write your code more like this:<\/span><\/p>\n

\"CSS<\/p>\n

No more redundantly specifying the parent selector! Using CSS Nesting lets us group the styling and, therefore, implicitly refer to the parent selector.<\/span><\/p>\n

Want to go further? You can also nest your CSS code deeper, allowing more style specificity. Obviously, with great power comes great responsibility, so don\u2019t overdo it. By default, the SASS Linting rule suggests keeping the maximum depth of nesting to 2, which is a good practice to follow.<\/span><\/p>\n

In some cases, nesting <\/span>might<\/span><\/i> also give a big reduction in code size. Instead of specifying the parent element over and over, nesting lets you remove that part from your code. <\/span> Looking at example 1<\/a> and example 2 <\/a>we can see that nesting lets us write more concise CSS code.<\/span><\/p>\n

Limitations<\/h1>\n

As of version 1 of the spec, you cannot have an element selector directly nested inside another selector:<\/span><\/p>\n

\"Error<\/p>\n

For this particular use case, the CSS Nesting Specification introduced <\/span> the &<\/code> selector<\/a>. The following characters indicate a nested selector to the CSS parser.<\/p>\n

\n
& @ : . > ~ + # [ *<\/pre>\n<\/blockquote>\n
This is why you don\u2019t need a special character when you nest classes, for instance, yet you do need one for HTML elements. But don\u2019t worry: If you forget, WebStorm and other JetBrains products have you covered. If you happen to run into this particular scenario, your IDE will suggest applying the `&` prefix, as you can see in the screenshot above. Note that at the time of writing this blog post, <\/span>there is an open bug<\/a> that requires the &<\/code> selector when using the universal selector *<\/code>.<\/p>\n
There is one more limitation, though. With CSS preprocessors, you can use nesting to concatenate selectors with the &<\/code> selector:<\/span><\/p>\n
\"Image
\nImage Taken from Sass Documentation<\/a>.<\/p>\n
This feature is extremely useful when using methodologies like Block Element Modifier<\/span> (BEM), <\/a>for instance. On the other hand, it\u2019s very ambiguous. It would be difficult for a parser to differentiate between a concatenated selector or a nested element selector, which could in theory also reference a custom element. Ensuring compatibility with existing web standards prevented this feature from landing in the specification.<\/span><\/p>\n
Version 2 of the specification is already being discussed, and this future update could further enhance the developer experience.<\/span><\/p>\n
Browser Support<\/h1>\n
For a feature whose official specification was released only 6 months ago, we already have decent browser support for CSS Nesting, particularly if you are targeting modern browsers. As of now, some mobile browsers still lack support, but always make<\/span> sure to consult canIuse <\/a>for the latest in supported browser information.<\/span><\/p>\n
\"Screenshot<\/p>\n
Summary<\/h1>\n
CSS Nesting is a great way to get more expressive in the way you write and structure your CSS code. Given its already decent browser support, I highly recommend you give it a try. WebStorm 2023.2 can support you as necessary. And don\u2019t forget the corner cases, where you\u2019ll have to use the &<\/code><\/a> selector when nesting element selectors.<\/span>
\nHappy Coding!<\/p>\n
The WebStorm Team<\/em><\/p>\n","protected":false},"author":1424,"featured_media":380191,"comment_status":"closed","ping_status":"closed","template":"","categories":[6711],"tags":[199,8211,1731,8118],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/webstorm\/376858"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/webstorm"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/types\/webstorm"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/users\/1424"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/comments?post=376858"}],"version-history":[{"count":11,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/webstorm\/376858\/revisions"}],"predecessor-version":[{"id":412851,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/webstorm\/376858\/revisions\/412851"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/media\/380191"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/media?parent=376858"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/categories?post=376858"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/tags?post=376858"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/cross-post-tag?post=376858"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}