Send port-closed notification when a frame with ports unloads....

Send port-closed notification when a frame with ports unloads.

Also add onLoad and onUnload chrome Event to our bindings, so we can add
listeners to these events without needing a DOM.  These don't hook into the
window "unload" event, so we no longer prevent Chrome's sudden termination of
tabs on shutdown.

BUG=12686
TEST=no

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

[Aaron Boodman, 2009-06-18 04:49:45]

http://codereview.chromium.org/125280/diff/3015/3020
File chrome/renderer/renderer_resources.grd (right):

http://codereview.chromium.org/125280/diff/3015/3020#newcode3
Line 3: without changes to the corresponding grd file. 4 -->
4?

http://codereview.chromium.org/125280/diff/3015/3028
File chrome/renderer/resources/event_bindings.js (right):

http://codereview.chromium.org/125280/diff/3015/3028#newcode142
Line 142: chrome.onLoad = new chrome.Event();
I'd rather not add these new public apis that do the same thing (from a
developer's pov) as the regular dom load and unload apis. This is an internal
implementation detail of our system.

[Matt Perry, 2009-06-18 19:48:58]

I added a small change to fix the unit tests as well.

http://codereview.chromium.org/125280/diff/3015/3028
File chrome/renderer/resources/event_bindings.js (right):

http://codereview.chromium.org/125280/diff/3015/3028#newcode142
Line 142: chrome.onLoad = new chrome.Event();
On 2009/06/18 04:49:45, Aaron Boodman wrote:
> I'd rather not add these new public apis that do the same thing (from a
> developer's pov) as the regular dom load and unload apis. This is an internal
> implementation detail of our system.

OK, I changed to onLoad_ and onUnload_ for now, and will make them hidden from
content completely in my next CL.

[Aaron Boodman, 2009-06-18 21:27:32]

LGTM