Removed navigator.pointerEnabled API.

Removed navigator.pointerEnabled API.

The deprecated API was added temporarily only to estimate its usage.

This CL also removes unused counters for Pointer Events.

BUG=631897
Committed: https://crrev.com/dd33bdb2ed843cdf6679dd27a5802136c69de0a4
Cr-Commit-Position: refs/heads/master@{#421526}

[mustaq, 2016-09-27 18:26:09]

The CQ bit was checked by mustaq@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-09-27 18:26:33]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[mustaq, 2016-09-27 18:29:50]

mustaq@chromium.org changed reviewers:
+ dtapuska@chromium.org, rbyers@chromium.org

[mustaq, 2016-09-27 18:29:51]

ptal

[dtapuska, 2016-09-27 18:37:43]

On 2016/09/27 18:29:51, mustaq wrote:
> ptal

lgtm % I presume we got enough data on these fronts?

[mustaq, 2016-09-27 20:07:31]

On 2016/09/27 18:37:43, dtapuska wrote:
> On 2016/09/27 18:29:51, mustaq wrote:
> > ptal
> 
> lgtm % I presume we got enough data on these fronts?

We only wanted to check if navigator.pointerEnabled could be causing the
apparently higher PE usage in Edge than in Chrome. It turned out not to be the
case:
https://docs.google.com/presentation/d/1hLMfplkibrjBGCafXfNvwFA-M5osj3xC-Uq8p...

@rbyers: I don't think we need to wait for data from Beta, right?

[commit-bot: I haz the power, 2016-09-27 20:25:57]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-27 20:25:58]

Dry run: This issue passed the CQ dry run.

[Rick Byers, 2016-09-27 20:38:06]

On 2016/09/27 20:07:31, mustaq wrote:
> On 2016/09/27 18:37:43, dtapuska wrote:
> > On 2016/09/27 18:29:51, mustaq wrote:
> > > ptal
> > 
> > lgtm % I presume we got enough data on these fronts?
> 
> We only wanted to check if navigator.pointerEnabled could be causing the
> apparently higher PE usage in Edge than in Chrome. It turned out not to be the
> case:
>
https://docs.google.com/presentation/d/1hLMfplkibrjBGCafXfNvwFA-M5osj3xC-Uq8p...
> 
> @rbyers: I don't think we need to wait for data from Beta, right?

We definitely don't want to ship this API, so removal LGTM with nit.
But the API did make it into M54, right?  We may still want to double check the
data in beta for users that had the pointer events finch trial enabled - we know
that dev channel usage can be quite biased but beta generally represents real
users a bit better.  Perhaps it's radically different in beta (eg.
mobile-optimized sites on Android)?

https://codereview.chromium.org/2372293002/diff/1/tools/metrics/histograms/hi...
File tools/metrics/histograms/histograms.xml (left):

https://codereview.chromium.org/2372293002/diff/1/tools/metrics/histograms/hi...
tools/metrics/histograms/histograms.xml:81920: -  <int value="1516"
label="NavigatorPointerEnabled"/>
nit: don't remove entries from histograms.xml.  We may still want to use the
dashboard to look at historical data, so generally things are never removed from
the XML file.

[mustaq, 2016-09-27 21:04:09]

On current Chrome-Win-beta (54.0.2840.34), ~0.53% of page visits access
pointerEnabled, which is less than dev channel fractions. The data seems to have
converged already but we can wait a bit more if needed.

https://codereview.chromium.org/2372293002/diff/1/tools/metrics/histograms/hi...
File tools/metrics/histograms/histograms.xml (left):

https://codereview.chromium.org/2372293002/diff/1/tools/metrics/histograms/hi...
tools/metrics/histograms/histograms.xml:81920: -  <int value="1516"
label="NavigatorPointerEnabled"/>
On 2016/09/27 20:38:06, Rick Byers wrote:
> nit: don't remove entries from histograms.xml.  We may still want to use the
> dashboard to look at historical data, so generally things are never removed
from
> the XML file.

Done.

[mustaq, 2016-09-28 13:56:08]

On 2016/09/27 21:04:09, mustaq wrote:
> On current Chrome-Win-beta (54.0.2840.34), ~0.53% of page visits access
> pointerEnabled, which is less than dev channel fractions. The data seems to
have
> converged already but we can wait a bit more if needed.

The page visit count here needs to be corrected, considering the fraction (50%)
of
beta that contributed to the pointerEnabled count. See the bug for correct
numbers.

The conclusion remains the same---the beta data shows a similar level of
pointerEnabled usage. I will commit the CL now.

[mustaq, 2016-09-28 13:57:01]

The CQ bit was checked by mustaq@chromium.org

[mustaq, 2016-09-28 13:57:01]

The patchset sent to the CQ was uploaded after l-g-t-m from
dtapuska@chromium.org, rbyers@chromium.org
Link to the patchset: https://codereview.chromium.org/2372293002/#ps20001
(title: "Reverted the xml changes.")

[commit-bot: I haz the power, 2016-09-28 13:57:13]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-28 15:37:52]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-09-28 15:46:47]

Description was changed from

==========
Removed navigator.pointerEnabled API.

The deprecated API was added temporarily only to estimate its usage.

This CL also removes unused counters for Pointer Events.

BUG=631897
==========

to

==========
Removed navigator.pointerEnabled API.

The deprecated API was added temporarily only to estimate its usage.

This CL also removes unused counters for Pointer Events.

BUG=631897

Committed: https://crrev.com/dd33bdb2ed843cdf6679dd27a5802136c69de0a4
Cr-Commit-Position: refs/heads/master@{#421526}
==========

[commit-bot: I haz the power, 2016-09-28 15:46:49]

Patchset 2 (id:??) landed as
https://crrev.com/dd33bdb2ed843cdf6679dd27a5802136c69de0a4
Cr-Commit-Position: refs/heads/master@{#421526}