[Webkit-unassigned] [Bug 222607] Implement WebXR Opaque Framebuffer

[bugzilla-daemon at webkit.org]

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

--- Comment #3 from Imanol Fernandez <ifernandez at igalia.com> ---
:dino r? 

Some comments before your review.

For a follow-up it may make sense to abstract out
some of the common code bits between default WebGL framebuffer and XR OpaqueFramebuffer into a base class. For example Gecko has a MozFramebuffer class that's used between both, I believe that chromium also has a similar DrawingBuffer class. That would be a big change that affects all the default FBO context code, and is out of the scope of this patch. Anyway this is a very specific use case of a Framebuffer, and it might not worth it to work on the common class that if we don't have more places in mind where "Default framebuffer" logic will be reused. IMO the future of WebXR will be more based on the WebXR layers to take advantage of multiview, and they use a Opaque Texture or TextureArray instead of a Opaque Framebuffer.

Also it would be nice to implement GL_EXT_multisampled_render_to_texture as a follow-up to support more performant antialias on devices not supporting the similar Imagination extension.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210302/c1de09d1/attachment.htm>