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
right now, making fd-slider do its thing will create visible sliders even for inputs whose CSS display is set to none, visibility is set to hidden or opacity is set to 0. It might be a good idea to look into whether it is possible to mirror the display, visibility and opacity values for the input element that is being fd-slider'd, so that currently hidden inputs don't suddenly turn into visible sliders, and toggling the visibility of the input element (through jQuery or what have you) just works, rather than requiring fd-slider-specific script to be written to make sure visibility applies to both the input and its corresponding fd-slider object.
The text was updated successfully, but these errors were encountered:
Hi, it would be easy to reflect the opacity/visibility/display on creation but you would still have to write a script that "shows" these hidden sliders whenever the associated input is shown. It's impossible to automatically detect changes to the opacity/visibility/display properties (short from using nasty timeouts or not-very-cross-browser events that are really expensive to run).
on creation is better than nothing - as long as it copies over the class/id then any opacity/visibility adjustments based on good CSS selectors (i.e. element agnostic) will still work since they'll be applied to the fd-slider instead
right now, making fd-slider do its thing will create visible sliders even for inputs whose CSS display is set to none, visibility is set to hidden or opacity is set to 0. It might be a good idea to look into whether it is possible to mirror the display, visibility and opacity values for the input element that is being fd-slider'd, so that currently hidden inputs don't suddenly turn into visible sliders, and toggling the visibility of the input element (through jQuery or what have you) just works, rather than requiring fd-slider-specific script to be written to make sure visibility applies to both the input and its corresponding fd-slider object.
The text was updated successfully, but these errors were encountered: