Open Bug 493435 Opened 15 years ago Updated 2 years ago

"Try Again" on offline error page should not show POSTDATA resubmission warning

Categories

(Core :: Networking, defect, P5)

defect

Tracking

()

People

(Reporter: jruderman, Unassigned)

Details

(Whiteboard: [necko-would-take])

Steps to reproduce: 1. Turn off wifi 2. Submit a POST form, such as the commit button on a show_bug page 3. Turn on wifi 4. Click "Try Again" on the error page resulting from step 2 Result: POSTDATA dialog warning me that I'm resubmitting a form and may be repeating a transaction. Expected: Not that.
I split this bug report from bug 160144 comment 74, where it was reported by Tony Mechelynck.
I think it may be hard to reliably detect whether the cause of the error page also prevented the initial submission.
In some cases, yes. But when Firefox says it is "currently offline and can't browse the web", that's not one of those cases ;)
OS: Mac OS X → All
Hardware: x86 → All
You could have gone offline right after the submission was submitted. With automatic link state detection, this isn't as far fetched as it may sound.
As of bug 435325, Firefox will now go back online when you click Try Again. So the postdata warning looks reasonable in that case.
Re Comment 5: The bug is about showing the dialog when the original submission failed because firefox was already offline. It does seem silly to show the warning when it's known that the POST request was never sent. Re Comment 4: Does automatic link state detection affect requests already in progress? I would think that if I hit submit before the state changes, it would go ahead and send as usual, which would result in a different error message than "can't do that while offline." If link state detection does kill requests in progress, shouldn't that generate another different error message? Something like "Uh-oh, your internet connection went out while submitting your form, there's no way to know if it went through or not, but no reply was received." It would be even better if "offline mode" messages included a link/button to the settings where the user can disable detection.
Whiteboard: [necko-would-take]
Priority: -- → P5
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.