Fix #20816: OneWay binding fails to update target after local change#20964
Fix #20816: OneWay binding fails to update target after local change#20964martimclaudino wants to merge 1 commit intoAvaloniaUI:masterfrom
Conversation
…al change When a OneWay binding target is modified locally (e.g., via user interaction on a ToggleButton), subsequent PropertyChanged events from the source were being ignored. This occurred because the binding expression incorrectly suppressed the update. This patch modifies UntypedBindingExpressionBase to ensure that OneWay bindings always propagate changes from the source to the target, overriding any previous local changes. Unit tests were also added to prevent future regressions on this behavior. Signed-off-by: Martim Claudino <martimffclaudino@tecnico.ulisboa.pt>
|
You can test this PR using the following package version. |
|
Please read the following Contributor License Agreement (CLA). If you agree with the CLA, please reply with the following: Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by AvaloniaUI OÜ and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant AvaloniaUI OÜ, and those who receive the Submission directly b. Patent License. You grant AvaloniaUI OÜ, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to AvaloniaUI OÜ. You agree to notify AvaloniaUI OÜ in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the Republic of Estonia, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and AvaloniaUI OÜ dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
What does the pull request do?
This PR fixes a desynchronization issue with
OneWaybindings where local changes to the target UI control permanently severed the binding's ability to receive updates from the source.What is the current behavior?
When a
OneWaybinding target is modified locally (e.g., via user interaction on aToggleButton), subsequentPropertyChangedevents from the source are ignored. The binding expression incorrectly suppresses the update, leaving the UI permanently inconsistent with the underlying application logic (e.g., a read-only ViewModel property).What is the updated/expected behavior with this PR?
The
OneWaybinding will now strictly respect the source as the single source of truth. Even if the target property is modified locally by the user, any subsequentPropertyChangedevent from the source will successfully propagate and override the local UI changes, keeping the target in sync with the source.How was the solution implemented (if it's not obvious)?
The issue was located in the binding engine (
UntypedBindingExpressionBaseandBindingExpression). I modified the evaluation logic (updating theConvertAndPublishValuecall) to ensure thatOneWaybindings do not suppress updates when triggered by the source'sPropertyChangedevent after a local change. A unit test was also added toBindingExpressionTests.Mode.csto explicitly cover this scenario and prevent future regressions.Checklist
Breaking changes
None.
Obsoletions / Deprecations
None.
Fixed issues
Fixes #20816