https://bugs.kde.org/show_bug.cgi?id=369016
Friedrich W. H. Kossebau <kosse...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Product|konversation |Breeze
Version|unspecified |5.20.3
Component|general |QStyle
CC| |kosse...@kde.org
Assignee|konversation-de...@kde.org |unassigned-b...@kde.org
--- Comment #2 from Friedrich W. H. Kossebau <kosse...@kde.org> ---
This is an issue with the Breeze style it seems. That one calculates a region
for the tab bar element in a QTabWidget which has a margin of 1 to the border:
see Style::tabWidgetTabBarRect() at
https://invent.kde.org/plasma/breeze/-/blob/master/kstyle/breezestyle.cpp#L1893
And thus as result also means that a with a tabbar placed next to the screen
border we do not get the infinite tabs which allow throwing the mouse against
the screen edge and clicking the tab easily, but instead enforces to properly
target them instead (something with Fitt's law and stuff).
With styles like Plastique, Windows or QtCurve that is not an issue.
I do not think we should try to workaround this in Konversation. Instead this
is a principle issue with the Breeze style.
That 1 pixel margin seems wanted for design issues, to not blend the outshape
lines with that of neighbouring elements I guess.
Yet to help with that case of screen edges, the active tab range should still
include also that margin pixels IMHO.
--
You are receiving this mail because:
You are watching all bug changes.
