Skip to content

[Due for payment 2025-07-04] [$250] Report Content Pushes Composer Slightly Out of View During Loading #64312

Closed

Description

@m-natarajan

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
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
Expensify/Expensify Issue URL:
Issue reported by: @shawnborton
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

  1. Navigate to Reports > Reports
  2. Open a report that takes a moment to load
  3. Observe the layout during the loading phase.

Expected Result:

The composer area should remain fixed and fully visible while the report loads.

Actual Result:

The loading content causes layout shift, pushing the composer partially or fully out of view.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Image

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021935033820143099096
  • Upwork Job ID: 1935033820143099096
  • Last Price Increase: 2025-07-05
Issue OwnerCurrent Issue Owner: @garrettmknight

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on Jun 17, 2025
  2. melvin-bot commented on Jun 17, 2025

    @melvin-bot

    Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. MelvinBot commented on Jun 17, 2025

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  4. mountiny commented on Jun 17, 2025

    @mountiny
    Contributor

    Someone from SWM will take a look at this cc @SzymczakJ

  5. SzymczakJ commented on Jun 17, 2025

    @SzymczakJ
    Contributor

    I'm able to reproduce it, still investigating.

  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on Jun 17, 2025
  7. changed the title [-]Report Content Pushes Composer Slightly Out of View During Loading[/-] [+][$250] Report Content Pushes Composer Slightly Out of View During Loading[/+] on Jun 17, 2025
  8. 20 remaining items

  9. melvin-bot commented on Jul 4, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @hoangzinh owed $250 via NewDot
    • Contributor: @SzymczakJ is from an agency-contributor and not due payment

    BugZero Checklist (@garrettmknight)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1935033820143099096/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  10. garrettmknight commented on Jul 4, 2025

    @garrettmknight
    Contributor

    @hoangzinh please complete the checklist.

  11. hoangzinh commented on Jul 4, 2025

    @hoangzinh
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: It's a small UI issue. It's pretty hard to find offending PR

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

      Nope, I think it's just a small UI issue when the report is still loading. We don't need a regression test for this bug.

  12. melvin-bot commented on Jul 5, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  13. garrettmknight commented on Jul 7, 2025

    @garrettmknight
    Contributor

    Payment summary:

  14. hoangzinh commented on Jul 7, 2025

    @hoangzinh
    Contributor

    Thank you @garrettmknight. I requested in ND

  15. JmillsExpensify commented on Jul 9, 2025

    @JmillsExpensify
    Contributor

    Summary: @hoangzinh owed $250 via NewDot

  16. garrettmknight commented on Jul 21, 2025

    @garrettmknight
    Contributor

    $250 approved for @hoangzinh

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.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions