In Communicator, select[n].value is a shortcut to select.options[n].value. This is not the case with Gecko. However, sites may be using this feature (http://snorkel/ernie/top100.html being one) and it may be desired for compatibility mode.

Setting all current Open/Normal to M4.

per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

QA contact re-assigned according to the product areas we're currently working on.

Vidur, this is a dup of bug 3340 (or vice versa). I'm not sure how to attack this. Should we be enabling this for backwards compatibility? I'm sure I'm oversimplifying, but can we just give HTMLSelectElement a length attribute and an item(index) method in HTMLSelectElement.idl, then define the corresponding methods? How else does the js know that it can index into an HTMLCollection?

Eric, since the standard DOM doesn't define this, we need to add an additional interface that includes the item() method and length property. To be conformant with previous cases, this additional interface is generally prefixed with "NS" (NSHTMLSelectElement) and the IDL for it is placed in the same file as that of the original interface (HTMLSelectElement.idl). Regenerating the IDL will create a new XPCOM interface that needs to be implemented by the SELECT element class. The JavaScript glue stuff should then work. Let me know if you have any questions.

*** Bug 3340 has been marked as a duplicate of this bug. ***

Redistributing bugs...

Just checked in a fix.

Verified. Working fine now.