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

Public link share cleanup #29721

Closed
wants to merge 1 commit into from
Closed

Conversation

felixheidecke
Copy link
Contributor

@felixheidecke felixheidecke commented Nov 30, 2017

Description

  • Reduce length of date field for external link
  • Change button text 'Save' to 'Share'
  • Change mail error text
  • Add send confirmation after sending notification

Related Issue

Fixes: #29694

How Has This Been Tested?

Visual tests in latest Chrome & Firefox

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests pass.

@felixheidecke felixheidecke added enhancement feature:sharing p2-high Escalation, on top of current planning, release blocker labels Nov 30, 2017
@felixheidecke felixheidecke added this to the development milestone Nov 30, 2017
@pmaier1 pmaier1 removed their request for review November 30, 2017 10:57
@phil-davis
Copy link
Contributor

@felixheidecke I saw that the UI tests were failing here, due to the text of the button on the UI changing to "Share". I made the change and intended to push it to a separate branch and do a PR to here - but accidentally committed it directly here.

Anyway, the latest commit here should make the UI tests pass.

@owncloud owncloud deleted a comment from codecov bot Dec 1, 2017
@felixheidecke
Copy link
Contributor Author

@phil-davis I don't mind you committing directly if it helps the PR pass :-)

Copy link
Member

@DeepDiver1975 DeepDiver1975 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please squash commits to reasonable units - THX

