Displays latest INIT_PROXY_RESOLVER log on the #proxy tab

Displays the most recent INIT_PROXY_RESOLVER source's log entries
on the #proxy net-internals tab.

Also adds a link to the #proxy tab to show all INIT_PROXY_RESOLVER
events on the #events tab.

BUG=56430
TEST=manual


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

[mmenke, 2010-10-22 15:44:52]

Somewhat redundant, but think both can be helpful.
Having the results and the log on the same page helps
diagnose why the current settings aren't working, and if
re-apply settings fixes things, the link makes it easy to
compare the log entries for the failed and successful
attempts.

[eroman, 2010-10-22 21:21:44]

lgtm

http://codereview.chromium.org/3990005/diff/4001/5001
File chrome/browser/resources/net_internals/index.html (right):

http://codereview.chromium.org/3990005/diff/4001/5001#newcode86
chrome/browser/resources/net_internals/index.html:86: <h4>Proxy resolver
events</h4>
Suggestions:

(1) I suggest moving this above the bad proxies table (so it is right beneath
the settings). Because this will usually be more useful.

(2) Rather than calling this "Proxy resolver events", how about "Proxy resolver
initialization" or "Proxy Auto-Config initialization".

http://codereview.chromium.org/3990005/diff/4001/5003
File chrome/browser/resources/net_internals/proxyview.js (right):

http://codereview.chromium.org/3990005/diff/4001/5003#newcode97
chrome/browser/resources/net_internals/proxyview.js:97:
ProxyView.prototype.onAllLogEntriesDeleted = function() {};
I think here we should clear the resolver log.

[mmenke, 2010-10-25 14:50:44]

http://codereview.chromium.org/3990005/diff/4001/5001
File chrome/browser/resources/net_internals/index.html (right):

http://codereview.chromium.org/3990005/diff/4001/5001#newcode86
chrome/browser/resources/net_internals/index.html:86: <h4>Proxy resolver
events</h4>
On 2010/10/22 21:21:44, eroman wrote:
> Suggestions:
> 
> (1) I suggest moving this above the bad proxies table (so it is right beneath
> the settings). Because this will usually be more useful.
> 
> (2) Rather than calling this "Proxy resolver events", how about "Proxy
resolver
> initialization" or "Proxy Auto-Config initialization".

(1) Had it there initially, wasn't sure where it would fit best.  Moved back up.

(2) Much better.  Done.

http://codereview.chromium.org/3990005/diff/4001/5003
File chrome/browser/resources/net_internals/proxyview.js (right):

http://codereview.chromium.org/3990005/diff/4001/5003#newcode97
chrome/browser/resources/net_internals/proxyview.js:97:
ProxyView.prototype.onAllLogEntriesDeleted = function() {};
On 2010/10/22 21:21:44, eroman wrote:
> I think here we should clear the resolver log.

Wasn't sure if there was any reason to bother.  Done.

[eroman, 2010-10-25 19:51:56]

lgtm