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.

Right now, bounding boxes are always rectangular, with the height of the tallest object it contains and the width of the widest one.

However, many times it is necessary for the box to maintain the exact same shape as the objects it contains, in order to only activate effects such as hover when the mouse is directly on top.

Consider the attached files. Here we have 3 tabs. I would like to make them "jump" up slightly on hover so users can tell it is clickable. The tabs do not overlap, but because the bounding box is rectangular, the active area of the first tab overlaps the other two. Therefore, when my mouse hovers over the second and third tabs, the first one does its "hover effect" because its bounding box covers that area.

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)

It can be great to be able to prototype complex animations and interactions. It can help us create more concrete prototypes with mouse and scroll animations or also infinite loop animations.

Detail of the idea in this article : https://uxplanet.org/the-killer-feature-im-waiting-for-in-our-modern-design-tools-87c3a5d3c4b3

Summary of the idea :
A 3 step process which allow you an infinity of possibilities by customizing each property with a math formula. We add syntax highlighting to help designers differentiate dynamic properties, static properties and constants or math functions.
Then, AdobeXD previewer will “just” have to recalculate and update these properties at a 60 Hz frequency to make our animations alive.
We can image some subfeatures to make this tool more powerful :
Autocompletion (like code editors) to help designers find the available properties to play with and the math functions they can use
A predefined animations library to help designers taking in hands this new feature before diving into custom formulas
The possibility to use other elements properties values as variables to create more complex animation (for exemple : use the current x position of a card to determine the opacity of its content)
Built-in easing functions we can use in our math formulas to help us create smooth interactions (yes, easing is also math)
The ability to work with more complex properties like colors, 3D rotation or 3D translation. All these properties have subcomponents, therefore we can define a formula for each subcomponent as below

Currently when you copy a component from one file to another it is a linked component. If you unlink the component, not only is it unlinked, but it is also ungrouped and no longer a component at all. Any additional states you had set up are lost.

Sometimes I don't want to use linked master components from a design system but just want to create a new local master component, similar to one in another file but then make some changes. I'd like to just copy the component over, with all it's states, not linked and make my tweaks to my new master.

Maybe the "unlink component" option just makes it a local master, with states preserved, and you'd have to ungroup it if you just want the objects. Or maybe there is a separate option to "make local master" that unlinks without ungrouping. Or an option to "paste without linking" that preserves component states.

I just want to either unlink a component without also ungrouping the component, or just paste it as a new master not linked, so I can keep my states intact. I copy and paste art between projects all the time and I'm tired of losing component states.

Another use case would be if someone is setting up multiple design systems for different brands, but wants to reuse some art as a starting point. If they've created many states with interactions, they are going to lose them when they copy and paste and unlink the art. I just think we should have a choice to ungroup the component and not have it be a forced function of unlinking.