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.
I want this too
This one is desperately needed. It's one of those things that I lose sooooo much time over....
This would be a great feature. If I just want to change text on a button, I have to change it on every state, which becomes very tedious. Or if you have something like a product listing and they all use the same component, you have to adjust every single item individually for every state.
I can see how this may be difficult to implement since it's hard to determine what should then change if you edit the master component. Though maybe the first determinant is positioning and sizing of objects within a component.
It was terrific if this improvement to be happen.
Roni Dalin commented
Need this one. ☝️
Mr. Will the design KING commented
WE LOVE YOU ADOBE...YOU CAN DO IT !@!@!@!
Pierce Porterfield commented
I thought this would come out with XD 2021 and was really disappointed
yes, this is needed BAD!!!!
Matt Brogan commented
Yes, this needs to happen. Please
It needs to be fixed asap. Working with design system in adobe xd is painful right now because of how the states work...
Please, fix this ASAP!!!!
This is exactly my same request, we need this ASAP
Martin Pernecky commented
I'm not sure why this is even a feature request or an idea. This is for me the basic functionality. With components clearly there to promote reuse and being used in design systems a concise propagation of properties is a must. If I resize a button component it should apply to all states.
It is even more clear that states is a feature of components and not of any single use design element.
I get that going from a MVP version that you introduced to a version that support this kind of inheritance might be tricky (after all you need to revert to parent / main / other state for each and any of the properties each object has) but this makes the component w/ states system basically useless.
If I create a design I can opt for a high-fidelity version for a very small subset of the design or do basic design for the entire scope of the project. Doing both just does not scale (with the frequency of changes and amount of work it would require to keep up to date).
As a side question, could there a plugin that could sync the properties to sub-states?
Ji Hoo Yoon commented
Why this is still need to be reviewed? It's a CERTAINLY feature for states not become useless
Can I add my name to the chorus? This is infuriating.
Desislava Slavkova commented
This is so very important, it makes components useless for buttons. I end up having the text outside of my button components but then, of course, it's impossible to update its look on hover.
This is an incredibly useful feature that is still missing from XD. Without it, components such as tabs are very difficult to re-use as you need to manually edit all the states.
i've tried to make 32 simple text links with hover to change color. do i have to do it manually?
or you guys have any suggestion? please .... im so painful when I had no time to make it all hoverable.
or I make one and explain how it looks like
@Arvid_F_B on twitter shared a great example video on this issue but also layers with the same text or icons preserving position and size when swapped with another component. Take a look. https://www.youtube.com/watch?v=QolKjEsbimE&feature=youtu.be