Get rid of oxide bits in //ui/gl/init

Bug #1675963 reported by Chris Coulson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Fix Released
Medium
Chris Coulson

Bug Description

We currently replace the ozone bits in //ui/gl/init with Oxide implementations. This originates from a time when Chromium/Ozone builds didn't support GLX, but that's not the case anymore.

I want to try to get Chromium's content shell working from an Oxide build in order to run the blink layout tests. The content shell will communicate directly with the windowing system rather than using Oxide, and so will require a full featured ozone platform. As part of this, I'm planning to enable the x11 ozone platform for Oxide builds, but in order to make this work, the ozone bits in //ui/gl/init need to be re-enabled.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :
Changed in oxide:
importance: Undecided → Medium
assignee: nobody → Chris Coulson (chrisccoulson)
milestone: none → branch-1.23
status: New → Fix Committed
Changed in oxide:
status: Fix Committed → Fix Released
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.