Allow component instance overrides to be inherited by all states
Currently (XD 24.0.22.19), if I drop an instance of a component and then adjust part of it (text in a button, size of the instance, etc.), that override is only applied to the selected state of the instance. So, if I have a button with many states (normal, hover, disabled, active, default action, etc.) I have to manually apply that override to each state of the instance. This is extremely tedious and error prone.
Please provide the ability to have an override of an instance be inherited by all states in that component instance.
Nate
shared this idea
83 comments
-
Anonymous
commented
100% needed
-
Ji Hoo Yoon
commented
Please, without this feature, the component states are really useless
-
Jono WePiphany, LLC
commented
Real pain. Sketch and Figma are better options.
-
Wonil
commented
Please update this. This is causing a major inefficiency currently.
-
Steve Markovich
commented
One of the major reasons I continue to use Sketch instead of XD,.
-
Anonymous
commented
This is really important.
It takes me a lot of time.
When working with big lists with interactions in each item it turns terrible. -
Jake Spillar commented
Yes please... should have shipped with this.
-
Pete Conway
commented
This feature is so, so important. The whole purpose of components is to speed up workflows and allow for consistency, but if I create a button or a field using a component and have a few different states (e.g. view mode, edit mode, mandatory, disabled) then I have to change the field label, value and size for EVERY state which renders much of the benefit of states and components lost. This is another gap with regard to components, just like the inability to see all of the states in the developer preview.
Another feature that would be really helpful for components is that if you select multiple instances of the same master component it would be great to be able to set them all to the same state, so that if I have a field component and I have 10 fields on an artboard I can just select them all and set them all to edit mode, or disabled at once.
-
Anonymous
commented
This drives me insane with hover states! Especially if it's a component that is repeated 10 or 20 times (such as a row in a table). Having to make each text change (or whatever) twice due to the hover state is extremely tedious. Thanks for looking at this one Adobe!
-
Jenni Merrifield
commented
OMG. Yes, I need this! Please!
-
Sebastian Hösl
commented
I need this!
-
Jesse
commented
The lack of this functionality is making me push my workplace to use Figma or Sketch instead of Adobe XD. Many wasted hours on changing the text on additional button states.... sigh
-
digita
commented
Too much manual and time-consuming editing, please improve it.
-
Anonymous
commented
I agree that I have spent hours reorganizing components because of this issue. I used to work with Sketch and Sketch identified a text field/color/icon as a part of a component that could be specific to a particular instance and provided a panel for modifying these for each instance. With XD, the component panel is only useful for hover and click states, but not for repeating styles. This is very disappointing!
-
uiux designer
commented
would be highly appreciated
-
Anonymous
commented
This issue makes the states feature very difficult to use. If the user creates a new state and edits one element of that state, it should be treated as an override. The new state should still inherit all other properties from the default state and any changes made to the default state should propagate to all other states unless there is an override present. This is the way it would work in simple css.
-
Anonymous
commented
may i ask, how this is still marked as "feature-under-review" but in the forum someone said, u are actively working on this (since nov 2018) how is this not done by now? this renders the feature almost useless
-
Cervantes
commented
This means I just simply can't have a functional and interactive design system. So now I have to delete all my components states because when I interact with them it is absolutely ugly. This should not be a feature but a bug fix. What it the point of having a library of components with different states if you can't interact with them? It prevents me to do a good job in my company. This issue has been highlighted for a long time now and you can't even give us a proper time frame to fix the issue.
-
Anonymous
commented
I'm literally having to remake all of my components. I have a UI Standards Guide with master components. If I drop a master component from my standards guide(for example a button) into a new design(file), then create a table (for example) that includes this button component (with a new label), then paste the table back into my UI Standards Guide for reference, it reverts the button to the master component label and width. Is there any override for this? We also, need a way to create a master component from a modified component.
-
James
commented
Yep, obvious really...