graceful degradation

[Oak]

How do you specify when the website should use js and when to use an alternative? or should both options always be available?

Thanks

[CloudedVision]

what do you mean by alternate? The <noscript> tag will hide it's content if the browser has javascript enabled. But NEVER, EVER make your site rely completely on javascript. Always have a backup. Many modern sites do this, but I can't figure out why.

[Oak]

When js is enabled, a site will display functions that are not present when js is disabled and vice versa?

So you say it is simple a question of adding <noscript> tag to a div? And so the <noscript> tag is back up?

[CloudedVision]

Ya. If a browser has javascript enabled, it will ignore everything in the noscript tag. If javascript is off, the noscript tag's content will be displayed. If the browser is so old it doesn't even know what javascript is, it'll think the noscript tag is an error and ignore it, displaying its contents.

If you have a link that is runs a javascript function (let's say AJAX) write it like this:

HTML: Select all

<a href="http://mysite.com/dir/dir/file.php" onclick="ajax_func(); return false;">My Link!</a>

The return false will stop the link from executing. that way if javascript is disabled the link will go to file.php, and if it is the ajax_func(); will be called and the browser will NOT head over to file.php

[Oak]

Ha.. ok thanks, that is very clear.

Though I don't see the noscript tag in your code ? or is this another way of doing it?

[CloudedVision]

The noscript would be something like this:

HTML: Select all

<script type="text/javascript">
<!--
document.write("Hello! You have javascript!");
//-->
</script>
<noscript>
Hello!  You don't have javascript!
</noscript>

[fside]

Originally Posted by Oak

How do you specify when the website should use js and when to use an alternative? or should both options always be available?

Someone mentioned noscript. I like to use that for somewhat involved sites. The viewer may not know what he/she is missing (some corporate 'workstations' are javascript disabled - the ONLY safe alternative to surfing the outer-net that admins could imagine, perhaps).

But generally, if I can, I'd build a site from the ground up. No script, no styles. Just headers, and paragraphs, and bullets, and etc. Then add on. But if it gets to a point where the add-on really adds a lot of 'thin client' functionality, I think it's fair to mention - turn on javascript - in a noscript tag on each page.

I prefer to surf with Firefox 2. And there's an add-in called, NoScript. It's not the end-all and ideal of security. But it ain't half bad. And until you allow the site you are viewing to run scripts, you can see what it is like without. Can be revealing. Some that redirect for subscribers, and such - they won't even display a thing.

What's the ultimate solution - a yet as unpopular or yet to be popularized app that handles all things web, to compete with browsers and 'platforms'? I don't know. Right now, it's the browser, so much so that M$ even basically reformed its IE team instead of going just with the OS/platform.

[CloudedVision]

Take godaddy.com for example. disable javascript and half the links won't work. thats definitely something you want to steer away from.