Le 22/10/2012 12:58, Brendan Eich a écrit : > Boris Zbarsky wrote: >> So we'd only need to worry about places in the Rust code on the DOM >> side that hold references to nodes that are not in the DOM tree. >> There shouldn't be that many (e.g. the -moz-element stuff would have >> that, perhaps, and things like image loads and whatnot), and we'd >> have to teach all of them about adoption. Or do some sort of scan on >> adopt. Or something. Either way, in terms of perf the hit would be >> when adopting only. > > Is adoptNode an important API? It's not a good design in my view, but > I'm in a glass house when it comes to criticizing DOM APIs :-P. > Perhaps it's ok for performance to be in a penalty box for adoptNode. As a web developer, I've never used adoptNode, I don't even recall having seen it in an actual website while view-sourcing. So if there is a trade-off to be made in which the downside is adoptNode being slow, I personnally think it's a worthwhile trade-off.
David _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
