2) Tabs can have various levels of nesting.

3) The developer must be able to programatically set a particular tab as selected so that, that particular tab shows up as selected in the browser.

4) There shall be no restriction on the kind of components that can be put inside a particular tab.

5) A developer can choose to either a) Provide data for all tabs at once b) Provide data only for the selected tab incrementally as tab selections happen. c) Provide data to a minimal number of tabs as the developer desires and then provide data for other tabs at a later point of time.

6) The contents of the tab and number of tab children it has can change dynamically depending on the state of the application.

7) The tabset widget hould be keyboard accessible.One should be able to use the tabset with a keyboard only and without having to use a mouse. You should be able to use the key board "tab" key to navigate through the tab and its sub components.

Tab with server side infrastructure (JSF)

8) Each tab in the tabset will have the option to make an asynchronous request to the server and fetch data for the particular tab . This option can be toggled with the help of a tag attribute. If this happens, then the tab will be redrawn with the new contents.

9) Components present inside the tab can make individual asynchronous requests to the server to update themselves.

10) Whenever a tab in a tabset is selected, the particular selection shall be informed to the server . This option can be toggled with the help of a tag attribute for the tabset.

11) The developer shall be able to configure that whenever a form submit is made , only the selected visible tab goes through the decode phase or all the tabs in the tabset go through the decode phase.

Accessibility

12) It should employ the latest accessibility support specified in the ARIA roadmap

UI Requirements

-- Main.venkatesh045 - 29 Nov 2007