rama wrote: > Visibility details can be obtained from dom tree. Selenium provides > methods to say whether the element is visible or > invisible(display:none).
So is that your definition of "invisible"? Note that there are multiple possible definitions, and which one you care about matters in terms of how much work needs to be done to compute it. > The pages take considerable time > to load on the browser. Hence I wanted to disable layout. In other > words I wanted a browser which does everything except for rendering on > screen. Those two statements contradict each other. Layout involves computing where things should be painted. "Rendering on the screen" usually means painting a precomputed geometry, though a lot of people lump layout under rendering.... So which exact part of the pipeline from "bytes on the HTTP server" to "lit-up pixels on screen" are you trying to bypass, and what functionality do you need to keep working? Note that if you're going to be doing anything that simulates users clicking on the web page, you must have complete geometry information computed and must have full z-ordering information as well. If you need all that, then all you can skip is the part of the pipeline from having a display list built to having lit-up pixels on the screen. That's not going to get you much time savings, most likely, but you might be able to do it by hacking the part of PaintFrame() that actually traverses the built-up display list. -Boris _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
