53428 - file not found (404) should not open an editor window

Status: NEW

(SeaMonkey :: Composer, defect)

Description

[Kathleen :Brade]

An editor window should not be opened in the case where a url can't be found.  
Instead we should present a dialog to the user.

to reproduce:
  Open Web Location (from browser or composer)
  enter this url:  http://www.mozilla.org/kathy.html
  make sure that the popup/drop down list says "New Composer Window"
  Click "Open" button

Notice that the error message is presented for users to edit.  Although 4.x also 
behaves this (buggy) way, I think we should intervene and catch this error 
earlier and not open a Composer window.

Comment 1

[Kathleen :Brade]

future

Comment 2

[rubydoo123]

accepting bug for post rtm fix

Comment 3

[Matthew Tuck [:CodeMachine]]

What if we actually want to edit the 404 page?  Maybe this should be a warning
rather than an error?

Comment 4

[Kathleen :Brade]

-->brade

Comment 5

[Syd Logan]

spam composer change

Comment 6

[Kathleen :Brade]

For the record, if you want to edit a 404 message, you shouldn't be trying to do 
that by editing a non-existing file.

Comment 7

[Jesse Houwing]

But what if I stuble upon a greatlooking 404 error message and want to edit it
to use for my own site, I can then enter a non existent url on that server, edit
it with composer and save it anywhere I want.

That's always better than having to save it from navigator, download all the
images as well and try to put things back together.

Comment 8

[Kathleen :Brade]

The above example is not a common case.  Most people do not expect to be able to 
edit such files.

Also, when saving/publishing that file back to the server, I don't think people 
would expect to publish it to the location they used for editing.

The workaround for the above example, is to load that page in the browser 
(probably where you first stumbled across it) and select all and copy/paste it 
into a blank composer page and then save it or publish it to the desired 
location.  I would think those steps are more obvious to users than the scenario 
presented above.

Comment 9

[Asa Dotzler [:asa]]

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)

Comment 10

[Kathleen :Brade]

not editorbase at this time

Comment 11

[Syd Logan]

nsbeta1+ per buffy triage

Comment 12

[Charles Manske]

Fixed as part of work on bug 174439

Comment 13

[sairuh (rarely reading bugmail)]

this still occurs (tested comment 0), using 2003.02.19. i get a composer window
with the "Not Found" text.

Comment 14

[Samir Gehani]

Composer triage team: nsbeta1-

Comment 15

[Tony Mechelynck [:tonymec]]

No comment in five years.

- Is this bug still happening? If not, close WORKSFORME.
- Is anyone interested in having it fixed? (Not me): if no, close WONTFIX.

Comment 16

[Tony Mechelynck [:tonymec]]

No reply to comment #15. Let's reset A+QA and see if anyone is watching.

Comment 17

[Kathleen :Brade]

This bug is very likely still a bug.  I don't think it should be resolved as WORKSFORME.  It *should* be fixed so WONTFIX doesn't seem appropriate.  Obviously a patch would be best.  :)

Comment 18

[Tony Mechelynck [:tonymec]]

(In reply to comment #17)
> This bug is very likely still a bug.  I don't think it should be resolved as
> WORKSFORME.  It *should* be fixed so WONTFIX doesn't seem appropriate. 
> Obviously a patch would be best.  :)
> 

"very likely": did you test it? (I never found out how to make Composer work).

Comment 19

[Terry R.]

No comment in another three years.

Is this bug still occurring? If not, can we close as WORKSFORME.
Is anyone interested in having it fixed?  If no, please close as WONTFIX.

Comment 20

[Philip Chee]

What does Blue Griffon or KompoZer do in this case?

Comment 21

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

Kompozer and BlueGriffon do not open an editor but they do open a tab... I guess
that's a new bug for bugzilla.bluegriffon.org, thanks for the heads up. Please
note both fire an alert. But they should close the recently opened tab after
the alert is closed.

I'm pretty sure Seamonkey has the same bug but you should test.

Comment 22

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

BlueGriffon bug:

  http://bugzilla.bluegriffon.org/show_bug.cgi?id=253

in case my future fix is reusable by Seamonkey or KompoZer.
I'll work on it next week.

Comment 23

[Philip Chee]

>   http://bugzilla.bluegriffon.org/show_bug.cgi?id=253

Thanks. Adding to Related bugs field.