[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 #17 from James Robinson <jamesr at chromium.org>  2012-01-26 14:02:46 PST ---
(In reply to comment #16)
> (In reply to comment #15)
> > what about having this function just call getCurrentFrame() and give a pointer to the frame object to the quad. then, if we do draw the quad, we can copyFrameToTexture() at draw time where we already have access to the LRC.
> 
> copyFrameToTexture() requires mutating the layer. The layer's list of textures, nativeTextureId, m_nativeTextureSize, etc. have to be modified, and the results need to be shared among the quads.

No, these are all draw-only state and they should live on the one quad that the video layer produces.

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