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

Single Select Old Value is always null when change listener is called #959

Closed
howudodat opened this issue Sep 11, 2024 · 0 comments
Closed
Assignees
Labels
bug Something isn't working version 2.x.x Version 2.x.x issues
Milestone

Comments

@howudodat
Copy link

select.addChangeListener((o,n) ...
if it is a multi select o is an array[] as is n.
if it is a single select o is always null even if something was selected

Select#onOptionDeselected (line 130) gets called prior to withOption (line108) so that when getValue() is called to get the old value, it returns null

To Reproduce
Run the demo app, use Single Select, select a value, Old Value = null. Select another value, Old Value = null;

Expected behavior
When a previous value was selected the change should pass in the old value

@vegegoku vegegoku self-assigned this Sep 12, 2024
@vegegoku vegegoku added bug Something isn't working version 2.x.x Version 2.x.x issues labels Sep 12, 2024
@github-project-automation github-project-automation bot moved this to To do in Domino UI Sep 12, 2024
@vegegoku vegegoku added this to the 2.0.3 milestone Sep 12, 2024
@github-project-automation github-project-automation bot moved this from To do to Done in Domino UI Sep 19, 2024
vegegoku added a commit that referenced this issue Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working version 2.x.x Version 2.x.x issues
Projects
Status: Done
Development

No branches or pull requests

2 participants