Side navigation
#10882 closed bug (fixed)
Opened November 24, 2011 08:28AM UTC
Closed November 24, 2012 08:26PM UTC
Cannot fire/handle custom hover event in jQuery 1.7
| Reported by: | Gidon | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | 1.next |
| Component: | event | Version: | 1.7.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
See the following fiddle: http://jsfiddle.net/s6gSe/
When running in jQuery 1.6.4, it works great.
Going up to 1.7, the custom hover event is not anymore handled. While my custom dblclick event is still handled correctly.
Attachments (0)
Change History (8)
Changed November 24, 2011 08:45PM UTC by comment:1
| component: | unfiled → event |
|---|---|
| milestone: | None → 1.next |
| priority: | undecided → low |
| resolution: | → duplicate |
| status: | new → closed |
Changed November 24, 2011 08:46PM UTC by comment:2
| resolution: | duplicate |
|---|---|
| status: | closed → reopened |
Changed November 24, 2011 08:46PM UTC by comment:3
| owner: | → dmethvin |
|---|---|
| status: | reopened → assigned |
Changed December 05, 2011 02:04PM UTC by comment:4
I was trying to add a custom event called 'xyz.hoverUrl.set' and it replaces that event with 'mouseleaveUrl'
The regex is too permissive in the hoverhack. Please make it more specific.
test case:
//////////////
var a = {};
$(a).bind('xyz.hoverUrl.set', function(){return});
//////////////
look at events for a and you will see 'mouseleaveUrl'
Changed March 04, 2012 07:54PM UTC by comment:5
@richhensel, that bug doesn't appear in 1.7.1 as far as I can tell, but if it does please create a new test case and ticket.
Changed June 26, 2012 01:37AM UTC by comment:6
Now that #11731 has deprecated the "hover" event for 1.8, this may be fixable once that hack is removed.
Changed October 22, 2012 05:28PM UTC by comment:7
| owner: | dmethvin |
|---|---|
| status: | assigned → open |
Need to actually move the deprecated code and unit tests to the jquery-compat plugin and write a unit test showing a custom "hover" event can be triggered now.
This was introduced by the "fix" for #7139, which I would gladly remove given its confusing properties. Perhaps we can convince everyone to remove it.