smaug: > But in principle I think some kind of filtering would be nice. > Implementing it for node removals would be a bit annoying in Gecko > case (since our internal nsIMutationObserver::ContentRemoved happens > after the removal) but it is doable. However it is unclear to me > what kind of performance characteristics we'd get - that is the main > concern I have atm. (I'd like to avoid adding APIs which can be > easily used in such way that it slows down all DOM operations > dramatically.)
We could probably use the same mechanism that we do for restyling, effectively modelling any registered selector observers as an additional style sheet rule (that doesn’t have any properties set in it). All of the data we store in the rule cascade so that we can quickly decide whether a given element needs to have rule matching run again could be re-used. -- Cameron McCormack ≝ http://mcc.id.au/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
