Closed
Bug 99244
Opened 23 years ago
Closed 23 years ago
File extension ignored on local files
Categories
(Core Graveyard :: File Handling, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 109236
People
(Reporter: stanisa, Assigned: law)
References
Details
When a new helper application is added, and a certain file extension is assigned to be dealt with by an external application, if this local file happens to be a text file, the browser prints it in it's window, without invoking the external application to deal with it. This is only the case with local files and not when mime type is determined by the web server with which the browser may be communicating.
Reporter | ||
Comment 2•23 years ago
|
||
These values were filled in: Description Of Type: RealMedia File Extension: rmm,ram MIME Type: application/x-pn-realaudio Application To Use: /usr/lib/RealPlayer8/realplay Then when a *.ram file is open from a local hard drive, it's content is printed in the browser window.
Comment 3•23 years ago
|
||
Not BE:Preferences. I think it's XPApps. Also adding to chofmann's helper app tracker.
Comment 5•23 years ago
|
||
it seems like we don't use RDF mime database for extension -> type mapping, and I think we already have a bug on this....
Whiteboard: DUPEME
Comment 7•23 years ago
|
||
It's not. This is about us not getting the type, not not getting the encoding.
Comment 8•23 years ago
|
||
OK. I suck. I was looking for this bug and could not find it. Then right after I filed a duplicate and attached a patch I found it. :( Marking dup; the patch should hopefully land once tree reopens for 0.9.7 *** This bug has been marked as a duplicate of 109236 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•