User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/2009011913 Firefox/3.0.6 (.NET CLR 3.5.30729) Any ASP.NET DropDownList that is databound does not get selected value. The browser is producing a postback on the control before the value is obtained. Example: When a user selects an item and the page postsback to the server, the DropDownList is rebound before getting the selected value. The results is always the first item in the list. I posted an example page so you can test it in both IE and Firefox. The example shows both a databound and none databound listbox. It works fine in IE. This could be a potential catastrophic issue as more and more application move to the web. Bad data from this issue could be detrimental and frustrating to users and businesses. Reproducible: Always Steps to Reproduce: 1.Select item in databound dropdownlist 2.item select will always be the first item in the list due to postback issue 3. Actual Results: See Details Expected Results: See Details See Details
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.