summaryrefslogtreecommitdiffstats
path: root/WebCore/manual-tests/inspector
diff options
context:
space:
mode:
authorSteve Block <steveblock@google.com>2011-05-06 11:45:16 +0100
committerSteve Block <steveblock@google.com>2011-05-12 13:44:10 +0100
commitcad810f21b803229eb11403f9209855525a25d57 (patch)
tree29a6fd0279be608e0fe9ffe9841f722f0f4e4269 /WebCore/manual-tests/inspector
parent121b0cf4517156d0ac5111caf9830c51b69bae8f (diff)
downloadexternal_webkit-cad810f21b803229eb11403f9209855525a25d57.zip
external_webkit-cad810f21b803229eb11403f9209855525a25d57.tar.gz
external_webkit-cad810f21b803229eb11403f9209855525a25d57.tar.bz2
Merge WebKit at r75315: Initial merge by git.
Change-Id: I570314b346ce101c935ed22a626b48c2af266b84
Diffstat (limited to 'WebCore/manual-tests/inspector')
-rw-r--r--WebCore/manual-tests/inspector/bp-in-named-eval-after-reload.html65
-rw-r--r--WebCore/manual-tests/inspector/command-line-api.html6
-rw-r--r--WebCore/manual-tests/inspector/console-assert.html37
-rw-r--r--WebCore/manual-tests/inspector/console-call-line-numbers.html14
-rw-r--r--WebCore/manual-tests/inspector/console-dir.html31
-rw-r--r--WebCore/manual-tests/inspector/console-log-formatting.html68
-rw-r--r--WebCore/manual-tests/inspector/console-time.html33
-rw-r--r--WebCore/manual-tests/inspector/debugger-execution-while-paused.html15
-rw-r--r--WebCore/manual-tests/inspector/debugger-pause-during-load.html5
-rw-r--r--WebCore/manual-tests/inspector/debugger-pause-on-else-statements.html18
-rw-r--r--WebCore/manual-tests/inspector/debugger-pause-on-for-in-statements.html18
-rw-r--r--WebCore/manual-tests/inspector/debugger-pause-on-for-statements.html16
-rw-r--r--WebCore/manual-tests/inspector/debugger-scopes-inspection.html35
-rw-r--r--WebCore/manual-tests/inspector/debugger-shortcuts-with-console-opened.html16
-rw-r--r--WebCore/manual-tests/inspector/debugger-status-bar-buttons-state.html2
-rw-r--r--WebCore/manual-tests/inspector/debugger-step-on-do-while-statements.html29
-rw-r--r--WebCore/manual-tests/inspector/debugger-step-on-for-in-statements.html35
-rw-r--r--WebCore/manual-tests/inspector/debugger-step-on-for-statements.html28
-rw-r--r--WebCore/manual-tests/inspector/debugger-step-on-while-statements.html29
-rw-r--r--WebCore/manual-tests/inspector/debugger-watch-expressions.html115
-rw-r--r--WebCore/manual-tests/inspector/display-form-data.html249
-rw-r--r--WebCore/manual-tests/inspector/display-sql-null.html21
-rw-r--r--WebCore/manual-tests/inspector/display-sql-transaction-error.html24
-rw-r--r--WebCore/manual-tests/inspector/dom-mutation.html31
-rw-r--r--WebCore/manual-tests/inspector/duplicate-resource-urls.html61
-rw-r--r--WebCore/manual-tests/inspector/error-warning-count.html60
-rw-r--r--WebCore/manual-tests/inspector/errors-with-space in-url.html7
-rw-r--r--WebCore/manual-tests/inspector/escape-links.html1
-rw-r--r--WebCore/manual-tests/inspector/forzen-ui-while-paused.html11
-rw-r--r--WebCore/manual-tests/inspector/hidden-evals.html118
-rw-r--r--WebCore/manual-tests/inspector/highlight-nodes.html23
-rw-r--r--WebCore/manual-tests/inspector/highlight-source-line.html4
-rw-r--r--WebCore/manual-tests/inspector/multiple-console-messages.html86
-rw-r--r--WebCore/manual-tests/inspector/named-evals.html72
-rw-r--r--WebCore/manual-tests/inspector/profiler-test-call.html35
-rw-r--r--WebCore/manual-tests/inspector/profiler-test-many-calls-in-the-same-scope.html42
-rw-r--r--WebCore/manual-tests/inspector/remember-last-script.html42
-rw-r--r--WebCore/manual-tests/inspector/resources/loop-statements.js22
-rw-r--r--WebCore/manual-tests/inspector/resources/mutate-frame-2.html12
-rw-r--r--WebCore/manual-tests/inspector/resources/mutate-frame.html10
-rw-r--r--WebCore/manual-tests/inspector/resources/script-console-calls.js8
-rw-r--r--WebCore/manual-tests/inspector/resources/script-error.js6
-rw-r--r--WebCore/manual-tests/inspector/returnEvent-crash.html17
-rw-r--r--WebCore/manual-tests/inspector/styled-error-bubbles-in-scripts.html6
-rw-r--r--WebCore/manual-tests/inspector/webinspector-log.html22
45 files changed, 0 insertions, 1605 deletions
diff --git a/WebCore/manual-tests/inspector/bp-in-named-eval-after-reload.html b/WebCore/manual-tests/inspector/bp-in-named-eval-after-reload.html
deleted file mode 100644
index 4612cd6..0000000
--- a/WebCore/manual-tests/inspector/bp-in-named-eval-after-reload.html
+++ /dev/null
@@ -1,65 +0,0 @@
-<style>code{background-color: #ffc;}</style>
-<p><b>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=31375">Bug 31375</a> - Web Inspector: breakpoints in named evals are not restored after a reload</b>
-
-<ul>
-<li><p>open this page with Web Inspector
-<li><p>switch to the Scripts panel, enabling debug if required
-<li><p>the available scripts in the select element should be:
-<ul>
-<li>(program): f1.js
-<li>(program): f2.js
-<li>bp-in-named-eval-after-reload.html
-</ul>
-<li><p>In <code>(program) f1.js</code>, set a breakpoint on the first
-executable line of the function <code>f1()</code>, the invocation of <code>doNothing()</code>.
-<li><p>In <code>(program) f2.js</code>, set a breakpoint on the first
-executable line of the function <code>f2()</code>, the invocation of <code>doNothing()</code>.
-<li><p>click this button: <input id=button type=button value="click me">
-<li><p>debugger should stop in the <code>f1()</code> function.
-<li><p>resume the debugger
-<li><p>debugger should stop in the <code>f2()</code> function (the function in <code>(program) f2.js</code>)
-<li><p>resume the debugger
-<li><p>switch to the web page, reload the web page, switch back to web inspector
-<li><p>in the breakpoints sidebar panel, click on the two breakpoints listed
-and the source for those functions should be shown in the source panel, and
-the previous breakpoint markers should be visible
-<li><p>click the "click me" button above, again
-<li><p>debugger should stop in the <code>f1()</code> function.
-<li><p>resume the debugger
-<li><p>debugger should stop in the <code>f2()</code> function.
-<li><p>resume the debugger
-</ul>
-
-<p>Note that without the fix in <a href="https://bugs.webkit.org/show_bug.cgi?id=31375">Bug 31375</a>,
-the breakpoints won't work after reloading the page.
-
-<script>
-
-function doNothing() { /* allows multi-line functions, easier to debug */ };
-
-eval([
- "function f1() {",
- " doNothing();",
- " console.log(new Date() + ': f1() called');",
- "}",
- "//@sourceURL=f1.js"
-].join("\n"));
-
-f2 = Function([
- "",
- " doNothing();",
- " console.log(new Date() + ': f2() called');",
- "//@sourceURL=f2.js"
-].join("\n"));
-
-var button = document.getElementById("button");
-
-button.addEventListener("click", clickHandler, false);
-
-function clickHandler() {
- f1();
- f2();
-}
-
-</script>
-<!-- End -->
diff --git a/WebCore/manual-tests/inspector/command-line-api.html b/WebCore/manual-tests/inspector/command-line-api.html
deleted file mode 100644
index 8b9a153..0000000
--- a/WebCore/manual-tests/inspector/command-line-api.html
+++ /dev/null
@@ -1,6 +0,0 @@
-<script type="text/javascript" charset="utf-8">
- var $ = function() { console.log("OK") };
-</script>
-
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=20385">Bug 20385: Firebug command line extensions interfere with existing objects</a>.</p>
-<p>To test, execute "$()" in the Inspector's Console. Also trying setting $.</p>
diff --git a/WebCore/manual-tests/inspector/console-assert.html b/WebCore/manual-tests/inspector/console-assert.html
deleted file mode 100644
index df2c4cc..0000000
--- a/WebCore/manual-tests/inspector/console-assert.html
+++ /dev/null
@@ -1,37 +0,0 @@
-<script>
- function createClickHandler(result, str) {
- return function() {
- console.assert(result, "%s", str);
- }
- }
-
- function load() {
- var tests = [
- "",
- "false",
- "null",
- "document.body",
- "!document.body",
- "true"
- ];
-
- for (var i = 0; i < tests.length; ++i) {
- var test = tests[i];
- var result;
- try {
- result = eval(test);
- } catch(e) {
- result = false;
- }
- var button = document.createElement("button");
- button.innerText = "console.assert(" + test + "): should" + (result ? " not" : "") + " assert";
- button.onclick = createClickHandler(result, test);
- var p = document.createElement("p");
- p.appendChild(button);
- document.body.appendChild(p);
- }
- }
-</script>
-<body onload="load()">
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=19134">Bug 19134: Inspector should support console.assert</a>.</p>
-<p>To test, click the buttons below and look at the Inspector's Console.</p>
diff --git a/WebCore/manual-tests/inspector/console-call-line-numbers.html b/WebCore/manual-tests/inspector/console-call-line-numbers.html
deleted file mode 100644
index ae831c5..0000000
--- a/WebCore/manual-tests/inspector/console-call-line-numbers.html
+++ /dev/null
@@ -1,14 +0,0 @@
-<script>
- console.info("Test console.info");
- console.log("Test console.log");
- console.warn("Test console.warn");
- console.error("Test console.error");
- console.time("Test console.time");
- console.timeEnd("Test console.time");
- console.count("Test console.count");
- console.assert(false, "Test console.assert");
-</script>
-<script src="resources/script-console-calls.js"></script>
-<body>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=17234">Bug 17234: Inspector should link console.{log,warn,info,error} back to call site</a>.</p>
-<p>To test, open the Inspector's Console and verify that all console messages have correct resource URLs and line numbers. Also verify that errors and warnings show up inline as bubbles in the resource source view.</p>
diff --git a/WebCore/manual-tests/inspector/console-dir.html b/WebCore/manual-tests/inspector/console-dir.html
deleted file mode 100644
index 90f389d..0000000
--- a/WebCore/manual-tests/inspector/console-dir.html
+++ /dev/null
@@ -1,31 +0,0 @@
-<body>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=24329">Bug 24329: REGRESSION: console.dirxml() Console API broken</a>.</p>
-<p>To test, open the Inspector's Console and verify that all console messages have the correct output.</p>
-</body>
-<script>
- console.log("Testing console.dir:");
- console.dir(undefined);
- console.dir(123);
- console.dir(null);
- console.dir({});
- console.dir({test: 1, test1:{apple: "orange"}});
- console.dir("Test");
- console.dir(document);
- console.dir(document.body);
-
- console.log("\nTesting console.dirxml:");
- console.dirxml(undefined);
- console.dirxml(123);
- console.dirxml(null);
- console.dirxml({});
- console.dirxml({test: 1, test1:{apple: "orange"}});
- console.dirxml("Test");
- console.dirxml(document);
- console.dirxml(document.body);
-
- console.log("\nTesting console.log's %o and %O formatters:");
- console.log("%o %O", document.body, document.body);
- console.log("%o %O", undefined, undefined);
- console.log("%o %O", 123, 123);
- console.log("%o %O", null, null);
-</script>
diff --git a/WebCore/manual-tests/inspector/console-log-formatting.html b/WebCore/manual-tests/inspector/console-log-formatting.html
deleted file mode 100644
index d59ebc9..0000000
--- a/WebCore/manual-tests/inspector/console-log-formatting.html
+++ /dev/null
@@ -1,68 +0,0 @@
-<script>
- var s = "this is a string";
- var i = 5;
- var ni = -5;
- var f = 3.14159;
- var o = { prop1: 1, prop2: 2 };
- var specifiers = {
- s: "string",
- i: "integer",
- d: "integer",
- f: "float",
- "0.3f": "float with precision",
- o: "object",
- z: "unsupported",
- };
-
- function test(args) {
- var functions = ["log", "debug"];
- for (var i = 0; i < functions.length; ++i) {
- console.info("console." + functions[i] + "(%s)", args);
- try {
- eval("console." + functions[i] + "(" + args + ")");
- } catch (e) {
- console.error(e);
- }
- }
- }
-
- function testAllSpecifiers(value, description) {
- for (var specifier in specifiers)
- test("'Format " + description + " as " + specifiers[specifier] + ": %" + specifier + "', " + value + "");
- }
-
- function runTests() {
- var values = [
- { value: "window.noSuchVariable", description: "undefined" },
- { value: "s", description: "string" },
- { value: "i", description: "positive integer" },
- { value: "ni", description: "negative integer" },
- { value: "f", description: "float" },
- { value: "o", description: "object" },
- { value: "document.body", description: "body" },
- { value: "/test/", description: "RegExp" },
- { value: "true", description: "boolean" },
- { value: "null", description: "null" },
- ];
-
- for (var i = 0; i < values.length; ++i)
- testAllSpecifiers(values[i].value, values[i].description);
-
- var tests = [
- "'simple test'",
- "'multiple', 'parameters', 'should', 'be', 'concatenated'",
- "document",
- "document, document.body, window, window.location",
- "document, document.body, 'hello', 'goodbye', window.location",
- "'Format string with fewer specifiers than parameters: %o %i %f', document.body, i, f, ni, o",
- "'Format string with more specifiers than parameters: %o %i %f %i %o', document.body, i, f",
- ];
-
- for (var i = 0; i < tests.length; ++i)
- test(tests[i]);
-
- }
-</script>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=17228">Bug 17228: console.{log,warn,info,error} should support format strings, variable arguments</a>.</p>
-<p>Open the Inspector (right-click and choose "Inspect Element"), then click the "Run Tests" button.</p>
-<button onclick="runTests()">Run Tests</button>
diff --git a/WebCore/manual-tests/inspector/console-time.html b/WebCore/manual-tests/inspector/console-time.html
deleted file mode 100644
index 6c24373..0000000
--- a/WebCore/manual-tests/inspector/console-time.html
+++ /dev/null
@@ -1,33 +0,0 @@
-<script>
-function test() {
- // Test 1: call timeEnd before time
- console.log(">>>console.timeEnd(\"1\")");
- console.timeEnd("1");
- // Test 2: call time two times before timeEnd
- console.log(">>>console.time(\"2\")");
- console.time("2");
- setTimeout(function() {
- console.log(">>>console.time(\"2\")");
- console.time("2");
- console.log(">>>console.timeEnd(\"2\")");
- console.timeEnd("2");
- console.log("2: If it says ~1000ms the first time is not overwritten.");
- }, 1000);
- // Test 3: call timeEnd two times
- console.log(">>>console.time(\"3\")");
- console.time("3");
- console.log(">>>console.timeEnd(\"3\")");
- console.timeEnd("3");
- console.log(">>>console.timeEnd(\"3\")");
- console.timeEnd("3");
- // Test 4: call time/timeEnd without title parameter
- console.log(">>>console.time()");
- console.time();
- console.log(">>>console.timeEnd()");
- console.timeEnd();
-};
-
-</script>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=19159">Bug 19159: Inspector should support console.time/console.timeEnd</a>.</p>
-<p>Open the Inspector (right-click and choose "Inspect Element"), then click the "Run Tests" button.</p>
-<button onclick="test()">Run Tests</button> \ No newline at end of file
diff --git a/WebCore/manual-tests/inspector/debugger-execution-while-paused.html b/WebCore/manual-tests/inspector/debugger-execution-while-paused.html
deleted file mode 100644
index 67446d4..0000000
--- a/WebCore/manual-tests/inspector/debugger-execution-while-paused.html
+++ /dev/null
@@ -1,15 +0,0 @@
-<script>
-function stepOne()
-{
- var x = 1;
-}
-
-function stepTwo()
-{
- alert("Test failed. The second button event still fired.");
-}
-</script>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=20284">Bug 20284: JavaScript can be executed even though debugger is running and at a break point</a>.</p>
-<p>To test, open the Inspector and start a debugging session. Set a break point inside the stepOne() function. Now click the Step One button in the page. The breakpoint should be hit. While paused at the breakpoint click on the Step Two button. You should not see an alert dialog.</p>
-<button onclick="stepOne()">Step One</button><br><br>
-<button onclick="stepTwo()">Step Two</button><br><br>
diff --git a/WebCore/manual-tests/inspector/debugger-pause-during-load.html b/WebCore/manual-tests/inspector/debugger-pause-during-load.html
deleted file mode 100644
index 631cafc..0000000
--- a/WebCore/manual-tests/inspector/debugger-pause-during-load.html
+++ /dev/null
@@ -1,5 +0,0 @@
-<script>
-debugger; // You should see this code and execution line in the Scripts panel.
-</script>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=19053">Bug 19053: Source code not visible when script is paused before onload fires</a>.</p>
-<p>To test, open the Inspector and start a debugging session. You should see this file and execution line in the Scripts panel.</p>
diff --git a/WebCore/manual-tests/inspector/debugger-pause-on-else-statements.html b/WebCore/manual-tests/inspector/debugger-pause-on-else-statements.html
deleted file mode 100644
index 424fb7e..0000000
--- a/WebCore/manual-tests/inspector/debugger-pause-on-else-statements.html
+++ /dev/null
@@ -1,18 +0,0 @@
-<script>
-function test()
-{
- debugger;
-}
-
-if (false)
- debugger; // This should not be hit.
-else
- test();
-</script>
-
-Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=21944">Bug 21944: Can't set a breakpoint on the statement after a single line "else"</a>.
-<br><br>
-Start a debugging session in the Web Inspector and open this file. When the debugger breaks, select the (program) node
-in the call stack, you should see the execution line on the call to test().
-<br><br>
-Also set a breakpoint on the call to test(), and reload. It should break before the test() function is called.
diff --git a/WebCore/manual-tests/inspector/debugger-pause-on-for-in-statements.html b/WebCore/manual-tests/inspector/debugger-pause-on-for-in-statements.html
deleted file mode 100644
index c0c24e0..0000000
--- a/WebCore/manual-tests/inspector/debugger-pause-on-for-in-statements.html
+++ /dev/null
@@ -1,18 +0,0 @@
-<script>
-function test()
-{
- debugger;
-}
-
-var object = { test: 1 };
-
-for (var property in object)
- test();
-</script>
-
-Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=22004">Bug 22004: Can't set a breakpoint on the statement after a single line "for"</a>.
-<br><br>
-Start a debugging session in the Web Inspector and open this file. When the debugger breaks, select the (program) node
-in the call stack, you should see the execution line on the call to test().
-<br><br>
-Also set a breakpoint on the call to test(), and reload. It should break before the test() function is called.
diff --git a/WebCore/manual-tests/inspector/debugger-pause-on-for-statements.html b/WebCore/manual-tests/inspector/debugger-pause-on-for-statements.html
deleted file mode 100644
index 43a63e2..0000000
--- a/WebCore/manual-tests/inspector/debugger-pause-on-for-statements.html
+++ /dev/null
@@ -1,16 +0,0 @@
-<script>
-function test()
-{
- debugger;
-}
-
-for (var i = 0; i < 1; ++i)
- test();
-</script>
-
-Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=22004">Bug 22004: Can't set a breakpoint on the statement after a single line "for"</a>.
-<br><br>
-Start a debugging session in the Web Inspector and open this file. When the debugger breaks, select the (program) node
-in the call stack, you should see the execution line on the call to test().
-<br><br>
-Also set a breakpoint on the call to test(), and reload. It should break before the test() function is called.
diff --git a/WebCore/manual-tests/inspector/debugger-scopes-inspection.html b/WebCore/manual-tests/inspector/debugger-scopes-inspection.html
deleted file mode 100644
index f06b3e7..0000000
--- a/WebCore/manual-tests/inspector/debugger-scopes-inspection.html
+++ /dev/null
@@ -1,35 +0,0 @@
-<script>
-
-var obj = {
- objField: 30
-};
-
-function handleLoad(e) {
- new C().m();
-}
-
-function C() {
- this.a = 10;
- this.timestamp = Date.now();
-}
-
-C.prototype.m = function() {
- this.timestamp = Date.now();
- with (obj) {
- debugger;
- objField++;
- }
- var self = this;
- setTimeout(function() {
- self.m();
- }, 1000);
-};
-
-
-</script>
-<body onload="handleLoad(event)">
-
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=34161"> Bug 34161 - Local scope is shown as With scope in scope chain pane </a>.</p>
-<p>To test, open the Inspector and start a debugging session. In a second debugger will pause. While paused look at scope chain pane. There should be three scopes: 'With scope' containing objField variable, 'Local scope' with this and self variables and 'Global scope'. All scopes but 'Global' should be expanced. 'Global' scope should be collapsed(it takes too long to expand DOMWindow so we prefer to do it on demand). </p>
-</body>
-
diff --git a/WebCore/manual-tests/inspector/debugger-shortcuts-with-console-opened.html b/WebCore/manual-tests/inspector/debugger-shortcuts-with-console-opened.html
deleted file mode 100644
index df089d5..0000000
--- a/WebCore/manual-tests/inspector/debugger-shortcuts-with-console-opened.html
+++ /dev/null
@@ -1,16 +0,0 @@
-<script>
-function testFunction()
-{
- showAlert();
-}
-
-function showAlert()
-{
- alert("Test completed.");
-}
-</script>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=31252">Bug 31252: Web Inspector: Debugger shortcuts (F8, F10, F11) have no effect if the Console view is open</a>.</p>
-<p>To test, open the Inspector and start a debugging session. Open the Console view (press Esc or click the "Show console" button in the status bar) and make sure it is focused (the cursor is blinking in the text prompt.)
-Set a breakpoint inside testFunction() (on the showAlert() call) and press F8. Now click the Test button in the page. The execution should stop on an HTML line containing <b>onclick="testFunction()"</b>. Press F8. The execution should stop on the breakpoint.
-Press F11, F10, F11 sequentially. You should see the "Test completed." alert dialog ONLY after the last keypress.</p>
-<button onclick="testFunction()">Test</button><br><br>
diff --git a/WebCore/manual-tests/inspector/debugger-status-bar-buttons-state.html b/WebCore/manual-tests/inspector/debugger-status-bar-buttons-state.html
deleted file mode 100644
index 31ca3b1..0000000
--- a/WebCore/manual-tests/inspector/debugger-status-bar-buttons-state.html
+++ /dev/null
@@ -1,2 +0,0 @@
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=19173">Bug 19173: Tool tips for Inspector debugger status bar buttons are wrong/missing</a>.</p>
-<p>To test, open the Inspector and go to the Scripts panel. Check that the tool tips for the debugger's two status bar buttons make sense when each button is toggled on and off.</p>
diff --git a/WebCore/manual-tests/inspector/debugger-step-on-do-while-statements.html b/WebCore/manual-tests/inspector/debugger-step-on-do-while-statements.html
deleted file mode 100644
index 190cbf8..0000000
--- a/WebCore/manual-tests/inspector/debugger-step-on-do-while-statements.html
+++ /dev/null
@@ -1,29 +0,0 @@
-<script src="resources/loop-statements.js"></script>
-<script>
-function runDoWhile()
-{
- /* place breakpoint on next line and click continue */ debugger;
- do {
- statement();
- increment();
- } while (condition());
-}
-
-</script>
-Start a debugging session in the Web Inspector and open this file.
-<br><br>
-Before running the tests please perform the following:
-Make sure the execution is not paused in the debugger.<br>
-Click the button and when the debugger breaks, set a breakpoint on the first line in the loop
-(as indicated by the comment), and click continue.<br>
-The debugger should stop at the beggining of the loop.<br>
-The above actions should be performed before <b>each</b> of the following tests.
-<br><br>
-<input type="button" value="run do-while" onclick="initialize();runDoWhile()"/>
-<br><br>
-TEST 1: Click 'continue'. Execution should continue without stopping on the loop breakpoint again.<br>
-TEST 2: Click 'Step over'. Debugger should step inside the loop to the next statement line.
-'Step over' until the debugger reaches the 'while' line. Click 'Step into' - the debugger should
-enter the 'condition' function.<br>
-TEST 3: 'Step over' to the end of the loop (and 'while' statement) and step over again. Debugger
-should go to the beggining of the loop.<br>
diff --git a/WebCore/manual-tests/inspector/debugger-step-on-for-in-statements.html b/WebCore/manual-tests/inspector/debugger-step-on-for-in-statements.html
deleted file mode 100644
index 8d6de78..0000000
--- a/WebCore/manual-tests/inspector/debugger-step-on-for-in-statements.html
+++ /dev/null
@@ -1,35 +0,0 @@
-<script>
-var myObj = {test : 1};
-function getObject()
-{
- return myObj;
-}
-
-function statement() {
- ;
-}
-
-function runForIn()
-{
- /* place breakpoint on next line and click continue */ debugger;
- for (var property in getObject())
- statement();
-}
-
-</script>
-Start a debugging session in the Web Inspector and open this file.
-<br><br>
-Before running the tests please perform the following:
-Make sure the execution is not paused in the debugger.<br>
-Click the button and when the debugger breaks, set a breakpoint on the first line in the loop
-(as indicated by the comment), and click continue.<br>
-The debugger should stop at the beggining of the loop.<br>
-The above actions should be performed before <b>each</b> of the following tests.
-<br><br>
-<input type="button" value="run for-in" onclick="runForIn()"/>
-<br><br>
-TEST 1: Click 'continue'. Execution should continue without stopping on the loop breakpoint again.<br>
-TEST 2: Click 'Step over'. Debugger should step inside the loop to the next statement line.<br>
-TEST 3: Click 'Step into'. Debugger should step into 'getObject' function.<br>
-TEST 4: 'Step over' to the statement line and then 'Step over' again. Debugger should pause on
-the for-in loop again.<br>
diff --git a/WebCore/manual-tests/inspector/debugger-step-on-for-statements.html b/WebCore/manual-tests/inspector/debugger-step-on-for-statements.html
deleted file mode 100644
index d3a50c6..0000000
--- a/WebCore/manual-tests/inspector/debugger-step-on-for-statements.html
+++ /dev/null
@@ -1,28 +0,0 @@
-<script src="resources/loop-statements.js"></script>
-<script>
-function runFor()
-{
- /* place breakpoint on next line and click continue */ debugger;
- for (initialize(); condition(); increment())
- statement();
-}
-</script>
-Start a debugging session in the Web Inspector and open this file.
-<br><br>
-Before running the tests please perform the following:
-Make sure the execution is not paused in the debugger.<br>
-Click the button and when the debugger breaks, set a breakpoint on the first line in the loop
-(as indicated by the comment), and click continue.<br>
-The debugger should stop at the beggining of the loop.<br>
-The above actions should be performed before <b>each</b> of the following tests.
-<br><br>
-<input type="button" value="run for" onclick="runFor()"/>
-<br><br>
-TEST 1: Click 'continue'. Execution should continue without stopping on the loop breakpoint again.<br>
-TEST 2: Click 'Step over'. Debugger should step inside the loop to the next statement line.<br>
-TEST 3: Click 'Step into'. Debugger should step into 'initialize' function. Click 'Step into' until
-outside of the 'initialize' function - debugger should enter the 'condition' function.<br>
-TEST 4: 'Step over' to the statement line and then 'Step over' again. Debugger should pause on
-the for loop again. Click 'Step into'. Debugger should step into the 'increment' function.
-Click 'Step into' until outside of the 'increment' function - debugger should enter the 'condition'
-function.<br>
diff --git a/WebCore/manual-tests/inspector/debugger-step-on-while-statements.html b/WebCore/manual-tests/inspector/debugger-step-on-while-statements.html
deleted file mode 100644
index fd077bc..0000000
--- a/WebCore/manual-tests/inspector/debugger-step-on-while-statements.html
+++ /dev/null
@@ -1,29 +0,0 @@
-<script src="resources/loop-statements.js"></script>
-<script>
-function runWhile()
-{
- /* place breakpoint on next line and click continue */ debugger;
- while (condition()) {
- statement();
- increment();
- }
-}
-
-</script>
-Start a debugging session in the Web Inspector and open this file.
-<br><br>
-Before running the tests please perform the following:
-Make sure the execution is not paused in the debugger.<br>
-Click the button and when the debugger breaks, set a breakpoint on the first line in the loop
-(as indicated by the comment), and click continue.<br>
-The debugger should stop at the beggining of the loop.<br>
-The above actions should be performed before <b>each</b> of the following tests.
-<br><br>
-<input type="button" value="run while" onclick="initialize();runWhile()"/>
-<br><br>
-TEST 1: Click 'continue'. Execution should continue without stopping on the loop breakpoint again.<br>
-TEST 2: Click 'Step over'. Debugger should step inside the loop to the next statement line.<br>
-TEST 3: Click 'Step into'. Debugger should step into 'condition' function.<br>
-TEST 4: 'Step over' the statements until reaching the end of the loop. Debugger should
-step over to the beggingin of the while loop again. Click 'Step into'. Debugger should step into
-the 'condition' function.<br>
diff --git a/WebCore/manual-tests/inspector/debugger-watch-expressions.html b/WebCore/manual-tests/inspector/debugger-watch-expressions.html
deleted file mode 100644
index eb883c9..0000000
--- a/WebCore/manual-tests/inspector/debugger-watch-expressions.html
+++ /dev/null
@@ -1,115 +0,0 @@
-<p>Test for
-<a href="https://bugs.webkit.org/show_bug.cgi?id=27514">Bug 27514 - add support for watched expression</a>.
-
-<p>To begin test, open web inspector, go the scripts panel
-(enabling script debugging if necccessary), and then click this link:
-<a href="javascript:runTest()">[begin test]</a>.
-
-<p>Perform the following steps, and note the expected results:
-
-<ol>
-
-<li><p>After clicking the link above, you should now be paused in the body of
-the test method, thanks to the <code>debugger</code> statement.
-
-<li><p>Add the following expressions to the "Watch Expressions" section of the
-Scripts panel sidebar pane: "<code>this</code>", "<code>a</code>",
-"<code>b</code>", "<code>c</code>" and "<code>d</code>". Do <b>NOT</b> enter the quotes.
-
-<li><p>The values of the expressions as shown in the window should a
-<code>DOMWindow</code> for <code>this</code>, <code>undefined</code> for
-the <code>a</code>, <code>b</code>, and <code>c</code> variables, and a
-value of <code>ReferenceError: Can't find variable: d</code>
-for the <code>d</code> variable.
-
-<li><p>Note that the value for <code>d</code> should not change for the life of
-the test, as the variable <code>d</code> is never introduced in the program.
-
-<li><p>Step through the code, and you'll see the values of <code>a</code>,
-<code>b</code>, and <code>c</code> change, as the variables are assigned.
-Also note that as the scope changes due to the function invocation, values
-will be changed to refer to their current scope. The <code>this</code>
-expression will change when the method is invoked on the object constructed by
-the test.
-
-<li><p>Click different stack frames in the Call Stack section to ensure the
-expressions change value appropriately as the current stack frame changes.
-
-<li><p>Drive the debugger through the end of the outermost function, so that
-the debugger is no longer in paused state. The values of
-<code>a</code>, <code>b</code>, and <code>c</code> should all be a
-ReferenceError like <code>d</code>, since these variables are defined in the
-<code>runTest()</code> function, and the expressions are being evaluated against
-the global object.
-
-<li><p>From the console, execute the statement "<code>a = 1</code>". The
-watch expressions do not currently refresh, so the value for <code>a</code>
-should still be ReferenceError.
-
-<li><p>Click the "Refresh" button in the Watch Expressions section and the
-value for "<code>a</code>" should now be "<code>1</code>".
-
-<li><p>Close down the browser, start it back up, traverse to a web site,
-bring up web inspector, go to the Scripts panel. You should see the same
-set of Watch Expressions in the list as you had when you last used web
-inspector.
-
-<li><p>Delete an expression by moving the mouse into the Watch Expression
-section, and clicking the X icon which appears to the right of an
-expression (on hover).
-
-<li><p>Delete an expression by double-clicking anywhere on a top-level line
-of a watch expression, and changing the expression to an empty string or
-nothing but white-space.
-
-<li><p>Modify an entry by double-clicking anywhere on a top-level line
-of a watch expression, and changing the expression.
-
-<li><p>Enter a new expression, "<code>new Date()</code>". The value should be
-a toString() version of the date. Repeatedly press the Refresh button to see
-the value updated with the current time.
-
-</ol>
-
-<script>
-function runTest() {
-
- // a nested function
- function subFunction() {
- debugger;
- var a = "a in subFunction()";
-
- subSubFunction();
-
- // another nested function
- function subSubFunction() {
- debugger;
- var b = "b in subSubFunction()";
- }
- }
-
- // a class
- function aClass() {
- this.x = "xxx";
- this.y = "yyy";
- }
-
- aClass.prototype.aMethod = function() {
- debugger;
- var c = "c in aMethod()";
- }
-
- // main logic
- debugger;
-
- var a = "a in runTest()";
- var b = "b in runTest()";
- var c = "c in runTest()";
-
- subFunction();
-
- var object = new aClass();
- object.aMethod();
-
-}
-</script>
diff --git a/WebCore/manual-tests/inspector/display-form-data.html b/WebCore/manual-tests/inspector/display-form-data.html
deleted file mode 100644
index 48cd817..0000000
--- a/WebCore/manual-tests/inspector/display-form-data.html
+++ /dev/null
@@ -1,249 +0,0 @@
-<html>
-<head>
-<title>Tests for Bug 22920</title>
-<meta http-equiv="Content-Type" content="text/html;charset=utf-8" >
-</head>
-
-<body>
-<p>Tests for
-<ul>
-<li><p><a href="https://bugs.webkit.org/show_bug.cgi?id=22920">Bug 22920: Inspector Request Headers Should Show Data/Variables/Parameters Sent With Request</a>
-<li><p><a href="https://bugs.webkit.org/show_bug.cgi?id=28970">Bug 28970: content-type parameters not taken into account when building form-data</a>
-</ul>
-
-<p>To test, open the Inspector on this page, go to the Resources panel,
-and select the various resources created by this page in the left column of the
-Resources panel. Note that for test-4 ...
-test-11, the -sync and -async versions should show the same Form Data,
-Request Payload and/or Query String Parameter values.
-
-<ul>
-
-<li><p><b>test-1</b>:
-<br>no Form Data, Request Payload or Query String Parameters
-
-<li><p><b>test-2</b>:
-<br>Query String Parameters (1): "parm1: abc"
-
-<li><p><b>test-3</b>:
-<br>Query String Parameters (2): "parm1: def" and "parm2: g h i";
-Hovering over either parm should yield a tooltip:
-<i>"Double-Click to toggle between URL encoded and decoded formats"</i>.
-Double-clicking on either parm should toggle between encoded and decoded
-versions of the string. The decoded form is initially displayed.
-The encoded form of parm2 is "g%20h+i".
-
-<li><p><b>test-4</b>:
-<br>no Form Data, Request Payload or Query String Parameters
-
-<li><p><b>test-5</b>:
-<br>Query String Parameters (1): "parm1: abc"
-
-<li><p><b>test-6</b>:
-<br>Query String Parameters (3): "parm1: def" and "parm2: g h i" and "parm3: jj kk ll"
-
-<li><p><b>test-7</b>:
-<br>Request Payload: 3 lines of text data with a very long 2nd line which should wrap
-
-<li><p><b>test-8</b>:
-<br>Request Payload: 3 lines of text data with a very long 2nd line which should wrap
-
-<li><p><b>test-9</b>:
-<br>Request Payload: 3 lines of text data with a very long 2nd line of binary data which should wrap
-
-<li><p><b>test-10</b>:
-<br>Form Data (1): "parm1: abc"
-
-<li><p><b>test-11</b>:
-<br>Form Data (2): "parm1: def" and "parm2: g h i"
-
-<li><p><b>test-12</b>:
-<br>Query String Parameters (2): "parm1: abc" and "parm2: d e f"
-<br>Form Data (2): "parm1: ghi" and "parm2: j k l"
-
-<li><p><b>test-13</b>:
-<br>Query String Parameters (2): "parm1: &auml;bc" and "parm2: d &#x11B; f"
-<br>Form Data (2): "parm1: ghi" and "parm2: j k l"
-<p>Note that you should view the encoded values of the query string parameters
-by double-clicking on one of the parameters. The values should be:
-<pre>
-parm1: %C3%A4bc
-parm2: d%20%C4%9B+f
-</pre>
-
-<li><p><b>test-14</b>:
-<br>Same results as for test-13, a slightly different but compatible Content-Type
-is used for the form data.
-
-<li><p><b>test-15</b>:
-<br>Query String Parameters (2): "parm1: % (unable to decode value)" and "parm2: % (unable to decode value)",
-with the parenthesized part in red.
-<br>Form Data (2): "parm1: % (unable to decode value)" and "parm2: % (unable to decode value)",
-with the parenthesized part in red.
-<p>Note that you should view the encoded values of the query string parameters
-by double-clicking on one of the parameters. The values for all four parameters should be "%".
-
-<li><p><b>test-form</b>:
-<br>For this test, invoke the form at the bottom of the page
-by pressing the submit button. The Resources panel should have a "test-form"
-resource, with the following data:
-<p>Form Data (2): "field1: value &auml;;b;c" and "field2:value d;&#x11B;;f"
-<p>Note that you should view the encoded values of the query string parameters
-by double-clicking on one of the parameters. The values should be:
-<pre>
-field1: value+%C3%A4%3Bb%3Bc
-field2: value+d%3B%C4%9B%3Bf</pre>
-</ul>
-
-<p><b>test-form</b>
-<form id="form" action="http://example.org/test-form" method="post" enctype="application/x-www-form-urlencoded">
-<span style="font-size:200%">field1:</span> <input style="font-size:200%" type="text" name="field1" value="value &auml;;b;c"><br>
-<span style="font-size:200%">field2:</span> <input style="font-size:200%" type="text" name="field2" value="value d;&#x11B;;f"><br>
-<input type="submit">
-</form>
-
-<div style="display:none">
-
-<img src="http://example.org/test-1">
-<img src="http://example.org/test-2?parm1=abc">
-<img src="http://example.org/test-3?parm1=def&amp;parm2=g%20h+i">
-
-</div>
-
-<hr>
-
-<p><b>NLS sample info</b>
-
-<pre>
-<span style="font-size:300%">&auml;</span> - LATIN SMALL LETTER A WITH DIAERESIS
-Unicode: 0x00E4 == 228
-UTF8: C3 A4
-HTML: &amp;auml;
-
-<span style="font-size:300%">&#x11B;</span> - LATIN SMALL LETTER E WITH CARON
-Unicode: 0x011B == 283
-UTF8: C4 9B
-HTML: &amp;#x11B;
-</pre>
-
-<script>
-
-function getReadyState(num) {
- switch(num) {
- case 0: return "uninitialized";
- case 1: return "loading";
- case 2: return "loaded";
- case 3: return "interactive";
- case 4: return "complete";
- default: return "unknown: " + num;
- }
-}
-
-function getProcessXHR(request) {
- return function() {
- if (true) return;
- var rs = getReadyState(request.readyState);
- console.log("ready state change for " + request.url);
- console.log(" ready state: " + rs);
- console.log(" response text: " + request.responseText);
- if (request.readyState == 4) {
- console.log(" status: " + request.status);
- console.log(" status text: " + request.statusText);
- }
- }
-}
-
-function sendXHR(url, method, headers, body) {
- if (!method) method = "GET";
- if (!headers) headers = [];
- if (!body) body="";
-
- // copy headers
- var headersNew = [];
- for (var i=0; i<headers.length; i++) {
- headersNew.push(headers[i]);
- }
- headers = headersNew;
-
- if (body != "") {
- headers.push(["Content-Length", body.length.toString()]);
- }
-
- // sync
- var req = new XMLHttpRequest();
-
- req.url = url.replace("^","-sync");
- req.onreadystatechange = getProcessXHR(req);
- req.open(method, req.url, false);
-
- for (var i=0; i<headers.length; i++) {
- req.setRequestHeader(headers[i][0], headers[i][1]);
- }
-
- req.send(body);
-
- // async
- var req = new XMLHttpRequest();
-
- req.url = url.replace("^","-async");
- req.onreadystatechange = getProcessXHR(req);
- req.open(method, req.url, true);
-
- for (var i=0; i<headers.length; i++) {
- req.setRequestHeader(headers[i][0], headers[i][1]);
- }
-
- req.send(body);
-}
-
-var headersPlain = [
- ["Content-Type", "text/plain"]
-];
-
-var headersForm = [
- ["Content-Type", "application/x-www-form-urlencoded"]
-];
-
-var headersFormExtra1 = [
- ["Content-Type", "application/x-www-form-urlencoded;something-else=here"]
-];
-
-var headersFormExtra2 = [
- ["Content-Type", "application/x-www-form-urlencoded ; something-else=here"]
-];
-
-var headersBinary = [
- ["Content-Type", "application/octet-stream"]
-];
-
-var longText = "some text with a \n";
-for (var i=0; i<40; i++) {
- longText += "very-";
-}
-longText += "long\nline in it";
-
-var binaryData = "some text with binary data\n";
-for (var i=0; i<256; i++) {
- binaryData += String.fromCharCode(i);
-}
-binaryData += "\nin the middle of it";
-
-
-sendXHR("http://example.org/test-4^");
-sendXHR("http://example.org/test-5^?parm1=abc");
-sendXHR("http://example.org/test-6^?parm1=def&parm2=g%20h+i&parm3=jj++kk%20%20ll");
-
-sendXHR("http://example.org/test-7^", "POST", null, longText);
-sendXHR("http://example.org/test-8^", "POST", headersPlain, longText);
-sendXHR("http://example.org/test-9^", "POST", headersBinary, binaryData);
-sendXHR("http://example.org/test-10^", "POST", headersForm, "parm1=abc");
-sendXHR("http://example.org/test-11^", "POST", headersForm, "parm1=def&parm2=g%20h+i");
-sendXHR("http://example.org/test-12^?parm1=abc&parm2=d%20e+f", "POST", headersForm, "parm1=ghi&parm2=j%20k+l");
-sendXHR("http://example.org/test-13^?parm1=%C3%A4bc&parm2=d%20%C4%9B+f", "POST", headersFormExtra1, "parm1=ghi&parm2=j%20k+l");
-sendXHR("http://example.org/test-14^?parm1=%C3%A4bc&parm2=d%20%C4%9B+f", "POST", headersFormExtra2, "parm1=ghi&parm2=j%20k+l");
-sendXHR("http://example.org/test-15^?parm1=%&parm2=%", "POST", headersForm, "parm1=%&parm2=%");
-
-</script>
-
-</body>
-</html> \ No newline at end of file
diff --git a/WebCore/manual-tests/inspector/display-sql-null.html b/WebCore/manual-tests/inspector/display-sql-null.html
deleted file mode 100644
index 1d1403b..0000000
--- a/WebCore/manual-tests/inspector/display-sql-null.html
+++ /dev/null
@@ -1,21 +0,0 @@
-<script>
- try {
- var db = openDatabase("InspectorTest", "0.1", "Database for Inspector tests", 200000);
- db.transaction(function(tx) {
- tx.executeSql("CREATE TABLE DisplaySQLNull (test TEXT)", [], function(tx) {
- tx.executeSql("INSERT INTO DisplaySQLNull (test) VALUES (NULL)");
- })
- });
- } catch (e) {
- }
-</script>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=18837">Bug 18837: Database panel fails to display tables if any value is NULL</a>.</p>
-<p>To test:</p>
-<ol>
- <li>Open the Inspector</li>
- <li>Go to the Databases panel</li>
- <li>Click on the <code>DisplaySQLNull</code> table inside the <code>InspectorTest</code> database</li>
-</ol>
-<p>If the contents of the table appear (a single row with the value
-"<code>null</code>" in the <code>test</code> column), you have passed the
-test.</p>
diff --git a/WebCore/manual-tests/inspector/display-sql-transaction-error.html b/WebCore/manual-tests/inspector/display-sql-transaction-error.html
deleted file mode 100644
index da2d310..0000000
--- a/WebCore/manual-tests/inspector/display-sql-transaction-error.html
+++ /dev/null
@@ -1,24 +0,0 @@
-<script>
- try {
- var db = openDatabase("InspectorTest", "0.1", "Database for Inspector tests", 200000);
- db.transaction(function(tx) {
- tx.executeSql("CREATE TABLE DisplaySQLTransactionError (test TEXT)", []);
- });
- } catch (e) {
- }
-</script>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=19438">Bug 19438: Transaction errors are never displayed in database query view</a>.</p>
-<p>To test:</p>
-<ol>
- <li>Open the Inspector</li>
- <li>Go to the Databases panel</li>
- <li>Click on the <code>InspectorTest</code> database</li>
- <li>Enter the following text on the query input line: <code>INSERT INTO DisplaySQLTransactionError (test) VALUES (NULL)</code></li>
-</ol>
-<p>If the line of text you entered remains and an error line is output below
-it, you have passed the test.</p>
-<p>If the line of text you entered disappears and no error line is output, you
-have failed the test.</p>
-<p>If the line of text you entered remains and no error line is output, then
-the test has become invalid and needs to be modified to cause the error
-callback passed by the Inspector to <code>db.transaction</code> to be called.</p>
diff --git a/WebCore/manual-tests/inspector/dom-mutation.html b/WebCore/manual-tests/inspector/dom-mutation.html
deleted file mode 100644
index 33e8333..0000000
--- a/WebCore/manual-tests/inspector/dom-mutation.html
+++ /dev/null
@@ -1,31 +0,0 @@
-<script>
-function test1() {
- document.getElementById("test").src = "resources/mutate-frame.html";
-}
-
-function test2() {
- document.getElementById("test").src = "resources/mutate-frame-2.html";
-}
-
-var count = 1;
-function run() {
- var container = document.getElementById("test2");
- var div = document.createElement("div");
- div.textContent = "Testing " + (count++);
- container.appendChild(div);
- if (count > 10)
- container.removeChild(container.firstChild);
-}
-
-setInterval(run, 1000);
-</script>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=6590">Bug 6590: Web Inspector shows stale DOM tree if the DOM changes after the inspector has loaded</a>.</p>
-<p>To test, open the Inspector and watch the DOM change to match the page. Clicking the buttons will navigate the subframe, and the all the subframe child nodes should change.</p>
-<div style="clear: both">
-<button onclick="test1()">Test Frame 1</button>
-<button onclick="test2()">Test Frame 2</button>
-</div>
-<div style="float: left">
-<iframe id="test" src="resources/mutate-frame.html" width="200" height="300"></iframe>
-</div>
-<div style="float: left; margin-left: 10px;" id="test2"></div>
diff --git a/WebCore/manual-tests/inspector/duplicate-resource-urls.html b/WebCore/manual-tests/inspector/duplicate-resource-urls.html
deleted file mode 100644
index 7a9be7e..0000000
--- a/WebCore/manual-tests/inspector/duplicate-resource-urls.html
+++ /dev/null
@@ -1,61 +0,0 @@
-<html>
-<head>
-<title>Tests for Bug 30079</title>
-<meta http-equiv="Content-Type" content="text/html;charset=utf-8" >
-</head>
-
-<body>
-<p>Tests for
-<ul>
-<li><p><a href="https://bugs.webkit.org/show_bug.cgi?id=30079">Bug 30079: unselectable resources in resource panel</a>
-</ul>
-
-<p>To test, open the Inspector on this page, go to the Resources panel.
-
-<p>First off, you should be able to actually select each "abc" resource to see
-the HTTP info / content. Bug 30079 didn't allow you to select all of these.
-
-<p>For each of the "abc" resources open the <b>HTTP Information</b> and
-<b>Request Payload</b> tree elements above the content. One of the resources
-will not have a <b>Request Payload</b>.
-
-<p>There should be one each of the following resources:
-
-<ul>
-<li><p>One with a Request Method: GET and no Request Payload
-<li><p>One with a Request Method: POST and Request Payload of "123"
-<li><p>One with a Request Method: POST and Request Payload of "456"
-</ul>
-
-<p>Another change made by this bug was to change the way the drag/drop of
-the resource itself worked. The previous method of handling drag/drop of
-the resource was actually causing the unselectability. So the drag/drop
-of the resources needs to be tested as well.
-
-<ul>
-<li><p>Select one of the resources.
-<li><p>Drag it to an application that can accept text or a link
-<li><p>The application should provide some feedback indicating it will accept
-the drop, but may not
-<li>Drop, and the URL for the resource should be rendered appropriately.
-
-<script>
-
-var xhr;
-
-xhr = new XMLHttpRequest();
-xhr.open("POST", "http://example.org/abc");
-xhr.send("123");
-
-xhr = new XMLHttpRequest();
-xhr.open("POST", "http://example.org/abc");
-xhr.send("456");
-
-xhr = new XMLHttpRequest();
-xhr.open("GET", "http://example.org/abc");
-xhr.send();
-
-</script>
-
-</body>
-</html>
diff --git a/WebCore/manual-tests/inspector/error-warning-count.html b/WebCore/manual-tests/inspector/error-warning-count.html
deleted file mode 100644
index 9f6b9c2..0000000
--- a/WebCore/manual-tests/inspector/error-warning-count.html
+++ /dev/null
@@ -1,60 +0,0 @@
-<script>
- function clickHandler(errors, warnings)
- {
- return function()
- {
- for (var i = 0; i < errors; ++i)
- console.error("Error " + (i + 1));
- for (var i = 0; i < warnings; ++i)
- console.warn("Warning " + (i + 1));
- }
- }
-
- function loaded()
- {
- var tests = [
- { errors: 0, warnings: 0 },
- { errors: 1, warnings: 0 },
- { errors: 2, warnings: 0 },
- { errors: 0, warnings: 1 },
- { errors: 0, warnings: 2 },
- { errors: 1, warnings: 1 },
- { errors: 1, warnings: 2 },
- { errors: 2, warnings: 1 },
- { errors: 2, warnings: 2 },
- { errors: 100, warnings: 100 },
- ];
-
- for (var i in tests) {
- var test = tests[i];
-
- var button = document.createElement("button");
- var content = "";
- if (!test.errors && !test.warnings)
- content = "(nothing)";
- else {
- if (test.errors > 0)
- content += test.errors + " error" + (test.errors != 1 ? "s" : "");
- if (test.warnings > 0) {
- if (content.length)
- content += ", ";
- content += test.warnings + " warning" + (test.warnings != 1 ? "s" : "")
- }
- }
- button.innerText = content;
- button.onclick = clickHandler(test.errors, test.warnings);
- var p = document.createElement("p");
- p.appendChild(button);
- document.body.appendChild(p);
- }
- }
-</script>
-<body onload="loaded()">
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=18650">Bug 18650:
-Errors/warnings in Inspector should be visible outside of Resources</a>.</p>
-<p>To test, open the Inspector and click one of the buttons below. You should
-see an error and/or warning count in the Inspector's status bar. Clicking on
-the error/warning count should open the Console. Hovering over the
-error/warning count should show you a tooltip that matches the text in the
-button you clicked.</p>
-<p>Note: You must reload the page between each button press.</p>
diff --git a/WebCore/manual-tests/inspector/errors-with-space in-url.html b/WebCore/manual-tests/inspector/errors-with-space in-url.html
deleted file mode 100644
index 07e8ee0..0000000
--- a/WebCore/manual-tests/inspector/errors-with-space in-url.html
+++ /dev/null
@@ -1,7 +0,0 @@
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=19065">Bug 19065:
-Resources with a space in their URL don't get error/warning bubbles</a>.</p>
-<p>To test, open the Inspector and refresh this page. There should be a red
-bubble with the number "1" in it next to the main resource in the Resources
-panel. Clicking the button below should change the "1" to a "2".</p>
-<p></p></p>
-<button onclick="console.error('hi')">click me</button>
diff --git a/WebCore/manual-tests/inspector/escape-links.html b/WebCore/manual-tests/inspector/escape-links.html
deleted file mode 100644
index 5c5f6c0..0000000
--- a/WebCore/manual-tests/inspector/escape-links.html
+++ /dev/null
@@ -1 +0,0 @@
-<html>
diff --git a/WebCore/manual-tests/inspector/forzen-ui-while-paused.html b/WebCore/manual-tests/inspector/forzen-ui-while-paused.html
deleted file mode 100644
index b8d50b0..0000000
--- a/WebCore/manual-tests/inspector/forzen-ui-while-paused.html
+++ /dev/null
@@ -1,11 +0,0 @@
-<script>
-function foo() {
- var timeout = setTimeout(function() { alert("This should not happen. If you do see this alert, then timers on the page are firing while paused!") }, 0);
- debugger;
- clearTimeout(timeout);
-}
-
-setTimeout(foo, 100);
-</script>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=20042">Bug 20042: UI frozen when the debugger is paused</a>.</p>
-<p>Open the inspector and start debugging in the Scripts panel. While paused, try to open the Console. The Console should animate open fully.</p>
diff --git a/WebCore/manual-tests/inspector/hidden-evals.html b/WebCore/manual-tests/inspector/hidden-evals.html
deleted file mode 100644
index c507bcd..0000000
--- a/WebCore/manual-tests/inspector/hidden-evals.html
+++ /dev/null
@@ -1,118 +0,0 @@
-
-<p><b>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=30212">Bug 30212</a> - Each JS execution in console adds extra item into "scripts" combo</b>
-
-<p>The following manual test creates functions via <tt>eval()</tt> and the
-<tt>Function()</tt> constructor, some functions are named using the
-<code>//@sourceURL=</code> directive, some aren't. Some contain
-<tt>debugger</tt> commands, some don't.
-
-<p>The functions named <tt>f_named_X</tt> are 'named' via the
-<code>//@sourceURL=</code> directive, the ones named <tt>f_unnamed_X</tt>
-are not. The 'named' functions should show up in the Scripts select element used
-to select a resource/script to view, the 'unnamed' ones should not.
-
-<ul>
-<li><p>open this page with Web Inspector
-<li><p>switch to the Scripts panel, enabling debug if required
-<li><p>the available scripts in the select element should be:
-<ul>
-<li>(program): f_named_1.eval
-<li>(program): f_named_2.eval
-<li>(program): f_named_3.eval
-<li>hidden-evals.html
-</ul>
-<li><p>click this button: <input id=button type=button value="click me">
-<li><p>debugger should stop in the <code>clickHandler</code> function
-<li><p>at this point, start stepping <b>into</b> the code
-<li><p>you should be able to step into functions <code>f_unnamed_1()</code>
-and <code>f_unnamed_2()</code>. There are no resource/scripts in the
-select element that contain these functions, until you actually are paused
-in them. At that point, entries for these functions will be in the select element,
-named: "(program)". After pausing in both functions, there will be two "(program)"
-entries.
-<li><p>you should be able to use the next/prev buttons (to the left of the select element)
-to switch to other resources/scripts that have been opened, including the ones
-containing these functions
-<li><p>you should be able to click on the functions that exist in the 'hidden'
-resources from the Call Stack, and be shown the source; click around the
-stack trace entries to verify
-<li><p>rather than stepping into the <code>f_named_3()</code> call, press the
-resume button
-<li><p>the debugger should stop in <code>f_named_3()</code> because of the
-<code>debugger</code> command
-<li><p>rather than stepping into the <code>f_unnamed_3()</code> call, press the
-resume button
-<li><p>the debugger should stop in <code>f_unnamed_3()</code> because of the
-<code>debugger</code> command. At this point, a third "(program)" entry for
-this function is added to the select element.
-</ul>
-
-<script>
-
-function doNothing() { /* allows multi-line functions, easier to debug */ };
-
-eval([
- "function f_named_1() {",
- " doNothing();",
- " return 'named_1';",
- "}",
- "//@sourceURL=f_named_1.eval"
-].join("\n"));
-
-eval([
- "function f_unnamed_1() {",
- " doNothing();",
- " return 'unnamed_1';",
- "}"
-].join("\n"));
-
-f_named_2 = Function([
- "",
- " doNothing();",
- " return 'named_2';",
- "//@sourceURL=f_named_2.eval"
-].join("\n"));
-
-f_unnamed_2 = Function([
- "",
- " doNothing();",
- " return 'unnamed_2';"
-].join("\n"));
-
-f_named_3 = Function([
- "",
- " debugger;",
- " doNothing();",
- " return 'named_3';",
- "//@sourceURL=f_named_3.eval"
-].join("\n"));
-
-f_unnamed_3 = Function([
- "",
- " debugger;",
- " doNothing();",
- " return 'unnamed_3';"
-].join("\n"));
-
-var button = document.getElementById("button");
-
-button.addEventListener("click", clickHandler, false);
-
-function clickHandler() {
- debugger;
- f_named_1();
- f_unnamed_1();
- f_named_2();
- f_unnamed_2();
-
- // press "resume" at this point
- console.log("press resume before calling f_named_3()");
- f_named_3();
-
- // press "resume" at this point
- console.log("press resume before calling f_unnamed_3()");
- f_unnamed_3();
-}
-
-</script>
-<!-- End -->
diff --git a/WebCore/manual-tests/inspector/highlight-nodes.html b/WebCore/manual-tests/inspector/highlight-nodes.html
deleted file mode 100644
index 6712b3a..0000000
--- a/WebCore/manual-tests/inspector/highlight-nodes.html
+++ /dev/null
@@ -1,23 +0,0 @@
-<style>
-.skewed {
- -webkit-transform:skew(-5deg,-5deg);
-}
-</style>
-<p>This page has basic tests of node highlighting in the inspected page. To tests, load this page, open the inspector and mouseover the nodes in the treeview of the inspector. You should see the highlights happen with the appropriate padding/border/margin/content highlights.</p>
-<div style="padding:10px; border: 10px solid; margin: 10px;">padding:10px; border: 10px; margin: 10px;</div>
-<div style="padding:10px; border: 10px solid;">padding:10px; border: 10px;</div>
-<div style="padding:10px; margin: 10px;">padding:10px; margin: 10px;</div>
-<div style="border: 10px solid; margin: 10px;">border: 10px; margin: 10px;</div>
-<div style="padding:10px">padding:10px;</div>
-<div style="border: 10px solid;">border: 10px;</div>
-<div style="margin: 10px;">margin: 10px;</div>
-<div>no padding, border, or margin</div>
-<div class=skewed style="padding:10px; border: 10px solid; margin: 10px;">-webkit-transform:skew(-5deg,-5deg); padding:10px; border: 10px; margin: 10px;</div>
-<div class=skewed style="padding:10px; border: 10px solid;">-webkit-transform:skew(-5deg,-5deg); padding:10px; border: 10px;</div>
-<div class=skewed style="padding:10px; margin: 10px;">-webkit-transform:skew(-5deg,-5deg); padding:10px; margin: 10px;</div>
-<div class=skewed style="border: 10px solid; margin: 10px;">-webkit-transform:skew(-5deg,-5deg); border: 10px; margin: 10px;</div>
-<div class=skewed style="padding:10px">-webkit-transform:skew(-5deg,-5deg); padding:10px;</div>
-<div class=skewed style="border: 10px solid;">-webkit-transform:skew(-5deg,-5deg); border: 10px;</div>
-<div class=skewed style="margin: 10px;">-webkit-transform:skew(-5deg,-5deg); margin: 10px;</div>
-<div class=skewed >-webkit-transform:skew(-5deg,-5deg); no padding, border, or margin</div>
-
diff --git a/WebCore/manual-tests/inspector/highlight-source-line.html b/WebCore/manual-tests/inspector/highlight-source-line.html
deleted file mode 100644
index 2520485..0000000
--- a/WebCore/manual-tests/inspector/highlight-source-line.html
+++ /dev/null
@@ -1,4 +0,0 @@
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=19204">Bug 19204: Inspector should highlight source lines when following links to them</a>.</p>
-<p>To test, open the Inspector and reload this page. Then open the Inspector's Console and click the link for the markup error. You should see the line containing the error briefly highlighted in the source view.</p>
-
-<p>This line contains a markup error</i>.</p>
diff --git a/WebCore/manual-tests/inspector/multiple-console-messages.html b/WebCore/manual-tests/inspector/multiple-console-messages.html
deleted file mode 100644
index 842e6aa..0000000
--- a/WebCore/manual-tests/inspector/multiple-console-messages.html
+++ /dev/null
@@ -1,86 +0,0 @@
-<html>
-<head>
- <script>
- function generateErrors(number)
- {
- for (var i = 0; i < number; ++i)
- console.error("This is an error.");
- }
-
- function generateLogs(number)
- {
- for (var i = 0; i < number; ++i)
- console.log("This is a log.");
- }
-
- function generateWarnings(number)
- {
- for (var i = 0; i < number; ++i)
- console.warn("This is a warning.");
- }
-
- function generateInfos(number)
- {
- for (var i = 0; i < number; ++i)
- console.info("This is an info.");
- }
-
- function startTest()
- {
- generateErrors(3);
- generateLogs(3);
- generateWarnings(3);
-
- console.group();
-
- generateErrors(2);
- generateLogs(1);
- generateErrors(2);
-
- generateLogs(2);
- generateWarnings(1);
- generateLogs(2);
-
- generateWarnings(2);
- generateErrors(1);
- generateWarnings(2);
-
- console.groupEnd();
-
- generateErrors(1);
- console.group();
- generateErrors(1);
- console.group();
- generateErrors(1);
- console.groupEnd();
- generateErrors(1);
- console.groupEnd();
- generateErrors(1);
-
- console.warn("Same message, different level");
- console.error("Same message, different level");
- console.log("Same message, different level");
- console.info("Same message, different level");
-
- console.log("Variadic message: %s", "message 1");
- console.log("Variadic message: %s", "message 2");
- console.log("Variadic message: %s", "message 3");
- console.log("Variadic message: %s", "message 4");
-
- console.warn("Warning and error on same line."); console.error("Warning and error on same line."); console.warn("Warning and error on same line."); console.error("Warning and error on same line.");
-
- }
- </script>
-</head>
-<body onload="startTest()">
-This test generates warnings, errors, and logs to test the grouping of repeated
-messages in the Web Inspector. To check this test open the Web Inspector and see
-that there are never any repeated messages that don't have a number next to them.
-<br>
-<br>
-<input type="button" onclick="generateErrors(1)" value="Put Error in Console"></input>
-<br>
-<input type="button" onclick="generateLogs(1)" value="Put Log in Console"></input>
-<br>
-<input type="button" onclick="generateWarnings(1)" value="Put Warning in Console"></input>
-</body>
diff --git a/WebCore/manual-tests/inspector/named-evals.html b/WebCore/manual-tests/inspector/named-evals.html
deleted file mode 100644
index 0c52531..0000000
--- a/WebCore/manual-tests/inspector/named-evals.html
+++ /dev/null
@@ -1,72 +0,0 @@
-<html>
-<head>
-<script>
-
-function log(message) {
- console.log(message)
-}
-
-var funcBody = "(){\n" +
-" var thisFunc = arguments.callee;\n" +
-" if (!thisFunc.name) thisFunc.displayName = 'f%';\n" +
-" log(thisFunc.name || thisFunc.displayName);\n" +
-"}";
-
-var funcs = [];
-var patterns = [
- // proper use of @sourceURL comment
- "//@sourceURL=f%.js\nfuncs.push(function" + funcBody + ")",
- "//@sourceURL=f%.js\nfuncs.push(function f%" + funcBody + ")",
- " //@sourceURL=f%.js\nfuncs.push(function f%" + funcBody + ")",
- "// @sourceURL=f%.js\nfuncs.push(function f%" + funcBody + ")",
- "//@ sourceURL=f%.js\nfuncs.push(function f%" + funcBody + ")",
- "//@sourceURL =f%.js\nfuncs.push(function f%" + funcBody + ")",
- "//@sourceURL= f%.js\nfuncs.push(function f%" + funcBody + ")",
- "//@sourceURL=f%.js \nfuncs.push(function f%" + funcBody + ")",
- " // @ sourceURL = f%.js \nfuncs.push(function f%" + funcBody + ")",
- "//@sourceURL=f%.js\nfuncs.push(function f%" + funcBody + ");\n//@sourceURL=should-not-see\n",
- "funcs.push(function f%" + funcBody + ")\n//@sourceURL=f%.js\n",
- "funcs.push(function f%" + funcBody + ")\n//@sourceURL=f%.js \n",
- "funcs.push(function f%" + funcBody + ")\n//@sourceURL=f%.js",
-
- // improper or non-existant use of @sourceURL comment
- "funcs.push(function f%" + funcBody + ")",
- "//@sourceurl=f%.js\nfuncs.push(function f%" + funcBody + ")",
- "//sourceURL=f%.js\nfuncs.push(function f%" + funcBody + ")",
- "/*@sourceURL=f%.js*/\nfuncs.push(function f%" + funcBody + ")",
- "//\nsourceURL='f%.js';\nfuncs.push(function f%" + funcBody + ")",
- "//@sourceURL=\nfuncs.push(function" + funcBody + ")",
-];
-
-
-for (var i=0; i<patterns.length; i++) {
- eval(patterns[i].replace(/%/g, i));
-}
-
-</script>
-</head>
-
-<body>
-<p>This page's JavaScript calls functions from named eval()'s.
-
-<p>Used to test <a href="https://bugs.webkit.org/show_bug.cgi?id=25475">https://bugs.webkit.org/show_bug.cgi?id=25475</a>
-
-<p>Load the Web Inspector and look at
-the script's panel, and the script list drop-down control.
-You should see entries for scripts named
-<tt>"(program):f0.js"</tt> through <tt>"(program):f12.js"</tt>. The entries were named
-via proper use of the <tt>//@sourceURL</tt> comment. There will also be entries
-named <tt>"(program)"</tt> for source that does not properly use, or use at all,
-the <tt>//@sourceURL</tt> comment.
-
-<p>Now, set a breakpoint in the body of the <tt>"f0"</tt> function in the
-<tt>"(program):f0.js"</tt> script. Then click this button:
-
-<p><input type="button" value="run" onclick="funcs[0]()">
-
-<p>When stopped at the breakpoint, the entry for the function in the
-call stack control should the name of the script, <tt>"(program):f0.js"</tt>,
-beside the function name <tt>"f0"</tt>. Note the function name for
-<tt>f0</tt> is set with the new <tt>"displayName"</tt> property.
-</body>
-</html>
diff --git a/WebCore/manual-tests/inspector/profiler-test-call.html b/WebCore/manual-tests/inspector/profiler-test-call.html
deleted file mode 100644
index 572a2e9..0000000
--- a/WebCore/manual-tests/inspector/profiler-test-call.html
+++ /dev/null
@@ -1,35 +0,0 @@
-<html>
-<head>
-<script src="resources/profiler-test-JS-resources.js"></script>
-<script>
-console.profile("Using the call() method");
-function startTest()
-{
- var myObject = new fakeObject(1, 2);
- endTest();
-}
-
-function fakeObject (x, y)
-{
- this.x = x;
- fakeInteriorFunction.call(this, y);
-}
-
-function fakeInteriorFunction(y)
-{
- this.y = y;
-}
-
-</script>
-</head>
-
-<body onload="startTest()">
-This page's JavaScript has a call to call() in it.
-<br>
-<br>
-To use this test, load it in the browser then load the WebInspector and look at
-the profile. In the profile there should be a call to fakeObject() with call() as
-its child and a fakeInteriorFunction() as call()'s child.
-<div id="output"></div>
-</body>
-</html>
diff --git a/WebCore/manual-tests/inspector/profiler-test-many-calls-in-the-same-scope.html b/WebCore/manual-tests/inspector/profiler-test-many-calls-in-the-same-scope.html
deleted file mode 100644
index da5be42..0000000
--- a/WebCore/manual-tests/inspector/profiler-test-many-calls-in-the-same-scope.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<html>
-<head>
-<script src="resources/profiler-test-JS-resources.js"></script>
-<script>
-console.profile("Many Calls In The Same Scope");
-function startTest()
-{
- insertNewText();
- insertGivenText("This was a triumph.");
- arrayOperatorFunction(7);
- intermediaryFunction();
- anonymousFunction();
- end()
- endT();
- endT();
- endTest();
-}
-
-function end()
-{
- var x = 0;
-}
-
-function endT()
-{
- var y = 1;
-}
-
-</script>
-</head>
-
-<body onload="startTest()">
-This page's JavaScript has many function calls in the same scope.
-<br>
-<br>
-To use this test, load it in the browser then load the WebInspector and look at
-the profile. In the profile many functions should be the children of startTest.
-Use the sorting capabilites to make sure the similarly named functions are sorted
-correctly.
-<div id="output"></div>
-</body>
-</html> \ No newline at end of file
diff --git a/WebCore/manual-tests/inspector/remember-last-script.html b/WebCore/manual-tests/inspector/remember-last-script.html
deleted file mode 100644
index 52e7f02..0000000
--- a/WebCore/manual-tests/inspector/remember-last-script.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<style>code{background-color: #ffc;}</style>
-<p><b>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=27552">Bug 27552</a> - remember last script displayed in Scripts panel</b>
-
-<ul>
-<li><p>open this page with Web Inspector, switch to the <b>Scripts</b> panel, enabling debug if required
-<li><p>the available scripts in the select element should be:
- <ul>
- <li><b>(program): f1.js</b>
- <li><b>remember-last-script.html</b>
- </ul>
-<li><p>select <b>(program): f1.js</b> so the source is available
-<li><p>switch to the <b>Resources</b> panel
-<li><p>close Web Inspector
-<li><p>Repeat the following several times. Each time, <b>(program): f1.js</b>
-should be the selected script:
- <ul>
- <li>open Web Inspector, switch to the <b>Scripts</b> panel, then close Web Inspector
- </ul>
-<li><p>open Web Inspector, switch to the <b>Scripts</b> panel
-<li><p>select <b>remember-last-script.html</b> so the source is available
-<li><p>Repeat the following several times. Each time, <b>remember-last-script.html</b>
-should be the selected script:
- <ul>
- <li>open Web Inspector, switch to the <b>Scripts</b> panel, then close Web Inspector
- </ul>
-</ul>
-
-<script>
-
-f1 = Function([
- "",
- " doNothing();",
- "//@sourceURL=f1.js"
-].join("\n"));
-
-function doNothing() { /* allows multi-line functions, easier to debug */ };
-
-doNothing();
-f1();
-
-</script>
-<!-- End -->
diff --git a/WebCore/manual-tests/inspector/resources/loop-statements.js b/WebCore/manual-tests/inspector/resources/loop-statements.js
deleted file mode 100644
index cbb4e0d..0000000
--- a/WebCore/manual-tests/inspector/resources/loop-statements.js
+++ /dev/null
@@ -1,22 +0,0 @@
-var i;
-var a;
-
-function initialize()
-{
- i = false;
-}
-
-function condition()
-{
- return !i;
-}
-
-function increment()
-{
- i = !i;
-}
-
-function statement()
-{
- a = i;
-}
diff --git a/WebCore/manual-tests/inspector/resources/mutate-frame-2.html b/WebCore/manual-tests/inspector/resources/mutate-frame-2.html
deleted file mode 100644
index 9d413b9..0000000
--- a/WebCore/manual-tests/inspector/resources/mutate-frame-2.html
+++ /dev/null
@@ -1,12 +0,0 @@
-<script>
-var count = 1;
-function run() {
- var div = document.createElement("div");
- div.textContent = "Testing " + (count++);
- document.body.appendChild(div);
- if (count > 10)
- document.body.removeChild(document.body.firstChild);
-}
-
-setInterval(run, 1000);
-</script>
diff --git a/WebCore/manual-tests/inspector/resources/mutate-frame.html b/WebCore/manual-tests/inspector/resources/mutate-frame.html
deleted file mode 100644
index 08fc656..0000000
--- a/WebCore/manual-tests/inspector/resources/mutate-frame.html
+++ /dev/null
@@ -1,10 +0,0 @@
-<script>
-var count = 1;
-function run() {
- var div = document.createElement("div");
- div.textContent = "Testing " + (count++);
- document.body.appendChild(div);
-}
-
-setInterval(run, 1000);
-</script>
diff --git a/WebCore/manual-tests/inspector/resources/script-console-calls.js b/WebCore/manual-tests/inspector/resources/script-console-calls.js
deleted file mode 100644
index 9c7bc35..0000000
--- a/WebCore/manual-tests/inspector/resources/script-console-calls.js
+++ /dev/null
@@ -1,8 +0,0 @@
-console.info("Test console.info");
-console.log("Test console.log");
-console.warn("Test console.warn");
-console.error("Test console.error");
-console.time("Test console.time");
-console.timeEnd("Test console.time");
-console.count("Test console.count");
-console.assert(false, "Test console.assert");
diff --git a/WebCore/manual-tests/inspector/resources/script-error.js b/WebCore/manual-tests/inspector/resources/script-error.js
deleted file mode 100644
index c8be5ea..0000000
--- a/WebCore/manual-tests/inspector/resources/script-error.js
+++ /dev/null
@@ -1,6 +0,0 @@
-var test = document.body;
-this.will.be.an.error = 1;
-
-function test() {
- return 42;
-}
diff --git a/WebCore/manual-tests/inspector/returnEvent-crash.html b/WebCore/manual-tests/inspector/returnEvent-crash.html
deleted file mode 100644
index 5dd1119..0000000
--- a/WebCore/manual-tests/inspector/returnEvent-crash.html
+++ /dev/null
@@ -1,17 +0,0 @@
-<script>
- function test2() {
- var y = 6;
- y += 3;
- return y;
- }
-
- function test() {
- var x = 5;
- eval("test2()");
- x += 6;
- return x;
- }
-</script>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=19038">Bug 19038: Crash in JavaScriptDebugServer::returnEvent when inspecting an attached Inspector</a>.</p>
-<p>To test, open and attach the Inspector's debugger, then click the button below. If you don't crash, you have passed the test.</p>
-<button onclick="test()">click me</button>
diff --git a/WebCore/manual-tests/inspector/styled-error-bubbles-in-scripts.html b/WebCore/manual-tests/inspector/styled-error-bubbles-in-scripts.html
deleted file mode 100644
index 0049cef..0000000
--- a/WebCore/manual-tests/inspector/styled-error-bubbles-in-scripts.html
+++ /dev/null
@@ -1,6 +0,0 @@
-<script src="resources/script-error.js"></script>
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=20345">Bug 19065:
-Error bubbles are clobbered when syntax highlighting JavaScript resources</a>.</p>
-<p>To test, open the Inspector. There should be a red bubble with the number "1"
-in it next to the the only script resource in the Resources panel. Clicking the
-resource should show syntax highlighted JavaScript with a red error bubble.</p>
diff --git a/WebCore/manual-tests/inspector/webinspector-log.html b/WebCore/manual-tests/inspector/webinspector-log.html
deleted file mode 100644
index cdc5663..0000000
--- a/WebCore/manual-tests/inspector/webinspector-log.html
+++ /dev/null
@@ -1,22 +0,0 @@
-<p>Test for <a href="https://bugs.webkit.org/show_bug.cgi?id=28047">Bug 28047: add utility method to enable logging messages for inspector development</a>.</p>
-
-<ul>
-<li>Open a browser, go to any web page.
-<li>Open web inspector
-<li>Open the console panel
-<li>Open a web inspector on the web inspector
-<li>Open that inspector's console panel
-<li>In that panel, run the code:
-<pre>
- WebInspector.log("hello, world")
-</pre>
-</ul>
-
-<p>Results:
-<br>In the original inspector window, there should now be a message
-in the console with the text "hello, world". There will be a blue
-maginifying glass icon to the left of the message. Run the same
-command again, and you should see the repeat count go to 2.
-The message and repeat count are blue.
-
-