[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages

2020-09-10 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=421822 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com --- Comment #11 from Kamil

[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages

2020-09-10 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=421822 --- Comment #13 from Kamil Dudka --- It might be inperfect but at least it is usable again. I am not a GUI developer either, so I will rather not touch the code myself. I would prefer if this bug was fixed by fully reverting the change that

[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages

2020-09-10 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=421822 Kamil Dudka changed: What|Removed |Added Keywords||regression -- You are receiving this mail

[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages

2020-09-15 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=421822 --- Comment #17 from Kamil Dudka --- (In reply to Nate Graham from comment #15) > Are we all talking about the same thing? Nope. For me the issue is the smooth scroll animation that blocks the scrolling. It makes it impossible to scroll la

[okular] [Bug 420755] Option to disable animated scroll transitions

2020-09-15 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=420755 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this

[okular] [Bug 422050] Scrolling issues with PageDown/PageUp navigation

2020-09-15 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=422050 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com --- Comment #20 from Kamil

[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages

2020-09-15 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=421822 --- Comment #23 from Kamil Dudka --- (In reply to Nate Graham from comment #18) > Got it. Looks like everyone's actually complaining about Bug 422050, which > was just fixed! :) Yes, I was facing exactly this bug. Thank you for pointing me