153432 - Javascript call does not result in proper new window pop

Status: VERIFIED DUPLICATE of bug 146507

(Core :: DOM: Core & HTML, defect)

Description

[Jason Compton]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1a) Gecko/20020611
BuildID:    20020611

When clicking the Contact Us link near the bottom of the Gartner home page, the
expected window does not pop up.

Reproducible: Always
Steps to Reproduce:
1.Browse to www.gartner.com
2.Click on Contact Us, second row up from bottom of the page
3.See nothing happen

Actual Results:  New window fails to open.

Expected Results:  Should have opened new window with new page of contact
information.

Javascript for Navigator IS enabled. All options enabled.

Comment 1

[Christian Eyrich]

Can confirm this with 2002061712 on Windows.
Reason for this failure is Error: "uncaught exception: Permission denied to set
property Window.fullScreen" while loading utility.js.
But since I don't know JavaScript in depth I can't say what's the forbidden
thing in this function name (error doesn't occur after renaming the function to
anything else).

An other problem is the error the "if (storeNewWin)" in function
openNewAdmin(href) produces, but without the above exception this wouldn't
matter here.

Comment 2

[Phil Schwartau]

The problem is, in view-source:http://www4.gartner.com/js/utility.js,
the site authors define a function called |fullScreen|:

function fullScreen(theURL)
{
 newWin = window.open(theURL, '', 
                      'fullscreen=yes,scrollbars=auto,status=yes,menubar=yes');
 storeNewWin(newWin);
 return false;
}


This name, as all function names, enters the global JS namespace.
In the DOM, that means the |window| namespace. But there is ALREADY
a global identifier with this name: |window.fullScreen|.

That's why, when we load this site in Mozilla, we see this error
in the JavaScript Console:

           Error: uncaught exception:
           Permission denied to set property Window.fullScreen


So in Mozilla, the function fullScreen() remains undefined, and so
do all functions defined after it in the utility.js file. (Just load
the site in the Mozilla JS Debugger; you won't see any functions
appearing in the File View after the function openNewSubAdminFooter()).

That's why the "Contact Us" link fails: it depends on one of these
missing functions...

Reassigning to DOM Level 0. Should site authors be able to name
a global function "fullScreen"? 

Comment 3

[Christian Eyrich]

Phil, who defined the already existing window.fullScreen and where? Not the
sites author obviously, is it a Mozilla internal thing?
However, fullScreen is a not seldom used name for a fullScreen window function,
so to prohibit authors to use this function name seems not very wise to me.

Comment 4

[Phil Schwartau]

Christian: I'll have to let the DOM experts answer that one.
There is, (or was), a native DOM property |window.fullScreen|.

See bug 127405, "Scripts can put a window in fullscreen mode"
Looks like it used to be there, but access to it has been disabled
for security reasons...(?)

Comment 5

[Brant Gurganus]

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

Comment 6

[Phil Schwartau]

Verified Duplicate -