From b46442d7e2e8cccf5f9bcafb2e1e3b7cf23d424b Mon Sep 17 00:00:00 2001
From: "joi@chromium.org"
 <joi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Wed, 29 Jun 2011 02:16:06 +0000
Subject: Wholesale move of debugger sources to content.

Other references are modified only to point to the new
location. Follow-up changes will move build rules for the debugger
into content.

This adds a somewhat permissive DEPS file to
content/browser/debugger. Follow-up work will whittle that down to
zero dependencies on chrome/.

BUG=84078
TEST=existing

Review URL: http://codereview.chromium.org/7274031

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@90912 0039d316-1c4b-4281-b951-d872f2087c98
---
 .../manual_tests/console-call-line-numbers.html    |  15 +++
 .../manual_tests/debugger-exception-on-load.html   |   5 +
 .../debugger-execution-while-paused.html           |  17 ++++
 .../manual_tests/debugger-fake-workers.html        | 102 +++++++++++++++++++++
 .../debugger-pause-on-else-statements.html         |  16 ++++
 .../debugger-pause-on-for-in-statements.html       |  16 ++++
 .../debugger-pause-on-for-statements.html          |  14 +++
 .../debugger-step-on-do-while-statements.html      |  27 ++++++
 .../debugger-step-on-for-in-statements.html        |  35 +++++++
 .../debugger-step-on-for-statements.html           |  25 +++++
 .../debugger-step-on-while-statements.html         |  28 ++++++
 .../manual_tests/debugger-watch-expressions.html   |  79 ++++++++++++++++
 .../debugger/manual_tests/dom-mutation.html        |  32 +++++++
 .../debugger/manual_tests/element-styles.html      |  40 ++++++++
 .../debugger/manual_tests/error-warning-count.html |  58 ++++++++++++
 .../debugger/manual_tests/event-listeners.html     |  30 ++++++
 ...eap-profiler-test-basic-grid-functionality.html |  32 +++++++
 .../heap-profiler-test-snapshots-comparison.html   |  83 +++++++++++++++++
 .../debugger/manual_tests/highlight-nodes.html     |  23 +++++
 .../manual_tests/highlight-source-line.html        |   3 +
 .../profiler-test-basic-grid-functionality.html    |  38 ++++++++
 .../profiler-test-console-control.html             |  27 ++++++
 .../profiler-test-focus-and-exclude.html           |  71 ++++++++++++++
 .../manual_tests/profiler-test-re-opening.html     |  37 ++++++++
 .../browser/debugger/manual_tests/resources/fib.js |  20 ++++
 .../manual_tests/resources/loop-statements.js      |  22 +++++
 .../manual_tests/resources/mutate-frame-2.html     |  12 +++
 .../manual_tests/resources/mutate-frame.html       |  10 ++
 .../debugger/manual_tests/resources/primes.js      |  13 +++
 .../manual_tests/resources/script-console-calls.js |   8 ++
 .../manual_tests/resources/worker-primes.js        |  10 ++
 31 files changed, 948 insertions(+)
 create mode 100644 content/browser/debugger/manual_tests/console-call-line-numbers.html
 create mode 100644 content/browser/debugger/manual_tests/debugger-exception-on-load.html
 create mode 100644 content/browser/debugger/manual_tests/debugger-execution-while-paused.html
 create mode 100644 content/browser/debugger/manual_tests/debugger-fake-workers.html
 create mode 100644 content/browser/debugger/manual_tests/debugger-pause-on-else-statements.html
 create mode 100644 content/browser/debugger/manual_tests/debugger-pause-on-for-in-statements.html
 create mode 100644 content/browser/debugger/manual_tests/debugger-pause-on-for-statements.html
 create mode 100644 content/browser/debugger/manual_tests/debugger-step-on-do-while-statements.html
 create mode 100644 content/browser/debugger/manual_tests/debugger-step-on-for-in-statements.html
 create mode 100644 content/browser/debugger/manual_tests/debugger-step-on-for-statements.html
 create mode 100644 content/browser/debugger/manual_tests/debugger-step-on-while-statements.html
 create mode 100644 content/browser/debugger/manual_tests/debugger-watch-expressions.html
 create mode 100644 content/browser/debugger/manual_tests/dom-mutation.html
 create mode 100644 content/browser/debugger/manual_tests/element-styles.html
 create mode 100644 content/browser/debugger/manual_tests/error-warning-count.html
 create mode 100644 content/browser/debugger/manual_tests/event-listeners.html
 create mode 100644 content/browser/debugger/manual_tests/heap-profiler-test-basic-grid-functionality.html
 create mode 100644 content/browser/debugger/manual_tests/heap-profiler-test-snapshots-comparison.html
 create mode 100644 content/browser/debugger/manual_tests/highlight-nodes.html
 create mode 100644 content/browser/debugger/manual_tests/highlight-source-line.html
 create mode 100644 content/browser/debugger/manual_tests/profiler-test-basic-grid-functionality.html
 create mode 100644 content/browser/debugger/manual_tests/profiler-test-console-control.html
 create mode 100644 content/browser/debugger/manual_tests/profiler-test-focus-and-exclude.html
 create mode 100644 content/browser/debugger/manual_tests/profiler-test-re-opening.html
 create mode 100644 content/browser/debugger/manual_tests/resources/fib.js
 create mode 100644 content/browser/debugger/manual_tests/resources/loop-statements.js
 create mode 100644 content/browser/debugger/manual_tests/resources/mutate-frame-2.html
 create mode 100644 content/browser/debugger/manual_tests/resources/mutate-frame.html
 create mode 100644 content/browser/debugger/manual_tests/resources/primes.js
 create mode 100644 content/browser/debugger/manual_tests/resources/script-console-calls.js
 create mode 100644 content/browser/debugger/manual_tests/resources/worker-primes.js

