[Webkit-unassigned] [Bug 24722] Sticky Autoscroll Fix

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=24722





------- Comment #5 from idanan at chromium.org  2009-03-24 07:08 PDT -------
(In reply to comment #4)
> (In reply to comment #3)
> > 
> > To clarify, the issue comes from the use of middle-click on a link to mean
> > "Open In New Tab" (as it does in every tab-supporting browser) and the
> > relatively recent WebKit addition to use middle-click to initiate autoscroll
> > (which can be user-disabled in every other browser, probably for this kind of
> > usability issue). 
> 
> Maybe we should add a similar preference to WebKit.

That is fine by me.

> > There are hundreds of reasons why someone would accidentally click on something
> > that is not a link. A great example when UPS sends an email with package
> > tracking information. Next to each package number there is a UPS logo with the
> > words 'Click here to track'. Middle-clicking there just turns autoscroll on.
> > Why? Because the email they sent does not contain a link but a Javascript
> > onclick handler (which opens the tracking info in a new window or popup).
> > 
> 
> This sounds like a bug. What do Firefox and IE do here?

Don't know about IE, but Firefox has the same bug.

> > Now as for the desired behavior, here is why autoscroll should not be sticky.
> > This even works in favor of those you actually use it:
> > - Accidental autoscroll triggering (middle-click on a non-link) returns to
> > normal immediately. No action needed to get out of autoscroll.
> > - Entering autoscroll willingly, scrolling and return out to autoscroll mode
> > requires 3 action: press, drag, release. In sticky mode it requires 5: press,
> > release, drag, press, release.
> 
> Personally, I agree, but the current behavior matches the platform convention.
> I think we should maintain that when resolving the issues that people are
> having.

Glad you agree. Now I also understand the need for uniformity across products
in
the name of simplifying user experience but in this case I disagree because
being
uniform creates A usability issue. Surely we are allowed to do better than
other
browsers, not being different to be different, but to improve things further.

Given the implementation of the option as you suggested, this point would not
be
as important. I think that would be the only sensible way to deal with this if
you also want to provide the just-like-Firefox behavior.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.