The JavaScript Debugger module API lets you customize the way you create the debug version of a document. You need to create a debugger module if you want to make the JavaScript Debugger work with a browser other than Netscape Navigator and Internet Explorer, which supports. You can create a module for a specialized purpose, such as counting the number of JavaScript statements that are used in a particular document.
Note: Currently only SCRIPT tags and event handlers are parsed for instrumentation. There are some other ways to use JavaScript in HTML documents, such as JavaScript URLs, JavaScript entities, and conditional comments, but these methods are not currently supported.
The JavaScript Debugger module API functions are significant only in the context of module files. Specifically, automatically calls the getStepInstrument() function if it is defined in the module file. For any other extension file, a function named getStepInstrument() acts as a user-defined function; you must call it explicitly.
Unlike working with functions in the main JavaScript API, you are responsible for writing the body of each function and returning a value, if required, for the modules. For the functions in the main API, you call and pass arguments, and generates return values, if any. For the JavaScript Debugger modules, calls the functions and passes arguments to them, and you generate return values, if any.
All the JavaScript Debugger module functions are optional. If a function is not defined, nothing happens when calls it.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117