Firefox/Projects/Network Error Pages: Difference between revisions

Jump to navigation Jump to search
→‎Design Decisions: late night change of heart.. recommending code not be on main error page
(+sections)
(→‎Design Decisions: late night change of heart.. recommending code not be on main error page)
Line 94: Line 94:
**This follows previous conventions; on all major operating systems, error warnings provide a link to more information.
**This follows previous conventions; on all major operating systems, error warnings provide a link to more information.


* The error code (404, DNS Not Found, etc) should be displayed, but not as the main text.
* The error code (404, DNS Not Found, etc) does not need to be displayed on the main error page.
**The goal in the main text should be to explain as clearly and simply as possible to the user what is wrong.  While both error codes and text would explain the problem to experienced users, error codes do not explain the problem to beginning users.  Thus, both benefit from non-coded text.
**The goal in the main text should be to explain as clearly and simply as possible to the user what is wrong.  While both error codes and text would explain the problem to experienced users, error codes do not explain the problem to beginning users.   
**The main reason for including error codes is diagnosis.  For instance, if an experienced user needs to know which particular error he is looking at, or if a beginning user is trying to get help from an experienced user, these codes would be important.  So, including them in a visible but not prominent way can address this use case. This is similar to how Chrome and IE handle codes in network error warnings.
**The main reason for including error codes is diagnosis.  For instance, if an experienced user needs to know which particular error he is looking at, or if a beginning user is trying to get help from an experienced user, these codes would be important.  However, considering adding the code to the main page provides little benefit in most cases and the same benefit can be had putting the error code on a separate page, including it with the extra information and recommendations could be a better way to preserve this information.
 
* The network error pages should display the most useful* tools possible for the given input, but no more than five tools.
* The network error pages should display the most useful* tools possible for the given input, but no more than five tools.
**<nowiki>*</nowiki>Most useful will be determined an inexact science of approximation of a "best match," given the tools we have available.  For instance, if a page is only one letter off from the user's input, it would have a higher "usefulness" score than simply linking a failed subdirectory to the domain-level page
**<nowiki>*</nowiki>Most useful will be determined an inexact science of approximation of a "best match," given the tools we have available.  For instance, if a page is only one letter off from the user's input, it would have a higher "usefulness" score than simply linking a failed subdirectory to the domain-level page
Confirmed users
954

edits

Navigation menu