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

[Feature Request] Disable Middle-Click Tab-Close when scrolling #10

Open
aphirst opened this issue May 26, 2016 · 3 comments
Open

[Feature Request] Disable Middle-Click Tab-Close when scrolling #10

aphirst opened this issue May 26, 2016 · 3 comments

Comments

@aphirst
Copy link

aphirst commented May 26, 2016

If I happen to have clicked my middle mouse button to scroll upwards on a webpage, it's frustrating that, given that I'll tend to put the mouse right to the top of the screen in order to scroll quickly, another middle-click to exit the auto-scroll mode also ends up closing the tab that the mouse cursor was inevitably over.

To the best of my awareness, this does not occur in e.g. Firefox's auto-scroll mode.

It would be cool if inhibition of this behaviour were considered, if not necessarily as standard behaviour, but at least as an option, for implementation in a future release.

@Pauan
Copy link
Owner

Pauan commented May 29, 2016

That's a good idea, but it's not currently possible.

Unlike Firefox extensions, Chrome extensions are very limited in what they can do.

AutoScroll can modify webpages, but it cannot modify Chrome itself, so there's no way for AutoScroll to prevent Chrome from closing the tab.

I'll leave this issue open, in case Chrome ever adds in an API that allows for this.

@aphirst
Copy link
Author

aphirst commented May 30, 2016

Thanks for the feedback. Shame to hear that this currently isn't possible. Might it be worth mentioning to the Chrom(ium) developers at some point, perhaps simply to indicate (reinforce?) interest in such functionality?

@Pauan
Copy link
Owner

Pauan commented Jun 3, 2016

It wouldn't hurt to ask, but I think the chances of them adding in that functionality is very low.

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

2 participants