-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome/Split tooltip on range slider not aligned #483
Comments
Regardless of how simple the code is, we always ask to see an example. Please show one. |
You got it - sorry for the delay, had to extract the relevant code. |
I'm having the same ussie, with without the split tooltip. It's also reproducable by the given example from @dreamcasting (change |
Having the same problem with tooltip_split:false. When initialized the tooltips inline css "margin-left" value is always set to "0px". |
Having the same issue. When the tooltip is initialized it has |
@golear91 sweet workaround! 'margin-left': '-40.5px for me when using tooltip_split: false. |
how to implement that css after initialization? I am having same issue. |
@sorryjack just use the code I pasted above. It is basically selecting the element using jquery and then applying a css attribute |
@goleary was trying your code many times, seems not worked. then I found that it actually triggered. $('.filter-harga .tooltip-min').css({'margin-left': '-21px'}); now it worked. thanks man. |
Use `transform: translate()` instead of margin-* for the tooltips. Fix #483
I'm using Chrome 47 for Windows and a range slider with split tooltips which are also set to always show. Until I click on the slider the tooltips are always misaligned, then they jump to the correct place. This is within a bootstrap modal. I've changed the tooltip CSS but then the tooltips will jump on click and be incorrect afterward.
The code I'm using is pretty straight up -
function gradeFilter() { var slider = $("#gradeFilter").bootstrapSlider({ tooltip: 'always', tooltip_split: true });
The text was updated successfully, but these errors were encountered: