-
Notifications
You must be signed in to change notification settings - Fork 754
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
Internet Explorer 10 - Sticky header is jumping when attached to its parent #1018
Comments
Hi @pankajkumar45! I'll try to look into this issue again this weekend. |
Sorry, I don't think it is possible to fix this issue... If Using |
Thanks For your valuable suggestions, i will let you know as soon as i am done with implementation. |
I'm having this problem too- here a demo of the [production] site. Can you please look into it? |
Hi @CrazyPython! Is this problem in IE10 only? I don't think MS even supports IE10 anymore. I tried viewing that page in IE11, and it wouldn't load the table because of a few issues:
I'm going to close this issue, but please feel free to continue our discussion here. |
@Mottie Oh, I'm seeing it happening in Chromium actually... I may have missed a bit of the title 😅 |
Not on any desktop OS. |
Any solution for this problem, bro? |
Actually looking at this again, I realized that the widget is constantly updating the class on the header. When it is only updated when the class needs to change, it smooths it out. Odd, that it's rock-solid in Firefox without this modification. I'll make this change in the master branch, so it'll be available there, but I need to resolve a few other issues before the next release. |
Really hope to see the next version. |
Hmm, Chrome is weird. Even though the header has a |
Open demo URL http://mottie.github.io/tablesorter/docs/example-widget-sticky-header.html in internet explorer 10 and go to section Attach sticky header to its parent.
Notice that sticky header is jumping when scrolling table.
Can you please provide a fix for the same asap.
Thanks in advance.
The text was updated successfully, but these errors were encountered: