You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2023-12-26] [$1000] mWeb - Composer - Unnecessary blank area is created when scrolling down while keyboard is open #19642
Write multiline text in the composer until the enlarge composer icon appear (keep the keyboard open)
Tap on the maximize composer icon
Above the keyboard, scroll down
Expected Result:
The bottom of the screen should stick to the bottom of the input composer, and no extra blank area should be created when the user scrolls down on the screen
Actual Result:
When scrolling down while the composer is maximized, an excessively wide area is created below the composer, resulting in continuous resizing of the composer when scrolling both upward and downward
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android / native
Android / Chrome
iOS / native
iOS / Safari
MacOS / Chrome / Safari
MacOS / Desktop
Version Number: 1.3.18.0
Reproducible in staging?: yes
Reproducible in production?: Yes - but the composer does not keep resizing, only the blank area is presented
If this was caught during regression testing, add the test name, ID and link from TestRail:
changed the title [-]mWeb - Composer - Unnecessary blank area is created when scrolling down while keyboard is open[/-][+][$1000] mWeb - Composer - Unnecessary blank area is created when scrolling down while keyboard is open[/+]on May 26, 2023
Hmmm, I'm a bit confused where we're at on payment. It looks like the original contributor's PR was reverted, so that leaves us with @suneox who was assigned more recently. That payment summary would be:
I think it's incorrect automated logic on our side. Given that you were assigned a couple of weeks ago, I think the $500 offer is correct and I can pay that amount on payout. Do you agree?
Hi @JmillsExpensify
I also found another issue that has paid match with the title at this comment and the bonus program is also available for this comment, so I think this issue also applies to the payment matching with the title
@JmillsExpensify This bug is very old and has retained the $1000 price tag. I think since this issue predates all our pricing changes we should just pay this one out at the original price
Activity
melvin-bot commentedon May 26, 2023
Triggered auto assignment to @abekkala (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon May 26, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)[-]mWeb - Composer - Unnecessary blank area is created when scrolling down while keyboard is open[/-][+][$1000] mWeb - Composer - Unnecessary blank area is created when scrolling down while keyboard is open[/+]melvin-bot commentedon May 26, 2023
Job added to Upwork: https://www.upwork.com/jobs/~01302d5f678fb0c5f7
melvin-bot commentedon May 26, 2023
Current assignee @abekkala is eligible for the External assigner, not assigning anyone new.
melvin-bot commentedon May 26, 2023
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel (
External)melvin-bot commentedon May 26, 2023
Triggered auto assignment to @thienlnam (
External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.152 remaining items
JmillsExpensify commentedon Dec 27, 2023
Hmmm, I'm a bit confused where we're at on payment. It looks like the original contributor's PR was reverted, so that leaves us with @suneox who was assigned more recently. That payment summary would be:
suneox commentedon Dec 28, 2023
Hi @JmillsExpensify
I have received an offer 1000$ but currently is 500$ so have we got any mistake or update?
JmillsExpensify commentedon Dec 29, 2023
I think it's incorrect automated logic on our side. Given that you were assigned a couple of weeks ago, I think the $500 offer is correct and I can pay that amount on payout. Do you agree?
suneox commentedon Dec 30, 2023
I have a bit confuse for the job title it still 1000$, so how can contributor get to know the actual payment? Thanks
suneox commentedon Jan 2, 2024
Hi @JmillsExpensify
I also found another issue that has paid match with the title at this comment and the bonus program is also available for this comment, so I think this issue also applies to the payment matching with the title
and this comment
thienlnam commentedon Jan 2, 2024
@JmillsExpensify This bug is very old and has retained the $1000 price tag. I think since this issue predates all our pricing changes we should just pay this one out at the original price
JmillsExpensify commentedon Jan 3, 2024
Cool, I'm not incredibly passionate. Updated the payment summary above.
JmillsExpensify commentedon Jan 3, 2024
Contributor has been paid out and regression created. @parasharrajat Please submit a request via Expensify and we'll get your paid.
suneox commentedon Jan 3, 2024
Thank @thienlnam @JmillsExpensify @parasharrajat I have received the payment.
parasharrajat commentedon Apr 1, 2024
Payment requested as per #19642 (comment)
JmillsExpensify commentedon Apr 3, 2024
@laurenreidexpensify Do you mind confirming the payment summary on this issue before I approve payment?
laurenreidexpensify commentedon Apr 3, 2024
Payment Summary:
$1000 Contributor - @suneox payment issued in Upwork
$1000 C+ - @parasharrajat requested in newdot
JmillsExpensify commentedon Apr 3, 2024
$1,000 approved for @parasharrajat