Skip to content
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

[Bug] Page and Book Navigation wrong positioned (auto-scroll does not work) #1434

Closed
JHenneberg opened this issue May 8, 2019 · 2 comments

Comments

@JHenneberg
Copy link

commented May 8, 2019

Describe the bug
The problem appeary in Firefox (66.0.5) and Chrome ( 74.0.3729.131) a bit differently. Page and Book Navigation is wrong positioned in long articles when the window of Firefox/Chrome is so small in width so that the Details and Actions Panel is on the left side too. In Firefox the Navigations are positioned in the vertical middle and in chrome always on top. The auto-scroll is not working

In Addition to this in FireFox the Content area is also not shown correctly. You need to use the herizontal scrollbar because it is not adjusting to the size of the window.

Steps To Reproduce
Steps to reproduce the behavior:

  1. You need to open a relative long article for example "Examples of Different Content" from the demo.
  2. Then adjust the width of the window that the Details and Actions Panel is on the left side too
  3. See error

Expected behavior
Page and Booknavigation should be right under the Details and Actions Panel and then following when you scroll vertically

Screenshots
Firefox
image

Chrome
image

Your Configuration (please complete the following information):

  • Exact BookStack Version (Found in settings): 0.26.0
@ssddanbrown

This comment has been minimized.

Copy link
Member

commented Jun 16, 2019

Thanks for reporting @JHenneberg. These points have been address in master, will be in the next release.
Note that I've made it so only the original left sidebar items will remain sticky on this screen size (Page & Book navigation items mainly) due to layout/sticky limitations. Think that provides a nice experience anyway as the navigation items are more likely to be required when you're further down the page.

@JHenneberg

This comment has been minimized.

Copy link
Author

commented Jun 17, 2019

sounds good. I will check this out in the next release version.
Did you also had time to look into the horizontal scroll issue (That the content area is not adjusting its width)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.