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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

鉀戯笍 Polishing for new sharing design and flow 馃 #40172

Closed
16 of 23 tasks
AndyScherzinger opened this issue Aug 31, 2023 · 5 comments 路 Fixed by #40266, #40365, #40372 or #40389
Closed
16 of 23 tasks

鉀戯笍 Polishing for new sharing design and flow 馃 #40172

AndyScherzinger opened this issue Aug 31, 2023 · 5 comments 路 Fixed by #40266, #40365, #40372 or #40389

Comments

@AndyScherzinger
Copy link
Member

AndyScherzinger commented Aug 31, 2023

Follow-up to #26691 listing the remaining open issues to be fixed in master as well as stable27


#39472 (comment)

Share list

  • BUG: Quick access menu should close when click outside

Bugs specific to share settings

  • BUG: Setting "Allow public upload" disabled should also disable options to set file drop, according permissions

Screenshot 2023-08-17 at 12 23 33



  • BUG: Create a new share to a user, change to custom permission, click save share, go back to the share details -> now update and share check-boxes are missing (the custom permissions are the same as view only, but nevertheless the check-boxes should of course still be available)
  • BUG: Creating shares should probably not reload the full file list. Edit (louis): only an issue with 27 as the logic to handle share changes is not fine-grained enough to only refresh the share status of a file. Also, it was not introduced by the new sharing flow.
  • BUG: Related resources should not appear in the share details view - Hide additional content when share details is open聽#40365

Non-blocking

  • Accessibility fixes for quick menu
  • "Delete share" button does not need to be sticky, can just be a tertiary button (no background by default) below the advanced settings toggle (not inside advanced settings)
  • The "Cancel" and primary button on the bottom need a backdrop to separate them a bit from the background, best a fade from color-main-background on the bottom to transparent on the top.
  • Currently links are sorted below emails once created, but sorting should be: Links, mails, users
  • Too many share saved/updated notifications when updating/creating shares
  • QA: Needs side by side testing if all old options are possible or also properly limited with the new one
  • Clarify how to handle tests, currently most (if not all) e2e tests in selenium would become obsolete, should probably be followed up by cypress tests聽#40436
  • If allow public upload admin setting is unchecked we should rename "Allow upload and editing" to "allow editing" and file drop / create permission should be disabled state

#39472 (review)

Follow-ups:

  • Switching between permissions presets should not close the advanced settings view
  • The content of the sidebar is scroll-able when it should only be the content of the share tab

Screenshot from 2023-08-29 11-52-15

UI comments:

  • Button at the bottom of the details view should not move when scrolling to the bottom
  • "Delete share" button text seems smaller than other buttons
  • It is confusing to have the download permission under "Custom permissions" as it is not taken into account for bundles
@AndyScherzinger AndyScherzinger added this to the Nextcloud 28 milestone Aug 31, 2023
@AndyScherzinger AndyScherzinger added 1. to develop Accepted and waiting to be taken care of and removed 0. Needs triage Pending check for reproducibility or if it fits our roadmap labels Aug 31, 2023
@AndyScherzinger
Copy link
Member Author

It is confusing to have the download permission under "Custom permissions" as it is not taken into account for bundles

@artonge can you elaborate on this item, what is meant by it?

@Fenn-CS
Copy link
Contributor

Fenn-CS commented Sep 15, 2023

This was closed automatically, reopening to all boxes are checked.

@AndyScherzinger
Copy link
Member Author

@Fenn-CS better to move the remaining items to a new issue and close this one. The closed ones are resolved with 27.1.0 the remaining ones would then be 27.1.1 and the ticket can't reflect that when not split up 馃槉

@sorbaugh
Copy link
Contributor

@AndyScherzinger on it

@AndyScherzinger
Copy link
Member Author

remaining items have been moved to #40438 as a follow-up issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment