Moving Chord Changes Minimum Distance to -999

[BanjoJake]

In the attached file, select the C chord in bar 6 by clicking on it. In the Inspector window, set Offset Y= -5sp.
Click elsewhere on the screen to de-select the chord, then select it again, this time set Offset Y= -1.50sp.
Click elsewhere on the screen to de-select the chord, then select it again. Note that the minimum distance has changed to -999, even though the original and final positions are well above the staff line. This results in various other downstream misbehavior.

Also happpens when the chord symbol is moved with a mouse.

Observed in MuseScore (64-bit):
3.7.0.9481291153 / 5518553 on Windows 10 3.6.2.548021803 / 3224f34 on Windows 11

Moving Chord Changes Minimum Distance to -999.zip

[BanjoJake]

According to musescore.org/en/node/322365#comment-1085645, Musescore intentionally sets the minimum distance to -999 if an item is moved too close to the staff. Whatever that threshold distance is, it should be reduced (or the behavior omitted entirely) for chord symbols.

[BanjoJake]

Work-around is to turn off Automatic Placement,

[BanjoJake]

Here's an example where moving one chord changes the minimum distance of a different chord to -999. Select the G chord in bar 1 by clicking on it. In the Inspector window, set Offset Y= -5sp. Click elsewhere on the screen to de-select the chord, then select it again, this time set Offset Y= -1.50sp.
Click elsewhere on the screen to de-select the chord. Select the G chord in bar 5 by clicking on it. In the Inspector window, set Offset Y= -5sp. The G chord in bar 1 immediately jumps down and its minimum distance changes to -999..

Windows 10, MuseScore version (64-bit): 3.7.0.9493594215 / 5518553 Moving one Chord Moves Another.zip