W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2001

Re: What is the meaning of the DOM ECMAScript binding?

From: Neil Laurance <neil_laurance@yahoo.co.uk>
Date: Fri, 9 Nov 2001 14:39:00 +0000 (GMT)
Message-ID: <20011109143900.45355.qmail@web20710.mail.yahoo.com>
To: Jim Ley <jim@jibbering.com>, www-dom@w3.org
--- Jim Ley <jim@jibbering.com> wrote:
> > >getBrowserType();  // some function to determine browser type based on
> > >navigator object
> 
> Which is an utterly prepostrous idea that leads to nothing but errors,
> and severe barriers of entry to new browser, who either have to spoof
> their user agent string (as Opera does.) or not have support for legacy
> content.  Please do not promote this stupid technique and complain to
> anyone who does, object detection is the appropriate method, it's more
> reliable now and supports future browsers which browser detection
> doesn't.

Jim. Could you elucidate what you mean by 'object detection'. I am not familiar
with this term. I am all for browser-neutral code, but my my example was merely
to illustrate that that we're not all out of a job and can continue to code, no
matter what the objects are named by a vendor :). And in most cases the vendors
use the same convention.

Cheers, Neil

=====
+44 7866 462220           (mobile)
neil_laurance@yahoo.co.uk (mobile)
neil_laurance@adc.com     (work)

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
Received on Friday, 9 November 2001 09:39:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:55 GMT