jekillen.com lab 51

To develop intellectual property protection


reload

protect inline image demo:   
guitar image
protection will not eliminate the possibility that intellectual property,
such as the image to the left, will be protected from copy. But this
strategy will make it more difficult to isolate the image for copy to
a local client system.

In addition, the default state of the image is set to a group of css
rules that will prevent it from being selected and/or dragged off
onto the desktop to copy. The context menu is also disabled for
the whole page.

In the protected state, the image is set to div element background
URL and set with an opacity that will allow the background tile to
show through. An attempt to copy the image via a screen capture
will include the faint background tile behind the image.


Comments: Last comment on top.
8/22/2021
The browser must be presenting the background images in isolation from cache rather than
executing a new get query. Sampling of the get query processing shows no activity, when it
should.

So, I have found out that when the tile image or the guitar image is isolated by the browser
it will not drag off and copy to the desktop. So in that sense the images are protected. And
when the guitar image is set as an img src it will not be set in isolation. But it will be
included in a 'Save' download. The practice of displaying images as background attributes in
css rules does protect them from copy to a client system separate from the browser. This has
been most thoroughly test in Firefox with some perfunctory testing in Chrome.

8/21/2021
This is not working as it does in my local development server.
(browser: Firefox) using the dev tools inspector panel:
When clicking on a css background rule with a clickable representation of the get query,
the image is produced in a separate display in place of the main interface page. It shouldn't.
What should display is the text 'access denied'.