[Patch] a renderer for <FIELDSET> and <LEGEND>

[Germain Garand]

Le Jeudi 25 Juillet 2002 07:57, Lars Knoll a écrit :
> > Which means, if you follow strictly the spec, that Legend must accept
> > funny things such as <IMG>s, <INPUT>s, anchors and other fontstyling
> > element, but should not actually render them because the container is not
> > %flow !?! That sucks beyond belief !
>
> Ok. You;re right. But that means that we should treat the first legend as
> the one to render the "legend" of the fieldset, and all others (they should
> not exist, but we all know how web pages look...) as regular flows.

Ah OK... that's also the behaviour of Mozilla, I think.
If another legend was given, I was removing the previous one, so I've corrected this - it even simplify things.
I also handle better the case were an element of the legend would be absolutely positioned  or floating (yuck!)

Updated patch attached.

>> I do ensure that legend is unique inside it's HTMLFieldsetElementImpl, but
>> you could only extract #PCDATAs from here, as innerText() do... that's not
>> following the DTD either... why would they be more important than e.g. an
>> image ?
>
>Please apply your patch then :)

Thanks ! I'll do it in a few hours then... 

Bye,
Germain



-------------- next part --------------
A non-text attachment was scrubbed...
Name: html_formimpl.diff
Type: text/x-diff
Size: 4489 bytes
Desc: not available
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20020725/f91c8a45/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: render_form.diff
Type: text/x-diff
Size: 7883 bytes
Desc: not available
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20020725/f91c8a45/attachment-0001.diff>