Clean up some style and organization in the browser about handler. No code...

Clean up the browser about URL handler to not derive from WebContents. It is
instead integrated in the BrowserURLHandler for special schemes. This solves
a number of problems and cleans things up nicely.

Most of the functions were not necessary to have in the header file of the
browser about handler, so I made them local to the .cc file. I moved everything
around, but there was no change to any of the About...() functions.

This improves the about:memory page to not include the memory of the new tab
page it replaced. The entry for itself also has the proper title. This works
by using a meta refresh to the actual page, the the process transition no longer
happens at the same time as the about:memory page computation.

This also fixes problems with the about:network and about:ipc dialogs opening
blank pages and also re-opening the dialog when you close the browser.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=10941

[Mike Belshe, 2009-03-03 16:55:50]

looks good, with comments below

http://codereview.chromium.org/27238/diff/2018/3017
File chrome/browser/browser_about_handler.cc (right):

http://codereview.chromium.org/27238/diff/2018/3017#newcode601
Line 601: if (AboutHandler::WillHandle(*url))
I wonder if this should be renamed "RendererAboutHandler"?

http://codereview.chromium.org/27238/diff/2018/3027
File chrome/browser/memory_details.cc (right):

http://codereview.chromium.org/27238/diff/2018/3027#newcode233
Line 233: contents->controller()->GetPendingEntry();
whoops - this is broken (set to null rather than GetPendingEntry()).

But - given the redirect, should we get rid of the PendingEntry checking and
associated comment above?