Initializing Oxide should leave the UI thread GL state intact

Bug #1430582 reported by Chris Coulson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Triaged
Medium
Unassigned

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.

Changed in oxide:
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.