Any use of input range does not seem to work for me in Chrome 63 (OSX Sierra). Clicking the slider and its number field in the following example has no effect, it won’t receive focus so I have no way to modify it.
In FireFox it seems to work properly.
Do you have strict site isolation enabled in chrome://flags? We’ve heard reports of this causing exactly this issue. If you’re willing, try reseting your flags to their default values and see if that fixes the problem.
Edit: Specifically, this known issue in Chrome:
In some cases, clicking or scrolling on cross-site iframes may not work properly.
For example, this can happen when there is a partly transparent overlay above an iframe. (This is fixed in Chrome 65.)
Ah, yup, I have isolation on. Just tested in Canary and it works fine.
Thanks!
Sadly, I’m seeing the same problem in Chrome 63, and strict site isolation is set to Default.
Uncaught DOMException: Failed to read the 'sessionStorage' property from 'Window': The document is sandboxed and lacks the 'allow-same-origin' flag.
at Object.qa.getAndResetPendingTask (<anonymous>:69:30640)
at a.addPendingTask (<anonymous>:65:8471)
at D (<anonymous>:64:17877)
at c (<anonymous>:64:18398)
at d (<anonymous>:63:8456)
at <anonymous>:63:8721
at q.d.promiseDispatch (<anonymous>:63:2730)
at <anonymous>:63:1493
at MessagePort.c (<anonymous>:63:6156)
Domain policies prohibit me from upgrading to the latest version of Chrome on this machine.