Public bug reported:
During initialization of Oxide, it creates a couple of GL contexts and
makes them current on the UI thread. However, it doesn't restore the
previous UI thread GL state. This could be surprising for applications
that instantiate the first instance of a WebView (or other class that
triggers Oxide startup) and don't expect the GL state (eg, the current
context) to change.
** Affects: oxide
Importance: Medium
Status: Triaged
** Changed in: oxide
Importance: Undecided => Medium
** Changed in: oxide
Status: New => Triaged
--
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/1430582
Title:
Initializing Oxide should leave the UI thread GL state intact
Status in Oxide Webview:
Triaged
Bug description:
During initialization of Oxide, it creates a couple of GL contexts and
makes them current on the UI thread. However, it doesn't restore the
previous UI thread GL state. This could be surprising for applications
that instantiate the first instance of a WebView (or other class that
triggers Oxide startup) and don't expect the GL state (eg, the current
context) to change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1430582/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
