124416 - Implement keyboard commands in Don't Save/Cancel/Save dialog

Status: RESOLVED DUPLICATE of bug 207510

(SeaMonkey :: Composer, defect)

Description

[Greg K.]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.8) Gecko/20020205
BuildID:    2002020516

The Save/Cancel/Don't Save dialog shown when closing an unsaved/unsent Composer
document cannot presently be controlled by keyboard commands. Such commands
should be implemented, such as Command-D for Don't Save, Command-. for Cancel,
and Command-S for Save.

Reproducible: Always
Steps to Reproduce:
1. Spawn a new Composer document window
2. Type one character into the document
3. Close the window
4. When the dialog appears, hit Cmd-D, Cmd-S, or Cmd-.

Actual Results:  No buttons were activated by the keyboard commands.

Expected Results:  The appropiate dialog button should have been activated.

Comment 1

[kinmoz]

--> Composer

Comment 2

[Kathleen :Brade]

-->cmanske for fix or reassignment

Comment 3

[Aaron Leventhal]

Command+. should be system wide for cancel in a dialog on Mac. Don't we have a
bug for that specific things.

Other than that, I think we should use accesskeys for this, right? In that case,
this would be a dependancy on bug 959.

Comment 4

[Greg K.]

My mistake. Command+. does, in fact, work in that dialog.

Comment 5

[Charles Manske]

We need to do this in all dialogs, covered by bug 112732

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

Comment 6

[sujay]

verified.

Comment 7

[Greg K.]

Reopening. Bug 112732 was fixed, and though command+. and command+s work,
command+d does not.

Comment 8

[Cecelia S]

The control key is implemented instead of the command key as I've just noticed
with build 20030925.

Comment 9

[Greg K.]

See also bug 207510.

Comment 10

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614