-
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
[$250] Room - Page does not scroll to bottom when send message in #expensify-roadmap public room #52208
Comments
Triggered auto assignment to @sonialiap ( |
Job added to Upwork: https://www.upwork.com/jobs/~021855979378378206243 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @akinwale ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Page does not scroll to bottom of the conversation in #expensify-roadmap public room What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?The What alternative solutions did you explore? (Optional)NA |
ProposalPlease re-state the problem that we are trying to solve in this issue.Room - Page does not scroll to bottom when send message in #expensify-roadmap public room What is the root cause of that problem?We are calling the What changes do you think we should make in order to solve the problem?We need to wrap this block into the App/src/pages/home/report/ReportActionsList.tsx Lines 417 to 429 in b2d6a0e
So this below is the working block;
What alternative solutions did you explore? (Optional)N/A Contributor detailsYour Expensify account email: anasup1995@gmail.com |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
@Anaslancer Could you post a video demo of your proposed solution? |
@akinwale Here is the before video before.mp4 |
@akinwale Here is the after video after.mp4 |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@akinwale, @sonialiap Eep! 4 days overdue now. Issues have feelings too... |
@akinwale what do you think of the videos showing the proposal? |
I will review and test this today. |
We can move forward with @Anaslancer's proposal here. 🎀👀🎀 C+ reviewed. |
Triggered auto assignment to @aldo-expensify, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@akinwale @sonialiap @aldo-expensify this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
📣 @Anaslancer You have been assigned to this job! |
Applied on Upwork. Thank you!!! |
May I create a PR now? |
Yes, you have been assigned to the issue, so you can go ahead. |
Waiting on: #52955 (review) |
Current assignee @sonialiap is eligible for the Bug assigner, not assigning anyone new. |
I'm OOO Dec 16-20, adding a leave buddy next steps:
|
Triggered auto assignment to @twisterdotcom ( |
👋 it looks like this issue might be a regression from the PR for this fix. @aldo-expensify / @akinwale can you have a look? |
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.59-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
)
Expected Result:
Page should scroll to the bottom when send new message
Actual Result:
Page does not scroll to bottom of the conversation
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6657900_1731001767296.Recording__4488.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @akinwaleThe text was updated successfully, but these errors were encountered: