BusterIT

It would be nice if the changes could be implemented soon. In my use case (typing a location or set value by geo location) it´s not so nice to start...

I was not able to downgrade or throwing the 8.0.10 js framework references completely out of my build pipeline. So I did this hack and it solved the issues at...

Just simply push this solution. It is more performant than always set the binding context new: internal bool TrySetBindingContextToAttachedViewBindingContext() { if (this is not Behavior behavior) { throw new InvalidOperationException($"{nameof(ICommunityToolkitBehavior)}...

> @BusterIT I don't think that solutions works for all use cases. It won't work if you have a behavior attached to a view inside a CollectionView and it's bound...