Jason Duell Reporter
	Description • 14 years ago

We'd like to be able to determine if channels are to be downloaded in chrome, without needed to involve content.   But right now URILoader lives in content, and we're hacking around it (bug 562444).   

We should figure out how to move URILoader and/or the logic it uses for this into chrome.  Since content processes may load/unload add-ons or extensions that handle specific content-types, this may involve a subscription model where content processes can update the chrome process when they add/remove the ability to handle a certain type of file.

It would be nice to fix this by the time we use e10s/necko for Firefox.