I want the option when setting up character styles that there doesn't need to be a color associated with the character style.

For example, I set up my H1, H2, H3 with their respective font families, font weight, & font size. But my design has different background colors. Sometimes my H1 is lack on a white background, which is how I set it up in the Character Styles. While other times my H1 is white on a black background,. But if I change the H1 to white it no longer correlates to the H1 I setup in my character styles unless I create another H1 variant that has the color white.

I would like if my character styles were color agnostic so I can make sweeping changes when editing my text without having to create multiple color variants of my character styles

◆ Overview
After releasing "State" feature, it's been able to prepare complex interactions like "hover." Following feature may help to reduce required time preparing a new component with similar behaviors/instructions.

◆ Actual
New component with state settings every time when a similar behavior is expected in different look and feel.
(Currently, preparing another XD file is believed to be the only solution to avoid this by selecting "Make it as local component" after loading it from another XD file.")

◆ Expected
By select "Use it as a new Master Component" is to make a new Master component instead of copying it as an instance component.

◆ Why is this valuable to you?
When using a single, new XD file and load a master component from other XD files, it is possible to make it "local component"; however, it is unable to make it happen within the same XD file.

This helps to reduce time to prepare a set of basic state setting from the beginning each time. This also helps NOT to get affected unconsciously on the new component by editing the template master component by someone else.

Since Co-Editing feature is now beta version, some larger project may have a couple of co-editors of components on the same XD file in the future. While a group of designers keeps upgrading a basic behaviors for future use, another group of designers is working on on-going project to finalize a specific look and feel based on the template component.

Let's say we want to add a Radio Group and use our Design System Radio Button Component for that. Currently it's not possible to set one of the components to the selected state.

As a workaround we can create the list with the repeat grid, then ungroup it and change the desired item. But that can't be how it's intended to work.

ps: I feel bad for lodging a Feature Request days after you released such a great feature. It sounds lI'm ike complaining instead of being thankful - thats not the case, the component states are awesome,d thank you all for this!

When I type in a text box on the artboard and I hit escape it keeps the text I just changed and takes me out of editing mode with the cursor.

When I type in a layer to change the name of it and I hit escape it removes the changes I just made and take me out of editing mode with the cursor. To effectively keep the changes I must hit return on the keyboard.

If I hit return on the keyboard while editing a text box on the artboard I get what I would expect -- a carriage return.

It would be great if while editing a name of a layer and I hit escape or return it would keep the changes. I find that I am often duplicating items changing text and changing layer names and having to mentally switch back and forth from remembering to hit return or escape is a point of frustration.

(1) While editing a component, you can't change the state of the component unless you click on the parent layer first.

The State menu in the inspector panel disappears when you select anything other than the root layer. This makes it so you cannot change the state unless you have the root layer selected.

Instead, the State menu should be available while any layer inside the component is selected.

Let's say I'm making a button and changing the size of the shape layer. I want to match the Default state and Hover state, so with the shape layer selected I don't have the Component State menu available. I need to click on the root node of the component to get the State menu, then I can change the state, then I need to drill back down to the shape layer again.

It would be great if the State menu was ALWAYS available when working inside a component. For example while my button shape layer is selected, the State menu should STILL be available in the inspector panel so I can switch states without having to click out to the root layer first.

(2) It's a lot of clicks that gets very tedious. It's stupidly inefficient, especially since the layers panel and the State panel are on opposite sides of the screen.

The "Stack" feature added recently is very useful, it helps a lot when designing components, but it is still limited.

Today the default behavior is always to push the elements to the right, and this is not the correct thing every time.

The resource could have a way of defining which way the elements will be pushed, similar to the responsiveness control.

Example: In a navbar I have buttons that are fixed on the right, when updating the button text, alignment on the right is lost.

Attachments:
"Stack example - Master component.png" shows the master component and the configuration used.

"Stack example - instances.png" shows an instance of the component, the current behavior and the suggestion for improvement.

Component states are awesome, but right now the size increase for a complex component is not scalable. After doing some testing, components appear to increase their size proportionally to the number of states.

For example if I have a Default state, create a new state and move the components, say in a mask, to do an animation the size has now doubled. Then if I copy that to a new artboard, it doubles again, because both states get carried around. Therefore what originally would have been a master with an instance in 2 separate artboards with size 2X is now size 4X because there are two instances with 2 states. Add another unused state and it is now 6X

I understand why this method would be used, but it has not been scalable for some of our work.

Any plans to address this?