Changes between Version 1 and Version 2 of Ticket #16242, comment 8


Ignore:
Timestamp:
Oct 31, 2012, 2:37:30 PM (7 years ago)
Author:
mikeb
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16242, comment 8

    v1 v2  
    33
    44StackContainer cannot just set the roles on its children to tabpanel because that child may already have a role that will get reset. This will cause problems when there are role-specific aria attributes on the child. For example, if you use a Tree in a StackContainer, it will have role=tree and aria-multiselectable. But since there is no wrapper for the child, if we just reset the role to tabpanel, we'll have to remove all of the tree related aria attributes. Then we also have the bigger problem of now the child tree dijit is not accessible. So yes, the practical advantage of having two nested divs with separate roles exists as long as those roles are different.
     5
    56
    67> Right, and there could also be multiple !StackController widgets controlling a single !StackContainer, although I guess in that unusual case it wouldn't matter which one was referenced.