We want to extend the Tabs API to support lazy loading of heavy tab content, including the ability to load content even for tabs that are not yet active or visited, in order to improve perceived performance. This should be configurable at the individual tab level, allowing each tab to define whether its content should be preloaded before it becomes visible.
In addition, we need an option at either the tab group or individual tab level to persist previously visited tab content. When enabled, the content should remain mounted after the user navigates away from the tab, so that returning to it results in immediate rendering without re-initialization or loading delays.
We want to extend the Tabs API to support lazy loading of heavy tab content, including the ability to load content even for tabs that are not yet active or visited, in order to improve perceived performance. This should be configurable at the individual tab level, allowing each tab to define whether its content should be preloaded before it becomes visible.
In addition, we need an option at either the tab group or individual tab level to persist previously visited tab content. When enabled, the content should remain mounted after the user navigates away from the tab, so that returning to it results in immediate rendering without re-initialization or loading delays.