On Wed, 15 Oct 2003, Gisle Aas wrote: [...] > <option label=x value=3>2</option> [...] > Of the browsers I have here Mozilla displays "2" for the second value > while konqueror shows "x". I guess my question is what MSIE shows?
2! Damn. (For IE 5 -- has there been any standards-compliance effort with IE 6? I certainly doubt it on this particular point.) [...] > > > <input name=sex type=radio value=F> <b>Fe</b>male > > > > > > in the expected way. > > > > Officially, those <b>s aren't allowed, are they? > > Yes. After the input you are in plain text context. The input tag is > implicitly empty. Oh, right. > > seen them 'in the wild', though :-( Probably I should strip tags even for > > OPTION element contents... > > But I think <option> is different as it is a container. You can't > have <b> here, but I have not tested what browsers do. Officially you can't, right, but we all know how this game works ;-). But as I said, my parser won't pick any up anyway, being event-driven, and IIRC yours code is similar in that respect (albeit 'pull' rather than 'push', which is a nicer way of doing it). [...] > > I see. It can still be used for the list items of INPUT type=radio, or > > whatever, though (though, as I said, probably rarely). > > I'll deal with it if somebody complains :) Good plan. John
