Can't edit text in nested instanses

Hey, ​@Daria Kalinina 👋 Thanks for the attached video. 

I took a look but couldn't pin down the root cause from what's visible there. Is this still happening to you? If so, I’ll get our support ticket opened. — Jaycee

​@Jaycee Lewis 
I’ve been having the same issue for a while. Its incredibly frustrating. 
I have to detach multiple components just to present designs with correct content, then revert back in history to continue iterating. I had to start having a separate document to keep track of copy. 

For example: I have a component for input fields with text value properties. I have a table cell component with nested content. In some instances, the nested component within is the input from above. Up to here, the text on the nested instance is still editable, but when I have the cell component within a row/column component, then the text of the “deep” nested input field is no longer editable. 

This needs to be fixed, please. 

Hi ​@Shudwick, thanks for chiming in here! 

I understand how this must be slowing down your workflow. Here are the three most likely causes:

1. Expose Properties in the Main Component

• If child properties aren't exposed at the parent level, they won't be editable on instances. To fix this:
  • Select the Main Component (not an instance)
  • In the right-hand sidebar, go to Properties and click + (Create property)
  • Choose Expose properties, select the nested component, then pick the specific property to expose (e.g. variant, text content, or boolean)

2. Check Your Selection

• Figma doesn't support editing nested component properties across multiple selected instances. Try clicking a single instance, then make your edits in the right-hand panel.

3. Check for Locked Layers

• Locked layers in the main file can prevent edits. Open the Layers panel and look for the lock icon, or press Shift + Cmd + L (Mac) / Shift + Ctrl + L (Windows) to toggle locks.

Please let us know if any of these help, but we’ll also be happy to help get you connected with our support team, if needed. 

​@Jaycee Lewis 
Yes, this is still hapenning. I’ve already spent like 6 hours trying to find the root cause the answer is that there is simply none and I don’t know what to do

Hi, ​@Daria Kalinina 👋 Thanks for confirming it's still happening, and sorry for the time you've sunk into this. Based on your video plus a matching pattern reported by ​@Shudwick  on this thread, I opened a support ticket (ID 1930692) on your behalf so we can dig in further. You'll get an email from Support shortly — please reply there so we can keep everything in one place. Thanks again for following up 🙌 – Jaycee

I am still facing this extremely frustrating issue. 
​@Jaycee Lewis Thanks for raising a support ticket (ID 1930692). Do we have any updates on this?

Hey, ​@Shudwick 👋 Thanks for the follow up. The support ticket I opened was for the OP. Lets get your example together and I’ll get a case opened for you and your specific issue.

Just to confrim, in a support ticket (not here), can you share:

• Include a full-size screen recording of the issue
• The URL of the affected file(s). Grant edit access to support-share@figma.com so our team can attempt to reproduce the issue

• Sharing file access won't impact your billing — it just allows our team to debug further on their end. Please be sure to use your Figma email account when sharing

As soon as I hear back, I’ll get the support ticket opened and email you the details with how to help support get the details they need to investigate. Thanks again! — Jaycee