Closed Bug 283520 Opened 20 years ago Closed 19 years ago

Context.newObject( ) methods search for constructor in incorrect scope

Categories

(Rhino Graveyard :: Core, defect)

1.6R1
x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: djgredler, Assigned: igor)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

All the Context.newObject() methods say in their JavaDocs that the scope passed
in is searched for the constructor with the specified name. However, the scope
searched is actually the top level scope for the specified scope. One or the
other is wrong!

Reproducible: Always

Steps to Reproduce:
Rhino does not supports application-level scope objects with non-null
getParentScope(). Although it may apparently work, there are many issues with
that. If you need to share scopes, use protype chain, not scope chain.

The docs should be more explicit about that, but that is a topic for another bug.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.