[vector_graphics] Respect BoxFit parameter with viewbox (closes #158496)#11012
[vector_graphics] Respect BoxFit parameter with viewbox (closes #158496)#11012Gustl22 wants to merge 2 commits intoflutter:mainfrom
Conversation
There was a problem hiding this comment.
Code Review
This pull request fixes an issue where BoxFit was not being respected for vector graphics with a viewBox. The change refactors the sizing logic in _VectorGraphicWidgetState to correctly use FittedBox. The PR also renames an internal variable for clarity and adds extensive new tests, including golden file tests, to verify the fix. The changes are logical and well-tested. I've included a few minor suggestions to align with Dart's style guide.
81bbbe6 to
baa096a
Compare
|
It seems, that the goldens fail, although they succeed locally on my Mac. As I am not sure, if we should keep them anyways, I wait until generating on Linux (as I need to set it up then). |
| }); | ||
| }); | ||
|
|
||
| // TODO(gustl22): can be removed if redundant |
There was a problem hiding this comment.
Can remove goldens (if too costly for CI), but maybe is a good thing to have them in place (more intuitive to see, what's going on).
Closes flutter/flutter#158496
Pre-Review Checklist
[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under1.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under1.///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2 ↩3