[Extensions] Add renderer-side logic to short circuit activity logging

chrome/browser/extensions/activity_log/activity_log.h

Index: chrome/browser/extensions/activity_log/activity_log.h
diff --git a/chrome/browser/extensions/activity_log/activity_log.h b/chrome/browser/extensions/activity_log/activity_log.h
index 76e927658d1764dbd66f62d9ba191f98789bd26c..f01b99bb093e465d14da46c698b6926869dcfff3 100644
--- a/chrome/browser/extensions/activity_log/activity_log.h
+++ b/chrome/browser/extensions/activity_log/activity_log.h
@@ -118,6 +118,8 @@ class ActivityLog : public BrowserContextKeyedAPI,
   // Deletes the database associated with the policy that's currently in use.
   void DeleteDatabase();
 
+  bool is_active() const { return is_active_; }

[asargent_no_longer_on_chrome, 2016/06/23 13:35:56]

nit: this could use a comment with an explanation of what "active" means

[Devlin, 2016/06/23 16:59:02]

There is a comment on the |is_active_|, and I think for accessors we don't add
additional documentation (because one or the other will likely forget to be
updated).  But I added some more detail to the |is_active_| description, since
it was rather sparse.

+
   // If we're in a browser test, we need to pretend that the watchdog app is
   // active.
   void SetWatchdogAppActiveForTesting(bool active);