There is an error in opening the mobile page of the onlyCover parameter

[sy-records]

Bug Report

Steps to reproduce

1. Setting param

window.$docsify = {
 onlyCover: true,
}

What is current behaviour

Should be removed, Otherwise, when you click it, the problem of Figure 2 will appear.

What is the expected behaviour

Other relevant information

• Bug does still occur when all/other plugins are disabled?

• Your OS: mac

• Node.js version:

• npm/yarn version:

• Browser version:

• Docsify version: 4.11.3

• Docsify plugins:

Please create a reproducible sandbox

Mention the docsify version in which this bug was not present (if any)

[anikethsaha]

can we keep the burgur icon and fix the sidebar so that when it is clicked, it slides as it suppose to be ?

else we can remove it 👍

[sy-records]

What it does is load only the cover page when you visit the home page.

I'm not sure if I should remove the burgur icon when it exists.

[sy-records]

https://simps.io/ For my site, I think it should be deleted.

[sy-records]

But the sidebar style of the docsify-dark-mode theme also needs to be fixed.
https://docsify.js.org/ website was affected.

[anikethsaha]

ok cool , I didnt notice the onlyCover option. feel free to fix it.

But the sidebar style of the docsify-dark-mode theme also needs to be fixed.
https://docsify.js.org/ website was affected.

go ahead 👍

[trusktr]

Makes sense to not show the menu in that case.

I added the bug label and put it in the To do column of the 4.x project board. Let's triage issues as we go.

[mohammedsahl]

This seems like a quick CSS fix. I can work on this. From my understanding, all that needs to be done is remove the burger icon (sidebar-toggle) from the cover when viewed on a mobile device. @sy-records

[sy-records]

@mohammedsahl It may be necessary to judge configuration items: onlyCover: true

When onlyCover is true, you can delete the icon on the homepage,

but it does not affect the icon on the body.

[mohammedsahl]

Done with fixing the bug. Writing up an integration test right now. I should have a PR out pretty soon

[mohammedsahl]

The integration test, as it turns out, needs a bit of fiddling around with cypress. While I can push a fix to this issue I don't wanna do so until an integration test is also included, as implied from #1217. What I'm currently working on is setting up the test suit so that multiple configs can be tested, which in-turn, can help others and myself add new tests as required. I suppose it is going to be the same for issue #1233.

Easy fix, but no integration test.

I wanted to know if I should push my changes regardless and shift focus to writing up a suite to test multiple config files right after.

The problem is that I cannot really triage the work required since this is the first time I'll be cypress. But I know for sure that issues #1173 and #1233 are simple enough fixes. I simply want to include a cypress test as this is the ideal practice. Doing that will take some time.

@trusktr @sy-records @anikethsaha