Adding MimeHandlerView.

chrome/browser/renderer_host/chrome_render_message_filter.cc

Index: chrome/browser/renderer_host/chrome_render_message_filter.cc
diff --git a/chrome/browser/renderer_host/chrome_render_message_filter.cc b/chrome/browser/renderer_host/chrome_render_message_filter.cc
index c0e66d4c08d9b1465c9a26957c99032fe7dec5ac..04213659e2fe03107d772a6b3d8c4eccb5a7fe30 100644
--- a/chrome/browser/renderer_host/chrome_render_message_filter.cc
+++ b/chrome/browser/renderer_host/chrome_render_message_filter.cc
@@ -184,7 +184,11 @@ void ChromeRenderMessageFilter::OnAllowDOMStorage(int render_frame_id,
                                                   const GURL& top_origin_url,
                                                   bool local,
                                                   bool* allowed) {
-  *allowed =
+  // TODO(zork): Decide if we need this.
+  // We need to put renderer state in IO thread for MimeHandlerViewGuest and
+  // we can retrieve whether we need special cooking settings for this
+  // {|render_process_id_|, |render_frame_id|} pair.
+  *allowed = true;

[Fady Samuel, 2014/08/29 18:52:31]

Implement something equivalent to WebViewRendererState for MIMETypeHandler. Then
always allow DOM Storage there.

[lazyboy, 2014/08/29 22:08:24]

Yes, will do once the TODO is resolved, i.e. make sure we need this.

       cookie_settings_->IsSettingCookieAllowed(origin_url, top_origin_url);
   // Record access to DOM storage for potential display in UI.
   BrowserThread::PostTask(