Skip to content

[HOLD for payment 2023-12-26] [$1000] mWeb - Composer - Unnecessary blank area is created when scrolling down while keyboard is open #19642

Closed

Description

@kbecciv

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:

  1. Open the testing link https://staging.new.expensify.com/
  2. Open any chat
  3. Write multiline text in the composer until the enlarge composer icon appear (keep the keyboard open)
  4. Tap on the maximize composer icon
  5. 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:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

https://platform.applause.com/services/links/v1/external/8e4abb883a4188a43758f0561fbfd5c7900892adaded42ecb9fb365ac7c0b0a3

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01302d5f678fb0c5f7
  • Upwork Job ID: 1662142490327298048
  • Last Price Increase: 2023-05-26
  • Automatic offers:
    • suneox | Contributor | 28039355

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 26, 2023
  2. melvin-bot commented on May 26, 2023

    @melvin-bot

    Triggered auto assignment to @abekkala (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. melvin-bot commented on May 26, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on May 26, 2023
  5. 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
  6. melvin-bot commented on May 26, 2023

    @melvin-bot
  7. melvin-bot commented on May 26, 2023

    @melvin-bot

    Current assignee @abekkala is eligible for the External assigner, not assigning anyone new.

  8. melvin-bot commented on May 26, 2023

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel (External)

  9. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on May 26, 2023
  10. melvin-bot commented on May 26, 2023

    @melvin-bot

    Triggered auto assignment to @thienlnam (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

  11. 152 remaining items

  12. JmillsExpensify commented on Dec 27, 2023

    @JmillsExpensify
    Contributor

    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:

  13. suneox commented on Dec 28, 2023

    @suneox
    Contributor

    Hi @JmillsExpensify
    I have received an offer 1000$ but currently is 500$ so have we got any mistake or update?

  14. JmillsExpensify commented on Dec 29, 2023

    @JmillsExpensify
    Contributor

    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?

  15. suneox commented on Dec 30, 2023

    @suneox
    Contributor

    I have a bit confuse for the job title it still 1000$, so how can contributor get to know the actual payment? Thanks

  16. suneox commented on Jan 2, 2024

    @suneox
    Contributor

    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

  17. thienlnam commented on Jan 2, 2024

    @thienlnam
    Contributor

    @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

  18. JmillsExpensify commented on Jan 3, 2024

    @JmillsExpensify
    Contributor

    Cool, I'm not incredibly passionate. Updated the payment summary above.

  19. JmillsExpensify commented on Jan 3, 2024

    @JmillsExpensify
    Contributor

    Contributor has been paid out and regression created. @parasharrajat Please submit a request via Expensify and we'll get your paid.

  20. suneox commented on Jan 3, 2024

    @suneox
    Contributor

    Thank @thienlnam @JmillsExpensify @parasharrajat I have received the payment.

  21. parasharrajat commented on Apr 1, 2024

    @parasharrajat
    Member

    Payment requested as per #19642 (comment)

  22. JmillsExpensify commented on Apr 3, 2024

    @JmillsExpensify
    Contributor

    @laurenreidexpensify Do you mind confirming the payment summary on this issue before I approve payment?

  23. laurenreidexpensify commented on Apr 3, 2024

    @laurenreidexpensify
    Contributor

    Payment Summary:

    $1000 Contributor - @suneox payment issued in Upwork
    $1000 C+ - @parasharrajat requested in newdot

  24. JmillsExpensify commented on Apr 3, 2024

    @JmillsExpensify
    Contributor

    $1,000 approved for @parasharrajat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions