-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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-31] [$250] Chat - Composer goes to the top on pressing expand @thesahindia #11437
Comments
Triggered auto assignment to @laurenreidexpensify ( |
ProposalIt is happening because the ReportActionCompose is wrapped by OfflineWithFeedback App/src/pages/home/ReportScreen.js Lines 290 to 296 in b058975
To solve it we need to use style.h100 for the View at 90 and 92 App/src/components/OfflineWithFeedback.js Lines 90 to 94 in b058975
|
Triggered auto assignment to @amyevans ( |
Reproducible, releasing to |
Current assignee @laurenreidexpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Triggered auto assignment to @Beamanator ( |
Not overdue, reviewing this morning |
Yep ^ @rushatgabhane would you mind reviewing the one proposal in this issue today? |
@Puneet-here It is no longer the case in |
@Beamanator apologies for the delay, im 100% back now |
ProposalRCA: App/src/pages/home/report/ReportFooter.js Lines 89 to 103 in eb26cc4
This happens because when composer expanded, the parent view ( OfflineWithFeedback ) doesn't stretch to full height so this.props.isComposerFullSize && styles.chatItemFullComposeRow in ReportActionCompose container style isn't applied so it doesn't stretch to full height.
Solution: <OfflineWithFeedback
pendingAction={this.props.addWorkspaceRoomPendingAction}
+ style={this.props.isComposerFullSize && styles.chatItemFullComposeRow}
+ contentContainerStyle={this.props.isComposerFullSize && styles.flex1}
>
<ReportActionCompose
onSubmit={this.props.onSubmitComment}
reportID={this.props.report.reportID.toString()}
reportActions={this.props.reportActions}
report={this.props.report}
isComposerFullSize={this.props.isComposerFullSize}
/>
</OfflineWithFeedback> And in https://github.com/Expensify/App/blob/main/src/components/OfflineWithFeedback.js, <View style={props.style}>
{!hideChildren && (
- <View style={needsOpacity ? styles.offlineFeedback.pending : {}}>
+ <View style={[needsOpacity ? styles.offlineFeedback.pending : {}, props.contentContainerStyle]}>
{children}
</View>
)} |
@aimane-chnaif's proposal is too similar to @Puneet-here's proposal. And @Puneet-here most likely would have submitted an updated proposal same as @aimane-chnaif's proposal |
@Beamanator I think we should hire @Puneet-here because they were first. C+ reviewed 🎀 👀 🎀 |
Makes sense to me @rushatgabhane |
This comment was marked as outdated.
This comment was marked as outdated.
@Puneet-here's proposal didn't explain that those styles needed only when composer expanded ( |
Agree with @aimane-chnaif, @Beamanator sorry for the back and forth but I think we should hire @aimane-chnaif |
Ooh thanks for bringing that up @aimane-chnaif , this one is tough since the proposal are both small, but I agree with @rushatgabhane let's change up who was hired 👍 |
📣 @aimane-chnaif You have been assigned to this job by @Beamanator! |
Thanks @rushatgabhane @Beamanator |
PR under review, should be merged soon 👍 |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.18-10 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-31. 🎊 |
Payments:
@rushatgabhane @aimane-chnaif as soon as you've accepted job in Upwork I will issue payment. Thanks |
Everyone has been 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:
The composer should expand and shouldn't move
Actual Result:
The composer goes to the top
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.9.0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): any
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screenrecording_20220926_182030.mp4
Expensify/Expensify Issue URL:
Issue reported by: @thesahindia
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1664196729312989
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: