213
edits
Changes
→Caveats, Restrictions, Outstanding Questions
=Caveats, Restrictions, Outstanding Questions=
* Wholesale override of 404 pages would be unpopular, and there is no reliable way to tell the difference between a 404 error page provided by a default install of the web server and a custom 404 error page. The other major browsers seem to look at file size and if it’s below a certain threshold, assume that it’s it's a default page and overridable. Additionally a Firefox override might be useful even for custom error pages in some circumstances.
* The old error page, by design, runs without chrome privileges, and the new page must also be chromeless. This is to prevent an XSS attach from escalating into a privilege escalation attack.
* There are privacy issues around using Google Link Doctor that will need to be addressed if we are to use it automatically.
* The current 404 error page interception/redirection code just does a document.location.replace on EndDocumentLoad to redirect to the Firefox 404 error page. This has some limitations, and it may be necessary support this functionality at deeper level in the docshell. This should be possible in the Firefox.next timeframe.
* One click access to the original server-supplied 404 error page might be desirable.
=UI Designs=
