-
-
Notifications
You must be signed in to change notification settings - Fork 672
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
TT: buttons logic with long text #3307
Conversation
3c840e3
to
a4415c3
Compare
Looks good. 👌🏻👌🏻👌🏻 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code-wise LGTM. I have some small nits, but they are not so important
(maybe also please include [no changelog]
into the first commit, so the changelog checks are green)
d6c97b1
to
aa6574e
Compare
ea9a4d6
to
94aeeca
Compare
Is here any change that is related to Suite? e.g. change of the message sent to Suite… |
No, should not affect Suite at all. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it makes a lot more sense with Root
👍
3aff84f
to
795648a
Compare
795648a
to
0c0a6c3
Compare
QA OK Info:
|
Fixes #2902, fixes #2888.
As
SwipePage
evolved it accumulated some features that are currently not used, mainly the ability to use anything as the control elements on the last page. Except hold-to-confirm button, which had to useSwipeHoldPage
component instead. By hardcoding a pair of buttons and merging the hold-to-confirm logic the code is somewhat simplified, also I've renamed it toButtonPage
as swiping is not what most users will do.UI diff | differing screens
Note: the following screen is in the UI diff a lot because the width of the left button changed from 53 to 56 as is in Figma.
Also changes hold-to-confirm to draw loader over the screen title, fixes #3000.