Unable to expand "defaultView" JavaScript Object when inspecting Chrome document

RESOLVED FIXED

Status

defect
RESOLVED FIXED
12 years ago
11 years ago

People

(Reporter: bugs, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a8) Gecko/2007091216 GranParadiso/3.0a8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a8) Gecko/2007091216 GranParadiso/3.0a

The "defaultView" JavaScript Object doesn't display any children when trying to inspect the Chrome document.

Clicking on the outline icon changes it back and forth between "+" and "-", but it never expands and never displays any children.

Other properties at the same level work as expected, e.g. "documentElement".

"defaultView" does, in fact, contain child properties.  This can be confirmed by right-clicking on it and choosing "Evaluate JavaScript".

Reproducible: Always

Steps to Reproduce:
1. Start Firefox / Gran Paradiso.
2. Open Tools, DOM Inspector.
3. From DOMi, choose File, Inspect Chrome Document, then choose any of the main browser windows.  Address should show as "chrome://browser/content/browser.xul".
4. Select "Object - JavaScript" object from the drop-down in the right panel.
5. Find the "defaultView" child of "Subject", and attempt to expand it by clicking on the "+".
Actual Results:  
The outline icon changes to a "-", but it does not expand, and no children are displayed.

Expected Results:  
The outline should expand, displaying the children of "defaultView".

To verify that "defaultView" does, in fact, contain child properties, right-click on it, choose "Evaluate JavaScript", and evaluate the following code:

var vals=[]; for(var val in target){vals.push(val);} alert(vals);
Reporter

Comment 1

11 years ago
Marking as "fixed" as this is now working in the "DOM Inspector 2.0.0" posted at https://addons.mozilla.org/en-US/firefox/addon/6622.

(See also: bug 339229 and bug 398285).
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.