https://bugs.kde.org/show_bug.cgi?id=482149
--- Comment #7 from Felix Ernst <felixer...@kde.org> --- (In reply to András Manţia from comment #5) > This bug is even more annoying than I thought: the shortcut keeps resetting > itself That would be annoying but it would be considered unrelated to this bug. (In reply to Ivan from comment #6) > (In reply to Felix Ernst from comment #4) > > I am not sure "being conservative" works here. When a completely blind > > person sits in front of Konsole and tries to go to the menu F10 is their > > only option AFAIK. Take that away and they can't even open the help menu > > AFAIK. > > > > That's why I suggested that Konsole should only give up control of the F10 > > key when the current terminal application uses it. This way the general > > accessibility of Konsole doesn't have to suffer just because some terminal > > applications also want to use F10. > > I disagree. F10 is often used in terminal applications. People are used to > Ctrl+C and Ctrl+V and other common shortcuts, but that's not how it works in > Konsole. The same should be applied to F10 and F11. > > I'm pretty much blind and when I'm using terminal apps like I'm used to > instead of getting F10 action from my application I'm getting some useless > menu. > > In my opinion this is serious bug Of course any change we ever make (even if it is during a major transition from Qt 5 to Qt 6 like this) will go against previously expected behaviour. I don't really see though in what way what you are saying disagrees with me. I do agree with your point that it is unwanted when a terminal program's F10 shortcut doesn't work because it was stolen by Konsole. But this doesn't change the argument I made which was: "When a completely blind person sits in front of Konsole and tries to go to the menu F10 is their only option AFAIK. Take that away and they can't even open the help menu AFAIK." -- You are receiving this mail because: You are watching all bug changes.
