CiviCRM Community Forums (archive)

I am working on an event that needs some conditional fields which requires a little javascript. As I was working on determining the jquery selectors I would need to show/hide various options, I noticed that the fields should render in a div with a class named '$fieldname-section'. That holds true for html select and text box fields, but fields rendered as checkboxes or radio buttons were rendering as just ' -section'.

I took a look at the smarty debug output and the template file and found that the template was looking for an id attribute on the field object which doesn't exist for the items that will be rendered as checkboxes or radio buttons.

In the template we have
{assign var=n value=$field.name} and the id is grabbed as the field is being rendered
<div class="crm-section {$form.$n.id}-section">
I changed the rendered div to simply
<div class="crm-section {$n}-section"> which works fine on my single form for now. Is there any danger in just using the name attribute? It appears to be the same value as the id attribute, but there may be cases when this is not true.

Should this be filed as a (very minor) bug?