Version: (using KDE KDE 3.5.4) Installed from: Slackware Packages OS: Linux When a tab bar becomes too long so that it gets scroll buttons, mousewheeling on those scroll buttons should scroll the tab bar (like clicking on those buttons does), instead of switching to each tab consecutively. The reasons: repeatedly clicking on the scroll buttons, or pressing the button down to scroll the tab bar, are tiring operations. The mousewheel is traditionally used for scrolling, and therefore makes this task much easier. Switching between tabs often means loading multiple documents into the UI, which is usually slow and/or causes flickering, so it's usually more desirable to scroll the tab bar until the user sees what he/she wants, and select it with a click.
I have made a screenshot illustrating this bug: http://heybryan.org/shots/2008-05-25_bug132480.png I hope this helps. /me goes off to find a vertical taskbar that can really do scrolling. - Bryan
Created attachment 29847 [details] Patch/fix for bug 132480.
There is confusion in this report... Yaohan was talking about tabbars (like konqueror's tabs, for example), while Bryan's screenshot and patch is about the kicker task bar - which is obsoleted by plasma in KDE 4. So, back to the tabbar: indeed the mouse wheel changes the active tab rather than scrolling the tabbar. This would be a Qt issue, though, should be reported at http://bugreports.qt.nokia.com (not doing it myself because I see more pressing bugs right now ;)
Why is it solved, is it because it was reported on KDE3? For me this is still an issue in 4.4. The current behaviour is really annoying if you work on a touchpad with sidescrolling. IMHO this should be implemented in QT (if it isn't already) and there should be a global option somewhere in system settings. This tab bar behaviour (toghether with lack of good dragging/reordering support) is what drives me away from using konqueror and it's present in Akregator which I love and use so much. p.s.: A hug for all KDE devs, I love KDE s.c. :)
"Why is it solved" -> see the resolution, which is: UPSTREAM. As I said, this is a Qt bug/missing feature, so it should be reported at http://bugreports.qt.nokia.com