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
AFAIK, this is part of the FullCalendar library and it doesn't create a separate View Display. If you want to customise the look and feel, you will need to target the elements with CSS....
FullCalendar Views - way to modify list view?
CSS - font-weight: bold. If in the future you want to remove the bold for that field on all pages of the site, changing the formatting of all pages is very difficult, unlike changing the CSS...
Use text editors in Summary Field
thanks! you understood me perfectly. Displays was the place to go... now it seems so obvious! thanks!!@
How to switch on/off taxonomy titles within a node?