More info about UX around app recommendation and selection; network failures #140
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added some explicit mention of scenarios per 16 June payment app task force call.
ianbjacobs
changed the title
|
LGTM @ianbjacobs - I think we need to go through the doc and put all of the questions and todos inside blocks with the class |
|
I am happy to go through the spec and markup up questions with class=""issue". Can we do the merge and I'll attack that tomorrow? Ian |
| <ol> | ||
| <li>User has no registered payment apps.</li> | ||
| <li>User has apps with supported but no enabled payment methods.</li> | ||
| <li>User has apps with supported but no enabled payment methods.</li> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added some explicit mention of scenarios per 16 June payment app task
force call.