-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Docs layout issue: content container does not grow to take all the available space #8369
Comments
Can someone close this Issue if it's completed? |
It's not completed yet. The issue is still there. |
In case someone finds this and still has the same issue. I added the following to my /* Full Size Sidebar */
.main-wrapper > div {
flex: 1 0
} |
Will look into it, indeed it seems we have a little flex problem. Not related to the hideable sidebar, can also be seen here: https://tutorial.docusaurus.io/docs/tutorial-basics/congratulations/ @Tandashi good workaround. Do you want to send a PR with a proper solution? |
@slorber Sure, will try my best |
@slorber Looks like it's already fixed in the |
Thanks, looks like you are right and it's fixed already! See prod URL: https://docusaurus.io/tests/docs/more-test Looks like this issue has been fixed in #7966 and it's a breaking change pr and not backported to 2.x Will do a quick fix for docusaurus-v2 branch |
should be fixed in #8707 |
fix issue reported in #8369 (comment)
Have you read the Contributing Guidelines on issues?
Prerequisites
npm run clear
oryarn clear
command.rm -rf node_modules yarn.lock package-lock.json
and re-installing packages.Description
The docs layout looks particularly weird when sidebar/content is smaller than viewport, which is likely to be the case on small pages + vertical screen
Follow-up of bug discussed in:
Reproducible demo
No response
Steps to reproduce
https://docusaurus.io/tests/docs/doc-with-another-sidebar
Expected behavior
The content container (sidebar + main) should grow
Actual behavior
The content container does not expand
Your environment
No response
Self-service
The text was updated successfully, but these errors were encountered: