New-UDTabs -RenderOnActive – deprecation warning still present in 2026.1.7

New-UDTabs -RenderOnActive – deprecation warning still present in 2026.1.7

avatar

Hi,

we still get this warning whenever a page with New-UDTabs -RenderOnActive is opened:

"[Warning] [App-Development] RenderOnActive is deprecated and will be removed in 4.0"

The deprecation was tracked in https://github.com/ironmansoftware/powershell-universal/issues/1937 with the note that -Dynamic on New-UDTab should be enough. The same question was already asked on the but never got an answer (RenderOnActive is deprecated and will be removed in 4.0? - PowerShell Universal - Ironman Software Forums).
We're on 2026.1.7 now, -RenderOnActive is still a valid parameter, and the warning is still emitted.
Could someone clarify what the current status of this is and what the recommended migration path looks like?

Thank you

All Comments (3)

avatar

Hi wolfbergmann,

Thank you for reporting this.

I reviewed the current status and I agree that this is confusing. The GitHub issue you referenced indicates that -Dynamic on New-UDTab should be enough, but the current Tabs documentation still shows New-UDTab -Dynamic together with New-UDTabs -RenderOnActive for the Dynamic Tabs scenario.

Because of that, I do not want to give you an incorrect migration recommendation until we confirm whether the warning is outdated, the documentation needs to be updated, or there is still a valid scenario where -RenderOnActive is required.

I am going to raise this internally so we can clarify the intended behavior and the recommended migration path for current PSU versions. For now, if the current implementation is working correctly aside from the warning, I would avoid changing production behavior only to suppress the message until we confirm the expected replacement pattern.

If possible, could you also share a small sanitized example of the New-UDTabs / New-UDTab block you are using? That will help us validate the exact scenario against the current behavior.

Thanks,
Ruben Tapia

avatar

Hi Ruben,

thank you for you fast response. Here is one of our simple implementations.

I hope this helps, thank you,
Wolf

New-UDLayout -columns 1 -Content {
    New-UDTabs -RenderOnActive -Id "tabs_XXX_$TabId" -ScrollButtons 'off' -Variant 'scrollable' -Tabs {
        #Code
        New-UDTab -Id 'fake_1' -Disabled -Content {
            #Code
        }
    }
}
avatar
Hi Ruben,

thank you for you fast response. Here is one of our simple implementations.

I hope this helps, thank you,
Wolf
New-UDLayout -columns 1 -Content {
New-UDTabs -RenderOnActive -Id "tabs_XXX_$TabId" -ScrollButtons 'off' -Variant 'scrollable' -Tabs {
#Code
New-UDTab -Id 'fake_1' -Disabled -Content {
#Code
}
}
}


@wolfbergmann

Hi Wolf,

Thank you for sharing the sample implementation.

This helps. One thing I noticed is that the simplified example still uses `New-UDTabs -RenderOnActive`, but the visible `New-UDTab` in the sample does not include `-Dynamic`. Since the current guidance around this behavior is tied to Dynamic Tabs, could you please also validate whether the real tabs inside your `#Code` blocks are using `New-UDTab -Dynamic`?

This week we will be running this in our lab against the current PSU behavior to compare a few scenarios:

1. `New-UDTabs -RenderOnActive` without `New-UDTab -Dynamic`
2. `New-UDTabs -RenderOnActive` with `New-UDTab -Dynamic`
3. `New-UDTab -Dynamic` without `New-UDTabs -RenderOnActive`

From your side, if possible, please test removing `-RenderOnActive` in a non-production environment and confirm whether you see any functional change, such as tabs rendering too early, slower initial page load, empty tab content, or different behavior when selecting a tab.

For now, I would not recommend changing the production implementation only to suppress the warning until we finish validating the intended behavior and migration path.

Thanks,
Ruben Tapia