The most time consuming job is to text edit names in all existing states in a component instance. For example, text of a primary button label "LOG IN" (master component) is typically repeated from a default to hover and active states; and when using an instance of this primary button component for other functionality (e.g. LOG OUT) designer have to manually edit text label for each state of the component instance (a copy of master).

Here, I am looking for automation to auto-change text label (on demand) across all existing states in a component instance upon the text is manually edited in the default state.

Let's just use logical outcomes shall we?

Why on earth do component states not resize when the component is resized?
Resizing a component should be a single action.
Right now you need one resize action per state and then ensure that the positioning is exactly the same for all states after resizing. Another feature request which is really a bug report...

It's insane that resizing a component with several states requires going through all the states and resizing them individually, there should be a way of doing this in one go.

In all honesty, the WHOLE way interactions and component states work should be reconsidered from the ground up or it's just going to get worse and worse and worse rather than better and better and better...

I've landed here, hoping to find a solution for my components inheriting the text content (between states) from the master component. I assumed that I am perhaps missing the obvious feature. After reading the thread, I have only one question: Who uses this product?

Sometimes I want to make a change to a component that should populate through all or some of the states of my components. I love Layer Comps in Photoshop, where you can propagate a change across multiple selected layer comps at once. I wish there was a way to do this within a component in XD.

When creating a hover state, it would be awesome if the hover state could inheriate the text and asset (e.g. image) from the default state. At the moment, having to change the hover state on every instances is a little onerous.

I'm starting to think about switching our company to Figma 🤣

Hello dear XD Team,
I enthusiastically switched from Figma to XD. And then I have to realize that this function does not exist! Is there a reason for this?

In reality, the states in Adobe XD is not used which means you will fall into a pit when you use the states of components so messy and a bad experience.

That is not to be called a design system haha.

I've been building quite a few design system and this limitation one is by far to most irritating part when it comes to my team using published libraries.

The ability to mark elements as persistent through all states as someone mention in the comment below, is quite fundamental to this overall feature to work properly or at least to feel complete.

2022... not solved yet.

Adding another comment to this thread. We need the ability to mark elements within a component as persistent through all states of the component. This gives all elements within a component the option to be persistent or state-specific.

@elain (adobe) - this isn't a bug, it's a missing feature of the component system.

Thanks!

We NEED XD to keep the labels through ALL STATES/ variants we create so we don't have to change the labels for all states of our component it makes us waist so much time and kills workflow.

Properties on components and their states/variants need to apply separately.

Seems to be the same request as https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/38973007-allow-component-instance-overrides-to-be-inherited, which has considerably more votes. All who voted here might consider voting for the request linked above, too.

Bump! This would save me tons of time... it's like XD doesn't even want to be a design program.

Heyyyyyyyy adobe can you pleeeaaaaase at leaaaaast consider the fudging feature?
Figma had this forever! Gosh using component is sooo frustrating in XD. You can tell by how many letters I had to my words :(

We need a component with the option to keep text persistent. Every time I make a new iteration of a button I have to change the text in every single state of the button.

If I have 10 buttons with 3 states each, that's so much editing of text.

It's not just buttons - cards, simple text links, any component with text and a state other than "default" requires editing of every single state. There should be an option to keep any selected layer persistent across all states.

I can't even count the number of times I've been presenting a prototype, showed a hover-state and was disappointed to find the hover text was wrong.

Working with components becomes a very cumbersome content management task when working with multiple states.

Simple example: a button component with standard, hover and active states. Re-use this component for another button and change the text – I have to update the text in each state separately.

Or have a pic that zooms on hover.

Would be best if I could designate a "variable" like text-field or pic-frame, once filled in in the "standard" state, it carries it´s content troughout different states and ONLY applies changes to it (color, size, …)

Working with components becomes a very cumbersome content management task when working with multiple states.

Simple example: a button component with standard, hover and active states. Re-use this component for another button and change the text – I have to update the text in each state separately.

Or have a pic that zooms on hover.

Would be best if I could designate a "variable" like text-field or pic-frame, once filled in in the "standard" state, it carries it´s content troughout different states and ONLY applies changes to it (color, size, …)

I have created many button states on my main UI (the base of my design system).

BUT when I'm prototyping or building a screen with my UI kit and I change the copy of the "rest" state, this copy doesn't change for the rest of the states which forces me to modify it, EVERY time, BY HAND.

This (as you can imagine) is time-consuming and not ideal.
Id' love if you just allow the component to inherit the copy of the rest state.