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
Introduced by #3875 and discovered via this test app. Below is a minimal reprex of the problem we were seeing there.
To reproduce, run the app.R below. Once open, remove "A" and "D" from the 1st selectize (choices). That causes input$selected to be NULL (when it should be "B"!).
If you then open the browser's devtools, and run the following JS $("select#selected").val(), you'll see the result is [], which is why the binding is reporting NULL. Interestingly, $("select#selected").selectize().getValue() returns the expect result (["B"]), so selectize.js must've recently moved away from using the DOM as the source of truth for the select's state.
Introduced by #3875 and discovered via this test app. Below is a minimal reprex of the problem we were seeing there.
To reproduce, run the
app.R
below. Once open, remove "A" and "D" from the 1st selectize (choices). That causesinput$selected
to beNULL
(when it should be"B"
!).If you then open the browser's devtools, and run the following JS
$("select#selected").val()
, you'll see the result is[]
, which is why the binding is reportingNULL
. Interestingly,$("select#selected").selectize().getValue()
returns the expect result (["B"]
), so selectize.js must've recently moved away from using the DOM as the source of truth for the select's state.app.R
The text was updated successfully, but these errors were encountered: