[TYPO3-dev] weird rendering of form with radio buttons (4.0rc2, CSC)

[Christopher]

Hi,

On 3/28/06, Axel Jindra <a.jindra at gmx.de> wrote:
> Hi,
> sorry for posting twice (posted before on typo3.english), but I think
> it's a problem with the CSC rendering so it might belong in this group:
>
> I have a mailform with radio buttons which gets rendered strangely cause
> of a double fieldset around the radio buttons:
>
> <div class="csc-mailform-field">Anrede
>    <fieldset class="csc-mailform-radio" id="testform_radio">
>    <fieldset id="mailformAnrede">
>    <legend>Anrede</legend>
>    <input type="radio" name="Anrede" id="mailformAnredeHerr"
> value="Herr" class="csc-mailform-radio" />
>    <label for="mailformAnredeHerr">Herr</label>
>    <br />
>    <input type="radio" name="Anrede" id="mailformAnredeFrau"
> value="Frau" class="csc-mailform-radio" />
>    <label for="mailformAnredeFrau">Frau</label>
>    <br />
>    </fieldset>
>    </fieldset>
> </div>
>
> I've had a look at CSC and it says:
>
> 1248: tt_content.mailform.20 {
> 1254:   layout = <div class="csc-mailform-field">###LABEL###
> ###FIELD###</div>
> 1256:   RADIO.layout = <div class="csc-mailform-field">###LABEL###
> <fieldset class="csc-mailform-radio"
> id="testform_radio">###FIELD###</fieldset></div>
> 1257:   LABEL.layout = <div class="csc-mailform-field">###LABEL### <span
> class="csc-mailform-label">###FIELD###</span></div>
> 1258:   labelWrap.wrap = |
> 1260:   radioWrap.wrap = |
> 1262:   stdWrap.wrap = <fieldset class="csc-mailform"> | </fieldset>
> 1263:   params.radio = class="csc-mailform-radio"
> 1266: }
>
> So I see the outer fieldset is rendered statically and the inner one
> dynamically. Problems will arise if there is more than one radio button
> fieldset because the id attribute is not unique anymore. On the other
> hand the fieldset with the dynamically created id attribute lacks the
> class attribute.
>
> Somewhat confused what to do... Is this a bug worth posting on
> bugs.typo3.org?

There are at least a couple of bugs already posted about this issue in
the bugtracker--though it's not clear to me what action is being /
will be taken.

-Christopher