information from the windows registry. This is later used by the helper app dialog. Correctly implement different
behaviors for mime info action types of useSystemDefault vs. useHelperApp
r=alecf
code review will come when this is done and gets turned on.
Landing of the RDF data source which keeps track of all the user specified mime type information.
Landing implementation of user over ride information when determining what helper app to run. now we'll
check the information stored in the data source first. If we don't ahve any over-ride information, then
fall back to the OS defaults.
code review will come when this is done and gets turned on.
Add the ability to launch urls using a OS specified protocol handler for windows. Implement nsIExternalProtocolService.
code review will come when this is done and gets turned on.
Use the 4.x windows registry information in an effort to figure out the correct file extension
for a particular content type. This is necessary because we need the file extension to figure out
which helper app to use, not the content type.
Pass the file extension to be associated with this content type to the external content handler when
we create it.
code review will come when this is done and gets turned on.
Add external application implementation.
Add windows registry sniffying code to find the right external helper application for a given file extension.
Add windows registry code for launching the application.
