-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Typing indicator ellipses #5933
Typing indicator ellipses #5933
Conversation
src/languages/en.js
Outdated
@@ -160,7 +160,7 @@ export default { | |||
newMsg: ({count}) => `${count} new message${count > 1 ? 's' : ''}`, | |||
}, | |||
reportTypingIndicator: { | |||
isTyping: 'is typing...', | |||
isTyping: 'is typing', |
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 we should keep this as it is??
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.
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.
cc: @NikkiWines
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.
Hmmm, I think it's fine for now since is typing...
is pretty standard if there's no animation for a user typing.
src/styles/styles.js
Outdated
function getTypingIndicatorTextStyle(isSmallScreenWidth) { | ||
return isSmallScreenWidth | ||
? { | ||
maxWidth: 200, | ||
} | ||
: { | ||
maxWidth: 500, | ||
}; | ||
} | ||
|
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.
Hmm. This is supposed to be fluid. Take max available space with hiding is typing...
<Text | ||
style={[ | ||
styles.chatItemComposeSecondaryRowSubText, | ||
styles.chatItemComposeSecondaryRowOffset, | ||
getTypingIndicatorTextStyle(this.props.isSmallScreenWidth), |
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.
We will not need it. See comment below...
<Text | ||
style={[ | ||
styles.chatItemComposeSecondaryRowSubText, | ||
styles.chatItemComposeSecondaryRowOffset, | ||
styles.ml1, |
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 we should take the natural gap of 1 char
.
@parasharrajat PR updated. |
@@ -108,6 +100,7 @@ ReportTypingIndicator.displayName = 'ReportTypingIndicator'; | |||
|
|||
export default compose( | |||
withLocalize, | |||
withWindowDimensions, |
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.
Seems like unsued now.
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.
@akshayasalvi Did you test it on all platforms after the recent changes? If so, please update the screenshots.
I see that It does not work well on Android.
The name should not trim until you have consumed all the available space. In the screenshot, there is plenty of space after is typing...
So the Name will be trimmed when is Typing...
is close to the right edge where the composer ends.
Yes, you're right. I tried and it does break in Android. I've tried to fix it but it then increases the whitespace between the email and is Typing. Will check. |
Any update @akshayasalvi ? |
Tried but haven't figured a solution that ensures fluid for all cases. Still checking. |
@parasharrajat @NikkiWines I've made changes and it works fine on Android but I am not sure it doesn't work fine on the Android emulator. Attached is the screenshot from my android phone. |
I will check it later. |
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.
Couple minor comments but it's looking great
<View style={[styles.chatItemComposeSecondaryRow, styles.flexRow]}> | ||
<View style={[styles.chatItemComposeSecondaryRowOffset, styles.flexShrink1]}> | ||
<Text | ||
style={[ |
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.
this can be a single line instead
style={[styles.chatItemComposeSecondaryRowSubText]}
</Text> | ||
</View> | ||
<View style={[styles.flexShrink0]}> | ||
<Text |
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.
This can also be a single line:
<Text style={[styles.chatItemComposeSecondaryRowSubText]}>
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. Tests well. Please refer to Nikki's comments and we are good here. Thanks for the changes.
@parasharrajat @NikkiWines PR updated |
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.
👍 Looks good!!
@parasharrajat not sure if you wanted to give this another review or not. If you haven't by EOD, I'll merge 🚀 |
✋ 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 @NikkiWines in version: 1.1.12-4 🚀
|
Accessibility Issue : Incorrect focus order. Attachments : Focus.order.fails.mp4 |
Accessibility Issue : Incorrect Focus order through messages is reversed bottom-to-top. Attachments : Focus.order.fails.from.top.to.bottom.mp4 |
Accessibility Issue : "+" (plus), 'Emoji', 'Send' Buttons has wrong button role, state not announced. Similar to the bug #5677. Attachments : name.role.vale.+.button.mp4 |
🚀 Deployed to production by @yuwenmemon in version: 1.1.13-2 🚀
|
Details
Fixed Issues
$ #5623
Tests
QA Steps
is typing
word visibleMultiple users typing...
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
Android