Skip to content

Conversation

@tshradheya
Copy link
Contributor

Description

Fixes #1195

Outline of Soultion

  • Made submit button always enabled. Before it was disabled when title was empty and it wasn't intuitive to user as to what is happening on click when title is empty
  • Whenever the submit button is clicked with title empty a toast is shown as in screenshot

Screenshots showing what changed

whatsapp image 2018-02-26 at 2 17 59 pm

@codecov-io
Copy link

Codecov Report

Merging #1211 into master will decrease coverage by <.01%.
The diff coverage is 0%.

Impacted file tree graph

@@            Coverage Diff            @@
##           master   #1211      +/-   ##
=========================================
- Coverage    3.82%   3.82%   -0.01%     
=========================================
  Files         125     125              
  Lines        5810    5811       +1     
  Branches      568     567       -1     
=========================================
  Hits          222     222              
- Misses       5573    5574       +1     
  Partials       15      15
Impacted Files Coverage Δ
.../free/nrw/commons/upload/SingleUploadFragment.java 0% <0%> (ø) ⬆️

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 215c97e...6a05231. Read the comment docs.

@tshradheya
Copy link
Contributor Author

@neslihanturan Could you review this as you have reviewed my PR's before?

@neslihanturan
Copy link
Collaborator

@tshradheya currently it works exactly as intended.
Giving disabled design to send button is also an approach. Currently it is meaningless because it looks same when it is disabled or enabled. I think this approach is more expected and familiar. What do you think?

And what everyone else think? If any one agrees with the strategy implemented here, I will merge.

@tshradheya
Copy link
Contributor Author

While trying to find a solution to this, initially I was unaware that the button was disabled cause it looked exactly the same to me. This is not very good for users cause they can still press the button but see no response.

I feel the current solution is better cause

  1. The button is always enabled so it always responds
  2. Giving a toast makes the instruction clear

@maskaravivek
Copy link
Contributor

We can probably have this fix for now and maybe take up the enabled/disabled design later.

@tshradheya
Copy link
Contributor Author

@maskaravivek @neslihanturan Any update on this?

@tshradheya
Copy link
Contributor Author

Sorry for bothering.
This PR is ready for review :)

@maskaravivek
Copy link
Contributor

maskaravivek commented Mar 3, 2018

LGTM. @tshradheya Sorry for the delay in reviewing your diff.

Hope you understand that we are also just volunteers and we do it in the free time. Moreover recently the project has been getting a lot of attention, so there's a lot of things to take care of. :)

@maskaravivek maskaravivek merged commit 4c3513b into commons-app:master Mar 3, 2018
@misaochan
Copy link
Member

Sorry for the late comment, but "Please give a Title to proceed" feels slightly off to me. Perhaps "Please provide a title for this file" (without the capital T) might be better?

@neslihanturan
Copy link
Collaborator

Should we revert @misaochan ?

@tshradheya
Copy link
Contributor Author

I will just create another PR to quickly fix the message

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants