-
Notifications
You must be signed in to change notification settings - Fork 25.6k
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
position: sticky
causes sidebar overlap in Chrome
#752
Comments
Does the overlap happen on all pages that have the author sidebar? or just that one? I'm on Chrome 55 on Windows and not able to reproduce it. Are there any sort of JavaScript errors in the console or is it disabled for any reason? There is a JS polyfill for Other than that I'm at a loss as to what's going on. |
OK, looks like it's related to |
position: sticky
causes sidebar overlap in Chrome
Tested on beta Chrome 56 on Windows and all works as it should. With Still not sure why it's broken for that redditor, could be something JS related. I know there's stuff in the theme that was added awhile back that tests the width of things to trigger the sticky polyfill, and that could be borked for whatever reason. |
- Fallback to default positioning for browser that don't support it IE, Chrome < 56, etc. - Issue #752
Blown away by your care and thoroughness in handling this issue! Humbling! ❤️ |
I do what I can 😉 In the end I took out the polyfill. In Firefox, Safari, and Chrome 56 the sidebar will "stick" as it should. On older browsers it scrolls with the rest of the page, which isn't so bad either. If you're interested in making the changing it's pretty small and in this commit. I'll roll it out officially in the next release. |
@nathanheffley Definitely not the case. It may be hard to tell from the GIF but the screen was much wider than 100px. Tested on both Windows and Mac Chrome 56 (beta) and couldn't reproduce the overlap. Screen width Curious to know if you have any plugins installed that might mess with JS or noticed any script errors in the console. |
Getting
I should probably wait a while before it hits rubygems, sharing just in case |
@kvz Stange. It should be there, along with |
- Fallback to default positioning for browser that don't support it IE, Chrome < 56, etc. - Issue mmistakes#752
- Fallback to default positioning for browser that don't support it IE, Chrome < 56, etc. - Issue mmistakes#752
- Fallback to default positioning for browser that don't support it IE, Chrome < 56, etc. - Issue mmistakes#752
- Fallback to default positioning for browser that don't support it IE, Chrome < 56, etc. - Issue mmistakes#752
Hi, thanks for minimal-mistakes! I just deployed it yesterday on kvz.io and loving it so far. One person on reddit reported it looked weird - but it looks fine in my browsers.
The page in question is http://kvz.io/blog/2017/01/04/introducing-lanyon/ - Beyond social buttons, i did not make any layout changes, only config & markdown.
For convenience here is a direct screenshot for Chrome 56 on windows: http://i.imgur.com/BxfzHrn.png
The text was updated successfully, but these errors were encountered: