DevTools: rename debugger/ to devtools/, move DevTools files into content/renderer/devtools.

content/browser/debugger/manual_tests/debugger-step-on-for-statements.html

Index: content/browser/debugger/manual_tests/debugger-step-on-for-statements.html
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
deleted file mode 100644
index 75289e5fac022db40fd33b00b259f3d9970c671a..0000000000000000000000000000000000000000
--- a/content/browser/debugger/manual_tests/debugger-step-on-for-statements.html
+++ /dev/null
@@ -1,25 +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>
-<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>