@@ -314,7 +311,7 @@
var self = this;
var title = t('files_sharing', 'Edit link share: {name}', {name: this.itemModel.getFileInfo().getFullPath()});
var buttons = [{
text: t('core', 'Save'),
text: t('core', 'Share'),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does "Share" also make sense when editing a link ? I'd rather have "Save" on edit and "Share" a creation time

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, good point!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@felixheidecke felixheidecke force-pushed the public-link-share-cleanup branch 2 times, most recently from 505f118 to 90b08dc Compare December 13, 2017 09:37
@owncloud owncloud deleted a comment from codecov bot Dec 13, 2017
@felixheidecke
Copy link
Contributor Author

please squash commits to reasonable units - THX

@DeepDiver1975 doesn't "Squash and merge" do this in one go?

@codecov
Copy link

codecov bot commented Dec 13, 2017

Codecov Report

Merging #29721 into master will increase coverage by 2.08%.
The diff coverage is 0%.

Impacted file tree graph

@@             Coverage Diff              @@
##             master   #29721      +/-   ##
============================================
+ Coverage     60.52%   62.61%   +2.08%     
+ Complexity    18380    17589     -791     
============================================
  Files          1090     1038      -52     
  Lines         60949    57930    -3019     
============================================
- Hits          36888    36271     -617     
+ Misses        24061    21659    -2402
Impacted Files Coverage Δ Complexity Δ
core/ajax/share.php 0% <0%> (ø) 0 <0> (ø) ⬇️
apps/dav/lib/Files/FilesHome.php 0% <0%> (-100%) 4% <0%> (-8%)
lib/private/Template/Base.php 71.11% <0%> (-2.48%) 13% <0%> (-4%)
lib/private/L10N/Factory.php 92.98% <0%> (-2.48%) 63% <0%> (-3%)
lib/private/legacy/app.php 58.33% <0%> (-1.16%) 202% <0%> (+5%)
lib/private/Route/Route.php 74.41% <0%> (-1.14%) 14% <0%> (ø)
apps/dav/lib/Server.php 48.33% <0%> (-0.85%) 11% <0%> (-1%)
lib/private/legacy/template.php 43.94% <0%> (-0.71%) 38% <0%> (-1%)
lib/private/Server.php 82.18% <0%> (-0.46%) 128% <0%> (ø)
lib/private/User/Manager.php 75.75% <0%> (-0.27%) 59% <0%> (-1%)
... and 61 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 25ba394...bbd325d. Read the comment docs.

@phil-davis
Copy link
Contributor

@felixheidecke "Squash and Merge" squashes everything into a single commit. It has been disabled on this repo, because (for generating release notes changelog etc...) the ordinary "Merge pull request" is useful. It makes a "merge commit" on top of the "real" commit(s). That merge commit has a reference back to the PR and makes automated extraction of changes back to PRs easier. (my understanding at least)

@davitol
Copy link
Contributor

davitol commented Dec 14, 2017

@pmaier1 @felixheidecke

In the ticket related #29694 it is said:

Adapt password and expiration date fields to a reasonable length
Currently these fields use the whole width of the modal. Just give them a reasonable length to make it look better (e.g. the date field always has the same width). For consistency I suggest to make the length of the two fields equal.

but with this PR we get this:

screen shot 2017-12-14 at 09 53 21

@davitol
Copy link
Contributor

davitol commented Dec 14, 2017

@pmaier1 @felixheidecke
Show "Sending"/"E-Mail sent" indicator longer and maybe turn green upon success
Currently the modal disappears in, say, 0,1 seconds after clicking the button so users have a hard time to see if the action was successful or not (I guess there is no "unsuccessful" but users should be able to take note of the success). Please increase the time the modal is shown after success to a reasonable value, e.g. 1-2 sec.

The solution given is a pop up that appears after sending the email

screen shot 2017-12-14 at 10 38 24

@pmaier1
Copy link
Contributor

pmaier1 commented Dec 14, 2017

For consistency I suggest to make the length of the two fields equal.

Hmm, please adapt..

The solution given is a pop up that appears after sending the email

From #29694:

Please increase the time the modal is shown after success to a reasonable value, e.g. 1-2 sec.

@davitol
Copy link
Contributor

davitol commented Dec 14, 2017

  • ❌ Adapt password and expiration date fields to a reasonable length
    Currently these fields use the whole width of the modal. Just give them a reasonable length to make it look better (e.g. the date field always has the same width). For consistency I suggest to make the length of the two fields equal.

  • Rename the "Save" button to "Share"
    This is to better reflect that the share and notifications effectively are created when the button is used.

  • Rename error message when invalid mail addresses are entered
    => "Could not send mail to the following recipient(s)"
    This is to better differentiate between external recipients and internal users

  • ❌ Show "Sending"/"E-Mail sent" indicator longer and maybe turn green upon success
    Currently the modal disappears in, say, 0,1 seconds after clicking the button so users have a hard time to see if the action was successful or not (I guess there is no "unsuccessful" but users should be able to take note of the success). Please increase the time the modal is shown after success to a reasonable value, e.g. 1-2 sec.

Tested in Firefox, Chrome, Safari, Edge and IE11 browsers

@felixheidecke
Copy link
Contributor Author

modal

As seen in the screenshot … the wording is rather inconsistent. I'm sure there are no guidelines on wording for forms; @pmaier1 pls find the right words for title and placeholder so I can choose a length.
Also, this length can differ in other languages … so giving a bit more space is recommended.

@felixheidecke
Copy link
Contributor Author

… maybe turn green …

While "solutions" are made up on the spot and case by case, we keep creating an inconsistent user experience. Nowhere in ownCloud, we have this type of UI feedback so I wouldn't recommend it introducing it here.

While I am currently working on bringing UIKit into the game and creating a unified and consistent UI/UX, I suggest sticking to the separate "notification was sent to xyz" for now.

@pmaier1
Copy link
Contributor

pmaier1 commented Dec 14, 2017

@pmaier1 pls find the right words for title and placeholder

Suggestion

Password
Choose a password.

Expiration date
Choose an expiration date.

and align text field length

Also, this length can differ in other languages … so giving a bit more space is recommended.

Good point!

While "solutions" are made up on the spot and case by case, we keep creating an inconsistent user experience. Nowhere in ownCloud, we have this type of UI feedback so I wouldn't recommend it introducing it here.

Turning green was just an idea. What's required here is just that the modal stays visible a bit longer. It already says something like "sent" or similar.

Change button text 'Save' to 'Share'
Change mail error text
Add send confirmation after sending notification
defer link creation upon failing email notification
Modify UI tests for Public Link dialog Share button
Show button text "share" if creating a new share
@felixheidecke felixheidecke deleted the public-link-share-cleanup branch December 20, 2017 15:07
@lock
Copy link

lock bot commented Aug 1, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
2 - Developing enhancement feature:sharing p2-high Escalation, on top of current planning, release blocker
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Public link share UI cleanup
7 participants