Accessibility: Next Element loses position after Delete

• Feb 15, 2019 - 15:16
Reported version
S3 - Major

If you use the Next or Previous Element commands, find something to delete, press Delete, then continue using Next or Previous Element, the score position is lost and you return to stave 1, bar 1.


  1. Create a new score, treble clef single line to demonstrate, but any template will do.

  2. Enter Note Entry mode, press N.

  3. Enter some notes, e.g. crotchet C, D, E, F, G, A, B, C.

  4. Add a dynamic forte onto any note, say the G in bar 2.
    The actual symbol you add is actually irrelevant, it could be fingering, ornament, crescendo, etc, etc.

  5. Press Escape to exit Note Entry mode. (Note, why is this step necessary?)

  6. Navigate with Next or Previous Element (Alt + Right or Alt + Left) to find the dynamic on the G.

So far, everything is working as expected.

  1. Press Delete to remove the unneeded dynamic.

Expected behaviour, the cursor should now be on the G itself.
Actual behaviour: position is lost.

  1. Press Next Element.

Expected behaviour here is that you would navigate to the A following the G, bar 2, beat 2.

Actual behaviour is that you're on the key signature at the very beginning of the score.


The practical upshot of this problem is that you must keep using the Find (Goto Bar) command to get back to the correct bar, then navigate down the voices and staffs to the correct staff, then navigate across to the correct item within the bar to continue work. This can be very tedious.


Frequency Many Once
Severity S4 - Minor S3 - Major

I think this would be a major problem (at least) if I were blind and looking at measure #425 of a 600 measure symphony movement. The frequency is set to Once since you are the only person to mention it.

Status PR created fixed

Fixed in branch master, commit f0f329edfa

_fix #284203: select note or rest after deleting attached element + collect_artifacts

cmdDeleteSelection calculates the tick of the element to select after deleting,
but children of notes and rests were not handled.
No additional handling was necessary, we just needed to expand a test to allow this._

Fix version