Closed Bug 410540 Opened 17 years ago Closed 6 years ago

JS_NewPropertyIterator is confused by faux-native object ops

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: shaver, Unassigned)

Details

JS_NewPropertyIterator assumes that OBJ_IS_NATIVE indicates that all properties are stored in sprops (and also that the scope is already mutated).  This foils use on array objects which have their own object ops and enumeration protocol, but use js_NewObjectMap.
(In reply to comment #0)
> array objects which have their own object ops and enumeration protocol,

I should say: _possible_future_ Array objects, such as in bug 322889.
Assignee: general → nobody
JS_NewPropertyIterator is no longer present, therefore closing this bug as INCOMPLETE.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.