We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
Component states are great, but apparently the hover effect uses hit area of all the states.
I'm creating a tooltip for a button that appears by hovering. I'm doing this by hiding a layer in component on normal state, and displaying that layer on hover state.
Now, XD uses the hit area for the component from the hover state, effectively making the hover state trigger for things that are no visible for the component on regular state.
Dear Adobe, please use only normal state of the component for its hit area.
Thanks for reaching out. If I understood correctly, you are talking about the similar feature discussed here: https://community.adobe.com/t5/adobe-xd/feature-request-to-make-component-interactions-have-priority...
If correct, please post a new request or upvote an existing request. If that's not what you are looking for, would you mind explaining a bit more with the help of a few screenshots of the design? We'll try our best to help you with it.
Here's a video that describes the problem.
The intention is to display the text container when I hover on the button.
The text container should not be part of the area that reacts to mouse. However, moving my mouse to the white area above the button seems to trigger the hover state.
Did you ever get a fix or workaround for this? I'm having the exact same problem?