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.
@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
Righttt I have had a week with adobe XD I am going back to Sketch, it's so much better
Really needed. An example is designing a Main Component for a button that has different states (hover, disabled, etc). If I use this component and update the text, I have to update each state... This includes Size in most cases.
I´m designing a lot of B2B interfaces and work a lot with forms. If you have to update every single text field component. This is a huge pain. This is not a good UX for me. 3D Transform is nice but does not help me in this case. FIGMA will release an update with interactive components in January. I think they will nail it.
I was really really hoping this would be adressed in the Adobe Max 2020 update. Instead we got 3D Transforms.
Greg Kondziela commented
We definitely need this option. Updating all states manually is super annoying
Hurry! Let's go!
Is there any news on this?
Jon Y commented
How about, drop a component onto the page, edit the values for the default state and have an option for 'update instance states with edited values'?
This is insane. I'm trying to switch from Sketch to XD, but a bug like this (and it not being addressed for a year) makes it kind of unusable for me :(
Any updates about this bugfix/feature? Not having it prevents from using XD for design systems.
Still waiting after one year
Agreed! This drives me crazy and results in so much wasted time.
Please do this!
David Goss commented
I'm often have issues where this, where I create a component (lets say a button) and I now want to change an instance from the "Default" state to the "Warning" state, but in doing so the label for the button resets to the default value (because the value isn't inherited)
This is hilarious. it seems like such a basic thing.
Until I realised the feature was broken, I just thought I couldn't get this working because I was a full size dummy.
Aluko Design commented
As much as I love XD performance wise, there seems to be a lot of common sense features the team overlooks. For example not being able to simply duplicate a component (without the copying to another doc workaround.)
A recent frustration of mine this morning was the fact that component states don't maintain size overrides. If I reisize the default state, and I change states (which in this case is just a color shift), I have to resize all those states as well. This means I usually have to duplicate (using workaround), a component , create a component - small version from the main component.
I wish there was at least an option to say "inherit default's overrides" for all the subsequent states. Because otherwise if I have 7 states I have to go through and change each 1-by-1, an it is very time consuming.
this needs to be done asap
PLEASE PLEASE make this a priority! It makes sharing UI Kits with components across our design team near impossible. Everyone has become so frustrated with having to update every state, it's almost easier to just recreate the component each time. UI Kits aren't being used by the team anymore.
No more features until you fix this. PLEASE.
This is so annoying - it is also an issue when for example updating the master button style in a shared component and all instances and states revert to the text of the master (not sure if this is a separate issue, but closely related). Almost negates the time saved by using reusable components in the first place!
How can this still be an issue after a year, Adobe? Basic feature in Sketch / Figma.
Leonardo Akamatsu commented
it's so painful