Title: Message
|
Mmm...
but that's OK because it's Netscape 6 not Netscape 4 - that css bug is only in
one of the 4.x versions I think. Along with all the other stupid Netscape bugs.
I find that Netscape 6, while not as easy to work with as Mozilla, is much much
better than it used to be.
K.
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
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 :)
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 -----
In my environment the baseref is
mike.work.net
request.stylesroot is
styles
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.
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?
LeeBB
----- Original Message -----
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="javascript:void(0);"></script>
<cfif
not request.suppress.billboard>
<cfinclude
template="#request.scriptroot#/dsp_billboard.cfm">
</cfif>
<cfinclude
template="#request.scriptroot#/security.cfm">
</head>
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
==^================================================================
|
