Hit area of component Hover state

[Markus_Kuuranta]

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.

[LOGAlex]

OK I've tried it a few more times. It sometimes works and sometimes doesn't. Also editing anything else inside the 'hover' state can cause the bounds to recalculate themselves and then it breaks the whole thing. Thanks for the workaround but it really needs proper support for cases like this, this feels more like i'm leveraging a bug within XD to get it to hackily work.

[Kenneth Kawamoto]

Yes, this is basically exploiting XD's bug, so not an official way and unreliable

[ThomHayes]

Thanks for finding this workaround - worked for what i needed too. But yeah, bit of a pain that if you need to make any edits to it, the bounding box resets and you have to build the component again from scratch! 

[Lukas-r24]

Hi, I'm looking for a solution to this problem.
Has Adobe resolved the problem after two years?

[Shoaib Ur Rah384642869nlh]

1 more thing. after hiding the layer please also uncheck the auto layout "fixed width" and "Fixed Height" that will reduce the boders to only button. so rest will not disturb.

Hope it helps

[_OTA_]

thank you!! struggled with this for three days..
if it helps anybody i tried to do the same where my hover area will  also act as a button to another page, i thought the button wouldn't work when hidden in hover state but it worked. i just switched the component back to default state and exited the component' after that i adde a tap prototype to the button while in default state.