For some time now, I noticed that inspector no longer shows element properties. Neither standard DOM nor DOM0. Only methods and constants are shown. Test case is obvious, inspecting any element on any page and looking in the "Properties" panel, you'll see no property only methods (more than before) and constants (i.e. on node interface). I did not back-search into previous nightly to find the turning release.
I can't reproduce this behavior in ToT on Windows. 1. Right-click on the page and choose Inspect Element 2. Expand the "Properties" section 3. Click on the "Node <br> Prototype" section I see ATTRIBUTE_NODE, COMMENT_NODE, DOCUMENT_NODE, etc., listed. Is this not the case for you?
In reply to Adam: Those "ATTRIBUTE_NODE, COMMENT_NODE, DOCUMENT_NODE" are constants of node object. Not properties. On previous version, and on current Safari 3, the first block under the "properties" section lists all inherited properties, like "id, className…", standard properties or "innerHTML, offsetWIdth…" for proprietary ones. The current webkit only lists properties defined by the selected element class. This is not useful. It should : either: summarize inherited properties like before or: add as many blocks as needed to list every class it inherit, with relevant properties for this class. This is the current choice for prototypes, listing methods at each level.
This regression comes from the changeset 29174, in the file page/inspector/PropertiesSidebarPane.js http://trac.webkit.org/projects/webkit/changeset/29174 I verified that nigthly 19173 correctly displays properties.
Correction to my previous comment : I verified that nigthly 29173 correctly displays properties Also I tried to revert to the 29173 PropertiesSidebarPane.js file in current webkit. This does not work.
I rather wonder there is something wrong with __lookupGetter__(). The security risk might have been overlooked.
…and today Safari 3.1 is out with this useless properties pane while this bug is still unconfirmed. I can't believe I'm the only one using Webkit as primary dev browser. I now have to use firefox to look at properties values.
(In reply to comment #6) > …and today Safari 3.1 is out with this useless properties pane while this bug > is still unconfirmed. > I can't believe I'm the only one using Webkit as primary dev browser. I now > have to use firefox to look at properties values. Please post a specific URL or attach the HTML to a test page that demonstrates this behavior. Also, are you using Mac OS X (10.4 or 10.5?) or on Windows (XP or Vista)?
Created attachment 19870 [details] useful properties pane capture
Created attachment 19871 [details] current webkit faulty properties pane
Any url can do, this is a global recessive bug. I'm on Mac 10.5. I also confirmed this bug on another machine running 10.4. The two attachments just added are made on this 10.4 system looking at the Webkit.org home page.
I think the change in behavior may be a security fix. Not sure if it can be worked around.
I may have a fix for this, but my fix would indicate that this regressed in r30146.
Committed a fix in r31320.
Well done! Replacing utilites.js in current nightly does it.
<rdar://problem/5834227>