Closed
Bug 92376
Opened 24 years ago
Closed 21 years ago
[DUP]history fails to remember selected option.
Categories
(Core :: DOM: Navigation, defect)
Core
DOM: Navigation
Tracking
()
Future
People
(Reporter: ssaux, Assigned: rods)
References
()
Details
(Keywords: qawanted)
Reproducible: always.
Using build 07202001.0.9.2, but pretty much anything will do.
To reproduce:
Go to the bugzilla query page.
Select:
product: PSM
target-milestone 2.1
submit.
hit the back button.
The target-milestone is not remembered.
Notes:
4.7X handles that just fine.
I suspect that two things might play a role in the session history being lost in
this case. One is that by selecting PSM, the page javascript changes the
available options for the target-milestone. The other is that when the js does
that, it redraws the select boxes shape as well as the content (4.7X only
changes the options and keeps whatever size the select box had when the first
was first loaded).
Forgetting this type of session information is bad because:
For most select boxes (the one that were not redrawn by js) the selection is
remembered, so the user is unsuspecting that for some the selection is
forgotten, and the result of the second submit is likely to be wrong. The
selection forgotten could very well have been "Do not charge me $1000"
Comment 1•24 years ago
|
||
cc'ing pollmann. This may need work in the backend restoration code, which
should probably take care of such dynamic things.
Comment 2•24 years ago
|
||
Rod has a bug that this is a duplicate of, handing to him...
If I remember correctly, Rod came up with a patch, but nearly any approach for
fixing this problem has potentially dangerous side effects.
Assignee: radha → rods
Assignee | ||
Comment 3•24 years ago
|
||
If options are dynamically added or removed we don't remember the it
This is a dup
Summary: history fails to remember selected option. → [DUP]history fails to remember selected option.
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Comment 4•24 years ago
|
||
Is this futured just b/c you think it's a dupe? Or are we really not going to
fix this bug. I can't find the dupe...
Comment 5•24 years ago
|
||
Dupe of bug 83033, which was a bug in bugzilla. That bug has since been fixed,
but mozilla is still broken - see bug 125421
Comment 6•23 years ago
|
||
This bug is stale and should be resolved as fixed/dupe, afaics ??
Keywords: qawanted
It seems like Bug 95622 might be the best one to dupe this bug against. If that
issue is fixed, then the query page as it currently exists will work fine. If
not, there's also also Bug 153074.
Comment 8•21 years ago
|
||
*** This bug has been marked as a duplicate of 95622 ***
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
You need to log in
before you can comment on or make changes to this bug.
Description
•