Closed Bug 76925 Opened 21 years ago Closed 12 years ago

Format|Properties should have an accelerator (alt+enter...)

Categories

(SeaMonkey :: Composer, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: nbaca, Unassigned)

References

Details

(Keywords: platform-parity, Whiteboard: [keybnd])

Build 2001-04-19-04: NT4

Overview: According to the "Mail Compose Menu" spec, the HTML/New Message 
window's Format|Properties menu should have an accelerator, Alt+Enter.

The "Mail Compose Menu" spec can be found at 
http://mozilla.org/mailnews/specs/compose/Comp_Menus.html

Actual Results: Composer does not have an accelerator therefore the HTML/New 
Message window also does not have an accelerator for Format|Properties.

Expected Results: Can Alt+Enter be used?
Keywords: nsbeta1
OS: Windows NT → All
If Alt+Enter is used in message composition, it would be expected that the same 
keyboard shortcut could be used elsewhere -- e.g. for showing properties for 
the selected message in the three-pane window, or for showing properties of the 
selected bookmark in the Bookmarks window.

However, on Mac OS the standard meaning for Option+Enter is to open the 
selected item, while closing the parent window -- e.g. opening the selected 
message in a standalone window while closing the three-pane window, or opening 
the selected bookmark in a Navigator window while closing the Bookmarks window.

So certainly Alt+Enter should be used on Windows, since that is the standard on 
that platform, but something else needs to be used on Mac OS.
command i =>get info, right?
Reassigning to brade.
Assignee: beppe → brade
command-i won't work for Mac since that is "italic"
command-shift-i?

Set this to mozilla 1.0 until we know what keybindings we want.  Also, there may 
not be a way to implement this in a platform-specific way and have it show up 
correctly in the menus (if I remember correctly).  If that is true, we'll 
probably need to push this off further.
Target Milestone: --- → mozilla1.0
Temporarily move this item to mozilla 0.9.1 milestone for consideration before UI 
freeze.  If we want to have an accelerator on Format | Properties, we need to 
decide soon.

Can we use accel-shift-i on every platform?
What about accel-shift-r? or accel-shift-p?  
(or is accel-shift-p to be used with print/page setup?)
Keywords: pp
Target Milestone: mozilla1.0 → mozilla0.9.1
imo we should follow platform convention (which probably means using the 
platform dtd instead of redefining the elements).
no decision was made on this issue so pushing off to future
Target Milestone: mozilla0.9.1 → Future
Summary:
Alt+Enter for Windows is perfect.
Mac kbd team (brade+lordpixel+mpt) needs to find shortcut for properties on Mac.
Whiteboard: [keybnd]
spam composer change
Component: Editor: Core → Editor: Composer
Status: NEW → ASSIGNED
Keywords: nsbeta1nsbeta1-
Sounds like you need to create platformComposerBindings.xul à la
platformNavigationBindings.xml
no we don't. properties should be bound across the product.

<DShadow_> I've seen Cmd-J used for "Properties"
<DShadow_> you might also want to consider cmd-shift-i
<JFK-> I'd lean on command-j for info, as dragthing does
<JFK-> but it depends on which is used more
<DShadow_> Movie Player also uses it
*** Bug 184851 has been marked as a duplicate of this bug. ***
-->composer
Assignee: brade → composer
Status: ASSIGNED → NEW
*** Bug 250048 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Assignee: composer → nobody
QA Contact: sujay → composer
Target Milestone: Future → ---
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
Status: NEW → UNCONFIRMED
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
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
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
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
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.