Custom Attributes dialog is cut off on mobile screens
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
Research direction
Start at the site configuration page and locate the custom attributes dialog opened from /cp/sites. Reproduce at a viewport narrower than 450px, then inspect the dialog layout and its close and per-key remove controls. Done means the dialog and both kinds of controls fit on screen and remain usable at that width.
Written by the indexing model from the issue text.
Description
Bug description
On the site configuration page, on mobile screens with viewport widths less than 450px, the custom attributes dialog UI is cut off. Both the button for closing the dialog and removing individual attributes are missing.
How to reproduce
- Set the browser viewport width to less than 450px
- Goto /cp/sites
- Click the Add attributes dropdown to open the dialog
Note, I tested this on:
- Firefox Responsive Design Mode
- Device emulated: iPhone 17 preset (402 × 874, DPR 3)
Expected: The dialog fits within the screen, with the close button and per-key remove buttons fully visible and usable.
Actual: The dialog is cut off on the right side. The close button and the per-key remove buttons are not visible.
Logs
Environment
Environment
Laravel Version: 12.69.2
PHP Version: 8.3.10
Composer Version: 2.10.2
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file
Storage
public/storage: NOT LINKED
Statamic
Addons: 0
License Key: Not set
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 5.70.0 PRO
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
- Dominant language
- PHP
- Stars
- 4.9k
- Forks
- 647
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 137
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from statamic/cms
-
auth needs more info
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
statamic/cms#15698 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[7.x] Reintroduce parser error for mixed pipe/shorthand modifier syntaxPossibly taken A pull request linked to this issue is open or already merged. Openantlers
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Warning dialog not displayed after updating site handlePossibly taken @lazerg claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
landsman/adminer-desktop#206 ·
Maintainers usually reply within 1 day
-
Explosm: Cyanide & Happiness failed with: https://explosm.net/comics/latest#comic resulted in 307Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
RSS-Bridge/rss-bridge#5154 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
iftechfoundation/ifdb#1415 ·
Maintainers usually reply within 1 day