[GitHub issue by tonychung on 2012-09-26T05:35:57Z, https://github.com/mozilla-b2g/gaia/issues/5199] While i enjoy the netlingo with smileys and emoticons, we need to be putting out a more helpful 404 page to the world that explains what's happening. @jcarpenter, ux thoughts? Screenshot: http://i.imgur.com/lmpra.png ## Environment : * Otoro daily: 9-25-2012 * gaia commit: 71e89d4338d59a86e8599abeda24dbfaf1c80e1a * gecko commit: 1c333645ec70bfce2176876e4bfaf24bfd4bbde5 ## Repro : 1. launch Browser App 2. Load a page that will throw a 404 3. Verify the error page fires a sadFace image with buttons. But there's no real helpful text to the user on what happened. ## Expected : * Have a more professional page that describes what err'd out to the user on this page. :( face doesn't explain anything. ## Actual : * sadFace page
[GitHub comment by stasm on 2012-09-26T08:23:44Z] Weren't we supposed to show the default error message that Gecko displays?
[GitHub comment by daleharvey on 2012-09-26T08:42:51Z] We are supposed to be showing error messages from gecko for non fatal errors, I think your page actually crashed while it was loading What is the specific url? and can you test another url that you expect to 404 (probably from a different domain) Styling for the crashed page is files under #4045
[GitHub comment by tonychung on 2012-09-26T16:26:58Z] ah okay, i'll try to reproduce. i was trying to visit planet.mozilla.org at the time when i got this message.
[GitHub comment by jcarpenter on 2012-09-26T18:22:42Z] What @daleharvey said. Also related: #5067 (Style default Gecko error messages)
What is this bug actually about? We show network errors from Gecko and the crash screen for fatal errors as per spec. Please re-open if there's any work left to do on this.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.