The Tab stack is not the real culprit here. What you are seeing is the inability of some stacks to function as expected when they are initially hidden at page load time.
There is also no way of detecting when an element becomes visible, no “hey I just became visible event”, so no way to re-run the code that normally works as expected at page load time, when the element eventually becomes visible.
In short. There is no way around this at the moment. But the web and the api’s we use are constantly evolving. One day we may get access to a “hey I just became visible event”, and then we can remove this limitation in all stacks.