Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Tab going to page 2 on opening

Avatar

Level 10

More tab fun...

Can't track this one down. If I leave tab order on auto it works fine.

If I make even one change to the tab order, anywhere in the document, on opening the pdf and tabbing it will go to page 2 first.

Unfortunately, the tab order does need some tweaking which I may end up fixing with setFocus(), but would like to figure out what's going on.

https://share.acrobat.com/adc/document.do?docid=1ef89c07-d057-489a-aac4-9af179938929

1 Accepted Solution

Avatar

Correct answer by
Level 10

Hi Jono,

I would be interested in how people are doing tabbing, as its always caused me so much trouble.  I've never had any luck with the given up using the Tab Order panel in Designer.  I've always done tabbing manually in the XML Source view, removing all <traversal> elements and then adding my own <traversal> element and using a fully qualified SOM expression.  This way I get exactly what a keyboard user would expect, though a "read out aloud" function would miss a lot of the document.  This is painful enough but what is worse is that once done the any change to the forms layout and I have to redo the <traversal> elements, so it is always the last thing I do.

Anyway your problem is the <traversal> element below.

        <traversal>
            <traverse operation="first" ref="subSetOff[0].Text3[0]"/>
        </traversal>

In the XML Source view find this and remove it.  It's in the MainSub subform so on entry to that subform focus is set to "subSetOff[0].Text3[0]" which has

              <traversal>
                  <traverse ref="Text3[1]"/>
              </traversal>

which then has

               <traversal>
                  <traverse ref="OngoingPayment[0]"/>
               </traversal>

So you end up on page two

I often find I'm better off without any  <traversal> elements.

Bruce

View solution in original post

2 Replies

Avatar

Correct answer by
Level 10

Hi Jono,

I would be interested in how people are doing tabbing, as its always caused me so much trouble.  I've never had any luck with the given up using the Tab Order panel in Designer.  I've always done tabbing manually in the XML Source view, removing all <traversal> elements and then adding my own <traversal> element and using a fully qualified SOM expression.  This way I get exactly what a keyboard user would expect, though a "read out aloud" function would miss a lot of the document.  This is painful enough but what is worse is that once done the any change to the forms layout and I have to redo the <traversal> elements, so it is always the last thing I do.

Anyway your problem is the <traversal> element below.

        <traversal>
            <traverse operation="first" ref="subSetOff[0].Text3[0]"/>
        </traversal>

In the XML Source view find this and remove it.  It's in the MainSub subform so on entry to that subform focus is set to "subSetOff[0].Text3[0]" which has

              <traversal>
                  <traverse ref="Text3[1]"/>
              </traversal>

which then has

               <traversal>
                  <traverse ref="OngoingPayment[0]"/>
               </traversal>

So you end up on page two

I often find I'm better off without any  <traversal> elements.

Bruce

Avatar

Level 10

Thanks, forgot about the traversal tags, haven't had to play with them for a while - tab order has been pretty good since the last big update.