Closed Bug 620448 Opened 15 years ago Closed 15 years ago

Trouble using sort menus on m.sears.com

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 619426

People

(Reporter: marcia, Unassigned)

References

()

Details

(Whiteboard: [websitecompatibility])

Seen while running the latest nightly on the HTC Evo. STR: 1. Load the sears.com site. In my case it detects the mobile version. 2. Select Browse Departments 3. Select Appliances -> Refrigerators 4. Select Counter Depth 5. Select some sort criteria and then hit go Expected: It would sort the items as the Android browser does Actual: It cannot detect that we have made a selection.
Whiteboard: [websitecompatibility]
I can't reproduce the problem with the latest nightly build 20110103 on a Droid II. Sort criteria works for me. Could you try again with the latest nightly build and report back if you still see the issue? Thanks
Status: NEW → UNCONFIRMED
Ever confirmed: false
This works for me, using: Mozilla/5.0 (Android; Linux armv7l; rv:2.0b9pre) Gecko/20110103 Firefox/4.0b9pre Fennec/4.0b4pre ID:20110103042041 Marcia, can you still reproduce this?
Using the latest nightly, I can perform the action but I still do see an issue. Here are my what I see when I follow the same STR: Using the android browser, when I select the sort criteria I then am returned to where the "Go" button is next to the "Sort By" box (The menu collapses back) Using Fennec, after I select the criteria the entire selection area never collapses, so it obscures the "Go" button which is next to the sort criteria box. I can still use the "Go" button in the top search area. So there appears to still be a layout issue or some sort of issue with the way the sort menu is handled.
I think we can close this bug, the problem with the select menu as you describe it made me thought of bug 619426 isn't it?
Ok, duping to 619426.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.