activeTab:1 // consider this should not be a constant
=> Tab1 is active (Tab2 should be)
3) Now remove property activeTab:0 from TabPanel
4) Save, publish and test => Tab2 is active (expected result)
5) Now add a new panel to TabPanel (or reorder existing)
=> activeTab:0 is automatically added to TabPanel config
No, I'm not overriding from 1 to 0, it is the way to reproduce it (SA set 0 as default).
If you read further, you should see that I removed activeTab property from TabPanel.
Let's consider having a toolbar with 2 buttons that open a window containing this tabpanel.
The first button opens window with tabpanel.activeItem = 0
The second one opens window with tabpanel.activeItem = 1
Since my window is not destroyed on close, I have no problem only after it has been showed once.
Now if any dev-guy need to add a third panel (and so another button), he will get throw this annoyance.
Any button that will be clicked will always open window with activeTab:0 since deleted activeTab property will 'magicallly' come back
The fact is that it may be an ExtJs bug instead of an Architect one. activeTab property should be overridden by container defaults, that does not happen here.