Description of problem:
This is for chromium-freeworld, version 87.  chromium-browser works fine.  The problem is that it does not work using the new ozone capability for wayland.

Version-Release number of selected component (if applicable): 87


How reproducible: Always


Steps to Reproduce:
1. Try running the command: chromium-freeworld --enable-features=UseOzonePlatform --ozone-platform=wayland
2.
3.

Actual results: Error message: cannot open DISPLAY :0


Expected results: Run the browser as a wayland application.


Additional info: There's a simple workaround.  The problem is that chromium-freeworld is a shell script, and apparently, it tries to force running as an X11 application before doing an exec of /usr/lib64/chromium-freeworld/chromium-freeworld.  The workaround is to run /usr/lib64/chromium-freeworld/chromium-freeworld directly, instead of /usr/bin/chromium-freeworld.  This works perfectly for me, but it would probably be better to modify the shell script.

The wayland capability is important, at least on my machine.  If I run a GNOME wayland session, chromium is extremely slow when run using X11, so much so that it's unusable.  When run as a wayland application, it runs without problem.