Drop down fields (Select elements, input element date, time etc.) are not yet supported in Smart Go Next. Few of the points I considered here are as follows;

1) Current Smart Go Next won't dismiss IME at any time, meaning it will always trigger focus to an editable input field. So user can see continue inputting contents inside form and whenever he wanted to go next field, he can press "NEXT" because NEXT is always there as part of IME. This is kind of a better state now.
2) If we start supporting drop down elements, checkbox, radio button etc. IME will be dismissed when user presses NEXT from an text field while moving focus to Drop down elements, and there is no way, we can show "NEXT" as part of drop down elements. User has to again touch on editable field to bring back IME.

So I am not sure, do we really wanted to support Drop down elements as part of Smart Go Next by compromising few above points.

kochi@ and changwan@ - Could you share your opinion on above thoughts ?

Removing Restrict-View-Google / ReleaseBlock-Stable.

Considering the feature is only available on Androids with touch-screen
and on-screen keyboards, selecting dropdown box is not what we want to do
using on-screen keyboard, and the current behavior looks reasonable.

So it may be something that on-screen keyboard can control (e.g.
typing "J" will jump to one in the dropdown list which starts with "j"),
but as current Android + on-screen keyboards don't work that way,
this can be closed as "WontFix"?

IMO, the user should be able to fill out form data in the right order. If pressing 'next' button skips dropdown / checkbox, then the user should come back to or completely skips the missing field, which can be very confusing.

#8 is giving another angle of form filling scenario. Visually user feels some field is getting missed (Select Element and any drop down element say Date etc. has more significance here, probably checkbox and radio has less significance, not sure though). So I think we should avoid any confusion to the user in all possible cases.
Shall we go ahead in supporting Select Element and other drop down elements ?

Yes, My concern is same as #8. User can unknowingly miss a field in a given form.

Thanks Ashwini for verifying Smart Go Next and reporting issues.

kochi@ and changwan@ - I am planning to extend Smart Go Next by including Select elements and Drop Down elements. If you have any suggestion, please let me know

Are there native apps that supports sending prev/next information
to on-screen keyboard, and have an input form with text fields and
at least one select or checkbox that we can study the behavior as an example?

@kochi - I am not sure any native app is supporting this model. I will check few apps, but target app set might be huge.

Hmm... I cannot think of a native app that has this. It might be easier to create an app and test it using android studio.

 Issue 854193  has been merged into this issue.