#8397 closed bug (duplicate)
.hover + .clone(true) broken?
| Reported by: | cowboy | Owned by: | Rick Waldron |
|---|---|---|---|
| Priority: | high | Milestone: | 1.next |
| Component: | manipulation | Version: | 1.5.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Maybe this is a bug. Event callbacks bound with the .hover helper function don't seem to get copied over with a .clone(true).
http://jsfiddle.net/cowboy/d6wm8/
(Tested in Chrome 10 beta)
Change History (7)
comment:1 Changed 9 years ago by
| Component: | unfiled → manipulation |
|---|---|
| Priority: | undecided → high |
comment:2 Changed 9 years ago by
| Owner: | set to Rick Waldron |
|---|---|
| Status: | new → assigned |
comment:3 Changed 9 years ago by
Hmmm... Seems like *any* events attached via the special events API may not have their setup/teardown done properly unless they take the possibility of cloning into account. For example, #7340 (backed out in 1.5 for other reasons) was trying to remember the number of attaches so it could disconnect the event when it dropped to zero. That's gonna break if you clone elements.
comment:4 Changed 9 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | assigned → closed |
comment:6 Changed 9 years ago by
same problem here. Hover events are not copied. As well as with 1.4.2 as with 1.5.2
comment:7 Changed 8 years ago by
Same thing for me. I'm using quicksand to clone elements and then when I try to use the .hover on it, simply doesn't work.
More specifically, mouseenter/mouseleave: http://jsfiddle.net/danheberden/d6wm8/3/
Ben also asked about focusin, wrt possible events getting missed