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 532478 - strange behaviour expander in list view
strange behaviour expander in list view
Status: RESOLVED DUPLICATE of bug 342357
Product: nautilus
Classification: Core
Component: Views: List View
2.22.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-10 13:03 UTC by andbelo
Modified: 2008-05-10 13:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description andbelo 2008-05-10 13:03:33 UTC 
Please describe the problem:
When using Nautilus in the list mode, for either browser or default mode and either single or double-click, clicking anywhere between expander arrow and folder icon triggers action on highlighted file/folder even if this highlighted item is not the one that is being clicked

Steps to reproduce:
1. Open nautilus in list view mode and expand several folders that can be in the same hierarchical level
2. highlight one file/folder using the cursor or mouse
3. click (single-click mode) or double-click (double-click mode) in the space between any of the expander arrows and its respective icon causes Nautilus to trigger the default action for the highlighted file/folder


Actual results:
Open a file/folder without request

Expected results:
The expander arrow should expand/collapse the folder being clicked

Does this happen every time?
Yes, it does. In addition to that, it happened in Gnome 2.20 and now also occurs in Gnome 2.22

Other information:
Linux distros tested: Ubuntu Gutsy (7.10) and Hardy (8.04)

Bug originally submitted to Ubuntu in Launchpad (https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/174942)
Comment 1 Cosimo Cecchi 2008-05-10 13:22:30 UTC 
This has been already fixed in SVN trunk, thanks for the bug report.

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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