Firefox/Projects/Network Error Pages: Difference between revisions
No edit summary |
|||
| Line 82: | Line 82: | ||
[[Image:Picture_13.png|Firefox error page after a dnsNotFound error.]] | [[Image:Picture_13.png|Firefox error page after a dnsNotFound error.]] | ||
= Notes = | |||
Can we use Places autocomplete for link correction? A mis-typed link will often be in error in only the last couple of characters -- we can truncate the last 2 or 3 characters and rely on Places auto-complete to give us recommendations... | |||
http://mxr.mozilla.org/mozilla-central/source/toolkit/components/places/tests/autocomplete/ | |||
A related alternative would be to construct an edit-distance function and register it with SqlLite. We can then do a query on minimal edit distance (async of course) to get the best link correction matches. | |||
Problem is, how do we hook link correction into the error page? We'd like to provide suggestions inside the web page similar to Google's "did you mean" on the search results page. | |||
= connectionFailure error = | = connectionFailure error = | ||
Revision as of 01:26, 27 February 2009
Overview
Sprint lead: curtis
Sprinters: johnath, boriss
- Description
- More useful/helpful set of network error pages that offer tools helping users get to a useful end point via search, analysis of Places DB, or automatic redirects/reloads.
Status
- Simple prototype which adds a search box to the default page. Still need to figure out if we can improve the utility by how we construct the search, and whether adding the search box makes sense in general, or if it only really makes sense for certain error types.
Steps
- Identify the 3 most important pages to improve.
- Pick one of the three pages.
- Improve it.
- Rinse and repeat.
Goals / Use Cases
tbd
Non Goals
tbd
Design
tbd
Bugs
Bug 479922 - Network error pages should give me tools instead of asking me questions
Reference
nsDocShell::DisplayLoadError -- dispatches various error pages
about:neterror
about:config -- urlclassifier.alternate_error_page default string = "blocked" -- for example -- tells nsDocShell::DisplayLoadError to use the "blocked" page instead of the default generic page.
https://johnath.com/ -- triggers a "Secure Connection Failed" error page.
http://example.example.com/ -- triggers an "Address Not Found" error page.
Error Types
Which ones do we want to improve first?
- Some "tools" may broadly apply -- change the generic template? (e.g. search)
- No new pages, just make the existing pages better?
- Add a search field to addressNotFound page.
- neterror important???
- protocolNotFound
- fileNotFound
- dnsNotFound important???
- connectionFailure important???
- netInterrupt
- netTimeout important???
- nssBadCert
- nssFailure2
- phishingBlocked
- malwareBlocked
- malformedURI
- redirectLoop
- unknownSocketType
- netReset
- netOffline
- isprinting
- deniedPortAccess
- proxyResolveFailure
- proxyConnectFailure
- contentEncodingError
- unsafeContentType
dnsNotFound error
URL that results in a dnsNotFound error page
Notes
Can we use Places autocomplete for link correction? A mis-typed link will often be in error in only the last couple of characters -- we can truncate the last 2 or 3 characters and rely on Places auto-complete to give us recommendations...
http://mxr.mozilla.org/mozilla-central/source/toolkit/components/places/tests/autocomplete/
A related alternative would be to construct an edit-distance function and register it with SqlLite. We can then do a query on minimal edit distance (async of course) to get the best link correction matches.
Problem is, how do we hook link correction into the error page? We'd like to provide suggestions inside the web page similar to Google's "did you mean" on the search results page.
connectionFailure error
URL that results in a connectionFailure error page
[image:xxxxxxxxxxx Screenshot of a connectionFailure error page]