1 of 1 people found this helpful
Yes. Please don't use "W3Schools" as a guide, though. So much on there is wrong, wrong, wrong (it's not curated by actual developers).
Marketo forms natively support a Slider field type based on the standard HTML5 Range type. Cross-browser, it has more features than the native Range, namely a current value display --
-- but it doesn't bring all the HTML5 features, such hashes, labels, and lists, unless they're natively supported by the browser.
If you want a more bells-and-whistles range slider you should use a standard Text field and then enhance it with a UI library, like noUiSlider.
sorry - the W3Schools wasn't mean to be a reference or guide - just an example of a slider (to help clarify what I was after).
How dense of me - I didn't even pick up on the slider type!
Those noUiSliders are really nice.
As always, thank you for the legendary knowledge and support!
Right, I was just sounding the general alarm... in addition to using outdated practices (like Element.onclick, etc.) without a disclaimer, they don't seem to care about browser compatibility. So while some of their demos (like this one) can be perfectly fine in the browser you're currently using, they might be very not-fine when you open another (fully modern) browser.
Range is a good example of a feature that someday will be very cool, but is spottily supported to the point that you might as well start from a totally 3rd-party widget (instead of trying to add hashes & labels to a native widget).