When running on ozone/drm devices in the mushrome configuration, the mouse cursor bitmap image is not updated as the mouse cursor moves over different areas of the screen. Mustash configuration does not have this issue.
This reproduces on local builds; you don't need a device to be hit by this.
This happens because mushrome mode doesn't have a cursor manager. In classic mode, an AshNativeCursorManager is made which collaborates deeply with the ozone platform object. In mus mode, the views layer installs its own NativeCursorManagerMus which proxies calls to the WindowPortMus (and therefore across the mus boundary).
Comment 1 by e...@chromium.org
, Jun 6 2017