> In a controlled input situation (eg: a web developer's blog), a > solution like Patrick Lauke's 'type' link styling expermient ( > http://www.splintered.co.uk/experiments/38/ ) adds more useful info to > the markup and can be used the same way; but when a client is in > control of the content you set up whatever automated help you can and > cross your fingers ;D
The client factor highlights why inobtrusive/separated Javascript is the way to go... things have a chance so long as the user doesn't have to do anything extra, much less have to *consistently* do something extra. If we don't have to teach them anything, they can't get it wrong and we avoid offending the academic/client ego.... ;) h -- --- <http://www.200ok.com.au/> --- The future has arrived; it's just not --- evenly distributed. - William Gibson ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
