Is there a way to get better idea about overrides logic?

Hey there

I am struggling to figure out a complexity behind overrides logic. I got a setup that does not work the way I would expect it to work. It seems like Figma is struggling to balance it out, fixing one use case completely ruins another one. Or I am just not smart enough to get it :wink:

So here is my thing

  1. I got base component that implements basic shape with rounded corners, I want to reuse it over and over again to keep my radii under control


  1. Now I made another component that uses chrome component inside. This other component is supposed to be interactive one, e.g. it has few visual states like rest, hover and selected


  1. Now when it is time to use instances I got an issue… So I change the “radii” property to get different rounded corners and at this point there is NO transition from selected state back to normal, rest state.


It seems like whenever I change the “chrome” component “radii” property all the other overrides become permanent.

Playground -

Would appreciate thought on the matter. Maybe I am doing it wrong? Don’t know!

@Figma_Support you input matters too!

Hey @Pavel_Kiselev, I experimented a bit with your file and I was only able to preserve overrides with boolean union operation. And, as usual, all overrides must be on the “union” layer.

You can see examples in this file:

1 Like

Ace man, much appreciated!

It’s very interesting, seems like making union isolates underlying component that holds the shape, now I do not override underlying component but the shape itself. Seems a bit dirty, but it works, niceeeee =)

@tank666 love the way you split the shape into individual components, instance swap property makes it super easy to surface the shape props on a component level!


Found a quick solution to your problem.

Just added outline stroke FFFFFF0% to ◇chrome in ❖interactive-variants/rest.
Explanation & demo in Figma file.

Your issue was new for me too :metal: Shared my learnings in the figma file.

Me and my team use this basic understanding of overriding in figma. See image attached. Hope this helps



Hey @Amar_Varma, adding a stroke doesn’t resolve the issue. The stroke still goes to rest state and the hover state is lost after changing the radius variant. You can check in your own file.

And the alternative method with a mask works as expected, but I see a problem with the number of layers in it and consider it not optimal.

1 Like

Thanks for digging into this, much appreciated! Unfortunately, stoke method did not work, I did not find a good reason why it should though :wink: The mask looks promising, will definitely explore

Cheers mate!

1 Like