Potential Bug With AccordionPane in dojo .4.1 with Regards to Tab Sequence

[guest]

We noticed that the AccordionPane? (or one of its subwidgets) does not handle tabbing correctly in Firefox 2.0. Specifically, given the following code snippet, the user interface will get ugly when one tabs out of the first text field in the first Pane:

 <span>
        <dojo:AccordionContainer>
            <dojo:ContentPane selected="true" label="Label 1" >
                <input type="text" />
            </dojo:ContentPane>
            <dojo:ContentPane selected="false" label="Label 2" >
                <input type="text" />
            </dojo:ContentPane>
        </dojo:AccordionContainer>
    </span>

As a temporary workaround, we added the following CSS3 Selectors to stop the problem:

div div.accordionDetail {  
     visibility: hidden; 
}
div[class*='-selected'] div.accordionDetail {  
     visibility: visible;
}

[Adam Peller]

I'm not sure to what level we supported keyboard navigation in 0.4. Can you check to see how this works in 0.9?

[bill]

I bet this was broken in 0.4 because the unselected panes, rather than being display:none, were display: block (but were hidden because of z-index, etc.)

And I bet it's fixed in 1.0 because now the unselected panes are display:none. But need to check.

[bill]

PS: the problem is that it's tabbing into an input in an unselected pane, right?

[guest]

Bill -

You are correct. The problem is that it tabs into the input in the unselected pane. For what its worth, the CSS solution was meant merely a workaround for us. I'm sure there's a deeper underlying cause. I haven't had time to test it with .9 yet.

Josh

[guest]

Replying to peller:

I'm not sure to what level we supported keyboard navigation in 0.4. Can you check to see how this works in 0.9?

FYI - I just tested this with .9 and it seems to work perfectly. I'm assuming we can close this ticker or at least let it live on the .4 branch?

Thanks,

Josh

[bill]

Great, that's what I expected. Yeah, I'm gonna close this bug since we don't have plans to support keyboard stuff on 0.4 (and also since it would be a major change to get it to work.)