-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't compare with original version anymore (zoom-levels inconsistent) #443
Comments
I'm guessing a change to the width/height/viewbox is causing the size change? Disable that plugin? |
|
Sorry, I wasn't clear. All the settings on the right are technically SVGO plugins. Can you give me the original SVG? |
Sure, here's the original:
I've narrowed it down to the "Remove unknowns and defaults" toggle. The only difference in output (when using that toggle) is in the removal of 3 Input:
Output:
Hope that helps. I'll stop using that toggle for now, and manually remove those attributes afterwards. |
It seems like the invalid |
Hey @jakearchibald
In the past I could switch to the original version of the SVG to do a quick visual comparison of the changes. The previous versions of SVGOMG would zoom-lock the two versions so that you'd always compare like-to-like.
This seemed to have broken recenty.
I have SVGOMG installed as a 'Chrome App' on macOS 14.5.
Here's how it would break for me…
As I'd start the app, and paste the markup of the SVG, I'd see the new version (with my default settings) loaded at initial zoom:
I'd then zoom in on the new version to check for any undesired changes…
When I switch back to the Original version, it would (frustratingly) be set at the initial zoom
This breaks the 1:1 zoom functionality that would be super useful, flipping between original and not while panning the SVG around. :(
If I later try zoom into the original version to try match the two zoom levels…
And switch back to the new version, the new version would be zoomed in even further:
It's not a deal-breaker, but it would be nice to have the confidence that the SVG output is good.
Cheers,
-Shaun
The text was updated successfully, but these errors were encountered: