summaryrefslogtreecommitdiffstats
path: root/chrome/browser/debugger/manual_tests/debugger-pause-on-for-in-statements.html
diff options
context:
space:
mode:
Diffstat (limited to 'chrome/browser/debugger/manual_tests/debugger-pause-on-for-in-statements.html')
-rw-r--r--chrome/browser/debugger/manual_tests/debugger-pause-on-for-in-statements.html16
1 files changed, 16 insertions, 0 deletions
diff --git a/chrome/browser/debugger/manual_tests/debugger-pause-on-for-in-statements.html b/chrome/browser/debugger/manual_tests/debugger-pause-on-for-in-statements.html
new file mode 100644
index 0000000..79f7983
--- /dev/null
+++ b/chrome/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.