477946 - wish: Ability to specify external commands for displaying open/save dialogs

Status: NEW

(Firefox :: General, enhancement)

Description

[Stephan Sokolow]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.6) Gecko/2009020905 Gentoo Firefox/3.0.6 Ubiquity/0.1.5
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.6) Gecko/2009020905 Gentoo Firefox/3.0.6 Ubiquity/0.1.5

While I understand that KDE dialogs in Firefox aren't going to become a supported feature, I'm getting a bit tired of having to kill and restart Firefox every time KGtk's jerry-rigged dialogs stop responding. (LD_PRELOAD patching)

Is there any chance Firefox could gain a pair of preferences which, if set, let you specify commands like `kdialog --getopenfilename $STARTDIR $FILTER` and `kdialog --getsavefilename $STARTDIR` to override the default file picker?

Both example commands return the filename via their stdout or a nonzero exit code to indicate cancellation and they can always be wrapped by shell scripts to convert argument formats if need be. ($FILTER is a space-separated list of mimetypes)

That'd be hacky enough to justify never having to support KDE dialogs, but it'd still assuage people like me who just want their systems to be comfortable and it'd provide a low-effort way for integrators to support KDE dialogs.

There is partial precedent in the print.print_command preference.

Reproducible: Always

Comment 1

[Robert Strong (they/them - no direct email)]

Not a shell integration bug... over to general for triage

Comment 2

[Tyler Downer [He/Him]]

This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.

Comment 3

[Stephan Sokolow]

Given that this is a feature request rather than a bug report, testing on a new profile wasn't necessary, but I did it anyway. No new config property has appeared to resolve this in the time since it was reported.