Kickoff 4.8.x: Good 'bugfixes', or unacceptable enhancements?

[Rick Stockton]

As you know, I propose to resolve the "missing back button" bug 
supporting the "Back" button on the mouse instead (with no visible 
changes to GUI layout.) Original BugID 
https://bugs.kde.org/show_bug.cgi?id=274489 , my BugID for the 
mouse-based alternative https://bugs.kde.org/show_bug.cgi?id=289519.

I can easily provide this in both 4.9 (QML) and the 4.8.x Widget-based 
Kickoff. Both are easy to accomplish, but when do I "cross the line" 
into an unnacceptable level of new features, added into a minor Release 
of 4.8.? These ARE "new features". But IMO, we might consider at least 
one of these because of the GUI "Back Button removal in 4.6 -> 4.7. And 
because of all the Bug votes and recurring mail messages.

Martin, Aaron, I will follow your instructions. If I'm seeing things 
correctly, this would all occur within kickoff/ui/flipscrollview.cpp, 
and I see 4 alternatives:

(1) Back Button alone. We would test "if (event.button == 
Qt::XButton1)", separating that button from other possible buttons. I 
don't recommend this AT ALL, because there are lots of mice with tilt 
wheels and no side buttons....

(2) Back Button or a "Scroll-Left" wheel event. Do the exact same "back" 
functionality for both input methods.

(3) Add Arrow Key support on the Keyboard (all 4 directions, including 
the 'Left' Arrow).

(4) Do nothing for any upcoming 4.8; even though they somewhat replace 
the old Back Button, these constitute FEATURES, not bugfixes. Postpone 
until the 4.9 QML version is being worked on.

- - - - -
Which do you guys choose for me?
Thanks in advance, Rick.