You are right - i just tested it and clearing the tab order seems to be random tab order (im sure there is some rhyme and reason to it, but i dont see it - maybe creation order, but some do not tab at all)
I was not able to get around this myself. I see clearing the tab order works in FM but not for the web via IWP. Maybe this is something IWP can not control over the web alone. M
I guess this is under browser control but I don't even see the logic in its sequence. I have 2 fields stacked, a btn centered under them, another btn further down. Tabbing from field 2 jumps to the btn further down. That btn was further left. I though maybe tabbing was going L to R so I moved that brn R of everything else. Still the same result. So the pattern, type data, tab, type data, tab, press Enter is going to give confusing results.
My guess would be that the tab order that the browser is using is somewhat based on the order of the page elements as they appear in the HTML source of the page.
As far as I have observed, the order of how the page elements appear in the source of an IWP page is based on the following:
- Elements in the header part appear before elements in any other part part
- Elements in the body part appear before elements in the footer page part
- Within a given part, elements appear in the page source in an order based on when they were added to the FM layout; elements that were first added to your layout will appear earlier in the page source (before elements added later).
I have not tested the theory about the browser part of the above described interaction, so half of what I am saying here is just speculation. Observations about the order that the FM elements appear in the page HTML should be fairly sound -- I have looked at IWP HTML output a fair amount, and consistently I have seen this pattern.
I don't think this information helps you much, but it at least might shed some light on the seemingly random tab order that you are seeing.
That does help. I could try deleting and recreating a btn I want to go to last. That might save a little confusion. Hopefully since tabbing doesn't give any visual cue that it goes to btns users will just use the mouse anyway.
In IWP, I always thought it was the stacking order of the objects that determined the tab order.
So an object 'Sent to Back' would be the first object tabbed into and another object 'Moved to Front' would be the last item in the tab order, with all the other objects in between. So using move forward or backward on individual objects, should let you control the tab order.
Best wishes - Alan Stirling - London, UK.
Yep, that does affect order. I tried just copy/paste the btn and then delete the original but that didn't do anything. So I make a new btn from scratch and deleted the original. That moved it to the end of the tab order. Whoda thought?
I wanted to thank you for mentioning the idea of the stacking order influencing the tab order. This is a possibility that I had overlooked in my own inquiry into this.
Thanks and best regards,