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
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list
If you haven't already, flush all the caches. If it is in the modules folder whether directly or in a custom folder it will show up. If not, something else is wrong with your site; check...
custom module not showing up in modules list
Awful idea! That's not how modules get installed! The number in db indicates the installed state and schema version. You're not supposed to fiddle in the database directly. There's an...
custom module not showing up in modules list