<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body>Alan,<BR>
This problem has been discussed earlier in this forum, but I don't remember<BR>
the conclusions.<BR>
<BR>
FIRST STEP - (Preventing Browser cache)<BR>
<BR>
<HTML><BR>
<HEAD><BR>
<BR ><META HTTP-EQUIV="Expires" CONTENT="-1"><BR ><META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"><BR>
<BR>
</HEAD><BR>
<BODY><BR ><DIV style="width:200; height:128; background-image:<FONT class="">url</FONT>('precious.jpg')"></div><BR ></BODY><BR>
<HEAD><BR>
<BR>
<META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE"><BR>
<BR>
</HEAD><BR>
</HTML><BR>
<BR>
This code has a triple action against browser caching.<BR>
(Keep it exactly as is - yes, both headers in the same order of document flow)<BR>
|||||||This code will suffice for Opera 9 - no other actions required|||||||||<BR>
<BR>
SECOND STEP - (Clearing RAM, unloading images on suspicious user action)<BR>
<BR>
<SCRIPT><BR > var alles=document.getElementsByTagName("DIV") <BR>
var tmpImages=new Array();<BR>
<BR>
for(i=0;i<<FONT class="">alles.length</FONT>; i++){<BR>
tmpImages[i] = alles[i].style.backgroundImage } <BR > <BR>
function clearRAM(){<BR > for(i=0; i<<FONT class="">alles.length</FONT>; i++){<BR > alles[i].style.backgroundImage = "url(imageoffline.jpg)"//you may chose to either leave it empty or give a warning image<BR > }<BR > }<BR>
function restoreImages(){<BR > for(i=0;i<<FONT class=""><FONT class="">alles.length</FONT>;i</FONT>++){<BR > alles[i].style.backgroundImage = tmpImages[i]<BR > }<BR > }<BR>
<BR>
onblur = clearRAM<BR >onfocus = restoreImages<BR>
</SCRIPT><BR>
<BR>
|||||||This code will suffice for IExplorer - no other actions required|||||||||<BR>
In Explorer client case, this script will not allow to even click on the image. So, the context menu options like:<BR>
"save background as"; "set as background" & "copy background", will only give the opportunity to save the <BR>
warning image since it will be switched immediately. <BR>
In Firefox/Navigator<BR>
This code will clear/replace all the background images with the copyright warning image in case the user<BR>
goes for: Tools/ Page Info ... Media Tab/Save As in Firefox or Navigator thanks to the Options Box receiving focus.<BR >Same will do in case the user goes for File /Save As ...complete page.<BR>
So far so good, but there is one last hole:<BR>
Firefox special Context Menu Option "View Background Image", is designed to act as a complete bitch.<BR>
This option will blow off all we have achieved in previous steps. Allowing user to navigate to a new page <BR>
containing the protected image caught offguard.<BR>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!<BR>
!!!! Netscape/Firefox not solved !!!!<BR>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!<BR>
Since mozillas event model has always been a week point, we are forced to use a non scripting solution for it.<BR>
Unclean workaround of displaying fully transparent gifs on top of these backgrounds. For now of course...<BR>
<BR>
THIRD STEP - JavaScript Disabled<BR>
(Denying javascript disabled browsers from viewing images unless they decide to enable it)<BR>
As we can see. We have another door OPEN: the script disabled client browser.<BR>
A hard coded HTML with a clear message like: "This page can not display properly with Javascript disabled, blla blla blla"<BR>
Should be used. Than you should decide how to make these images available to the browser render engine through script<BR>
You can decide for, either using css visibility/display or set background properties dynamically with javascript during runtime.<BR ><BR >THE SCREEN CAPTURE ISSUE - my last cent<BR>
Since almost all screen capture applications along with the "print screen" are invoked with a key stroke, we can use<BR>
key down event to call the clearRAM function just in time before the actual capture takes place. So there will be no <BR>
screen capturing either.<BR>
<BR>
<BR>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR > Troy III<BR > progressive art enterprise<BR >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR ><BR ><BR>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #008080 2px solid; MARGIN-RIGHT: 0px">
<HR id=EC_stopSpelling>
From: alaneaston666@hotmail.com<BR>To: javascript@LaTech.edu<BR>Date: Fri, 21 Jul 2006 09:58:26 +0100<BR>Subject: [Javascript] Disable left mouse click and drag on images<BR><BR>
<DIV>
<DIV class=EC_RTE>Hello People,</DIV>
<DIV class=EC_RTE> </DIV>
<DIV class=EC_RTE>Now I know the issues surrounding trying to stop people stealing images off your website, it basically cannot be done, you can make life awkward, but essentially it cannot be done.</DIV>
<DIV class=EC_RTE> </DIV>
<DIV class=EC_RTE>Well, I have a client who wants me to make it as difficult as possible for any visitor trying to save their images.</DIV>
<DIV class=EC_RTE> </DIV>
<DIV class=EC_RTE>I have disabled right-click on images, but you can still left click on an image, and drag it to either the location bar, then save it once the image shows, or drag it to your desktop.</DIV>
<DIV class=EC_RTE> </DIV>
<DIV class=EC_RTE>Question is, does anyone have a trick that I can use to stop this "left-click and drag" on images....????</DIV>
<DIV class=EC_RTE> </DIV>
<DIV class=EC_RTE>Any help would be appreciated.</DIV>
<DIV class=EC_RTE> </DIV>
<DIV class=EC_RTE>Alan...</DIV></DIV></BLOCKQUOTE><br /><hr />Express yourself instantly with <a href='http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=joinmsncom/messenger' target='_new'>Windows Live Messenger</a></body>
</html>