Skip to main content
JaroslawM
Participant
November 7, 2019
Answered

Feature Request-States do not inherit component instance default state modifications

  • November 7, 2019
  • 44 replies
  • 28501 views

Hi, so the scenario is as follows:

  1. You make a button template component, that has a body shape with fill and border, and a text label.
  2. For that component you add a state - let's say Hover, but any state works the same
  3. You make an instance of the component. You adjust the button width and change the button's label (standard component usecase I suppose?)
  4. You test the hover effect: of course the interaction is applied, but the instance adjustments were not inherited in any way for the instance's states - on hover the button's label changes back to the default placeholder, and the button auto-animates to the master's size.

I suppose the solution is to apply instance modifications to each of the instance's states separately, but that seems like something the component feature should address rather than require the user to do manually for every element.

The new states feature has been especially disappointing with an ongoing app design, where I already have most of the design system established. It was initially logical to me that I could add a Hover state to the component's master and all the instances, across the artboards in the entire prototype would "simply" inherit it, but alas - I found they only show the master's state on hover. Needed to undo all of that since it basically broke the prototype for any kind of use, and I definietely do not have the time to go instance-by-instance and apply all the component edits again.

 

Unless I missed something and am doing this wrong.

This topic has been closed for replies.
Correct answer Sherif Assaf

Hi All -

 

Apologies for the inconvenience around the effort required to manually change states in component instances.

 

We're actively working on addressing this issue so that changes made to the Default State in an instance would propagate to other states within that instance.

 

Stay Tuned.

 

Thanks,

Sherif

 

 

44 replies

majurVB
Participant
February 9, 2021

Please, it's something really important... You don't have an idea how much time it could save me today with changing the text on instance back and forth on hover. 

Participating Frequently
February 9, 2021

It is time to move on from XD.

Known Participant
February 9, 2021

Easier said than done. At my last job I used Sketch. Then I lost my job because my company was severely impacted by Covid. Joined a new company, and their tool is XD. I've told them over and over how limited it is, and how I will try to look up a tutorial on how to do something, only to find a USER VOICE post requesting the feature... a feature that it's such a necessary part of prototyping and has been in Sketch and Axure for years! It drives me crazy. But that's our company tool. My boss is used to it and doesn't want to change. What am I supposed to do?

zerhackelt
Participant
January 27, 2021

It's been a while. Figma can do it. When will this be a priority?

Participant
January 24, 2021

Hi, any updates on this? This issue makes working with XD a pain...

dessita
Participant
January 8, 2021

Hello, any update on this? It's been a while and this is really one of the most common frustration with Adobe XD I experience. I bet a lot of people end up switching to alternative software because of this.

Participant
January 4, 2021

@Project Nimbus Prerelease are you still working on this issue? In my perspective it's a blocker for even working with states and one of the main things to set XD far behind other design tools! If not fixed very soon we consider using another supplier and I bet other companies will do the same. 

Adobe Employee
January 11, 2021

@Sari5E0C We definitely understand the friction that you're facing in that area. It is certainly a high priority in our roadmap and we are working on a some foundational aspects to provide a seamless, performant solution. Stay tuned!

Participant
December 4, 2020

I decided to give Adobe XD a try after a long pause, currently working with Sketch. This is a very basic feature for a product that wants to compte in this category.

Participating Frequently
December 5, 2020
FYI: Guys you should upgrade. It’s been fixed maybe a month or two back 🙂 yay.

It doesnt apply for components of a component, though. Or something like that. But for basic master/instance it finally works as expected.


Sent from my iPhone
Spas K.
Community Expert
Community Expert
December 5, 2020

It hasn't been fixed 🙂 The only thing that was fixed was some nested component issues, and nested hovers.

 

The issue this thread is about is different. Let's say you make a component, like a button for example, and it has 3 states - default, hover and pressed - they have the same text, but different colors.

 

If you make an instance of that button, and change the text in the Default state, the other states stay with the text of the Master Component, so you need to change the text for every state of every instance manually, which defeats the purpose of having component states completely.

Participant
December 2, 2020

This is a make or break feature. Major Gaffe.

Participating Frequently
November 6, 2020

Still waiting. One year later.
There is no design system without this option.

Known Participant
November 5, 2020

New unpopular opinion. Maybe those changes shouldn't apply to the other states, or should be an option only (checkbox or something to choose "apply changes to other states").

Right now I'm trying to make changes to the default state, and they keep appearing on the other states. Random elements that make sense on the default state but not on the other states.

 

I feel like I'm going crazy.

Participating Frequently
November 3, 2020

It's now been a year and this issue still exists. What's going on?