Improperly triggers mouseout when hovering a child inputs auto complete suggestion.

[alastairjwright]

Like the r5 issue which would improperly trigger mouse out when entering a child input[type="text"]. Same issue except it happens when you hover over a chrome autocomplete suggestion for an input element.

Reference to old bug: "hoverIntent r5 suffers from a defect in Google Chrome that improperly triggers mouseout when entering a child input[type="text"] element. hoverIntent r6 uses the same mouseenter/mouseleave special events as jQuery's built-in hover, and jQuery 1.5.1 patched this issue. Thanks to Colin Stuart for tipping me off about this and for providing isolated code to demonstrate/test."

[usmonster]

Thanks for reporting this, @alastairjwright! Are you using the tagged v1.8.1 version, or the version from the master branch? In what version(s) of Chrome have you seen this?

Can you please provide a simplified demo via jsFiddle/jsbin to help us investigate? Thanks again!

[alastairjwright]

Yes this is using the most recent version of hover intent and the most recent version of chrome (44.0.2403.107).

Just click the input in the menu dropdown and hover one of the input suggestions by chrome. Note, if you're on a new browser the input field may not offer any past email address suggestions.
http://jsfiddle.net/alsweeet/9x1cnteh/

[usmonster]

I'm not seeing any issue on my end. I am able to hover over the autofill suggestions, and the out handler is not called at any time.

To further help investigation, can you tell me what OS you're using? Also, can you make sure the issue you are experiencing doesn't manifest when you use jQuery's own .hover() method?

[alastairjwright]

I am seeing the bug on Mac OS X Yosemite (10.10.5). Just tested on windows and the bug is not present.

[usmonster]

Ah, that's a clue. I will try to take a closer look later in the week.

In the meantime, can you verify that this doesn't happen with normal .hover(), and can you also check this with the previous version(s) of hoverIntent to help identify when this issue appeared? (If you're feeling ambitious, you can maybe do a git bisect.. ;)

Thanks again for the quick feedback!

[usmonster]

I took a look, and it also happens when using jQuery's .hover(): http://jsfiddle.net/9x1cnteh/2/

This seems to be a bug in Chrome on Mac, possibly related to this one: http://crbug.com/475366 . You can star and comment on the issue there to get it more attention, though it looks like it's being worked on.

As this is not an issue in hoverIntent (and a workaround for a transient, low-impact bug seems unnecessary), I'll close the issue. Thanks yet again for your report!

[matthewstick]

Is there going to big a fix for this? I am having the same issue

[usmonster]

Hello @mdunnerstick. Thanks for your comment!

This issue was closed. If you're experiencing something similar, please open a new issue with clear reproduction steps and a link to a demo using JSFiddle, CodePen, or similar.

Thanks!

[matthewstick]

I made a new issue:
#75