See reply below:

On 11/3/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> I think this change is controversial: several people have voiced their
> concerns regarding this change. It is something we have been opposed
> to until very recently (label with <span/>). You propose to change
> markup that is outside Wicket's control, I think that is a slippery
> slope and I advise against it, hence my -0.9.
>
> A <div /> does have a different meaning in XML versus HTML. We
> shouldn't just go about and muck things up.
>
> I've done some digging in firefox's bugzilla and found:
>  - https://bugzilla.mozilla.org/show_bug.cgi?id=327637
>  - https://bugzilla.mozilla.org/show_bug.cgi?id=369609
>  - https://bugzilla.mozilla.org/show_bug.cgi?id=135425
>
> where the first 2 are marked as dupes for the last one.
>
> After reading this and the firefox developers I think the <div />
> element used in these cases is a user bug, and therefore my comparison
> to fixing spelling errors still holds.
>
> Does this buggy behavior still exist when you serve the page as XML?
It exists when you serve it as xhtml document. However not with xml
header, as I stated before, xml header is unusable. Unfortunately.

>
> So if you go ahead make sure it works for XML, XHTML and HTML documents.

I don't see what possibly it could break.
For xml and xhtml document, <div /> and <div></div> are semantically
equivalent. For html documents <div /> is an error, however if we
replace it with <div></div> the error is corrected.

I think the practical approach is justified here. Most of people are
using xhtml doctype. What good is xhtml doctype when you can't have
valid xml tags in document?

I wish we could just set the mime type to text/xml and the problem
would be gone. But text/xml doesn't work in internet explorer and that
is hardly a fact that you can ignore. So the only way of serving xhtml
files is with html header.

I know this is a browsers problem but if we used that as excuse every
time we wouldn't get anywhere. Part of web framework responsibility is
to shield user from inconsistencies like this.

-Matej

>
> Martijn
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.0-beta4 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
>

Reply via email to