Why using $parent[0].lastChild

[giulioprovasi]

When trying to use a custom position for the loading bar, I must create two nested div in order for the bar to works (css are for demo only):

<div id="loader" style="position:absolute; background: #FC0; width: 100%; height:50px; top:100px;">
        <div style="background: #c3325f; width: 100%; height:50px; top:100px;"></div>
      </div>

as this won't work:

<div id="loader" style="position:absolute; background: #FC0; width: 100%; height:50px; top:100px;">
      </div>

Isn't it possible to append the bar to the currentSelector instead of parentSelector ?

[chieffancypants]

I'm not following the exact question, but the title of your issue is related to this commit: c21a146. Is this causing a problem?

[omeid]

Yes, I have the same problem. It is now not possible to use an empty element for the parent.

Also, it would be nice if one could use a query selector or an actual dom/jqlite.element object on parentSelector instead of $document.find which is restricted to tag names only.

[chieffancypants]

I dont know -- that commit specifically was taken out of the Angular team's migration guide. Are you using an older version of angular?

[omeid]

No, latest.

Can you maybe post an example where the loading bar is injected into an empty element? It doesn't show up for me at all if there is no element within the cfpLoadingBarProvider.parentSelector element.

[giulioprovasi]

Sorry for late reply, as omeid explained well enough, I'd like to use a generic selector instead of the parentSelector, so that we can inject the loader in any empty container.

[joaovieira]

I've pointed this out before. Just never got the time to write CoffeeScript tests.. #170 (comment)

[joaovieira]

Added the PR: #218

[jklaus]

See pull 272.