Copy link to clipboard
Copied
Hi Everyone,
I'm in the process of making a prototype and have been struggling finding a way around it.
I have a dropdown navigation and the sub items are larger than the main nav item.
So when I try to hover over the next menu item, the first menu item is still active OR if I mouse off the main navigation item, it's still active.
https://xd.adobe.com/view/e4c42261-3c4f-468f-69e1-8f333b4cd0d3-92f5/
{Renamed By MOD}
Hi Matthew,
Thanks for reaching out. If the bounding box of a component is overlapping with the bounding box of another component then 2nd hover will not activate. The only workaround I can think of is reducing the size to ensure that the bounding box doesn't overlap, I understand that this may not be feasible but I am afraid this behaviour on the app is expected. Having said that, I will pass on your feedback with the Engineering Team and you can do that too by upvoting this request: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/39051358-interactions-are-blocked-when-hover-state-is-open
...Copy link to clipboard
Copied
Hi Matthew,
Thanks for reaching out. If the bounding box of a component is overlapping with the bounding box of another component then 2nd hover will not activate. The only workaround I can think of is reducing the size to ensure that the bounding box doesn't overlap, I understand that this may not be feasible but I am afraid this behaviour on the app is expected. Having said that, I will pass on your feedback with the Engineering Team and you can do that too by upvoting this request: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/39051358-interacti...
Let us know if you need any further assistance, we'll be happy to assist you.
Regards
Rishabh
Copy link to clipboard
Copied
Yes, as Rishabh pointed out, we are forced to use "click" triggers with overlays for such dropdown elements, and the hover "feature" is worthless in that case, as well as many others.
This is the actual functionality that we need, so you should upvote that instead (although it's clear upvoting has little effect on the features that are developed 🙂
In this way the hover event would work like it works irl with CSS. Unfortunately, that's yet another problem with the half-baked component states feature.