552140 - Implement Heads Up Display event handlers/observers

Status: VERIFIED FIXED

(DevTools :: General, defect, P1)

Description

[David Dahl :ddahl]

Event handlers and observers for window object creation, new tabs, new windows, tracking all of these objects and destruction/cleanup when things go away.

First item: Browser window creation/ replacement observer/event handling

Comment 1

[David Dahl :ddahl]

Currently have hudwindowobserver.js component to observe window creation and an HTTP event observer built into hudservice.js (HUDService)

Working on hudconsoleobserver.js component to surface global content script errors and messages.

Comment 2

[David Dahl :ddahl]

here are the current implementations:
http://hg.mozilla.org/users/ddahl_mozilla.com/heads-up-display/file/42b38ea8143e/toolkit/components/console/hudservice/hudwindowobserver.js

http observer:
http://hg.mozilla.org/users/ddahl_mozilla.com/heads-up-display/file/42b38ea8143e/toolkit/components/console/hudservice/hudservice.js#l527

the consoleobserver will be checked in tonight.

Comment 3

[David Dahl :ddahl]

It seems I need to create another observer for handling images and media that are loaded by a contentDocument. This data is loaded via an imageRequest, and perhaps other types of requests. 

It appears that each image or media channel will have a different loadGroup from the originating html document that is loaded. (sometimes the loadGroup is null)

I have been using loadgroups to tie in all network requests so far, and this is not a comprehensive solution.

 I'm not going to block on this for beta, but it would be nice to figure out how to tie all of the requests together from the originating http request.

Comment 4

[Boris Zbarsky [:bzbarsky]]

> It appears that each image or media channel will have a different loadGroup
> from the originating html document that is loaded. (sometimes the loadGroup
> is null)

For images, the necko channel will be in a synthetic loadgroup.  The imgRequestProxy request will be in the document loadgroup.

Image loads are shared across documents, so you can't really tie them to a specific document.

I can't speak to what the media loads look like.

Comment 5

[David Dahl :ddahl]

Need to figure out what additional observers and event listeners to set.

Comment 6

[Kevin Dangoor]

We have implemented all of the event handlers we plan to for Firefox 4.