Like #1096, this is an angularjs upgrade issue too, which was already fixed once, so strange.