Skip to main content
Question

Ready for Dev state doesn't change, when changing slot content

  • April 23, 2026
  • 1 reply
  • 13 views
Carl123

Hey there,

Short version: Component with a slot, component is used in a frame, ready for dev state is set, later it doesn't reset when the slot content is changed.


Longer version

I was using slots to create template for an application page, so I only need to fill the content area (represented by a slot) for each page I design for this application.

When I first use an instance of my master page component and fill the slot with some content the ready for dev state is changed to not ready, when it was ready before. This is the correct behaviour, BUT when I then change the content within the slot, the ready for dev state is not removed and it is still ready for dev although I made changes within the slot.

Does anyone have the same issue, is it a bug or the wanted behaviour?

1 reply

Jaycee Lewis
Figmate

Hi ​@Carl123 👋 thanks for the detailed write-up. I appreciate that you clearly laid out the steps to repro.

Slots is still in open beta, and there may be some edge cases around how it works with other features like Dev Mode statuses. The ready for dev "changed" state does have a few documented cases where it intentionally doesn't trigger — when an instance updates from a shared library or when a variable value changes on an attached layer. But I don’t see slot content changes on an instance as one of those exceptions.

To get this in front of the team so they can investigate, could you submit a bug report? That's the fastest path forward since they'll need file access to take a closer look.

To do that:

  • go to the Support Hub
  • click Start a chat
  • type "Report a bug."

Please include the following in the form:

  • A direct URL to the file
  • Invite support-share@figma.com to the file with view access so the team can take a closer look. (This is our official Support account, and you won't be billed for this seat.)
  • Any screenshots or video recordings of the issue. This helps us visualize and reproduce the behavior on our end

Thank you!

Terms & ConditionsCookie settingsAccessibility statement