[6.x]: Fields on a revision are shown as disabled instead of read-only

Closed
#20,271 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@riasvdv is already working on this.

Since Nov 3, 2026.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
php

Research direction

Start from the page payload that sets "mode": "readOnly" for a revision, then find where the field and input rendering turns that mode into a disabled attribute instead of readonly. The issue names no files, so trace the mode from the revisions panel to the field templates. Done means revision fields render with readonly and stay focusable, and the revision view matches the Field read-only story.

Written by the indexing model from the issue text.

Description

bug repo:cms
What happened?

Steps to reproduce

  1. Open an entry that has a few revisions.
  2. Open an older revision from the Revisions panel.

Expected behavior

The fields are shown read-only, like the read-only Field story in the UI Storybook (and like revisions in Craft 5): the values are easy to read, and can be focused, scrolled and selected.

Actual behavior

Every field is disabled. The values are dimmed (the title text renders at about 2.1:1 contrast against the white background), they can't be focused with the keyboard, and screen readers announce them as unavailable.

The page payload marks the controls as read-only ("mode": "readOnly"), but the rendered fields and inputs have disabled set and not readonly.

Craft CMS version

6.x-dev (craftcms/cms at 395aae2)

PHP version

No response

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions
Dominant language
PHP
Stars
3.6k
Forks
712
Avg merge
13h 20m
Merged PRs (30d)
357

Getting set up

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 craftcms/cms

All issues in craftcms/cms

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.