Bug 393697 - [vertical tabs] first tab not fully visible on popup show
Summary: [vertical tabs] first tab not fully visible on popup show
Status: RESOLVED DUPLICATE of bug 395390
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) (show other bugs)
Version: 5.12.4
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-30 19:16 UTC by Dmitry Khlestkov
Modified: 2018-10-20 15:46 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
"after" the commit (230.09 KB, image/png)
2018-04-30 19:16 UTC, Dmitry Khlestkov
Details
"before" the commit (230.79 KB, image/png)
2018-04-30 19:17 UTC, Dmitry Khlestkov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Khlestkov 2018-04-30 19:16:47 UTC
Created attachment 112329 [details]
"after" the commit

This started a couple weeks ago. I've tracked the issue down to specific commit: https://phabricator.kde.org/D11098

before the commit vertical tabs are working as expected, but after the commit first tab is not fully visible when kickoff is opened for the first time. Clicking on any other tab (or hovering mouse if "Switch tabs on hover" is enabled) forces the tab to slide down back into place (the kickoff popup can be closed/reopened but the issue persists until any other tab is activated).

P.S.
Horizontal tabs are working as expected both before and after the commit.
Comment 1 Dmitry Khlestkov 2018-04-30 19:17:30 UTC
Created attachment 112330 [details]
"before" the commit
Comment 2 Alexander Mentyu 2018-09-24 16:08:47 UTC
Can reproduce this bug also on Wayland - both in left and right panel positions

Operating System: KDE neon Developer Edition
KDE Plasma Version: 5.14.80
Qt Version: 5.11.1
KDE Frameworks Version: 5.51.0
Kernel Version: 4.15.0-34-generic
Comment 3 Alexander Mentyu 2018-09-26 09:24:41 UTC
*** Bug 398423 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2018-10-20 15:46:49 UTC

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