Doc Sidebar is covering NavBar Buttons

[fabrusso]

🐛 Bug Report

The navbar in the documentation page is not working.
Is correctly working in the Home page.

I checked the the HTML and It seems that the sidebar containing Doc link has a margin-top that is covering the buttons area.

Have you read the Contributing Guidelines on issues?

yes

To Reproduce

If possible, use https://new.docusaurus.io to create a CodeSandbox reproducible demo of the bug.

(Write your steps here:)

1. Go to documentation
2. Try click on navbar "left positioned" button near the logo

Expected behavior

I expect the buttons to redirect me to the url\src

Actual Behavior

Buttons are not clickable

Your Environment

• Docusaurus version used: @docusaurus/core": "^2.0.0-beta.0
• Environment name and version: Mozilla for Developers
• Operating system and version (desktop or mobile): MacOS BigSur

Reproducible Demo

Doc to check:
https://crono.matchplat.io/docs/installation/installation

Current margin of the child DIV:

Parent DIV covering:

Disabling that margin-top:

The Sidebar with no Margin Top and clickable buttons:

[lex111]

@fabrusso hi, could you please provide a reproducible repo or website link?

[fabrusso]

@fabrusso hi, could you please provide a reproducible repo or website link?

https://crono.matchplat.io/docs/installation/installation

Thanks.

[mhwinkler]

I'm also experiencing this issue, it may be related to CSS minification.

When using the local server, my /styles.css contains:

--ifm-z-index-dropdown: 100;
--ifm-z-index-fixed: 200;
--ifm-z-index-overlay: 400;

After a production build, the same lines read:

--ifm-z-index-dropdown: #100;
--ifm-z-index-fixed: #200;
--ifm-z-index-overlay: #400;

[lex111]

This was fixed in PR cssnano/cssnano#1122 @omgovich thanks for that!

@fabrusso @mhwinkler we have explicitly bumped the appropriate versions of CSS minification packages, but since we use caret ranges, you can simply reinstall dependencies of your site and remove previous build artifacts by running yarn clear command, after that the issue will be fixed.

[ishan-grubtech]

@lex111 when I run npm run start, this fix seems to be working. but when I do an npm run build followed npm run serve it's still broken.

[rrdelaney]

Also still happening to me 😕

[slorber]

@rrdelaney you are using cssnano@5.0.3, please make sure it's not the case anymore.

A good way is to re-generate your lockfile by deleting it, it will pick a newer (non-buggy) cssnano version