Recent versions of Angular 2 don't support custom self-closing tags anymore, because they are not valid HTML5
On Tuesday, December 29, 2015 at 5:02:26 PM UTC+1, david wendelken wrote: > Woot! That did it. > > If that fixes it then it appears the problem is caused by a flaw in the > templateUrl logic. It's not properly recognizing the end of the tag. > > On Tuesday, December 29, 2015 at 10:46:40 AM UTC-5, Robert Zehnder wrote: > Have you tried <my-directive foo="bar"></my-directive>. I have seen issues > when dealing with self-terminating tags > > > > On Tuesday, December 29, 2015 at 10:17:31 AM UTC-5, david wendelken wrote: > > I'm creating a directive that makes use of the templateUrl capability. > > The directive works as intended except for one "feature". > > Here's a sample of the html markup that invokes my directive: > ================= > > > > <my-directive foo='bar' /><br /> > Some text after my directive > > > When the page is run, this is what I get: > =================== > > > The text my directive produced > > This is what I expected: > ================== > > > The text my directive produced > Some text after my directive > > However, if I wrap my directive in a span or div, like this, I get what I > expected (except, of course, for the unwanted span or div tag in the output): > > > <span> > <my-directive foo='bar' /> > </span><br /> > Some text after my directive > Is there some way I can avoid having to do this? -- 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.
