273383 - Javascript links on this page do not work if this page was reached by following a link

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Lyman Epp]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; brip1)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

The "Bowl Site Menu" links on the right side of this page work fine when this 
URL is entered in the location bar.

However, the "Bowl Site Menu" links do not work if this page is reached by 
following the link (below the Capital One Bowl logo) on this page:
http://www.iowalum.com/AthleticTours/BowlTour04.html

If this link is middle-clicked to open in a new tab, the "Bowl Site Menu" 
links on the target page will work correctly.

Reproducible: Always
Steps to Reproduce:
1. http://www.iowalum.com/AthleticTours/BowlTour04.html
2. Left-click on the link for http://www.doddsathletictours.com/iowacapone/
3. Click on links in the "Bowl Site Menu" on the right-hand side of the page.

Actual Results:  
Nothing (for the javascript links)

Expected Results:  
Page navigation should occur for all links.

Clean installation with no themes or extensions.

Comment 1

[Caio Tiago Oliveira (asrail)]

The JavScript console shows the following messages:

'Error: slave has no properties
Source file: http://www.doddsathletictours.com/iowacapone/
Line: 94'

This line change for each link.

'Error: nativeMethod.call is not a function
Source file: chrome://global/content/XPCNativeWrapper.js
Line: 90'

Clicking the scroll pane returns:
'Error: uncaught exception: permission denied to get property Window.tourpane'


So, it looks like a bad designed page instead of a Mozilla or Firefox bug.
This issue looks like a Tech Evangelism bug.

Comment 2

[Lyman Epp]

The page works if it is accessed directly. It doesn't work when accessed from a
hyperlink.

Comment 3

[Martijn Wargers (dead)]

The new opened page (in a new window) is opened on a different domain.
The link has this javascript function when clicked upon:
onClick="Lvl_targetIframe('','tourpane','home.html')

That's this function:
function Lvl_targetIframe(f,i,u){ //v1.0 4LevelWebs
 var
b=(!f)?i:f+".frames['"+i+"']",o=(eval("opener&&opener.parent."+b))?"opener.":'';
 var el=eval(o+"parent."+b);el.location=u;document.MM_returnValue=false;
}

So basically this script tries to get a property from the opener window, which
isn't allowed in Mozilla when the opener window is from a different domain.

Comment 4

[Clive Miller]

It seems to be the window.opener property which is null, even if a window has
been opened by another. A specific demonstration of it not working can be seen at:
<a href="www.pluton.co.uk/test.html">www.pluton.co.uk/test.html</a>

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.