"<option>" quirk

[Ken Case]

> 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.

I don't believe we're actually ignoring the option tag; I'm pretty  
sure we're putting it into the popup where it's getting ignroed because  
the AppKit doesn't allow duplicate options in popups.

> I realize OW2.7 is unsupported, but I was wondering if this is
> correct behavior and if OW3 behaves the same?

OmniWeb 3 has the same behavior (for the same reason).

> FWIW, I tried similar code on Netscape at work, and it reports
> 2 options : a & a.

I don't remember off-hand what the HTML standard says about this case  
(probably nothing), but since Netscape allows duplicate options, I  
guess we'd better too.  (Since the AppKit doesn't allow them, I guess  
that means we'll add some spaces to the end of those duplicate options  
to make them unique.)

Thanks for the report!

				Ken