Created on 10 August 2023, about 1 year ago
Updated 25 August 2023, about 1 year ago

Problem/Motivation

I love that this module disables a user's ability to edit a field, but I do not love how the widget displays the field values. The most ubiquitous way of displaying disabled fields today seems to be to style the field and inputs in a disabled state. Often micro-copy further illustrates that the field is disabled or read-only.

At the bare minimum, I think a 'Read-Only' label adjacent to the field label would be an improvement. I've attached a quick and dirty screenshot of what this could look like in an admin theme like Gin.

This module could implement the read-only label and base styling for Claro. A dedicated Gin Read-only Field Widget module could be created to make it even nicer for Gin admin theme sites.

✨ Feature request
Status

Closed: works as designed

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States aaronlsilber Charleston, WV

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @aaronlsilber
  • πŸ‡ΊπŸ‡ΈUnited States aaronlsilber Charleston, WV
  • Status changed to Closed: works as designed about 1 year ago
  • πŸ‡¦πŸ‡ΊAustralia thtas

    Thank you for your feedback and glad you find the module useful.

    But I think I'd prefer to elect to to leave this up to the particular theme implementation. This module should not really be too opinionated about the theming above adding appropriate classes to the markup. There should be enough classes on the markup for any theme to prepend text or for a theme/module to add text using pre-process hook.

  • πŸ‡ΊπŸ‡ΈUnited States aaronlsilber Charleston, WV

    Fair enough, thanks for your review!

Production build 0.71.5 2024