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.
Apologies! I sent the Email to the wrong ticket.
Maybe we can have it when you right click a component and select "Force changes through all states"?
Dunno if someone has requested this or if already possible somehow, but this would save me sooo much time.
Example: If I make a button component (or whatever) with multiple states. If I change the button text in default state it will change the other states as well of this master component. Can we have the same for child components please?
Kit Grose commented
I often design something as a component and make many instances of it before realising I need a variation of the component that substitutes something like an icon (using a nested component).
So I edit the main component for my element, add a new state, swap out the icon with another component and then go back to the specific instance of the component and apply the new state only to find all my text overrides are reset.
This is hugely painful and requires a huge amount of manual correcting.
When editting a Text in a component on Default State also edit on the rest of the States.
Adam CLark commented
It is frustrating when placing a component instance, specifically a button, on the artboard and change the buttons label for every state.
This can be a very time consuming and manual process.
Could we have an override of some fashion to fix the label of all states? Something in the instance properties perhaps and a text field to set the label of the button?
Moises Lopez commented
I have component where the Default state of my text link has a font family as Regular, and in State 2, I changed the font weight to bold, it becomes very painful to reuse that component because I have to re-write the copy in every state. Imagine doing that for 20 links on a main navigation panel... not very fun to maintain either.
Axel Grollemund commented
When using the states for a button or any other component using text.
When using the states for design systems and use it across different features, I need to be able to change the text without having to change every states. Its really time consuming.
Would be great if we could have a text overwrite that replace all the texts keeping the styling of every state.
Matt Playford commented
when creating rollovers it would be nice to create a component with rollover state. The reuse component - changing text in default state, then it automatically being updated in rollover state. I thought it did this but its not doing for me. Which makes creating repeatable simple rollovers pointless.
There is a huge problem with child component and you should take it into consideration.
In my design system I defined a button, my master. This button is made of a background color and a label. There are different state for my button : normal, hover, pressed, disabled, error. So the background or the border and even the color of my label change depending of the state.
When I changed the label's value text on the main state all the other state are changed accordingly. Wonderfull !!!
It's exactly what I want for all childrens in all my different prototypes using this button. But it's not possible... If I change label's text in the main state of a child button I have to change manually all the other state ! And it's huge ! So much time lost... And I don't speak about the fact that if I change the master component children will not take the change.
So may be one solution could be to tag my label's text as overriden element so the value of the label is not part of the component.
If your have questions :)
Melissa Sanchez commented
To have the ability to select which content is kept throughout the different states (text, size, colors, etc), sometimes for example text content is not always auto-updated and has to be changed on all states of each instance.
Components are meant to be used multiple times. Most of the time, when a component, for example a Picture-Text-Link, is used many times we need to change the text und the picture. This has to be done for every state of the copied component manually (default state, hover state, ...). This takes a lot of time and can be slightly annoying.
It would be a great update if changing the text and picture in the default state of a copied component would automatically be adapted in every state of the copied component.
Kieran Hawes commented
The ability to have multiple formats spanning across devices (mobile, tablet, desktop etc.) under one component would be a game changer. If I change the colour of a button on desktop it's replicated across all the components formats.
Currently if a client makes a last-minute request to change fonts, colours etc. we have to make the change across all devices.