quickMARC: Keep the user's focus when user hits Save & keep editing

Works as noted in requirements. Will write additional stories related to

• Inline errors focus

• Modal focus handling

Tests are updated according to clarification. Ready for PO review.

Case 3 = Works as expected
Case 8 and 10 = KG to create a story for handling modals and return to focus

Case 12 = Works as expected

Tested on Sprint testing environment for MARC bib, MARC authority, MARC holdings records:

Case 1 - user updates subfield of any field - works as expected.
Actual result: Focus stays in the last updated field.
See attached screencast:

Case 2 - user updates any field - works as expected.

Actual result: Focus stays in the last updated field (MARC tag box)
See attached screencast:

Case 3 - user updates any indicator box - question.
Actual result: Focus stays in the last updated indicator box, but value is highlighted. Should we fix it?
See attached screencast:

Case 4 - user updates position of “008” field - works as expected.
Actual result: Focus stays in the last updated position.
See attached screencast:

Case 5 - user updates position of “LDR” field - works as expected.
Actual result: Focus stays in the last updated position.
See attached screencast:

Case 6 - Move icons - works as expected.
Actual result: Focus stays in the last clicked arrow icon
See attached screencast:

Case 7 - Delete field - works as expected.
Actual result: Focus stays on the moved down icon placed next to deleted field
See attached screencast:

Case 8 - Update 1XX of linked MARC authority record - Question
Actual result: Focus doesn’t stay in 1XX field after saving. Should we fix it?
See attached screencast:

Case 9 - Update Location of MARC holdings record - works as expected.
Actual result: Focus stays in “Permanent location look-up”
See attached screencast:

Case 10 - Link MARC bib field with MARC authority - Question: Where should focus go?
See attached screencast:

Case 11 - Edit editable boxes of linked MARC bib field - Works as expected.
Actual result: Focus stays in edited box.
See attached screencast:

Case 12 - Perform some update >> move focus to another (not edited) field >> Click on the “Save & keep editing - Question, is it expected to leave focus in not updated field in this case?
See attached screencast:

Hi - please review cases marked with Questions and provide expected results for them. And if you see some other cases, please share.

Hey - when we save a record, for optimistic locking we check instance._version from inventory/instances/id. Does this guarantee that fields from records-editor/records?externalId=id were not updated too and we don’t need to request fields again? In the current implementation, we request fields again after saving the record and it interferes.