Web designers: stop wasting time breaking the Internet


 

What is it about some web designers that, instead of spending time on developing a great user interface and making the site look good, decide to add code that breaks basic functionality.

A couple of days ago someone sent me a link to an article about gadget discounts. When I visited the site, not only was the link to the manufacturer not hyperlinked, but the left mouse button had been disabled when the pointer was over text in order to stop copy and pasting.

web breaking code 540x205 Web designers: stop wasting time breaking the Internet

I had to type in the URL because I could neither click through nor C&P.

Huh?

When I examined the code I noticed some other “niceties” such as a ‘ban’ on right-clicking over images.

The code looked for anyone using Internet Explorer or Netscape Navigator (seriously, what decade are we living in?) and, if they dared to right click on an image, a pop-up box spewed out a copyright message.

They hadn’t bothered to do a complete job on the code, mind, because using Safari I was quite able to copy the image.

That said, I would have been able to copy the images and text anyway. Automated scrapers would’ve managed it. Anyone intent on ‘stealing’ content would have done so regardless.

The only people this tactic hurts are regular surfers who just want to use their PC and the web in the way it was designed.

Hyperlinks. Full mouse functionality. Copy and paste.

It really shouldn’t be too much to ask.

Web designers: if your client asks you to ‘protect’ their web pages, please politely decline, inform them that there’s no way to stop people determined to copy content, and then design to standards and principles that don’t crap all over your visitors.

Thank you.


 

0 Responses to Web designers: stop wasting time breaking the Internet

  1. JC says:

    Do you seriously think that’s something created this week? Maybe if you redate this post to 1999 and say “Hey there, I’m from the future, this is baaaaad”… except, back in 1999 and earlier, we already knew it was bad, but back then everyone was paranoid about people stealing their content and required stupid right click blockers.

    And that “standards” argument is a heaping, steaming pile. HTML 3.2 was a standard. Javascript 1.0 was a standard. Those two together probably make up the page you’re kvetching about.

    If you want to do a meaningful rant on this topic, rant about companies that don’t keep their websites current, not fixes.

    PS — your blog doesn’t work if javascript is disabled. Pot. Kettle. :)

  2. JC says:

    Oops, skip that last bit. Your blog just doesn’t work, period, past the homepage. Server problem or something.

Leave a Comment

Your email address will not be published.

*