fix: Avoid desync between start and end (outer and inner) radial gradient circles #3112
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to the way
_mdf
(modified) flags are checked inSVGElementsRenderer.renderGradient()
, it's possible that thefx
andfy
components of a radial gradient, defining its "inner" circle (used for highlights via.h
and.a
members of agf
shape element in the Lottie JSON), fall out of sync withcx
andcy
which define its outer circle.In particular, the branch which sets
fx
/fy
triggers only when the gradient end point changes, but then setsfx
andfy
based on a calculation that involves both the start and end points. Therefore, if the start point of a gradient ever changes without a corresponding change in the end point, thecx
/cy
value will be updated but not thefx
/fy
value, causing visual artifacts.File exhibiting issue: radial-gradient-repro.json
Current rendering:
After fix: