April 26, 201511 yr I found this - http://kryogenix.org/code/browser/everyonehasjs.html and it made me think. Which points do you think should be taken into account? To be honest I can't imagine life without Javascript / jQuery and although I do try to provide fallbacks for users with disabled js, some complex features are simply not usable without it. Interested to hear your thoughts.
April 26, 201511 yr This statement could be added to the list. "If your users are viewing your pages using a game console or TV all JS is most likely disabled"
April 27, 201511 yr This statement could be added to the list. "If your users are viewing your pages using a game console or TV all JS is most likely disabled" Who really uses the web using those devices these days? There are edge cases but thats literally it. Many modern web apps are now much more complex than simple ajax calls and its either not possible or not financially fesable to write fallbacks for. We can simply inform the user to use a js enabled device. If its simple to create a fallback, like for ajax then we should. The few users who do browse with js disabled must already be used to having a terrible browsing experience because most do not provide any kind of fallback.
April 27, 201511 yr Who really uses the web using those devices these days? Only 0.11% Worldwide according to statcounter.com (0.34% in UK). Hardly reason enough alone to invest resources in fall backs, I agree (unless of course your target audience are gamers). But the fact that many game consoles are not JS enabed is still something that developers should be aware of. Edited April 27, 201511 yr by Nillervision
April 27, 201511 yr most gamers are probably overflowing with alternative devices (pc, smart phone, tablet, apple watches... ) and will probably just jump onto one of those. different scenario possibly to a work/study place where js is locked down. (and even then smartphones to the rescue)
Create an account or sign in to comment