831724 - Variables View: [object undefined] for Window when inspecting raw objects

Status: RESOLVED FIXED

(DevTools :: Debugger, defect, P2)

Description

[Mihai Sucan [:msucan]]

If you try to inspect the Window object with the Variables View, using the rawObject approach, you get [object undefined] for the window property, for |self| and for other objects.

It seems vview does not correctly determine the class for some objects.

After a bit of investigation I saw the problem is in getGrip(). You might want to use WebConsoleUtils.getObjectClassName() to determine the class name - this is something reusable from the Web Console property panel. If you use that for the |class| grip property, things should be fine.

Comment 1

[Victor Porof [:vporof][:vp]]

(In reply to Mihai Sucan [:msucan] from comment #0)
> 
> After a bit of investigation I saw the problem is in getGrip(). You might
> want to use WebConsoleUtils.getObjectClassName() to determine the class name
> - this is something reusable from the Web Console property panel. If you use
> that for the |class| grip property, things should be fine.

Excellent, thanks for digging this up!

Comment 2

[Victor Porof [:vporof][:vp]]

Attachment: v1

Simply using getObjectClassName made the test fail, because it expected class names to start with an uppercase letter.

Mihai, something unrelated to this patch: REGEX_MATCH_FUNCTION_NAME doesn't seem to match neither
> function() {}
nor
> function () {}

Comment 3

[Mihai Sucan [:msucan]]

Comment on attachment 703817 [details] [diff] [review]
v1

Patch looks good. Also tested it with my patches for bugs 783499 and 808370.

Please test that the WCU change doesn't break existing web console tests, otherwise r+.

Comment 4

[Victor Porof [:vporof][:vp]]

(In reply to Mihai Sucan [:msucan] from comment #3)
> Comment on attachment 703817 [details] [diff] [review]
> v1
> 
> Patch looks good. Also tested it with my patches for bugs 783499 and 808370.
> 
> Please test that the WCU change doesn't break existing web console tests,
> otherwise r+.

Already did, everything seems fine.
Thanks!

Comment 5

[Mihai Sucan [:msucan]]

Victor, thanks for your patch!

(In reply to Victor Porof [:vp] from comment #2)
> Mihai, something unrelated to this patch: REGEX_MATCH_FUNCTION_NAME doesn't
> seem to match neither
> > function() {}
> nor
> > function () {}

The regex comment is confusing in WCU.jsm. The purpose of the regex is to match/find the function name, even if it doesn't have a name. In the case when it doesn't have a name, it doesn't match anything (no name = nothing to match). Those examples are meant to show what I tested against.

Since you modify WCU, maybe you can make the comment less confusing? Thanks!

Comment 6

[Victor Porof [:vporof][:vp]]

https://hg.mozilla.org/integration/fx-team/rev/c201b9d74699

Comment 7

[Victor Porof [:vporof][:vp]]

Somehow this made a webconsole test unhappy (test_object_actor.html). I don't understand why I didn't catch this previously. Fixed: https://hg.mozilla.org/integration/fx-team/rev/1bc9ef10c261

Comment 8

[Tim Taubert [:ttaubert] (inactive)]

https://hg.mozilla.org/mozilla-central/rev/c201b9d74699