116286 - ECMA 262 vs Web Developer JS Debugger views

Status: RESOLVED FIXED

(Other Applications Graveyard :: Venkman JS Debugger, enhancement)

Description

[Bob Clary [:bc] (inactive)]

Proposal: Include differing debugger views for the full ECMA specification and
for Web Developers.

The current implementation of Venkman shows the structure of the JS Engine/JS
Objects, etc in a 1-1 fashion with the ECMA 262 Specification. I believe that
this is a very important view of the JavaScript in a web page however it is
difficult to understand for normal web developers who are used to other
interactive debuggers such as MS' script debugger for IE where the internals of
JS are hidden from view.

For example, a Web Developer view of an object might include all
properties/methods that are available via following the scope resolution through
the prototype chain.

There are other possible improvements in the interface for Web Developers as
well. For example, the current view of loaded scripts includes many from the
chrome itself which are not always of interest for web developers. Reducing the
list of loaded scripts to those loaded by a web page would help a web developer
focus only on the scripts which belong to them.
 
Exposing the global object (window) using a tree widget for particular urls
would also be of great use to Web Developers.

Comment 1

[Robert Ginda]

fixed on branch

Comment 2

[Robert Ginda]

Mass marking bugs that were Fixed On Branch as fixed, because the branch has
landed.  If you believe this bug is not fixed, please reopen it.