Skip to content

Help panel - Help panel opens behind RHP on edit photo and view attachment page #57806

Closed

Description

@mitarachim

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: 9.1.9-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+ps309@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: User Settings

Action Performed:

Precondition:

  • Run Onyx.set('nvp_sidePaneExpanded', {}) in console.
  1. Go to staging.new.expensify.com
  2. Go to Settings > Profile.
  3. Click on the avatar.
  4. Select a photo.
  5. On Edit photo page, click Help icon.
  6. Note that help panel opens behind the RHP.
  7. Upload the photo.
  8. Click on the avatar.
  9. Click View photo.
  10. Click help icon.
  11. Note that help panel does not have right padding and it opens behind the RHP.

Expected Result:

In Step 6, help panel will open next to the RHP.
In Step 11, help panel will have right padding and it will open next to the RHP.

Actual Result:

In Step 6, help panel opens behind the RHP.
In Step 11, help panel does not have right padding and it opens behind the RHP.

Step 11 also happens when viewing attachment.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6761339_1741134590738.20250305_082259.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 5, 2025
  2. melvin-bot commented on Mar 5, 2025

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (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. melvin-bot commented on Mar 5, 2025

    @melvin-bot

    Triggered auto assignment to @robertjchen (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Mar 5, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Mar 5, 2025

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Mar 5, 2025
  7. 8 remaining items

  8. blazejkustra commented on Mar 11, 2025

    @blazejkustra
    Contributor

    FYI I'm working on this issue and two other that are strictly connected. I should have updates tomorrow!

  9. CortneyOfstad commented on Mar 13, 2025

    @CortneyOfstad
    Contributor

    Thanks @blazejkustra! Any update?

  10. blazejkustra commented on Mar 13, 2025

    @blazejkustra
    Contributor

    Update: I'm working on this, I'm on a good track but still not a final solution:

    userprofile.mov
  11. blazejkustra commented on Mar 18, 2025

    @blazejkustra
    Contributor

    Update: PR is ready for review.

  12. melvin-bot commented on Mar 20, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  13. melvin-bot commented on Mar 20, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  14. blazejkustra commented on Mar 27, 2025

    @blazejkustra
    Contributor

    PR got merged, we can slowly wrap this issue up.

  15. brunovjk commented on Mar 27, 2025

    @brunovjk
    Contributor

    I can't reproduce this anymore after implementing this PR. Tested on 27 Mar v9.1.20-2 Develop. We can close, payment and BZ checklist will be handled here. Thanks!

  16. CortneyOfstad commented on Mar 28, 2025

    @CortneyOfstad
    Contributor

    Sounds good — thanks @brunovjk!

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringInternalRequires API changes or must be handled by Expensify staffReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions