[Webkit-unassigned] [Bug 27289] New: Click/releases on scrollbars misbehave when mouse move is missed

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jul 14 22:18:01 PDT 2009


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

           Summary: Click/releases on scrollbars misbehave when mouse move
                    is missed
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: viettrungluu at gmail.com


Created an attachment (id=32765)
 --> (https://bugs.webkit.org/attachment.cgi?id=32765)
Demonstrates bug.

The bug is in WebKit/WebCore/page/EventHandler.cpp.

When a mouse click occurs on a scrollbar, but is not preceded by a mouse move
onto that scrollbar, the release is not processed correctly.

This occurs in a number of situations:
- when you move the mouse after activating a context menu, and refocus onto the
scrollbar without moving the mouse again after the context menu is gone (this
is Google Chromium bug 6823
<http://code.google.com/p/chromium/issues/detail?id=6823>;
- when a scrollbar appears due to some event (and your mouse just happens to be
in the right place to click).

This applies to enabled and disabled scrollbars; see also bug 19033
<https://bugs.webkit.org/show_bug.cgi?id=19033>.

The "context menu" incarnation happens on all current (including dev) versions
of Chromium, on Safari 3.x and 4.x on Windows; it does not occur on Safari 4.x
on Mac (don't know about 3.x; perhaps a Safari developer "fixed" it by creating
a mouse move event after the context menu is dismissed?).

The "appearing scrollbar" incarnation happens on everything I've tried
(Chromium, Safari).

Patch coming in a jiffy, as soon as I've run tests.

-- 
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