Side navigation
#1475 closed bug (fixed)
Opened August 08, 2007 10:26AM UTC
Closed December 12, 2007 01:46AM UTC
clone() stop event propagation
| Reported by: | gregoire.cachet | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.2.2 |
| Component: | event | Version: | 1.1.3 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
I'm trying to clone() a DOM node during a change event on this node.
It appears that it stop the propagation of my change event (actually it should call another callback function after the callback who clones the node, that's how I noticed because it wasn't called).
It works fine with the DOM cloneNode() method.
I'm running Firefox 2.0.0.6.
Attachments (1)
Change History (3)
Changed August 10, 2007 06:28AM UTC by comment:1
| component: | core → event |
|---|---|
| milestone: | → 1.1.4 |
Changed September 27, 2007 03:17PM UTC by comment:2
| need: | Review → Test Case |
|---|
Changed December 12, 2007 01:46AM UTC by comment:3
| milestone: | 1.1.4 → 1.2.2 |
|---|---|
| resolution: | → fixed |
| status: | new → closed |
I was unable to reproduce this in the current SVN. Clone has changed quite a bit since 1.1.3 so I'm going to mark this as fixed. If the test case isn't what you had in mind feel free to reopen the bug and attach one that shows the problem.