Hello Cesar,

Did you test with ActiveTabId instead of ActiveTabIndex?

Regards,
Dimo
Progress Telerik

Hello Cesar,

"Set the initial ActiveTabIndex to 0" means to set the value of the variable, which is associated with the TabStrip ActiveTabIndex parameter. Setting component instance properties directly is incorrect in Blazor and often doesn't work anyway.

<TelerikTabStrip @bind-ActiveTabIndex="@ActiveTabIndex" />

@code {
    public int ActiveTabIndex { get; set; } = 0;
}

On the other hand, if you replace ActiveTabIndex with ActiveTabId, the unexpected initial scrolling does not occur, so this is a better approach. You need Telerik UI for Blazor version 9.0 or later. Here is a test page:

https://blazorrepl.telerik.com/QpkimMYU29zhhAoG58

Regards,
Dimo
Progress Telerik

Hi Cesar,

I must admit that the status of this item remains "Unplanned" and it's not scheduled for a specific release. Sorry about that. If the problem is a show stopper for you, please consider these workarounds:

• Set the initial ActiveTabIndex to 0 (and optionally reorder the tabs). In this case there will be no page scrolling.
• Change the ActiveTabIndex at runtime when the user scrolls down or does something that requires a tab change.

Regards,
Dimo
Progress Telerik

Hi Cesar,

Thank you for reaching out!

The behavior seems like a bug to me, too. After some additional testing, I can confirm it also occurs in earlier UI for Blazor versions.

As the ticket does not contain any sensitive information, I am converting it to a public bug report visible in our feedback portal. I added your vote to it and as a creator, you are automatically subscribed to get status updates.

Last but not least, I rewarded your account with some Telerik points as a small gesture of appreciation for your report.

Regards,
Nadezhda Tacheva
Progress Telerik