[Bug] Disabled fields look the same as non-disabled fields, in dark mode

[jcastroa87]

In dark mode, the active field and the disabled fields look the same, there is no clear graphical difference for the user experience. For example in this image text input "Name" is active and text input "Name 2" as disabled and they look exactly the same.

[tabacitu]

I see Tabler styles "readonly" differently from "disabled":

• disabled is greyed out
• readonly is same as normal but uneditable

I think this makes sense, right? We can do the same in our custom inputs.

[tabacitu]

CoreUIv4 does the same thing:

So it might be standard-practice.

---

I remember we made readonly inputs look like disabled in CoreUIv2 (Backstrap), but I don't think we should do that any more. Let's keep the themes as much as possible "as they are".

So to answer your question again @jorgetwgroup - we try to replicate the same looks in our custom fields:

• readonly looks the same but is unclickable;
• disabled looks greyed out;

[tabacitu]

So to sum up, the bug is that in all inputs (including the text field):

• on dark mode, readonly looks the same as normal - not ok ❌
• on dark mode, disabled looks the same as normal - not ok ❌
• on light mode, readonly looks white but unclickable - that's ok ✅
• on light more, disabled looks grey and unclickable - that's ok ✅