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 703030 - When renaming a file at the end of a folder, it get covered by a label
When renaming a file at the end of a folder, it get covered by a label
Status: RESOLVED DUPLICATE of bug 661991
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-06-25 08:43 UTC by Andreas Nilsson
Modified: 2015-06-15 13:11 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screenshot (85.65 KB, image/png)
2013-06-25 08:43 UTC, Andreas Nilsson 		Details

Description Andreas Nilsson 2013-06-25 08:43:47 UTC 
Created attachment 247705 [details]
screenshot

It seems the label only considers mouse focus and not keyboard focus.
Comment 1 António Fernandes 2013-06-25 08:49:42 UTC 
In this specific case, moving it to the right side would get it out of the way. But if the floating label is too wide, this won't do. I'd rather see the general issue addressed: bug 651293
Comment 2 Nelson Benitez 2013-07-20 12:00:07 UTC 
Antonio, shouldn't this be a duplicate of bug 651293 ? If not, what is the difference?
Comment 3 António Fernandes 2013-07-20 14:07:11 UTC 
(In reply to comment #2)
The reason left this report open is that Andreas raised an interesting point about considering keyboard focus in addition to pointer movement.

If you move the pointer over the floating bar, you will notice that it moves to the opposite side of the window. Making this happen for keyboard focus as well would be an enhancement to the floating bar, and would fix the particular case in this screenshot, even though it won't fix bug 651293.
Comment 4 Alexandre Franke 2015-06-15 13:11:04 UTC 

*** This bug has been marked as a duplicate of bug 661991 ***