TabViewItem instances reused incorrectly about microsoft-ui-xaml HOT 3 CLOSED

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you!

Open similar issues:

• TabView creates first TabViewItem twice, events get unsubscribed after binding to SelectedItem (#8573), similarity score: 0.80
• WinUI3 TabViewItem drag and drop issue (#8679), similarity score: 0.76

Closed similar issues:

• Behaviors are detached from controls inside TabView after being attached when returning back to cached page. (#4999), similarity score: 0.80
• Behaviors set in DataTemplates are mixing among ListView's items (#8866), similarity score: 0.77
• TabView: Memory usage does not go down after opening/closing tabs (#3597), similarity score: 0.75

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

from microsoft-ui-xaml.

@michael-hawker Is this an issue with behaviors not working well with virtualizing controls ?

from microsoft-ui-xaml.

The TabView uses virtualization for its items so it will reuse the instances of the TabViewItems, so that is expected. Since Behavior is a part of WCT, TabView does not know anything about it so it is not able to do anything special here. It might be the case that Behavior needs to be improved to handle this scenario better, but there is nothing that TabView can do to handle this.

from microsoft-ui-xaml.