Hookup print and save buttons in the out of process PDF plugin

chrome/browser/resources/pdf/background.js

Index: chrome/browser/resources/pdf/background.js
diff --git a/chrome/browser/resources/pdf/background.js b/chrome/browser/resources/pdf/background.js
index 06f5b2e0d768225039bf04a19d041ac281247e11..65a26a349842fde651ab69207c81be675a3aee12 100644
--- a/chrome/browser/resources/pdf/background.js
+++ b/chrome/browser/resources/pdf/background.js
@@ -2,11 +2,30 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
+/**
+ * Keep a stack of stream details for requests. These are pushed onto the stack
+ * as requests come in and popped off the stack as they are handled by a
+ * renderer. Using a stack here simply ensures they are handled in the same
+ * order that the requests come in.

[koz (OOO until 15th September), 2014/02/19 01:52:10]

Won't this mean that the requests get handled in reverse order? Is that what you
intend?

+ */
+var _streamsCache = [];
+
+function popStreamDetails() {
+  if (_streamsCache.length > 0)
+    return _streamsCache.pop();
+}
+
 chrome.streamsPrivate.onExecuteMimeTypeHandler.addListener(
   function(mime_type, original_url, content_url, tab_id) {
     // TODO(raymes): Currently this doesn't work with embedded PDFs (it
     // causes the entire frame to navigate). Also work out how we can
     // mask the URL with the URL of the PDF.
-    chrome.tabs.update(tab_id, { url: 'index.html?' + content_url });
+    var streamDetails = {
+      mimeType: mime_type,
+      originalURL: original_url,
+      streamURL: content_url
+    };
+    _streamsCache.push(streamDetails);
+    chrome.tabs.update(tab_id, { url: 'index.html' });
   }
 );