Implement XS breakpoint of transaction component - Close #80 #160
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
ginacontrino
force-pushed
the
80-transaction-xs-breakpoint
branch
from
80e8be2
to
539e8f1
Compare
ginacontrino
force-pushed
the
80-transaction-xs-breakpoint
branch
from
539e8f1
to
a074f5c
Compare
ginacontrino
force-pushed
the
80-transaction-xs-breakpoint
branch
from
1a9a27f
to
3599fe5
Compare
slaweet
changed the title
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.
What was the problem?
XS breakpoint needed to be implemented
How can I test it?
In order to log in on mobile (with custom node) it's probably the best to just hardcode passphrase, address and network into your state in the login component, so everything is prefilled (it's impossible to fill out the network form on mobile anyway bc the forms conflict)
and make sure the login button is not disabled.
Review checklist