Hi! Has anyone experienced this issue after the latest update of OS UI, where the handle of RangeSliderInterval is out of position? Please see the image below
Scenario: On first load of screen the widget is working fine but after redirecting to another screen and went back to the same screen where the RangeSliderInterval was the issue occurs.
First Load:
HTML:
After pressing back or homepage button:
Hoping anyone can solve this. Thanks in advance :)
Hi Eugene,
I believe so, as there's external provider code (noUiSlider) still being loaded and creates conflicts between their versions of JavaScript and CSS.
If you can test it on your side, please, I'm confident this is the root cause, it happened before, as customers migrate to the new version of the RangeSliders in some screens.
Best regards,
Bernardo Cardoso
Hi Bernardo,
Thanks for your help. I've tried your suggestion on our code and it fixes the issue.
So we do really need to remove all deprecated widgets or it depends on the widget? even though we have validations to which widget will be shown to the user?
Is it possible that you have both the new RangeSliderInterval and the DEPRECATED_RangeSliderInterval on the same application being used?
Other than that, I believe we will need an oml with that issue happening, to be able to help you further!
Yes, we keep the deprecated widget but it is on a container that is not visible on the app. Is it possible that it still can have effect on the css even though it is not loaded in frontend?
From what we know, this just happens with the RangeSlider, due to the way the library is built (and at some point they changed their CSS quite a bit).
I believe you will only need to do this for the RangeSlider Patterns. Although I would suggest avoiding mixing DEPRECATED and new version, for the patterns that depend on external libraries.
You can find the list of them on the table from this documentation page.
Noted on this. Thanks again for your help! :)