Bug 457887 - ScrollView Rework Causes scrollbars to be invisible neochat
Summary: ScrollView Rework Causes scrollbars to be invisible neochat
Status: RESOLVED DUPLICATE of bug 456574
Alias: None
Product: frameworks-kirigami
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: Master
Platform: Neon Linux
: NOR normal
Target Milestone: Not decided
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-14 17:05 UTC by James Graham
Modified: 2022-08-15 17:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Graham 2022-08-14 17:05:27 UTC
SUMMARY
***
Recently when developing on neochat I noticed that the scrollbars were not being shown. This was happening on master, my patch branch and even on the release version after investigation. This seemed to coincide with an update to kirigami on my Neon Dev VM. I also saw that the scrollbar was missing in the left menu of the system settings app. 

The missing scrollbars were on the main window and room list of neochat, both scrollable pages. So going back through the commits I could see the recent one to port away from internal scrollview commit c28dff79721d3805edcd413ef233216b3b3b0104. By reverting this the scrollbars were restored.


STEPS TO REPRODUCE
1. Update to latest kirigami master
2. Open neochat

OBSERVED RESULT
Scollbars missing for scrollable pages all the time

EXPECTED RESULT
Scrollbars should be visible when required


SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.25.80
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.15.0-46-generic (64-bit)
Graphics Platform: X11
Processor: 1 × AMD Ryzen 5 3600 6-Core Processor
Memory: 3.8 GiB of RAM
Graphics Processor: SVGA3D; build: RELEASE; LLVM;
Manufacturer: innotek GmbH
Product Name: VirtualBox
System Version: 1.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-08-15 17:33:24 UTC
It's actually a Qt bug; see Bug 456574.

The Kirigami commit in question triggered this issue due to that Qt bug, and reverting that commit fixes it in some places, but not all. The real solution is to fix the Qt bug, and there is an open patch for it.

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