The default bug view has changed. See this FAQ.

wrappedJSObject hides "next" property

RESOLVED FIXED

Status

()

Core
XPConnect
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: Honza, Assigned: mrbkap)

Tracking

1.9.2 Branch
x86
Windows XP
Points:
---
Bug Flags:
blocking1.9.2 -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [firebug-p2][3.6.x])

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
One reported problem in Firebug
http://code.google.com/p/fbug/issues/detail?id=2580

...says that an object's property labeled "next" is not visible in the DOM panel.

After digging into the problem I have found that if a JS object defined on a page eg:

var a = {a:1, b:2, next:3};

... is accessed from chrome using wrappedJSObject, the "next" property is not visible when iterating properties using for-in loop. 

Test case here:
http://getfirebug.com/tests/content/dom/2580/issue2580.html

Firebug 1.5b8 here:
http://getfirebug.com/releases/firebug/1.5X/

Honza
(Reporter)

Updated

7 years ago
Whiteboard: [firebug-p2]
(Assignee)

Updated

7 years ago
Assignee: nobody → mrbkap
(Assignee)

Comment 1

7 years ago
Created attachment 418736 [details] [diff] [review]
Fix

By adding the 'next' function after we grab the snapshot of the iterator's properties, we avoid this.
Attachment #418736 - Flags: review?(jst)

Comment 2

7 years ago
Requesting blocking to get this evaluated for risk and on some list to get in a release
Flags: blocking1.9.2?
Can someone please respond to comment 2? I'm guessing that this is not a blocker and a good target for a 3.6.x release, so marking in the whiteboard with that tag.
Whiteboard: [firebug-p2] → [firebug-p2][3.6.x]
Blake caught me on IRC and said that this was low-risk and low-impact enough that we could take it on the branch after we ship. Not blocking, but marked for branch update attention.
Flags: blocking1.9.2? → blocking1.9.2-

Updated

7 years ago
Attachment #418736 - Flags: review?(jst) → review+
(Assignee)

Comment 5

7 years ago
http://hg.mozilla.org/mozilla-central/rev/050abb8ffcd7
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.