Check policy when checking device access for enumerating devices.

chrome/browser/profiles/profile_io_data.h

Index: chrome/browser/profiles/profile_io_data.h
diff --git a/chrome/browser/profiles/profile_io_data.h b/chrome/browser/profiles/profile_io_data.h
index eed446ea6c26e2d4d35af22c122920602d4e755f..9f1999eb81d0c743902ce656f18a1404803ad070 100644
--- a/chrome/browser/profiles/profile_io_data.h
+++ b/chrome/browser/profiles/profile_io_data.h
@@ -420,6 +420,8 @@ class ProfileIOData {
     explicit ResourceContext(ProfileIOData* io_data);
     virtual ~ResourceContext();
 
+    void set_profile(Profile* profile);

[tommi (sloooow) - chröme, 2014/08/22 19:42:56]

I'm wary of making changes to ResourceContext and this one seems to be
potentially introducing circular references or the possibility of associating a
resource context to a profile that is not related to the io_data_.
If at all possible, I'd like to not make changes to this file.

[Henrik Grunell, 2014/08/25 08:21:46]

Maybe asking for access based on policy via RenderFrameHostDelegate instead, the
same route as RequestMediaAccessPermission currently takes? I'll also need to
add asking for app permission (in case of an extension), which should be done
via RenderFrameHostDelegate. So adding both there might make sense anyway. Wdyt?

+
     // ResourceContext implementation:
     virtual net::HostResolver* GetHostResolver() OVERRIDE;
     virtual net::URLRequestContext* GetRequestContext() OVERRIDE;
@@ -442,6 +444,7 @@ class ProfileIOData {
     bool AllowContentAccess(const GURL& origin, ContentSettingsType type);
 
     ProfileIOData* const io_data_;
+    Profile* profile_;

[tommi (sloooow) - chröme, 2014/08/22 19:42:56]

this would need a lot of documentation I think and tests to go with it

 
     net::HostResolver* host_resolver_;
     net::URLRequestContext* request_context_;