Repository navigation
Web - Search - Group expense box is not highlighted evenly when selected by keyboard #51784
Description
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.56-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: applausetester+kh2310001@applause.expensifail.com
Issue reported by: Applause - Internal Team
Action Performed:
- Go to staging.new.expensify.com
- Submit two expenses to any user
- Go to Search
- Go to Outstanding
- Navigate to the group expenses in Step 2 using keyboard
- Click on the empty area to remove the blue border
Expected Result:
The group expense box will be highlighted evenly
Actual Result:
The top and bottom of the group expense box have different shade than the middle of the box
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
Activity
github-actions commentedon Oct 31, 2024
👋 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:
melvin-bot commentedon Oct 31, 2024
Triggered auto assignment to @iwiznia (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 31, 2024
💬 A slack conversation has been started in #expensify-open-source
Nodebrute commentedon Oct 31, 2024
Regression from #51158
jjcoffee commentedon Oct 31, 2024
@nkdengineer Can you take a look?
iwiznia commentedon Oct 31, 2024
I don't think this is a blocker, but it seems the change created a bunch of other issues and is being reverted already.
Beamanator commentedon Nov 4, 2024
Reverted in #51795 & that was checked off by applause, so seems to be fixed!
mjasikowski commentedon Nov 7, 2024
Fix was submitted in #51937
iwiznia commentedon Nov 12, 2024
The PR above was deployed