More than one year later, I was wondering if there now was an implemented approach to disable and re-enable watchers from a given scope tree. Anyone ?
On Wednesday, December 18, 2013 at 5:16:20 PM UTC+1, Pierre Gayvallet wrote: > > Hi. > > I have the need to be able to ask a scope to simply stop listening to all > of it's watchers until I ask him otherwise. > > The need is simple : We've got an application with some complexe pages, > complexe enought for performance to start beeing an issue on IE9, and we > need to start perf optim where we can. > > On the app, we've also got a navbar which can open a configuration popin. > > The popin : > a/ can be opened from any page > and > b/ only take 80% of the screen (width and height) , so the page under the > overlay is still visible. > > The popin is model, so when it's open, i KNOW i dont care about UI refresh > ( or anything, for that matter ) on the "underground" page. But I cannot > simply remove the underground page because it's still visible ( and it can > have a state which I dont want to loose ). > > So I would like to just "freeze" the watchers of the page under the > overlay until the popin is closed. > > Is it currently possible with angular watchers ? How could I do to get all > the $watch from a scope hierarchy to temporarily be disabled then > reactivated later ? > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
