1,295
edits
Gecko:Frame Painting: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 15: | Line 15: | ||
The frame display list can be built by with code similar to [ http://www.w3.org/TR/CSS21/zindex.html]. We should be able to avoid of the trickery of display list construction in the view system. | The frame display list can be built by with code similar to [ http://www.w3.org/TR/CSS21/zindex.html]. We should be able to avoid of the trickery of display list construction in the view system. | ||
One question is whether we really need a display list. Given that it lets us unify event handling, bitblit analysis, and painting, and also lets us optimize cases where lower frames are covered by opaque higher ones, I think it's worth having. | One question is whether we really need a display list if we could paint everything in one recursive traversal. Given that it lets us unify event handling, bitblit analysis, and painting, and also lets us optimize cases where lower frames are covered by opaque higher ones, and serves the needs of various embedders, I think it's worth having. Also I think that we can construct it in just one traversal of the frame tree, which could be more effecient than doing several passes over the frame tree if we directly followed Hixie's z-order spec. (E.g., doing separate passes over large frame subtrees just to see if there are any 'outline's seems very slow and wasteful). | ||
== More Details == | == More Details == | ||