Subfields problem in 111 and 711

I'm having trouble reproducing this in my current 2.0.0+ instance, so
perhaps the bug has already been fixed. The validation control map in
marcedit.js says that 711 $a,$c,$d is supposed to be controlled by 111
$a,$c,$d - and doesn't attempt to control the $n or $0 subfields, so
those shouldn't be an issue.

Are these the right steps to follow?

1. Add a 711 field to a bibliographic record with subfields $a, $n, $d, $c
2. Right-click on the 711 field and select "Create new authority ->
Immediately". The $0 subfield will be added to the 711 field.
3. Click "Validate" in the MARC Editor for the bibliographic record.

When I click "Validate", the 711 field stays black.

I did exactly the same steps, but after the click "Validate" the 711 became red!

Okay. So either the underlying bug has been fixed since 2.0 RC2, or
there's something specific to the data that you're using that's
triggering the problem.

I suspect it might be the latter; I resolved a problem last week in
which the data from the MARC Editor was not being normalized to the
same format that the data in the database uses, and therefore was
returning incorrect matches.

Can you paste the exact data that you're using?

Confirmed that some combinations of cursor positioning can trigger this bug.

The problem is that the new ID subfield was getting inserted into the wrong location in the DOM for the XUL display - but not in the MARCXML. A workaround is to switch to the flat-text editor, then switch back to the classic MARC editor; the XUL elements will be recreated based on the MARCXML and the Validate button will work as expected.

Committed a fix in r19402 in trunk, and r19403 in rel_2_0 so that this can go into the 2.0.2 release.