You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at https://www.chartjs.org/docs/latest/general/responsive.html#important-note, the div around should be with position: relative. I am able to stop the growth when I put say style="position: relative; height: 80vh" (in Firefox web developer editor) to the div class="card-body". However, I have no idea what value of height I should pick for a potential pull request.
The Important note also suggest that another way of fixing the problem is disabling the resize altogether, with `maintainAspectRation: true'. But I have no idea what that change would break and how important the resizing is for Content Resolver's operation.
I don't know what causes that issue to manifest itself on my Firefoxes and how to prevent it on my side, while I understand it does not happen for others. However, since the Chart.js documentation says "this method requires the container to be relatively positioned", I believe Content Resolver should go with that recommendation/requirement anyway.
The text was updated successfully, but these errors were encountered:
Whenever I display page like https://tiny.distro.builders/workload-overview--httpd-no-weak-deps--repository-fedora-rawhide.html on my Firefox under XFCE, the canvas with the graph gradually grows vertically, keeping CPU quite busy.
Looking at https://www.chartjs.org/docs/latest/general/responsive.html#important-note, the div around should be with
position: relative
. I am able to stop the growth when I put saystyle="position: relative; height: 80vh"
(in Firefox web developer editor) to thediv class="card-body"
. However, I have no idea what value ofheight
I should pick for a potential pull request.The Important note also suggest that another way of fixing the problem is disabling the resize altogether, with `maintainAspectRation: true'. But I have no idea what that change would break and how important the resizing is for Content Resolver's operation.
I don't know what causes that issue to manifest itself on my Firefoxes and how to prevent it on my side, while I understand it does not happen for others. However, since the Chart.js documentation says "this method requires the container to be relatively positioned", I believe Content Resolver should go with that recommendation/requirement anyway.
The text was updated successfully, but these errors were encountered: