It would be really nice if I didn't have to implement an event handler if all I wanted to do was change the visibility of an element.
I voted for beter interopability between WPF and Silverlight for this feature, but I will vote again. We actually use both silverlight and WPF in our product, and there is a lot of custom controls that we could EASILY share they could add triggers (they were originially created in WPF).
Why you cannot use view states within VisualStateManager? imho this way is more usable than triggers in WPF
And also DataTrigger and MultiTrigger would be real nice
Stefan Olson commented
What's even more important than this to me, is the fact that it allows you to share code more easily between WPF and Silverlight.