ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chrisccoulson@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: oxide
     Importance: Medium
     Assignee: Chris Coulson (chrisccoulson)
         Status: Fix Committed

** Changed in: oxide
   Importance: Undecided => Medium

-- 
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/1675963

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

Status in Oxide:
  Fix Committed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1675963/+subscriptions