|
|||||||||
|
|||||||||
| |||||||||
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
|
|
#17
April 25th, 2001, 01:39 PM
|
|||
|
|||
|
uh no...the reason it would piss me off is because 99% of scripts that disable right click, also disable the wheel on my mouse...and i use it all the time...
my point is(which was not demonstrated in my past post), that script could possibly kick clients off of your site. and if i were that client who got kicked off i would go back to the site for one thing...to complain, and that would be it. lets not forget that the majority of web users have no idea what goes into putting sites together. making a user feel as if they have done something wrong and in turn penalizing them is just going to make them even more scared to explore the web.
|
|
#18
April 25th, 2001, 02:26 PM
|
|||
|
|||
|
That's interesting. I use the Microsoft IntelliMouse at work and Logitech Mouseman Wheel at home and I've yet to experience the wheel not functioning when the ability to right-click is removed on a web site. At work, I use Windows 2000 and I use MacOS 9.1 at home. Do you have the wheel set to act as a "third" button or as the "second" button? Do you have the latest drivers for your mouse installed?
In any case, the users that have no idea what is going on, often times do not even know that they can right-click. Trust me on that one -- I used to do support for an ISP for five years. The clueless users have a hard enough time dealing with one button, let alone two (or two and a wheel). I would wager that the people it would piss off are the same people that get pissed off when a web page disables your ability to pick a typeface size (through CSS). There are pros and cons to both sides of the argument and you're entitled to your opinion. However, rmharmon's client is obviously not of the open-source "mentality". Believe it or not, some people aren't necessarily looking for the largest possible audience. Others are even willing to sacrifice viewership/membership by building their entire site in Flash (for instance) and requiring the plug-in in order for anyone to get anything out of the site. In my professional opinion, disabling the ability to right-click on your site isn't going to detract that many people. On the flipside, I also don't think it's worth the effort, unless you are also willing to build the window without menus, etc. Citibank does that to enhance the security of their online banking.
|
|
#19
April 25th, 2001, 03:31 PM
|
|||
|
|||
|
are you saying that my script affects your mouse wheel? You wern't very clear on that. And besides you could make the bye() function send you to a page instead of freezing. Ill post the code for in later.
|
|
#20
April 25th, 2001, 06:12 PM
|
||||
|
||||
|
Hi,
Isn't it rude to freeze the visitors' browser window? I would never do anything like that because I want to keep them happy (I seem to be an exception). About the middle mouse wheel: the script I posted doesn't kill the middle mouse wheel, only the right mouse button. Pieux said: Quote:
Why, to disable viewing the source and thus disabling the user to view the exact location of the image? If you want to disable them to view to source you can simply put your site in a frame. Personally I don't protect my images, because there is no good reason for me to do so. If I had a good reason to protect them I would put my site in a frame and I would use JavaScript to disable the right mouse button. Of course, it would still be possible to steal the image (for example by using "print screen" or looking in the temporary internet files) but most people would be to lazy or to stupid. Or maybe I would use Flash. Bizzk Last edited by bizzk : April 25th, 2001 at 06:35 PM.
|
|
#21
April 25th, 2001, 07:15 PM
|
|||
|
|||
|
Like I said in the previous post, you can change the bye() func to open a window with a .html explaining why you dont want the user right-clicking.
Also, my script doesn't affect MY mousewheel
|
|
#22
April 26th, 2001, 03:42 AM
|
||||
|
||||
|
I tested Pyro's script and it doesn't affect my wheel either.
The script is good but I still think that is to rude. Even redirecting the viewer would probably piss him of and cause him to never return again. At least, I would never re-visit that page (unless it was unique and superbe maybe). Bizzk
|
|
#23
April 26th, 2001, 10:53 PM
|
|||
|
|||
|
Bizzk,
Unless you disable all the menus in conjunction with the right-mouse button, frames still don't help, because you can view the source of the frameset, get the URL to the individual frames, go to the individual frames and view source on those. You would want to hide source not only to "protect" proprietary information/code, but also to increase security (for financial applicaations, for instance).
|
|
#24
April 27th, 2001, 07:14 AM
|
||||
|
||||
|
You are right, I didn't think about that.
When you are building a financial application you should always eliminate all possible security risks.
But images can not be protected for 100%, because there is no way to disable print screen (maybe you can let your visitors download some .exe file, but I doubt if the will like that...). The only thing you can do is making it a little harder but you shouldn't irritate the visitor by freezing his window or using a window without the menu. Bizzk
|
|
#25
April 27th, 2001, 01:26 PM
|
|||
|
|||
|
I dont think its rude to freeze their browser if they have been warned. This code does that. Alternativly, you could point the code to another page.
Code:
<SCRIPT LANGUAGE="JavaScript">
/*
This script was coded by: Pyro_Ice
Part of EclipceNet© 2001 & EclipceNet© .com
*/
document.onmousedown=click
var times=0
var times2=10
function click() {
if ((event.button==2) || (event.button==3)) {
tell(); times++
}
}
function tell() {
if (times<=2){
alert("Function Disabled");}
if (times>=3){
alert("Function Disabled\n (Last Warning)");}
if (times>=4){
alert("Your privilages of veiwing this\npage have been removed.");
// Freeze Code
var color = new Array;
color[1] = "black";
for(x = 0; x <5; x++){
document.bgColor = color[x]
if(x == 1){
x = 0;}
}
}
}
</SCRIPT>
((Again, please leave the comments in if you decide to use this))
|
|
#26
April 27th, 2001, 03:33 PM
|
|||
|
|||
|
Thanks
Thanks everyone. I will inform the client of the options. I really don't know why they are even worried about it The images are not really much to look at in the first place.
|
|
#27
April 27th, 2001, 09:26 PM
|
|||
|
|||
|
WE WENT THRU ALL THIS FOR CRAPPY PIX????
hehehe just joking.  Just wondering why do they not want the people to steal them? Are they just regular images or are they a product of some sort.(Or are you even @ liberty to say?  )Pyro_Ice
|
|
#28
May 9th, 2001, 04:38 PM
|
|||
|
|||
|
I delurked just to reply to this thread, as this anti-right-click functions are a pet peeve with me, so I hope no one minds. Also, these comments are not directed at the person implementing this for his client or the writers of these scripts, so I don't mean them personally.
 I think scripts like these are against what web developers are normally trying to achieve with commercial sites, and that is to cultivate a feeling a goodwill with users to attract and keep traffic. It should be a privilege to have our sites viewed by people (as the internet is being more competitive with more companies getting websites); it shouldn't be a privilege for a user to view our sites (as the alert box in one of the posted scripts suggested). I also believe we shouldn't treat browser windows as if we owned them. A browser belongs to the user, so I think it's rude to cause harm or disfunction to it (ie, it's rude to disable right clicking and definitely to freeze it). It seems that a common attitude is people right click just to steal images and code. When I right click on an image, my menu contains 16 items, only one of them being "save picture as". When I right click (not on an image), my menu contains 18 items, none of them being "save picture as". I commonly right click to open links in new windows and open frames in new windows. So an alert box or a new window explaining to me the reason why I can't right click doesn't really explain it to me, since I wasn't doing it to steal their images. Additionally, an anti-right-click script seems hugely disproportionate to the problem when it blocks 16-18 shortcuts and functions just to prevent one. Just wanted to add my thoughts on this.
|
|
#29
May 9th, 2001, 06:41 PM
|
||||
|
||||
|
ninurta:
I totally agree with you. Protecting images (with right-click-prevention, slicing or whatever) is just an option, and it has many difficulties and problems. But, as many of the professional web developers on the forum might have experienced, some clients are afraid of hackers/copyright thiefs, and it is very hard to convince them that the problems of protecting the images are bigger then the gain .Bizzk
|
|
#30
May 11th, 2001, 02:56 PM
|
|||
|
|||
|
One other alternative
you can also use layers in IE5. Put a layer over your image and you cant right click to save it. combined with a warning script, cutting up your images and putting a watermark or something, the only way to get the pure image would be to contact you directly.. (other than the obvious "print screen") but then again they wont have the pure image. I would say if your client wants to protect the image, put a mark on it that doesnt take away from the overall effect but that lets others know that it is ovbiously not the real image.
__________________
Matt Owen Webmaster www.texasbeta.org
|
|
| Viewing: Dev Shed Forums > Web Design > Web Design Help > Stealing Images |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
