MuseScore 4's Font menu navigation regression: Keystrokes not working properly

Here on MacOS MuseScore 4 ignores well established Font menu behaviors, such as those found in:

     • in MuseScore 3's Text panel>Font menu
     • in MuseScore 3's Mixer>Sound menu
     • in Apple Pages app ...

The net result is a large waste of time because efficient menu navigate is nearly impossible. Seems like a small issue, but when one needs to change the font of several text objects—particularly objects that can't be selected simultaneously—these menu issues/oversights become painfully tedious indeed.

Presently there are at least three font menu issues in MuseScore 4

1)  Once a Text panel>Font menu is open, pressing a letter key should jump to the first font starting with that letter:

     a) this does not happen in MuseScore4's Text panel>Font menu and it's a regression.

     b) there's a focus issue where each "menu intended" keystroke goes to the score, where it can inadvertently change the letter name of the parent note of the text object. The impact is obvious when the keypress is: a, b, c, d, e, f, g.

It happens 1) when only the child text object is selected 2) when the selection contains a note and a text object simultaneously.

Other keystrokes may produce unseen effects! For instance the keystroke r tries to invoke the Repeat command, but if there's no note selected it only causes MuseScore to post an alert.

2)   Page Down and Page Up should jump an amount equal to the height of the displayed menu, but it's REALLY messed up:

     a)  Page Down instantly jumps to the top of the menu, or does so on the second press

     b)  Page Up scrolls downward through the font menu items, opposite to normal convention

3)  Down and Up cursor keys in the Text panel>Font menu:

    • The Down arrow works properly when held (i.e while stillDown).

    • Pressing and holding the Up arrow works for a bit ... but eventually invokes a jump to the top of the list.

These keystrokes work normally in MuseScore 3 on MacOS ... so the errant menu behaviors are obvious MuseSccore 4 regressions.

Can someone confirm on Windows? And on MacOS?

scorster