368086 - Cmd- S in save dialog brings up a new dialog

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Widget: Mac, defect)

Description

[Phillip M. Jones, C.E.T.]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1

In Previous versions to SeaMonkey 1.1 if I wished to save an email separately I could hit key Combination would bring up window to allow me to choose location to save an item. Then I could hit "Command-S (Save AS) again and would save item (usually an email post) in desired location. Now the first instance bring up the window. but second instance, the window disappear for split second the rebounds without saving anything, in fact, if even if the subject line slightly it rejects the name change. SeaMonkey is the only application to which this behavior happens. 

Reproducible: Always

Steps to Reproduce:
1. choose item to save, then hit command-S to bring up save as window
bringing up Save as file  item up in SM has same affect.
2.name as desired if necessary and choose location
3.Command-S this time does not save item.
4. Save Button does work but not save as then cond instance.
Actual Results:  
Window disappears rebounds no indication of saving anything has occured

Expected Results:  
Hard Drive activity indicating writing of file to Hard Disk

Saved file and  Save as window disappeared indicating job done

Comment 1

[Phillip M. Jones, C.E.T.]

A third Party has provide proof and suggested what problem is: Hear is text from creator of Default Folder X from Saint Claire software.

-----------------------------

-At 1:28 AM +0000 01/25/2007, Phillip Jones wrote:

> comments:  Up until just recently I've been able to call up an item to save (default Folder window) by hit Command-S then when in window choose location to save then hit Command-S again and it would save. now I can only use the save button that I must click. If I hit Command-S again the window disappears as though it has saved, but then pops up a split second later. And if you had changed the name slightly to prevent copying over something else the name is back to the original.
>
> use it mostly with SeaMonkey (Mozilla Suite) Just started in version 1.1.


As far as I can tell from some quick experimentation with SeaMonkey, what's happening is this:

1.  command-S brings up the save dialog
2.  pressing command-S again saves the file
3.  the file dialog does not remove the command-S keypress from the event
    queue, so SeaMonkey sees it again and immediately puts up a new Save
    dialog.

This is clear once you get rid of the save dialogs - a save confirmation window  appears once for each save that was done.  Count them as you close them, and that'll correspond with the number of times you clicked cmd-S within a Save dialog.

As for a solution, I'm afraid I can't do anything about this.  If you uninstall Default Folder X, the problem still happens - it's a bug in SeaMonkey.  You'll either need to get used to hitting the Return key instead of pressing cmd-S again in a save dialog, or contact the SeaMonkey team and get them to fix the bug :-(

 - Jon

-- 
________________________________________________________________________
  St. Clair Software              http://www.stclairsoft.com/
    Fax [phone]              ftp://ftp.stclairsoft.com/

Comment 2

[Stefan [:stefanh]]

Does this happens in Firefox 2.x? The reason I'm asking is that it sounds more like a core issue since we're using the native save dialog.

Comment 3

[Phillip M. Jones, C.E.T.]

I can not say because I only use Command-S (Save As) in the email portion of SeaMonkey.

If you desire me to I'll be gald to attempt to if FireFox.

Let me know here or privately. 

Comment 4

[Phillip M. Jones, C.E.T.]

Just Tried.
works as follows in FF 2.0..1.

Command-S the first time brings up window.
Command-S second press window blinks off, back on.

IF I click the save command Window dismisses and the Download Command comes up.

So appears same bug is in FF 2.0.0.1

here is version of FF:

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

Appreciate your taken effort to look into this. I was begining to wonder if anyone would take some as such seriously. I've brought up in Support group adn its been made fun of. 

Comment 5

[Stefan [:stefanh]]

OK, thanks. Fwiw, it works on trunk so I assume this is a widget: mac issue. So, when the save dialog comes up and you hit cmd+S, the file is saved, the dialog vanishes and pops up again. I'm confirming this since I can't find any dupes (but there might be).

Comment 6

[Phillip M. Jones, C.E.T.]

I have heard anyone else say they have the issue. Might have known me and my quirky way of doing things would uncover a bug know one is interested in or doesn't know about because they don't do the things I do. :-( . 

If its a duplicate feel free to mark this as such and let me know or put me on CC list for that bug so That I can track any progress

As far as I know this is all I contribute.

Oh I did try on my Lap too, using OSX.4.8 and get the same result from the same version of FF. As the software developer for Default Folder X  said  in his comments he tried on other things and it appears SM 1.1.1 only had this problem. 

Comment 7

[Phillip M. Jones, C.E.T.]

This is an update. I've since updated to SM 1.1.2 which is based on FF 2.0.0.3 now. It no nobody has looked at this problem. As its still not fixed.

This is on  Mac G4-500 using OSX.3.9 and G4 1.67Gb 17" Powerbook using OSX.4.8.  

Comment 8

[Phillip M. Jones, C.E.T.]

This an update as of April 24, 2009
OSX now up to 4.11.

SeaMonkey now up to 1.1.16.

I have tried beta of SM 2 and same issue their as well no change.

Comment 9

[Phillip M. Jones, C.E.T.]

Update November 25, 2009 I've just tried appears this issue may be fixed in SM 2.0

Just tried because this because a message popped up in email yet it appears no one has added anything other than myself.

I'll try again another day and if it still works I will asked it be marked closed.