I’m in the middle of redesigning my company’s homepage, and apparently when they made it there were some issues with IE4, layers and re-sizing. They weren’t too sure what they were though, as it was made by an outside agency. All we are sure of is that we have to run a detection, and load up one page if the browser is IE4, and another if it isn’t. :-\
Anyone have any ideas on what these problems could be? And I guess, more importantly, how on earth to get round them? :q:
When I was a webmaster, way back when, we had to do this because Netscape tended to reload the entire page when resized. My site was heavily dynamic, so reloading took an amazing amount of time (broadband was not very common in residential use).:-\
As far as IE4, it handles layers quite differently than Netscape, and the positioning of those layers could really make it ugly in the wrong browser:)
As to the work-around, I don’t know:(
that is why I don’t do a lot in layers:-\ but then again, with the stats I have just seen, less than 10% of your visitors will be on something other than IE 5-6…=)
Yeah, according to our stats the number of people actually using IE4 is very low, but because we are a huge business, we have to cater for these people. It’s part of the design brief that will never change.
As it is I’m having a hard time convincing people that we should be designing for 1024 screen res as an optimum…
Well IE handles layers using div tags with a z-index setting.
Netscape handles layers using actual layer tags. They can be an absolute pain.
My way of detecting browsing isn’t actually very advanced, but it seems to work for me…
<SCRIPT LANGUAGE="JavaScript">
<!--
if (document.all) { // IF IE
//SCRIPT HERE
}
else if (document.layers) { //IF NETSCAPE LESS THAN 6
//SCRIPT HERE
}
else if (document.getElementById) { //IF NETSCAPE 6+
//SCRIPT HERE
};
}
// -->
</SCRIPT>
Ok, I just typed that up here, so I am not 100% positive it will work, but I have a 95% good feeling it will.
Yeah, that’s basically what we’ve got at the moment, a couple of if statements and that to find out then run the right page.
Must be the div tags that are doing it then. Since I’ve been asked to redesign the front page, I’m planning on giving them the boot completely, which should eliminate the need for two separate pages.
Yeah, I am not sure Netscape supports div tags, and if it does, it definitely doesn’t support the z-index feature.
If you are going to be using layers, you definitely have to have 2 different versions, or a way to call certain features on the page through Javascript so that it will work in either or, but still be the same page.
Well you can have a look at the current site homepage at www.churchill.com. It’s all in a frameset so no-one can view the source, but it’s built using a multitude of layers, and it’s the tickertape in the right corner that causes the problems I’m led to believe.
They’ve also said they want the whole thing, script, graphics and code, reduced down to 40K.
It looks to me that you could take your site into Dreamweaver and convert layers to tables (overlapping layers can be troublesome). Then, take your ticker tape gizmo and trash it, replace it with Flash! Woooohooo!
It’s yet another part of the corporate design brief. Since this company aims their insurance at middle-aged people and upwards, they have to take into account that these peeps won’t neccessarily have the latest versions, plugins or anything. We have to assume they’re running the worst possible setup imaginable. Has to work on Netscape and IE, PC and Mac. No applets, no Flash, not fancy ColdFusion or anything like that. JavaScript and HTML is all we’re allowed to use, and pages must be under 40K for everything.
Yeah, I know what you mean. When I had to rebuild my schools website they also wanted me to rebuild my schools College Office webpage (grrr, I hated my school!), anywho, I opened the file and it was so painful to look at! They used some really old HTML code.
I had to rebuild it, and make it easy to understand and edit, because the college office demanded that they be the ones to update it (fine by me), well I rebuild it, added comment tags galore to help them edit, made it simple as pie, I looked at it after their first update…THEY REDID EVERYTHING I DID - IN THEIR PRIMITIVE CODE!!!
WHAT WAS THE POINT OF MAKING ME REDO IT!!! (bastards!)
Well, I was pissed, now I am straying from the convo…so I will stop talking about it.
When building a site, I use whatever knowledge I have and make a page that works in both IE and NS (my current website excluded, that was just an experiment).