Why support is not js

Question

lets look at it, everyone uses facebook ... - actually surely everyone has js ... why does it seem like you should support multiple (if any) without js?

Answer 1

I think it completely depends on your target audience. The main reason standards exist is to let web developers focus on everyone, regardless of their browser / operating device. Yes, most people using a computer or a modern phone will be able to run JavaScript. Therefore, you cannot worry about non-js browsers and avoid this.

But at least in the US, attention is focused on accessibility for people with disabilities. Screen readers for the blind, entering data into a computer for those who type with something other than a keyboard, and other viewing methods for the disabled, means that web developers need to know about non-traditional users. There are some good guidelines on the ADA website that explain what to consider.

Thus, it all depends on how much you want your site to be and how much you care about everyone, regardless of their viewing mode.

Answer 2

Some corporations require it to be disabled.

No one has a difficult number for how many people turn it off. I read somewhere between 0-10%.

You support those few when you cannot afford to alienate X% from your customer base. This is not so difficult to do, but an advantage can be important. Why not?

Answer 3

I think when it comes to it, it really depends on your target audience. If you know that your target audience is likely to have JavaScript enabled, then so be it.

I have a situation at work, however, when I know that some of the people I develop can use old browsers and whether I like it or not, I cannot get them to update.

You also want your site to be accessible across all platforms and browsers, and this includes audio and text browsers. Your site may not be accessible to people with disabilities.

How important is it enough for you to develop a non-JavaScript version of your site for you.

Answer 4

The only compelling reason to support non-JS browsers, I would think if you have clients who pay you for it. The end of the story.

Answer 5

I do not think that you really support users who do not support js, you support unknown methods. Coding drops links, and this is good practice. This helps search engines, web scrapers, and primitive mobile devices that do not yet support js, or an older browser 508. I myself tend to agree that the website is currently pretty useless without js, but you should still do everything possible to support non js in emergency mode.

Answer 6

JavaScript is fragile. There are many things that can cause it to break, from errors in browsers that you have not tested (especially mobile browsers), to browser extensions that play with your code, to dodgy Internet security applications that block parts of your code. If your site works without JavaScript, you have nothing to worry about, because it will probably still work in these circumstances.

JavaScript tends to interact poorly with accessibility aids. A site that runs without JavaScript will be more likely to use screens to read other unusual user agents that you may not have agreed with.

And besides people looking at JS for security / privacy or because they have no choice, there is also a pretty important non-JavaScript user agent class: spider. Hide all your content so that it is not accessible without JavaScript, and you just lost a friend on Google. I hope you did not count on a lot of visitors or something else.

Create a site that runs without scripts, and then add JS magic with progressive enhancement. You will have a site that works for more people, which is likely to have fewer usability problems (*), and is more SEO friendly. This is a comprehensive victory if (a) you have a task that by its nature requires scenarios, or (b) you are simply lazy.

(*: for example, links that you can click with a middle click, but which simply open in a JS error, unregistered subpages, user interface elements that do not respond to keyboard interaction, broken navigation ... you can write JS in a clean way minimize these problems, but most people do not.)

Answer 7

You do not need to support it. If you think that you will not lose noticeable traffic by proposing a JS-only site, suggest a JS-only site. But if you think you will see more traffic and possibly get more sales, given that a non-JS website is a good idea.

Also make a distinction between a full-featured JS site and several JS add-ons that make forms more usable. In many cases, you can easily offer the same functionality as those few JS subtleties.

And always be sure to add the necessary checks / checks to the backend, since you cannot be sure that someone uses JS, and therefore it can be processed by the interface.

Answer 8

lets you deal with this, everyone uses facebook ... - in fact, of course, everyone has a js function ... why does it seem like you should support several (if any) without js?

I do not seem to be all. I disabled JS by default. I'm not paranoid, but I don't like viagra-promotion passing through my browser and similar toys (maybe I'm not the only one).

But this is not a problem, if I visit a page that seems interesting to me, I can turn it on with one click. As for me regarding your question: if you forget users without javascript like me, they won’t be able to see if your page might be interesting.

So, the question is really simple to answer: if you do not want to lose users due to disabled JS , you also support them.

Also keep in mind: if you have a business on your page, you not only lose users, you lose profit.

Answer 9

The Yahoo Dev network has done some testing of this, and depending on how many users you visit your site, it can be a significant number of people.

http://developer.yahoo.com/blogs/ydn/posts/2010/10/how-many-users-have-javascript-disabled/

Answer 10

Many mobile devices do not yet support JS. Even New-ish Blackberries has terrible browsers that either have the javascript-statement disabled, or it's just so bad that you still don't want to enable it.

Answer 11

rudeness. Errors in your Javascript code tend to become low-severity issues, not serious ones.

Answer 12

Since JavaScript is an easy-to-learn language and really easy to use on web pages and starting to write scripts in its own way, and because of this there are terribly bad written scripts and plugins that users put on their sites, causing terrible errors, slowdown , intermittent and almost impossible user experience, lagging and horror coding among other things.

In addition, mobile device users may want to disable it in order to save bandwidth (money) and CPU usage (battery). Many mobile browsers have really poor JS support, and therefore it is useless anyway.