Opened 12 years ago
Closed 11 years ago
#10882 closed bug (fixed)
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.
Change History (8)
comment:1 Changed 12 years ago by
Component: | unfiled → event |
---|---|
Milestone: | None → 1.next |
Priority: | undecided → low |
Resolution: | → duplicate |
Status: | new → closed |
comment:2 Changed 12 years ago by
Resolution: | duplicate |
---|---|
Status: | closed → reopened |
comment:3 Changed 12 years ago by
Owner: | set to dmethvin |
---|---|
Status: | reopened → assigned |
comment:4 Changed 12 years ago by
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'
comment:5 Changed 12 years ago by
@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.
comment:6 Changed 11 years ago by
Now that #11731 has deprecated the "hover" event for 1.8, this may be fixable once that hack is removed.
comment:7 Changed 11 years ago by
Owner: | dmethvin deleted |
---|---|
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.
comment:8 Changed 11 years ago by
Resolution: | → fixed |
---|---|
Status: | open → closed |
Close #10882. Test case for "hover" event in 1.9
Changeset: 6b00b3cad94e348c0ba31c196aaac9fbf819fea3
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.