☰Read-only archive⌕
Looking for help with Bokeh?

This is a read-only archive. Ask questions and join the conversation on GitHub.

Visit Community Support on GitHub →
Archived discussions · Captured October 28, 2026

Weird slider.py interactions with chrome 51 on win 7

Community Support
Jan_Burgy
Jan_BurgyJan 18, 2018   #1

I observe a weird bug after upgrading to chrome 51 (sic), reproducible with slider.py — Bokeh 2.4.2 Documentation.

Dragging the 'Amplitude' handle works as expected but dragging 'Frequency' afterwards moves *both* of them together. Happens with 'Phase' and 'Offset' as well. Does not happen when I click on the base left or right of the .handle. You can even click anywhere in the .widget-box below the sliders to move them. It looks like chrome associates .bk-noUi-handle elements with the .bk-widget-box instead of their individual .bk-widget but only after they've been selected once.

⌁   Link to post
Bryan
BryanJan 18, 2018   #2

I can't reproduce any problem on current Chrome 63. Chrome 51 is going on two years old, unfortunately due to lack of resources its unlikely we can investigate an issue like this on such an old version. If you happen to have a small fix that can be demonstrated to work on current browsers, we'd be happy to consider a contribution.

Thanks,

Bryan

···

On Jan 18, 2018, at 11:25, Jan Burgy <jburgy@gmail.com> wrote:

I observe a weird bug after upgrading to chrome 51 (sic), reproducible with https://bokeh.pydata.org/en/latest/docs/gallery/slider.html\.

Dragging the 'Amplitude' handle works as expected but dragging 'Frequency' afterwards moves *both* of them together. Happens with 'Phase' and 'Offset' as well. Does not happen when I click on the base left or right of the .handle. You can even click anywhere in the .widget-box below the sliders to move them. It looks like chrome associates .bk-noUi-handle elements with the .bk-widget-box instead of their individual .bk-widget but only after they've been selected once.

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bokeh+unsubscribe@continuum.io.
To post to this group, send email to bokeh@continuum.io.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/5ef5edce-0a9e-40d2-9983-b7cb48469fab%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

⌁   Link to post
Bryan
BryanJan 18, 2018   #4

Well, BokehJS currently uses noUiSlider v0.10:

  https://github.com/bokeh/bokeh/blob/master/bokehjs/package.json#L106

Upgrading to version 11 is something we could try easily enough. If things look good and a PR is merged, we can publish a dev build that would be easy for you to test. Can you make a GH issue to request updating the nouislider version?

  Issues · bokeh/bokeh · GitHub

Thanks,

Bryan

···

On Jan 18, 2018, at 14:01, Jan Burgy <jburgy@gmail.com> wrote:

How can I test whether it's related to Serious bug when using multiple sliders on chrome (v 51.0.2704.84) · Issue #805 · leongersen/noUiSlider · GitHub which Leon fixed in 11.0.0?

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bokeh+unsubscribe@continuum.io.
To post to this group, send email to bokeh@continuum.io.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/4f24002d-d93e-4852-89d1-d707b97b27ad%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

⌁   Link to post

End of archived discussion · Replies are disabled