mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #255] [Bug]: iPhone UI buttons overflow header on Archives and Statistics pages #156
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#156
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 @Sllepper on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/255
Originally assigned to: @maziggy on GitHub.
Bug Description
On iPhone devices, some header action buttons overflow outside the page container and extend beyond the screen edge.
This issue occurs on the following pages:
Archives Page:
The buttons "Export", "Select", and "Upload 3mf" overflow outside the header area.
Statistics Page:
The buttons "Reset Layout", "Recalculate Cost", and "Export" also overflow beyond the header container.
This appears to be a responsive layout issue on small screen widths.
Screenshots are attached for reference.
Expected Behavior
Header action buttons should stay fully visible within the page header on iPhone screen sizes.
Buttons should adapt properly to small screens, for example by wrapping to a new line, resizing, or collapsing into a menu.
Steps to Reproduce
Printer Model
Not printer-related
Bambuddy Version
0.1.6
Printer Firmware Version
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
No response
Additional Context
No response
Checklist
@Sllepper commented on GitHub (Feb 4, 2026):
@maziggy commented on GitHub (Feb 4, 2026):
Fixed in branch 0.1.8b. Please let me know if it works now.