Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: support for disabling site-specific access keys #348

Open
dumblob opened this issue Jan 8, 2016 · 0 comments
Open

Enhancement: support for disabling site-specific access keys #348

dumblob opened this issue Jan 8, 2016 · 0 comments

Comments

@dumblob
Copy link

dumblob commented Jan 8, 2016

First, thanks for this great extension - I'm using pentadactyl, but at work I have to use Chrome on Windows and because other vim-inspired extensions for Chrome don't work very well, this one saved my life.

Anyway, I'm stuck with few bugs (features?) and the biggest one is the lack of possibility to completely disable all site-specific access keys (usually in DOM as accesskey attribute of different tags).

Do you think it would be possible to add some directive which would disable them? In pentadactyl, the keys which collide with pentadactyl key bindings (including user-specified key bindings) are not pass through and thus collisions never happen contrary to Vrome.

These access keys can be found e.g. in many web-based email clients (e.g. the one used by volny.cz and centrum.cz) or similar desktop-app-mimicking web pages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant