I was studying why maze solver from Microsoft is so slow with B2G and Gecko, in last few days. If I am right, I found refresh driver always invalidate whole region of display port, if there is, or visual overflow rect of root frame. For the case of maze solver, even it changes style of just small number of elements, refresh driver makes all frames (almost) on frame tree to generate display items since they are falling in the dirty region. It takes a lof of time to build display list, and spend more time to process display items.
I know we have display list based invalidation, but it does not work for refresh driver. My question is why refresh driver works like this. Is it possible to improve it with display list based invalidation or other solution? -- Sinker -- 天教懶漫帶疏狂 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
