[Webkit-unassigned] [Bug 67341] Scissor rect optimization for chromium compositor

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=67341





--- Comment #8 from Shawn Singh <shawnsingh at chromium.org>  2011-09-01 16:55:30 PST ---
One last thing for now...

catching things at the drawQuad level may allow us to hook into quads associated with individual tiles - that was another good point Nat had.

But the way I see it:

(1) The primary purpose of this patch is to compute the scissor rect, and there is no reason that computing the scissor needs to be tiling-aware.

(2) The logic for deciding whether a layer (or tile) gets drawn, I'm actually not changing that logic.  I might end up re-arranging the code, but not changing the logic.  If tiling has other clever ways to cull tiles from being drawn, I think those are independent of this patch, and those optimizations seem to mostly already exist.

Thoughts?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.