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

Now that the "Tap/Hover Effect" request ()https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/12941394-tap-hover-effect?tracking_code=c41a5301558789f85205f7c47ec8b9ca) is officially closed, we need a feature to do what (I believe) the 8952 people who voted for it have been asking for since March of 2016:

A way to assign Hover events as triggers for the existing interactions platform.

Component states is a wonderful addition to XD, but it barely scratches the surface of what designers need for prototyping hover events.

We need to be able to add tooltips, menu pop-up overlays and many other effects that still can only be achieved by transitioning to another artboard. As it stands, to prototype a menu overlay that will ultimately occur as a hover event, we must use the "Tap" trigger and tell the design reviewer "this will be activated by a mouse-over event, we just can't simuate that with our current tool."

Obviously, XD is able to trap the hover event. We just need it to be wired to the transition interactions.

i ve just noticed you removed the preserve scroll position from design. This is a horrible thing for me. Doing that forces me to prototype EVERYTHING.

for example: i have 100 artboards that are unconnected due to time saving ( i dont need to prototype everything ) but moving that button forces me to do it becaus now i cant make a quick preview for my client where he can scroll up and down. Now i will have to connect ALL 100+ boards together.

why? Because when you are EXPORTING for REVIEW or DEVELOPMENT
only the connected boards are being exported. which is a horror for a long time now for me, and that is why i rarely prototype more than 5 artboards together when i have serious design work

this takes up soo much time

Trying out the new coediting feature in November 2019 update. It's good and convenient. However, i currently encounter document crashing as it is unable to reconnect.

Having previous version is helpful as it backs up my working file and enabling me to download it. But I would still like it to be saved into the same document instead of forcing me to close. The current cloud doc is considered as a corrupted file. It is troublesome as I need to recreate a new cloud file for other partners once again. Viewer/reviewers also cannot use back the same link to view the file.

Reverting back to previous version should work with the same link instead.

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!

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?

FINALLY there's a hover state on components! GREAT!

However I quickly ran into a limitation. When the user touches a button or clicks it with the mouse/trackpad, the button needs an "on tap" or "on click" state that very briefly changes a button's appearance to give the visual feedback "your click or touch was detected".

So now that you have HOVER please add ON CLICK/TAP ort whatever you want to cal it.

Basically the component state changes for a definable amount of time before the destination or next state is triggered.

While you're at it, how's about looking at some of the long-time available link states we know from the web, like visited, or on-focus (when users like to use the tab button to move from button to button)