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 587617 - "search-as-you-type" prevents correct clicking in listview
"search-as-you-type" prevents correct clicking in listview
Status: RESOLVED DUPLICATE of bug 587074
Product: nautilus
Classification: Core
Component: Views: List View
2.26.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-07-02 16:30 UTC by Psy[H[]
Modified: 2009-07-03 08:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Psy[H[] 2009-07-02 16:30:16 UTC 
Please describe the problem:
As similar bug 462875 was reported fixed long ago, I will file a new one.
using Ubuntu Jaunty, current upgrades, Nautilus 2.26.2
Clicking on file or folder while searchbox is still visible results in unfolding the first visible folder in browsing window, if there are no folders visible - nothing happens. In both cases doubleclick on file or folder does not result in desired action.
Pressing enter instead of clicking works fine.

Steps to reproduce:
1. open folder with other folders in nautilus
2. switch to list view
3. start typing some folder or file name, then doubleclick on any visible file or folder while searchbox is still visible.


Actual results:
Clicking results in unfolding the first visible folder in browsing window, if there are no folders visible - nothing happens. In both cases doubleclick on file or folder does not result in desired action while searchbox is visible

Expected results:


Does this happen every time?
yes

Other information:
Comment 1 Nelson Benitez 2009-07-03 08:44:38 UTC 
Hi, it's a bug in gtktreeview (which nautilus uses for listview), I've already submitted a patch for gtktreeview, will mark this as dupe. 

Thanks for taking the time to report!

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