Thanks for the feedback, @Brooke_White!
We’ll pass this onto our team for future consideration.
THIS. Re-doing the work or being forced to detach is my biggest headache of any of Figma’s limitations. It causes so much work to be wasted. This and similar auto-layout changes to components has been requested by users multiple times over the years, a quick Google search will pull up multiple other related posts in the forum.
it is super helpful for multilingual design systems, where text order can switch between rtl and ltr.
I cannot upvote this enough, say for example I have a dropdown menu component, many of our platform’s options menus share similar options e.g.
Most of the main feature menus have: Overview, Add [Insert feature name], Statistics, Reporting, Utilities, Settings. Then most of our sub feature menus have: Add [Insert object name], Edit [Insert object name], Delete [Insert object name], etc.
The issue is there are always options in the menu between these common ones based on the other options that are individual to a feature/sub-feature, and the total number of options may vary.
If I were to detach the component to get around this, then I would lose the components state variables when I am using it e.g. being able to toggle between whether or not it is enabled, hovered, selected etc. for my wireframes and prototypes. I could just add placeholder options in the middle of the main shared ones and hide these when I don’t need them but its messy and inflexible. I also don’t want to have to create a dedicated component for each feature and sub-feature dropdown we have as that defeats the purpose of creating re-usable components…
That is just one example of when I encounter this issue but I also encounter it with other use-cases. Surely we can’t be the only users frustrated by this.