What’s The Issue
</figure> I included more code here than is required because it’s important to see the context of where the problem lies. We’re looking at the prototype object definition for the TabContainer control, the root object of the TabControl. The problem method here is the **raiseActiveTabChanged **definition. What this brilliant little snippet does is pretty much say, if there’s a client side handler for when the tabs change, fire it off. Then there’s the postback. What’s problematic here is that the result of the user handler for tab changes is completely left out of the decision to postback. I suppose someone could be sneaky and just set the autopostbackid to null but that seems like an important piece. When I started out, I thought maybe this was the place to make my attack, but then there was the second issue, illustrated below:
I am a full stack software architect with over 20 years of experience developing scalable, enterprise level applications targeted for Windows and the web. I have worked with a number of SPA front end frameworks, .NET middleware technologies, both relational and document databases and various big data search platforms. I'm currently interested in Microservice and Serverless architecture patterns.