well, it's like fixing IE6 bugs. i mostly double-code functions like
form-checks that are
done pre-posting in javascript, to be checked again on server side
again for the case
javascript is turned off.

if you can't "double-code" some functions make sure the most important
work without
javascript, too. seperate necessary functions and effects you've done.
in most cases
it's no problem if some effects don't work, but make sure basic
functions like form-validations
or whatever you call basic-functionality on your project works with
javascript disabled.

on the other hand (really depends on your project) it's ok inform the
user that he has to turn
on javascript to make the site work.

i guess it's a matter of taste. i remember sites warning the user if
he used an old browser,
or sites that alert users that "this site is optimized for <insert
browser name> here". i prefer
sites that make use of standards and work on (nearly) all browsers.

turn off javascript, visit some sites you think are "state-of-art" and
see how they handle it :)

imho: have some kind of fallback and make sure basic
functionality/validations/checks work,
but don't care about visual effects working without javascript. just
my 10 cents.

On Tue, Feb 10, 2009 at 11:05 AM, Jeztah
<webmas...@thecarmarketplace.com> wrote:
> I am writing a site that uses heavy prototype libraries +
> scriptaculous + jQuery ...
> The issue i am having is a simple one ....
> The site is marketed on its ease of use due to certain techniques ive
> developed but they rely on Javascript and wont work without it.... The
> site still functions without javascript but some core functions cannot
> be achieved .. by this i mean someone can still browse the site and
> search it and do alot of things.
> So ive gone down the thinking process of redirecting people wihtout
> javascript enabled or no javascript to a page on my site telling them
> to enable javascript....
> Now i know this is a big concern to alot of web developers as the norm
> (mostly for me aswell) is make a functioning site then enhance the
> Users Experiance with ajax/js technologies .... But my feeling is if
> people dont start to force the issue of requiring javascript then the
> web wont evolve into what it could become....
> As of January 2008 95% of the browsers in the world had Javascript
> turned on see here http://www.w3schools.com/browsers/browsers_stats.asp
> .. and i am personally not bothered about the 5% that dont .. i also
> know of a few major websites that demand javascript be turned on to
> enter them .
> So my questions are ..
> A. Should we as developers be taking these leaps of faith and
> demanding a better development environment for our client side
> programming.
> B. Would googlebot and other Search Engines follow my <noscript>
> header redirect !!
> Hopefully this wont get flamed to much !!
> Thanks in advance
> Alex
> >

Lars Schwarz
Heiligengeiststr. 26
26121 Oldenburg
T 0441 36110338
M 0151 1727 8127
W www.bitrocker.com

You received this message because you are subscribed to the Google Groups 
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to