- From: <bugzilla@jessica.w3.org>
- Date: Thu, 13 Mar 2014 15:59:32 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24872 --- Comment #10 from Jonas Sicking <jonas@sicking.cc> --- I agree. I'd prefer to see these usecases solved through an imperative API. I don't understand how you're planning on solving the performance issues involved here? Without the change here, it appears that whenever a node is changed, we only need to check if that affect where that node itself is inserted. With this change we now have to recheck where are all its siblings are inserted too. Either way, adding more complex selectors will only get you so far. An imperative API will always be needed so I think we should start there. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 13 March 2014 15:59:33 UTC