" The question is: how is bootstrap not finding the element when it clearly
and definitely exists."
As far as the bootstrapper knows, it doesn't exist. So you have to figure
out why not. There are various reasons (not transpiled because of error,
not in the location the code says it is, development not synced with the
running application)...
"Additionally, document.getElementsByTagName('login') correctly returns the
login element."
Which tells you the <login></login> tags are in the DOM, as you would guess
from the fact that you put them in the index.html file. It does not tell
you anything else. Those tags should trigger a lookup for the component
with the login selector, but it doesn't find one. Which means whatever you
are expecting to be loaded is not being loaded, either because you are
passing in the wrong thing, or the right thing does not exist.
I did a quick check to make sure <login> isn't some special keyword and it
isn't. See this plunker: https://embed.plnkr.co/8cYSrPackDFxPTas951o/.
That shows that there isn't anything special with <login></login> which
means any issues you are seeing are a problem with something you aren't
showing.
I assume when you have template: *template* that you are just shortening
your posted code to remove the actual template code right?
--
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.
