Hi,
Thanks, as this topic caused a bit of unrest last evening. After looking in terms of a gathering in which diverse taste need accommodation, serving one vegetarian entree as an alternative is just courteous. Browser sniffing, can be used in such a manner to allow a seamless experience for non-plug in users, or wireless. Serving (1) standards based alternative, not a buffet of little hacks to please every UA.
So I look forward to adding this technique to my tool kit, as with any tool, to be called upon only when needed.
"Complexity is good, complicated is bad."
—Paolo Soleri
On Friday, June 25, 2004, at 01:35 AM, Mordechai Peller wrote:
Chris Blown wrote:
There are plenty of reasons to do so server side, log files being the most common. I use sniffing to determine whether I should serve up XHTML 1.1 or HTML 4.01.Thats _really_ bad
Browser checking is a thing of the past and should be gladly forgotten.
Something that we can all thank the web standards project for.
Is there a valid reason to do browser checking? I can't think of one...
Even client side, the use of @-rules to hide CSS from certain browsers, and for that matter, all CSS hacks, are a form of browser checking.
Also, many mobile phones use the wrong style sheet (screen instead of handheld). Browser sniffing is a way around that.
*****************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
*****************************************************
***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
