Currently in both windows and web when using <TAB> the cursor progresses to anything that looks like something a user can enter data. Also the Windows and Web don't behave the same (I wonder where this will take us in Universal); Web does not progress to the next tab/label on a multi tab/label form, whereas windows does (might be due to readonly fields as the last thing on the current form). I can't really tell in Web where the cursor is after a few readonly fields...
I'd like to see that changed in the following sense
- Let the cursor not “land” on a read-only field, but rather ignore them and progress to the next changeable field in the form.
- If there are multiple tabs on a form (either by resolution restriction or by design), let the gui open the next tab (already the case in the Windows gui)
- When tabbing back (<shift>+<Tab> on the first field in a multi tabbed form, select the previous tab on the same form (now a detail tab of the table is selected) or the last tab when the first tab is selected.
- Let the cursor not land on a lookup item (the "magnifying glass” icon)
