-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Button VisualStates do not work #19690
Copy link
Copy link
Open
Labels
area-controls-buttonButton, ImageButtonButton, ImageButtonpartnerIssue or Request from a partner teamIssue or Request from a partner teampartner/syncfusionIssues / PR's with Syncfusion collaborationIssues / PR's with Syncfusion collaborationplatform/androidplatform/iosplatform/macosmacOS / Mac CatalystmacOS / Mac Catalysts/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Milestone
Metadata
Metadata
Assignees
Labels
area-controls-buttonButton, ImageButtonButton, ImageButtonpartnerIssue or Request from a partner teamIssue or Request from a partner teampartner/syncfusionIssues / PR's with Syncfusion collaborationIssues / PR's with Syncfusion collaborationplatform/androidplatform/iosplatform/macosmacOS / Mac CatalystmacOS / Mac Catalysts/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.
Description
Setters are not unapplied when using custom VisualState on a Button on Android, iOS and MacCatalyst.
Steps to Reproduce
Expected: When the Button is clicked the second time it should go to Normal state.
Actual: When the Button is clicked the second time it visually stays in Custom state.
Link to public reproduction project repository
https://github.com/telerik/ms-samples/tree/main/Maui/ButtonVisualStatesIssue
Version with bug
8.0.3
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
iOS, Android, macOS
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
No response