User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2.1) Gecko/20021130 When searching for the furniture type "Desk" in Mozilla, the site reports "Sorry, we did not find any products that fit your search criteria, please try another search." while under IE, the site finds many examples. Is there some sort of indexing problem, perhaps? Reproducible: Always Steps to Reproduce: 1.Go to web site. 2.Selecte Desk 3.Mash the "Search" button. 4.Say bummer. Actual Results: I said bummer, then remembered that I had seen such things before. Oh--you meant that I saw the "Sorry" message. Expected Results: Showed me an array of lovely desks. I am rating this as serious, as it looks like everything is working fine, when it clearly is not.
Interesting. Submitting in NS4 goes to: http://www.harden.com/pages/products.asp?key=800&value=815&id=&type=r&menu=784&showlist=1&start=752 Loading this in Mozilla shows desks. Submitting in mozilla goes to: http://www.harden.com/pages/products.asp?key=800&value=815&id=&type=r&menu=784&showlist=1&start=752&item1=0&item2=0 Loading this in ns4 shows no desks. The problem is this BiuldItemList() function that assumes that some values should be "null" in non-IE browser whereas they are the empty string in mozilla... Over to form controls to decide whether we should have null or empty string there.
Assignee: asa → form
Status: UNCONFIRMED → NEW
Component: Browser-General → Layout: Form Controls
Ever confirmed: true
OS: MacOS X → All
QA Contact: asa → tpreston
Hardware: Macintosh → All
Assignee: layout.form-controls → nobody
QA Contact: tpreston → layout.form-controls
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 2 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.