Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 75459 - False double-click activation on icons
False double-click activation on icons
Product: Red Hat Linux
Classification: Retired
Component: nautilus (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Havoc Pennington
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2002-10-08 15:15 EDT by Kumaran Santhanam
Modified: 2015-01-07 19:00 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-10-08 15:15:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kumaran Santhanam 2002-10-08 15:15:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020827

Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Open a folder in Nautilus with a few folders in it
2. Make sure there is some empty space in that window
3. Pick a folder icon to open, but don't click on it yet
4. Quickly:  click on the empty space, then on that folder icon

Actual Results:  The selected folder opens.

Expected Results:  The folder should simply be selected, since the double-click
was not performed at the same pixel location.

To see the proper behavior, click on the empty space, wait for
2 seconds, then click on the folder icon.

Additional info:

I haven't looked at the code, but it seems that the canvas
widget must be registering double-click events even for
clicks that are not local to each other.  What isn't clear is
if this is a Gnome library problem, or specific to Nautilus.
Comment 1 Havoc Pennington 2002-10-08 16:52:06 EDT
I'm moving this bug to http://bugzilla.gnome.org/show_bug.cgi?id=95213

Closing on Red Hat level. We will get a fix with new upstream versions.

Note You need to log in before you can comment on or make changes to this bug.