Closed Bug 128989 Opened 23 years ago Closed 23 years ago

XBL form controls need to save/restore state

Categories

(Core :: XBL, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla1.0

People

(Reporter: dean_tessman, Assigned: hyatt)

References

Details

(Whiteboard: [nav1])

1. Open http://bugzilla.mozilla.org/query.cgi 2. My default query loads with a few items selected in the Status list 3. select a different item in the Status list 4. Click the Severity link 5. After the page loads, click the Back button Expected Results: query page displays with the Status selected in step 3 Actual Results: query page displays with the initial items selected from step 2 Reproducible: always Build: 2002030308 on Win2K
-> hyatt
Assignee: bryner → hyatt
Keywords: nsbeta1
Summary: XBL <select>s don't remember selected items after history.back() → XBL form controls need to save/restore state
Target Milestone: --- → mozilla1.0
This isn't just about HTML form controls done in XBL. This is about any form control done in XBL. We need a well defined way for XBL bindings to say they wish to take part in the session history. We need this to let authors style arbitrary elements as form elements and have them work. (Similarly, we need such a system to let them take part in form submission.)
See bug 108309, which has a start at being implemented. I took the wussy way out and just added it to nsIFormControl, which will keep it somewhat efficient and fix both XBL form controls and regular form controls with display: none.
Depends on: 130015, 130016
*** Bug 130017 has been marked as a duplicate of this bug. ***
nsbeta1+ per Nav triage team, nav`
Keywords: nsbeta1nsbeta1+
Whiteboard: [nav1]
Blocks: 133791
Blocks: 108309
No longer blocks: 133791
oops
Blocks: 133791
No longer blocks: 108309
Depends on: 108309
All XBL form controls should be saving and restoring state correctly now.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Cannot reproduce the original bug report using 2002040103 on Win2K. Verified Fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.