-
Notifications
You must be signed in to change notification settings - Fork 59
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
Problem: documentation page misalignment #254
Labels
Comments
Thanks for looking into this issue! Which browser were you trying to use to
reproduce the issur? I know that it doesn't reproduce in Firefox but it
does in WebKit-based browsers. I didn't do any dirty/quick fixes yet
…On Jun 7, 2017 8:04 PM, "cougarten" ***@***.***> wrote:
You made a dirty fix already, right? I can't reproduce.
I think your content slipped behind your header bar. You have to account
for the occupied space because with the fixed position the header does not
push the rest of the site down.
Enter your header height here:
![http://malea.lacerta.uberspace.de/up/3f76685b-b15e-
4b24-bcb8-577aaec24987.png]
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#254 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAABxPHmfukNxBKTZY5Ymet1LU8vSjfQks5sBp_qgaJpZM4NFPCE>
.
|
I just managed to reproduce in chrome. It's a seperate issue from what I described. What I described would also be good to do though, on windows the scroll-bar gets cut off at the top currently. I don't know what causes the scrolling, sorry. |
is there a source of theme.js? I doubt CSS can change the scroll position itself. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
URL: http://pumpkindb.org/doc/master
Upon initial load, all documentation pages are scrolled down just a tiny bit, but it makes a bad initial impression (feels messy). Has something to do with the gitbook theme we're using, I suppose. When pages are changed by clicking on menu items, there is no such issue because subsequent navigation is done over AJAX.
This is how it should be:
The text was updated successfully, but these errors were encountered: