dom/indexedDB/test/test_webapp_clearBrowserData_inproc_inproc.html

Wed, 31 Dec 2014 06:55:50 +0100

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Wed, 31 Dec 2014 06:55:50 +0100
changeset 2
7e26c7da4463
permissions
-rw-r--r--

Added tag UPSTREAM_283F7C6 for changeset ca08bd8f51b2

michael@0 1 <!--
michael@0 2 Any copyright is dedicated to the Public Domain.
michael@0 3 http://creativecommons.org/publicdomain/zero/1.0/
michael@0 4 -->
michael@0 5
michael@0 6 <!--
michael@0 7 We have three similar tests here which each check that indexedDB data for a
michael@0 8 browser inside an app is cleared upon request:
michael@0 9
michael@0 10 1) test_webapp_clearBrowserData_inproc_oop.html,
michael@0 11 2) test_webapp_clearBrowserData_oop_inproc.html, and
michael@0 12 3) test_webapp_clearBrowserData_inproc_inproc.html.
michael@0 13
michael@0 14 The only difference between these is that the first constructs an in-process
michael@0 15 app frame which contains an out-of-process browser frame, the second
michael@0 16 constructs an out-of-process app frame which contains an in-process browser
michael@0 17 frame, and the third has both frames in process.
michael@0 18
michael@0 19 The tests share all their JS code. webapp_clearBrowserData.js determines
michael@0 20 which frames are in- and out-of-process by looking at the test's filename.
michael@0 21 -->
michael@0 22
michael@0 23 <html>
michael@0 24 <head>
michael@0 25 <title>Indexed Database Clear Browser Data Test inproc/inproc</title>
michael@0 26 <script type="text/javascript" src="/tests/SimpleTest/SimpleTest.js"></script>
michael@0 27 <link rel="stylesheet" type="text/css" href="/tests/SimpleTest/test.css"/>
michael@0 28 <script type="text/javascript;version=1.7" src="webapp_clearBrowserData.js"></script>
michael@0 29 <script type="text/javascript;version=1.7" src="helpers.js"></script>
michael@0 30 </head>
michael@0 31 <body onload="start();">
michael@0 32 </body>
michael@0 33 </html>

mercurial