Why just in review?! This should be there from the first day of instances in components.

PLEASE fix this asap, as it's a much needed and obvious feature to include. It's a mess trying to manually adjust to the same size

Please add this feature!

fix this pleeeeeeaseeeeeeeeeeeeee!!!!!

Yeah, current components are not usable. Just states.

Please fix this! Components are unusable.

it is an extremely important, basic and fundamental function!

Please implement it now, it is absolutely frustrating the current flow and it makes the states on the buttons useless if I have to change a thousand labels every time

As a new user, I found the lack of this feature to be immensely frustrating and one of several workflow issues with components and assets that really hurts XD in terms of building a design system. There is an incredible opportunity with the DSP format and VSCode plugin I am hoping to use here but to get there I find myself forced to do a huge amount of rework to make what should be simple variations of main components to add to the asset library.

I'm in the middle of getting started with XD and this is just a brutal lack-of-feature to stumble across. Trying to use existing design systems for prototyping and figured this would be a slam dunk and is instead making me consider other options.

I too thought it would work like Adobe Animate. It's counterintuitive

Very poor that this features is not implemented after nearly two years. How many developers work on such important features for XD? Zero or even one?

I'm new to XD, i'm a figma user but I wanted to give it a try. This HUGE issue is definitely a deal breaker for me! The request has been made for almost 2 years !

I wrongly assumed that a feature as basic as this would be included and spent a few hours trying to work out what I was doing wrong, or what the workaround was, only to realize that a feature as basic as this isn't even provided :-(.

And yes, it should probably be an optional checkbox to cover those cases when you want a different size for different states.

I´ve been using XD for just a couple of months, saw people asking for this feature during 3 years now (2018), with no solution, and I am already so frustrated about this.

A lame ass workaround in some cases could be to make a separate component of only a button-bg i.e. and give this his own 'hover'-effect.
Than group this with the variables (text) and create a new component who contains both.
Nesting components is the closest we can get.

But I'm very dissapointed that - even after 2 years - Adobe didn't took us serious on this point..

Sketch is far ahead on this point...

Please fix this very basic thing. I'm currently trying to make design libraries easier for the other designers, and this makes it harder

In my workflow I would always want the states to scale. Please fix this

These are the quality fo life issues that prevent XD from being truly wonderful.

Any plug-ins fixing this tedious feature?

Vote up for this! This is absolutely counterintuitive. If I write a button in pure HTML, when I change the text in a button, I am expecting the hover state to reflect the change as well because the HTML takes care of the content, and the CSS takes care of the style. The current workflow doesn't reflect the front-end logic. I also hate the current status of switching between states when modifying the styles. It's so confusing and prone to mistakes. So many times I've done my modification and found I am in the wrong state. That's super frustrating. Why can't you guys come up with a panel that summarizes the differences into several properties that we can play around with? Like what Figma has.

I don't even use hover states for this exact reason. Way too much of a pain!!!