Closed duhrer closed 9 months ago
In recent manual testing, it really does seem like tooltips work as they would for a keyboard without muddying the waters and act like both a mouse and keyboard. I think we should close this one unless we have a more specific example of why it's needed.
Currently, when navigating between elements, we blur the previous element and focus on the new element. For tooltips and the like, it might be better to also simulate a hover. Unlike focus, there is no explicit method to hover over an element.
We might be able to simulate this by sending a
mouseenter
event beforefocus
, and amouseleave
event beforeblur
.We should test this with an element that has a tooltip on hover out in the wild using the developer console first.
This might make sense to tackle either right before or right after #139 (simulated mouse), as we will need to simulate a range of mouse events, including hover. It might also be helpful with regard to #124.