Comment 1 for bug 1793773

Confirmed by SCLENDS (3.1.8, Google Chrome). Here is how one SCLENDS cataloger describes the web client change versus XUL:

"My biggest annoyance and time swallower is that you never know when adding a subfield or adding a field where the cursor is going to end up. Before, we knew the cursor would advance to the place where we could start typing, so we didn’t have to constantly eyeball the screen. Now, if you don’t watch it, you can end up wiping out the text in a subfield or field because the cursor didn’t advance."

The cataloger points out that it slows the natural workflow of cataloging by introducing the need to keep a close eye on where your cursor is. Many catalogers can "type" through a MARC record very quickly: in other words, for a cataloger, this is like typing a document but not being sure where the space bar will land your cursor (weird example, but I hope it helps explain why this is important to catalogers).

A related complaint is that it's difficult to undo the accidental deletions that result from this behavior. Current workaround is putting the cursor in the field where you accidentally deleted information and using CTRL+Z to resurrect the text letter-by-letter.