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.
-
Adam Trabold commented
yeah, this is a giant timesuck for us as well. we've completely stopped using hover states because of how frequently we'd forget to click into the hover to edit text on a button, for example. gets really confusing when those accidents make it out the door during a usability test or something.
in my opinion, text should follow the same rules as everything else on a component state...if you have states, the link between the default state should only be broken when it is specifically changed on a non-default state.
so...if i change text within the default state, it should populate all other states, unless i've manually changed it inside a child state.
-
John commented
Yeah soo annoying... Please fix this immediately. Also let us reset individual item states, e.g. like Sketch where you can reset the Text or Color override, etc. or even reset a sub-component override (when you use a component in another component).
-
Xavier commented
If you work on this issue you will give us possibilities to create real components in our design system. Today create components with states in a design system is a complete waste of time.
Even a simple button with a label and common states become pain in the *** :) when you try to use it across your prototypes... Just because you have to override your "Label placeholder" for each state... And when you do that because you override the original component then it's like you have no more design system... And here begin a vicious circle impossible to break. -
jsharp commented
This is hugely needed! I could have sworn this was possible after watching one of the new XD features video (not sure which one now).
-
Felicia Birloi commented
I have just started playing with Adobe XD 1 day ago and half of the time I was looking for how to achieve this specific issue. I thought I didn't discover it yet, but then I find this thread. Clearly this is a major needed feature.
-
Luis Rodrigues commented
The components really need more features of overriding and instance like in Sketch, I am working on a huge DS and I have been importing components from Sketch when I want to use a symbol and replace for another icon inside we should have an easy way of replacing this, it happens that when I drag the icon from the components because it has a different size, overrides the size assuming the size of this icon it's completely insane
-
John commented
This is the most annoying issue I have currently for XD. It requires so much work to fix this every time. It's sometimes even better to create completely new components in different sizes now..
-
Jodie commented
This has been bugging me for ages!! Any progress??
-
O.G. de Boer commented
Yessss I need this.
-
Zee commented
This is needed! Such a waste of time to change the text in all the states
-
Anonymous commented
I'm amazed. how critical this is. One of the biggest reasons of migrating to XD from Sketch was the prototyping ability and the value in Component States. This oversight renders states essentially useless. We can't switch until this is resolved.
-
Tomas As commented
+ add functionality if i selected 20 components and dropped txt file update them all not just first one and do this in all states. This would make 1000 times faster work on complicated pages + easy iterations.
-
Tomas As commented
It could be like option "do you want default state changes to update other states" yes/no. In this case if someone is using this in different way they have old functionality too.
-
Rob commented
I'm voting for that. It's a disaster and just adds to my workflow. Please fix.
-
Daniel M commented
I agree. Maybe a way to multi-select the states and make a bulk change.
-
Lukasz commented
I think people create Compotent states for different various reason, but I think it should also possible to make new states keep e.g. texts and/or properties from Default state. It would be useful for creating different styles of the same element like button or frame. So if you want to make a button as secondary and keep the same text and size, you just switch the state.
My idea how to make it in attachment
-
Spas Kakarchev commented
This is probably such a fundamental failure of the whole states feature, that they will need to re-design it from scratch to make it work properly. It was clearly rushed for release to get more people talking about xd. That's why they are still not addressing this accordingly.
I assume their whole plan is to release such half-baked features for marketing purposes and rework or fix them months or years down the road. Keep in mind some of the most popular requests here have been "in the backlog" for years now - this shows you how much they care about what the users actually need.
-
Nikola commented
Adobe XD is a joke with this bug being there. It’s even more frustrating that adobe doesn’t provide any eta on fixing this. A decent engineer in a well-designed architecture should be able to fix this in a week, so it makes me wonder if the whole adobe xd has some fundamental design issue given that this hasn’t been fixed yet.
Please, the bottleneck in my designs are manually updating all the states. The goal of XD is to make us efficient and this clearly breaks that.
-
Martin Klausen commented
+ 10
-
Guillaume Martin commented
This issue needs to be adressed fast, it's a huge issue that slows down my workflow terribly.