Repository navigation
[$250] Web -Search - Grouped expenses row is still slightly grayed out after unselecting the expenses #45078
Description
Activity
- addedDeployBlockerCashThis issue or pull request should block deploymentThis issue or pull request should block deploymentDailyKSv2KSv2BugSomething is broken. Auto assigns a BugZero manager.Something is broken. Auto assigns a BugZero manager.DeployBlockerIndicates it should block deploying the APIIndicates it should block deploying the API
on Jul 9, 2024 Triggered auto assignment to @sonialiap (
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.Triggered auto assignment to @stitesExpensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.👋 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:
- Identify the pull request that introduced this issue and revert it.
- Find someone who can quickly fix the issue.
- Fix the issue yourself.
@stitesExpensify 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
We think that this bug might be related to #vip-vsb
Proposal
Please re-state the problem that we are trying to solve in this issue.
Grouped expenses row is still slightly grayed out after unselecting the expenses
What is the root cause of that problem?
App/src/components/Pressable/PressableWithFeedback.tsx
Lines 51 to 56 in 6e5a966
<OpacityView shouldDim={!!(!rest.disabled && (isPressed || isHovered))} dimmingValue={isPressed ? pressDimmingValue : hoverDimmingValue} style={wrapperStyle} needsOffscreenAlphaCompositing={needsOffscreenAlphaCompositing} > On
PressableWithFeedbackwe set thedimmingValuewith thepressDimValueif pressed, the defaultpressDimValueis 0.8, so it set the opacity to 0.8And we don't set
pressDimmingValuehereWhat changes do you think we should make in order to solve the problem?
set
pressDimmingValue={1}here so it wont greyed out after clickWhat alternative solutions did you explore? (Optional)
20 remaining items
Current assignee @stitesExpensify is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new.
- removedHelp WantedApply this label when an issue is open to proposals by contributorsApply this label when an issue is open to proposals by contributors
on Jul 17, 2024 📣 @dominictb 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖- addedReviewingHas a PR in reviewHas a PR in reviewWeeklyKSv2KSv2and removedDailyKSv2KSv2
on Jul 18, 2024 Issue not reproducible during KI retests. (First week)
@sonialiap I think the automation is not working here, the PR already hit production on the 25th of July. Could you give me the payment summary? Thank you!
[@mollfpr] The PR that introduced the bug has been identified. Link to the PR:
[@mollfpr] 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:No offending PR. It's a pretty rare case and hard to notice.
[@mollfpr] 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:
The regression step should be enough.
[@mollfpr] Determine if we should create a regression test for this bug.
[@mollfpr] 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.- Go to NewDot
- Go to Search.
- Go to Shared.
- Click on the select all checkbox of the group expenses (not the select all checkbox for all types of expenses, it's the checkbox for the grouped expenses).
- Click on the select all checkbox again to unselect.
- Move the cursor outside the grouped expenses.
- Verify that the row will not be grayed out.
- 👍 or 👎
Reacted by Sonia LiapounovaPayment summary:
- @mollfpr $250 - please request in ND
- @dominictb $250 - paid in upwork
$250 approved for @mollfpr
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.5-4
Reproducible in staging?: y
Reproducible in production?: no
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 team
Slack conversation:
Action Performed:
Precondition:
Expected Result:
In Step 7, after unselecting the grouped expenses, the row will not be grayed out.
Actual Result:
In Step 7, after unselecting the grouped expenses, the row is slightly grayed out.
The grayness is gone after clicking on the empty area (Step 9).
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6536029_1720454461384.Screen_Recording_2024-07-08_at_23.34.51.mov
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mollfpr