@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:
The heatmap height is being corrected
-
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:
The heatmap is skipped due to invalid canvas size
But from the moment that the next input matrix arrives, the new matrices will be drawn in the heatmap (since the height has got meanwhile the correct value). For me this solution is sufficient at the moment ...
Could you please test it, and let me know if I can publish it as version 1.0.0 on NPM.
