I have a Slider component with updatemode=drag, and I’m seeing the callback for the slider receive callbacks that are sometimes out of order. That is, sometimes the most recent callback on the Python side actually corresponds to a value that isn’t the most recent value on the browser side.
How do I know this? In my slider callback I update a Div with the value of the slider. Interestingly, the value in the Div is always consistent with the apparent position of the slider (which is good). But when I print the value of the slider passed into the callback, I can see that the most recent value printed is not the value in the Div in some cases – it’s rare, but it happens, and it’s a problem. The fact that the 2 values – the value that’s printed in the callback is different than the value in the Div – is hugely puzzling. It’s as if on the browser side, it knows which message it receives from the callback corresponds with the most recent slider value.
I can post an example. But I’m wondering if this is a known issue and if there is a workaround or fix.