When familysearch.com displays a form give the first field focus.
Hi @Douglas McPhaden
If you're referring to Indexing/Reviewing using Form Entry mode and changing from one "Form"/Entry to the next, if you use Ctrl+Enter to progress, you should land on the next "Form"/Entry with the focus in the first Field of that next "Form"/Entry.
Not referring to that.
The point is to avoid the need to establish focus, obviating the need to break the flow of input to establish focus. "Look ma no hands!"
Yes! The fix is just one line of code.
If I understand you correctly -- I don't have a problem with "Enter/Return" or some other single keystroke defaulting to the action of advancing to the first field of the following Entry panel after indexing the last field in an Entry -- as long as there is a way (e.g., a keyboard shortcut) to retain focus on a user-selected field other than the first field from Entry to Entry. I have found that there are situations when I want to remain in (i.e. keep the focus on) a field other than the first field on successive Entries.
I didn't follow your predicate. My desire is no strokes to begin with as the default. Examples are type or paste without having to focus. Don't understand why indexing is germane. If you need to start in a different field sometimes, do that by selecting the focus. If there are 2 types, the default should be the more frequently encountered.
For the purpose of this discussion, I'm not concerned with anything but Indexing/Reviewing. For that case/situation, the default starting focus is the first field of the first entry, and when you index the intervening and finally the last field in that entry and click Enter or Tab, you are taken to the first field of the next entry, etc. So, the default action is exactly what you seem to desire/require.
Perhaps I misunderstand what you are proposing. If you're referring to another situation/Family Search form or another mechanism, I don't have anything to add.
Indexing was not accounted for in my suggestion. In future, I will explicitly state the scope.
OK. Thanks, @Douglas McPhaden.