Safari 1.3+

J

Justin Koivisto

Does anyone know if there is a quick test to tell if Safari 1.3 (or 2.0
will suffice) is the browser that doesn't rely on the typical
navigator.* methods? For instance, there is the good 'ol document.all
test for MSIE... Looking to add Safari support to my tty editor for my cms.
 
G

Gérard Talbot

Justin Koivisto wrote :
Does anyone know if there is a quick test to tell if Safari 1.3 (or 2.0
will suffice) is the browser that doesn't rely on the typical
navigator.* methods? For instance, there is the good 'ol document.all
test for MSIE... Looking to add Safari support to my tty editor for my cms.


Developing Cross Browser/Cross Platform Pages:
Browser identification (aka "browser sniffing"): not best, not reliable
approach;
Using Object/Feature detection: best and overall most reliable
http://www.mozilla.org/docs/web-developer/upgrade_2.html#DevCrossBrowser

A Strategy That Works: Object/Feature Detecting by comp.lang.javascript
newsgroup FAQ notes
http://jibbering.com/faq/faq_notes/not_browser_detect.html#bdFD

Browser detection - No; Object detection - Yes by Peter-Paul Koch
http://www.quirksmode.org/js/support.html

Gérard
 
J

Justin Koivisto

Gérard Talbot said:
Justin Koivisto wrote :


Developing Cross Browser/Cross Platform Pages:
Browser identification (aka "browser sniffing"): not best, not reliable
approach;
Using Object/Feature detection: best and overall most reliable
http://www.mozilla.org/docs/web-developer/upgrade_2.html#DevCrossBrowser

This was my initial read quite a few months ago....
A Strategy That Works: Object/Feature Detecting by comp.lang.javascript
newsgroup FAQ notes
http://jibbering.com/faq/faq_notes/not_browser_detect.html#bdFD

Has code very similar to what I am doing on my devel version already...
Browser detection - No; Object detection - Yes by Peter-Paul Koch
http://www.quirksmode.org/js/support.html

Which is what I am looking to do...

I know I have a big rewrite ahead for my editor, but I just need a quick
fix for now, and I know that the navigator.* methods aren't going to work.

<rant>
Why is it that when I post a question to usenet that gets replies, they
quite frequently don't answer question asked?
</rant>
 
M

Matt Kruse

Justin said:
Why is it that when I post a question to usenet that gets replies,
they quite frequently don't answer question asked?

Two reasons:

1) A lot of times people asking questions don't ask the right questions, or
don't understand that there's a better way to do what they're trying to do,
etc. If posters only got their direct questions answered, they wouldn't
learn how to do things the correct way to avoid their question altogether.

2) Many trolls on usenet are know-it-alls whose purpose in life is to prove
that they know more about a topic than others by mocking their questions,
posting sarcastic questions and replies, and pointing them to information
which is way beyond what they are looking for.

Since you didn't note in your original post that you already know about
object detection and that it is the preferred way to judge browser support
for various things, a reader of this group would naturally assume you
weren't away of it and point you to resources that would guide you to a much
better way of performing your task.

If you preface a question like yours with information about why you want to
do things the 'bad' way for now, and that you know of the better long-term
solution already, you might get a response closer to what you're looking
for.

And on a side note, I have no idea what the answer to your question is. I
hate Safari :)
 
G

Gérard Talbot

Justin Koivisto a écrit :
Gérard Talbot wrote:




This was my initial read quite a few months ago....

I personally updated that document a few weeks ago, even just a few days
ago.
Has code very similar to what I am doing on my devel version already...




Which is what I am looking to do...

I know I have a big rewrite ahead for my editor, but I just need a quick
fix for now, and I know that the navigator.* methods aren't going to work.

<rant>
Why is it that when I post a question to usenet that gets replies, they
quite frequently don't answer question asked?
</rant>

I thought it was more appropriate to give you useful reading on the
issue than a specific answer to a question which may proceed from a
wrong analysis, a wrong perception of a website difficulty/issue.
There are serious chances that several ways to detect MSIE 7 will fail
because many webpages rely on poor cross-browser pages to begin with. (1)

In a few weeks from now, I'm sure this newsgroup will have questions like:
"is there a quick test to tell if IE 7 is the browser?"
And the logical answer is you do not need some sort of script trick to
detect browser and browser versions to begin with if your code relies on
object/feature detection. That is the current best available answer to
the issue of cross-browser support.

Gérard
--
remove blah to email me
(1) "we continue our testing of IE7 we continue to come across web sites
that are not expecting version 7 of the browser. Often they helpfully
suggest an upgrade to an alternative browser or to IE5 or later."
IE 7 user agent string July 13th 2005
http://blogs.msdn.com/dmassy/archive/2005/07/13/438625.aspx
On May 11th 2005, I rewrote the entire section of cross-browser
development and updated an example with a browser sniffing example which
would fail to deal with IE 7.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
474,432
Messages
2,571,680
Members
48,796
Latest member
Greg L.

Latest Threads

Top