Open Bug 1297597 Opened 8 years ago Updated 2 years ago

Investigate to bypass compositor for WebGL canvas elements in fullscreen mode on android

Categories

(Core :: Graphics: Layers, defect)

Product:
Core
Component:
Graphics: Layers
Version:
49 Branch
Type:
defect

Tracking

()

People

(Reporter: sotaro, Unassigned)

References

Details

Attachments

(1 file)

temporal patch - Render WebGL directly to SurfaceView by very hacky way
(deleted), patch
Details | Diff | Splinter Review
android firefox run without using content process, then it might be simpler to implement it than other platforms.
Assignee: nobody → sotaro.ikeda.g
When WebVR is enabled, SharedSurfaceTextureClient is forwarded to VRDisplayHost and it composite the TextureHost without using gecko Compositor. VRManagerChild is derived from TextureForwarder, then it could allocate TextureClient. Current gecko seems not care about fullscreen in gecko. \ The following is a diagram around VRManager. https://github.com/sotaroikeda/firefox-diagrams/blob/master/gfx/gfx_VRManager_51.pdf
When Element is requested to be fullscreen, Element's primary frame occupy the screen. It does not ensure that fullscreen WebGL always fill screen. Background could be shown and chrome ui could be shown in some cases. The following is a diagram around Element.requestFullscreen(). https://github.com/sotaroikeda/firefox-diagrams/blob/master/dom/dom_Element_requestFullscreen_51.pdf
The patch is just to check performance of WebGL when bypassing Compositor. The patch seems to have a problem to update rendering.
Summary: Bypass compositor for WebGL canvas elements in fullscreen mode on android → Investigate to bypass compositor for WebGL canvas elements in fullscreen mode on android
Assignee: sotaro.ikeda.g → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: