Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-select Bug #2627

Closed
cyberduck opened this issue Oct 3, 2008 · 2 comments
Closed

Multi-select Bug #2627

cyberduck opened this issue Oct 3, 2008 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Oct 3, 2008

anonymous created the issue

There have been multiselect bugs reported in the past, but I think they have been misunderstood as other bugs. The multiselect bug is still present and unfixed.

This bug is reproducible by connecting to a site, selecting a folder, then clicking the arrow of another folder that has NOT been opened yet (meaning a child list has not been made for that folder). There are two things selected at this point. One, the original folder that was selected and two, the now expanded folder.

This behavior is contrary to selecting a folder, then expanding (or contracting) an already loaded folder. This action does not change the folder selection.

Furthermore, once the selection error takes place, additional selections below the original selection in the file tree continue to be multiselections.

This bug can cause users to mistakenly believe they have single selected something new, when the folder expands in the window. However, once the folder has expanded in the window it pushes the still selected folder out of view of the user. So as the user moves to delete a single child file, Cyberduck deletes everything selected (the entire folder). The user thinks this is a delete bug and reports it incorrectly... like ticket #2590

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 4, 2008

anonymous commented

Additionally, if you preform an action on an item within a folder, its parent folder becomes selected once the action is complete. I think the general mechanism here is that when a folder's content is refreshed, that folder becomes selected without deselecting anything that might have been originally selected.

An example of this is renaming a folder within another folder, once renamed (has to be a different name than the original name) the parent folder is refreshed to sort the contents with the item's new name. Once this refresh is complete, the parent folder is selected along with the renamed item.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 4, 2008

@dkocher commented

In 2e524f2.

Loading

@cyberduck cyberduck closed this Oct 4, 2008
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants