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
iOS might need to compute this in the same fashion.
But if that's not accurate enough for the designer intentions, then we might need access to figma's actual points. It gives this with SVG outputs and apparently maybe with more raw access to nodes / transforms.
Figma gives us coordinates for gradient points that are always between 0% and 100%. But the intention for many of our gradients looks like they are at ~-8%, etc. CSS makes this less bad by actually having the points originate outside the box due to the angle of the gradient. https://developer.mozilla.org/en-US/docs/Web/CSS/gradient/linear-gradient#composition_of_a_linear_gradient
iOS might need to compute this in the same fashion.
But if that's not accurate enough for the designer intentions, then we might need access to figma's actual points. It gives this with SVG outputs and apparently maybe with more raw access to nodes / transforms.
This (maybe) talks about this:
https://forum.figma.com/t/how-to-convert-figma-gradient-to-css-gradient/20814
https://9elements.com/blog/gradient-angles-in-css-figma-and-sketch/
The text was updated successfully, but these errors were encountered: