[thelist] Speaking of detecting: howto detect Javascript on/o ff?

Ryan Finley RyanF at SonicFoundry.com
Wed Mar 14 11:19:45 CST 2001

I'm going to have to disagree on this.

Any form verification should be done both client-side and server-side.  It
is better from the user's perspective to know about problems without waiting
for the server to respond.  It is better from an overtaxed server's
perspective to take some load off.

My website requires 4.0 browsers and above with javascript.  It is a
reasonable expectation to require javascript.

By the way, the following code will check for javascript:

<noscript><meta HTTP-EQUIV="refresh" CONTENT="0;

	Ryan Finley
	President - SurveyMonkey.com

-----Original Message-----
From: Tony Collen [mailto:manero at yossman.com]
Sent: Wednesday, March 14, 2001 11:18 AM
To: thelist at lists.evolt.org
Subject: Re: [thelist] Speaking of detecting: howto detect Javascript

On Wed, 14 Mar 2001, Martin Kuplens-Ewart wrote:

> Umm, that sounds like the only feasible way to do so... unless you can
> get your site design to work so that it doesn't really matter if you
> have javascript on or not... then you wouldn't need to. :P

I try to avoid using javascript wherever possible.

<tip author="Tony Collen (manero at yossman.com)" type="Saving Hassles With
Save yourself the hassle of debugging javascript by not using it in the
first place! Save your client development costs and save yourself from
ripping your hair out! If the functionality of your site depends on a lot
of programming and you're using javascript, you should probably use
something server-side.

Anthony Collen
manero at yossman.com

For unsubscribe and other options, including
the Tip Harvester and archive of TheList go to:
http://lists.evolt.org Workers of the Web, evolt ! 

More information about the thelist mailing list