-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2023-10-05] [$500] Web - Overlay background colour is different #27353
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @dangrous ( |
This is from @rushatgabhane @adamgrzybowski but i dont think this is a blocker |
This is a regression of this PR, but it looks by intention |
Yeah it seems intentional, in order to fix #26405 @shawnborton can you give this a quick look to confirm what color for the overlay is expected here? You had looked at the PR, too, but not sure if your approval included the color, or just the size issue that was being fixed. Thank you! |
removing the label, shouldn't block deploy and will sync with Shawn once he's in working hours |
Chatting in Slack but yeah, I think we messed up and the overlay color is now incorrect. We should standardize on the correct color and update it everywhere. I'm thinking maybe using our colors.highLightBG color @ 72% opacity. Which would be |
Totally agree @shawnborton. Let's make it happen. 🚀 |
ProposalProblemOverlay background colour is different Root CauseNo root cause, just a color change ChangesWe need to change |
@ishpaul777 forgive me if this is a dumb comment/if I'm misunderstanding something, but the hex code Our Just want to make sure we don't inadvertently update this to be wrong. Again, please forgive me if I am just not understanding something. 🙈 |
Hii @dannymcclain, You are right here, thanks for correcting it was dumb mistake I made. Updated the Proposal. |
I'm gonna add the Bug label to this so we can peruse external proposals! Shawn and Danny - it looks like from the Slack conversation that we're going to likely want different opacities depending on the theme. Should we add that as a separate theme variable, or include it in a specific separate color variable for the overlay in the theme? |
Triggered auto assignment to @laurenreidexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
@grgia can you provide guidance on how we should handle adding a new color variable for the modal overlay BG to both dark and light themes? Or do we just get the new dark theme value merged here and we'll deal with light mode separately? |
We could use a helper function to set the rgba for a hex in FE. I think I've seen that pattern in app for some of these overlays. As part of this issue, we should make sure that all overlays in App reference the same variable/method |
This has nothing to do with darkHighlightBackground, so no need to touch that. |
📣 @s77rt 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @ishpaul777 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
📣 @Krishna2323 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app! |
Assigned! Let's make sure any values that we update live inside the themes! |
🎯 ⚡️ Woah @s77rt / @ishpaul777, great job pushing this forwards! ⚡️ The pull request got merged within 3 working days of assignment, so this job is eligible for a 50% #urgency bonus 🎉
On to the next one 🚀 |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.74-3 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 2023-10-05. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
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:
|
|
Yeah this was not a bug that would have been caught by any process I don't think - we should be good! Mostly just a bit of a misunderstanding comboed with changing design |
Payment Summary:
|
@laurenreidexpensify The payment here should be $250 as the PR caused a regression no bonus is applicable and the total is subject to -50%. I have refunded $500 |
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:
Expected Result:
The overlay should be same as the newdot.
Actual Result:
The overlay is different from the newdot.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.69.0
Reproducible in staging?: y
Reproducible in production?: n
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
Monosnap.screencast.2023-09-13.19-08-29.mp4
Recording.4437.mp4
Expensify/Expensify Issue URL:
Issue reported by: @Krishna2323
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694612443986939
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: