Hello,
thank you for your response, but in our app, there is it a little bit different.
We create the Nested Tab views dynamically in code, and then the user clicks, lets say on an label in the content ob a tabview. Thereafter a popup is opened, allowing the user to edit the content of the label. After editing the content the popup is closed and the content of the label is updated. This leads to a recalculation of the size of the Tab View, and this leads in the end to the fact, that it tries to jump to the last Tab.
Therefore my question: is there a mechanism which triggers in code behind the switch of the tabs, when the size is invalidated and can this be surpressed?
I have found out in the meantime, that with Version 18.3.x the problem is not appearing, so I will stay on this verison for the moment for this particular component.
Best regards
Bernhard