-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
Affix flickering on iOS 8.2 #16198
Comments
+1 |
Would you mind posting a jsbin or jsfiddle showing an example of this? |
Check the |
The code in question was committed here: There is no explanation given on why scrollTop is just used once for initialization and position.top otherwise. |
@charlesbjohnson Do you happen to recall the reason for the Interestingly, making the suggested change doesn't break any unit tests in any browser. |
@cvrebert making the change wont' break any tests because there aren't any unit tests. This could only be tested visually. I can't recall the exact reasoning behind the Take a look at the PR I made last year. In the diff comments there are some gifs and other explanations. |
The above fix solved my iOS affix flicker issues too. |
I've tested on iOS 8.4 and it works when using affix with top-fixed navigation bar. |
This fix is a gift. Thank you. |
Bootstrap 3 is no longer being officially developed or supported. All work has moved onto our next major release, v4. As such, this issue or pull request is being closed as a "won't fix." For additional help and support, we recommend utilizing our community resources. Thanks for your understanding, and see you on the other side of v4! <3, |
If I touch the screen in order to scroll down, while the navigation bar is not yet at the upper edge of the view (it's below it), and I'm scrolling down such that the original navigation bar position moves out of sight (still touching the screen), this is the moment the flickering starts.
The line js/affix.js:53 is the reason for this issue:
Why not replace it by
? This way it works fine.
The text was updated successfully, but these errors were encountered: