-
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 2022-10-05] [$250] IOS - Chat - User get highlighted in grey when message is sent #11227
Comments
Triggered auto assignment to @neil-marcellini ( |
Yeah that's odd. Sending external. |
Triggered auto assignment to @arielgreen ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Triggered auto assignment to @luacmartins ( |
ProposalRoot cause App/src/pages/home/sidebar/SidebarLinks.js Line 165 in b75faf0
It's already implemented on the App/src/components/OptionsList/BaseOptionsList.js Lines 176 to 177 in b75faf0
Solution diff --git a/src/components/LHNOptionsList/LHNOptionsList.js b/src/components/LHNOptionsList/LHNOptionsList.js
index 941057579..1b39dc546 100644
--- a/src/components/LHNOptionsList/LHNOptionsList.js
+++ b/src/components/LHNOptionsList/LHNOptionsList.js
@@ -26,6 +26,9 @@ const propTypes = {
/** Callback to execute when the SectionList lays out */
onLayout: PropTypes.func.isRequired,
+
+ /** Disable focus options */
+ disableFocusOptions: PropTypes.bool,
};
class LHNOptionsList extends Component {
@@ -69,7 +72,7 @@ class LHNOptionsList extends Component {
<OptionRowLHN
reportID={item}
viewMode={this.props.optionMode}
- isFocused={this.props.focusedIndex === index}
+ isFocused={!this.props.disableFocusOptions && this.props.focusedIndex === index}
onSelectRow={this.props.onSelectRow}
/>
);
@@ -100,5 +103,8 @@ class LHNOptionsList extends Component {
}
LHNOptionsList.propTypes = propTypes;
+LHNOptionsList.defaultProps = {
+ disableFocusOptions: false,
+};
export default LHNOptionsList; Result Screen.Recording.2022-09-24.at.23.55.40.mov |
ProposalisFocused is being used to know which option is focused and we apply styles to the focused option. We want this functionality to work for LHN at big screens but not for small screens. We can use withWindowDimensions to know the screen width and we can just check if it's a small screen width device Replace this line 72 with isFocused={!this.props.isSmallScreenWidth && this.props.focusedIndex === index}
This way we won't see the highlighted row in the mobiles |
@luacmartins I like @mollfpr's proposal.
App/src/pages/home/sidebar/SidebarLinks.js Line 146 in e33cfb3
🎀 👀 🎀 C+ reviewed |
@mollfpr your proposal looks good. Assigning you to the issue! |
📣 @mollfpr You have been assigned to this job by @luacmartins! |
@luacmartins @rushatgabhane PR raised! |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.8-0 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 2022-10-05. 🎊 |
Issue not reproducible during KI retests. (First week) |
@mollfpr @rushatgabhane sent Upwork invite, please accept and I will remit payment |
@arielgreen Accepted, thank you! |
Paid. |
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:
User should not get highlighted in grey when message is sent
Actual Result:
User get highlighted in grey when message is sent
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.5.0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): applausetester+09162022abb@applause.expensifail.com / Feya86Katya
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Bug5744747_RPReplay_Final1663886502.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: