Side navigation
#1127 closed feature (fixed)
Opened April 16, 2007 04:54AM UTC
Closed August 31, 2007 06:51AM UTC
replaceNode support
| Reported by: | pfh | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.2 |
| Component: | core | Version: | 1.1.4 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
While replacing a node can be trivially achieved by .after().remove(), this is not an atomic operation and can cause twitching (at least in Firefox). The DOM has an atomic replace operation, replaceNode, that avoids this problem.
Atomic replacement would be especially useful for edit-in-place.
Attachments (0)
Change History (1)
Changed August 31, 2007 06:51AM UTC by comment:1
| description: | While replacing a node can be trivially achieved by .after().remove(), this is not an atomic operation and can cause twitching (at least in Firefox). The DOM has an atomic replace operation, replaceNode, that avoids this problem.\ \ Atomic replacement would be especially useful for edit-in-place. → While replacing a node can be trivially achieved by .after().remove(), this is not an atomic operation and can cause twitching (at least in Firefox). The DOM has an atomic replace operation, replaceNode, that avoids this problem. \ \ Atomic replacement would be especially useful for edit-in-place. |
|---|---|
| milestone: | 1.1.3 → 1.2 |
| resolution: | → fixed |
| status: | new → closed |
| version: | 1.1.2 → 1.1.4 |
Fixed in SVN.