Bug 254942

Summary:	Information panel switches to file's parent folder information when I move the cursor away from it
Product:	[Applications] dolphin	Reporter:	Nikita Churaev <lamefun.x0r>
Component:	general	Assignee:	Peter Penz <peter.penz19>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugzilla, mail
Priority:	NOR
Version First Reported In:	16.12.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Nikita Churaev 2010-10-22 11:23:26 UTC

Version:           unspecified (using KDE 4.5.2) 
OS:                Linux

This bug is pretty hard to explain. After I navigate to a folder by clicking on its icon in Dolphin, put the mouse cursor over some file to view it's information and then move the cursor away from it, the information panel switches to its parent folder information when it should continue to show the file information. Also when I put it over the file again, it doesn't show it's info at all.

Reproducible: Sometimes

Steps to Reproduce:
1. Open your home folder
2. Create a folder named "lol" in it
3. Create a file named "omg" in folder "lol"
4. Go back to the home folder
5. Open the folder "bug" by clicking on it
6. Put the mouse pointer over the file "omg"
7. Wait for the information panel to show it's info
8. Move the mouse pointer away from the file
9. Put the mouse pointer over the file "omg" again

Actual Results:  
The information panel switches to info of the folder "lol" immediately after the mouse pointer leaves the file. Also when you put the pointer over the file again, it doesn't show it's information at all.

Expected Results:  
The information panel should still show the information of file "omg"

Comment 1 Janet 2010-11-13 15:02:44 UTC

I partly agree: IMHO it is the *correct* way that the information panel shows the folder's info instead of the file's one when the cursor leaves the file and the file is not selected. That's what I expect, that's what I need. Please don't change that. When I want the file's information to stay I explicitly select/mark the file. Maybe an aditinal option for single-click to auto-select files after a user given period would help to avoid that confusion.

But now comes the bug: as soon as you hover over the file again of course the file information should be shown again. And that is not always the case by now. 

- Hover over file A and see the file's info. Hover over file B and see file B's info. Hover back over file A and see file A's info. Does work. Always.

- Hover over file A, see its info, hover over blank space in folder, see folder's info (ok so far), hover back over file A - still folder's info. So just the chain "file - folder - same file" does not work.

-Hover over file A, see its info, hover over blank space, see folder's info, hover over file B, see its info, hover over blank space, see folder's info, hover over file A, see its info etc. - this could go on forever, works.

Comment 2 Peter Penz 2010-11-13 15:09:16 UTC

@lamefun: Are you using the details view? In this case a regression has been fixed recently in trunk... (@Janet: No worry, it does not change the basic behavior)

Comment 3 Janet 2010-11-13 16:02:21 UTC

Funny, I just got the problem the other way round:

I hovered over a file in a subfolder, got its information in the sidebar, returned up one directory to the parent folder - and still the *file's* information was displayed in the information pane. I switched back into the subfolder - and now I *cannot* get the folder's information anymore when I hover over blank space, I always see the information for the last file the mouse hovered over! It even doesn't help to click into the blank space of the folder. No folder information anymore when I leave the files. It's the same dolphin instance. I just closed and reopened konqueror webbrowser in the meantime. I use icon view with column alignment. I really need to restart dolphin to get the behaviour back to show the folder's information when leaving a file.

Comment 4 Peter Penz 2010-11-13 16:06:51 UTC

@Janet: This issue has also been fixed in 4.6 :-) It was quite tricky to reproduce, but finally I found the root cause.

Comment 5 Julian Steinmann 2018-03-15 19:16:40 UTC

Both issues have now been fixed, closing this bug :)