---- Reported by jim@yorba.org 2010-06-16 15:54:00 -0700 ----

Original Redmine bug id: 2133
Original URL: http://redmine.yorba.org/issues/2133
Searchable id: yorba-bug-2133
Original author: Jim Nelson
Original description:

Tab/Shift+Tab does not move the focus to the histogram sliders in the Adjust
window.



---- Additional Comments From shotwell-maint@gnome.bugs 2011-09-29 15:48:00 -0700 ----

### History

####

#1

Updated by Adam Dingle over 3 years ago

  * **Priority** set to _High_

####

#2

Updated by Adam Dingle over 3 years ago

  * **Status** changed from _Open_ to _Review_
  * **Assignee** changed from _Anonymous_ to _Lucas Beeler_

####

#3

Updated by Adam Dingle over 3 years ago

  * **Priority** deleted (<strike>_High_</strike>)

Lucas has done some great work getting this feature started, but it won't make
0.7 at this point. Dropping to medium.

####

#4

Updated by Adam Dingle over 2 years ago

  * **Assignee** changed from _Lucas Beeler_ to _Anonymous_

####

#5

Updated by Adam Dingle about 2 years ago

  * **Description** updated (diff)
  * **Priority** changed from _Low_ to _High_
  * **Target version** set to _0.12_

All Shotwell features should be accessible via the keyboard.  Let's try to fix
this for 0.12 as we move to GTK 3.

####

#6

Updated by Jim Nelson about 2 years ago

  * **Description** updated (diff)
  * **Priority** changed from _High_ to _Low_
  * **Target version** deleted (<strike>_0.12_</strike>)

Since the histogram controls aren't going to be rewritten for GTK+3, there
won't be the easy opportunity to fix this.



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

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

Unknown Component 
   Using default product and component set in Parameters 
Unknown version " in product shotwell. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product shotwell. 
   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