ozone-wayland

> ChromeOS adding almost zero value here. Functional hardware accelerated video playback is a pretty big value to have (neither firefox nor chrome supports hwa video decoding on linux, see https://wiki.archlinux.org/index.php/Hardware_video_accelera... ). It also has a much better system compositor than X11, actually shaking off the broken legacy cruft that Linux distros seem determined to cling on to. You can get some of this on "regular" linux with projects like https://github.com/intel/ozone-wayland but the state of graphics & video support on Linux continues to be a joke (relevant xkcd from 10 years ago https://xkcd.com/619/ )

Firefox works on Wayland now. So, unless you have redefined Firefox as a non-major browser, "is far from certain whether any of the major browsers will ever run on Wayland" is flatly wrong. Also: https://github.com/01org/ozone-wayland And the obvious point is that turning ChromeOS into a full linux distribution defeats the point of ChromeOS itself: to have very few "moving parts", and only those necessary to launch Chrome. Also, the bulk of the work "for wayland" is not wayland itself: it is KMS/Mesa/glamor/libinput, which are already used by ChromeOS (except for libinput, I think).

Can you point to any commits on the Firefox tree or is your evidence limited to blog posts and mailing-list messages? There are commits [1] on the Chrome tree designed to get Chrome working on Wayland, but for those commits to reach significant numbers of users will require the cooperation or at least the "non-interference" of the employer of most of the Chrome devs -- which is at this time an unknown. [1] https://github.com/01org/ozone-wayland/commits/master