js/src/jit-test/tests/debug/Debugger-onNewGlobalObject-08.js@ac0c01689b40 (annotated)
js/src/jit-test/tests/debug/Debugger-onNewGlobalObject-08.js
Thu, 15 Jan 2015 15:59:08 +0100
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Thu, 15 Jan 2015 15:59:08 +0100
- branch
- TOR_BUG_9701
- changeset 10
- ac0c01689b40
- permissions
- -rw-r--r--
Implement a real Private Browsing Mode condition by changing the API/ABI;
This solves Tor bug #9701, complying with disk avoidance documented in
https://www.torproject.org/projects/torbrowser/design/#disk-avoidance.
| michael@0 | 1 | // Creating a global within an onNewGlobalObject handler causes a recursive handler invocation. |
| michael@0 | 2 | // |
| michael@0 | 3 | // This isn't really desirable behavior, as presumably a global created while a |
| michael@0 | 4 | // handler is running is one the debugger is creating for its own purposes and |
| michael@0 | 5 | // should not be observed, but if this behavior changes, we sure want to know. |
| michael@0 | 6 | |
| michael@0 | 7 | var dbg = new Debugger; |
| michael@0 | 8 | var log; |
| michael@0 | 9 | var depth; |
| michael@0 | 10 | |
| michael@0 | 11 | dbg.onNewGlobalObject = function (global) { |
| michael@0 | 12 | log += '('; depth++; |
| michael@0 | 13 | |
| michael@0 | 14 | assertEq(global.seen, undefined); |
| michael@0 | 15 | global.seen = true; |
| michael@0 | 16 | |
| michael@0 | 17 | if (depth < 3) |
| michael@0 | 18 | newGlobal(); |
| michael@0 | 19 | |
| michael@0 | 20 | log += ')'; depth--; |
| michael@0 | 21 | }; |
| michael@0 | 22 | |
| michael@0 | 23 | log = ''; |
| michael@0 | 24 | depth = 0; |
| michael@0 | 25 | newGlobal(); |
| michael@0 | 26 | assertEq(log, '((()))'); |
