I'm sure you have already done this, but just in case: Make sure to
check your browser sniffing code to allow for Safari. Previously I only
determined the difference between IE and Netscape by searching for
'MSIE' in the agent. Worked great when there were only two stipulations.
On the CF side I use something like this:
<!---- browser detect ---->
<cfif find('MSIE', CGI.HTTP_USER_AGENT) OR find('Safari',
CGI.HTTP_USER_AGENT)>
<cfset browser = "ie">
<cfelse>
<cfset browser="net">
</cfif>
Adam Wayne Lehman
Web Systems Developer
Johns Hopkins Bloomberg School of Public Health
Distance Education Division
-----Original Message-----
From: Bruce Sorge [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 3:02 PM
To: CF-Talk
Subject: RE: Safari Issues
They are using the latest. I have confirmed that.
_____
From: David Fafard [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 1:48 PM
To: CF-Talk
Subject: Re: Safari Issues
Make sure it's the lastest build of Safari.
Safari 1.1 ??? If memory serves me, I recall an
issue with _javascript_ values not being passed
with older versions.
HTH,
Dave
----- Original Message -----
From: Bruce Sorge
To: CF-Talk
Sent: Tuesday, November 25, 2003 2:38 PM
Subject: RE: Safari Issues
Since I cannot use session or client variables on this site (that is a
whole
other discussion), I have to use a frame set, and then I use form
and/or
URL
variables for "session" state. The biggest problem is that some form
variables or URL variables are not being passed. At first I thought
that
maybe the users were disabling JS, which I am using for form field
validation, but then I remember that I have other checks in the system
to
trap these errors for user who disabled JS. Besides, one part that I
have
on
the site uses the two select related tags, so they have to enable JS
to
make
that work or they will never be able to register. So I am at a loss as
to
what could be causing these issues. At first I was not concerned, but
since
M$ has announced there will be no new upgrades to the MAC version of
IE,
and
Apple has come out with Safari, it is a big enough problem that I have
to
start being concerned.
Thanks,
Bruce
_____
From: Adam Wayne Lehman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 1:03 PM
To: CF-Talk
Subject: RE: Safari Issues
A good rule of thumb I've found is that Safari closely resembles IE's
_javascript_/DOM. If it works on IE, it usually works on safari.
What type of errors are you getting from Safari clients?
Adam Wayne Lehman
Web Systems Developer
Johns Hopkins Bloomberg School of Public Health
Distance Education Division
-----Original Message-----
From: Kevin Graeme [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 1:34 PM
To: CF-Talk
Subject: Re: Safari Issues
The only things I've seen are a few CSS quirks and the obvious lack of
ActiveX capability. I haven't spent a whole lot of time at it though.
-Kevin
----- Original Message -----
From: "Bruce Sorge" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Tuesday, November 25, 2003 12:05 PM
Subject: Safari Issues
> Has anyone had any problems with their sites from users that are
using
the
> Safari browser? I am getting several errors a day from Safari users,
but
> when I try to duplicate them with a powerbook I have access to, I
cannot
get
> them to occur. Is there anything different about that browser than
IE
and
> Netscape?
>
>
>
> Thanks,
>
>
>
> Bruce
>
>
>
_____
_____
_____
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
