Subj : Re: Problem with links showing from previously hidden layer
To   : netscape.public.mozilla.jseng,netscape.public.mozilla.dom
From : Martin Honnen
Date : Wed Jan 26 2005 06:13 pm

Crosspost and followup-to netscape.public.mozilla.dom as this doesn't 
belong in jseng.

danb wrote:

> The site in question is my design portfolio page
> 
> www.dib.co.uk

I thought Dan Brown makes big bucks writing novels and me buying them, 
now he comes here as a freelance web developer -:)

> The main function of the page is based on a script from Bratta.com from
> 2001, written by Michael van Ouwerkerk, called PageSlideFade

> Everything works fine except for the following on Mozilla browsers (i
> have NN6 and Firefox1):
> 
> - the links on the left navigation show/hide the content layers, which
> can be scrolled etc. Fine.
> - If the links on the left were labelled 1 to 5 and you activate each
> in turn (ie 12345) then fine. However in Mozilla if you go "backwards"
> in order, eg click link 3 then 2, the correct div is shown BUT the
> links dont work - in fact the "hotspots" are retained from the previous
> (now hidden) layer - ie the link is not visible but the pointer cursor
> becomes a "hand" where the link would be in the previously shown layer
> (3 in the example above).
> 
> Can anyone help or set me in the right direction? 

Start with the JavaScript console, it throws
   Error: overview is not defined
all over the place when using that page so it is likely that the script 
you use is simply not working properly with Mozilla.
Those links have
activate(1); SLC(overview,'__overview *'); SLC(skills,'__skills'); 
SLC(egs,'__examples'); SLC(url,'__older URLs'); 
SLC(contact,'__contact'); return false;
meaning the activate call works in Mozilla but then the first SLC call 
throws an error and the other SLC calls are not done then after the 
error. That is not necessarily causing the problem but a way to start.

It is hard to tell what goes wrong besides that with all that convoluted 
code, I would start by using DOM inspector to look at the computed CSS 
values of those divs, probably they are sitting on top of each other.

-- 

	Martin Honnen
	http://JavaScript.FAQTs.com/

.