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 713436 - In conversation viewer and composer Shift+TAB should shift focus out of the web view
In conversation viewer and composer Shift+TAB should shift focus out of the w...
Status: RESOLVED OBSOLETE
Product: geary
Classification: Other
Component: ux
unspecified
Other All
: High normal
: 0.14.0
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: geary-wk2 792388
Blocks:
 
 
Reported: 2012-03-15 07:15 UTC by Adam Dingle
Modified: 2021-07-05 13:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Make Shift+TAB focus subject when focus is in a composer widget (3.30 KB, patch)
2017-05-25 18:43 UTC, Kacper Bielecki
none Details | Review

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


---- Reported by adam@yorba.org 2012-03-15 12:15:00 -0700 ----

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

When I'm composing a message in Geary, I sometimes enter a Subject, tab down
to the message area, then realize I want to change the Subject I entered. It
would be nice if I could press Shift+TAB to return to the Subject line in this
case.

Related issues:
related to geary - 5014: in composer, message area should follow Subject
in tab order (Fixed)
related to geary - 5360: Keyboard focus strangeness when composing new
message (Duplicate)
related to geary - 7675: Shift+Tab should move focus from conversation
viewer to ... (Open)



---- Additional Comments From geary-maint@gnome.bugs 2013-11-06 19:22:00 -0800 ----

### History

####

#1

Updated by Adam Dingle over 1 year ago

  * **Target version** deleted (<strike>_0.1_</strike>)

####

#2

Updated by Jim Nelson 15 days ago

  * **Category** set to _ux_



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

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

Unknown version " in product geary. 
   Setting version to "!unspecified".
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.
Resolution set on an open status.
   Dropping resolution 

Comment 1 ponyesteves 2016-09-29 20:44:36 UTC
I run into the same problem! +1 to fix this
Comment 2 Michael Gratton 2017-01-31 23:58:02 UTC
Currently in the composer's message body editor, Shift+Tab is bound to "remove current tab" - i.e. if you press Tab, you get a tab character inserted, and if you press Shift+Tab it is removed. This only works if the text cursor is in front of a tab however, and so it is basically redundant given the Backspace key.

So we should probably remove the custom handling for Shift+Tab, and look into updating the custom focus chain so this works.

Note for the moment that you can use Ctrl+Tab and Ctrl+Shift+Tab to escape the editor.
Comment 3 Michael Gratton 2017-02-16 07:06:48 UTC
This is applicable to the conversation viewer as well.
Comment 4 Kacper Bielecki 2017-05-25 18:43:20 UTC
Created attachment 352590 [details] [review]
Make Shift+TAB focus subject when focus is in a composer widget

While implementing it I tried to find a way to move focus using default GTK focus flow logic. However, after looking into GTK code, it seems to me that all that logic is private to GTK.

This is why, proposed solution sets focus explicitly on Subject entry.
Comment 5 Michael Gratton 2018-06-26 04:47:22 UTC
Bump tickets to 0.14 that aren't going to make 0.13.
Comment 6 GNOME Infrastructure Team 2021-07-05 13:24:50 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/geary/-/issues/

Thank you for your understanding and your help.