From my preliminary profile, it's spending an abnormal amount of time recalculating the style, which is bizarre as nothing major has changed. Admittedly, my own experiences have been for large data tables where you tend to reuse cell nodes as data gets repurposed, so styles aren't updated as often. I also used scoped styles to ensure that nodes wouldn't search the whole tree to find their styles (something that has since been removed from Chrome). Supposedly this is replaced now by Display Locking [0], but I wasn't able to get it to work for this example in my limited testing. Going back to my old project, it also seems to have regressed in performance. Grr.
I will admit that DOM is some serious black magic, the browser is an unfortunate moving target, and when I say "should be able to update 10k", I am lying as much blame at the feet of the browser developers as I am at the frameworks.
I would go back and edit my old post now, since you're clearly right in this case, but it seems the time limit on it has run out.
I will admit that DOM is some serious black magic, the browser is an unfortunate moving target, and when I say "should be able to update 10k", I am lying as much blame at the feet of the browser developers as I am at the frameworks.
I would go back and edit my old post now, since you're clearly right in this case, but it seems the time limit on it has run out.
[0] https://github.com/WICG/display-locking/blob/master/README.m...