activate shouldn't be called unless the tab is being activated. During instantiation, when there is only one tab, it gets "activated". Problem is this should be delayed until after all the tabs are created and the activeTab config param is processed.

Funny the "better" testcase was in the Stackoverflow post..... I thought you wanted something easier to see. Admittedly console.log was cool, but I figured you wanted the stack backtrace to see it was happening during instantiation, hence the breakpoint method.