102258 - Opening a text file in the browser should not prompt to download the attachment

Status: VERIFIED DUPLICATE of bug 85461

(Core Graveyard :: File Handling, defect)

Description

[TucsonTester2]

Build ID: 20010924

If you open a text file in the browser it will prompt you to download the
document or to open in it in a program.  It should not do this.  NS 4.7 opened
text files without prompting for a save.

Reproducible: Always

Steps to Reproduce:
1. Open Browser
2. Click on file -> Open
3. Navigate to a text file and choose to open it

Actual Results:
It will prompt you to download a file of type (text/readme) and to save it to
disk or to open it using an unspecified program.

Expected Results:
I would expect that the file would be opened automatically.  In my case the text
file was made of html and did not have the .html extension to define it as an
html file.  When opened in NS 4.7 it displayed the text as an html page with the
different text and background colors.

Comment 1

[TucsonTester2]

Sorry, the steps to reproduce are different. To get this to reproduce you will
have to use the following steps:

1.Open Composer
2.Change the color of the background and type some text
3.Save the file but do not save with the .html extension
4.Close the composer window and open the browser
5.Click on File and choose "Open File"
6.Navigate to the file you made and open it.

Comment 2

[R.K.Aa.]

related: bug 100900 (Mac), bug 45441 (Mac)

Comment 3

[TucsonTester2]

I can only get this bug to reproduce on OS 9.1 and OS X. Marking as Mac OS 9.x

Comment 4

[Doron Rosenberg (IBM)]

xpapps?

Comment 5

[Greg K.]

Confirmed using Mac/2001091311 (0.9.4), but Mozilla claims it's an "untyped binary file 
(application/octet-stream)" file, which is further from the truth.

In truth, any file whose only characterizing metadata is that it's a text file, should be 
opened and displayed as a text file, regardless of its' contents. If it's an HTML file, it 
should be characterized as such by a Type code of "HTML". "TEXT" files are text files, 
period.

I don't want Mozilla to get in the business of parsing files based on their CONTENTS, 
rather than their METADATA. Nothing could be more a waste of engineers' time than 
that.

(This bug is actually a duplicate of another bug of similar description, but I don't recall its' 
number at the moment.)

Comment 6

[timeless]

i suspect this is a dupe of 2 bugs. one that composer isn't marking as HTML and 
one that the uri somethingeranother isn't working or being used correctly.

Comment 7

[sairuh (rarely reading bugmail)]

spam: over to File Handling. i have not changed the assigned developer [or the
other fields for that matter], so if anyone realizes that a bug should have a
more appropriate owner, go ahead and change it. :)

Comment 8

[sairuh (rarely reading bugmail)]

->law for retriage as needed.

Comment 9

[Bill Law]

*** This bug has been marked as a duplicate of 85461 ***

Comment 10

[michael wendell]

Verified.