Closed Bug 970603 Opened 6 years ago Closed 6 years ago

Analyze error recovery on about:neterror with "try again" button

Categories

(Firefox :: General, defect)

x86
macOS
defect
Not set

Tracking

()

RESOLVED FIXED
Firefox 30

People

(Reporter: vtsatskin, Assigned: vtsatskin)

References

Details

(Whiteboard: [qa-])

Look at all the possible error situations in about:neterror and see how the "try again" button aids the users in solving the problem at hand. 

Questions to answer:
- Does the try again button exist on the page?
- What will pressing "try again" do in terms of solving the problem?
- Does having this behavior make sense? (I.e. does the user actually recover from the problem?)
- Is there a better way of handling the error? (E.g. automatically fixing the problem; extra behavior that will diagnose or fix the problem)
The analysis on the problem can be found at in this spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0Ajlm_wkte9-mdGtTVURJbVdhS2tNYVVPU2p1UFJ5c0E&usp=sharing
It is clear that for almost all cases "try again" won't do anything to actually solve the problem. If we are looking at this from the situation of a user only pressing the try again button and not doing anything else to resolve the problem (e.g. fixing the server, checking internet connection), we can break down the errors into the following categories:

Errors which when pressing try again will not solve the problem:

- File Not Found
- Malformed URI
- Unknown Protocol Found
- Redirect Loop
- Denied Port Access
- Unsafe Content Type

Errors which when pressing try again almost always not solve the problem:

- proxyResolveFailure
- proxyConnectFailure
- nssFailure2
- DNS Not Found

Errors which when pressing try again may solve the problem:

- Generic
- Corrupted Content Error
- Connection Failure
- Net Timeout
- Network Reset
- Net Offline
- Net Interrupt
- Unknown Socket Type
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 30
Keywords: verifyme
Avaida on IRC reached out to me for clarification of this issue. This issue's scope is just the analysis of the effect "try again" will have on each type of error.

The actual work based on these recommendations has been delegated to blockers to bug 982347. These bugs start with the text "change behaviour...". If a full bug list is needed for clarification, please feel free to ask.
(In reply to Valentin Tsatskin [:vt] from comment #3)
> Avaida on IRC reached out to me for clarification of this issue. This
> issue's scope is just the analysis of the effect "try again" will have on
> each type of error.
> 
> The actual work based on these recommendations has been delegated to
> blockers to bug 982347. These bugs start with the text "change
> behaviour...". If a full bug list is needed for clarification, please feel
> free to ask.
Thank you for clarifying this, Valentin. I'll mark this fix as [qa-] based on Comment 3, testing efforts will be redirected towards the blockers from Bug 982347.
Keywords: verifyme
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.