Skip to content
← Adobe XD: Feature Requests (Read-Only)

Request details

Adobe XD: Feature Requests (Read-Only): 01 : Design mode

Categories

(thinking…)

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.

1,472 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Nate shared this idea  ·   ·  Report…  ·  Admin →

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Natalie commented  ·   ·  Report

    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  ·   ·  Report

    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  ·   ·  Report

    This is also an issue on the main component regarding the hover state...

  • Marioba q commented  ·   ·  Report

    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.

  • Brandon commented  ·   ·  Report

    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  ·   ·  Report

    Please add this feature ASAP. It makes changing the instances very tedious!

  • yoooowow commented  ·   ·  Report

    Please add this feature as soon as possible

  • Nick Araos commented  ·   ·  Report

    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  ·   ·  Report

    The absence of this feature is a big downside in the app. Adobe, please improve your product and your users experience.

  • Souheil commented  ·   ·  Report

    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.

  • Lina commented  ·   ·  Report

    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  ·   ·  Report

    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  ·   ·  Report

    Still waiting... Can't you just post the code of XD on GitHub? The community then will fix this stuff within hours...

  • Ivan Minárik commented  ·   ·  Report

    Feature has been under review for almost 2 years. What is there to consider? Not being able to swap assets across all states of an instance at once is such a waste of time.

  • Sean Johnson commented  ·   ·  Report

    Just coming back to see if this is still a thing before I make the move to Figma

  • Shaun commented  ·   ·  Report

    How on earth is this not a thing yet? It's a simple fix. If you edit the text in the Default state of a main component, it already updates automatically to the other states. Can't you simply make it so that the same applies to component instances? Or at least provide a way to update all states within an instance with a single click?

    This isn't rocket science.

  • Zach Lambert commented  ·   ·  Report

    Bumping this. This issue is making my making a project I'm doing a total nightmare.

  • Aaron Nelson commented  ·   ·  Report

    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  ·   ·  Report

    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.

2 4 5 … 16 17