New and returning users may sign in

We're glad you're here

Please sign in to leave feedback

Signed in as (Sign out)
Close
Close
← Adobe XD: Feature Requests

Request details

Feedback

Adobe XD: Feature Requests: 01 : Design mode

Categories

  • CATEGORIES
  • All ideas
  • My feedback
  • 01 : Design mode 1356 ideas
  • 02 : Prototype mode 368 ideas
  • 03: Share mode 46 ideas
  • 04 : Sharing on the web 214 ideas
  • 05 : Asset exporting 154 ideas
  • 06 : Extensibility 37 ideas
  • 07 : Integration with other tools 117 ideas
  • 08 : Mobile (iOS) 25 ideas
  • 09 : Mobile (Android) 18 ideas
  • 10: Developer Handoff 138 ideas
  • 11: Plugins 134 ideas
  • Other 102 ideas

(thinking…)
  • Searching…

    No results.

    Clear search results
    • Adobe XD: Feature Requests 2,836 ideas

Keep elements properties between states (propagate text)

It would be awesome to be able to mark some elements inside a compontent to not change some properties on its states, for example, text. If I change the text on the main state, it would change the text inside the other states. With that, I would be able to improve my work on making hover buttons all over my prototype. The way it is now, I need to change the text inside all the states, what makes it impossible.

  •  
    button.png 23 KB
  • CTA qui déconne un poil.mov
    CTA qui déconne un poil.mov 5187 KB
  •  
    Component state editing.jpg 79 KB
  •  
    Component Change Propagation.png 119 KB
  •  
    Screen Shot 2021-01-20 at 10.07.31 PM.png 38 KB
179 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

Anonymous shared this idea  ·  November 11, 2020  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →

How important is this to you?

We're glad you're here

Please sign in to leave feedback

Signed in as (Sign out)
Close
Close
AdminElaine (Adobe) (Product Manager, Adobe) responded  ·  August 24, 2021

Apologies! I sent the Email to the wrong ticket.

Show previous admin responses (1)
action-required  ·  AdminElaine (Adobe) (Product Manager, Adobe) responded  ·  August 24, 2021

Thanks for filing a ticket! This seems like a bug and not a feature request, so you should definitely file this on the Community Support Forum. https://community.adobe.com/t5/adobe-xd/bd-p/xd?page=1&sort=latest_replies&filter=all

Tweet
  • Remove
Attach a File

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
  • Eugene commented  ·  May 18, 2022 07:06  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

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

    Submitting...
  • Timo commented  ·  April 21, 2022 07:05  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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?

    Submitting...
  • Oyunbold Bayansan commented  ·  April 18, 2022 21:09  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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.

    Submitting...
  • Mr. D commented  ·  April 08, 2022 05:12  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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.

    Submitting...
  • Edu Couchez commented  ·  April 06, 2022 05:20  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    2022... not solved yet.

    Submitting...
  • Mike L commented  ·  February 22, 2022 14:09  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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!

    Submitting...
  • Johan commented  ·  February 03, 2022 06:11  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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.

    Submitting...
  • Matthias Dreher commented  ·  January 21, 2022 02:18  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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.

    Submitting...
  • Bruno De Simpelaere commented  ·  January 19, 2022 04:39  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

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

    Submitting...
  • Romain Guilbault commented  ·  January 05, 2022 08:56  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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 :(

    Submitting...
  • Mike L commented  ·  December 03, 2021 09:20  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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.

    Submitting...
  • Martin Schilde commented  ·  September 19, 2021 23:09  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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, …)

    Submitting...
  • Martin Schilde commented  ·  September 19, 2021 23:09  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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, …)

    Submitting...
  • Evaluz Luna commented  ·  September 16, 2021 08:15  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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.

    Submitting...
  • Anonymous commented  ·  September 03, 2021 05:46  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Please do this quickly - this is a huuuge time-waster.

    Submitting...
  • Anonymous commented  ·  August 23, 2021 07:34  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    See also: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/39051064-create-new-main-component-from-existing-component

    A duplicate of a component as a new base for another element could help here to keep also other properties e. g. width.

    Submitting...
  • Anonymous commented  ·  August 17, 2021 08:30  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Description: I want to create a button with text and different states as a component in the library. Each state should show the same text. Only element properties like the color of the button, the button outline and the text color should change from state to state. In the component instance it should be able to change the text in the default state and then all states take and display this text.

    Current behavior: When I create new states of the button, each state gets a copy of all button elements. If I now use this button from the library, I get an instance, where I can change the text of the button. But the text will only be overridden in the current state and not in all states at once. I need to go to each state and change the text to the desired button name. This is much work when having a lot of states and a lot of different buttons.

    Solution: Add the property “Keep text of the Default State” as an option for a component instance.

    Value: It saves time in the prototype creation phase if I only need to change the text of the default state in an instance of a button component with many states.

    Submitting...
  • Michael Provenzano commented  ·  August 11, 2021 04:21  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    A checkbox to ALLOW for text propagation would be an invaluable addition for designers, not only for their workflows but for developer handoff. As someone who wears both hats, I tend to be a developer-friendly designer.

    To ensure consistent typographic styles, including padding, I create a "Text | Content" component. I can then toggle between text states as if they were HTML classes or HTML tags (H1, H2, H3, P, etc.) While this approach is faster and more flexible than having separate components per tag/class, I have to copy and paste the text from one state to another if I decide to change my styling from an "H1" to an "H2", for example.

    This feature would speed up my workflow while ensuring consistent typography in my designs.

    Submitting...
    •  
      Screen Shot 2021-08-11 at 7.11.20 AM.png 27 KB
  • Ara Garabedian commented  ·  August 04, 2021 16:55  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Hahaha, a blast from the past indeed, but a bit more useful for components than what we have now imo

    Submitting...
  • plainclothes commented  ·  August 04, 2021 15:38  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Wow -- that Flash reference brought back some painful memories!

    Submitting...
← Previous 1 2 3 Next →

Adobe XD Feedback : Feature Requests & Bugs · UserVoice Terms of Service & Privacy Policy · Adobe Terms of Use · Adobe Privacy Policy