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
In looking in some profiles, I noticed from time to time that some time is spent in getting some images visible in the toolbar, which doesn't really make sense.
So I thought that the scope where a css variable is defined could matter and then after reading https://lisilinhart.info/posts/css-variables-performance/ I thought it really matters.
So I tried...
Here is a profile with no change (I just played with the mouse wheel to zoom/unzoom on windows 11):
and another one where the variable has been moved in the viewer container:
The text was updated successfully, but these errors were encountered:
When a css variable is update in a node then all the children under this
node are updated.
In order to avoid to update all the UI when a page is rescaling, this
patch moves the --scale-factor from the :root to the viewer container.
In looking in some profiles, I noticed from time to time that some time is spent in getting some images visible in the toolbar, which doesn't really make sense.
So I thought that the scope where a css variable is defined could matter and then after reading https://lisilinhart.info/posts/css-variables-performance/ I thought it really matters.
So I tried...
Here is a profile with no change (I just played with the mouse wheel to zoom/unzoom on windows 11):
and another one where the variable has been moved in the viewer container:
The text was updated successfully, but these errors were encountered: