-
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
[$1000] mWeb Android - Not able to create multiline description #22284
Comments
Triggered auto assignment to @muttmuure ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.mWeb Android - Not able to create multiline description What is the root cause of that problem?Root cause is the This prop causes this behavior as when user presses enter for a new line in description, it rather submits the current form App/src/pages/tasks/TaskDescriptionPage.js Lines 67 to 77 in f08ab19
What changes do you think we should make in order to solve the problem?We need to remove the submitOnEnter prop from here
and also other two pages: As per the new discussion here #21205 (comment) , we are going to keep submitOnEnter and we have decided to opt for an android specific fix. So since we the issue is only present in mobile web versions, we can disable submitOnEnter on those fields specifically submitOnEnter={!Browser.isMobile()} Browser.isMobile() will return true only for mobile web versions where we are unable to enter multiline description ResultsScreenrecorder-2023-07-06-11-38-38-854.mp4What alternative solutions did you explore? (Optional) |
@muttmuure Eep! 4 days overdue now. Issues have feelings too... |
BUMP @muttmuure |
Lots of high priorities. Getting to this tomorrow |
Still not had time |
Seeing this as fixed 2023-07-17_16-44-25.mp4Maybe we caught it somewhere else? |
@aimane-chnaif did we push a fix for android for this? |
@muttmuure bug is for the mweb |
#21664 is for money request description, not task. |
I'm also seeing this as fixed on Android Chrome. Am I holding it wrong here? 2023-07-19_13-10-00.mp4 |
@muttmuure still able to reproduce with real device |
@muttmuure 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! |
@muttmuure Eep! 4 days overdue now. Issues have feelings too... |
Catching up from ooo |
📣 @mananjadhav Please request via NewDot manual requests for the Reviewer role ($1000) |
📣 @chiragxarora 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
All yours @chiragxarora ! |
PR is ready for review @mananjadhav |
@chiragxarora I commented on the PR for missing screenshots. |
🎯 ⚡️ Woah @mananjadhav / @chiragxarora, 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 🚀 |
This was deployed to production 2 days back, but the title wasn't updated. |
@muttmuure Can you post the payout summary here? This has been in production for 7 days but the title wasn't updated. |
@muttmuure i didn't get any upwork offer automatically, can you send offer manually |
I would call this as small polish/feature request. We linked the other issue, and the comment says it was expected change. I also don't think we need a regression test here. |
@muttmuure quick bump. |
Waiting on payment summary for NewDot payment. |
Reporter - @gadhiyamanan $250 |
I don't think I received the offer @muttmuure |
offer sent! |
@muttmuure i didn't get any offer |
Sent one to you too @gadhiyamanan |
@muttmuure offer accepted, thanks! |
All paid up |
$1,500 payment approved for @mananjadhav based on BZ summary above. |
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:
Should add new line same app
Actual Result:
Not able to add new line
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: 1.3.34-1
Reproducible in staging?: y
Reproducible in production?: y
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_20230702_224836_Chrome.1.mp4
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688318894783959
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: