[TIMOB-9659] MobileWeb:Launching kitchensink always lands us on the 'Controls' tab & not on the 'Base UI' tab even though base UI comes before controls.
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | Low |
|---|
| Status | Closed |
|---|
| Resolution | Invalid |
|---|
| Resolution Date | 2012-06-20T11:01:21.000+0000 |
|---|
| Affected Version/s | Release 2.1.0 |
|---|
| Fix Version/s | n/a |
|---|
| Components | MobileWeb |
|---|
| Labels | qe-mw020912 |
|---|
| Reporter | Lokesh Choudhary |
|---|
| Assignee | Chris Barber |
|---|
| Created | 2012-06-20T10:54:24.000+0000 |
|---|
| Updated | 2014-01-28T23:57:35.000+0000 |
|---|
Description
Launching kitchensink always lands us on the 'Controls' tab & not on the 'Base UI' tab even though base UI comes before controls.
Not a Regression, occurs with 2.0.2GA
Steps to reproduce:
Iphone:
1.Build kitchen sink for mobile web in titanium studio.
2.Type the ip address of your laptop into the mobile device's web browser.(safari for iphone & IE for Windows Phone mango).
3.Hit go or enter.
4.Kitchen sink will fire up in the browser.
5.Notice that the current tab highlighted is 'Controls' & not 'Base UI',even though baseUI comes before controls from left to right direction.
Actual result:
1.Launching kitchensink always lands us on the 'Controls' tab & not on the 'Base UI' tab even though base UI comes before controls.
Expected result:
1.Launching Kitchensink should land on 'Base UI' tab instead of 'Controls' tab.
Attachments
This is not a bug. KitchenSink explicitly changes the tab after the TabGroup is created: Resources/ui/common/ApplicationTagGroup.js Line 62: self.setActiveTab(1);