{"id":211,"date":"2017-05-17T09:26:45","date_gmt":"2017-05-17T13:26:45","guid":{"rendered":"http:\/\/blogs.igalia.com\/tonikitoo\/?p=211"},"modified":"2017-05-19T15:15:24","modified_gmt":"2017-05-19T19:15:24","slug":"chromium-musozone-update-h12017-wayland-x11","status":"publish","type":"post","link":"https:\/\/blogs.igalia.com\/tonikitoo\/2017\/05\/17\/chromium-musozone-update-h12017-wayland-x11\/","title":{"rendered":"Chromium Mus\/Ozone update (H1\/2017): wayland, x11"},"content":{"rendered":"

Since January, Igalia<\/a> has been working on a project whose goal is to make the latest Chromium Browser<\/a> able to run natively on Wayland-based environments. The project has various phases, requires us to carve out existing implementations and align our work with the direction Chromium’s mainline is taking.<\/p>\n

In this post I will provide an update on the progresses we have made over 2017\/H1, as well as our plans coming next.<\/p>\n

In order to jump straight to the latest results section (including videos) without the details, click here<\/a>.<\/p>\n

Background<\/h4>\n

In 2016\/Q4, my fellow Igalian Fr\u00e9d\u00e9ric Wang<\/a> and I ran a warm-up project to check the status of the existing Wayland support in Chromium’s mainline repository<\/a>, and estimate how much work was needed to get the full (and latest) Chromium browser running on Wayland.<\/p>\n

As part of this warm-up we were<\/a> able<\/a> to build<\/a> and<\/a> launch<\/a> ChromeOS’s Chrome for both desktop and embedded<\/a> Linux distributions, featuring either X11 or Wayland. Automotive Grade Linux<\/a> running on the Renesas’ R-car M3<\/a> board is an example of the embedded environments we tested.<\/p>\n

\"Mus+ash
Mus+ash on LinuxOS (Nov\/2016)<\/figcaption><\/figure>\n

Although this was obviously not our end goal (some undesirable ChromeOS widgets were visible at the bottom), it allowed us to verify the overall performance of the build, and experiment with things a bit. Here is a brief summary of the most relevant findings:<\/p>\n