OLD | NEW |
(Empty) | |
| 1 <script> |
| 2 var myObj = {test : 1}; |
| 3 function getObject() |
| 4 { |
| 5 return myObj; |
| 6 } |
| 7 |
| 8 function statement() { |
| 9 ; |
| 10 } |
| 11 |
| 12 function runForIn() |
| 13 { |
| 14 /* place breakpoint on next line and click continue */ debugger; |
| 15 for (var property in getObject()) |
| 16 statement(); |
| 17 } |
| 18 |
| 19 </script> |
| 20 <p>To test, open the DevTools (Ctrl+Shift+I) and reload the page. |
| 21 <br><br> |
| 22 Before running the tests please perform the following: |
| 23 Make sure the execution is not paused in the debugger.<br> |
| 24 Click the button and when the debugger breaks, set a breakpoint on the first lin
e in the loop |
| 25 (as indicated by the comment), and click continue.<br> |
| 26 The debugger should stop at the beggining of the loop.<br> |
| 27 The above actions should be performed before <b>each</b> of the following tests.
</p> |
| 28 <br><br> |
| 29 <input type="button" value="run for-in" onclick="runForIn()"/> |
| 30 <br><br> |
| 31 TEST 1: Click 'continue'. Execution should continue without stopping on the loop
breakpoint again.<br> |
| 32 TEST 2: Click 'Step over'. Debugger should step inside the loop to the next stat
ement line.<br> |
| 33 TEST 3: Click 'Step into'. Debugger should step into 'getObject' function.<br> |
| 34 TEST 4: 'Step over' to the statement line and then 'Step over' again. Debugger s
hould pause on |
| 35 the for-in loop again.<br> |
OLD | NEW |