The test for tabset in update table from top is not working as expected.

• load application three rows in datatable are displayed all with tab1 selected
• change tab selection for row with John1, so Taylor1 is selected
• Add new row to data table, John3 is added to the top of the table
• Notice Taylor1 is not displayed as selected any more, Taylor0 is displayed as selected now ( it is not the second row i the data table)

Page URL: http://localhost:8080/tab/dataStructures/updateTable2.jsf
testcase at: \svn\repo\qa\trunk\Regression-Icefaces2\Sparkle\tabset

Please modify the test application so that the tabSet component's selectedIndex property has a ValueExpression to a property on the dataTable component's row object.

When there is no ValueExpression, the tabSet must maintain the selectedIndex property itself, which internally relied on the clientId. When inserting or removing rows from the dataTable, the clientId's for each row are altered, causing properties to be shifted to the incorrect rows.

sing;eSubmit & immediate components not working. no errors message is displayed for input component with required=true in side the tabset.
Page URl: http://localhost:8080/tab/tabsetAttribute.jsf
testcase at: \svn\repo\qa\trunk\Regression-Icefaces2\Sparkle\tabset

Once ICE-6490 is complete, this will need retesting.

The only concern left is we don't really have anything in place to error catch a dynamic style when validation exceptions occur. Currently, we lose all style with a dynamic change of style/styleclass, singleSubmit and the cancelOnInvalid set to false (not checked).

Other than that, I think the test should list the behavior looking for which each combination.
For example, we have cancelOnInvalid, which really has identical behaviour to singleSubmit="true", and immediate="true". However, this needs to be further defined.

There is a serious lag before the styles are loaded on this test page. Might be another event we listen for so that the styles are loaded before the page is rendered (pretty sure I saw that in the yui event api)

Found that if I put an inputText on one of the panes and an inputText bound to the same el #

" while in the same form, and an outputText bound to the same el like this:_

<h:form styleClass="ice-skin-sam" prependId="false">
<h2> Demo has a TabchangeListener </h2>
<ice:tabSet id="myTabSet" tabChangeListener="#

" styleClass="#

"
singleSubmit="#

"
immediate="#

"
rendered="#

"
selectedIndex="#

"
orientation="#

"
cancelOnInvalid="#

"
clientSide="#

"
style="#

">
<ice:tabPane id="tp1" label="Tab contents from JSP" >
<h:outputText value="YUI generally works well with mobile browsers that are based on A-Grade browser foundations."/>
<h:inputText id ="in" required="true"/>
</ice:tabPane>
<ice:tabPane id="tp2" label="tab Contents to check singleSubmit">
<h:outputText value="#

" required="true"/>

</h:form>
<h:outputText id="singleSubmitTest" value="#

"/>
<h:messages/>

modified the tests as in two of the three instances here, the test pages were not quite right. CancelOnInvalid property confuses tests especially for singleSubmit and immediate. The cancelOnSubmit option only has to do with validation of the components within the tabset component itself. If there are components outside of tabSet and on the form, then input outside the form will do standard jsf behaviour and not be submitted.