Agree 100%. There are many cases where it easy to lose the location on the page, specially when things that are not clicks say "click here". You try to open them in a new tab with middle-click and oops you lose where you were because it was not a link but an onclick handler for example (UPS tracking confirmation emails do this). Plus, there is simply the case where you miss a genuine link. It used to happen to me dozens of times a day which got very frustrating. There is no solution yet but to compile WebKit without PAN_SCROLLING enabled.
There is a bug open on WebKit for them to have them to have this option. Until that or something more generic gets addressed we cannot have a solution in Chromium. Even if it does, a more generic solution where say an extension can control the behavior will probably be preferred as to not have to add an option to Chromium. - Itai On Jul 9, 8:57 am, Philippe <[email protected]> wrote: > I second that middle clic is a serious issue. I find that deactivating > the autoscroll with a second clic is really annoying. > > On Jul 6, 2:17 am, Zr40 <[email protected]> wrote: > > > > > Autoscroll is middle-clicking on a page and moving the mouse, so that > > the page scrolls in that direction without any effort. > > > I can see why autoscroll is useful for some power users. But for other > > users, including other power users, this feature is annoying. An often > > cited example is trying to middle-click a link but misclicking. This > > happens either because of actually misclicking, or accidentally > > scrolling (for most users, the middle mouse button is also the scroll > > wheel). This activates autoscroll. The page can scroll off, but even > > if it does not, it requires a second click to deactivate autoscroll > > before the link can be clicked again. > > > The root issue behind this is not misclicking, but the unintuitive > > multiple meanings for the middle mouse button. Middle clicking on a > > tab can only close the tab, and this is intuitive because the tab is a > > distinct visual element. Middle clicking on a navigation button can > > only open the previous/next page in a new tab. This too is a distinct > > visual element. > > > However, links are not distinct visual elements, and don't even need > > to appear as links at all. There can also be non-link elements that > > appear as a link. This actually presents two problems: how can the > > user indicate he wants autoscroll when the mouse is over a link, and > > how can the user indicate he does not want autoscroll when not over a > > link? > > > There have been several issues created about this in the Chromium > > issue tracker. All of them have been merged into issue 12478, which > > has been closed WontFix. However, there has not been any explanation > > at all about why an option to disable autoscroll, hidden or not, will > > not be added. > > > Can the reason for not implementing the option please be explained? Or > > even better, can it be implemented? --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
