---
title: "Discussion on \"Transition to `height: auto` & `display: none` Using Pure CSS\" | Hashnode"
description: "Discussion on \"Transition to `height: auto` & `display: none` Using Pure CSS\". Find out how to easily transition to intrinsic sizes and trigger transitions when an element receives its first style update using new CSS features."
url: "https://hashnode.com/posts/transition-to-height-auto-display-none-using-pure-css/66b52b6964b7931f978d1abb"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Transition to \`height: auto\` & \`display: none\` Using Pure CSS](https://blog.css-weekly.com/transition-to-height-auto-display-none-using-pure-css?utm_source=hashnode&utm_medium=feed)

Find out how to easily transition to intrinsic sizes and trigger transitions when an element receives its first style update using new CSS features.

Aug 8, 2024 · 14 min read · blog.css-weekly.com  
Updated Sep 12, 2024  
Read the article

-   [#css](https://hashnode.com/tag/css)
-   [#css3](https://hashnode.com/tag/css3)
-   [#css-animation](https://hashnode.com/tag/css-animation)
-   [#css-transitions](https://hashnode.com/tag/css-transitions)

## Written by

[Zoran Jambor](https://hashnode.com/@zoranjambor)

@zoranjambor

  
[View profile](https://hashnode.com/@zoranjambor)

Frontend developer & content creator, author of CSS Weekly.

Frontend developer &amp; content creator, author of CSS Weekly.

## Responses 3

Markdown supported · ⌘↵ to post

[Fr Legends Mod Apk](https://hashnode.com/@frlegend)

[Nov 6, 2024](https://hashnode.com/posts/transition-to-height-auto-display-none-using-pure-css/66b52b6964b7931f978d1abb/comment/672b6a2c866b91493a5fd4d1)

Great topic! The evolution of web development is fascinating, especially with how quickly new tools and frameworks are being introduced. It’s incredible to see how technologies like AI are shaping the way we build websites and apps. I’m curious to hear everyone’s thoughts on how tools like Next.js or Astro are impacting front-end development—are they making things easier, or are we just adding more complexity to the stack? Looking forward to hearing your insights!

[Shahn32125](https://hashnode.com/@shahn32125)

[Sep 21, 2024](https://hashnode.com/posts/transition-to-height-auto-display-none-using-pure-css/66b52b6964b7931f978d1abb/comment/66ee9083fbf1df89f04343f3)

Thanks for sharing [19216811.cam](https://19216811.cam/) [1921681001.id](https://1921681001.id/)

[Zoran Jambor](https://hashnode.com/@zoranjambor)

[Sep 21, 2024](https://hashnode.com/posts/transition-to-height-auto-display-none-using-pure-css/66b52b6964b7931f978d1abb/comment/66ee9083fbf1df89f04343f3#reply-66ee96d54d58996df1ea9496)

Thank you for reading and commenting, Jawed! I’m thrilled to hear you found it useful. 🙂

[Alina](https://hashnode.com/@subislav)

[Sep 4, 2024](https://hashnode.com/posts/transition-to-height-auto-display-none-using-pure-css/66b52b6964b7931f978d1abb/comment/66d88b0f279247054b02e788)

hello

[Matteo Fogli](https://hashnode.com/@pecus)

[Sep 2, 2024](https://hashnode.com/posts/transition-to-height-auto-display-none-using-pure-css/66b52b6964b7931f978d1abb/comment/66d5b86537bf8775ae7a1469)

as of september 2nd, Chrome (v130) is missing proper support for the at-support rule tests of the `calc-size()` function, meaning this code will _not_ work

```
@supports (height: calc-size(auto)) {
/* ... */
}
```

This seems to be tracked in chromium bug #358461053

[Zoran Jambor](https://hashnode.com/@zoranjambor)

[Sep 12, 2024](https://hashnode.com/posts/transition-to-height-auto-display-none-using-pure-css/66b52b6964b7931f978d1abb/comment/66d5b86537bf8775ae7a1469#reply-66e2b7d8258ed72e1f163ed9)

Thanks so much for the heads-up, Matteo. 🙏

It seems that the implementation of calc-size() has changed and it now only supports two-argument form. So this at-supports rule works correctly: `calc-size(auto)` no longer works.

I'm updating the article now to reflect this change. All `calc-size(auto)` examples must now be `calc-size(auto, size)`.
