tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 53bc750bce3389c911aba2d8bff4423d65bc98dc..baa2cc3effd8ea6d0fbd56c3c2966f4dbf83b18b 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -89505,7 +89505,7 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   <int value="413" label="VTTCueRenderLineNotAuto"/>
   <int value="414" label="VTTCueRenderPositionNot50"/>
   <int value="415" label="VTTCueRenderSizeNot100"/>
-  <int value="416" label="VTTCueRenderAlignNotMiddle"/>
+  <int value="416" label="VTTCueRenderAlignNotCenter"/>

[foolip, 2017/02/08 13:39:41]

Did you rename this manually, or did running
tools/metrics/histograms/update_use_counter_feature_enum.py update it? I had
thought that the script wouldn't change existing entries.

I don't know if changing this file will trickle through to
https://www.chromestatus.com/metrics/feature/timeline/popularity/416

[maksims (do not use this acc), 2017/02/08 14:44:27]

I've changed it using the above mentioned script

[Rick Byers, 2017/02/08 22:00:51]

Renaming enum members is supposed to be OK (IIRC we removed some comments from
UseCounter.h saying not to do this), but chromestatus.com still has an open bug
about handling it properly:
https://github.com/GoogleChrome/chromium-dashboard/issues/266

We decided not to put in the presubmit rule to block renames, so go ahead. 
We'll worry about the chromestatus issue separately.

   <int value="417" label="ElementRequestPointerLock"/>
   <int value="418" label="VTTCueRenderRtl"/>
   <int value="419" label="PostMessageFromSecureToInsecure"/>