On 11 Jan 2009, at 14:54, [email protected] wrote:
> @Lee... Javascript should only really be used in addition to standard > HTML mechanisms, as an improvement for those users / browsers that > want to utilise it. No reason you can't do both, and gracefully degrade. Although unless their was a clear dollar advantage to doing both, I'd not do it - it's premature optimization, edge case functionality, and it's going to adversely affect user experience for EVERYONE due to the increased server-side load of using a non client-side solution. Remember, a disabled user doesn't mean a disabled browser. I think you've over analysed, and have the two confused. I think you'll find the percentage of users without JS is incredibly small - although I guess this depends on your target demographic. For a site like perl.org I expect it will be much higher, as the demographic is likely to use text based browsers etc. Besides, if you're talking about screen readers, you've got more problems than just javascript - this is TABULAR data you're talking about ;) If your concern truly is for disabled users, don't present the data in a table. Sometimes the simplest solutions are the best :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
