Skip to content

[HOLD for payment 2023-07-24] [$1000] The "No results found" message in the emoji picker is scrollable #22504

Closed

Description

@kavimuru

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Login to ND
  2. Go to any chat
  3. Open emoji picker
  4. Type "tt" in the search input
  5. Try to scroll "No results found" message

Expected Result:

The "No results found" message should remain fixed in its position

Actual Result:

The "No results found" message is scrollable

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

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

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.38-2
Reproducible in staging?: y
Reproducible in production?: y
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

RPReplay_Final1688818788.mov
DFNN4026.MP4

Expensify/Expensify Issue URL:
Issue reported by: @aman-atg
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688824480134429

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01e4d1df988507fb8b
  • Upwork Job ID: 1678462833490141184
  • Last Price Increase: 2023-07-10

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 9, 2023
  2. melvin-bot commented on Jul 9, 2023

    @melvin-bot

    Triggered auto assignment to @lschurr (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. melvin-bot commented on Jul 9, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. GItGudRatio commented on Jul 9, 2023

    @GItGudRatio
    Contributor

    Proposal

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

    We can notice that on iOS, the text "No results found" is scrollable, when it should not be.

    What is the root cause of that problem?

    This is a native issue with iOS and the way iOS handles scrolling within containers by calculating the available space for scrolling content. When using the ListEmptyComponent in React Native, it is rendered within the same container as the list itself. If the list is empty and the ListEmptyComponent has content that exceeds the available height of the container, iOS may consider it as scrollable content and enable scrolling behaviour.

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

    In order to fix this problem, we can add the prop scrollEnabled={this.state.filteredEmojis.length !== 0} to the FlatList in EmojiPickerMenu for native devices.

    What alternative solutions did you explore? (Optional)

    N/A

  5. bernhardoj commented on Jul 9, 2023

    @bernhardoj
    Contributor

    Proposal

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

    We can "scroll" the Not found text in emoji picker.

    What is the root cause of that problem?

    The not found text is a ListEmptyComponent that is part of the list (FlatList). It's a normal behavior of a FlatList in iOS to be able to scroll a bit more (I think this is called bounces in RN) even if it reaches the edge of the list.

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

    Set alwaysBounceVertical to false.

    This prop will allow to bounce only if the list items are scrollable. So, if the text no found is shown, bounce is deactivated, but when the emoji list is shown (and scrollable), it will be activated back.

  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jul 10, 2023
  7. changed the title [-]The "No results found" message in the emoji picker is scrollable[/-] [+][$1000] The "No results found" message in the emoji picker is scrollable[/+] on Jul 10, 2023
  8. melvin-bot commented on Jul 10, 2023

    @melvin-bot
  9. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jul 10, 2023
  10. melvin-bot commented on Jul 10, 2023

    @melvin-bot

    Current assignee @lschurr is eligible for the External assigner, not assigning anyone new.

  11. melvin-bot commented on Jul 10, 2023

    @melvin-bot

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

  12. sobitneupane commented on Jul 11, 2023

    @sobitneupane
    Contributor

    Thanks everyone for the proposal.

    Rather than a bug, it can be considered as polish. I am okay with the present state where "No results found" bounces/scrolls. But If we want to polish it,
    Proposal from @bernhardoj looks good to me.

    🎀 👀 🎀 C+ reviewed

    Update: #22504 (comment)

  13. 29 remaining items

  14. lschurr commented on Jul 24, 2023

    @lschurr
    Contributor

    PR up on July 11th at 12:32pm PT
    Merged July 13th at 7:03am PT

    Qualifies for bonus.

  15. lschurr commented on Jul 24, 2023

    @lschurr
    Contributor

    @sobitneupane - do we need a regression test for this one?

  16. lschurr commented on Jul 24, 2023

    @lschurr
    Contributor

    Also @sobitneupane - could you accept the offer in Upwork?

    And @aman-atg could you apply?

    https://www.upwork.com/jobs/~01e4d1df988507fb8b

  17. sobitneupane commented on Jul 24, 2023

    @sobitneupane
    Contributor

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@sobitneupane] The PR that introduced the bug has been identified. Link to the PR:

    #18221

    • [@sobitneupane] 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:

    #18221 (comment)

    • [@sobitneupane] A discussion in #expensify-bugs 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:

    This is an edge case. I don't think any udpate on the PR review checklist is required.

    • [@sobitneupane] Determine if we should create a regression test for this bug.

    Yes.

    • [@sobitneupane] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

    #22504 (comment)

  18. sobitneupane commented on Jul 24, 2023

    @sobitneupane
    Contributor

    Regression Test Proposal

    1. Login to newDot.
    2. Navigate to any chat.
    3. Click on the Emoji button in the composer.
    4. Enter some random text. Verify that the "No results found" is not scrollable/bouncing.

    Do we agree 👍 or 👎

  19. sobitneupane commented on Jul 24, 2023

    @sobitneupane
    Contributor

    @lschurr Payment Requested on newDot.

  20. aman-atg commented on Jul 24, 2023

    @aman-atg
    Contributor

    @lschurr I've applied to the job, thanks!

  21. lschurr commented on Jul 24, 2023

    @lschurr
    Contributor

    Offer sent @aman-atg

  22. lschurr commented on Jul 25, 2023

    @lschurr
    Contributor

    Bump @aman-atg - could you accept the offer in Upwork?

  23. aman-atg commented on Jul 25, 2023

    @aman-atg
    Contributor

    @lschurr Sorry for the delay, I've now accepted the offer

  24. lschurr commented on Jul 25, 2023

    @lschurr
    Contributor

    All set. Closing this one out.

  25. JmillsExpensify commented on Jul 27, 2023

    @JmillsExpensify
    Contributor

    Reviewed details for @sobitneupane. This pay of $1500 (base + urgency bonus) is accurate based on comment from Business Reviewer and approved for payment in NewDot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions