https://bugs.kde.org/show_bug.cgi?id=457409
Bug ID: 457409
Summary: Accidentally moving out of tab bar's y-coordinate
range stops movement
Product: kate
Version: 22.04.3
Platform: Other
OS: All
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: dchme...@gmail.com
Target Milestone: ---
SUMMARY
Accidentally moving out of tab bar's y-coordinate range stops movement.
STEPS TO REPRODUCE
1. Try to move tab.
2. Keep moving but accidentally slightly move above or below tab bar.
3. Tabs tops and one must move back within tab bar's y-coordinate range--often
multiple times--to resume moving.
OBSERVED RESULT
Accidentally moving out of tab bar's y-coordinate range stops movement. Tab
stops and isn't even positioned right but a space appears... one must move back
within tab bar's y-coordinate range--often multiple times--to resume moving.
EXPECTED RESULT
Ingore y-coordinate moving tabs; let user continue: only keep checking
x-coordinate.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Slackware64 15
KDE Plasma Version: 5 to 5.25.3
KDE Frameworks Version: 5 to 5.96.0
Qt Version: 5 to 5.15.5
ADDITIONAL INFORMATION
Despite TVs get larger & larger, monitors with comparative resolution get
smaller & smaller: much, much smaller pixels than older monitors, so some 8K
are same size as 4k are smaller than some 1080p. All GUI elements get too
small: panels, titlebars, menubars, toolbars, tabbars, infobars, scrollbars, so
you CANNOT assume a user will even easily be able to stay within an element's
range when still acting on it so absolutely shouldn't expect/make them to.
Best/original tab definers like Firefox don't care if you move out of tab bar
y-coordinate range. Worst UI implementers such as Google (zero design sense)
do same and worse--if you move out-of-range tab will pop out as a new window.
Best to not do that and not stop until user releases (unless some users want
option if they move out-of-range, then stop, but would they be crazy or what?)
--
You are receiving this mail because:
You are watching all bug changes.
