Forum Moderators: open

Message Too Old, No Replies

Wax Cartons with Plastic Screw Tops?

Is this "plus" merely JS added to a website?

         

tangor

9:08 pm on Feb 28, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



You've seen 'em... ordinary wax paper cartons with fold out tops which (in recent years) have an unscrew plastic cap as a secondary method for unloading content. (Milk, orange juice, etc.)

How much java script do you add to your website which does nothing more than this? Doing the same thing the "old way" does sans "js add-ons". Just wondering how much traffic the script enamored folks might be missing with the rising number of JS killer browsers out there.

caribguy

2:44 am on Mar 1, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



rising number of JS killer browsers
I do not believe this to be true among ordinary users.

Do you have any facts to back up your statement?

Exampli grati: Faceboo is unusable without JS.

/add I am in the middle of reworking a site that was launched in 2007. *Everything* will be dependent on jQuery, and I don't even see it as a gamble. Sorry, there will be no fallback for non-js browsers.

SevenCubed

3:37 am on Mar 1, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I use JS sparingly but when I need to use it I just give them the <noscript>BIG RED WARNING</noscript> if they have it disabled so they know they are missing out on something.

rocknbil

5:49 pm on Mar 1, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



The real issue with these stupid web tricks is not really how much Javascript is involved, it's one of usability . . . see webpagesthatsuck.com. People aren't impressed by cool widgets, but the site owners sure are. :-)

How much are they losing? If they code it right . . . none.

The way most Javascript stuff is supposed to work - even Jquery - is via progressive enhancement (or graceful degradation, take your pick. :-) ) When you see this

<a href="real-url.html" onclick="return some_javascript();">Blah</a>

(or it's equivalent externally assigned)

They lose nothing. But this,

<a href="#" onclick="return some_javascript();">Blah</a>

or

<a href="javascript:some_javascript();">Blah</a>

A lot. It renders the content inaccessible so definitely, losing a lot. But I guess the redeeming factor is, the developers/site owners don't care. They justify their decision with the same old arguments - most of the world has Javascript enabled, I don't care about non-Javascript users, either get up to speed or get out. Apple can get away with hostile marketing, most of us can't, and shouldn't.

I talk to so many people every day - ordinary people - housewives, grandparents, users who couldn't care less about bells and whistles, they just trust in what their perceived authorities tell them - who, for one reason or another, have Javascript and Flash off because someone told them it's how you get hacked. Or they run AVG software that disables most Javascript and trust it openly. There is a huge market out there for accessible sites, Javascript or not, I refuse to turn them away because my ego says so.

What gets me about all this is that it's so EASY to make your Javascript accessible. It really is.

g1smd

6:04 pm on Mar 1, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



There are a rising number of sites that result in my browser giving this error message:
A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.
[Stop script] [Continue]

The amount of inefficient dross being coded into pages is rising, and it looks like that trend is set to continue.