132421 - publish with a filename w/o the .html extension throws HTML code in browse window

Status: RESOLVED WORKSFORME

(SeaMonkey :: Composer, defect)

Description

[sujay]

using 3/20 build on windows

1) launch netscape
2) launch composer
3) enter Hello World
4) enter valid publish settings, but for filename, give it "hello" make sure
you don't append ".html"
5) publish
6) browse

look at the HTML code in the browse window..

Comment 1

[Kathleen :Brade]

how was this published?  ftp or http?
what server?
is it true for publishing to all servers or only that one?

Comment 2

[sujay]

happens for both ftp and http.
I tried two different servers....same problem

servers = jazz and marvin

very easy to reproduce

Comment 3

[sujay]

take a look: http://jazz/users/sujay/publish/hello 

"hello" is the file I just published up w/o HTML extension

you should see HTML code in your browser

Comment 4

[Boris Zbarsky [:bzbarsky]]

This sounds like the server is just misconfigured and sends the file as
text/plain....

Comment 5

[Charles Manske]

Attachment: Patch v1.

Add HTML extensions if missing. This is exactly what we do when saving file
to local disk.

Comment 6

[Kathleen :Brade]

Comment on attachment 75406 [details] [diff] [review]
Patch v1.

I disagree with the approach in this patch.  Users should be able to publish
files without extensions.

Comment 7

[Charles Manske]

FYI:
In Windows, it is very standard to automatically append an extension if the user
didn't supply one and the file type is known, which is true for editing HTML in 
Composer. We do this now when saving to local disk.

Comment 8

[Charles Manske]

Removing "FIX IN HAND". We'll discuss further

Comment 9

[Charles Manske]

I *really* think we should add ".html" if user doesn't supply and extension.

Comment 10

[sujay]

any resolution on this?

Comment 11

[Kathleen :Brade]

I still contend this is a server issue.  There are no current plans to fix this
soon unless the server problem can be diagnosed and addressed.

Comment 12

[sujay]

nominating....users can easily run into this.

Comment 13

[Charles Manske]

We know when users are editing HTML from the mimetype. If it is, I think we 
should automatically append ".html" if user hasn't supplied an extension.

Comment 14

[Kathleen :Brade]

I'd prefer if we prompted users so that they could still publish files without
extensions but the default button would append whatever extension we said (also,
we'd make them click publish again in case they prefer .htm over .html?)

Robin--could you help us with the wording for this dialog?

Comment 15

[Charles Manske]

Kathy: I'm surprised! You're usually against extra popups like this!
I still don't think people need to publish extensionless files. 
We don't allow that when saving to disk (we append ".html" if missing, just as I 
suggest here.)

Comment 16

[robinf]

I tend to agree with Charley and Sujay. In the Publishing help ("Solving Common
Publishing Problems"), we remind users to make sure that their Composer file
names end with either .htm or .html. 

In the Publish tab, we use this example next to the Filename field  -- "e.g.,
mypage.html"

We seem to be telling users to make sure their Composer file names end with the
.htm or .html extension. This bug, if fixed, would further reinforce that
message. I don't think we should give users the choice to not include the .htm
or .html extension.

Comment 17

[Kathleen :Brade]

Charley--you are right that in most cases I am opposed to these annoyances. 
However, I don't think we should disallow having no extension or forcing our
preference (*.html) over the user's preference (*.htm).

Also, to clarify the claim in comment 15--I am able to save a local file without
an extension (as I should be able to).

Comment 18

[Charles Manske]

Than must only be on Mac! In Windows, it appends ".html"

Comment 19

[Claus Färber]

There is a reason to allow publishing w/o an extension:
http://www.w3.org/Provider/Style/URI

Comment 20

[Akkana Peck]

Plussing -- we don't necessarily need a complete solution, but let's come up
with at least a partial solution for buffy.

Comment 21

[Samir Gehani]

Composer triage team: nsbeta1-

Comment 22

[Serge Gautherie (:sgautherie)]

Charles,
Are you still working on this ?

Comment 23

[Phoenix]

Checked, file published without extension, but displayed correctly, so closing as WFM
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0 SeaMonkey/2.13a1
Build identifier: 20120712003002