>> What was the performance hit? > Triggering an event on every element that's being removed can be > costly if you remove an element that has a large sub-tree. What are > you using the event for? If it's providing useful functionality we > may keep it.
We use it for functionality similar to google pages. We have the front end display and we keep and manipulate the configuration for the page in memory (which is then later saved). By being able to bind remove, we are better able to make sure the config is up to date with what is on the screen. We have other, similar roll-your-own functionality throughout and remove is quite helpful. thnx, Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery UI" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-ui?hl=en -~----------~----~----~----~------~----~------~--~---
