Add way for PermissionContext to be automatically restricted to secure origins.

chrome/browser/content_settings/permission_context_base.h

Index: chrome/browser/content_settings/permission_context_base.h
diff --git a/chrome/browser/content_settings/permission_context_base.h b/chrome/browser/content_settings/permission_context_base.h
index 0f24beedf833c7f999bbd32fd8cf63e6820db64d..61a6937bcdbe1353f080c35aaac45d3f2984f657 100644
--- a/chrome/browser/content_settings/permission_context_base.h
+++ b/chrome/browser/content_settings/permission_context_base.h
@@ -46,6 +46,7 @@ using BrowserPermissionCallback = base::Callback<void(ContentSetting)>;
 // After this you can override several other methods to customize behavior,
 // in particular it is advised to override UpdateTabContext in order to manage
 // the permission from the omnibox.
+// It is mandatory to override IsRestrictedToSecureOrigin.
 // See midi_permission_context.h/cc or push_permission_context.cc/h for some
 // examples.
 
@@ -123,6 +124,9 @@ class PermissionContextBase : public KeyedService {
                                     const GURL& embedding_origin,
                                     ContentSetting content_setting);
 
+  // Whether the permission should be restricted to secure origins.
+  virtual bool IsRestrictedToSecureOrigins() const = 0;
+
  private:
   // Called when a bubble is no longer used so it can be cleaned up.
   void CleanUpBubble(const PermissionRequestID& id);