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.
Nate
shared this idea
-
Zach Lambert commented
Bumping this. This issue is making my making a project I'm doing a total nightmare.
-
Aaron Nelson
commented
How has this been a suggestion for 3 years with no results yet? This is a major flaw in XD that really needs to be addressed. So much time is wasted editing text in every state of every instance of a component.
-
Petr Široký
commented
It is truly unbeleivable how this has not yet been added. It makes handling components an everyday pain, wasting a lot of time. Maybe if XD team was forced to actually work with their software, they would start prioritizing things such as these.
-
Philip Lundgren
commented
Not having this makes components completely useless for buttons, input fields, and many other things. This alone will drive me away from XD.
-
Fannie Deschênes
commented
Our team converted from using Sketch to Adobe XD, and this specific aspect was handled SO MUCH BETTER on Sketch.
Components states are pretty much useless if you have to manually edit each of them with new text whenever a button has a different label. -
Audrey
commented
Please!
-
Daniel Constance
commented
Can we add this as a toggle on each layer inside of the component group? Then you can control which elements you want to remain linked to the default state and which should be overridden by changes in the child states.
-
Henke
commented
Yeah this is so cumbersome that I eventually decided to only use all component states once in a document.
Please fix this. -
Andrey Nechaev
commented
Up
-
Hannes
commented
Really, this feature would improve my efficiency a lot! Please add it.
-
Cliff
commented
Come on Adobe - This is very basic to build and adds 300% to product experience!
-
Guillaume Janne
commented
This is definitely THE missing feature on XD. Please Adobe make something.
-
Jarek commented
The amount of "we don't care" on the Adobe side is too damn high! :D
-
Greg Roy
commented
Seriously 1219 votes aren't enough ?? Oh, please...
-
Cyrill Studer commented
What's the status of this feature? Please add it! It's such a needed one. This would make sense as an optional feature for components.
-
Anonymous
commented
It's very important to go faster creating components and states for buttons, menu, etc...
-
Erik Gunnarsson
commented
Cringeworthy to see community managers replying to https://community.adobe.com/t5/adobe-xd-discussions/feature-request-states-do-not-inherit-component-instance-default-state-modifications/td-p/10720718/page/6 marking it as fixed in 2019 but also telling users "it's in the works" whilst such a rudimentary feature is still missing 3 years later.
-
Ian
commented
Very challenging to create large website Design system without this functionality.
-
Pxlpshr
commented
These overrides are a basic feature needed for prototyping. In large projects, with lots of components with many states, XD really reduces our productivity. Fixing all the states all the time is a nightmare!
-
Bryan edwards
commented
AGREED! Sticking with Figma until this is fixed. (But would love to stay in the Adobe family :( )