This is mostly done to prevent other users from copying or stealing their work. Go try it out for yourself.When you are surfing the web, you may come across certain websites that does not allow you to perform right click to copy text or any images. It may have the occasional undesirable side-effect, then, but on balance RightToClick is still a great way to get annoying web pages working more or less normally. If you find you need to drag and drop some object on a page, but this isn’t working, say, it’s fairly obvious that clearing the "Disable page drag/drop handlers" will be a good place to start. Leave RightToClick off until you need it, for instance, then turn it off again when you’re done, and you won’t have to worry about this at all.Īnd even if you don’t precisely understand the consequences of RightToClick’s various options, their names alone will often tell you enough. This isn’t a fatal problem, though, and you shouldn’t let it put you off entirely. Is it best to allow "event listeners", or disable them, for instance? Should you permit "page mouse-move CSS handlers", or block them? Are you sure? But while this sounds good in theory, it’s far from obvious how some of these options should be configured.
You can try to reduce the chance of problems via RightToClick’s Options dialog, which allows you to choose exactly which areas of JavaScript you’d like to turn off.
And it often will, too, but there’s also a chance that it will break some otherwise legitimate web pages. RightToClick isn’t analyzing a page in great depth, trying to spot the precise restriction and disable that alone rather it’s turning off whole categories of JavaScript functions and hoping one of these will do the job. We say "should" because this won’t always be true.
0 kommentar(er)
