If you click on the name of the directory, and you don't have the correct
permissions to enter/expand the node, a warning dialog pops up. There is no
warning if you only click on the little triangle to expand the branch. It
silently fails.

This was confusing for a minute when I was testing copy and paste. I would
click, and nothing would happen.



------- Additional Comments From mjs@noisehavoc.org 2000-11-03 20:41:23 ----

We could probably show visual feedback for this - an emblem or "unreadable
folder" icon of some sort. Design help!




------- Additional Comments From sullivan@eazel.com 2000-11-06 12:08:03 ----

My first thought is that there's probably not enough room in the tree view to 
make a recognizable "reduced permissions" graphic. (Where would it go? 
On top of the tiny folder icon?). So even if we do come up with a 
perhaps-recognizable graphic, I think we probably do want to put up a "you 
can't do that" dialog when the user tries to expand the folder.



------- Additional Comments From arlo@workthatmouse.com 2000-11-06 14:05:34 ----

I've been pushing Andy to let there be a special folder design for 

non-readable folders.



If this were the case, the user would see that folder type in the tree view 

and know that they couldn't expand it.



------- Additional Comments From sullivan@eazel.com 2000-11-06 14:45:17 ----

I think such a design could certainly help, but I am not confident that all 
users would understand the distinction by itself. These icons are very 
small, and different themes would look different (maybe some lazy 
theme-maker would use the same icon for both cases), so the visual 
distinction might not be enough. I still think displaying a dialog isn't a bad 
idea.

Another possibility is to make the expansion triangle be present but look 
disabled, but I don't know how much work that would be too get right, and 
it still might not be totally clear to everyone.



------- Additional Comments From mjs@noisehavoc.org 2000-11-27 22:08:53 ----

If you visit an unreadable directory in the main nautilus view
(/home/httpd/cgi-bin makes a good example) it gets displayed but appears to be
empty. So fundamentally the problem here is that unreadable directories are
being treated the same as empty directories. Would appreciate design guidance
for resolving the general case of this problem.

(NautilusDirectory currently has no API to detect directory load errors; perhaps
Darin has advice on the subject so I am cc-ing him).




------- Additional Comments From darin@bentspoon.com 2000-11-28 12:01:08 ----

It's easy to add what we need to NautilusFile so that the clients can detect the error. I 
still don't know what the minimum acceptable desired user interface is, though, so 
it's hard to make a specific suggestion. It would be easy to add an error code to the 
done_loading signal, for example, but I can't tell if that would be sufficient.

We'll need to fix the tree view and the main content view separately, of course, and 
probably use different UI for the two cases. Having one bug to cover both seems 
suboptimal.



------- Additional Comments From mjs@noisehavoc.org 2000-12-20 16:33:57 ----

This only seems to happen in the tree view currently.

A good design might be to refuse to rotate the disclosure triangle, and put a
message in the status bar.




------- Additional Comments From mjs@noisehavoc.org 2000-12-20 16:36:15 ----

This can probably wait until 1.0.1 or later.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:45 -------