Closed
Bug 924067
Opened 11 years ago
Closed 7 years ago
Add a "user methods/properties" filter to the Object Inspector of the Web Developer Tools
Categories
(DevTools :: Console, enhancement, P3)
DevTools
Console
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: regagnon, Unassigned)
Details
- Go to a web page. - Open the Web Developer Console. - Type "window" in the console to see the content of the global variable. - Open the Object Inspector by clicking on the console output. - Try to understand which global properties and methods were defined by the page author. (not native, or by the browser) - Loose patience We can use a text field to filter the object inspector. But there is no way to filter only methods or properties defined by the page author. Firebug offers many filters when inspecting an object. By default, it seems to only display the "user methods/properties .
Comment 1•11 years ago
|
||
Assuming you're referring to enumerable vs. non-enumerable properties on an object, the Variables View already exposes this functionality (via the enumVisible and nonEnumVisible setters). The webconsole does not expose these settings like the debugger. Marking this as a Web Console bug.
Status: UNCONFIRMED → NEW
Component: Developer Tools: Object Inspector → Developer Tools: Console
Ever confirmed: true
OS: Mac OS X → All
Hardware: x86 → All
Updated•11 years ago
|
Priority: -- → P3
Updated•7 years ago
|
Severity: normal → enhancement
Comment 2•7 years ago
|
||
I think this can be closed. If you go to `data:text/html,<script>window.foo = "bar";console.dir(window);</script>` and open the console, you'll see that the window object is expanded, and only show a few nodes : ``` ▼ Window | foo: "bar" | ▶︎ [default properties] | ▶︎ __proto__: WindowPrototype { … } ``` All the native window properties are put in a [default properties] bucket, and only the non-native properties are directly visible (and the proto).
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•