This bug should probably be reassigned to QT then.That said, it would be very useful if you could check if this bug appears only with musescore or if it's the same with other QT related software.
Cheers.
Talking with upstream (lasconic) a few minutes ago, he thinks that
musescore is relying on QT for this.
