The current presubmit requirements are [https://cs.chromium.org/chromium/src/media/PRESUBMIT.py?type=cs&sq=package:chromium&l=142]:
'UMA_HISTOGRAM_ENUMERATION reports in src/media/ are expected to adhere\n'
      'to the following guidelines:\n'
      ' - The max value (3rd argument) should be an enum value equal to the\n'
      '   last valid value, e.g. FOO_MAX = LAST_VALID_FOO.\n'
      ' - 1 must be added to that max value.\n'

Wheres UMA documentation recommends using COUNT value as the last value of the enum: "The COUNT value should not include an explicit value--this lets the compiler keep the COUNT up-to-date." [https://chromium.googlesource.com/chromium/src.git/+/HEAD/tools/metrics/histograms/README.md]

This leads to confusing both when submitting the code and during code reviews.
 

The current presubmit requirements are [https://cs.chromium.org/chromium/src/media/PRESUBMIT.py?type=cs&sq=package:chromium&l=142]:
'UMA_HISTOGRAM_ENUMERATION reports in src/media/ are expected to adhere\n'
      'to the following guidelines:\n'
      ' - The max value (3rd argument) should be an enum value equal to the\n'
      '   last valid value, e.g. FOO_MAX = LAST_VALID_FOO.\n'
      ' - 1 must be added to that max value.\n'

Wheres UMA documentation recommends using COUNT value as the last value of the enum: "The COUNT value should not include an explicit value--this lets the compiler keep the COUNT up-to-date." [https://chromium.googlesource.com/chromium/src.git/+/HEAD/tools/metrics/histograms/README.md]

This leads to confusion both when submitting the code and during code reviews.