Skip to content
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

[PAID] [HOLD for payment 2024-11-29] [$250] mWeb -Finder -User not scrolled to top of chats list when scrolling down and deleting search #50562

Closed
1 of 6 tasks
lanitochka17 opened this issue Oct 10, 2024 · 57 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor

Comments

@lanitochka17
Copy link

lanitochka17 commented Oct 10, 2024

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.47-1
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/5068088&group_by=cases:section_id&group_order=asc&group_id=229066
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause - Internal Team

Action Performed:

  1. Open the staging.new.expensify.com website
  2. Log in to an account with a large list of chats
  3. Tap on the search icon on the top right corner
  4. Write a few letters to trigger some results
  5. Scroll down to the middle of the results
  6. Select all the content in the search input and delete it
  7. Verify the chats list is updated and the user is navigated to the top of it

Expected Result:

After deleting the content in search input, the chats list should be updated and the user should be navigated to the top of it

Actual Result:

When writing a few letters to trigger a search, scrolling down to the middle of the results, selecting all the content on search input and deleting it, the chats list updated but the user is not redirected to the top. The list stays in the middle

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6630312_1728534947618.Finder.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021846215092993792827
  • Upwork Job ID: 1846215092993792827
  • Last Price Increase: 2024-11-12
  • Automatic offers:
    • allgandalf | Reviewer | 104904927
    • wildan-m | Contributor | 104904928
Issue OwnerCurrent Issue Owner: @CortneyOfstad
@lanitochka17 lanitochka17 added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Oct 10, 2024
Copy link

melvin-bot bot commented Oct 10, 2024

