Closed
Bug 246438
Opened 20 years ago
Closed 20 years ago
Can't handle MIME typed files with browser directly.
Categories
(Core Graveyard :: File Handling, defect)
Tracking
(Not tracked)
People
(Reporter: mozilla, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8 There are several file types that I regularly deal with (.idl, .C, .pl, etc.) that have valid MIME types in the browser. If I use it to browse to a file on disk (file:///...) When I click on one of these files, I get a dialog asking me what I would like to do with this file. There is no option that says "Handle in browser" I think that this should be one of the settings in the "File Types" setting. I should be able to enter a MIME type or file extension, and say "Handle In Browser" I would then do this for .C, .pl, .idl, etc. files and I could view them directly as if they were text/plain files. Actually, that would be an interesting way to handle this setting: Have a MIME type transformer that lets me say "Always treat mime type X as mime type Y" Then, I would say handle all "application/x-perl" as "text/plain". The browser is trying to be too smart, and is getting a little annoying. Reproducible: Always Steps to Reproduce: 1. Enter a local file:// URL to a perl file. 2. Notice dialog that comes up asking you what you want to do. 3. Be frustrated by inability to "view in browser." Actual Results: Frustration. :) Expected Results: I should be able to choose "View in Browser" as a default option for many simple text files.
Comment 1•20 years ago
|
||
*** This bug has been marked as a duplicate of 57342 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Summary: Can't handle MIME typed files with browser directly. → Can't handle MIME typed files with browser directly.
Updated•8 years ago
|
Product: Core → Core Graveyard
Updated•2 years ago
|
Type: enhancement → defect
You need to log in
before you can comment on or make changes to this bug.
Description
•