-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Composer - Suggestion list is above the composer when typing @ in multiline text #50373
Comments
Triggered auto assignment to @garrettmknight ( |
Triggered auto assignment to @lakchote ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
Found the blocker it's #41071 cc @eVoloshchak @stitesExpensify @dukenv0307 can you fix this timely or should we revert? |
Checking this now. |
For the first bug, we deiced to not display the suggestion overlap the composer [here]
Created a PR for the second bug |
@dukenv0307 are you fixing this in a different PR somewhere? |
@garrettmknight My PR is reverted, so this issue is fixed. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.46-1
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): applausetester+kh051001@applause.expensifail.com
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
The suggestion modal should appear above @ or :sm when the composer has multiline text.
Actual Result:
The suggestion modal is above the composer instead of above @ or :sm when the composer has multiline text.
On mweb, Android and iOS app, there is big space between the composer and the modal.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6627974_1728363620860.suggestion.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: