Skip to content

[HOLD for payment 2024-01-31] [$500] Mention - Only 3 user are scrollable when use keyboard to pick user to mention #33613

Closed

Description

@kbecciv

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: 1.4.17-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:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal
Slack conversation:

Action Performed:

Precondition:
Connect the pc keyboard to mobile device
Steps:

  1. Navigate to staging.new.expensify.com
  2. Go to any chat
  3. Start texting until chat is expanded
  4. Type @ to open mention member list
  5. Use keyboard arrows to scroll through the list

Expected Result:

User should be able to navigate to all members in the list

Actual Result:

When using keyboard arrows user is able to scroll only 3 members from the list

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

Bug6326341_1703616195297.Recording__1643.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~017bdddeb3dc37e5c7
  • Upwork Job ID: 1739721691952898048
  • Last Price Increase: 2024-01-09
  • Automatic offers:
    • mkhutornyi | Contributor | 28095701

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 26, 2023
  2. changed the title [-]Mention - Only 3 user are scrollable when use keyboard to pick user to mention[/-] [+][$500] Mention - Only 3 user are scrollable when use keyboard to pick user to mention[/+] on Dec 26, 2023
  3. melvin-bot commented on Dec 26, 2023

    @melvin-bot
  4. melvin-bot commented on Dec 26, 2023

    @melvin-bot

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

  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Dec 26, 2023
  6. melvin-bot commented on Dec 26, 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
  7. melvin-bot commented on Dec 26, 2023

    @melvin-bot

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

  8. mkhutornyi commented on Dec 26, 2023

    @mkhutornyi
    Contributor

    Proposal

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

    Mention - Only 3 user are scrollable when use keyboard to pick user to mention
    This happens on emoji suggestion as well

    What is the root cause of that problem?

    function getMaxArrowIndex(numRows, isAutoSuggestionPickerLarge) {

    Here, we're getting max arrow index from 2 factors: list size and isAutoSuggestionPickerLarge
    So if isAutoSuggestionPickerLarge = false and list size > 3, this function always returns 3, ignoring list size. And this sets maxIndex of arrow focus manager to 3.

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

    arrow max index should not depend on visible size as it's scrollable
    So replace this line with maxIndex: suggestionValues.suggestedMentions.length - 1

    maxIndex: SuggestionsUtils.getMaxArrowIndex(suggestionValues.suggestedMentions.length, isAutoSuggestionPickerLarge),

    Same applies to SuggestionEmoji

  9. rrrshtt commented on Dec 26, 2023

    @rrrshtt

    Proposal

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

    Suggestions stacked in 3 items with keyboard control.

    What is the root cause of that problem?

    function getMaxArrowIndex(numRows, isAutoSuggestionPickerLarge) {

    maxIndex: SuggestionsUtils.getMaxArrowIndex(suggestionValues.suggestedMentions.length, isAutoSuggestionPickerLarge),

    The entire function getMaxArrowIndex() is incorrect for this purpose since it's a keyboard controller.

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

    We can simply use the length of suggested mentions in the keyboard controller because we only need the total number of items in the hook.

  10. melvin-bot commented on Dec 26, 2023

    @melvin-bot

    📣 @rrrshtt! 📣
    Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
    Please follow these steps:

    1. Make sure you've read and understood the contributing guidelines.
    2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
    3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  11. rrrshtt commented on Dec 26, 2023

    @rrrshtt

    Contributor details
    Your Expensify account email: mrishat03@gmail.com
    Upwork Profile Link: https://www.upwork.com/freelancers/~012f657c01285b6cf0

  12. 42 remaining items

  13. changed the title [-][$500] Mention - Only 3 user are scrollable when use keyboard to pick user to mention[/-] [+][HOLD for payment 2024-01-31] [$500] Mention - Only 3 user are scrollable when use keyboard to pick user to mention[/+] on Jan 24, 2024
  14. melvin-bot commented on Jan 24, 2024

    @melvin-bot

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

  15. melvin-bot commented on Jan 24, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.30-1 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-01-31. 🎊

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

  16. melvin-bot commented on Jan 24, 2024

    @melvin-bot

    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:

    • [@eVoloshchak] The PR that introduced the bug has been identified. Link to the PR:
    • [@eVoloshchak] 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:
    • [@eVoloshchak] 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:
    • [@eVoloshchak] Determine if we should create a regression test for this bug.
    • [@eVoloshchak] 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.
    • [@CortneyOfstad / @bfitzexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  17. CortneyOfstad commented on Jan 31, 2024

    @CortneyOfstad
    Contributor

    Payment Summary

    @mkhutornyi (Contributor) — paid $500 via Upwork
    @eVoloshchak (C+) — to be paid $500 via New Dot

  18. CortneyOfstad commented on Jan 31, 2024

    @CortneyOfstad
    Contributor

    @eVoloshchak any update on the checklist above? Thanks!

  19. CortneyOfstad commented on Feb 1, 2024

    @CortneyOfstad
    Contributor

    @eVoloshchak just bumping on the checklist so we can get this closed. Thanks!

  20. eVoloshchak commented on Feb 3, 2024

    @eVoloshchak
    Contributor
    • The PR that introduced the bug has been identified. Link to the PR: Performance: chat input #25758
    • 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/25758/files#r1477093662
    • 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: I don't think an additional discussion is needed, this is a very minor bug
    • Determine if we should create a regression test for this bug.
      Is it easy to test for this bug? No, this requires an Android device with a physical keyboard connected to test
      Is the bug related to an important user flow? No
      Is it an impactful bug? No
      We don't need a regression test here, the bug is rare and isn't impactful, and it might be hard for QA to test
  21. eVoloshchak commented on Feb 3, 2024

    @eVoloshchak
    Contributor

    Requested the payment

  22. JmillsExpensify commented on Feb 3, 2024

    @JmillsExpensify
    Contributor

    $500 approved for @eVoloshchak based on summary above.

  23. CortneyOfstad commented on Feb 5, 2024

    @CortneyOfstad
    Contributor

    Thanks all!

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