mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Problem with big tables on page #195
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Irbis-snowbars on GitHub (Oct 31, 2016).
BookStack Version: 0.12.2
PHP Version: PHP 7.0.8-0ubuntu0.16.04.3 (cli) ( NTS )
MySQL Version: 5.7.16-0ubuntu0.16.04.1 (Ubuntu)
Expected Behavior:
The correct location of the block "Book tree" to the left of the page content, IMHO.
Actual Behavior:
At the moment a large table in the pages of the book overlap a block "book tree".
@ubaltaci commented on GitHub (Nov 2, 2016):
I second that tree navigation should be placed in left side.
@AngelGL commented on GitHub (Nov 10, 2016):
Would be great if add the option to use horizontal scroll for big tables. It would solve the problem when visiting the page from mobile device.
@ghost commented on GitHub (Feb 1, 2017):
Yes, we are also facing the same problem for big tables.
@pranay-kd commented on GitHub (May 1, 2017):
Also facing the same issue.
@s0n- commented on GitHub (Aug 22, 2017):
Also facing the same problem and I would add that they arent necessarily "big" tables either. A lot of the tables we use get cut off until you scroll down.
Moving navigation to the left would be a great and simple start.
@ssddanbrown commented on GitHub (Aug 22, 2017):
@s0n- As part of the in-progress design update the navigation is moving to the left.
@s0n- commented on GitHub (Aug 22, 2017):
@ssddanbrown Thank you very much, I want to thank you for all the work you've put into this product. Have you thought about using a funding platform for new features? I know personally I would put dollars or whatever you needed behind specific features for the product.
@ezzra commented on GitHub (Apr 3, 2019):
I guess this could be closed
@ssddanbrown commented on GitHub (Apr 11, 2019):
@ezzra Thanks for highlighting this.
Will close, Issues relating to responsiveness can be discussed within #1387