Bug Tracker

Opened 15 years ago

Last modified 14 years ago

#1127 closed feature

replaceNode support — at Initial Version

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.

Change History (0)

Note: See TracTickets for help on using tickets.