DefaultApplicationsFirefox
|
Size: 1696
Comment: this needs patch and source review, not discussions
|
Size: 2467
Comment: formatting
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ##(see the SpecSpec for an explanation) | == Status == |
| Line 3: | Line 3: |
| * '''Launchpad Entry''': https://launchpad.net/distros/ubuntu/+spec/default-applications-firefox * '''Created''': [[Date(2005-10-29T23:48:37Z)]] by MrPantless * '''Contributors''': MrPantless * '''Packages affected''': |
* See https://launchpad.net/distros/ubuntu/+spec/default-applications-firefox |
| Line 10: | Line 7: |
| http://bugzilla.ubuntu.com/show_bug.cgi?id=7023 | http://bugzilla.ubuntu.com/show_bug.cgi?id=7023 [[BR]] http://bugzilla.ubuntu.com/show_bug.cgi?id=18661 [[BR]] http://bugzilla.ubuntu.com/show_bug.cgi?id=8911. |
| Line 13: | Line 12: |
When it needs to ask about, or the user wants to specify, the application to use, this should not be done by offering a filesystem hierarchy browser. |
|
| Line 18: | Line 19: |
| See also: http://bugzilla.ubuntu.com/show_bug.cgi?id=18661 and some bug I can't find right now about mad mime type handling. |
== Design == |
| Line 22: | Line 21: |
| == Use cases == | The behaviour should be as follows: |
| Line 24: | Line 23: |
| == Scope == | * If the file's mime-type can be handled by firefox internally then firefox should do so. * If it cannot, then firefox should do with the file what Nautilus would do with it except that if that involves executing the file it should want to save it to disk. * There should be a way to tell firefox `open with ...' which should provide the options (1) firefox's internal display engine treating the file as html (2) firefox's internal display engine treating the file as text/plain (3) save to disk (4) same as Nautilus open with. |
| Line 26: | Line 27: |
| == Design == | Getting this correct may not be feasible given the current parlous state of the mime handling system in at least firefox 1.0.7. But we will try to get as close as possible. |
| Line 32: | Line 33: |
| '''Comments:''' | If completely correct behaviour cannot be achieved with only a reasonably sized patch(set) relative to upstream or Debian, then we will try to do the best we can without excessive divergence. === Comments and suggestions === |
| Line 37: | Line 40: |
=== Code === === Data preservation and migration === == Outstanding issues == == BoF agenda and discussion == |
Status
Summary
http://bugzilla.ubuntu.com/show_bug.cgi?id=7023 BR http://bugzilla.ubuntu.com/show_bug.cgi?id=18661 BR http://bugzilla.ubuntu.com/show_bug.cgi?id=8911.
Firefox should use the same default applications for opening unknown file types as GNOME, ideally through proper integration with GNOME, or at a minimum ship its own matching default settings.
When it needs to ask about, or the user wants to specify, the application to use, this should not be done by offering a filesystem hierarchy browser.
Rationale
Firefox's current mechanisms for determining which program to run are (a) inconsistent and (b) broken.
Design
The behaviour should be as follows:
- If the file's mime-type can be handled by firefox internally then firefox should do so.
- If it cannot, then firefox should do with the file what Nautilus would do with it except that if that involves executing the file it should want to save it to disk.
- There should be a way to tell firefox `open with ...' which should provide the options (1) firefox's internal display engine treating the file as html (2) firefox's internal display engine treating the file as text/plain (3) save to disk (4) same as Nautilus open with.
Getting this correct may not be feasible given the current parlous state of the mime handling system in at least firefox 1.0.7. But we will try to get as close as possible.
Implementation
This is more a case of looking at the right patches and the source than a BOF. If anyone has more useful information like that below then please provide it.
If completely correct behaviour cannot be achieved with only a reasonably sized patch(set) relative to upstream or Debian, then we will try to do the best we can without excessive divergence.
Comments and suggestions
JeffWaugh: Red Hat have patches, which may be upstream in the 1.5 branch, to integrate with the xdg-mime standard (instead of mailcap). On top of that, we may want to do some mailcap/xdg-mime synchronisation, so that other apps (such as mutt) can take advantage of the xdg-mime information.
MarkShuttleworth: We don't want to see the "do you want to do this by default?" box - just DOIT! If the Red Hat patches don't land, we want to hard code this. (JeffWaugh: ... or fix mailcap, by hardcoding or synchronising.)
DefaultApplicationsFirefox (last edited 2008-08-06 16:32:37 by localhost)