Bug 114579

Summary: EDITING:scrolling up in spreadsheet is slow/inconsistent; other scrolling ok
Product: LibreOffice Reporter: LenoreHorner
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: medium    
Version: 5.3.7.2 release   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: spreadsheet showing bad scrolling

Description LenoreHorner 2017-12-20 03:57:10 UTC
Description:
When I open a large spreadsheet with much conditional formatting and try to scroll up using two fingers on the trackpad, often nothing happens.  Sometimes a few lines scroll.  It takes several strokes to accomplish anything and I cannot predict how far the sheet will scroll for any given motion.  Scrolling down on the other hand is consistent, always responds immediately and I can predictably scroll the amount I intend to.  Left-right scrolling also behaves smoothly and predictably.

Steps to Reproduce:
1.Open LibreOffice on MacBook Air running 10.12.16
2.Open attached file.
3.Stroke down on trackpad with two fingers (this works fine).
4.Stroke up on trackpad with two fingers (scrolling probably won't happen, but eventually will a little)

Actual Results:  
scrolling happens sometimes, for part of the motion; up and down behave very differently

Expected Results:
scrolling happens smoothly every time from start of motion to end of motion; up and down should behave symmetrically


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 5.3.7.2
Build ID: 6b8ed514a9f8b44d37a1b96673cbbdd077e24059
CPU Threads: 4; OS Version: Mac OS X 10.12.6; UI Render: default; Layout Engine: new; 
Locale: en-US (en_US.UTF-8); Calc: group


User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:57.0) Gecko/20100101 Firefox/57.0
Comment 1 LenoreHorner 2017-12-20 03:59:03 UTC
Created attachment 138541 [details]
spreadsheet showing bad scrolling
Comment 2 Telesto 2017-12-20 16:49:15 UTC
A known issue, thanks for reporting anyway

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