170255 - Ctrl+Shift+V shortcut is not in the menu system.

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[Joseph Elwell]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0

Ctrl+Shift+V appears to be 'pasting as quoted' in Composer. (not listed in menu)

Expected: This keyboard shortcut should do nothing.

Reproducible: Always

Steps to Reproduce:

Comment 1

[Joseph Elwell]

sprinkling with flavour and cc'ing gail.

Comment 2

[gail]

adding some composer folks. 

Comment 3

[Kathleen :Brade]

Why is this a problem?  You should be able to remove the keybinding for your
particular usage (I'd have to look up the syntax tho).

We should have a bug for the keybinding not showing up in the menu.

Comment 4

[Joseph Elwell]

It's a problem for the same reason that it's a problem in the IM component a key
combo that was supposed to be undefined was suddenly doing something. It sounds
like the right fix is to get the item back in the menu.

Comment 5

[Akkana Peck]

I've seen the UE sentiment expressed several times that menus are not there to
document key bindings, and that items should not be added to menus simply for
that reason (corollary: it's okay to have functionality on keys that isn't in
the menus).

Personally, I like using the menus for that purpose (when learning new apps I
always browse the menus to see what's available, and look for key bindings
listed there to see if there's a quicker way) and if a UE person (ccing jglick)
rules that we should expose this, I'd be happy to implement it.

Comment 6

[Kathleen :Brade]

reassign to new placeholder

Comment 7

[Samir Gehani]

Composer triage team: nsbeta1-

Comment 8

[jglick]

Windows Guidelines says "If you define a keyboard shortcut for a command that
also appears in a drop-down menu, display the shortcut in the menu." 

Comment 9

[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

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

Comment 11

[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

Comment 12

[Robert Kaiser]

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