Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Custom Attributes dialog is cut off on mobile screens

Open Beginner friendly
#15,721 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
67/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
laravel, php
Domain
design, frontend

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
Image
  1. Set the browser viewport width to less than 450px
  2. Goto /cp/sites
  3. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from statamic/cms

All issues in statamic/cms

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.