After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 641514 - incorrect scroll bar mouse motion feedback processing
incorrect scroll bar mouse motion feedback processing
Status: RESOLVED NOTGNOME
Product: epiphany
Classification: Core
Component: Backend
2.30.x
Other Linux
: Normal minor
: ---
Assigned To: Xan Lopez
Epiphany Maintainers
Depends on:
Blocks: motion-event-tracker
 
 
Reported: 2011-02-04 16:07 UTC by Stanislav Brabec
Modified: 2016-02-28 17:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stanislav Brabec 2011-02-04 16:07:47 UTC
Scrolling in Epiphany incorrectly implements mouse motion feedback.

How to reproduce:

1. Load a complicated and slowly rendered page. Example: http://www.cesweb.org/awards/innovations/2010honorees.asp from https://bugs.webkit.org/show_bug.cgi?id=33366

2. Drag the scroll bar.

3. Quickly move scroll bar to another position.

4. Quickly stop the scroll bar and stop moving.

Actual result: Page stays scrolled at the position before the quick move. Scrolling happens after mouse button release.

Expected result: Scroll immediately and try to follow the mouse. (When no events come, page rendering should correspond to the latest available mouse position.)

It is not clean, whether it is a problem of GTK+, WebKit or Epiphany. I am reporting it here for now.

This bug fulfills all symptoms of motion-event-tracker bug pattern: https://bugzilla.gnome.org/show_bug.cgi?id=573154
Comment 1 Michael Catanzaro 2016-02-28 17:09:10 UTC
Hi, this appears to be a bug in WebKit.

If you are still able to reproduce this issue with WebKitGTK+ 2.10.6 or 2.10.7, please consider filing a bug on bugzilla.webkit.org. (To find your WebKitGTK+ version, open Epiphany's about dialog from the app menu.) When filing the bug, be sure to select the WebkitGtk component (else the bug will likely not be noticed) and to use the prefix [GTK] as the title of the bug. This will help the relevant developers find your issue.

If you think this issue is not a WebKit issue and was closed in error, please do leave a comment or reopen.