As far as angular, and SPAs in general, are concerned, I'm a complete newbie. I'm not even a frontend developer, but I've written a fair share of JavaScript and CoffeeScript. I have some experience with pjax, which is similar in that it replaces parts of a page without changing to another page.
What I learned there is that lots of JS libs don't handle it gracefully when the DOM is changed. They attach their event listeners to the original page contents and don't notice changes later on. Now, in my own code I can avoid this problem by using delegation instead of binding handlers to specific elements. At times, I have resorted to explicitly firing a "dom:changed" event and re-wire things in a handler. Is this a common problem with the current state of JS libs or is it really not much of an issue? Are there any best practices I ought to be aware of, for writing libs that can deal with DOM changes and to handle those that don't? Michael -- Michael Schuerig mailto:[email protected] http://www.schuerig.de/michael/ -- 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.
