Allow component instance overrides to be inherited by all states
Currently (XD 18.104.22.168), 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.
This has to be one of the most pressing deficiencies of Adobe XD. ANYONE working with any seriousness on designs of only basic complexity HAS to run into this issue.
With every XD Update I pray for this to have been fixed only to again be hugely disappointed. Even writing these lines feels futile by now. Makes me as a user feel powerless. Adobe behaves like a huge impenetrable bureaucracy apparatus. Yes, there is the appearance of user feedback being taken seriously. But it's all just smoke and mirrors.
Have some self-respect and fix this issue.
Agreed, this is very much needed
Henri Le Forestier commented
Don't even try to make a calendar with hover effect on days XD <- this is the lol emoji, very good naming choice for the app.
Seriously, guys it's been years and it's a basic feature. I'm working in a public institution and you guys are slower than us XD
Reading all the comments it becomes very clear that XD is a flawed product with no QA and no respect for its users. It is insulting that the users have to vote for a product to work AS IT SHOULD. These are no feature requests, just cries for XD to be made PROPERLY.
An analogy would be having to "feature request" a word processing software for being able to use capital letters.
Lone Wolf commented
Should we be requesting for this feature or just fking leave and use a software who's developer's have a bit of common sense.
Jamie Wooster commented
3 years later and another basic, fundamental feature still hasnt been introduced. Adobe, if you want us to all jump ship and use Figma, please just let us know and put us out of our ongoing misery.
Knowing the very high quality of other Adobe Software it is really strange that after two years still nothing has happened.
It takes hours to repeat every step for every component status. It would be really good to know if something is at least planned. Otherwise this is a showstopper.
Percy Swint commented
Adobe, I am a fan of over 10 years. You make extremely efficient tools for designers and have been leading the industry for quite some time. It's perplexing that this critical issue was escalated 3 years ago and no solution has been implemented. There are too many voices that have already spoken on the burden of editing text for multiple states. What is the hold up? I personally pay for an Adobe subscription (w/ XD) with my own money, while the company I work for uses Figma. On the daily basis, I am using both tools and comparatively Figma has the edge for essential needs like this. Is it fair to ask when will this urgent and important update take place?
Michaela Brown commented
This is also an issue on the main component regarding the hover state...
Marioba q commented
I can't believe how Adobe doesn't get serious on developing XD properly... Preferes to add experimental crap like voice commands and leaves critical things like components states unusable.
This should be a simple enough feature to create. The “default” state should always be the “Master” state, one that controls the content of that instance, then a Name editable first state would be created.
This would still allow a master component to control and change things, via the master state and likewise, changes made to individual states would “unlink” from the master state as it goes now but it would give control to things like text, color, size and even placement on our instances of a component in files.
It’s imperative to add this functionality as using it in the current state completely invalidates creating library components that have any complexity.
Jennifer Lucas commented
Please add this feature ASAP. It makes changing the instances very tedious!
Please add this feature as soon as possible
Nick Araos commented
Hi, another designer here. I'm in struggle town and I'm so over changing every single state for years! What do you need to make this happen?
Pedro Salas commented
The absence of this feature is a big downside in the app. Adobe, please improve your product and your users experience.
Adobe does not seem to take prototyping seriously, this feature is super-critical. I fail to believe Adobe uses XD to design their own products yet has not come across this as a major pain point.
Oyunbold Bayansan commented
It is game changer!!!!
This is a daily struggle for me. I seriously stumble upon this issue at leat 20 times a day, where I have a button that I forget to change the text on the hover state and it messes up my whole prototype and confuses the client....
Michael Beck commented
Since Adobe is not willing to take critical steps towards basic working functionality I'm really angry that I will have to consider Figma at last ... :-/
Bert de Weerd commented
Still waiting... Can't you just post the code of XD on GitHub? The community then will fix this stuff within hours...