Changes between Version 1 and Version 2 of Ticket #10101, comment 5
- Timestamp:
- Jun 14, 2014, 8:48:43 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #10101, comment 5
v1 v2 4 4 5 5 If the user has `CHANGESET_VIEW`, `BROWSER_VIEW` and `FILE_VIEW` they see the following: 6 6 7 [[Image(WithBrowserViewAndFileView.png)]] 7 8 8 9 If the user has `CHANGESET_VIEW` and either one or neither of `BROWSER_VIEW` and `FILE_VIEW` they see: 10 9 11 [[Image(WithoutBrowserViewOrFileView.png)]] 10 12 … … 15 17 I'm left wondering about the following behaviors: 16 18 * If a user has `FILE_VIEW` and `CHANGESET_VIEW`, I would expect to see a diff of the changed files and to browse to the files. I wouldn't expect `BROWSER_VIEW` is necessary to see a diff or a listing of the files that have been changed. The user needs only to possess `FILE_VIEW` to view the contents of a file, so I don't see why the same should not be true in the changeset realm. I would expect `BROWSER_VIEW` to be necessary for a user to navigate from the changeset view to a directory listing in the repository browser (e.g. view the contents of a new directory added in the changeset). 17 * In the repository browser view, if the user has `BROWSER_VIEW` but not `FILE_VIEW`, I would expect that they could see the contents of the directories, including the filenames in the directories, but not browse to view the contents of the files . In analogy to the `rwx` permissions in Linux, I would expect `BROWSER_VIEW` to behave as though the user had `r` and `x` for a directory. Possessing the `FILE_VIEW` permission would be like having the `r` permission for a file.19 * In the repository browser view, if the user has `BROWSER_VIEW` but not `FILE_VIEW`, I would expect that they could see the contents of the directories, including the filenames in the directories, but not browse to view the contents of the files (comment:1). In analogy to the `rwx` permissions in Linux, I would expect `BROWSER_VIEW` to behave as though the user had `r` and `x` for a directory. Possessing the `FILE_VIEW` permission would be like having the `r` permission for a file. 18 20 19 21 So the changes I propose are:
