Open
Description
Current Situation
Currently, property triggers are only available by takting the detour using the FrameworkElement.Style
property and its Style.Triggers
collection. Assigning a property trigger immediately to the FrameworkElement.Triggers
collection raises an error.
This restriction makes no sense and is a quirk that's repeatedly causing confusion and unneccessary ado.
Desired Situation
I propose to remove the current artificial restriction for the FrameworkElement.Triggers
collection that's constraining it to only accept event triggers and to harmonize the FrameworkElement.Triggers
collection's feature set with the Style.Triggers
feature set.