at your code, you need to put this at the very top:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
See if that helps.
Also, I'm almost completely ignorant of Fusebox, but that CSS link looks odd
to me. I kind of understand that in Fusebox everything is pulled in through
the index page, but I'd look at how the CSS for that actually is formatted.
If you put any <html><head><body> etc tags in the CSS page, then funny
things could happen.
-Kevin
----- Original Message -----
From: "Samuel Neff" <[EMAIL PROTECTED]>
To: "CF-Community" <[EMAIL PROTECTED]>
Sent: Thursday, October 16, 2003 11:37 AM
Subject: RE: Is Safari really prime-time ready? Do we need to consider it
supported in our apps?
> Thanks for the tip. Can you tell me how to tell what mode Mozilla is
> running on and how to switch modes? (quirks vs standard).
>
> The odd thing is that the Safari behavior is inconsistent. Sometimes it
> displays correctly and sometimes it just gives us a blank page, even
though
> HTML being sent back is exactly the same (it's always the No-Records
page).
> Same results from our dev and test servers both running CFMX6.1. Running
> the test through a trace utility didn't show anything interesting or
> different about the working vs. non-working requests.
>
> Here's the HTML for one page we're having trouble with. This HTML hasn't
> been modified in a few years (app dates back to 1998).
>
>
> <html>
> <head>
> <link rel="stylesheet"
>
href=""> > action="" type="text/css" />
> </head>
>
> <body>
>
> <div align="center" class="fieldNormalText">
> No records were found based on your search criteria.
> </div>
> <br>
> <div align="center">
> <a href=""> > src=""> > width="72" height="17" align="absmiddle" border="0" /></a>
> </div>
>
> </body>
> </html>
>
>
> Any suggestions would be appreciated.
>
> Thanks,
>
> Sam
>
> -----Original Message-----
> From: Ben Doom [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 16, 2003 10:22 AM
> To: CF-Community
> Subject: Re: Is Safari really prime-time ready? Do we need to consider it
> supported in our apps?
>
>
> If it's picking up fine in Mozilla, check to see if it's rendering in
> quirks mode or standards mode. If it's rendering in quirks mode, switch
> to standards mode and see if it still renders OK. If not, there's
> something "wrong" (by which I mean probably IE-based, and only wrong as
> compared to standards) with your code.
>
> Just an idea.
>
> --BenD
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
