ubuntu-webapps-bugs team mailing list archive
-
ubuntu-webapps-bugs team
-
Mailing list archive
-
Message #00956
[Bug 1312082] Re: Stop using deprecated compositing paths
** Changed in: oxide
Status: In Progress => Fix Released
** Changed in: oxide
Milestone: branch-1.2 => branch-1.1
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1312082
Title:
Stop using deprecated compositing paths
Status in Oxide Webview:
Fix Released
Bug description:
The 2 compositing paths we were previously using have been removed
from Chromium. As an interim, we are now using 2 other compositing
paths (software compositing mode or mailbox compositing mode).
However, both of these will eventually be removed in favour of the
delegated renderer.
Longer term, we want to hook the delegated renderer path in to the QML
scenegraph compositor so that we have a single compositor. However, as
an interim solution we could run a single-threaded browser-side
compositor for each webview (IIUC, this is how ContentViewCore and
ContentViewRenderView on Chromium Android work), and composite the
output of this in QML. This depends on fixing bug 1312081 first though
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1312082/+subscriptions
References