[Webkit-unassigned] [Bug 76720] [chromium] Refactor video drawing to be more data driven

[bugzilla-daemon at webkit.org]

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





--- Comment #8 from Ami Fischman <fischman at chromium.org>  2012-01-24 13:58:58 PST ---
It's potentially interesting that CCVLI::draw() has two, assymetric, codepaths:
1) NativeTexture frames: there is no "upload" needed, since the frame is already on a texture, but the underlying texture is reused as soon as putCurrentFrame() is called, so pCF() *must not* be called until the draw is done.
2) Non-NativeTexture frames: these must be uploaded to textures before pCF() is called, but then pCF() *can* be called *before* the draw is done, b/c CCVLI owns the texture in question, not the frame provider.

Today both paths through CCVLI::draw() have the same serialization look:
getCF() -> upload (no-op for native textures) -> draw -> putCF()

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