# Height set to auto doesn work after browser update?

**URL:** <https://forum.inductiveautomation.com/t/height-set-to-auto-doesn-work-after-browser-update/87021>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 8, 2024, 11:18am UTC](https://forum.inductiveautomation.com/t/height-set-to-auto-doesn-work-after-browser-update/87021 "2024-03-08T11:18:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Theodorska](https://avatars.discourse-cdn.com/v4/letter/t/34f0e0/32.png) [@Theodorska](https://forum.inductiveautomation.com/u/Theodorska)\
**Post date:** [March 8, 2024, 11:18am UTC](https://forum.inductiveautomation.com/t/height-set-to-auto-doesn-work-after-browser-update/87021/1 "2024-03-08T11:18:32Z")

</div>

Hello,

We had a menu popup that used to scale automatically to the browser window by using height set to auto. It got an error in Ignition, but worked fine in Edge and Chrome browsers across different devices for several months.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/f/3f0f15603c26fa93ad3dcf50872f6a90853c78fb.png)  
suddently it stopped working for all users. I noticed it following a browser update for Chrome.

My question is, has anyone else noticed similar issues or have I accidentially done something to mess this up?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 8, 2024, 3:34pm UTC](https://forum.inductiveautomation.com/t/height-set-to-auto-doesn-work-after-browser-update/87021/2 "2024-03-08T15:34:28Z")

</div>

Possibly this issue (a change in Chrome behavior that's arguably a bug):

> [@Issue with Modal Popup Positioning in Chrome](https://forum.inductiveautomation.com/t/issue-with-modal-popup-positioning-in-chrome/86535/2):
>
> This is caused by what we consider to be breaking changes in Chrome. [Their argument](https://issues.chromium.org/issues/326980470) is that it is expected as part of a forward-thinking approach, and other browsers will soon be following suit. We're aware and have an open ticket to fix it soon within Ignition. I'll try to get a Dev to chime in with the recommended short-term workaround.