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 754744 - Move keyboard focus to newly created folder
Move keyboard focus to newly created folder
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: general
3.26.x
Other Linux
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 780921 784401 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-09-08 21:15 UTC by Sebastian Keller
Modified: 2021-06-18 15:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch (1.10 KB, patch)
2017-03-20 05:05 UTC, Kevin Lopez
none Details | Review
Patch (1.35 KB, patch)
2017-03-22 18:40 UTC, Kevin Lopez
none Details | Review

Description Sebastian Keller 2015-09-08 21:15:57 UTC
After creating a new folder through the hamburger menu, the keyboard focus stays on the hamburger menu button, so you can't go to the newly created folder by simply pressing enter again.

Using the context menu works fine, but that's often not available when using the list view.
Comment 1 Stefan 2016-11-01 22:12:39 UTC
Please update the Version to 3.22.x because the problem is still existing.
Comment 2 Stefan 2016-11-01 22:16:46 UTC
Forgot to add, that in the list view, a newly created directory  through the hamburger menu looks like selected (blue color) but the focus is still on the hamburger menu.
This is very confusing.
Comment 3 Kevin Lopez 2017-03-20 05:05:34 UTC
Created attachment 348293 [details] [review]
Patch

(In reply to Stefan from comment #2)
> Forgot to add, that in the list view, a newly created directory  through the
> hamburger menu looks like selected (blue color) but the focus is still on
> the hamburger menu.
> This is very confusing.

Hope now works ok.

Regards!
Comment 4 Carlos Soriano 2017-03-22 16:21:23 UTC
Review of attachment 348293 [details] [review]:

Yes excellent!
We could do the same for every dialog, since we don't know where the focus would be. Something to think about...

Just a nitpick:

::: src/nautilus-files-view.c
@@ +2023,2 @@
     g_clear_object (&priv->new_folder_controller);
+    gtk_widget_grab_focus (GTK_WIDGET (view));

Can you add a comment why we need to do this?
Comment 5 Kevin Lopez 2017-03-22 18:40:12 UTC
Created attachment 348526 [details] [review]
Patch

(In reply to Carlos Soriano from comment #4)
> Can you add a comment why we need to do this?
Sure!
Comment 6 Carlos Soriano 2017-03-27 20:10:24 UTC
Pushed with some changes to the wording, thanks!
Comment 7 Daniel Boles 2017-03-27 20:12:48 UTC
(In reply to Stefan from comment #1)
> Please update the Version to 3.22.x because the problem is still existing.

AFAIK - but I welcome correction if I'm mistaken - the general policy is to leave the version at the value it had when the bug was originally reported, as a quick way to assess how long the bug has been around. Plus, it's really very impractical to imagine keeping all longstanding bugs' versions up-to-date constantly. :)
Comment 8 Carlos Soriano 2017-03-27 20:16:26 UTC
(In reply to Daniel Boles from comment #7)
> (In reply to Stefan from comment #1)
> > Please update the Version to 3.22.x because the problem is still existing.
> 
> AFAIK - but I welcome correction if I'm mistaken - the general policy is to
> leave the version at the value it had when the bug was originally reported,
> as a quick way to assess how long the bug has been around. Plus, it's really
> very impractical to imagine keeping all longstanding bugs' versions
> up-to-date constantly. :)

Not really, versions should be update to the latest one can reproduce, since we usually don't support older stable versions. In this way we can know if it's still happens or not, since the most common case is where bugs get invalid in some future versions but nobody goes to the old ones to test + close.
Comment 9 Daniel Boles 2017-03-27 20:18:08 UTC
Oops, I must have been thinking of some other project. Thanks for the correction!
Comment 10 Carlos Soriano 2017-03-27 20:26:14 UTC
(In reply to Daniel Boles from comment #9)
> Oops, I must have been thinking of some other project. Thanks for the
> correction!

Actually I'm almost sure this is for all GNOME projects. You can ask in #bugs for more info :)
Comment 11 Daniel Boles 2017-03-27 20:36:44 UTC
Sure, I meant some other, non-GNOME project. For GNOME, I shall bump versions wherever I notice and can repro. :D
Comment 12 Ernestas Kulik 2017-04-05 10:26:04 UTC
*** Bug 780921 has been marked as a duplicate of this bug. ***
Comment 13 Ernestas Kulik 2017-04-05 10:26:39 UTC
The fix doesn’t seem to work here.
Comment 14 Ernestas Kulik 2017-04-05 12:19:16 UTC
Due to how selection works (from set_selection), the keyboard focus isn’t moved, so grabbing focus of the container as in the patch doesn’t fully fix the problem. It only happens to work as expected if no item is selected or focused.
Comment 15 Ernestas Kulik 2017-06-30 21:07:14 UTC
*** Bug 784401 has been marked as a duplicate of this bug. ***
Comment 16 André Klapper 2021-06-18 15:53:54 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 of Files (nautilus), then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/

Thank you for your understanding and your help.