Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(389)

Unified Diff: extensions/browser/process_map.h

Issue 2892403002: Introduce lock screen app context to extension features (Closed)
Patch Set: . Created 3 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: extensions/browser/process_map.h
diff --git a/extensions/browser/process_map.h b/extensions/browser/process_map.h
index ed28a5272d3239ac7d78121e2482cdfa707564a2..0ec6227185d5e581a7827ae6de569ec905683b5e 100644
--- a/extensions/browser/process_map.h
+++ b/extensions/browser/process_map.h
@@ -116,6 +116,8 @@ class ProcessMap : public KeyedService {
//
// Anyhow, the expected behaviour is:
// - For hosted app processes, this will be blessed_web_page.
+ // - For processes of platform apps running on lock screen, this will be
+ // lock_screen_extension.
// - For other extension processes, this will be blessed_extension.
// - For WebUI processes, this will be a webui.
// - For any other extension we have the choice of unblessed_extension or
@@ -128,12 +130,20 @@ class ProcessMap : public KeyedService {
Feature::Context GetMostLikelyContextType(const Extension* extension,
int process_id) const;
+ void set_is_lock_screen_context(bool is_lock_screen_context) {
+ is_lock_screen_context_ = is_lock_screen_context;
+ }
+
private:
struct Item;
typedef std::set<Item> ItemSet;
ItemSet items_;
+ // Whether the process map belongs to the browser context used on Chrome OS
+ // lock screen.
+ bool is_lock_screen_context_ = false;
+
DISALLOW_COPY_AND_ASSIGN(ProcessMap);
};

Powered by Google App Engine
This is Rietveld 408576698