-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Scrolling doesn't work on Gmail #3216
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
Comments
Also doesn't work well with Google Docs and Google Sheets. Might be a general issue with Google webapps as they generally implement their own suite of keybindings. |
Vimium is disabled by default on GMail. You can enable it by removing the rule either in the popup or on the options page. Is that the issue, or is there something more? And re. Google Docs and Sheets... Yes, those pages do not play nicely with Vimium. Don't know how to solve it. I just disable Vimium, myself. |
This is because the scrollable areas in Gmail are scrollable divs. Related issues:
A simple workaround is to hit The message list ( If this isn't working, then you need to enable Vimium in Gmail. Here is my configuration that partially enables Vimium in Gmail. I have disabled all the native Gmail shortcuts via the 'Keys' field. Pattern: Notice I have disabled uppercase I have also changed the Gmail-shortcut for 'Remove label' from To edit Gmail keyboard shortcuts you need to enable this via EDIT: In single email view, the 'Primary' tab click workaround isn't possible. So you can click here: |
(dusting off this old thread) Thanks @benwoodward for your helpful and detailed note! I've been using this workaround for years, although really wish there was something that worked better here. One potential feature request that would make life better: visually differentiate hints that activate the scrollable divs, like what is seen with filtered links. This is discussed here and here, although not much has happened over last couple of years. |
Seeing this issue with scrolling and also find.
The text was updated successfully, but these errors were encountered: