"<option>" quirk

[Mike Elston]

Mark Hanley <mhanley at mdhost.cse.tek.com> wrote:
> I was fiddling with OW2.7 yesterday and noticed that
> repeating a text string after an <option> tag in HTML
> caused OW to ignore the <option> if the tag was a
> duplicate. For example :
>
> <select name=x>
> <option value=1>a
> <option value=2>a
> </select>
>
> results in a selector with 1 option - a. I realize
> OW2.7 is unsupported, but I was wondering if this is
> correct behavior and if OW3 behaves the same? FWIW, I
> tried similar code on Netscape at work, and it reports
> 2 options : a & a.

Probably because the appkit doesn't add an item to a popup if it's already  
there. Makes sense... even if Netscape doesn't agree.  But I see what you  
mean.

OTOH, try:

	<select name=x size=2>
	  <option value=1>a
	  <option value=2>a
	</select>

I guess no one can be perfect all the time...
/mike
--
Mike Elston                  | CaiSys                _|>
consultant                   | NeXT, Unix, CAI
Tel/Fax: +44 (0)171 987 0581
Email: mike at caisys.demon.co.uk (incl. NeXTMail and MIME)
***  The year 2000 is the *last* year of the *20th* century   ***
*** (the next millenium doesn't start till 00:00 01/01/01...) ***