Read only field dashed border is not visually distinctive enough
Maintainers usually reply within 1 day
@jaygeorge is already working on this.
Since Oct 15, 2026.
Assessment
This issue has not been assessed yet.
Description
Bug description
It appears that with the Statamic 5 -> 6 update read-only fields have only received a dashed border. Before, they were grayed out and had a "Read only" subscript;
We are receiving reports from clients that this is not visually distinctive enough. Can we fix that?
How to reproduce
- Have a read-only field
- View the UI in Statamic 5
- View the UI in Statamic 6
- Compare
Logs
Environment
Environment
Laravel Version: 12.69.3
PHP Version: 8.4.6
Composer Version: 2.8.8
Environment: dev
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: nl
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: file
Database: mariadb
Logs: stack / single
Mail: smtp
Queue: sync
Session: file
Storage
public/storage: NOT LINKED
Statamic
Addons: 4
License Key: Set
Sites: 4
Stache Watcher: Disabled (auto)
Static Caching: Disabled
Version: 6.35.1 PRO
Statamic Addons
statamic-rad-pack/runway: 9.7.0
statamic/eloquent-driver: 5.12.2
statamic/seo-pro: 7.15.1
Statamic Eloquent Driver
Addon Settings: file
Asset Containers: file
Assets: eloquent
Blueprints: file
Collection Trees: eloquent
Collections: file
Entries: eloquent
Fieldsets: file
Form Submissions: eloquent
Forms: file
Global Sets: file
Global Variables: eloquent
Navigation Trees: eloquent
Navigations: file
Revisions: eloquent
Sites: file
Taxonomies: file
Terms: file
Tokens: eloquent
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
- Dominant language
- PHP
- Stars
- 4.9k
- Forks
- 647
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 122
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
-
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
-
caching nocache
Difficulty 3/5 1-2 days Newbie friendliness 42/100
statamic/cms#15643 · 2 comments ·
Maintainers usually reply within 1 day
-
navigations
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
Authentication / Authorization Feature: Volunteer
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
PHP workflow streaming requests buffer the full SSE responsePossibly taken @Winoren claimed this today. Openreview: medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
langgenius/dify#44270 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
bug customer-reported
Difficulty 1/5 Under an hour Newbie friendliness 90/100
MagnaCapax/PMSS#1085 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day