In forms that use <OPTION SELECTED VALUE="Foo">, the 'SELECTED' option is ignored and the top item in the list of <OPTION>'s is selected by default. This can (and does in my case) break sites that depend on the chosen SELECTED option being selected by default. The option can be selected manually, but that breaks the use of SELECTED.
This works: <option selected value="Unassigned">Unassigned</option> This does not: <option value="Unassigned" selected>Unassigned</option>
worksforme, linux build 2002-02-24-06. See attached testcase -- both comboboxes have the right thing selected. Avleen, what build are you using? Is there an HTML page that demonstrates the problem?
I don't know how to explain this :-/ Even the test cases I had set up appear to work now :-/ But I certainly wasn't just seeing things!
> I don't know how to explain this :-/ 'Twas those damn daemons I tell you! <ahem> ;-)
I found a way to replecate the problem - this prompted me to change the severity to 'minor'. Open a page with a form, where 'selected' is not used. Now, edit the source so that 'selected' IS used, and click reload. The menu isn't updated to used the new 'selected' :-)
That's because form values persist across reload (bug 46845). Try shift-reload.
hmmmm I might be wrong.. if I am please correct me! Isn't the point of 'reload', to check if the page has been updated, and if so display the new page - and not keep old values around? If so, I don't see why there is a need for a Shift-Reload. I understand that it's used to tell systems to ignore the cache and fetch from the server, but if 'reload' is fetching from the server, why isn't it updating the screen? :-)