I came across this problem while working on #2731, where I needed to target some form elements in CSS. This turned out to not be as easy as expected, because the names of the form elements were too generic (like label, delta, and description). The requirement was to add more specific classes to the wrapper <div>s of the form elements.
I will explain in code examples, but instead of using the code in that specific use case, I will use more simplified and generic examples. So say you have this form definition:
$form['parent'] = array(
'#parents' => array(),
);
$form['parent']['checkbox'] = array(
'#type' => 'checkbox',
'#title' => t('Do something'),
);
$form['parent']['textfield'] = array(
'#type' => 'textfield',
'#title' => t('Enter some text'),
);
This will produce the following code:
<form class="some-form" id="some-form" >
<div>
<div class="form-item form-type-checkbox form-item-checkbox">
<label class="option" for="edit-checkbox">Do something </label>
<input type="checkbox" id="edit-checkbox" name="checkbox" class="form-checkbox">
</div>
<div class="form-item form-type-textfield form-item-textfield" >
<label for="edit-textfield">Enter some text </label>
<input type="text" id="edit-textfield" name="textfield" class="form-text">
</div>
</div>
</form>
...
Recent comments
Still trying to understand: you have this view and an exposed form on it, right. And you have two independent taxonomy terms and try to filter by them? Or is this a hierarchal...
Parent items won't show on Leaflet Widget.
Sorry. It is a taxonomy term.
Parent items won't show on Leaflet Widget.
Hi geoma, hm... I'm not quite sure, what "parent" means in that context. Is it a taxonomy term? Or a related node type? The map will only show geo data from the field...
Parent items won't show on Leaflet Widget.