By bloid
via thinksincode.blogspot.com
Published: Feb 21 2007 / 14:15
Nobody likes their HTML, JavaScript, or images stolen for use on another site without permission. One of the common ways to prevent this, unfortunately, are JavaScript snippets that stop a user from right-clicking anywhere on the page. While it might work for casual image thieves, this approach (1) is not foolproof, and worse, (2) will annoy many of your site's users.
Tweet
SaveShareSend
Tags: javascript, opinion, web design
-
How do I check if a string is a number in Python?
-
NeoAxis Game Engine 1.2 Released
-
09. Getting Testing Done in the Sprint – Test Tasks on the Board
-
If doctors would work like software engineers, no-one would consult them
-
Creating a new Ecore model with Obeo Designer 6.0
-
Processing 10 million messages with Akka
Comments
Jim Wilson replied ago:
I whole-heartedly agree. Right-click hijacking should be off limits in UI design.
Yes, yes, I know what you're thinking. "But what about webapps like Google Docs that use it for good?"
No. Leave right-click alone. Users expect right-clicking a page to provide the right-click menu - always. Doing anything else violates this expectation and kills functionality on which people rely every day.
Lowell Heddings replied ago:
I often use the right-click \ Back menu item on computers that don't have a "back" button on the mouse. It drives me crazy when somebody has disabled the menu.
daniel replied ago:
Personally, I kind of like how anti-right click is used in things like Writely (now Google Docs) and Google Spreadsheets. I mean, with FF 2.0 it can be a little annoying not getting the correct contextual menu in docs, but overall I think the UI advantage to having a custom contextual menu in the web page outweighs the annoyance.
That given, it drives me *&^%#$@ up the wall when web sites mess with "anticipated response" in general. Anything which doesn't do what the user expects it to has no place in your UI.
Voters For This Link (18)
Voters Against This Link (0)