Yup. I've found that making your HTML be compliant with "HTML 4.01 Transitional" and validating it through the W3C Validator service really helps with the compatibility issues. You can make the same content look fine in Netscape 4.x, IE and the new Gecko engine they're using in Netscape 6/AOL.
see: www.dtdns.com I just spent most of the day yesterday playing with the HTML and running it through the validator until it checked out ok. A few tweaks later and it renders in all of the browsers ok. Now to test in Opera, though I don't think it will cause any problems. -Justin Scott, DtDNS Admin PS: For the nitpicky, the whole site is not yet Fusebox or W3C compliant, but it's getting there ;) ----- Original Message ----- From: "Shannon Hicks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 19, 2002 10:19 AM Subject: RE: Strange but True Yeah, except for the fact that Netscape is about to take a very large chunk of the market share back from IE... The next version of AOL will have the newest Netscape browser in it instead of IE. Ouch. Shan -----Original Message----- From: Kay Smoljak [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 9:13 AM To: [EMAIL PROTECTED] Subject: RE: Strange but True I actually thought that the netscape bug was that it couldn't find css files in subdirs... if you put the css in the same dir as the page it should work fine. Maybe we should just kill netscape :) -----Original Message----- From: Lee Borkman [mailto:[EMAIL PROTECTED]] Sent: Friday, 19 April 2002 9:08 PM To: [EMAIL PROTECTED] Subject: Re: Strange but True What if you set request.stylesroot to "/styles" instead of "styles"? Netscape is obviously interpreting "styles" as the domain, and trying to wrap "www." and ".com" around it. Perhaps a leading "/" will discourage it...? Anyway, it looks like it can be worked around. As I mentioned, I tend to CFINCLUDE my stylesheets to get them working consistently with Netscape. An unsatisfactory solution, but we all have feet of clay ;-) See you later, LeeBB ----- Original Message ----- From: [EMAIL PROTECTED] In my environment the baseref is mike.work.net request.stylesroot is styles the url I use is http://mike.work.net and the version of Netscrape is 4.73...the lowest common denominator I have to develop for (fighting tooth and nail by the way). I hard coded the directory and this strange behavior has stopped. I like to hedge my bets, but you are usually more right than you are wrong so I gambled...and as usual you were correct. It seems that Netscape does not like the paths like that. Of course, the site still does not work...but it looks like those will be yet more issues on my plate to deal with. -----Original Message----- From: Lee Borkman [mailto:[EMAIL PROTECTED]] Okay, So you're using SES? * What's the value of #request.basehref# and of #request.stylesroot#? * And what's the URL of this page? * What version of Netscape? I think I have heard of an old bug in Netscape that ignore BASE HREF for Javascript and CSS files, or something like that. If that's the case, then you might have to workaround by actually CFINCLUDE-ing the stylesheet. Works fine, but you lose tha advantage that cacheing the stylesheet would give. Whatcha reckon? <http://bjork.net/index.cfm/fuseaction/content.display/page/donations.htm> LeeBB ----- Original Message ----- From: [EMAIL PROTECTED] Well...that's the rub...there is no generated output I can view. Netscape just spins its wheels. Figuring that since nothing has been output, it could very well be what's happening in the <head> tag of my main layout file. Hope this leads you to the right conclusion...I don't have much hair left. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>Health Level Seven</title> <BASE HREF="<cfoutput>#request.basehref#</cfoutput>"/> <link rel="STYLESHEET" type="text/css" href="<cfoutput>#request.stylesroot#</cfoutput>/main.css"> <link rel="STYLESHEET" type="text/css" href="<cfoutput>#request.stylesroot#</cfoutput>/toc.css"> <link rel="STYLESHEET" type="text/css" href="<cfoutput>#request.stylesroot#</cfoutput>/forms.css"> <script language="JavaScript" type="text/javascript" src="<cfoutput>#request.scriptroot#</cfoutput>/common.js"></script> <cfif not request.suppress.billboard> <cfinclude template="#request.scriptroot#/dsp_billboard.cfm"> </cfif> <cfinclude template="#request.scriptroot#/security.cfm"> </head> -----Original Message----- From: Lee Borkman [mailto:[EMAIL PROTECTED]] Hi Mike, Can we see the HTML source of the page that changes to http://www.styles.com/main.css ? I have a sneaking suspicion... ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
