Forum Moderators: open
It works fine in all the browsers (FF, IE5.01, IE5.5, IE 6), but Opera throws a wobbly. The page loads but sans the footer. BUT as soon as I hover over the menu, (which is also an include, remember) and the first menu drops down, Voila! - the footer pops up too.
Duuhh?
The footer is static html containing the XHTML validator images. The menu is some nested ul li construct fashioned after the sons of suckerfish dropdown menu. It formats purely with CSS and uses a few lines of JavaScript to force the a:hover pseudoclass down IE's throat.
In the html code, the div that calls the footer include is positioned before the div that calls the menu include.
Now, for this particular instance I don't much care if the few Opera browsers see the footer but the behaviour is definitely strange and I worry what will happen to other includes.
Anyone come across that before?
Narrowing down: Seems that the footer pop-up problem only occurs when the page is longer than the Opera window. Pages that fit into the available space will show their footer straight away. Pages where I have to scroll to see the footer only display it after I have triggered the drop down menu.
strrrrange
teylyn
And second, have you validated the final page source code?
W3C Validator - HTML [validator.w3.org]
W3C Validator - CSS [jigsaw.w3.org]
<off topic - the "owner edit" button has a relatively
short timer on it. We vary it from time to time, but no
matter what, it always time out relatively quickly.>
It's not enough of an issue to be a worry, and it doesn't happen with all IIS servers. Tthat's why I suspect some default configuration that can be changed. But it happens quite often, even on major sites that are hosted on IIS.
Note: the above is from memory, I'm struggling to find the article/documentation that will back this up...
However, is this really the cause of your problem? If once the page is loaded (but the footer is invisible), can you view the source code and see whether the markup for the footer is present? If so, then the problem is more likely to do with hide/show visibility in the Javascript than anything else.
I will experiment a bit more and see if the phenomenon persists if I remove all javascript to do with the includes. But these tests will have to wait a bit because I'm now off work for 10 days
HAPPY HOLIDAYS to you all.
cheers
teylyn