Ash does not support software compositing for custom cursors [1]. As a result, when using accessibility features that disable hardware cursors (e.g. large cursor, high contrast), the cursor is always the default pointer. Exosphere notably uses custom cursors, so this issue affects ARC windows.
[1] https://chromium.googlesource.com/chromium/src/+/master/ash/wm/ash_native_cursor_manager.cc#103
I've been using https://chromium-review.googlesource.com/#/c/chromium/src/+/858439 for testing. It seems to be working ok on ozone-Drm but I'm not sure if it's exactly what we want. Either way, I don't have cycles to work on this so feel free to use that patch or rewrite it.
Comment 1 by osh...@chromium.org
, Oct 31 2017