| Advertisement |
What is the "Allow Right-Click" extension and how does it work?
A website can intentionally disallow right-click access. You can use this extension to bypass this restriction. Websites can disable the default browser's context menu and use their custom context menu for their content, but this can also allow JavaScript to disable the browser's context menu without providing any useful functionality.
This extension provides an action button that, when clicked, unblocks the browser's context menu. Upon clicking the button, the extension injects a small script to release the context menu restriction. This extension only injects the script after the user clicks the action button. This manual injection is intended to avoid conflicts with any custom context menu that may be offered by the website. The extension is particularly useful in situations where the web page content is protected from being copied or pasted.
recommended "2FA (Two Factor Authentication)" extension for Chrome, and Edge browsers.
2FA (Two-Factor Authentication) is an Aegis-compatible browser extension for managing TOTP and HOTP codes. It stores your tokens in an encrypted Aegis database file on your device instead of browser storage, making it easy to sync across devices with any file-sharing service. The database uses the same strong encryption as Aegis Authenticator and is fully compatible with the Aegis Android app. You can create, edit, organize, and delete tokens, customize their details and icons, and use keyboard shortcuts for faster access. Read more here.
What's new in this version?
Please check the Logs section.
What steps should I take if I'm having trouble using this extension to unblock the right-click context menu on a web page?
You can report the issue by visiting the discussion section of the extension page (this page). Please be sure to provide an example page where the problem is reproducible so that it can be investigated.
Can the toolbar button be used to toggle the extension off and disable the protection?
[new versions] In the latest release of the extension, the action button can be used to partially disable the protection by clicking it once after the script has been injected. However, it's important to note that this action will not remove all of the injected methods. If the page is still not functioning normally after partially disabling the protection, it is recommended to refresh the page.
[old versions] No, it is not possible to use the toolbar button to disable the extension on the current page once it has been activated. When this extension is activated, it removes several event listeners and overwrites certain native methods. There is currently no method available to undo these actions. If you no longer require the protection, you can reload the page to revert to the default settings.
Why is the automatically unblocking feature not working after updating the extension to version 0.4.0?
In version 0.4.0 of the extension, the "webNavigation" permission has been moved to the optional section, which means it is now disabled by default. As a result, the extension no longer has access to browser tabs, which prevents the automatic injection from working. To enable this feature, you will need to visit the options page and opt-in to it.
Additionally, if you are using an older version of Chrome, you may need to restart the extension by disabling and re-enabling it or restarting your browser.
How can I make this extension unblock all frame elements on the current page instead of just the top frame element?
By default, this extension is only able to unblock the top frame element of the current page and all sub-frames with the same origin. To unblock all frame elements, you need to grant the extension the "webNavigation" permission, which is required to access cross-origin host elements on the current tab. To enable this feature, visit the options page of the extension and allow the "webNavigation" permission. Once the permission is granted, the extension will be able to unblock all frame elements on the current page (a page refresh is requested).
How can I test this extension?
Visit the webbrowsertools.com/test-right-click page, then enable the extension from the action area and follow each test.
How can I automatically unblock the right-click access on subdomains of a domain using this extension?
Starting from version 0.5.5, you can use wildcard hostname matching to unblock the right-click access. For example, if you want to unblock the right-click on all subdomains of "example.com", you can add "*.example.com" to the list of domains on the options page. More examples:
example.com -> unblocks both example.com and all its subdomains (e.g.: www.example.com)www.example.com -> unblocks www.example.com and all its subdomains (e.g.: sub.www.example.com)*.example.com -> unblocks all subdomains of exmaple.com but does not unblock example.comhttp://example.com -> unblocks "HTTP" scheme of example.com. It does not unblock the subdomains.*://example.com -> Unblocks "HTTP" and "HTTPS" schemes of exmaple.com. It does not unblock subdomainsWhat is the meaning of the colors used on the action button (version 0.6.2 and above)?
Please keep reviews clean, avoid improper language, and do not post any personal information. Also, please consider sharing your valuable input on the official store.
Users can manage hostnames in a whitelist via context menu actions. The list is stored in the hostnames variable and automatically filtered for uniqueness. Notifications indicate whether actions succeed or fail. The monitor variable is set to true if the required permissions are granted.
Users can manage host permissions directly from the options page using dedicated buttons to allow or remove permissions. The hostname input is displayed in a disabled textarea.
The extension's options page is accessible through the context menu.
Features:
Users can trigger a test action via the ‘test’ context menu item, opening a specific URL in a new tab.
Clicking the ‘inject-sub’ context menu item allows users to request script injection by prompting for the *://*/* permission.
The ‘simulate-click’ command lets users simulate mouse clicks on web pages by sending a message via chrome.runtime.sendMessage.
This feature injects CSS to allow pointer events and customize text selection on copy-protected web pages. It targets elements with the copy-protection-on class using CSS layers for specificity and automatically cleans up styles via window.pointers.run.
Enhancements:
user-select to initial to enable text selection.MutationObserver to dynamically handle changes in stylesheets and inline styles.mousedown event listener to override user-select on restricted elements.window.pointers.run.| Permission | Description |
|---|---|
| storage | to store local preferences |
| *://*/* | to be able to inject the script on all web pages |