GitLab

The touch device manager is currently using the public display::Display
interface to get the id and geometry of the display. This almost works,
except that when we associate touchscreens with displays the display id
is always set to "1" instead of the real native display id.

It's always "1" because the public display interface uses logical ids
that have a different meaning than the internal ids. However, touchscreen
association requires the internal ids to work.

To fix this, do the touchscreen work inside CastDisplayConfigurator where
it has access to native display internals. Because this has to also work
with stub display configuration (null NativeDisplayDelegate), this also
moves the stub display configuration path into CastDisplayConfigurator as
ConfigureDisplayFromCommandLine().

Bug: b/65594145
Test: rbyers.github.io/paint.html

Change-Id: Ic27529ec681e91a22e2395acb9bcf4ac04eab8ff
Reviewed-on: https://chromium-review.googlesource.com/933062
Commit-Queue: Michael Spang <spang@chromium.org>
Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Reviewed-by: Sergey Volk <servolk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538886}