UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce the problem:
1. Build Chromium with Ozone (w/ Wayland backend enabled) 
2a. Start `chromium --ozone-platform=wayland` on a high DPI monitor
--OR-- 
2b. Start `chromium --ozone-platform=wayland --force-device-scale-factor=2`

What is the expected behavior?
The UI is doubled on my high DPI screen, either from auto detection, or from force the scale factor

What went wrong?
The flag seems to be ignored, and auto-detection of the scale factor doesn't work, as it does in non-Ozone builds.

To be clear, non-Ozone builds of Chromium at this version have expected behavior on high DPI screens.

See in the screenshot:
- Sway (Wayland compositor)
- Firefox Nightly (native Wayland client)
- Chromium (this bug report build, Ozone/Wayland)
- termite - with me killing any Xwayland instances to show that these are all native Wayland clients.

Did this work before? No 

Chrome version: 72.0.3608.4 (Developer Build) (64-bit)  Channel: n/a
OS Version: 
Flash Version: (disabled)

I marked it as not a regression since I am assuming that scaling hasn't ever worked or been implemented in the Ozone path.
 

Deleted: lofi-chromium.png 1.7 MB

	lofi-chromium.png 1.7 MB View Download