After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 713369 - composer: cut/copy/paste shortcuts broken in To/Cc/Bcc
composer: cut/copy/paste shortcuts broken in To/Cc/Bcc
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: general
0.1
Other All
: High normal
: ---
Assigned To: Eric Gregory
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-04-05 09:54 UTC by Adam Dingle
Modified: 2013-05-01 06:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Charles Lindsay 2013-11-21 20:20:06 UTC 


---- Reported by adam@yorba.org 2012-04-05 14:54:00 -0700 ----

Original Redmine bug id: 5019
Original URL: http://redmine.yorba.org/issues/5019
Searchable id: yorba-bug-5019
Original author: Adam Dingle
Original description:

To see the problem:

1. Open the composer window.

2. Enter some text in the To field.

3. Select the text and try to press Ctrl+X to cut it. Nothing will happen.

It appears that Ctrl+C/V/X always act on the message area, even when the To,
Cc or Bcc field has keyboard focus.



---- Additional Comments From geary-maint@gnome.bugs 2013-05-01 11:49:00 -0700 ----

### History

####

#1

Updated by Eric Gregory over 1 year ago

  * **Category** set to _13_
  * **Status** changed from _Open_ to _5_
  * **Resolution** set to _fixed_

####

#2

Updated by Charles Lindsay 7 months ago

  * **Status** changed from _5_ to _Fixed_



--- Bug imported by chaz@yorba.org 2013-11-21 20:20 UTC  ---

This bug was previously known as _bug_ 5019 at http://redmine.yorba.org/show_bug.cgi?id=5019

Unknown Component 
   Using default product and component set in Parameters 
Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.