I'm leaning toward a combination of JS for user-friendliness with the validation coming from ColdFusion programming.
I get the best of both worlds that way. I'm not big on web standards and accessibility. At least not right now. I agree that the audience is a big factor, but if it's the general population we're talking about, then the small minority can make a choice to use my sites or not. *Their* choice to exclude themselves, not mine to exclude them. It's like coding for users of the Opera browser. If they want to be able to have the best experience on my sites, then install IE. It's just too much work to cater to every minority group in the virtual universe. Rick -----Original Message----- From: Robert Rawlins - Think Blue [mailto:[EMAIL PROTECTED] Sent: Monday, April 16, 2007 1:20 PM To: CF-Talk Subject: RE: Client-side validation or Server-side Validation? I don't think it's very user friendly at all, but I'm quite a big web standards and accessibility fan. You should always have an alternative version of your site that can be viewed on a small screen or text only browser and things like that. You can achieve a perfectly rich feel from server side validation on simple forms, if you want to do more complex stuff with AJAX then I'm sure that insisting on javascript enabled browser is something you don't really have a choice about, but that's something you have to consider when taking into consideration when deciding to go down that route. I think expecting or pressuring the user into doing anything is a bad move, after all assumption is the mother of all f*** ups. Like 'Josh' says it's really about your audience, when you're working with any high volume traffic of something you would deem 'mission critical' then why would you EVER take the risk of 10% of the potential market not being able to access your application? It would be madness. But 'rich content' and 'form validation' are very different things, and this thread started talking about form validation in which case, relying on JS alone, or having a system that doesn't work unless JS is enabled is a massive mistake to make. With rich content then you're probably a little safer, but with anything that is mission critical or a major revenue driver for your business, I think it's a risk you shouldn't be taking. Rob -----Original Message----- From: Les Mizzell [mailto:[EMAIL PROTECTED] Sent: 16 April 2007 17:47 To: CF-Talk Subject: Re: Client-side validation or Server-side Validation? > Looking at the latest published W3C statistics you would educate a guess of > about 10% of browsers not having JS enabled on them, that's a fairly hefty > chunk. How bad would it be to make having javascript turned on *REQUIRED* before visotors can view certain content (forms)? It's something I've considered, especially after looking at the extra code I've had to place on certain pages to check required fields if javascript is off - but how 'user friendly" is this if done? Opinions? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:275413 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
