Closed Bug 212816 Opened 21 years ago Closed 21 years ago

Browser selects wrong item in Choice after a Browser "Back"

Categories

(Core :: Layout, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 182157

People

(Reporter: cosmicrae, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624

When a Choice has multiple possible selections that have the same meaning (such
as A1, B, A2, C, A3), the user selects "A1", goes forward a page, then back, the
browser selects a different Choice item with the same meaning (usually the last
item in the Choice with the same meaning). In this contrived example it would be
"A3". This is not a show stopper, but is an annoyance from the perspective of
doing a double-take when a different (and less recognizable) item is selected
after the "Back".

Reproducible: Always

Steps to Reproduce:
1. go to the USPS International Rate Calculator
2. select "Package"
3. pick a country that has multiple entries (i.e. UK or Japan)
4. Enter some weight
5. click "Continue"
6. click on the Browser back icon
Actual Results:  
A different entry is shown in the country Choice. It is actually for the same
country, but not the one that I selected. It is usually (probably always) the
last item in the Choice for that country. For example, selecting "Great Britian"
results in "Wales (Great Britian and Northern Ireland)" being selected after the
Back click.

Expected Results:  
Should have redrawn with the same item selected in the Choice.

*** This bug has been marked as a duplicate of 181257 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Whoops.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---

*** This bug has been marked as a duplicate of 182157 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.