Allow component instance overrides to be inherited by all states
Currently (XD 184.108.40.206), 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.
Upvote! What's the point in creating a design system full of components if you have to redo every button state anyway?
Using components in a repeat grid and updating text by dragging a text file on it would also help, INCLUDING passing through to all states within the component.
Frustrating AF. Get it on, guys, we pay you enough money for this.
Celestine Fisser commented
Can we get an update on this feature? This is so frustrating!
Ed Aranda commented
If this doesn't get addressed in the next release I'm going to lose my f*!@ing mind. States are completely useless without this functionality.
This is so essential! I want one master button in many instance colors each one with it's own inherited state. Like this it all has to be done manually, it's so hard compared to Sketch!
Agreed, this is so close to. The default state auto resizes great, but then having to go through and rechange the size on the hover state background for EACH layer in a chart is painful.
Gavin Stokes commented
There is a lot of small stuff in XD that really stacks up the more you use it...and this one just kills me, I've an input box with 4 states, not including the default...I have to scale each state, that's just nuts. Can we get this fixed, simple check box or something
when resizing complex component with states only the active state is resized.
To whoever UX skipped this feature: You didn't use Xd did you?
Nathaniel Platts commented
This should be #1 above all other features you MUST deploy. This is so basic and YOU know it. I've been endorsing XD for years.....but I'm getting tired of the monotony of working with design system components and efficiency. I've worked with several teams helping them setup DS libraries and this one issue haunts me every time.
This could up being a deal-breaker for me now. If there is ANY HOPE please let me know :(
I cannot begin to convey how frustrated I am that after having built a whole design kit for the team to use with all the states for everything, instead of it being a triumph of efficiency and consistency it creates a massive pain in the ass because I have to manually make every basic change across every state in every instance whenever I build with it. And it's not even just the obvious stuff like the button label, it's resizing for responsive design, and removing subcomponents, like columns in a row, that you would assume would work because when you make those changes on the master it does, in fact, work as expected on the states of the master. I don't think I've managed to not run into an 'oops, forgot to fix the hover on that' on at least once while walking through something. Please, for the love of all that is good and my sanity, prioritize this feature.
Gerald Wildmoser commented
Absolut necessary feature to bring XD forward as a tool for design systems!!!!
Dean Logan commented
This is really surprising Adobe. Watching the Pinsky Masterclass 1 video and he breezes right through this. Clearly this is an update bug. Please fix.
Ephie Risho commented
I have run into this issue dozens of time on every project. Components and states are nice, but not anywhere near as robust as they could be with this simple change. Examples would be form fields with hover and active states.
Which brings me to a tertiary request: text changes. How nice it would be if XD had an option on components to allow changing all text within that instance. I can't tell you how many times I copy/paste a button, toggle, menu, nav or really any item, and have to go in and individually change the text of every state as well. What a silly waste of time. Please, Adobe, give us these two features soon.
Here is the current "correct answer" from Adobe as you can find it on the XD forum, from November 2019...:
SherifAssaf • Adobe Employee , Nov 08, 2019
Hi All - Apologies for the inconvenience around the effort required to manually change states in component instances. We're actively working on addressing this issue so that changes made to the Default State in an instance would propagate to other states within that instance. Stay Tuned. Thanks,Sherif
Por favor arreglenlo urgente!! En Figma funciona bien, no quiero cambiar de programa.
Dan Bartels commented
Cant believe there aren't more votes for this. The lack of this feature is highly frustrating and results in a lot of extra time spend fiddling with each button component instance and then in proofing to make sure every instance is correct.
not having this feature is a time and flow killer 🤬
Yes, please, makes use of any component states basically worthless