Closed
Bug 699705
Opened 13 years ago
Closed 13 years ago
Getting a property off an array that lives on a non-native on the proto chain and has a getter that uses |this| fails
Categories
(Core :: JavaScript Engine, defect, P2)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla10
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
Attachments
(1 file)
The problem is that we use js_NativeGet and hence have to stick to native objects. This is a remaining unfixed case from bug 434837. At the time we had no way to fix, but now we do.
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #571883 -
Flags: review?(jwalden+bmo)
Assignee | ||
Updated•13 years ago
|
OS: Mac OS X → All
Priority: -- → P2
Hardware: x86 → All
Whiteboard: [need review]
Version: 9 Branch → Trunk
Updated•13 years ago
|
Attachment #571883 -
Flags: review?(jwalden+bmo) → review+
Comment 2•13 years ago
|
||
As I noted on IRC, this patch demonstrates one reason why we should make getOwnProperty, in some form, the fundamental property-get operation. Every one of these methods has to hard-code the property-delegation lookup process, and every one has to be fixed if a bug is found, as here. I started this in bug 637378 half a year ago and hit a nontrivial XBL-based snag. Perhaps we should go back and beat XBL into submission so we could move further in that direction...
Assignee | ||
Comment 3•13 years ago
|
||
Flags: in-testsuite+
Whiteboard: [need landing]
Target Milestone: --- → mozilla10
Comment 4•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•