Stop showing notifications if they're ignored

chrome/browser/ntp_snippets/ntp_snippets_prefs.h

Index: chrome/browser/ntp_snippets/ntp_snippets_prefs.h
diff --git a/chrome/browser/ntp_snippets/ntp_snippets_prefs.h b/chrome/browser/ntp_snippets/ntp_snippets_prefs.h
new file mode 100644
index 0000000000000000000000000000000000000000..fb817aa2a00395eabf901cc3f6405ca8525d8532
--- /dev/null
+++ b/chrome/browser/ntp_snippets/ntp_snippets_prefs.h
@@ -0,0 +1,10 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CHROME_BROWSER_NTP_SNIPPETS_NTP_SNIPPETS_PREFS_H_
+#define CHROME_BROWSER_NTP_SNIPPETS_NTP_SNIPPETS_PREFS_H_
+
+extern const char kContentSuggestionsConsecutiveIgnoredPrefName[];

[Bernhard Bauer, 2017/01/11 15:21:49]

Prefs in chrome/ go in chrome/common/pref_names.{h,cc} (this also goes for
kNotificationIDWithinCategory, which I should have caught previously; sorry).

[sfiera, 2017/01/11 15:41:52]

Should the registration code also move somewhere else?

kNotificationIDWithinCategory is going to go away so that we can track multiple
notifications. Should it still move, if we're just going to get rid of it?

[Bernhard Bauer, 2017/01/11 15:58:24]

No, registration is in the same place where the pref is used, just the names
themselves are declared in a single location.
No, that's fine then.

+
+#endif  // CHROME_BROWSER_NTP_SNIPPETS_NTP_SNIPPETS_PREFS_H_