Great, thanks for your reply. I guess i'll see if role attributes will do the job, as my own replace directive sounds like the sort of thing i could really screw up :)
On Wed, 20 Jan 2016 at 06:18 Sander Elias <[email protected]> wrote: > Hi Kenese, > > As an alternative you can build your own replace directive. There are some > mayor pitfalls with it tough. (the core reason it's deprecated to begin > with). If you know your code and use cases, it can be worked around. Not an > easy task tough. Part of the problem is, that the dom nodes you remove are > holding the angular references you want to keep (this is put a bit simpler > as it is..) > > Regards > Sander > > -- > You received this message because you are subscribed to a topic in the > Google Groups "AngularJS" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/angular/rq94vFZagNs/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
