Closed justinmc closed 7 years ago
Thanks for lettings us know. I've confirmed the issue. Investigating...
It looks like this commit didn't fix all the places where selected_label
was used: https://github.com/ipython/ipywidgets/commit/aef3069a3b965bd675d983fa3952aec2c2067620
Edit: Nope, that's not it. Still looking...
Looks like it might have @afshin's commit: https://github.com/ipython/ipywidgets/commit/5b47aaac9285ec961e43525cc1dea2e9047b7edd#diff-61326cb05eb256df11c903abf2527196R605 - that's where it is switched from using the model's value
attribute to a selected_label
attribute, though it doesn't appear that such an attribute exists on the model.
Of course, we should have caught that on review of @afshin's PR too.
D'oh! I missed that; mea culpa.
:sweat_smile:
@afshin actually, the change from selected_item
to value
happened around the same time as your PR, so it is almost certainly a rebase thing 😄 .
Not sure if you guys are already aware of bugginess in Select in the beta releases, but I tried upgrading and noticed Selects weren't working so thought I'd submit this. Setting
value
on a Select seems to be broken in 6.0.0b1 and b2.The select shows up as blank (
None
selected) regardless of what I do programmatically. Also, observingvalue
does not call the given function when manually changing the selected option.