The most likely cause of this is that each jQuery UI plugin has a plugin instance stored in the data for that DOMElement. Cloning the DOM will result in the cloned plugin instances still referencing the old DOMElements. There's a ticket to make this work: http://dev.jqueryui.com/ticket/3803
If you're interested in helping out, you can add thoughts/patches for solutions to the ticket or you can start a discussion in the jquery-ui- dev group (though there won't be any benefit in starting yet another thread without a proposed solution or patch). Hope that helps. On Mar 21, 1:22 am, Saurabh <[email protected]> wrote: > hi, > > in our application we are caching the dom when we change tabs. by > caching i mean we clone whole dom in a javascript variable and keep in > memory. once the user returns to the cached tab we render that dom > again. > > what i have created here is a simple example of what we are doing in > our application. here in example i an taking full dom in a variable > when you press "cache and render again". you will see some alerts > which will explain the process. > > http://reach1to1.com/sandbox/jquery/cache_problem/index.html > > problem is datepicker or any other widget stops working once i do > this. > > waiting for replies, > > thanks in advance, > > regards, > saurabh --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
