Changing the selected index of a select element via the DOM doesn't seem to be reflected on the screen. To reproduce the symptoms: 1. Have NGLayout display a form containing a two-option select element. The first option is displayed in the list box. 2. Now, via XPCOM (nsIDOMHTMLSelectElement's SetSelectedIndex), set the index of the selected option to 1 (the index of the second option). The first option is still displayed in the list box, which is incorrect. 3. Note however that nsIDOMHTMLSelectElement's GetSelectedIndex now returns 1, indicating that the DOM was correctly updated (but the screen wasn't). This is the behavior using a Win32 optimized build of NGLayout, running under NT 4.0.

Using a debug 2/24 NT build, this works ok as the following test illustrates. Recent changes may have fixed this if an older build was used. An optimized build should not be causing this. <form> <input type=button value="print selectedIndex" onclick="printSelectedIndex()">&nbsp; <input type=button value="setSelectedIndex to 1" onclick="setSelectedIndex()"> <BR> <select name="select1"> <option value="std"> Standard </option> <option value="overnite"> Overnight </option> </select> <script> var selects = document.getElementsByTagName("SELECT"); var numSelects = selects.length; function printSelectedIndex() { for (var i = 0; i < numSelects; i++) { dump("selected index = " + selects[i].selectedIndex + "\n"); } } function setSelectedIndex() { selects[0].selectedIndex=1; } </script> </body> </html>

This seems working fine. Marking as verified.