dom/indexedDB/test/test_webapp_clearBrowserData_inproc_inproc.html

changeset 0
6474c204b198
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/dom/indexedDB/test/test_webapp_clearBrowserData_inproc_inproc.html	Wed Dec 31 06:09:35 2014 +0100
     1.3 @@ -0,0 +1,33 @@
     1.4 +<!--
     1.5 +  Any copyright is dedicated to the Public Domain.
     1.6 +  http://creativecommons.org/publicdomain/zero/1.0/
     1.7 +-->
     1.8 +
     1.9 +<!--
    1.10 +  We have three similar tests here which each check that indexedDB data for a
    1.11 +  browser inside an app is cleared upon request:
    1.12 +
    1.13 +    1) test_webapp_clearBrowserData_inproc_oop.html,
    1.14 +    2) test_webapp_clearBrowserData_oop_inproc.html, and
    1.15 +    3) test_webapp_clearBrowserData_inproc_inproc.html.
    1.16 +
    1.17 +  The only difference between these is that the first constructs an in-process
    1.18 +  app frame which contains an out-of-process browser frame, the second
    1.19 +  constructs an out-of-process app frame which contains an in-process browser
    1.20 +  frame, and the third has both frames in process.
    1.21 +
    1.22 +  The tests share all their JS code.  webapp_clearBrowserData.js determines
    1.23 +  which frames are in- and out-of-process by looking at the test's filename.
    1.24 +-->
    1.25 +
    1.26 +<html>
    1.27 +<head>
    1.28 +  <title>Indexed Database Clear Browser Data Test inproc/inproc</title>
    1.29 +  <script type="text/javascript" src="/tests/SimpleTest/SimpleTest.js"></script>
    1.30 +  <link rel="stylesheet" type="text/css" href="/tests/SimpleTest/test.css"/>
    1.31 +  <script type="text/javascript;version=1.7" src="webapp_clearBrowserData.js"></script>
    1.32 +  <script type="text/javascript;version=1.7" src="helpers.js"></script>
    1.33 +</head>
    1.34 +<body onload="start();">
    1.35 +</body>
    1.36 +</html>

mercurial