Closed
Bug 257865
Opened 20 years ago
Closed 1 year ago
Opening second window resubmits form without warning
Categories
(Toolkit :: Places, defect, P5)
Toolkit
Places
Tracking
()
RESOLVED
INVALID
People
(Reporter: arromdee2, Unassigned)
References
()
Details
User-Agent: Mozilla 5.0 (Compatible; MSIE 6.0; Windows NT 5.0) Netscape 7/7.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040817 When you open a new window, and the current page is the result of a form submission, the form is submitted again. The fields are blank and there is no warning like there is when reloading a page. Reproducible: Always Steps to Reproduce: 1. Set your options to display on a new window the last page visited. 2. Go to the above URL. 3. Type some text in and submit the form. Notice the result. 4. Open a new window. Actual Results: When the new window was opened, a second form was submitted. This second form was submitted with blank data and no warning was given that the form would be submitted a second time. Expected Results: Exactly what it should have done is up to Mozilla designers, but it probably should have either not showed the page, showed the page without submitting anything, or given a warning and showed nothing if the user chose not to submit anything. It definitely shouldn't have submitted the form with blank data. I've split this off from #245963.
Comment 1•20 years ago
|
||
Global history has no concept of POST pages, so it does a GET load of the URI. This probably needs a separate firefox bug too, due to the forked history impl. It's not clear what the right choice here is -- keeping POST pages out of the "last visited" slot can lead to weird results, and storing enough state in the history to force a load from cache is nontrivial. I find myself wondering yet again why we have this option at all...
Assignee: general → nobody
Status: UNCONFIRMED → NEW
Component: Browser-General → History: Global
Ever confirmed: true
OS: Linux → All
QA Contact: general → core.history.global
Hardware: PC → All
Reporter | ||
Updated•20 years ago
|
Severity: normal → critical
Updated•7 years ago
|
Component: History: Global → Places
Product: Core → Toolkit
Updated•7 years ago
|
Priority: -- → P5
Comment 2•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: critical → --
Comment 3•1 year ago
|
||
I don't think we have the option anymore, or better browser.startup.page = 2 is deprecated and not used anymore in the codebase.
Thus I don't think this can still happen. Maybe in Session Restore, I see bug 423800 that is somewhat related, even if not the same.
Anyway, this is not an History concern and comment 0 cannot happen today.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•