In gedit's Replace window, a single Tab does not move focus from Search to Replace field

Red: Choice disclosure control that currently receives input focus when Tab is pressed in Search field.
Green: Replace field, which should be the next control to receive focus when Tab is pressed in the Search field.

I tried the patch, it didn't seem to fix the problem. Initially I was seeing an error in the console:

sys:1: GtkWarning: GtkEntry - did not receive focus-out-event. If you
connect a handler to this signal, it must return
FALSE so the entry gets the event as well

So I added a return FALSE to gedit_history_entry_set_tab_index_callback, which suppressed the error but didn't actually make tab focus the replace entry. I still get the selector focused on tab.

Cannot fix it, anyone else?

There is a patch upstream.

If you can't work on a bug, then please set it back to Confirmed or Triaged and not New.

On 11/26/10 at 12:20pm, Papercuts Bug Mailer wrote:
> You have been assigned a bug task for a public bug by Vish (vish):
>
> When the user opens the Replace dialog (Search > Replace...), the
> default input focus lies in the Search field. The user types the search
> string, and presses tab to enter the replacement string, but the input
> focus moves from the Search field to the choice disclosure control
> instead of to the Replace field. Pressing Tab in the Search field should
> move input focus to the Replace field. The search field can recall
> history by pressing Up/Down arrows, and offers autocomplete, so changing
> the Tab focus chain does not prevent the user from recalling a previous
> search string.
>
> ** Affects: gedit
> Importance: Low
> Status: New
>
> ** Affects: hundredpapercuts
> Importance: Low
> Assignee: Papercuts Ninja (papercuts-ninja)
> Status: Triaged
>
> ** Affects: gedit (Ubuntu)
> Importance: Low
> Status: Triaged
I want to get start with this bug. I have one problem. I did:

$ bzr branch lp:ubuntu/gedit gedit
$ cd gedit
$ bzr bd -- -S -us -uc

I got errors:
http://pastie.org/1367760

Any suggestions?

Problem is solved. I installed a few other packages.

I tried to fix this bug but I encountered the problem. Function: set_focus_chain is not available in stable version of Gtk+. This function corresponds for "tab order" I think the good decision will be waiting to stable version of Gtk+ after that fix this bug.

Please change staus bug to: "Triaged"

Robert Sajdok , thanks for taking a look at this bug..!
No worries though that it dint work.. :) Feel free to take a shot at the other papercuts : <https://bugs.launchpad.net/hundredpapercuts/+bugs?field.status%3Alist=TRIAGED> .

@Vish
Yes. I am very keen in this project. I am looking for another bug now :)

I see this bug listed in "One Hundred Paper Cuts nt5-office "Evolution , gedit & LibO" associated with natty development. When I populated gedit and ran 'replace' dialog pressing tab with focus attached at search field hadn't reproduced this bug, or in otherwords, tabbing focus from 'search' to 'replace' seems to work as desired. Should this bug still be open for this development branch?

Christopher Overton, I was indeed able to reproduce this bug in Gedit version 2.30.4 that ships with Natty. I observed that when I press Tab when in the search field, focus is shifted first to the button that reveals the search field's dropdown menu, and a second tab is required to move into the replace field.

I confirmed this is still an issue with:

Ubuntu 12.04.2 64bit Alternate, Fresh Install
gEdit 3.4.1

Still an issue on Ubuntu 13.04, gEdit 3.6.2
There's a patch upstream by a gEdit developer, almost 3 years old. It works, but another developer said he doesn't like it (code-style-wise). Maybe we could implement it as Debian patch while we wait for an upstream solution?

To anyone affected by this issue,

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. This bug was reported some time ago and there have been many changes in Ubuntu and GNOME since that time.

I'm using Ubuntu 18.04 and gedit 3.28.1 hare and it seems that the issue has now been resolved.

Does anyone still see a problem related to the one that was reported in a currently supported version of Ubuntu?

Please let us know if you do otherwise this bug report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Bug did not expire due bug watch
Upstream issue closed "RESOLVED OBSOLETE" as version too old to fix
Fixed in new versions (comment #16) so closing as fixed