Bug 270367

Summary: Rekonq has issues with pressing both mouse buttons on scrollbar
Product: [Unmaintained] rekonq Reporter: Frank Steinmetzger <dev+kde>
Component: generalAssignee: Andrea Diamantini <adjam7>
Status: RESOLVED WORKSFORME    
Severity: normal CC: codestruct
Priority: NOR    
Version First Reported In: 0.7.0   
Target Milestone: 0.10   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Frank Steinmetzger 2011-04-07 22:12:46 UTC 
Version:           0.7.0 (using KDE 4.6.1) 
OS:                Linux

Rekonq somehow has a hickup with its reaction to mouse clicks on the scrollbar.
Using single LMB or RMB has the expected result (scroll by screen page or show context menu, respectively). But when both buttons are clicked, the scrollbar shows some strange behavior.

Reproducible: Always

Steps to Reproduce:
- Press and hold the LMB on the scrollbar area.
- Press the RMB
- now the scrollbar’s top edge jumps right to the cursor position and the context menu appears.

Actual Results:  
If the menu is closed by clicking it away (i.e. clicking outside of the menu), the scrollbar starts following the vertical position of the mouse cursor, no matter where on the screen that cursor is and even without me pressing down any mouse button.

Expected Results:  
Said following should not occur.
Comment 1 Andrea Diamantini 2012-01-04 13:02:52 UTC 
Is this yet happening using rekonq 0.8.x and qtwebkit 2.2.x ?
Comment 2 Frank Steinmetzger 2012-01-04 15:24:43 UTC 
I still have it in rekonq 0.8.1, KDE 4.7.4. However, my qt-webkit version is 4.7.4 also.

After the context menu appeared and I clicked it away, the scrollbar doesn't follow when I'm moving the mouse cursor in the client area. But it does when I move the cursor over the scrollbar area. Only after a click onto the scrollbar the following finally stop.
Comment 3 Andrea Diamantini 2012-09-18 19:36:54 UTC 
Someone needs to test this with rekonq 1.x and qtwebkit 2.2.x. This works for me :)
Comment 4 Gregor Mi 2018-04-10 13:51:59 UTC 
I close this bug due to age. Feel free to reopend if the problem persists.