Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Remove restriction to only allow event triggers in FrameworkElement.Triggers collection #10048

Open
SetTrend opened this issue Nov 10, 2024 · 0 comments
Labels
Enhancement Requested Product code improvement that does NOT require public API changes/additions

Comments

@SetTrend
Copy link

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.

@harshit7962 harshit7962 added Enhancement Requested Product code improvement that does NOT require public API changes/additions and removed Untriaged labels Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Requested Product code improvement that does NOT require public API changes/additions
Projects
None yet
Development

No branches or pull requests

2 participants