Bug 99591 - HitTestResult::scrollbar() is NULL when hit test point is over the main scrollbars
Summary: HitTestResult::scrollbar() is NULL when hit test point is over the main scrol...
Status: RESOLVED DUPLICATE of bug 114430
Alias: None
Product: WebKit
Classification: Unclassified
Component: UI Events (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 114430
Blocks: 104369
  Show dependency treegraph
 
Reported: 2012-10-17 06:33 PDT by Carlos Garcia Campos
Modified: 2013-04-25 06:15 PDT (History)
8 users (show)

See Also:


Attachments
Patch (1.50 KB, patch)
2012-10-17 06:38 PDT, Carlos Garcia Campos
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Garcia Campos 2012-10-17 06:33:11 PDT
It works for control element scrollbars, but not for the main ones. Events are correctly propagated to the scrollbars but the HitTestResult is not updated accordingly.
Comment 1 Carlos Garcia Campos 2012-10-17 06:38:14 PDT
Created attachment 169171 [details]
Patch
Comment 2 Eduardo Lima Mitev 2012-12-13 07:10:34 PST
adding myself to CC.
Comment 3 Darin Adler 2013-01-15 15:49:11 PST
Comment on attachment 169171 [details]
Patch

What’s the visible symptom of this?
Comment 4 Carlos Garcia Campos 2013-01-15 16:06:08 PST
The problem is that if you make a hit test for any point over a main scrollbar HitTestResutl::scrollbar() is NULL, so it's not possible to know whether you are clicking in a scrollbar or not, for example. We need that in Epiphany to ignore any action associated to mouse buttons when mouse is over a scrollbar and propagate the event to webkit.
Comment 5 Allan Sandfeld Jensen 2013-04-14 05:24:11 PDT
This is probably fixed by the patch for bug 114430
Comment 6 EFL EWS Bot 2013-04-23 17:40:45 PDT
Comment on attachment 169171 [details]
Patch

Attachment 169171 [details] did not pass efl-wk2-ews (efl-wk2):
Output: http://webkit-queues.appspot.com/results/65358
Comment 7 Carlos Garcia Campos 2013-04-25 06:14:12 PDT
(In reply to comment #5)
> This is probably fixed by the patch for bug 114430

Yes, this work now.
Comment 8 Carlos Garcia Campos 2013-04-25 06:15:01 PDT

*** This bug has been marked as a duplicate of bug 114430 ***