Context / Is your feature request related to a problem? Please describe.

• Some users complained, that when they have f.e. 10 tabs with each tabs 50 components, everything "gets soo slow". These users use the "tabs" like an App navigation and expect it should work.
• Some other Users claim, that tabs should remember things of components, and other users claim this should be definitely not the case.

What we implemented previously was the idea to "destroy" the components (inMemory) for inactive Tabs - to free memory and computing.

Describe the solution you'd like

Users should be able to activate or deactivate the whole behaviour :

1. Lazy Loading of Components in Tabs - as soon as the Tab get active.
2. Remembering of Component State for inactive tabs (re-opening present the last known state).
3. Fully rendered and only hidden state of all tab contents (visible and hidden) (no lazy loading, and no "forgetting of states".
4. Destroying of tab content for every hidden tab.

Ideally the User would be able based on switches to select the behaviour that fits best to his needs.