297471 - Javascript bug: wrong scope resolve

Status: RESOLVED DUPLICATE of bug 290774

(Core :: JavaScript Engine, defect)

Description

[Doeke Zanstra]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Within the code below, the function call "toLiteral" from within the function
test is resolved to Object.prototype.toLiteral (via the global window object),
instead of the expected global function toLiteral (window.toLiteral). It seems
there is a problem with scope resolution...

Reproducible: Always

Steps to Reproduce:
function toLiteral() {
  alert('expected');
}
Object.prototype.toLiteral=function() {
  alert('actual');
}
function test() {
	function subfunc() { alert('not important'); }
	toLiteral();
}
test();
Actual Results:  
output: 'actual'

Expected Results:  
output: 'expected'

-This happens on both FireFox Mac and Windows
-IE and Safari behave as expected
-When the sub function "subfunc" is omitted, you get the expected result
-When the body of subfunc is empty, you get the expected result as well. Empty like:
  function subfunc() { ; }
 or
  function subfunc() { void 0; }

Comment 1

[Steve England [:stevee]]

Reporter, could you try with firefox 1.1alpha (deer park) from
http://www.mozilla.org/projects/firefox/
and report back as to whether this still happens? thanks!

Comment 2

[Erik Fabert]

*** This bug has been marked as a duplicate of 290774 ***