148627 - selected option item isn't dynamically changed with JS

Status: RESOLVED WORKSFORME

(Core :: DOM: Core & HTML, defect)

Description

[Sagie Maoz]

In the specified URL, selecting a 'family' in the first <SELECT> changes the
values and texts of the second select tag using a simple JavaScript script.
It seems that the selected item in the second list is not modified as it's
configured to be and the last selected item still exists and is selected there.

I have tried different scripts that are supposed to do the same but the result
in Mozilla is the same.
These scripts work well on Netscape 6 and MSIE.

Comment 1

[Phil Schwartau]

Browser, not engine ---> DOM Level 0

Sagie: 

What build ID of Mozilla are you using? If I try this test on WinNT,
I get the same behavior in IE6 as in Mozilla trunk binary 2002053008.
This is what I get when I change choices in the 1st selectbox, and
make no manual choices in the 2nd selectbox:


           1st selectbox             2nd selectbox
      1.      "Levy"      -------->     "dani"
      2.      "Band"      -------->     "ohand"


Now suppose I choose "Levy" in the 1st selectbox, but change the item
in the 2nd selectbox from "dani" to the second possibility, "michal".
Now if I change the 1st selectbox to "Band", the 2nd selectbox shows
the second possible choice, "etty" instead of "ohand". That is,


           1st selectbox             2nd selectbox
      1.      "Levy"      -------->     "dani"
      2.  ------------------------>  Manually change item to "michal"
      3.      "Band"      -------->     "etty"



Again, the behavior is the same for me in Mozilla as it is in IE6.
Looking at the code, I can't see any line that dynamically sets the
selected option in the second selectbox, so I don't see any bug.

Comment 2

[Sagie Maoz]

Using build ID 2002052306 (1.0rc3).
1. Levy ---> "Choose Family"
2. Band ---> "Choose Family"

3. "Levy" ---> "Choose Family"
4. Manually change item to "michal"
5. "Band" ---> "michal"

Build specific bug?

Comment 3

[Phil Schwartau]

Yes, this could be build-specific. Could you try the latest nightly
build and see if the problem still exists? 

If it does, you could try running Mozilla under a new profile.
Sometimes that fixes things. To do this, launch Mozilla from 
a console window as follows:

[(path to Mozilla)] ./mozilla -profilemanager


But I'm hoping the up-to-date build will do the trick -

Comment 4

[Sagie Maoz]

Upgrading to nightly build (ID 2002060208) solved the problem. No need of a new
profile.
Thank you Phil ;)