So, this is what made it work for me:
Assuming all the form input fields are grouped under the same class="form-control" tag, the browser will provide the most logical tab order for you.
There is actually no use case (at least for me) to explicitly set the tabindex. If I lay out the input elements, and group them, the browser will take care of the rest.
Although this _technically_ does NOT address the issue that the widget simply does not use the passed parameters as documented.
On Friday, July 3, 2015 at 9:44:25 PM UTC-4, Jeff Dairiki wrote: