GitLab

Relying on OzoneDrmMojo feature is not a very good idea, because
it is mostly intended to be used with the Ozone/Drm platform, which can use both
the legacy IPC and mojo for communication. It happened once that the
Ozone/Wayland platform regressed due to misunderstandings why that
feature flag was used with ifdefs.

In Ozone/Wayland, the mojo IPC is a requirement to be able to run
the browser in a multi-process mode(there is a separate GPU process).
Thus, use PlatformProperties to know if the platform requires mojo communication
before the gpu is started. At the moment, only Ozone/Wayland
platform requires mojo communication in addition to the Ozone/Drm
platform, which can use both legacy IPC and mojo and uses OzoneDrmMojo
feature instead.

Bug: 578890
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I1f0fccb19ec2fc69a50320b55014979556739c2c
Reviewed-on: https://chromium-review.googlesource.com/c/1254209
Commit-Queue: Maksim Sisov <msisov@igalia.com>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596174}