Skip to content

Start chat - Keyboard-selected item background and hover background are the same #51975

Closed

Description

@lanitochka17

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.57-0
Reproducible in staging?: Y
Reproducible in production?: N
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
Email or phone of affected tester (no customers): applausetester+kh22100010ad@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to FAB > Start chat
  3. Navigate through the list via keyboard
  4. Hover over another member

Expected Result:

The selected item background and hover background will be different (production behavior)

Actual Result:

The selected item background and hover background are the same

Workaround:

Unknown

Platforms:

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

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6654534_1730741553460.20241105_013114.mp4

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Nov 4, 2024

    @melvin-bot

    Triggered auto assignment to @dangrous (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  2. melvin-bot commented on Nov 4, 2024

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  3. github-actions commented on Nov 4, 2024

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  4. nkdengineer commented on Nov 4, 2024

    @nkdengineer
    Contributor

    It's the new expected behavior.

  5. dangrous commented on Nov 4, 2024

    @dangrous
    Contributor

    yep, this is expected from #50779 - cc @Expensify/design

    I'm going to close but if anyone disagrees let me know

  6. shawnborton commented on Nov 5, 2024

    @shawnborton
    Contributor

    Yup, indeed that is intentional. Don't know where the blue outlines went though but I think that's a separate thing maybe?

  7. dangrous commented on Nov 5, 2024

    @dangrous
    Contributor

    yeah I think the blue outlines have been coming and going periodically... I believe it's being handled elsewhere? @nkdengineer do you happen to know?

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions