This change stems from a recent overhaul of how Highcharts handles container resizing. If you'd like to revert to the previous logic without downgrading the library version, you can use the workaround I’ve demonstrated in the demo below.
I don't think it's a regression bug; however, I am quite puzzled by the idea of adding a script full of constants and deeply dependent on the version, as it could stop working at any moment. For example, that script takes 'position == absolute' into account but not 'fixed,' is that correct? I don't know... it seems too convoluted and overly complex to me.
Is it possible that there isn't a more straightforward way?
This is a difficult topic because it all depends on the interpretation of how the container should behave with a given styling. If you think this wrap may be too unstable, you can try using the alternative code below:
Changes in patch version should not introduce breaking changes without backward compatibility. According to Semantic versioning "Given a version number MAJOR.MINOR.PATCH, increment the: ... 3. PATCH version when you make backward compatible bug fixes". This fix is not backward compatible.
I have also faced with similar issue and I am trying to create the minimal example because there is a lot of different code. I need some time. The issue I have is that bar placed near a custom donut chart has too big height after Highchart upgrade.
Yes, you're right. We're sorry for any issues this may have caused. This fix wasn't supposed to introduce breaking changes. If you've encountered a specific case where something isn't working correctly anymore, we encourage you to report the regression on GitHub: https://github.com/highcharts/highchart ... new/choose
I hope the current workaround is sufficient for now.