(limited to 'content/browser/debugger/manual_tests')

diff --git a/content/browser/debugger/manual_tests/console-call-line-numbers.html b/content/browser/debugger/manual_tests/console-call-line-numbers.html
new file mode 100644
index 0000000..98bb918
--- /dev/null
+++ b/content/browser/debugger/manual_tests/console-call-line-numbers.html
@@ -0,0 +1,15 @@
+<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>
+
+<p>To test, open the DevTools's Console (Ctrl+Shift+J) 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 panel file list and each individual resource view.</p>
diff --git a/content/browser/debugger/manual_tests/debugger-exception-on-load.html b/content/browser/debugger/manual_tests/debugger-exception-on-load.html
new file mode 100644
index 0000000..ef2384f
--- /dev/null
+++ b/content/browser/debugger/manual_tests/debugger-exception-on-load.html
@@ -0,0 +1,5 @@
+<script>
+debugger; // You should see this code and execution line in the Scripts panel. Click Resume (Play/Pause button to the right).
+</script>
+
+<p>To test, open the DevTools (Ctrl+Shift+I) and reload the page. You should see this file and execution line in the Scripts panel.</p>
diff --git a/content/browser/debugger/manual_tests/debugger-execution-while-paused.html b/content/browser/debugger/manual_tests/debugger-execution-while-paused.html
new file mode 100644
index 0000000..f33abea
--- /dev/null
+++ b/content/browser/debugger/manual_tests/debugger-execution-while-paused.html
@@ -0,0 +1,17 @@
+<script>
+function stepOne()
+{
+    console.log(1);
+}
+
+function stepTwo()
+{
+    alert("Test failed. The second button event still fired.");
+}
+</script>
+
+<p>To test, open the DevTools (Ctrl+Shift+I) and reload the page. 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. Continue script.</p>
+<button onclick="stepOne()">Step One</button><br><br>
+<button onclick="stepTwo()">Step Two</button>
diff --git a/content/browser/debugger/manual_tests/debugger-fake-workers.html b/content/browser/debugger/manual_tests/debugger-fake-workers.html
new file mode 100644
index 0000000..6a7cb03
--- /dev/null
+++ b/content/browser/debugger/manual_tests/debugger-fake-workers.html
@@ -0,0 +1,102 @@
+<html>
+<body onload="onLoad()">
+<script>
+
+function log(message) {
+  var div = document.createElement('div');
+  div.innerText = message;
+  document.getElementById('console').appendChild(div);
+}
+
+function strike(id) {
+  document.getElementById(id).style.textDecoration = "line-through"
+}
+
+function onLoad() {
+  if (!Worker.prototype.postMessage) { // fake workers
+      strike('s1');
+      strike('s2');
+      log('[using fake workers]');
+  } else {
+      log('[using real workers]');
+  }
+}
+
+var primeWorker;
+var invalidWorker;
+var count;
+var timer;
+
+function startWorkers() {
+  startButton.disabled = true;
+
+  primeWorker = new Worker('resources/worker-primes.js');                         	
+  primeWorker.onmessage = onMessage;
+  primeWorker.onerror = onError;
+  primeWorker.postMessage(2);
+  count = 3;
+
+  timer = setInterval(onTimer, 1000);
+  try {
+    invalidWorker = new Worker('non-existent-worker.js');
+  } catch(e) {
+  }
+  log('Started worker');
+}
+
+function onTimer() {
+  primeWorker.postMessage(count);
+  count+=2;
+}
+
+function onMessage(event) {
+  if (event.data[1]) {
+    log(event.data[0]);
+    if (event.data[0] === 5)
+      strike('s6');
+  }
+}
+
+function onError(event) {
+  log('Error in worker: ' + event.message);
+  strike('s8');
+}
+
+function causeError() {
+  primeWorker.postMessage('forty two');
+}
+
+function stopWorker() {
+  log('Stopping worker...');
+  if (timer) {
+    clearInterval(timer);
+    timer = 0;
+  }
+  primeWorker.terminate();
+  startButton.disabled = false;
+}
+
+</script>
+
+<h1>Tests debugging of HTML5 Workers</h1>
+
+<ol>
+
+<li id="s1">Open DevTools, Scripts Panel; Tick Debug on Workers sidebar.</li>
+<li id="s2">Reload the page.</li>
+<li id="s3"><button onclick="startWorkers()" id="startButton">Start Worker</button></li>
+<li id="s4">Observe 2 workers appear in the worker sidebar pane (including non-existent-worker.js)"</li>
+<li id="s5">Observe worker-primes.js and primes.js appear in scripts drop-down box.</li>
+<li id="s6">Assure primes are being logged to test console below.</li>
+<li id="s7">Set a breakpoint on one of worker scripts, assure it's hit.</li>
+<li id="s8">Try causing an error in worker, observe it's logged in DevTools console and in test console below.
+  <button onclick="causeError()">Cause Error</button>
+<li id="s9"><button onclick="stopWorker()">Stop Worker</button></li>
+
+</ol>
+
+<div id="console" style="font-family: courier; background-color: black; color: green; width: 80em; height: 25em; overflow: scroll">
+</div>
+
+</body>
+</html>
diff --git a/content/browser/debugger/manual_tests/debugger-pause-on-else-statements.html b/content/browser/debugger/manual_tests/debugger-pause-on-else-statements.html
new file mode 100644
index 0000000..3c80a43
--- /dev/null
+++ b/content/browser/debugger/manual_tests/debugger-pause-on-else-statements.html
@@ -0,0 +1,16 @@
+<script>
+function test()
+{
+    debugger;
+}
+
+if (false)
+    debugger; // This should not be hit.
+else
+    test();
+</script>
+
+<p>To test, open the DevTools (Ctrl+Shift+I) and reload the page. When the debugger breaks, select the (anonymous function) node
+in the call stack, you should see the execution line on the call to test().</p>
+<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/content/browser/debugger/manual_tests/debugger-pause-on-for-in-statements.html b/content/browser/debugger/manual_tests/debugger-pause-on-for-in-statements.html
new file mode 100644
index 0000000..79f7983
--- /dev/null
+++ b/content/browser/debugger/manual_tests/debugger-pause-on-for-in-statements.html
@@ -0,0 +1,16 @@
+<script>
+function test()
+{
+    debugger;
+}
+
+var object = { test: 1 };
+
+for (var property in object)
+    test();
+</script>
+
+<p>To test, open the DevTools (Ctrl+Shift+I) and reload the page. When the debugger breaks, select
+the (anonymous function) 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/content/browser/debugger/manual_tests/debugger-pause-on-for-statements.html b/content/browser/debugger/manual_tests/debugger-pause-on-for-statements.html
new file mode 100644
index 0000000..1a9e274
--- /dev/null
+++ b/content/browser/debugger/manual_tests/debugger-pause-on-for-statements.html
@@ -0,0 +1,14 @@
+<script>
+function test()
+{
+    debugger;
+}
+
+for (var i = 0; i < 1; ++i)
+    test();
+</script>
+
+<p>To test, open the DevTools (Ctrl+Shift+I) and reload the page. When the debugger breaks, select the
+(anonymous function) node in the call stack, you should see the execution line on the call to test().</p>
+<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/content/browser/debugger/manual_tests/debugger-step-on-do-while-statements.html b/content/browser/debugger/manual_tests/debugger-step-on-do-while-statements.html
new file mode 100644
index 0000000..f60dd6a
--- /dev/null
+++ b/content/browser/debugger/manual_tests/debugger-step-on-do-while-statements.html
@@ -0,0 +1,27 @@
+<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>
+<p>To test, open the DevTools (Ctrl+Shift+I) and reload the page.
+<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.</p>
+<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 into'. Debugger should step inside each 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/content/browser/debugger/manual_tests/debugger-step-on-for-in-statements.html b/content/browser/debugger/manual_tests/debugger-step-on-for-in-statements.html
new file mode 100644
index 0000000..e360394
--- /dev/null
+++ b/content/browser/debugger/manual_tests/debugger-step-on-for-in-statements.html
@@ -0,0 +1,35 @@
+<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>
+<p>To test, open the DevTools (Ctrl+Shift+I) and reload the page.
+<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.</p>
+<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/content/browser/debugger/manual_tests/debugger-step-on-for-statements.html b/content/browser/debugger/manual_tests/debugger-step-on-for-statements.html
new file mode 100644
index 0000000..75289e5f
--- /dev/null
+++ b/content/browser/debugger/manual_tests/debugger-step-on-for-statements.html
@@ -0,0 +1,25 @@
+<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>
+<p>To test, open the DevTools (Ctrl+Shift+I) and reload the page.
+<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.</p>
+<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>
+function.<br>
diff --git a/content/browser/debugger/manual_tests/debugger-step-on-while-statements.html b/content/browser/debugger/manual_tests/debugger-step-on-while-statements.html
new file mode 100644
index 0000000..7967172
--- /dev/null
+++ b/content/browser/debugger/manual_tests/debugger-step-on-while-statements.html
@@ -0,0 +1,28 @@
+<script src="resources/loop-statements.js"></script>
+<script>            
+function runWhile()
+{
+    /* place breakpoint on next line and click continue */ debugger;
+    while (condition()) {
+        statement();
+        increment();
+    }
+}
+
+</script>
+<p>To test, open the DevTools (Ctrl+Shift+I) and reload the page.
+<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.</p>
+<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>
+step over to the beggingin of the while loop again. Click 'Step into'. Debugger should step into
+the 'condition' function.<br>
diff --git a/content/browser/debugger/manual_tests/debugger-watch-expressions.html b/content/browser/debugger/manual_tests/debugger-watch-expressions.html
new file mode 100644
index 0000000..a2e9258
--- /dev/null
+++ b/content/browser/debugger/manual_tests/debugger-watch-expressions.html
@@ -0,0 +1,79 @@
+<p>Test for watched expression</p>
+
+<p>To begin test, open DevTools, go the Scripts Panel 
+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 be 
+<code>Object</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: d is not defined</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.
+
+</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/content/browser/debugger/manual_tests/dom-mutation.html b/content/browser/debugger/manual_tests/dom-mutation.html
new file mode 100644
index 0000000..a03b03c
--- /dev/null
+++ b/content/browser/debugger/manual_tests/dom-mutation.html
@@ -0,0 +1,32 @@
+<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>To begin test, open DevTools, Elements Panel 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.
+Expand DOM nodes in the Elements Panel to see new nodes appearing in the list live.</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/content/browser/debugger/manual_tests/element-styles.html b/content/browser/debugger/manual_tests/element-styles.html
new file mode 100644
index 0000000..cb33919
--- /dev/null
+++ b/content/browser/debugger/manual_tests/element-styles.html
@@ -0,0 +1,40 @@
+<style>
+.classTest {
+  -webkit-transform:skew(-10deg,-3deg);
+  color: green;
+  background: #CCC;
+  border: 2px solid blue;
+  padding: 5px 6px 7px 8px;
+}
+</style>
+<p>To begin test, open DevTools, select the Elements panel. Expand the Styles pane in the sidebar.</p>
+<ul>
+  <li>Choose the <b>&lt;div class="classTest"...></b> element in the DOM tree.
+You should see the following element styles in the ".classTest (inline stylesheet)" section:
+<pre>
+  -webkit-transform:skew(-10deg,-3deg);
+  color: green;
+  background: #CCC;
+  border: 2px solid blue;
+  padding: 5px 6px 7px 8px;
+</pre>
+  While changing all the property values, you should see corresponding live page changes.
+  <li>Double click the "-webkit-transform" rule and place the cursor at the second argument (-3deg).
+  <li>Press Up/Down keys do see the argument value change in 1.0 steps (0.1 steps in the [-1; 1] range).
+  <li>Press Shift+Up/Down keys to see the argument value change in 10.0 steps.
+  <li>Press Alt(Cmd)+Up/Downkeys to see the argument value change in 0.1 steps (1.0 steps in the [-1; 1] range).
+  <li>Move the mouse pointer within the section to display checkboxes to the right of the property values.
+  <li>Click the checkboxes to disable/enable the corresponding style properties and observe the page changes.
+You can disable the "-webkit-transform" property if the element overlaps the instructions.
+  <li>Double-click the "background" rule and alter the color to "#FFF". The text background should turn white.
+  <li>Double-click the "color" rule and alter the color to "black". The text background should turn black.
+  <li>Expand the "padding" shorthand property using the arrow at the left. You should see the following
+property values beneath: padding-top: 5px; padding-right: 6px; padding-bottom: 7px; padding-left: 8px;
+  <li>In the "Styles" pane titlebar click the gear button and choose "New Style Rule". In the editbox that appears, type:
+<pre>
+font-family: monospace;
+</pre>
+      The font of the test string should alter to a monospaced one.
+</ul>
+
+<div class="classTest">CLASS_TEST CLASS_TEST CLASS_TEST CLASS_TEST CLASS_TEST CLASS_TEST CLASS_TEST</div>
\ No newline at end of file
diff --git a/content/browser/debugger/manual_tests/error-warning-count.html b/content/browser/debugger/manual_tests/error-warning-count.html
new file mode 100644
index 0000000..3296742
--- /dev/null
+++ b/content/browser/debugger/manual_tests/error-warning-count.html
@@ -0,0 +1,58 @@
+<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>To begin test, open DevTools 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/content/browser/debugger/manual_tests/event-listeners.html b/content/browser/debugger/manual_tests/event-listeners.html
new file mode 100644
index 0000000..4dff96d
--- /dev/null
+++ b/content/browser/debugger/manual_tests/event-listeners.html
@@ -0,0 +1,30 @@
+<head>
+  <script>
+    function attachListener() {
+      document.getElementById("target").addEventListener("click", listenerFunction, true);
+      document.getElementById("targetParent").addEventListener("click", listenerFunctionParent, true);
+    }
+    function listenerFunctionParent(event) {
+      event.target.textContent = "event handled";
+    }
+    function listenerFunction(event) {
+      event.target.textContent = "event handled";
+    }
+  </script>
+</head>
+<body onload="attachListener()">
+<div id="targetParent">
+  <div id="target"></div>
+</div>
+<p>To begin test, open DevTools, select the Elements panel. Expand the Event Listeners
+pane in the sidebar.
+<ul>
+  <li>Choose the <b>&lt;div id="targetParent"...></b> element.
+You should see the "click" section in the Event Listeners pane. Expand the section to see
+the "listenerFunctionParent" function (at "div#targetParent") under it.
+  <li>Expand the targetParent node in the tree and choose the <b>&lt;div id="target"...></b>
+element. You should see the "click" section in the Event Listeners pane. Expand the section
+to see two functions, "listenerFunctionParent" (at "div#targetParent") and
+"listenerFunction" (at "div#target") under it.
+</ul>
+</body>
diff --git a/content/browser/debugger/manual_tests/heap-profiler-test-basic-grid-functionality.html b/content/browser/debugger/manual_tests/heap-profiler-test-basic-grid-functionality.html
new file mode 100644
index 0000000..5aa4555
--- /dev/null
+++ b/content/browser/debugger/manual_tests/heap-profiler-test-basic-grid-functionality.html
@@ -0,0 +1,32 @@
+<html>
+  <head>
+    <title>Heap Profiler: basic grid functionality test</title>
+  </head>
+  <body>
+    This is the test for basic functionality of heap snapshot view grid.
+    <br>
+    <br>
+    To use this test:
+    <ul>
+      <li>load file in the browser;
+      <li>open DevTools (Ctrl+Shift+I on Win/Linux, Command+Option+I on Mac);
+      <li>go to 'Profiles' page;
+      <li>press 'Take heap snapshot' button
+        (eye icon on the left side of status bar);
+    </ul>
+    <br>
+    On the left pane under 'Heap snapshots' section, an item called
+    'Snapshot 1' must appear, and a grid with snapshot data must
+    appear on the right. Now test the following functionality in the grid:
+    <ul>
+      <li>change sorting order in each column by clicking on its header;
+      <li>resize each column;
+      <li>toggle between showing absolute times and percents
+        (button with percent sign on the status bar);
+      <li>double-click on numbers in 'Count' and
+        'Size' columns to toggle between times and percents for
+        this column only;
+      <li>expanding and collapsing tree nodes.
+    </ul>
+  </body>
+</html>
diff --git a/content/browser/debugger/manual_tests/heap-profiler-test-snapshots-comparison.html b/content/browser/debugger/manual_tests/heap-profiler-test-snapshots-comparison.html
new file mode 100644
index 0000000..3a419d4e
--- /dev/null
+++ b/content/browser/debugger/manual_tests/heap-profiler-test-snapshots-comparison.html
@@ -0,0 +1,83 @@
+<html>
+  <head>
+    <title>Heap Profiler: heap snapshots comparison test</title>
+    <script type="text/javascript">
+      var aHolder = [], bHolder = [], cHolder = [], dHolder = [];
+
+      function A(x) {
+        this.x = x;
+      }
+
+      function B(x) {
+        this.x = x;
+      }
+
+      function C() {}
+
+      var i;
+      for (i = 0; i < 100; ++i) {
+        var b = new B('hello');
+        bHolder.push(b);
+        aHolder.push(new A(b));
+        b = null;
+      }
+      for (i = 0; i < 25; ++i) {
+        cHolder.push(new C());
+      }
+
+      function D() {}
+
+      function changeStuff() {
+        if (aHolder.length > 0) {
+          aHolder.splice(aHolder.length - 25, 25);
+        }
+        for (i = 0; i < 25; ++i) {
+          bHolder.push(new B('hello'));
+        }
+        cHolder = [];
+        for (i = 0; i < 25; ++i) {
+          dHolder.push(new D());
+        }
+      }
+    </script>
+  </head>
+  <body>
+    This is the test for heap snapshot comparison functionality.
+    <br>
+    <br>
+    To use this test:
+    <ul>
+      <li>load file in the browser;
+      <li>open DevTools (Ctrl+Shift+I on Win/Linux, Command+Option+I on Mac);
+      <li>go to 'Profiles' page;
+      <li>press 'Take heap snapshot' button
+        (eye icon on the left side of the status bar);
+      <li>press
+        <input type="button" name="changeStuff" value="this button" onclick="changeStuff()" />;
+      <li>press 'Take heap snapshot' button again;
+    </ul>
+    <br>
+    On the left pane under 'Heap snapshots' section, items called
+    'Snapshot 1' and 'Snapshot 2' must appear. Select 'Snapshot 2'. 
+    Ensure that absolute values are shown (not percents).
+    <br>
+    <br>
+    TEST 1. Verify the following:
+    <ul>
+      <li>the value in '+/- Count' column for 'A' must be '-25';
+      <li>after expanding 'A' item, the value in '+/- Count' column
+        for 'Array' child entry must also be '-25';
+      <li>the value in '+/- Count' column for 'B' must be '+25';
+      <li>after expanding 'B' item, the value in '+/- Count' column
+        for 'Array' child entry must also be '+25'; the value for 'A'
+        child must be '-25';
+    </ul>
+    <br>
+    TEST 2. Change display to percent view (using the percent button on the
+    status bar). Verify the following:
+    <ul>
+      <li>values in '+/- Count' and '+/- Size' columns for 'C' must be 'deleted';
+      <li>values in '+/- Count' and '+/- Size' columns for 'D' must be 'new';
+    </ul>
+  </body>
+</html>
diff --git a/content/browser/debugger/manual_tests/highlight-nodes.html b/content/browser/debugger/manual_tests/highlight-nodes.html
new file mode 100644
index 0000000..cbeae6f
--- /dev/null
+++ b/content/browser/debugger/manual_tests/highlight-nodes.html
@@ -0,0 +1,23 @@
+<style>
+.skewed {
+  -webkit-transform:skew(-5deg,-5deg);
+}
+</style>
+<p>This page has basic tests of node highlighting in the inspected page. To test, load this page, open the DevTools 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/content/browser/debugger/manual_tests/highlight-source-line.html b/content/browser/debugger/manual_tests/highlight-source-line.html
new file mode 100644
index 0000000..a56ed97
--- /dev/null
+++ b/content/browser/debugger/manual_tests/highlight-source-line.html
@@ -0,0 +1,3 @@
+<p>To test, open the DevTools and reload this page. Then open the 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/content/browser/debugger/manual_tests/profiler-test-basic-grid-functionality.html b/content/browser/debugger/manual_tests/profiler-test-basic-grid-functionality.html
new file mode 100644
index 0000000..1841715
--- /dev/null
+++ b/content/browser/debugger/manual_tests/profiler-test-basic-grid-functionality.html
@@ -0,0 +1,38 @@
+<html>
+  <head>
+    <title>Profiler: basic grid functionality test</title>
+    <script type="text/javascript" src="resources/fib.js"></script>
+  </head>
+  <body onload="run_fib()">
+    This test runs a simple looped computation to test basic
+    functionality of profile view grid.
+    <br>
+    <br>
+    To use this test:
+    <ul>
+      <li>load file in the browser;
+      <li>open DevTools (Ctrl+Shift+I on Win/Linux, Command+Option+I on Mac);
+      <li>go to 'Profiles' page;
+      <li>press 'Start profiling' button
+        (gray dot on the left side of status bar);
+      <li>wait for 5 seconds;
+      <li>press 'Stop profiling' button
+        (red dot on the left side of status bar);
+    </ul>
+    <br>
+    On the left pane under 'CPU profiles' section, an item called
+    'Profile 1' must appear, and a grid with profile data must
+    appear on the right. Now test the following functionality in the grid:
+    <ul>
+      <li>change sorting order in each column by clicking on its header;
+      <li>resize each column;
+      <li>toggle between showing absolute times and percents
+        (button with percent sign on the status bar);
+      <li>double-click on numbers in 'Self' and
+        'Total' columns to toggle between times and percents for
+        this column only;
+      <li>expanding and collapsing tree nodes;
+      <li>toggling between "Heavy" and "Tree" views.
+    </ul>
+  </body>
+</html>
diff --git a/content/browser/debugger/manual_tests/profiler-test-console-control.html b/content/browser/debugger/manual_tests/profiler-test-console-control.html
new file mode 100644
index 0000000..4f2001a
--- /dev/null
+++ b/content/browser/debugger/manual_tests/profiler-test-console-control.html
@@ -0,0 +1,27 @@
+<html>
+  <head>
+    <title>Profiler: test console controlling of CPU profiling</title>
+    <script type="text/javascript" src="resources/fib.js"></script>
+    <script type="text/javascript">
+      function profile_fib() {
+        console.profile();
+        run_fib();
+        window.setTimeout('console.profileEnd();', 5000);
+      }
+    </script>
+  </head>
+  <body onload="profile_fib()">
+    This test runs and profiles a simple looped computation.
+    <br>
+    <br>
+    TEST
+    <ul>
+      <li>load file in the browser;
+      <li>open DevTools with console (Ctrl+Shift+I on Win/Linux, Command+Option+I on Mac);
+      <li>go to 'Profiles' page;
+      <li>observe that 'Profile 1' item has appeared under 'CPU profiles' section;
+      <li>check for presence of 'eternal_fib' entry in the profile view.
+    </ul>
+    <br>
+  </body>
+</html>
diff --git a/content/browser/debugger/manual_tests/profiler-test-focus-and-exclude.html b/content/browser/debugger/manual_tests/profiler-test-focus-and-exclude.html
new file mode 100644
index 0000000..d33e3eb
--- /dev/null
+++ b/content/browser/debugger/manual_tests/profiler-test-focus-and-exclude.html
@@ -0,0 +1,71 @@
+<html>
+  <head>
+    <title>Profiler: focusing and exclusion test</title>
+    <script type="text/javascript" src="resources/fib.js"></script>
+  </head>
+  <body onload="run_fib()">
+    This test runs a simple looped computation to test focusing and
+    exclusion functionality of profile view grid.
+    <br>
+    <br>
+    To use this test:
+    <ul>
+      <li>load file in the browser;
+      <li>open DevTools (Ctrl+Shift+I on Win/Linux, Command+Option+I on Mac);
+      <li>go to 'Profiles' page;
+      <li>press 'Start profiling' button
+        (gray dot on the left side of status bar);
+      <li>wait for 5 seconds;
+      <li>press 'Stop profiling' button
+        (red dot on the left side of status bar);
+    </ul>
+    <br>
+    On the left pane under 'CPU profiles' section, an item called
+    'Profile 1' must appear, and a grid with profile data must
+    appear on the right. Now test the following functionality in the grid:
+    <br>
+    TEST 1:
+    <ul>
+      <li>select 'eternal_fib' function entry (without expanding it),
+        press 'Focus
+        on selected function' button (eye on the right of the status bar);
+      <li>ensure that only 'eternal_fib' function and its children are 
+        left in the tree, and 'Total' column for the function shows
+        '100%' value;
+      <li>expand 'eternal_fib' function node;
+      <li>press 'Restore all functions' button;
+      <li>verify that the value in 'Total' column is less than 100%;
+      <li>verify that 'eternal_fib' function node is can still be
+        collapsed and expanded back;
+    </ul>
+    <br>
+    TEST 2:
+    <ul>
+      <li>expand two levels of 'Script:' node, select the second-level
+        node;
+      <li>repeat the same steps for the selected node (in this case, immediate
+        parent nodes of the focused node must also remain visible after
+        focusing);
+    </ul>
+    <br>
+    TEST 3:
+    <ul>
+      <li>by expanding 'Script:' node, make sure that at least 3
+        'eternal_fib' function nodes are visible;
+      <li>select any of 'eternal_fib' nodes and press
+        'Exclude selected function' (cross) button on the status bar;
+      <li>verify that all 'eternal_fib' nodes are no more visible;
+      <li>expand more 'Script:' node levels, verify that no new
+        'eternal_fib' nodes appear with expansion;
+      <li>press 'Restore all functions' button;
+      <li>verify that 'eternal_fib' nodes are now visible;
+    </ul>
+    <br>
+    TESTS 4 and 5:
+    <br>
+    Now switch to 'Tree (Top Down)' view and repeat testing steps.
+    For the 'Exclude selected function' function test, use 
+    'Script:' function node, as 'eternal_fib' has only
+    one entry in this view.
+  </body>
+</html>
diff --git a/content/browser/debugger/manual_tests/profiler-test-re-opening.html b/content/browser/debugger/manual_tests/profiler-test-re-opening.html
new file mode 100644
index 0000000..a615afa
--- /dev/null
+++ b/content/browser/debugger/manual_tests/profiler-test-re-opening.html
@@ -0,0 +1,37 @@
+<html>
+  <head>
+    <title>Profiler: test profiles population on DevTools re-opening</title>
+    <script type="text/javascript" src="resources/fib.js"></script>
+    <script type="text/javascript">
+      function profile_fib() {
+        console.profile();
+        run_fib();
+        window.setTimeout('console.profileEnd();', 5000);
+      }
+    </script>
+  </head>
+  <body onload="profile_fib()">
+    This test runs and profiles a simple looped computation.
+    <br>
+    <br>
+    TEST
+    <ul>
+      <li>load file in the browser;
+      <li>open DevTools with console (Ctrl+Shift+I on Win/Linux, Command+Option+I on Mac);
+      <li>go to 'Profiles' page;
+      <li>observe that 'Profile 1' item has appeared under 'CPU profiles' section;
+      <li>reload page in browser;
+      <li>observe that after 5 seconds, 'Profile 2' item has appeared under
+        'CPU profiles' section;
+      <li>take a couple of heap snapshots by pressing 'Take heap snapshot.'
+        button (eye icon on the left of the status bar);
+      <li>close DevTools window;
+      <li>re-open DevTools window;
+      <li>go to 'Profiles' page;
+      <li>verify that CPU profiles 'Profile 1' and 'Profile 2', and heap profiles
+        taken previously are restored back (<b>Warning:</b> it may take some
+        time to re-process them).
+    </ul>
+    <br>
+  </body>
+</html>
diff --git a/content/browser/debugger/manual_tests/resources/fib.js b/content/browser/debugger/manual_tests/resources/fib.js
new file mode 100644
index 0000000..804c866
--- /dev/null
+++ b/content/browser/debugger/manual_tests/resources/fib.js
@@ -0,0 +1,20 @@
+function fib(n) {
+  return n < 2 ? 1 : fib(n - 1) + fib(n - 2);
+}
+
+function eternal_fib() {
+  var started = Date.now();
+  while(true) {
+    fib(20);
+    // Make page responsive by making a break every 100 ms.
+    if (Date.now() - started >= 100) {
+      setTimeout(eternal_fib, 0);
+      return;
+    }
+  }
+}
+
+function run_fib() {
+  // Let the page do initial rendering, then go.
+  setTimeout(eternal_fib, 200);
+}
diff --git a/content/browser/debugger/manual_tests/resources/loop-statements.js b/content/browser/debugger/manual_tests/resources/loop-statements.js
new file mode 100644
index 0000000..cbb4e0d
--- /dev/null
+++ b/content/browser/debugger/manual_tests/resources/loop-statements.js
@@ -0,0 +1,22 @@
+var i;
+var a;
+
+function initialize()
+{
+    i = false;
+}
+
+function condition()
+{
+    return !i;
+}
+
+function increment()
+{
+    i = !i;
+}
+
+function statement()
+{
+    a = i;
+}
diff --git a/content/browser/debugger/manual_tests/resources/mutate-frame-2.html b/content/browser/debugger/manual_tests/resources/mutate-frame-2.html
new file mode 100644
index 0000000..9d413b9
--- /dev/null
+++ b/content/browser/debugger/manual_tests/resources/mutate-frame-2.html
@@ -0,0 +1,12 @@
+<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/content/browser/debugger/manual_tests/resources/mutate-frame.html b/content/browser/debugger/manual_tests/resources/mutate-frame.html
new file mode 100644
index 0000000..08fc656
--- /dev/null
+++ b/content/browser/debugger/manual_tests/resources/mutate-frame.html
@@ -0,0 +1,10 @@
+<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/content/browser/debugger/manual_tests/resources/primes.js b/content/browser/debugger/manual_tests/resources/primes.js
new file mode 100644
index 0000000..64d38dc
--- /dev/null
+++ b/content/browser/debugger/manual_tests/resources/primes.js
@@ -0,0 +1,13 @@
+function Primes() {
+  this.primes_ = {};
+}
+
+Primes.prototype.test = function(p) {
+  for (var divisor in this.primes_) {
+    if (p % divisor === 0) return false;
+    if (divisor * divisor > p)
+      break;
+  }
+  this.primes_[p] = 1;
+  return true;
+}
diff --git a/content/browser/debugger/manual_tests/resources/script-console-calls.js b/content/browser/debugger/manual_tests/resources/script-console-calls.js
new file mode 100644
index 0000000..9c7bc35
--- /dev/null
+++ b/content/browser/debugger/manual_tests/resources/script-console-calls.js
@@ -0,0 +1,8 @@
+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/content/browser/debugger/manual_tests/resources/worker-primes.js b/content/browser/debugger/manual_tests/resources/worker-primes.js
new file mode 100644
index 0000000..8be021f
--- /dev/null
+++ b/content/browser/debugger/manual_tests/resources/worker-primes.js
@@ -0,0 +1,10 @@
+importScripts('primes.js');
+
+var primes = new Primes();
+
+onmessage = function(event) {
+  var p = event.data;
+  if (p != parseInt(p))
+    throw 'invalid argument';
+  postMessage([p, primes.test(p)]);
+}
-- 
cgit v1.1