Closed Bug 418983 Opened 18 years ago Closed 18 years ago

Scoping issues with window.__defineGetter__()

Categories

(Core :: XPConnect, defect)

Product:
Core
Component:
XPConnect
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 369259

People

(Reporter: mikeperry.unused, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12 It appears that using __defineGetter__ to override certain elements off window can have some bizarre side effects. For instance, doing a __defineGetter__ for the history and screen objects seems to make them disappear from the implicit window scope, though they can be accessed still by explicitly saying window.history and window.screen. Reproducible: Always
Component: General → XPConnect
Product: Firefox → Core
QA Contact: general → xpconnect
This was fixed on trunk by bug 369259. I sort of doubt this is a big enough issue that we'll port that fix to the 1.8 branch, but the fix will show up in Firefox 3.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.