Christian Heilmann wrote:
> Rule 1: JavaScript dependent elements
> should be generated with JavaScript,
> otherwise you promise functionality that
> may not be available.
I fully agree with this and practice it myself. Use JavaScript (JS) to print
JS functionality to the page. I regularly do this. I may offer, for example,
JS back link using javascript:history.go(-1); but I'll use it within
document.write so if JS isn't supported, the user doesn't get a link they
cannot use (see expanded example below). That is when a decision is made to
1) offer nothing because it was fluff anyway, or 2) to use <noscript> to
offer an alternative like "Use your back button to return"
Expanded example:
<script type="text/javascript">
//<![CDATA[
document.write("<p><a
href=\"javascript:history.go(-1)\">Return</a></p>");
//]]>
</script>
<noscript><p>Use your back button to return</p></noscript>
My method here does have a flaw thought in that document.write is deprecated
in the XHTML 1.1 spec I think. But maybe someone will offer an alternative.
Excellent advice, Christian.
Respectfully,
Mike Cherim
http://green-beast.com/
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
