If you are binding models to inputs that are included via a template, then
you end up with these spans inside your input fields, which will not only
break any type of CMS functionality but will also be visible to your users
as HTML when all they expect to see are values.
Michael Bielski says filter them out with .not(".ng-scope") but if you do
this you also filter out their content, so that won't help you if you are
trying to get to their content.
In my view this is a major problem. A javascript framework inserting
name-spaced attributes to existing HTML is one thing, taking away your
control over your HTML is quite another... that makes it disabling rather
than enabling for the developer and reminds me of my (shudder) Dreamweaver
days. I personally think this is an unjustifiable design flaw.
--
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/groups/opt_out.
