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
It seems that right now we completely remove the .svg-output/.code-output elements when switching tabs. Couldn't we keep the elements and update them as needed/hide the inactive one properly?
Secondly, if one's compressing a big file (like https://dev.w3.org/SVG/tools/svgweb/samples/svg-files/gallardo.svg), there's a noticeable slowdown when switching tabs. Might be related to the aforementioned point, but I was wondering if we using some kind of cache like we do elsewhere could help?
The text was updated successfully, but these errors were encountered:
It seems that right now we completely remove the
.svg-output
/.code-output
elements when switching tabs. Couldn't we keep the elements and update them as needed/hide the inactive one properly?Secondly, if one's compressing a big file (like https://dev.w3.org/SVG/tools/svgweb/samples/svg-files/gallardo.svg), there's a noticeable slowdown when switching tabs. Might be related to the aforementioned point, but I was wondering if we using some kind of cache like we do elsewhere could help?
The text was updated successfully, but these errors were encountered: