Possible problem with @children depending on location of <content>

[csaloio]

Please see this plunker:
http://plnkr.co/edit/0yEcM9eDlyaR5LnsjYZg?p=preview

If <content> is not nested the array created by @children is correct. WHen it is nested the array is always empty.

[EisenbergEffect]

Thanks for reporting this! We need to do some improvements how how @children works internally and those should fix this issue.

[charlespockert]

Was wondering when this would be fixed. Not a massive issue for me but it saves me having to use an extra div every time I want an instance of a certain control
#218

[EisenbergEffect]

I'm hoping to get it in the next iteration. It's been bugging me so I want to get it addressed sooner than later. Maybe next week?

[MikaelPorttila]

Any updates on this issue?

[EisenbergEffect]

Quick update on this. We are working on a solution. However, the fix is probably going to have to wait until we update to Shadow DOM v1 because the implementation details are strongly connected. We'll do a bit more research this week and see if there's a way we can address it before then.

[EisenbergEffect]

This issue is now fixed in our shadow dom v1 branch.