[Webkit-unassigned] [Bug 92589] New: Send NoPart as pressed to scrollbar when mouse is out of it.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Jul 28 21:25:34 PDT 2012


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

           Summary: Send NoPart as pressed to scrollbar when mouse is out
                    of it.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Event Handling
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: carloschilazo at gmail.com


Coming from: http://code.google.com/p/chromium/issues/detail?id=43170

What steps will reproduce the problem?
1. Left-click on the scrollbar
2. while holding the left button down, move to the web content
3. right-click (still holding the left button down) - a menu should appear
4. release both mouse buttons
5. move back to the scrollbar

What is the expected output? What do you see instead?

the scrollbar will behave, as if you'd still had the right button down.

I have reproduced the issue in: Chromium Linux, Chromium Mac & Safari Mac


Proposed patch sets NoPart as pressed in the scrollbar when we move the mouse out of it
*NOTE*: this still allows to keep the scrollbar pressed and move the mouse in any direction and the scrollbar will follow while holding the click. (because ScrollableArea::mouseExitedContentArea is called AFTER the mouse click is released)

With the patch: when the user issues another event, (is when ScrollableArea::mouseExitedContentArea actually gets called) the scrollbar selection is now clear to avoid weird stuff like in the mentioned bug/steps; and also this enforces the logic that while the cursor is out of the scrollbar we are not selecting any portions of it with the mouse.

I get no regressions introduced from this

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



More information about the webkit-unassigned mailing list