Closed dare-me closed 10 years ago
Hello,
This issue was reported in another place. I think I'll fix it in next release, even if it implies some side effects that are probably less important than this one.
I very much appreciate that. As I said I reported it earlier over uservoice on your website.
i have this problem too , and will appreciate to fix it start one shows correct value but end ones shows less value
I have same issue, what quick interim fix has been found?
Fixed in 5.5.0
We updated and tested the fix.
As you can see on the screen from the opening post we have a grid of one year. That distance from one to another year is at this time 108px wide. If we set the range to one year, the bar is 109px wide. This difference leads to a huge difference in positioning.
If we start at the very left, the sliding bar fits the one year grid, the more we move to the right, the more the sliding-bar is off the scale.
In the opening-post-screen you can see, that the off-scale was on the right. Now the off-sacle is on the left.
We removed every css change we made to the rangeslider in order to verify that the issues is not our fault.
Did you update the standard CSS as well, with the JS code?
Apparently the developer responsible fo the update forgot to update the css as well.
I am sorry for the inconvenience.
Hello, We are using this Plugin in one of our Customer Projects.
We use the slider, to give the user the ability to select a time frame.
As you can see, the user selected "Q3 13" to "Q4 14" (Q is for quarter) The slider selection "Q4 14" reaches into the next quarter.
I reported this issue once but you said, you can't do anything about it. My problem now is: The customer is not satisfied with this "solution" ... and there is no other plugin like this, there are other plugins, but none of them give me the abilities this one does. But the other ones are accurate, this one ... is not.
We did a quick and dirty fix, which shortens the width of the slider 10px, because that was the amount of pixels the slider was off. This fix was VERY dirty ... not productive.
In my eyes, this is a huge bug ... how come nobody is interested in this issue?! (because no other ticket like this was found)