Okay, I can confirm it’s an issue with the Angular template. It’s reproducible by just running npm test. It looks like the template hasn’t been updated since Angular v1.5.5, so I guess the code is a little out of date. Do you mind creating a ticket for this issue here, and digging around to see what you can find out? It looks like a pretty common issue.