Re:Chrome 53 Beta: Shadow DOM, PaymentRequest, and Android A...
by spankalee on Tuesday August 09, 2016 @08:50PM
(#12258758)
There's the cost of an extra node, since a shadow root is a node. It shouldn't be too much overall though.
Angular doesn't use incremental-dom, but yes, incremental-dom could walk smaller subtrees. incremental-dom could also walk smaller subtrees by calling it on small containers too. That's probably already the common pattern for componentized users of incremental-dom. I'm not sure why the memory usage would be much higher.
Re:Chrome 53 Beta: Shadow DOM, PaymentRequest, and Android A...
by merb on Wednesday August 10, 2016 @08:35AM
(#12261165)
angular2 uses it.
I have an additional node. considering I change a upper shadow-root which has 50+ shadow-roots it's 50 more node's.
We have lists which have a component per cell and per row which is like 100x10 lines. That would mean 1000 x 2 node's more? Changing the whole table would probably be way slower without the inner shadow-root's.
I mean theoretically it will still be faster since incremental-dom now see's less Node's for every root, but I thing the memory usage will probably way higher.