https://bugs.documentfoundation.org/show_bug.cgi?id=155422

            Bug ID: 155422
           Summary: Scrolling in Heading style widget on Kde Wayland skips
                    elements
           Product: LibreOffice
           Version: 7.5.3.2 release
          Hardware: All
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
Scrolling with the mouse in the heading style chooser widget skips at least one
row of available styles. If i use the keyboard arrows it select the next
element, as it should be(but still jumps around confusingly). 

I also can't drag the scrollbar with the mouse at all. 

As a result i can't select any of the styles which come 
immediately after heading 1

There is also a tiny target directly above and below the scrollbar where you
can click to scroll by 1 pixel, like an invisible arrow.

Launching Libreoffice with 

SAL_USE_VCLPLUGIN=gtk3 libreoffice 
or
SAL_USE_VCLPLUGIN=gtk4 libreoffice

the scrolling works just fine and is much smoother.

-I've attached a small video demo. In the video i first scroll with the mouse
wheel, then i try to drag the scrollbar and then i use the keyboard arrows. 

Issue is also the same on x11.


System info: 
Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Graphics Platform: Wayland

Steps to Reproduce:
1.Open Libreoffice writer with the Tabbed interface
2.Try to scroll in the Heading style chooser 
3.Try to drag the scrollbar 

Actual Results:
The scroll jumps too much and skips entire rows

Expected Results:
The scroll works smoothly


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.5.3.2 (X86_64)
Build ID: 50(Build:2)
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+wayland)
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to