-
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
[$250] Web - Chat - When editing last message, edition composer is cut in half by main composer #49787
Comments
Triggered auto assignment to @VictoriaExpensify ( |
@VictoriaExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
ProposalPlease re-state the problem that we are trying to solve in this issue.Web - Chat - When editing last message, edition composer is cutted in half by main composer What is the root cause of that problem?We are currently using the built-in View component from React Native here. App/src/pages/home/report/ReportActionItemMessageEdit.tsx Lines 499 to 552 in b9f8b86
What changes do you think we should make in order to solve the problem?We should use ScrollView to ensure proper scrolling behaviour.
What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issue.When the user edits the last message on a chat with long history, the edition composer, gets cutted in half by the main compose box What is the root cause of that problem?We already had the logic to focus on the edit composer in
Even though, we use
When the input is focus, the view automatically scrolls to that input, but we need to wait for composer edit animation end before focusing on the input. We did the same in many places, especially in What changes do you think we should make in order to solve the problem?Update this line to
What alternative solutions did you explore? (Optional)We can delay focus in ResultScreen.Recording.2024-09-26.at.22.45.30.mov |
I haven't had a chance to look at this yet, will take a look tomorrow |
@MuaazArshad - were you able to reproduce this? |
asking for a re-test https://expensify.slack.com/archives/C9YU7BX5M/p1727935116718019 |
Yes, and still reproducible. Screen.Recording.2024-10-03.at.5.41.24.PM.mov |
Able to reproduce screen-20241004-104821.mp4 |
Job added to Upwork: https://www.upwork.com/jobs/~021843415078855833463 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 ( |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@abdulrahuman5196, @VictoriaExpensify Huh... This is 4 days overdue. Who can take care of this? |
ProposalPlease re-state the problem that we are trying to solve in this issue.When editing the last message in the web chat, the edition composer is cut in half by the main composer. What is the root cause of that problem?When we press edit, the offset position of scroll is not perfectly pointed to the reportAction item, since the I can consistently reproduce the issue with the following step
What changes do you think we should make in order to solve the problem?To ensure proper offset position while editing, scroll to the start of the edited report action when it's the last report action. It may be necessary to remove Modify this App/src/pages/home/report/ReportActionItem.tsx Lines 267 to 273 in db592c9
To useEffect(() => {
if (prevDraftMessage !== undefined || draftMessage === undefined) {
return;
}
if(index === 0)
{
InteractionManager.runAfterInteractions(() => {
requestAnimationFrame(() => {
reportScrollManager.scrollToIndex(index);
});
})
}
focusComposerWithDelay(textInputRef.current)(true);
}, [prevDraftMessage, draftMessage]); Ensure proper scrolling functionality by using Result -- Before(left) - After(Right) Kapture.2024-10-29.at.13.23.51.mp4What alternative solutions did you explore? (Optional)N/A |
@abdulrahuman5196 you might find the answer in my proposal #49787 (comment) |
I haven't been able to reproduce the issue. Applying the retest label |
@VictoriaExpensify can you test with this reproduction steps?
Reproduction video and result can be seen here #49787 (comment) |
Able to reproduce using the provided steps. Screen.Recording.2024-10-30.at.6.08.24.PM.mov |
@abdulrahuman5196, @VictoriaExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@abdulrahuman5196, @VictoriaExpensify 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@abdulrahuman5196, @VictoriaExpensify 12 days overdue. Walking. Toward. The. Light... |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@abdulrahuman5196, @VictoriaExpensify 12 days overdue. Walking. Toward. The. Light... |
Yup, this is reproducible following the steps given. Let's move forward here |
Hi, I am still unable to repro the issue. I reached out in C+ channel to see if any one is able to repro this and takeover. |
I was able to reproduce. Will post a video shortly as well. |
Was able to reproduce: Screen.Recording.2024-11-14.at.3.25.31.AM.mov |
@VictoriaExpensify Can you please assign this to me? |
@VictoriaExpensify Kindly assign this issue to @allroundexperts for takeover. Unassigned myself. |
@VictoriaExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.40-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5006320&group_by=cases:section_id&group_order=asc&group_id=292106
Issue reported by: Applause - Internal Team
Action Performed:
3.Right click on the last sent message
Expected Result:
When editing the last sent message on a chat, the edition composer, should be fully visible
Actual Result:
When the user edits the last message on a chat with long history, the edition composer, gets cutted in half by the main compose box
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6615545_1727314558189.Cut_compose.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @abdulrahuman5196The text was updated successfully, but these errors were encountered: