# Div height 0 after deploy

**URL:** <https://discourse.nodered.org/t/div-height-0-after-deploy/8336>\
**Category:** Developing Nodes\
**Created:** [24 February 2019 18:59 UTC](https://discourse.nodered.org/t/div-height-0-after-deploy/8336 "2019-02-24T18:59:12Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [25 February 2019 21:14 UTC](https://discourse.nodered.org/t/div-height-0-after-deploy/8336/2 "2019-02-25T21:14:42Z")

</div>

I don't 100% understand what is going wrong, but I have found a workaround (which is sufficient for me at this time):

> [@Announce: node-red-contrib-ui-heatmap (beta release)](https://discourse.nodered.org/t/announce-node-red-contrib-ui-heatmap-beta-release/8125/11):
>
> @janek: About the DOMException: it looks to me that the dashboard gives us available height 0 only for a small amount of time (e.g. immediately after a deploy). Right after that small time interval, the height will get the correct value (in pixels). But our heatmap received that correct height not before the next deploy, so until then no heatmap updates were drawn ... I have published a new version node-red-contrib-ui-heatmap@1.0.0-beta.6 which contains a fix for the DOMException. As so…

---

_[View the full topic](https://discourse.nodered.org/t/div-height-0-after-deploy/8336)._