Re: Bug: Option element containing illegal font eats whitespace

Using MixedContent seems like a reasonable solution.
I think it is worth extending ParseText to discard
all inline tags not just font. For textarea, is it
worth escaping all instances of < and & in the content?
Isolated ones will be already, but what about the case
where the users will be allowed to type markup in to
the textarea box, and the author wants to include some
as the default value for the field. 

Regards,

-- Dave Raggett <dsr@w3.org> or <dave.raggett@openwave.com>
W3C Visiting Fellow, see http://www.w3.org/People/Raggett 
tel/fax: +44 122 578 3011 (or 2521) +44 771 213 7629 (mobile)

Received on Tuesday, 29 May 2001 08:12:03 UTC