-
Notifications
You must be signed in to change notification settings - Fork 25.8k
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
Sticky TOC pushes feature_row down #2263
Comments
Is this page hosted somewhere so I can inspect the HTML/CSS in browser? Which is why you're seeing the space. |
And no, the feature block is in the same parent div as other paragraphs and the TOC. |
@mmistakes That's more a workaround than a solution to me. The feature block is now at a wrong position. The first block should be right under What actually work for me was to add |
[1fa0092] Work around mmistakes/minimal-mistakes#2263
Not sure. Feature blocks weren't designed to be used as you have so that's likely why they misbehave for you. They're more for splash pages, not posts with table of Contents. Since you're doing images use the gallery helper instead. That's what it's designed for. https://mmistakes.github.io/minimal-mistakes/docs/helpers/#gallery |
Oh, much thanks for that. I should've read the docs thoroughly first! |
Environment
Wrong behavior
The sticky TOC pushes the first
feature_row
at an unexpected place. If the keyposition: sticky;
was removed from the class.sidebar__right.sticky
, then thefeature_row
locates at the correct place (i.e. no margin between it and the above heading 2 Overview).I have since disabled
toc_sticky
for the article to give it a normal look.To reproduce
Create an article with a
feature_row
at top, as well as a few headings to give the TOC some height. Settoc_sticky
on the page and check the result.Other
I'd like to know how to patch the CSS to fix this issue locally, but I'm not experienced in CSS and haven't yet figured out how. Yes, I do patch the CSS to create my own desired layout.
The text was updated successfully, but these errors were encountered: