I have just created a simple form with a Select_one with the appearance columns-2 quick within a GROUP which has the appearance field-list (to display 3 related questions).
When testing the form (oh yeah!) I noticed that the auto-advance actually moves to the next GROUP not the next QUESTION as indicated in the Docs. Same issue with just quick appearance, so it's not the columns causing the "problem".
This is unexpected behaviour (in terms of what the Docs say https://docs.getodk.org/form-question-types/#select-widget-with-autoadvance) - I was hoping that the form would advance to the next QUESTION (which is an integer) so that I can type a number without needing to change question focus first. [my form is very short, for rapid and repeated data entry so the fewer taps, the better!]
If this behaviour is intended, please can you update the docs to provide a note that auto-advance moves to the next question OR group (if the appearance field-list is used).
Otherwise, it might be a minor bug...
It feels counter-intuitive for a select_one to skip other questions on the same "screen" (my use case being that I group questions if they are logically connected, such as describing a single object or data point).
Which reminds me that in previous forms where I have a mix of integer and selects in a field-list group, I recall that when I complete the select, the focus for text / numbers remains with the previously answered question (i.e. you can end up adding to a previous number by mistake) - and of course I couldn't use auto-advance... If the quick behaviour changed, that would solve this issue too:
Q1 - how many can you see (integer) --------- response: 5
Q2 - are they all alive (select_one - appearance columns-2) ------- select: yes
Q3 - how tall is the tallest in cm (integer) ------- response: 314
After answering questions 1 and 2 the 'integer keyboard' remains on screen but the focus is still on question 1, so it is common to just type a number and Q1 response becomes (in this case) 5314 and Q3 is blank / null. Not everyone catches the fact that the number appears in the wrong box (or remembers the behaviour)... It would be more helpful if the keyboard was hidden for select questions (that don't include search) - then at least the enumerator can't answer / change the wrong question by mistake / lack of attention (I'm holding my own hand up here!). I know that another solution is not to use field-list appearance for groups in these situations...
Apologies if this has been raised elsewhere - I couldn't find a related question, and the Docs probably would benefit from the clarification, if this is all as intended...