[Extensions UI] Treat dismissal as acknowledgment for the NTP bubble
crbug.com/548269 made extension bubbles only consider themselves
acknowledged once the user interacted with the bubble; i.e., bubble
dismissal by deactivation wouldn't count. This was primarily to combat
the case of something potentially stealing focus, either intentionally
or unintentionally. However, this might have strayed too far into
peskiness.
Let's dial this back for the NTP bubble, where the effect is potentially
less dangerous (e.g., it's consistently obvious, unlike something like
a proxy override), and evaluate.
BUG=672272
Review-Url: https://codereview.chromium.org/2567273002
Cr-Commit-Position: refs/heads/master@{#447535}
diff --git a/chrome/browser/extensions/settings_api_bubble_delegate.h b/chrome/browser/extensions/settings_api_bubble_delegate.h
index 737fa58..9e36bd46 100644
--- a/chrome/browser/extensions/settings_api_bubble_delegate.h
+++ b/chrome/browser/extensions/settings_api_bubble_delegate.h
@@ -36,6 +36,7 @@
base::string16 GetActionButtonLabel() const override;
base::string16 GetDismissButtonLabel() const override;
bool ShouldCloseOnDeactivate() const override;
+ bool ShouldAcknowledgeOnDeactivate() const override;
bool ShouldShowExtensionList() const override;
bool ShouldHighlightExtensions() const override;
bool ShouldLimitToEnabledExtensions() const override;
