# Announce: node-red-contrib-ui-heatmap (beta release) **URL:** https://discourse.nodered.org/t/announce-node-red-contrib-ui-heatmap-beta-release/8125 **Category:** Share Your Nodes **Created:** [18 February 2019 23:23 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-heatmap-beta-release/8125 "2019-02-18T23:23:02Z") **Posts on this page:** 1 **Showing post:** 11

### 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:11 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-heatmap-beta-release/8125/11 "2019-02-25T21:11:37Z")

@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 soon as I detect that the heatmap canvas height is 0, I again determine the available height (that we get from the dashboard) and I set the heatmap canvas height to that value. You can see in the browser console log when this happens: - However sometimes (i.e. when the above correction is calculated during the small interval immediately after the deploy) the height I determine is still 0. In that case I don't draw the new input matrix, since it would fail anyway. As a result _this input matrix will never be drawn_, which you can see in the browser console log: Could you please test it, and let me know if I can publish it as version 1.0.0 on NPM. --- _[View the full topic](https://discourse.nodered.org/t/announce-node-red-contrib-ui-heatmap-beta-release/8125)._