Allow component instance overrides to be inherited by all states
Currently (XD 126.96.36.199), 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.
Angela Fioretti commented
How is this not the highest priority? This should be treated like styles not manual edits, at the very least address it for text driven items like BUTTONS and NAVIGATION (things that are on EVERY design). At the very least make it so you can copy the style of ONE change and apply it to the others. This is encouraging me to buy figma instead - the wasted billable time doing this tedious task is not worth it.
Stop reviewing now, develop it !!!
Marc Geiser commented
That this doesn't work costs me a lot of work every day, especially on projects with a lot of repetitive but slightly different elements. This needs to be fixed urgently. Currently, I am looking for alternative solutions for this reason, among others.
Stuart McCoy commented
Not having this feature implemented yet is embarrassing. It's been nearly two years since this was requested and quite frankly its lack makes this app unusable. This should have been the default behavior from the very beginning.
This is the single most painful hole in the XD experience. I have 5 states on all my buttons and the app I'm working at the moment has a LOT of buttons. In many cases, those buttons also have a leading icon.
Multiply this by five:
1. Change the text
2. Swap the icon component
3. Recolor the icon component (because it forgets the color override)
4. Resize the icon component (because it forgets the size override)
5. Switch to the next state
Component states are cool, but you pretty much hate them once you have a large app prototype up and running and you keep finding states you overlooked in your late night cram session.
Frankly, it's embarrassing that this feature hasn't been implemented yet. 100% crucial for a usable product design tool.
Can't wait this missing and essential feature! Please do it!
Jake Spillar commented
Please stop reviewing this feature and just do it already
This is fundamental for any product design tool. Looking forward to having this.
Henry Busch commented
This missing feature could singlehandedly make me leave XD
Mind boggling omission really
Still desperately hoping this feature gets released soon, so adding my voice to the masses. Thanks!
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!
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 :(