Triggered auto assignment to @CortneyOfstad (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

@lanitochka17
Copy link
Author

@CortneyOfstad 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

@melvin-bot melvin-bot bot added the Overdue label Oct 14, 2024
@CortneyOfstad
Copy link
Contributor

Didn't realize this was Android — so having Stevie do some testing for me!

@melvin-bot melvin-bot bot removed the Overdue label Oct 15, 2024
@CortneyOfstad
Copy link
Contributor

Confirmed that this was reproducible so getting eyes on it! S/O to @slafortune for her help!

@CortneyOfstad CortneyOfstad added the External Added to denote the issue can be worked on by a contributor label Oct 15, 2024
Copy link

melvin-bot bot commented Oct 15, 2024

Job added to Upwork: https://www.upwork.com/jobs/~021846215092993792827

@melvin-bot melvin-bot bot changed the title mWeb -Finder -User not scrolled to top of chats list when scrolling down and deleting search [$250] mWeb -Finder -User not scrolled to top of chats list when scrolling down and deleting search Oct 15, 2024
@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Oct 15, 2024
Copy link

melvin-bot bot commented Oct 15, 2024

Triggered auto assignment to Contributor-plus team member for initial proposal review - @allgandalf (External)

@huult
Copy link
Contributor

huult commented Oct 15, 2024

Proposal

Please re-state the problem that we are trying to solve in this issue.

User not scrolled to top of chats list when scrolling down and deleting search

What is the root cause of that problem?

After deleting the search, scrolling to the top is not possible because newSelectedIndex returns -1 when textInputValue === '' (which occurs after the previous search is cleared).

const newSelectedIndex =
textInputValue === '' || (flattenedSections.selectedOptions.length !== prevSelectedOptionsLength && prevAllOptionsLength === flattenedSections.allOptions.length) ? -1 : 0;
// reseting the currrent page to 1 when the user types something
setCurrentPage(1);
updateAndScrollToFocusedIndex(newSelectedIndex);

The function updateAndScrollToFocusedIndex receives this -1 and passes it to scrollToIndex. Inside scrollToIndex, there's a condition that checks if the index is -1. If true, it returns without performing the scroll, causing the issue
if (!listRef.current || !item || index === -1) {
return;
}

What changes do you think we should make in order to solve the problem?

To resolve this issue, we need to check if textInputValue is empty after the search text is removed. If it is, we need to return to index === 0 to enable scrolling to the top.

// .src/components/SelectionList/BaseSelectionList.tsx#L568
- const newSelectedIndex =
-            textInputValue === '' || (flattenedSections.selectedOptions.length !== prevSelectedOptionsLength && prevAllOptionsLength === flattenedSections.allOptions.length) ? -1 : 0;
+ const newSelectedIndex =
+            (textInputValue === '' && !prevTextInputValue) || (flattenedSections.selectedOptions.length !== prevSelectedOptionsLength && prevAllOptionsLength === flattenedSections.allOptions.length) ? -1 : 0;
POC
Screen.Recording.2024-10-16.at.01.34.42.mov

I've tested the previous issue, and this condition still works well after the update

POC
Screen.Recording.2024-10-16.at.01.36.45.mp4

@CortneyOfstad CortneyOfstad removed the Bug Something is broken. Auto assigns a BugZero manager. label Oct 15, 2024
@CortneyOfstad CortneyOfstad removed their assignment Oct 15, 2024
@CortneyOfstad CortneyOfstad added the Bug Something is broken. Auto assigns a BugZero manager. label Oct 15, 2024
Copy link

melvin-bot bot commented Oct 15, 2024

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

@CortneyOfstad
Copy link
Contributor

Hey @stephanieelliott! I am heading OoO shortly (until 10/23) so reassigning to keep an eye on this! Thanks!

Copy link

melvin-bot bot commented Oct 21, 2024

@CortneyOfstad, @stephanieelliott, @allgandalf Huh... This is 4 days overdue. Who can take care of this?

@melvin-bot melvin-bot bot added the Overdue label Oct 21, 2024
@allgandalf
Copy link
Contributor

@daledah :

We can consider to use const item = flattenedSections.allOptions[index] instead of at

What do you mean by this in your alternative solution ?

@melvin-bot melvin-bot bot removed the Overdue label Oct 22, 2024
@huult
Copy link
Contributor

huult commented Oct 22, 2024

@allgandalf Could you please review my proposal? My solution simplifies the process by updating the condition to check if the index is 0 after the text search is cleared.

@Kicu
Copy link
Contributor

Kicu commented Nov 20, 2024

FYI @allgandalf @rlinoz I see the video on this issue is presenting old ChatFinder functionality, but the code of ChatFinder is completely removed from App as of a few weeks. Probably when this issue was created, then ChatFinder was still in the code, but in end the final solution landed in SearchRouter (which had a similar problem).

As I'm refactoring SearchRouter right now (need it to behave a bit different) then I will simplify this code because the ref is completely unnecessary.

The previous value of query is right there in textInputValue, so a simple
if (updatedUserQuery || textInputValue.length > 0) {
is enough.

Just FYI - I have no idea if the isEmptyObject inside BaseSelectionList is needed or not, but I won't be touching it.
Here's the PR where SearchRouter is changing: #52568

CC @luacmartins just so you know

@luacmartins luacmartins changed the title [$250] mWeb -Finder -User not scrolled to top of chats list when scrolling down and deleting search [HOLD #52568][$250] mWeb -Finder -User not scrolled to top of chats list when scrolling down and deleting search Nov 20, 2024
@luacmartins luacmartins changed the title [HOLD #52568][$250] mWeb -Finder -User not scrolled to top of chats list when scrolling down and deleting search [$250] mWeb -Finder -User not scrolled to top of chats list when scrolling down and deleting search Nov 20, 2024
@luacmartins
Copy link
Contributor

Thanks @Kicu! I see that the PR for this issue is already merged. I think we can make changes to the solution if needed though.

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Nov 20, 2024
@Kicu
Copy link
Contributor

Kicu commented Nov 21, 2024

solution changed here: https://github.com/Expensify/App/pull/52568/files#diff-f8e8e46965e7e099296f3ec791faf7d61b208fb68dfff52e20e8d98483479a89R225

I included an android video showing that the bug is still fixed on my code

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Nov 22, 2024
@melvin-bot melvin-bot bot changed the title [$250] mWeb -Finder -User not scrolled to top of chats list when scrolling down and deleting search [HOLD for payment 2024-11-29] [$250] mWeb -Finder -User not scrolled to top of chats list when scrolling down and deleting search Nov 22, 2024
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Nov 22, 2024
Copy link

melvin-bot bot commented Nov 22, 2024

Reviewing label has been removed, please complete the "BugZero Checklist".

Copy link

melvin-bot bot commented Nov 22, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.65-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

If no regressions arise, payment will be issued on 2024-11-29. 🎊

For reference, here are some details about the assignees on this issue:

Copy link

melvin-bot bot commented Nov 22, 2024

@allgandalf @CortneyOfstad @allgandalf The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

@CortneyOfstad
Copy link
Contributor

@allgandalf can you please complete the checklist at your earliest convenience?

@CortneyOfstad
Copy link
Contributor

Please note that I am going to be OoO on 11/29 due to Thanksgiving in the US, but I will get this paid as soon as I am back on Monday. Most of the team will be out, so I apologize for the delay!

@allgandalf
Copy link
Contributor

No worries @CortneyOfstad , Hope you enjoy your time off 😄

@allgandalf
Copy link
Contributor

allgandalf commented Nov 28, 2024

BugZero Checklist:

  • [Contributor] Classify the bug:
Bug classification

Source of bug:

  • 1a. Result of the original design (eg. a case wasn't considered)
  • 1b. Mistake during implementation
  • 1c. Backend bug
  • 1z. Other:

Where bug was reported:

  • 2a. Reported on production
  • 2b. Reported on staging (deploy blocker)
  • 2c. Reported on both staging and production
  • 2d. Reported on a PR
  • 2z. Other:

Who reported the bug:

  • 3a. Expensify user
  • 3b. Expensify employee
  • 3c. Contributor
  • 3d. QA
  • 3z. Other:
  • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

    Link to comment: https://github.com/Expensify/App/pull/44222/files#r1861582359

  • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

    Link to discussion: N/A

  • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

  • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

    Link to issue: https://github.com/Expensify/Expensify/issues/449517

Regression Test Proposal

Precondition:

  • Account with large list of chats (For the scroll behaviour to exist)

Test:

  1. Open App > Tap on the search icon on the top right corner
  2. Write a few letters to trigger some results
  3. Scroll down to the middle of the results
  4. Select all the content in the search input and delete it

Verify the chats list is updated and the user is navigated to the top of it

Do we agree 👍 or 👎

Copy link

melvin-bot bot commented Dec 2, 2024

@rlinoz, @CortneyOfstad, @wildan-m, @allgandalf Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@CortneyOfstad
Copy link
Contributor

Payment Summary

@wildan-m — paid $250 via Upwork
@allgandalf — paid $250 via Upwork

Regression Test

https://github.com/Expensify/Expensify/issues/449517

@github-project-automation github-project-automation bot moved this from Bugs and Follow Up Issues to Done in [#whatsnext] #expense Dec 2, 2024
@melvin-bot melvin-bot bot removed the Overdue label Dec 2, 2024
@CortneyOfstad CortneyOfstad changed the title [HOLD for payment 2024-11-29] [$250] mWeb -Finder -User not scrolled to top of chats list when scrolling down and deleting search [PAID] [HOLD for payment 2024-11-29] [$250] mWeb -Finder -User not scrolled to top of chats list when scrolling down and deleting search Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor
Projects
Status: Done
Development

No branches or pull requests

10 participants