-
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
Android/mWeb - Emoji - When selecting emoji via compose box the screen (keyboard) flickers #27789
Comments
Triggered auto assignment to @garrettmknight ( |
Bug0 Triage Checklist (Main S/O)
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @bondydaa ( |
In Production another behavior Screen_Recording_20230919_141045_New.Expensify.mp4 |
This issue is related to this PR |
thanks for that context @s-alves10 🙇 moving the deploy blocker and closing this as it seems like expected behavior now with the new auto-focus. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
When you select an emoji via Compose Box, the emoji should appear in the input line without any visual defects in the form of keyboard "flickering" or similar.
Actual Result:
When selecting emoji via Compose Box the screen (keyboard) flickers.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.71-5
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Bug6206193_Record_Emoji_flicker_Androidmp4.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: