mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #123] Responsive design issue/UI layout issue. #109
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#109
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @allebb on GitHub (Apr 20, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/123
Using a Windows 10 PC, reproducible in both Google Chrome and Firefox, with my screen resolution 2560 x 1440 I get the following experience:
If I get time this weekend I'll submit a PR to fix it :)
Thanks for a great tool @jc21
@kolbii commented on GitHub (Apr 23, 2019):
Then can you please also fix the following use case:
@jc21 commented on GitHub (Apr 23, 2019):
For the main issue, it feels like there would be some errors in the browser console that would help
@jonfairbanks commented on GitHub (May 4, 2019):
Also seeing this on a 4k display. There are no errors in the console, only the welcome messages.
The following temporarily fixes it for me:
Find the div with id=app. In Chrome, uncheck
display:flex. Alternatively, locate.pagein main.css and remove the same.You should now see a fixed layout minus the footer.
To fix the footer, search for the
<footer>and add the highlighted CSS classes either temporarily in Chrome, or semi-permanently in main.css.Unfortunately any reboots to the host or Docker container will result in having to redo both of these steps.
@jc21 commented on GitHub (May 8, 2019):
The UI is based entirely on Tabler, and it uses the layout and styles from there. It's likely that it's a problem with their project.
@jc21 commented on GitHub (May 8, 2019):
Confirmed that this is because tabler released a new version compatible with latest bootstrap. Have rolled back tabler and will be fixed in 2.0.13
@jonfairbanks commented on GitHub (May 8, 2019):
Thanks a bunch!