When adding an author, automatically put the cursor in the "first name" field

[mietcls]

Enhancement

When adding an author, automatically put the cursor in the "first name" field.

Context: when librarians add people, it is an extra action to undertake and slows them down unnecessarily. If their cursor would already be in "first name" they can always use the tab to got "last name" if needed.

Current behaviour

1. Go to any publication or dataset, and navigate to People & Affiliations
2. Click "Add (author, editor, supervisor, ...)"
3. To start searching for a person, first click on "first name"
4. Start typing

Expected behaviour

1. Go to any publication or dataset, and navigate to People & Affiliations
2. Click "Add (author, editor, supervisor, ...)"
3. Immediately be able to start typing in the "first name" field

[nicolasfranck]

Why not for every form? This is done often.

[mietcls]

After discussing:

• We can focus on the input form where it makes sense
• The focus state lies on the first field: input, select, text area, .. each first field (not the first text input only). --> This needs to be in line with accessibility guidelines, HTML structure and tab order.
• For this we should probably make an epic and list the ones that need it (to be able to discuss with librarians/researchers if there's an issue or unclarity)
• the focus state needs to be more clear, which is a separate issue.

[nicolasfranck]

Some behaviour I noticed when autofocusing a select box:

Now use the scroll on your mouse:

So someone who uses his/her mouse to scroll down the page, accidentally scrolls down the selectbox.

To reproduce:

• type in the javascript console: document.querySelector("select").focus() and then close it
• scroll down or up

[mietcls]

@nicolasfranck is your mouse on the select box? I can't seem to reproduce it. We can call / or show me live.

[mietcls]

Is this one done, or is there something missing?

Edit: we decided to only do it for "first name" and will review the interaction as a whole. This issue is still relevant for now.

[mietcls]

The first- and last name search boxes are now switched.

Current behaviour:

First name search box looks for last name, last name search box looks for first name.

Expected behaviour:

First name search box remains in first place and looks for first name, last name search box remains in last name place and looks for last name.

[mietcls]

!! Leave as is right now, because:

We don't always have correct data now (e.g. people whose first name is surname and vice versa) - or we don't always know what is what (people with no surname or first name). So it is good to be forgiving, but we can break the odd pattern later (this is not consistent with expectations).

You would not expect to find "Jolien Danneels" when typing "Dann" in the first name area.

But keeping people from being able to find this can also be very blocking.