You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 11, 2023. It is now read-only.
When Vim-Vixen is configured to "blacklist" a site or partial URL, it seems still to inject its console IFRAME. The existence of this frame is sufficient to break some web sites.
Desired Behaviour
When Vim-Vixen is configured to be disabled on a particular site or page, it should not modify the DOM at all.
Visit the site and observe that it is still broken.
Using the Firefox debugger, observe that the V-V IFRAME is still present in the DOM.
System configuration
Firefox version: 69.0
Vim-Vixen version: 0.24
Console logs
The precise error will depend on what the web site is trying to do, but typically it will be a variation on SecurityError: Permission denied to access property "document" on cross-origin object
The text was updated successfully, but these errors were encountered:
Hi. Until this issue is resolved, I've found a workaround/hack for this. I created a simple Greasemonkey user script, that just removes the iframe from the site.
Bumping this issue, as it's still present in the latest version of VimVixen. The userscript posted by @mwuttke97 does the trick, but it would be better not to have to use it!
I'm opening this issue because:
Description
When Vim-Vixen is configured to "blacklist" a site or partial URL, it seems still to inject its console IFRAME. The existence of this frame is sufficient to break some web sites.
Desired Behaviour
When Vim-Vixen is configured to be disabled on a particular site or page, it should not modify the DOM at all.
Steps to Reproduce
System configuration
Console logs
The precise error will depend on what the web site is trying to do, but typically it will be a variation on
SecurityError: Permission denied to access property "document" on cross-origin object
The text was updated successfully, but these errors were encountered: