-
Notifications
You must be signed in to change notification settings - Fork 3k
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-06-21] [$1000] Dev: Only description's text has reduced opacity when it's disabled #19232
Comments
Triggered auto assignment to @johncschuster ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.task header description's text has reduced opacity when it's disabled. What is the root cause of that problem?After make the task mark as done, we disable the item to disable edit it, But we use different style for item disabled here. App/src/components/MenuItem.js Line 72 in 2090c05
the disable style work for task description, but not work for task title because title has additional prop shouldShowHeaderTitle which override disabled text color.
What changes do you think we should make in order to solve the problem?Solution Aset <MenuItemWithTopDescription
title={lodashGet(props.report, 'description', '')}
description="Description"
onPress={() => Navigation.navigate(ROUTES.getTaskReportDescriptionRoute(props.report.reportID))}
disabled={!isOpen}
titleStyle={styles.colorHeading} // <<<<<<<<< add this prop
/> Solution Badd prop What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issue.Only description's text has reduced opacity when it's disabled What is the root cause of that problem?It is caused by adding this line which overrides the above styles What changes do you think we should make in order to solve the problem?We should move it to the top of "disabled styles" like below which will resolve the issue. styles.popoverMenuText,
props.icon ? styles.ml3 : undefined,
props.shouldShowBasicTitle ? undefined : styles.textStrong,
props.shouldShowHeaderTitle ? styles.textHeadlineH1 : undefined,
props.interactive && props.disabled ? {...styles.disabledText, ...styles.userSelectNone} : undefined,
styles.pre,
styles.ltr,
isDeleted ? styles.offlineFeedback.deleted : undefined, As per the new requirements, we now have two options for Task header MenuItems :- 1. No reduced opacity and default cursorTo get this, we just need to use Code <MenuItemWithTopDescription
shouldShowHeaderTitle
title={props.report.reportName}
description={props.translate('newTaskPage.task')}
onPress={() => Navigation.navigate(ROUTES.getTaskReportTitleRoute(props.report.reportID))}
interactive={isOpen}
/>
<MenuItemWithTopDescription
title={lodashGet(props.report, 'description', '')}
description={props.translate('newTaskPage.description')}
onPress={() => Navigation.navigate(ROUTES.getTaskReportDescriptionRoute(props.report.reportID))}
interactive={isOpen}
/> Resultinteractive.mp42. No reduced opacity and not-allowed cursorTo get this, we need to use both Code <MenuItemWithTopDescription
shouldShowHeaderTitle
title={props.report.reportName}
description={props.translate('newTaskPage.task')}
onPress={() => Navigation.navigate(ROUTES.getTaskReportTitleRoute(props.report.reportID))}
interactive={isOpen}
disabled={!isOpen}
/>
<MenuItemWithTopDescription
title={lodashGet(props.report, 'description', '')}
description={props.translate('newTaskPage.description')}
onPress={() => Navigation.navigate(ROUTES.getTaskReportDescriptionRoute(props.report.reportID))}
interactive={isOpen}
disabled={!isOpen}
/> Resultdisabled.mp4 |
I don't think this is a bug. (Asking in Slack) |
@johncschuster Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@johncschuster Eep! 4 days overdue now. Issues have feelings too... |
@johncschuster Still overdue 6 days?! Let's take care of this! |
Triggered auto assignment to @Gonals ( |
@johncschuster @Gonals this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@johncschuster, @Gonals Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@Gonals do any of the above proposals look good to you? |
I think @aman-atg proposal looks a bit cleaner, but how come we don't have a C+ on this issue, @johncschuster? |
Oh geez. Cuz I forgot to click the |
Job added to Upwork: https://www.upwork.com/jobs/~015756347dcee86389 |
Current assignee @johncschuster is eligible for the External assigner, not assigning anyone new. |
📣 @aman-atg You have been assigned to this job by @Gonals! |
PR is ready @sobitneupane. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.27-7 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-06-21. 🎊 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.
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:
|
@sobitneupane Can you complete the BZ Checklist when you get a moment? |
@aman-atg / @sobitneupane can you apply to the Upwork job above? Thanks! |
NVM – I've invited you both! |
@johncschuster I have accepted the offer, thank you! |
I think this is resulted by change in design rather than a bug. So, it couldn't have caught earlier. |
Regression Test Proposal
Do we agree 👍 or 👎 |
Regression test issue created^ |
Payment has been issued! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
The values of both the description and title should be displayed with reduced opacity.
Actual Result :
Only description's text has reduced opacity
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: Main branch
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
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
Screen.Recording.2023-05-16.at.11.52.01.PM.1.mov
Expensify/Expensify Issue URL:
Issue reported by: @aman-atg
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684262325244699
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: