You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently facing the problem, that I have several select boxes which options should depend on each other.
If an option is selected in box A it should disapear in box B and the other way around.
I got it working by using the @remove and @select events – as long as the user is deselecting the previous selection and make a new selection afterward.
But if the user changes his selection in one step, no @remove event is currently fired and a @change event is not available as well.
I got it working finally with a construct like so, but it feels not realy good ...:
It would be much easier, if there would be a third parameter "removedOption" given to the @select event if previously a option was selected. This would not break the current behaviour and could imo be realized easily.
The text was updated successfully, but these errors were encountered:
mediaessenz
changed the title
[Feature] Fire @remove event before @select if a selection was changed
[Feature] Add third parameter "removedOption" to @select event if previously a option was selected
Oct 10, 2024
I'm currently facing the problem, that I have several select boxes which options should depend on each other.
If an option is selected in box A it should disapear in box B and the other way around.
I got it working by using the @remove and @select events – as long as the user is deselecting the previous selection and make a new selection afterward.
But if the user changes his selection in one step, no @remove event is currently fired and a @change event is not available as well.
I got it working finally with a construct like so, but it feels not realy good ...:
It would be much easier, if there would be a third parameter "removedOption" given to the @select event if previously a option was selected. This would not break the current behaviour and could imo be realized easily.
The text was updated successfully, but these errors were encountered: