Closed Bug 576449 Opened 14 years ago Closed 12 years ago

Make non-enumerable property iteration on window objects work correctly

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 807222
Tracking Flags:
Tracking Status
blocking2.0 --- -

People

(Reporter: Waldo, Unassigned)

Details

Right now, the same code handles all-iteration as enumerable-only-iteration, so I think Object.getOwnPropertyNames(window) will give you lies if you've defined "interesting" properties on window, mostly because my eyes were starting to glaze over from looking at baroque XPConnect/DOM code and thus I punted (but also because I wanted to get a mostly-working first cut in rather than wait for absolute perfection).  The code currently uses JS_NewPropertyIterator and JS_NextProperty, and I'm not aware of another iteration-object-returning protocol that can be fed an |enumerateAll| argument, but at worst it shouldn't be hard to add one.
Doesn't seem critical to fix for Firefox 4, if you disagree please justify and reopen.
blocking2.0: ? → -
No longer blocks: es5
Patch in bug 807222.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.