Thank you Ricardo. I could do a callback but there are a number of different types of things that get inserted so it's spread out across a number of functions. And these will likely grow with time. I think what I'm realizing is that what started as a "what would happen if I..." idea has now turned into a poorly architected (read: not at all) app. I probably need to take what I've learned and just start over. ouch.
Will On Apr 5, 2:19 pm, Ricardo <ricardob...@gmail.com> wrote: > Firefox has events for node insertion > etc:https://developer.mozilla.org/En/DOM_Events > but they are not available to IE, and can incur in significant > overhead for the page. > > If you're in control of the whole app's code, couldn't you just add a > callback for when a widget is added? > > On Apr 5, 2:08 am, will <willthem...@gmail.com> wrote: > > > Hi, > > > I'm trying to bind a function to the body element of a document that > > will fire any time any part of the page's DOM changes. > > > $("body").change() doesn't seem to do it. It does for some changes but > > not all. In particular, not when HTML or element attributes are added/ > > removed. Sorta key! It does trigger when a jEditable element is > > "saved". > > > What I'm trying to accomplish, in case some one can suggest another > > way: I'm making something sort of like iGoogle. When some one adds or > > edits a widget, I want to let them know the page contains changes and > > they orta think about saving it. Autosave isn't really an option as > > this app will save multiple pages. > > > I'd appreciate any insight. > > > Will > >
