Cross-process postMessage

content/browser/browser_context.h

Index: content/browser/browser_context.h
diff --git a/content/browser/browser_context.h b/content/browser/browser_context.h
index 2477af5edecf71176dfeb8c6f2d9c1ce0a571328..424844c45e9a50346f0cb31a019dc2e0b7b063c4 100644
--- a/content/browser/browser_context.h
+++ b/content/browser/browser_context.h
@@ -7,6 +7,7 @@
 #pragma once
 
 #include "base/hash_tables.h"
+#include "content/browser/frame_mapper.h"
 
 namespace fileapi {
 class FileSystemContext;
@@ -102,6 +103,10 @@ class BrowserContext {
   virtual ChromeBlobStorageContext* GetBlobStorageContext() = 0;
   virtual ChromeAppCacheService* GetAppCacheService() = 0;
   virtual fileapi::FileSystemContext* GetFileSystemContext() = 0;
+
+  FrameMapper& frame_mapper() { return frame_mapper_; }
+ private:
+  FrameMapper frame_mapper_;

[Charlie Reis, 2011/12/01 23:13:02]

Hmm, you might get pushback on this.  It might need to be created on the various
implementations of BrowserContext (ProfileImpl, OffTheRecordProfile,
ShellBrowserContext, TestBrowserContext).

There's a bigger question here if Albert does make isolated apps use a different
BrowserContext, though.  That's uncertain, but if so, a tab will change its
BrowserContext over time (and may send postMessages to tabs in other
BrowserContexts).

[supersat, 2011/12/09 23:08:20]

Are frames in different browser contexts able to script each other? 

[Charlie Reis, 2011/12/12 22:20:36]

Yes.  Picture an isolated app that opens a window to a different site, then
tries to use postMessage.  The isolated app would be in its own BrowserContext,
but could script windows outside of it.  (This does depart a bit from the idea
of an isolated app as living in a separate web browser, but I argue it makes a
lot of sense to allow postMessages across that boundary.)

Note that it's seeming more likely we're going down that path, so maybe we
should find a different place to store this map...

[supersat, 2011/12/15 19:30:49]

Okay. A BrowsingInstance initially seemed like the best place to put this, but
it seems like a BrowsingInstance can only have one BrowserContext. So, perhaps
we should make this global to the whole browser?

 };
 
 }  // namespace content