-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
fix: spacing on report typing indicator #10790
fix: spacing on report typing indicator #10790
Conversation
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.
@parasharrajat This is not just android thing but also other platforms. I had figured it out before, but I did not report it then. There is a margin of 5px in bottom of the composer. Lines 1374 to 1376 in 85172f7
-marginBottom: 5, This will fix the issue. Should we commit it here? |
I don't know why we have a bottom margin here. @shawnborton Could you please take a look and suggest us? Thank you. |
I'm afraid I have no time to test this myself, but you should be able Android Studio to determine the exact margin/padding that is used natively. Build a dev build and use the |
Thanks, @Julesssss. I already tested it and as @mdneyazahmad suggested there is an applied bottom margin by us. I am just curious to see the design impact of this. Before we remove it, it should be good to take confirmation from design team. |
@mdneyazahmad Please merge main to fix the tests. |
@parasharrajat merged main |
@parasharrajat this screenshot here looks perfect to me: I agree though that the bottom margin should be removed, not sure why/how that got there. |
Thanks, @shawnborton. the text has little extra space below it due to the margin otherwise, this is good. @mdneyazahmad Please remove the margin and share the screenshots for android and web of
|
Bump @mdneyazahmad |
@mdneyazahmad Did you remove the margin? |
@parasharrajat your recent screenshot looks different from the one above... vs. The second screenshot is correct - there should be just a little bit of margin above the typing/offline indicator. |
Yeah, the first screenshot is an issue but not in the scope of this PR. That is a global offline indicator. Fixed my comment(mistype 😄) |
Hmm but both the global offline indicator and the typing indicator should take up the exact same space right? So they do seem related to me. |
Yeah, they should. But this PR's issue was only talking about typing indicator which covers all the indicators of the composer. The global offline indicator resides in different parts of the code. But it can be done on this PR if @mdneyazahmad is up for it. |
Yeah, I think we should not treat the styling of them as separate personally. Basically the exact space where the typing indicator shows up is also the exact space where the global offline indicator would show up as well, so we should make sure they are congruent. |
So the screenshots look good to me, but I just tested the original bug again on the latest version of the app, and the bug is no longer happening. So before we merge these changes, do you know what might have happened? |
Co-authored-by: Rajat Parashar <parasharrajat@users.noreply.github.com>
8315f26
Strange, let me test. |
@mdneyazahmad Can you please confirm if the original issue is not more reproducible on the main? I can't reproduce. If that is the case, let's revert all the changes for alignment and only remove the margin bottom. |
@parasharrajat I had pointed this earlier #10790 (comment). This issue is fixed here. Should we continue with the refactor, or remove the change made here? |
If that is the case, let's revert all the changes for alignment and only remove the margin-bottom. |
Updated! This PR now addresses a completely different issue than the linked PR. |
That's not an issue. At least our effort didn't go wasted. |
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.
LGTM. Based on the latest discussion, we reverted the code and just fixed the margin.
cc: @Julesssss
Just want to confirm that the screenshots have been updated in the original comment? |
Ah, that wasn't clear to me in that message. But thanks for clarifying The latest edits to the description seem to show the most recent changes only, but @mdneyazahmad could you please confirm before I merge? Thanks |
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.
Reviewer Checklist
|
Stupid check. I'm ignoring this as I clearly filled the reviewer checklist. |
See this, it is not an emergency. |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by @Julesssss in version: 1.2.19-0 🚀
|
🚀 Deployed to production by @chiragsalian in version: 1.2.19-2 🚀
|
Details
Fixed Issues
$ #10486
PROPOSAL: #10486 (comment)
Tests
QA Steps
PR Review Checklist
PR Author Checklist
### Fixed Issues
section aboveTests
sectionQA steps
sectiontoggleReport
and notonIconClick
)src/languages/*
filesWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed
### Fixed Issues
section aboveTests
sectionQA steps
sectiontoggleReport
and notonIconClick
).src/languages/*
filesWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
have been tested & I retested again)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)Screenshots
Web
web.mp4
Mobile Web - Chrome
mweb-chrome.mp4
Mobile Web - Safari
mweb-safari.mp4
Desktop
desktop.mp4
iOS
ios.mp4
Android
android.mp4