View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003727||Far Manager||File System||public||2019-08-07 02:07||2019-08-07 20:04|
|Target Version||Fixed in Version||3.0|
|Summary||0003727: Unnecessary elevation prompt when navigating to directory containing item(s) needing elevation for read access|
|Description||Beginning with this commit, which was first released in build 5441, if a user enables the “Request administrator rights: for read” option and then navigates to a directory containing one or more files or subdirectories that need elevation for read access, the user is unnecessarily prompted for elevation. If the directory contains more than one such item, Far Manager prompts the user for each individual item.|
The expected behavior is to prompt the user for elevation only when accessing the actual item (e.g., viewing a file or navigating into a subdirectory) that needs elevation for read access, and not the parent directory.
|Steps To Reproduce|
|Tags||No tags attached.|
I just realized after some more experimentation that I inadvertently omitted a crucial piece of information:
The unnecessary elevation prompt occurs only if the current file panel mode includes the “LN” (number of hard links) column type.
> only when accessing the actual item
The mentioned commit also added support for elevation when requesting file owners.
Indeed, we don't want that when reading a directory so I've added a suppression in 5445.
Just in case - I recommend that you make sure that you really intended to show file owners and didn't enable them accidentally - it's a relatively expensive operation.
Ah yes, my mistake. It was triggering on file owners, not number of links. Thanks for adding the suppression.
Thanks also for letting me know that enabling file owners is relatively expensive. I do have them enabled by default, but I haven't felt any performance problems. Perhaps this just isn't an issue on a sufficiently fast system.
||Confirming that it's fixed in build 5445.|
|2019-08-07 02:07||Spire||New Issue|
|2019-08-07 02:50||Spire||Note Added: 0016554|
|2019-08-07 02:51||DrKnS||Assigned To||=> DrKnS|
|2019-08-07 02:51||DrKnS||Status||new => feedback|
|2019-08-07 02:51||DrKnS||Note Added: 0016555|
|2019-08-07 02:52||DrKnS||Note Edited: 0016555||View Revisions|
|2019-08-07 04:51||Spire||Note Added: 0016560|
|2019-08-07 04:51||Spire||Status||feedback => assigned|
|2019-08-07 19:04||Spire||Note Added: 0016561|
|2019-08-07 20:04||DrKnS||Status||assigned => closed|
|2019-08-07 20:04||DrKnS||Resolution||open => fixed|
|2019-08-07 20:04||DrKnS||Fixed in Version||=> 3.0|
|2019-08-07 20:04||DrKnS||Build||=> 5445|