Skip to main content

Bug Tracker

Side navigation

#8397 closed bug (duplicate)

Opened February 27, 2011 11:08PM UTC

Closed March 07, 2011 05:08PM UTC

Last modified March 13, 2012 02:37PM UTC

.hover + .clone(true) broken?

Reported by: cowboy Owned by: rwaldron
Priority: high Milestone:
Component: manipulation Version: 1.5.1
Keywords: Cc:
Blocked by: Blocking:

Maybe this is a bug. Event callbacks bound with the .hover helper function don't seem to get copied over with a .clone(true).

(Tested in Chrome 10 beta)

Attachments (0)
Change History (7)

Changed February 27, 2011 11:10PM UTC by danheberden comment:1

_comment0: More specifically, mouseenter/mouseleave:
component: unfiledmanipulation
priority: undecidedhigh

More specifically, mouseenter/mouseleave:

Ben also asked about focusin, wrt possible events getting missed

Changed February 27, 2011 11:58PM UTC by rwaldron comment:2

owner: → rwaldron
status: newassigned

Changed February 28, 2011 04:08PM UTC by dmethvin comment:3

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.

Changed March 07, 2011 05:08PM UTC by rwaldron comment:4

resolution: → duplicate
status: assignedclosed

Changed March 07, 2011 05:08PM UTC by rwaldron comment:5

Duplicate of #7037.

Changed April 14, 2011 01:15PM UTC by anonymous comment:6

same problem here. Hover events are not copied.

As well as with 1.4.2 as with 1.5.2

Changed May 17, 2011 01:10PM UTC by jaisonn comment:7

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.