Hi Botond thanks for replying, I just checked and calling drawWindow() doesn't output the entire page in the display-list dumps. It's as if this operation doesn't trigger the same things a regular render operation does.
But your reply got me thinking. If I can force Firefox to always render the entire page (instead of the optimized elements currently within the viewport), then I have all the information I need in the display-list dumps. I haven't found a way to do this yet. Can anyone point me to the part of source code that chooses which elements to include in the display-list? I'd like to override this optimization and include all elements within the document instead. > Op 16 apr. 2016 om 01:45 heeft Botond Ballo <bba...@mozilla.com> het volgende > geschreven: > >> On Fri, Apr 15, 2016 at 4:32 AM, Jip de Beer <jip.de.b...@gmail.com> wrote: >> Thanks for the reply. My problem with display lists is that they only >> contain this information about nodes within the viewport. I'm interested in >> all nodes that take up space within the document. >> >> I know Firefox can calculate the necessary information for nodes outside of >> the viewport because I can take a screenshot of the entire page with >> CanvasRenderingContext2D.drawWindow() and it correctly renders the entire >> page (also outside of the viewport). > > If it renders the entire page, it must build a display list for the > entire page. Can you get a display list dump from that operation? > > Cheers, > Botond _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
