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
Description of expected behavior and the observed behavior
While using widgets that support a value_throttled attribute (e.g. RangeSlider) and binding value_throttled to a callback works out fine, syncing the widget's value as a query parameter does not trigger the callback. It's worth mentioning that the widget's value is updated with the query parameters value.
In other words, while syncing a widget's value with a query parameter, the query parameter does not fire callbacks that are bound to value_throttled.
(Please don't confuse this issue with #7481 which features a similar code snippet)
Complete, minimal, self-contained example code that reproduces the issue
Once you have the code above, you can reproduce this issue by serving that app with e.g. panel serve --port 5099 throttled_sync.py and visiting "http://localhost:5099/throttled_sync?years=%5B2000%2C+2007%5D". I find that it only respects the URL parameter when depending on value, even though (as I understand it) it should be fine to depend on value_throttled as well.
ALL software version info
Software Version Info
Description of expected behavior and the observed behavior
While using widgets that support a
value_throttled
attribute (e.g.RangeSlider
) and bindingvalue_throttled
to a callback works out fine, syncing the widget'svalue
as a query parameter does not trigger the callback. It's worth mentioning that the widget's value is updated with the query parameters value.In other words, while syncing a widget's
value
with a query parameter, the query parameter does not fire callbacks that are bound tovalue_throttled
.(Please don't confuse this issue with #7481 which features a similar code snippet)
Complete, minimal, self-contained example code that reproduces the issue
Stack traceback and/or browser JavaScript console output
Screenshots or screencasts of the bug in action
The text was updated successfully, but these errors were encountered: