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

Purchases: Domain cancellation: confirm button enabled before user co… #784

Merged
merged 1 commit into from
Nov 26, 2015

Conversation

gziolo
Copy link
Member

@gziolo gziolo commented Nov 25, 2015

…nfirmed understanding terms

Fixes #726.

When cancelling a domain, if I select "The service isn't what I expected" / "I meant to get a free blog" / "Something not listed here" in the Confirm Cancellation screen, the Cancel Domain button is enabled right away.

It should only be enabled once the user has checked "I understand that canceling means that I may lose this domain forever".

Testing

  1. Go to http://calypso.localhost:3000/purchases.
  2. Select domain purchased in last 48h.
  3. Go to Cancel and Refund page.
  4. Go to Confirm Cancel Purchase page.
  5. Submit button should only be enabled once the user has checked "I understand that canceling means that I may lose this domain forever".

Note: When you send one request to Cancel Domain Purchase mail is sent. When you go again to Cancel Confirmation page the following message is displayed:
This upgrade cannot be cancelled.

Testing

  • Code review
  • QA review

/cc @fabianapsimoes

@gziolo gziolo added [Type] Bug When a feature is broken and / or not performing as intended [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. [Feature] Purchase Management Related to managing purchases such as subscriptions, plans, history, auto-renew, cancellation, etc. labels Nov 25, 2015
@gziolo gziolo self-assigned this Nov 25, 2015
@gziolo gziolo added this to the Purchases: v1 milestone Nov 25, 2015
@drewblaisdell
Copy link
Contributor

QA and code 👍 I used this a lot while testing cancelations.

} );
} );
form.addEventListener( 'submit', ( event ) => {
event.preventDefault();
Copy link
Contributor

Choose a reason for hiding this comment

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

Not directly related to this issue, but should we disable the submit button after it is clicked once?

Copy link
Member Author

Choose a reason for hiding this comment

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

@fabianapsimoes do you think we should implement it in v1? It sounds like a nice UX improvement. In v2 we should rather replace this whole Confirm Cancellation page with rewritten version based on design's team prototype.

gziolo added a commit that referenced this pull request Nov 26, 2015
…d-by-default

Purchases: Domain cancellation: confirm button enabled before user co…
@gziolo gziolo merged commit 83278c1 into master Nov 26, 2015
@gziolo gziolo removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Nov 26, 2015
@gziolo gziolo deleted the fix/726-submit-button-disabled-by-default branch November 26, 2015 06:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Purchase Management Related to managing purchases such as subscriptions, plans, history, auto-renew, cancellation, etc. [Type] Bug When a feature is broken and / or not performing as intended
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants