-
Notifications
You must be signed in to change notification settings - Fork 988
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
chats 1-1 reviews #17253
chats 1-1 reviews #17253
Conversation
Jenkins BuildsClick to see older builds (104)
|
fa8a9b7
to
9ff10bf
Compare
@@ -48,7 +48,7 @@ | |||
[theme window-height sheet-height {:keys [top]}] | |||
{:position :absolute | |||
:bottom 10 | |||
:max-height (- window-height sheet-height top) | |||
:max-height (- window-height sheet-height top 10) |
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.
I think this 10
need to be applied for Android only
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.
I checked with iOS and it seems necessary too to achieve the same design
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.
Also looks a bit like a magic number. Maybe some constant needs to be introduced or at least some explanation?
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.
Also looks a bit like a magic number. Maybe some constant needs to be introduced or at least some explanation?
@alwx I have added a comment on the code to explain how we arrive at that value. The selected item can only have a max-height of the remaining part of the screen not occupied by the bottom-sheet. We arrive at getting by: window-height
minus (bottom-sheet-height
+ (:top insets)
+ margin-bottom
). We minus the margin-bottom
as its part of the height not occupied by the bottom-sheet
(- window-height sheet-height top bottom-margin)
@@ -48,7 +48,7 @@ | |||
[theme window-height sheet-height {:keys [top]}] | |||
{:position :absolute | |||
:bottom 10 | |||
:max-height (- window-height sheet-height top) | |||
:max-height (- window-height sheet-height top 10) |
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.
Also looks a bit like a magic number. Maybe some constant needs to be introduced or at least some explanation?
5d198a2
to
780d097
Compare
:bottom 10 | ||
:max-height (- window-height sheet-height top) | ||
:bottom 8 | ||
;; we minus 8 on the max-height since the bottom has a margin of 8 |
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.
How about using a variable for bottom
instead of hardcoding 8
in both spots? This way, we won't need this comment, and it'll keep our UI safe in case we tweak bottom
down the road.
cff06f2
to
e9523ce
Compare
3c0adff
to
6590d50
Compare
67% of end-end tests have passed
Failed tests (14)Click to expandClass TestCommunityOneDeviceMerged:
Class TestCommunityMultipleDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestActivityCenterContactRequestMultipleDevicePR:
Passed tests (29)Click to expandClass TestCommunityOneDeviceMerged:
Class TestActivityMultipleDevicePRTwo:
Class TestCommunityMultipleDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestActivityMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestActivityCenterContactRequestMultipleDevicePR:
|
Thanx for the PR @jo-mut. I have checked the PR and frankly speaking I was not able to see any difference compared to nightly in terms of described areas of fixes. Let's ask @Francesca-G for review. |
@pavloburykh we're currently working on the 1.25 build review and we have a lot of comments for 1-1 chats. That should be all ready by Monday, so should we wait for that big review to be ready or does it make sense to review this now? :) |
Thank you @Francesca-G! This PR provides some fixes based on previous feedback (1.24 release review). So I would appreciate if you provide feedback on this PR exclusively in terms of these issues [#17252], [#17251], [#17250], [#17249] Based on 1.25 review we will create new umbrella issues which will be fixed in separate PRs. Thank you! |
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.
Thank you @Francesca-G! |
54ff783
to
0b68cc4
Compare
@Francesca-G @pavloburykh I have addressed the design feedback on the margins. Take a look. Thank you |
Once @Francesca-G approves the fix PR is ready for merge @jo-mut |
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.
Here's the review :)
Please refer to review 2.
0b68cc4
to
79fb829
Compare
@Francesca-G thanks for these comments. I have addressed them if you could have another look just to confirm |
73407ba
to
f60db7a
Compare
f60db7a
to
ef9ac02
Compare
ef9ac02
to
9d02e62
Compare
fixes [#17252], [#17251], [#17250], [#17249]