Participant

Answered

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

Forum|Forum|6 years ago
November 7, 2019
44 replies
28568 views

Hi, so the scenario is as follows:

You make a button template component, that has a body shape with fill and border, and a text label.
For that component you add a state - let's say Hover, but any state works the same
You make an instance of the component. You adjust the button width and change the button's label (standard component usecase I suppose?)
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.

Missing feature

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

Show previous replies

oscarpmosh

Participating Frequently

There is not even an aswer from Adobe, they focuse so hard on new features and some of them not even requested by people, but essential things like these are ignored completely. this has been here for years and I don't think they will fix it any time soon.

I should be thinking on moving my workflow to figma or other app.

Rishabh_Tiwari

Community Manager

Hi there,

We're so sorry for the delay. As of now, we don't have a time frame by when this feature would be available however, let me assure you I'll share your feedback with the Engineering team. Please stay tuned here for updates on the request.

Regards

Rishabh

S

Steven Cross

Participant

I hate to complain but the functionality being requested is really critical. Lacking this, I cannot even remotely understand how anyone at Adobe considered component states to be ready for release. If you have to go in and edit, what exactly is state bringing to the table? People have been asking for this for years now. I have convinced a couple of my Fortune 100 clients to use XD but I am starting to seriously regret it and plan to switch back to Sketch, or over to Figma, as soon as my current project allows for it. A real shame.

F

fixxdpls

Participant

Wake up Adobe, it's a must have...

N

nicoleduncandesign

Inspiring

I can't believe this still doesn't work.

A

adamschmid

Participating Frequently

Just use Figma already...

m4tze

Participating Frequently

Yep, same here. Basic functionality is apparently not an issue for Adobe – switching back to Sketch.

S

Sander5CE3

Participant

Wow... just wow...

I come from Figma and wanted to use Illustrator. Convinced the team to take the full application plan so we could start using XD only to find out a rather simple function is requested by many but never developed. I could write this feature in a day, it's only keeping track of references and keeping the content of the references in sync. Nov 2019 "we're actively working on addressing this issue". July 2021: still nothing. If I'd take 2 years to develop a rather simple feature, I'd want to quit my job.

How can this not be a priority? The whole point of a application like XD is fast UI development, if I wanted to copy my changes to different states I might as well use Illustrator.

That being said, I'll switch back to Figma with saddens me as I've been a fan of Adobe since Illustrator 8 because it's ease of use, intuitivity and sharing objects between applications. Saidly we pay for all the random features, voice-command whaat?, that are never used and have to wait for deal-breaking features.

A

Anonymous

I wasn't planning to write as by now I have lost all hope for XD. I downloaded Figma yesterday and played around with it some. It seems they got everything right that XD got horribly wrong. Adobe XD is dead. If it weren't for the occasional Photoshop/Acrobat needs I would ditch the Adobe subscription altogether (XD doesn't deserve our money). Someone wrote here that Adobe had stopped supporting XD, I didn't want to believe it but sadly, it's true. I don't see any chance whatsoever of them ever catching up with the competition. Bye.

S

Sander5CE3

Participant

I'm trying to finish the current project in XD to avoid transfering files but had 4 or 5 crashes in 2 workdays. The project consists of 4 artboards with not a lot in them. This application is a total joke.

XD doesn't deserve our money

Totally agree!

D

defaultu1vgqxeb7cie

Participant

Dear Adobe — Can you PLEASE put this as the #1 priority on your backlog? Thank you.

This problem alone made me switch to Sketch for my current project.

T

Timothy5DEE

Participating Frequently

Adobe has pretty much stopped supporting XD. Time to move on to greener pastures.

K

Kristian H. Bangsø

Participant

So empty promises?

Please fix this instead of working on stupid voice-command features that no one uses.

Fixing the product should be a number 1 priority instead of adding ridiculous things.

How do you event select features did some intern come up with that s***, and the board was just baffled by the randomness? This is exactly why people are moving to another solution.

G

garethf43309530

Participant

Anyone know if that has been fixed, I'm having the same problem

T

Timothy5DEE

Participating Frequently

Nah, it's been years. This isn't on anyone's radar.

D

defaultsda34uh0tdjb

Adobe Employee

More than 99% of the time in interactive screens, a hover state will have the same text as the link state. On the web, it'd take extra JS effort to change the content, and rarely is that a good experience for the user. Text change on hover is just not a thing. Occasionally we design a link or button with a progressively disclosed tooltip containing additional text.

So why would the XD feature support this, default to this, and make it hard to design hovers that don't change their text — the normal way they should work?

MatiouLilou

Known Participant

That's not the issue highlighted by op I think and it's not about changing the text when you hover over a link, which does not sound very user friendly.

It's more about creating an instance of an existing component (eg a button), and whishing that all the changes you apply to that the new button instance, be it text or colour or whatever is carried across its other states (eg Hover), for that particular instance of that button.

And as @Sherif Assaf said in 2019 :"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."

D

default2em34s5dro3k

Participant

Exactly! "Text change on hover is just not a thing".

As OP said, "States do not inherit default state modifications" — such as text changes.

But they should. Change the text in an instance, and its hover state should show that new text. Just the way HTML works. Who would want it otherwise? It's fair to say that not a single XD user over the past three years has liked how hover states work.

I'll update my nuber: 100% of the time a hover state will have the same text as the link state. 😂

Which is why Adobe is working on it.

rossul

Participating Frequently

@Sherif Assaf
Nov 2019 — We're actively working on addressing this issue... Stay tuned!
Jan 2021 — It is certainly a high priority in our roadmap... Stay tuned!

Any chance we can get more than just canned replies? Something like "this feature is on track to be part of the upcoming version 38 that is scheduled on ..... " would be helpful.

J

jonotrhc

Participating Frequently

Go to YouTube.
Search for Figma Variants. The UI in Figma for variants (states) is well done, even allows for boolean toggles.
Figma's approach with variatns is the future of what used to be just states. Variants are getting close to stylesheets (CSS) which is what we need.

I think the XD team knows this. Fixing "States" does not solve the bigger problem for XD, so it doesn't make sense to fix just states when the competition is way beyond this now. I am sure the XD team will come up with something great eventually, but I had to move on a long time ago, and couldn't be happier.

I've been using XD, Sketch and Figma for real work for years, and Figma is the current winner - as someone who designs and codes, Figma is years ahead at this point.

You can use Figma for free to get a feel for it. Watch Pablo Stanley's videos for an easy-in approach. The Figam team videos are great too.

MatiouLilou

Known Participant

That's amazing, thanks. I'll definitely check Figma Variants!

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded