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

Would you kindly replace 2nd confirm with exit module button ~ Marie #530

Open
WenSnake opened this issue May 9, 2016 · 5 comments
Open

Comments

@WenSnake
Copy link

WenSnake commented May 9, 2016

After you submit something, the checkmark button tries to submit the thing again instead of closing the window. So then it gives you a pop-up saying "you just submitted this, error" or something. Really awkward UI there.

There's only a "cancel" and the "confirm" button after submitting the changes, which makes it rather redundant and a little confusing. Once submitted, the confirm button should be an exit button or it should just close automatically.

~ From SaberMarie

@AlMcKinlay
Copy link
Contributor

I think we agreed this would be best to have the modals close after they finish updating.

Although, we still don't see where the bug came from, as submitting a link is not a modal.

@AlMcKinlay
Copy link
Contributor

So, this came up again, from the flair submission modal (From Marie)

I really don't like Marie's solution of turning the submit button into a close button, as changing what a button does is also really confusing.

However, I have 2 suggestions:

  1. Change "cancel" button to "close" (because it should be clear, with the submit button that the close button doesn't submit), and it makes it more clear what to do once we have submitted the first time. Then just disable the submit button after success until the modal is closed
  2. Close the modal after success, and use a toast notification to let the user know of success instead.

Thoughts, guys? I would be happy with either of these suggestions.

Once we've got gen 7 and a bit of legality done on porybox, I'd like to come back to flairhq for a bit to get some of these niggles sorted.

@TheSonAlsoRises
Copy link
Contributor

Option 1 is probably the most logical.

@Raia
Copy link
Member

Raia commented Jan 9, 2017

I need more context on this. What is the "something" we are submitting?

@AlMcKinlay
Copy link
Contributor

I need more context on this. What is the "something" we are submitting?

So, specifically it is flair text. There might be others, but I don't think there are.

@AlMcKinlay AlMcKinlay removed the next label Jun 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants