Directive template: "[ng-show] > [ng-if] > [ng-transclude]" throws exception. Bug?

[Wizek]

http://jsbin.com/pemadama/1

This should work without throwing the exception, right?

[rodyhaddad]

Check this comment for a workaround.

Here's your jsbin with the workaround: http://jsbin.com/pemadama/2/edit

hmm, I find it odd that ng-show plays a role in this

[Wizek]

Thanks @rodyhaddad, that was helpful.

I too have no idea why ng-show makes any difference.

Do you think it makes sense to attach a failing unit-test-case to this issue as a pull request?

[petebacondarwin]

So the reason that ng-show makes a difference is that it adds a directive between the top level "compile" node and the ng-if. You can see that any directive that gets in the way will cause this problem...

See http://jsbin.com/pemadama/6/edit

I think this is actually some kind of bug, since clearly the outer transclude is sort of available it is just not passed through when the compiler hits a directive that also creates a transclude. I feel that somehow we ought to have a stack of transclusion functions that directives can un-peel as we go down through the compilation....