As for the root cause, @ChristopherSwasey is correct. I asked several other Ember developers about this. There is no solution, but two interesting thoughts that may help:
1) One developer reported that he encountered this problem and circumvented it, making sure that the animated gif started before the javascript took a long time to execute.
2) Another developer suggested that using a virtualized list is the right way, so that only visible nodes are displayed. However, I am afraid that I do not yet know the open source class Ember virtualized list.
Hope this helps.
source share