Skip to main content
Kuma
Kuma
New Member
August 18, 2026
Solved

Default variant interaction changes when a published component from a library is used in a new file

  • August 18, 2026
  • 3 replies
  • 94 views

Description:

I've created a library file containing many components. In the same file, I've also created several website page templates to test those components.

The issue arises when the component is published and linked to a new file. In the new file, the instance's default variant interaction changes and no longer references its parent component. This happens with more than one component from the library. In the video I've linked, the component I'm demonstrating is the Checkbox component, but this issue also occurs with Button and others. I checked all the problematic components in the library and found no irregularities, such as inconsistent variant naming or similar issues.

I then tried unpublishing and republishing the library, and this made the instance work normally again after updating. However, oddly, when I copy and paste the component from the library file into a new file (to duplicate the component), the same issue persists.

I initially thought the library might be too large. However, I've already reduced the number of components by half and still encounter the same issue.

Steps to Reproduce:

  1. Create a library file containing multiple components (e.g., Checkbox, Button) with default variant interactions set.
  2. Publish the library.
  3. In a new file, connect to the library and place an instance of one of the components.
  4. Observe that the instance's default variant interaction no longer references its parent component.
  5. As a workaround attempt: unpublish and republish the library, then update the instance — the interaction works normally again.
  6. As a second test: copy and paste the component directly from the library file into a new file (instead of using it as a linked instance) — the same broken behavior persists.

Expected Behavior:
The instance's default variant interaction should consistently reference and inherit from its parent component after publishing.

Actual Behavior:
The default variant interaction breaks and no longer references the parent component, affecting multiple components (Checkbox, Button, and others) in the library.

Environment:
Figma Desktop App, Windows 10 (64-bit). Not yet tested on browser version.

Video:
https://drive.google.com/file/d/13E00YDsJL6t0WU1atuFvvg1P-FWWCJ0A/view?usp=drive_link

Files:

  •  

  •  

Best answer by Tom Reem

Thanks for confirming, ​@Kuma — and for your patience while I got back to you. The detail that the interactions live on the atomic instances inside "Block / Toolbar" is useful, as is knowing it reproduces in the browser too.

I've opened a case so we can dig in further. Your ticket number is: 2087760. Please keep an eye on the inbox tied to your Figma account. I've followed up there with a few questions, and that's where we can get deeper into file and account details.

I'll come back to this thread as we have more to share on a resolution as well.

3 replies

Tom Reem
Figmate
Tom Reem
Figmate
August 18, 2026

👋🏻 Hey ​@Kuma, thanks for flagging this and for taking the time to write it up so thoroughly.

What you’ve shown us in the video looks like a past issue where a variant's interaction played correctly in the library file but was dropped on instances in files that used the library, so I'd like to get this in front of the team.

Two things that would help us dig in:

  1. File access — thank you for sharing the file links. Could you grant support-share@figma.com can view access to both the library file and the file where you're placing the instance? Being able to open the actual components and test the update will help us reproduce this scenario.
  2. Instance-level interactions — do any of the affected instances have interactions set directly on the instance, on top of the ones defined on the main component? When interactions exist in both places, they don't always re-map after an update, and it'd be good to rule that out.

Also worth confirming whether you see the same thing in the browser version, since you've only tested the Figma Desktop App so far — and can you confirm you're running the latest version of the app?

For now, republishing the library and accepting the update on the instance sounds like the most reliable path. Let me know once access is granted and I'll pass the files along to the Technical Quality team for a deeper look.

Kuma
KumaAuthor
New Member
August 18, 2026

Hi, ​@Tom Reem, thanks for the reply.

I’ve sent invites to that email and granted “can edit” access to both files. 

Regarding the instance-level interactions, I don’t apply any of them. However, the “Block / Toolbar” component is created from several atomic instances (such as Buttons and Checkboxes). I only set the interactions on those atomic instances.

I’ve just tested in the browser version and the problem persists. I use the latest desktop app as well.

Tom Reem
Figmate
Tom ReemAnswer
Figmate
August 23, 2026

Thanks for confirming, ​@Kuma — and for your patience while I got back to you. The detail that the interactions live on the atomic instances inside "Block / Toolbar" is useful, as is knowing it reproduces in the browser too.

I've opened a case so we can dig in further. Your ticket number is: 2087760. Please keep an eye on the inbox tied to your Figma account. I've followed up there with a few questions, and that's where we can get deeper into file and account details.

I'll come back to this thread as we have more to share on a resolution as well.

Terms & ConditionsAccessibility statement