build id: June 21, 1999 M6 builds platforms tested against: Mac OS 8.6, Windows NT 4 SP 5 The above URL has a very simple text case. Behavior differs in seamonkey from legacy Netscape browsers in that in 4.x browsers, the mere presence of the multiple attribute displays the list of options as a list box and not a drop-down menu. This behavior is preferable to the current seamonkey behavior as it makes it possible to select multiple items; the current seamonkey behavior apparently makes that impossible. According to the DTD, "visual user agents are not required to present a select element as a list box; they may use any other mechanism, such as a drop-down menu" - I read this as list boxes being the default visual presentation of select elements, with drop-down menus as another option available if the UA so chooses. In this case, we really should do a list box in this one case instead of a menu to improve the user experience. Sample HTML: <form action="mailto:Kligor.T@gee.whiz.com"> <select multiple> <option>Assam <option>Darjeeling <option>Keemun <option>Sencha <option>Yunnan </select> </form>

This is a forms issue.

[TESTCASE] When correctly implemented, the SELECT MULTIPLE tag should allow the user to select multiple items, whether through a listbox or a variation of the dropdown menu, or whatever. See attachment (#914) for testcase.

Reassigning to Kevin.

This has been fixed for gfx-rendered selects in the July 21, 1999 2:55PM build. I'm marking it as [NATIVE-WIDGET] and moving it to M15.

Marking as Native widget issue, since it works with gfx-selects.

What should happen when you use javascript/dom to set the MULTIPLE attribute dynamically?? IE switches layout from list to drop down and back. <FORM> <SELECT ID=oSelect MULTIPLE SIZE="3"> <OPTION>Item 1</OPTION> <OPTION>Item 2</OPTION> <OPTION>Item 3</OPTION> </SELECT> : <BUTTON onclick="document.getElementById('oSelect').multiple=false">One</BUTTON> <BUTTON onclick="document.getElementById('oSelect').multiple=true">Many</BUTTON> </FORM>

Rod, here is something to check the gfx render combo box against.

Yes, this is a bug. I don't think it is worth fixing is it? Kevin, what do you think?

Based on rod's comments, marking as verified wont fix.