[EMAIL PROTECTED] wrote:
My question is how to fix this. My guess is that I might be able to tell gecko/gtkmozembed that I'm going to be doing a whole bunch of updates, do the updates, and then tell gecko that I'm done.
nsIDocument has an API for this (BeginUpdate/EndUpdate).... It's not frozen or anything, but maybe it'll help a little bit in your case.
Do you think this is what's causing the slow downs we're seeing?
Not very likely. A lot of the things that BeginUpdate/EndUpdate actually coalesce are coalesced even without them (e.g. layout, style changes, etc). As long as your application is not using CSS quotes or counters, BeginUpdate/EndUpdate won't help you that much.
Is there a consistent piece of code that's being slow? If so, I'd be interested in seeing it (and how it differs from the non-slow code).
-Boris _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
