Need Little bit tapping/hover effect on list/buttons/links during presentation to client. Its give an actual working product feel and help to make decision.
Tap & Hover functionality is now available in XD 24!
Dennis Ferreira commented
I really dig this feature request system. Totally makes using your software worth every penny. Thanks.
Vanessa Müller commented
Is this christmas? Thank you so much!
Mohit Saini commented
Thank you Very much
Pablo Sara commented
OMG, THIS IS HUGE!
Christmas came early!
Well done Adobe (round of appluase)
is this real life ? :D
Gil Alroy commented
Works nicely - thanks.
Scott Ehly commented
For anyone disappointed by this feature completion and the lack of support for transitions over state changes, I've created a new request to cover what I believe many who voted for it really wanted: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/38972416-hover-triggers-to-all-elements-to-trigger-artboard
Please add your votes there.
There are some nice aspects to the states with the hover but without being able to manually control this, it is severely limited. For example there is no way to have a simple hover state in which the component expands to the left. Instead it moves the whole damn thing. This is just another basic miss by this app that is frustratingly close to being very good.
hover inside hover is needed
Scott Ehly commented
I was so very excited with the announcement of the latest release. I spent an evening converting my icon library into individual components with multiple states. My excitement melted into despair, however, less than 24 hours later when I actually tried to set up prototypes with hover events.
According to the blog entry for the Nov 2019 release,
"You can also choose to manually apply the hover trigger to any element in prototype mode using the trigger dropdown in the Property Inspector. "
This is, if fact, all I've wanted for over a year now.
Sadly, it's not true. The "Hover" trigger has not been added to the Interactions list for any elements other than components with hover states.
...and that trigger can only change the state of the component. It will not allow navigation to a new artboard.
There´s absolutelly nothing that I can do to make the shared button from my design system show the hover effect on my projects. It´s impossible. I cut the link between my design system and rebuild it, but nothing. It only works on design system screen. The way I found is creating another button. It is very sad... I can´t use it on my actual projects and people are anxious to see all projects with hover effect.
In projects only appears "Default State".
Wow. I can't tell if this is supposed to have been completed in the Nov 2019 release or if it's still in progress. As of this writing, the status still says "Feature-Started _ March 25, 2019".
The Nov release has features that hint at hover triggers, but the resulting capability is extreeeeeeeeemly limited. So, now I can show the hover state of an icon without drawing a separate artboard for it. Wheeee! I still can't show hover activities that are truly substantial.
If this is considered 'completed', then I'm greatly disappointed.
With 8943 votes and 8 months of development, the new feature hardly scratches the surface of what I believe was requested.
Instead of simply trapping the hover event and adding it to the list of potential triggers
(as a recovering software developer, I'm having trouble imagining this could take more than 30 minutes to code),
we get this over-complicated marriage between component states* and specialized/exclusive interactions. What we didn't get was an actual hover trigger.
How can we simulate tooltips or hover-activated overlay menus if we can't assign a hover event to any object and then set it to navigate to the artboard containing the overlay?
In the process of typing this, I've thought up and tested several potential workarounds. Alas, XD has thwarted me at every turn. Clearly, there's more going on here than meets the eye, but without the luxury of an inside view on the code, I can't understand why the interaction menu doesn't simply incorporate the new elements (Hover as a trigger and Hover State as a Destination). Instead, they are completely exclusive manifestations.
* - The component states thing is awesome, btw! It's just not at all what I (and I suspect most of us) actually wanted from this feature request.
Mateus Barros commented
Finally hover is on XD, but is so limited... you can't create a hover with:
- degrees 360°;
Nice, but too basic. Like other said:
1. Hover should be a general trigger, not just for component states
2. Changes to the default state should propagate to other states as well, if unchanged.
You are doing half a job even with this basic functionality, too bad :/
Very nice addition but state changes should propagate in the exact same way as changes between the master component and its instances.
For example, if I change the text or width of the Default state, it should change in all the states where it hasn't been overwritten. And this should affect linked components as well.
That's the only way to make it work in the design systems which Adobe is promoting a lot lately.
EDIT: It seems it works like that within Source file but not with linked components.
It's really hard to understand why it has been accepted like this if during the keynote it has been said that Adobe is using XD and Spectrum to build their products. Does it mean that every time that button component is being used, Adobe designers have to change its label and width for every instance and state that differ from the Master in the Source file?
Good! But testing this feature i found a important thing: renaming a button and resizing the default instanced asset, for example, is not changing it in your other states... that's sad :(
Where the hell are people finding hover at? I updated my XD and still don't see it
EDIT: for anyone looking in the prototype interactions it's not there. It's in component states
Here's a tutorial on it
Stetson Finch commented
OMG AM I DREAMING!?!? IS THIS REAL!?!? Thanks for finally implementing components, Adobe. Luv u <3