ext Boris Zbarsky wrote:
Antônio Gomes wrote:
I've seen these methods already, and this is exactly the point I want
to get across: I understand the DOM Tree manipulation as the best way
to change the content of any thing in a web page. But sometimes,
accessing (hitting) the DOM Tree many times could make my app slower.
That shouldn't be happening. If it is, please file bugs. CC me on them.
Let me explain better: if I zoom-in (just text and images) a "large" web
page (by large I mean something like gmail showing 100/200 emails per
page) my zooming algorithm is doing the following:
* change some HTMLDOMImageElement attributes (height and width) - as you
pointed out - and setting the text size according to my scale (from the
nsIDOMWindow->SetTextSize).
* After 1#, the content of my page should be "redrawn" (layout layer I
presume) according to the new scale. However, often it does not happen
as it should: bad-formed | partially rendered content.
So as soon as I do something that requires a kind of repaint/rerendering
of showed content (like switching (topping) with another app and back to
the browser, for example), its content got updated (rendered properly -
new zooming scale and so on). The same occurs if I scroll up|down such
web pages. Is there something I can do to improve it ?
Of course, I'm running my application over a MiniMo build in a
linux-based-64M-of-RAM device, but even though it should be happening,
as you said.
--Antonio
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout
