Disable pushState and the rest of the history API in packaged apps via runtime-enabled features

chrome/test/data/extensions/platform_apps/restrictions/main.js

Index: chrome/test/data/extensions/platform_apps/restrictions/main.js
diff --git a/chrome/test/data/extensions/platform_apps/restrictions/main.js b/chrome/test/data/extensions/platform_apps/restrictions/main.js
index 566e90fbc45aa4d41cc4508801f58d687c7b6521..17af4b780776173782e78276b07b0262b0c53008 100644
--- a/chrome/test/data/extensions/platform_apps/restrictions/main.js
+++ b/chrome/test/data/extensions/platform_apps/restrictions/main.js
@@ -44,12 +44,17 @@ chrome.test.runTests([
   },
 
   function testHistory() {
+    // These are replaced by wrappers that throws exceptions.
     assertThrowsError(history.back);
     assertThrowsError(history.forward);
-    assertThrowsError(history.pushState);
-    assertThrowsError(history.replaceState);
     assertThrowsError(function() {history.length;});
-    assertThrowsError(function() {history.state;});
+
+    // These are part of the HTML5 History API that is feature detected, so we
+    // remove them altogether, allowing apps to have fallback behavior.
+    chrome.test.assertFalse('pushState' in history);
+    chrome.test.assertFalse('replaceState' in history);
+    chrome.test.assertFalse('state' in history);
+
     succeed();
   },