I was trying to figure out a way to solve #1968, but I see no way to target all these elements effectively in a single CSS rule. It would be easy if the #states elements had a generic .has-states class and perhaps also a second class with the specific state per element case. So a .states-[state] class where [state] would be one of:
- enabled
- disabled
- required
- optional
- visible
- invisible
- checked
- unchecked
- expanded
- collapsed
- relevant
- irrelevant
- valid
- invalid
- touched
- untouched
- readwrite
- readonly
Perhaps also a .states-lvl-x class if possible (where x is the numeric level of how many parent elements the element in question has).
I would file a PR, but this touches the Field API and I am not even remotely ready for than yet, so I rely on somebody else to tackle this. Once implemented, I think it will be easy(ier) for me to sort #1968
Recent comments
I do have the apache status page set up ... I will look in to this really fast. BRB.
Status Report Page throws : Forbidden You don't have permission to access this resource.
Hi TallElfin, that sounds like a webserver misconfiguration. It has nothing to do with the CMS itself. So... other paths work just fine, also admin paths, only the path "admin/...
Status Report Page throws : Forbidden You don't have permission to access this resource.
Hi Editing I see this: The CSS looks like this: /* Level 1: Standard Numbers */ .field-name-body ol { list-style-type: decimal; } /* Level 2: Lowercase Letters */ .field...
Numbered List format is different when editing