Tuesday 28 June 2011 12:50:51 pm
What's the problem with using ajax calls for this parts? It's a very common technique on all big sites.
I forgot this part. well, this is probably because some years ago i was more focused on developing sites that should pass accessibility tests. supposedly, if the site was paid by public money it needed to to pass the AA level, because as it was using public money, everybody should use the site. as you may know, one of the parts is that you cannot rely on javascripts and other technologies if you don't offer an alternative. so, thinking about ez publish and ezstarrating, ok, ezstarrating is a form with some radiobuttons converted to those nice starts for clicking. if a user doesn't use javascript (probably because of his browser) he can vote with the radio buttons. but if the page is using viewcaching, you cannot control if he has voted or not again... so, don't get me wrong. i like ajax stuff. but it's just it should have always an alternative without the need of it.
I really understand your points, I'm also always trying to preserve non JS backwards compatibility as much as I can. But the fact is that today JS is almost a standard for all sites and soon there will not be a single site that doesn't rely on it. For example...
- on cnn.com you cannot log in without JavaScript.
- on usa.gov, several parts of site don't work if you don't have JS enabled (especially "contact us", "chat" or "FAQ").
- on education.gov.uk the main menu and "increase contrast" don't work without JS
And interesting thing, if you look at share.ez.no without JS, it's only readonly mode for you... :) And there's another point... If you think in terms of fbconnect, your server cannot always found out if the current visitor is logged in into FB or not, but jour JS can. As much as I would also like all sites to have a full backwards compatibility with non JS browsers, this is something will have to leave to the past and full JS browsers should become a standard for all web. In my opinion the things that shouldn't rely on JS are:
- content - all content should be available without JS. Not only because of 1% of non JS users, but also because of search engines
- all links should be clickable and lead to some page, even if they open a JS popup. This is not only because of search engines, but because of "Open in new tab" too
- user interaction that is intended for general visitors (anonymous users) should have at least some fallback for non JS browsers
- on sites of general public importance posting user content should have at least some fallback
All other parts (if I didn't forget something), especially for loged in users can freely be implemented via JS, having fallbacks where it's suitable, but without making opstructions to the preformance optimisation that JS usage bring. P.S. Sorry for offtopic.
--
Nothing is impossible. Not if you can imagine it!
Hubert Farnsworth
|