170216 - Pretty up dns error page a bit

Status: VERIFIED DUPLICATE of bug 280190

(Firefox :: General, defect)

Description

[Blake Ross]

Comment 1

[Blake Ross]

I guess this can wait.

Comment 2

[Brian Crescimanno]

It probably can, but I'd certainly like to chip in.  I'm afraid I don't know
anything about the file format that's used, and I can't find it by rooting
around my phoenix directory.  Could someone post the actual .xhtml file that's
used right now and I'll do some hacking on it and come up with a couple of
solutions, or just point me at what to edit in my tree).  I'm sure I can whip up
some ideas in just a couple of days...that would at least keep you guys busy
with more important issues. :)

Comment 3

[David McCormack]

Only have the win32 binary version here, but;

toolkit.jar
   content/global/netError.js
   content/global/netError.xhtml

en-US.jar
   locale/en-US/global/netError.dtd

Comment 4

[Blake Ross]

Sure, a good looking error page would be great.  Help appreciated.

Comment 5

[Asa Dotzler [:asa]]

Brian, (in case you didn't know) jar files are just zip files so you can unzip
them to get at their contents. 

Comment 6

[Brian Crescimanno]

ahh..that suddenly makes my life easier.

Sorry, somehow I got off of the CC list on this and didn't receive any of the info.

Comment 7

[Stefan Huszics]

Would something looking like this be interesting?

http://hem.bredband.net/b103277/errorpage/index.html

It uses the systemcolors of the OS for all colors. Don't know it that is the
desired approach or if a more fixed color look is desired.

If it's in any way interesting I'll incorporate it into the netError.xhtml file.

Comment 8

[Collin Grady]

Had a thought, many people complain that they mistype a URL and have no way to
just fix the mistake and retry the page.

Maybe instead of just printing the url, make it a textbox that on submit goes to
the url in the box?

That way, its quite simple to fix a type and hit enter, instead of having to
copy the url from the try again box, edit the typo, and THEN go on to the right
page.

Comment 9

[Stefan Huszics]

> Maybe instead of just printing the url, make it a textbox that on submit goes to
the url in the box?

Yes, we have suggestions like that too over on Mozillazine forums :)
But there is also this bug that hopefully will make it not required.
http://bugzilla.mozilla.org/show_bug.cgi?id=157004

BTW this from my above post is no longer true
> It uses the systemcolors of the OS for all colors. 

It simply got too ugly when you had to design for all possible color combinations :)

Comment 10

[Michael Newton]

Is anyone still working on this?  I was thinking there are a number of internal
pages (about:plugins, about:cache, FTP listings) that have different "looks" to
them.  Actually, most have no look at all.  Maybe we should give all these pages
a common stylesheet?  The about:plugins page looks very neat and clean, maybe
use chrome://communicator/skin/plugins.css as a model.  Just a thought.

Comment 11

[Alessandro Minelli]

Proposing blocking 1.0, I think this should be a easy to fix issue, but very
useful for end users, and really better than IE error page.

Comment 12

[Ben Goodger (use ben at mozilla dot org for email)]

Nice to have, not going to block. -ing, leaving targeted at 1.0. Would take a
tested fix for this if someone posts a patch.

Comment 13

[Ben Basson]

Doing this wouldn't be that taxing, but it's not really worth fixing this bug
until the following bugs are also fixed, since they make the error pages pretty
disfunctional or (in some cases) useless:

Bug 157004 - Use original URL in history and URL bar when an error page is generated
Bug 159071 - If error pages are enabled, bookmark search will return the error
page as a result
Bug 161276 - Search in error pages should use user specified search engine
Bug 188795 - missing error page descriptions
Bug 237244 - "Try Again" on XUL error pages does not repost form data

Nonetheless, I'll see if I can dig up some threads on the MozillaZine forum and
see what people can come up with.

Comment 14

[Lech Deregowski [:lech]]

(In reply to comment #13)
> Doing this wouldn't be that taxing, but it's not really worth fixing this bug
> until the following bugs are also fixed, since they make the error pages pretty
> disfunctional or (in some cases) useless:

Perhaps a suggestion of leaving the wording of the error hardcoded and out of
reach but still brief and to the point. But allowing the stylesheets for errors
to be modified on a limited per-theme level (text color/display, some basic
images[if any]) along with maybe some type of universal header in the way
component extensions warnings are displayed with links to further help/how-to's
in that header (if users are truely lost and need help).

Comment 15

[Robert Accettura [:raccettura]]

While were on the topic, making these a pref could be very useful to corporate
installs.  If the pref is set to a URL, the browser would load the URL, which
may contain the error message.

Similar to using a .htaccess for custom error pages... just client side.

Comment 16

[Jesse Ruderman]

*** This bug has been marked as a duplicate of 280190 ***

Comment 17

[Henrik Skupin [:whimboo][⌚️UTC+1]]

v