Issue metadata
Sign in to add a comment
|
ContentSettingsType is out of sync with histograms.xml |
||||||||||||||||||||||
Issue descriptionFor example, the following two CLs added enum values out of order, and did not update histograms.xml https://codereview.chromium.org/1382783002 https://codereview.chromium.org/1706503002 raymes@: Any chance you could figure exactly what happened (do we need to re-interpret any UMA stats?) and fix histograms.xml today? If not, punt back to me and I'll do it.
,
Apr 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c5e0038e479176c8e130882203ca4567f169b38b commit c5e0038e479176c8e130882203ca4567f169b38b Author: raymes <raymes@chromium.org> Date: Tue Apr 18 00:27:45 2017 Make it harder to get ContentSettingsType histogram values wrong This CL forces the histogram value for a content setting to be explicitly specified to reduce the risk of getting out of sync with histograms.xml. BUG= 697234 Review-Url: https://codereview.chromium.org/2728303002 Cr-Commit-Position: refs/heads/master@{#465076} [modify] https://crrev.com/c5e0038e479176c8e130882203ca4567f169b38b/components/content_settings/core/common/content_settings.cc [modify] https://crrev.com/c5e0038e479176c8e130882203ca4567f169b38b/tools/metrics/histograms/histograms.xml
,
Apr 18 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by raymes@chromium.org
, Feb 28 2017