Hi, Chad. 

Thank you for the detailed description of the experienced issue. One or two releases away, we removed from our TabStrip demos the option to define the TabStrip tabs with a separate nested component. If you check the different examples, the tabs in the TabStrip are now defined using the tabs prop of the component. The TabStripTab component will be deprecated in a future breaking change release so we don't recommend its usage. 

Talking about the scenario that you want to implement, attached to my reply, you will find a runnable example that uses Composition API + Script setup that demonstrates how you can achieve the desired functionality. In the example we are passing the computedTabs computed property to the tabs prop of the TabStrip. The definition of the computedTabs property is as follows:

  const computedTabs = computed(() => {
    const tabToRemove = 'NewYork';
    return initialTabs.filter((tab) => tab.title !== tabToRemove);
  });

The above snippet is a dummy example of how we can filter the value of the computedTabs property. What you can do in your scenario is to implement your custom logic that returns only the tabs that should be visible in each specific case. 

With the above said, I've changed the status of the current fug fix to "Won't Fix" as the TabStripTab component will soon be officially deprecated. 

Please let me know if you have questions about the suggested implementation or if you need further assistance with the implementation of your scenario. 

Looking forward to your reply.

Regards,
Petar
Progress Telerik