[Webkit-unassigned] [Bug 93010] [chromium] Add WebExternalTextureProvider; an alternate means for providing textures to a TextureLayerChromium

[bugzilla-daemon at webkit.org]

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





--- Comment #26 from alexst at chromium.org  2012-11-27 08:54:56 PST ---
(In reply to comment #24)
> Similarly to James, I would favor a version where we don't add a new layer type, but try to merge the use cases to reduce the number of paths. For example, I suspect we can merge the existing 2 paths by fixing the respective users - I think only plugins (and tests) now call setTextureId as opposed to providing a client. That would balance the added complexity of an impl-thread provider.
> At a higher level, it's nice to be able to think about a layer type by what type of content it renders (e.g. a texture, a video frame, painted contents, a scrollbar, a 9-patch, ...), rather than how that content is provided. I'm comfortable with having different ways of providing the content in the same layer.

Thanks for the comments, I removed the new layer with this patch.

I could also put the work of merging the existing two layer types on my todo list if you'd like, but it'll need to be a follow on patch since it requires chromium changes to not break the current path.

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