This isn't a bug. By calling boxWrap, you're messing with the DOM structure of the component, meaning that the outer-most component of the element isn't what it once was.
Either:
a) Don't make the tabs directly the north region (over-nest on purpose)
b) Modify the object so it points to the new element correctly.
Marking as closed.
Twitter - @evantrimboli
Former Sencha framework engineer, available for consulting.
As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.
It seems odd that regular panels work fine, and even tab panels are fine outside of a border layout. I'm not changing the outer-most compenent of the tab panel at all... I'm putting the component inside of another container (the wrap). It seems like a bug to me, being that it works with regular panels inside or outside of a border layout and with tab panels outside of a border layout.
Of course you are. Look at the markup before and after you call boxWrap().
You're calling the method directly on the element, the component knows nothing about it, so it doesn't know how to resize with the new markup.
Twitter - @evantrimboli
Former Sencha framework engineer, available for consulting.
As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.
Of course I'm manipulating the dom, but the markup for the tab panel doesn't change at all. The only difference is the wrapping container. Without boxWrap, the container is the north panel's x-border-panel element. With the boxwrap, the container is x-box-mc element. Everything related to the actual tabpanel is unchanged.
I guess I'm wondering if there's a way to make this work as intended. I tried over-nesting and then calling obj.el.up(".nesting-ct").boxWrap() then tried the same thing with the addition of calling obj.el.up(".nesting-ct").doLayout() but got the same result in both cases. I also tried simply over-nesting and calling obj.el.boxWrap().
Edit... Tested this in Safari 3.2.1 Win too and don't get this behavior. Weird.
Edit again... Scratch that. Anytime a doLayout() is called it hoses up.
Anyway, here's the markup. Like I said, the actual tab panel markup doesn't change at all... All that changes is its container.
Twitter - @evantrimboli
Former Sencha framework engineer, available for consulting.
As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.