Include external touchscreen vid/pid in UMA hardware profile
commit86203925b50b728135317868bda6a8337cdd347a
authortdresser@chromium.org <tdresser@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Fri, 7 Feb 2014 08:10:10 +0000 (7 08:10 +0000)
committertdresser@chromium.org <tdresser@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Fri, 7 Feb 2014 08:10:10 +0000 (7 08:10 +0000)
tree6064a83b2dca0f067c1bfcc0707c82db62c31294
parentbd04a20e258098070c6671b04d9a03a7dfa56441
Include external touchscreen vid/pid in UMA hardware profile

Relanding https://codereview.chromium.org/103893005 after it was
reverted in https://codereview.chromium.org/135763002. When this
was first landed, it would try to read information on the
displays after ash::Shell had been destroyed, which caused
issues. This patch checks if the ash::Shell exists before
reading information on the displays.

This patch also fixes a bug in the previous patch in which we'd
log that the primary display was not a touch screen if we failed
to find the native screen.

Previously we looked at including the touchscreen name in the UMA
hardware profile: https://codereview.chromium.org/23619085/.

As that posed a privacy concern, this patch includes the vid/pid
instead.

BUG=248910

Review URL: https://codereview.chromium.org/134773004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@249617 0039d316-1c4b-4281-b951-d872f2087c98
chrome/browser/metrics/metrics_log_chromeos.cc
chrome/common/metrics/proto/system_profile.proto
ui/events/event_utils.cc
ui/events/event_utils.h
ui/events/x/touch_factory_x11.cc
ui/events/x/touch_factory_x11.h