Popup in text editing passes keyboard input to random destinations
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
Double click on the title in a score to enter text editing mode. In the popup, click on font selector (looks like dropdown, but unfolds as another popup). It might be hoped that the font list accepts keyboard input for quick navigation, but no. Instead, the list passes keys in unexpected ways. For example, s would go to text input field (possibly obscured by the list); r would go to directly to score - creates error message box about rests.
Input processing should be context dependent. In this case, the font list should handle all keyboard input and either process it or discard.
User should easily understand where input goes, and unhandled keys should not be redirected - to score or other destinations.
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
4.6.4
Regression
No.
Operating system
Windows 11 25H2
Additional context
Older issue on mostly the same subject - #24756.
Checklist
- [x] This report follows the guidelines for reporting bugs and issues
- [x] I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- [x] I have attached all requested files and information to this report
- [x] I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Quick-focus by pressing a letter with a dropdown open is logged as a request here: https://github.com/musescore/MuseScore/issues/16508
Perhaps a smaller fix would be to make the above work just for dropdowns first (not context menus yet, if that's more complicated).
Otherwise, if we can't fix that, we should just disable keyboard shortcuts when a dropdown is expanded in the interim.
I cannot reproduce this as described in the description above.
From what I can see, pressing keystrokes while the text styles widget is open simply inputs text in the associated text field.
https://github.com/user-attachments/assets/434c03b2-9ad8-4181-9ded-13a568575a75
The obviously desirable behaviour here would be initial letter navigation, as described here.
Could you perhaps upload a screen recording to show us what you're experiencing?
There is nothing to record without keyboard visualizer (could it modify input behaviour by changing focus briefly?).
Created new score, double clicked on title, clicked on the font selector, pressed r key while dropdown is visible and got this message box.
Key s still goes to the text as in your video.
Just in case, installer was MuseScore-Studio-4.6.4.253351238-x86_64.msi.
I can't reproduce the case when pressing R either, but found that these shortcuts will open various dialogs/panels while dropdowns are open:
- I opens the instruments dialog
- O opens the percussion panel
- P opens the piano keyboard panel
Also, focus seems to move back to text entry if I type three different characters in quick succession—the third one will get typed into the field, and anything else I then type afterward.
Same here for i, o and p keys. Quick typing trick suggests timing/synchonization dependence and this could be the reason why r does nothing special in your case.
Probably, no keys should bypass this font list popup; all keys should be processed internally or discarded.
If for some reasons it is impossible to use something like Windows' SetFocus(), then it should be emulated internally in program's logic.