Add tests to make sure copy/paste in an about:blank iframe in a hosted app works.

chrome/test/data/extensions/api_test/clipboard/extension/test.js

Index: chrome/test/data/extensions/api_test/clipboard/extension/test.js
diff --git a/chrome/test/data/extensions/api_test/clipboard/extension/test.js b/chrome/test/data/extensions/api_test/clipboard/extension/test.js
index 8432db7e2ab10bcc7c07459a16fd54de9b085463..4206d24e5b79453cdcbee5bb898e4845eb747340 100644
--- a/chrome/test/data/extensions/api_test/clipboard/extension/test.js
+++ b/chrome/test/data/extensions/api_test/clipboard/extension/test.js
@@ -17,6 +17,22 @@ chrome.test.runTests([
       chrome.test.succeed();
     else
       chrome.test.fail('execCommand("paste") failed');
+  },
+  function copyInIframe() {
+    var ifr = document.createElement('iframe');
+    document.body.appendChild(ifr);
+    if (ifr.contentDocument.execCommand('copy'))
+      chrome.test.succeed();
+    else
+      chrome.test.fail('execCommand("copy") failed in iframe');
+  },
+  function pasteInIframe() {
+    var ifr = document.createElement('iframe');
+    document.body.appendChild(ifr);
+    if (ifr.contentDocument.execCommand('paste'))
+      chrome.test.succeed();
+    else
+      chrome.test.fail('execCommand("paste") failed in iframe');

[not at google - send to devlin, 2014/08/21 20:28:11]

Another line-saver: I don't know why we don't do:

chrome.test.assertEq(true, execCommand(..));

for all of these, rather than those 4 lines.

[Marijn Kruisselbrink, 2014/08/21 20:50:20]

You'd still need chrome.test.succeed() or fail() to cause test.runTests() to
actually go on with the next test. Although always calling succeed after an
assert will still have the desired overall effect, but with confusing output if
the test actually fails.

   }
 ]);