Skip to content

Fix & refactor popover positioning#68026

Merged
pecanoro merged 32 commits intoExpensify:mainfrom
software-mansion-labs:fix/popover-positions-with-help-panel
Sep 2, 2025
Merged

Fix & refactor popover positioning#68026
pecanoro merged 32 commits intoExpensify:mainfrom
software-mansion-labs:fix/popover-positions-with-help-panel

Conversation

@jmusial
Copy link
Copy Markdown
Contributor

@jmusial jmusial commented Aug 6, 2025

Explanation of Change

Problems

  • some Popovers were showing below Help Panel
  • some Popovers were showing correct when Help Panel was open but when it got closed they were ending up in wrong spot
  • some Popovers were partially hidden by Help Panel
  • when Poover was open and user was opening help panel, Popover dissapeared. When Help Panel was being closed with Popover open. Popover was still appearing.

Solutions

  • unify anchor calculation logic for popovers. Anchor now calculates based on parent component location instead of static to the screen.
  • adjust anchor popover to use screen width adjusted by help panel width
  • always hide popovers on help panel animation

Note

Not all popovers were migrated to new calculation, but the PR was growing too much. In the leftover cases it makes more sense to use 'legacy' calculation method, but would be good to go through them as a follow up and migrate as well.

Fixed Issues

$ #66244

PROPOSAL:
N/A

Tests

At no points during tests popover should overlap with Help panel.

Changes should affect only wide screen envorinments, since on narrow screens popovers are replaced with Bottom Docked Modals.

1. Button With Dropdown Menu

  1. Open app
  2. Go to Reports
  3. Select Report
  4. Press "1 selected". Popover appears
  5. Open Help panel. (Popover disappears on first click outside).
  6. Press "1 selected". Popover appears
  7. Close Help panel. Popover disappears.

2. Dropdown Button

  1. Open app
  2. Go to Reports
  3. Press "From". Popover appears
  4. Open Help panel. (Popover disappears on first click outside).
  5. Press "From". Popover appears
  6. Close Help panel. Popover disappears.
  7. This can be tried on various screen widths. Popover anchors should adjust to help panel and never overlap.

3. Chat avatar

  1. Open app
  2. Go to Reports -> Chats
  3. Open chat with another user
  4. Add custom avatar if not present
  5. Press on avatar. Popover appears
  6. Open Help panel. (Popover disappears on first click outside).
  7. Press on avatar. Popover appears
  8. Close Help panel. Popover disappears.

4. Delegated access & Copilot

  1. Open app
  2. Go to Account -> Security
  3. Add a copilot
  4. Enter first magic code
  5. On second magic code press 3 dots menu. Popover appears
  6. Open Help panel. (Popover disappears on first click outside).
  7. Press 3 dots menu. Popover appears
  8. Close Help panel. Popover disappears.
  9. Enter second magic code
  10. Press 3 dots next to Copilot name. Popover appears.
  11. Open Help panel. (Popover disappears on first click outside).
  12. Press 3 dots next to Copilot name. Popover appears.
  13. Close Help panel. Popover disappears.

5. Workspaces list

  1. Open app
  2. Go to Worspaces (with at least one workspace)
  3. Press 3 dots menu. Popover appears
  4. Open Help panel. (Popover disappears on first click outside).
  5. Press 3 dots menu. Popover appears
  6. Close Help panel. Popover disappears.

Offline tests

Same as tests

QA Steps

Same as tests

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Popovers are not used on narrow screens.

Android: mWeb Chrome

Popovers are not used on narrow screens.

iOS: Native

Popovers are not used on narrow screens.

iOS: mWeb Safari

Popovers are not used on narrow screens.

MacOS: Chrome / Safari
0038.desktop.chrome.mov
MacOS: Desktop
0038.desktop.native.mov

Copy link
Copy Markdown
Contributor

@blazejkustra blazejkustra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Solid refactor, looks much cleaner!

vertical: 72,
},
POPOVER_DROPDOWN_WIDTH: 336,
POPOVER_DROPDOWN_WIDTH: 334,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why was this change necessary?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

334 is how it render width after size calculation. Without this change there is 2 px width flicker on the first render.

@blazejkustra
Copy link
Copy Markdown
Contributor

@jmusial FYI Tests are failing 👀

Copy link
Copy Markdown
Contributor

@mhawryluk mhawryluk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome work!! 🍿

@jmusial jmusial requested a review from blazejkustra August 20, 2025 09:46
Copy link
Copy Markdown
Contributor

@blazejkustra blazejkustra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, let's test it extensively (both popovers and help panel).

Also, can we wait with making this PR 'ready for review' for now? I would prefer to have this merged first 🙏

setIsMenuVisible(false);
}
}}
anchorPosition={shouldUseStyleUtilityForAnchorPosition ? styles.popoverButtonDropdownMenuOffset(windowWidth) : popoverAnchorPosition}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also clean up popoverButtonDropdownMenuOffset?

@blazejkustra
Copy link
Copy Markdown
Contributor

Back to you @hoangzinh

@hoangzinh
Copy link
Copy Markdown
Contributor

I found a bug:

Bug 1: Unable to add expense or export expense

Screen.Recording.2025-08-29.at.05.52.31.mov

@blazejkustra
Copy link
Copy Markdown
Contributor

The video is going through many screens and popovers, do I understand correctly that the only issue in this video is unclickable 'Add expense' at the start? @hoangzinh

CleanShot 2025-08-29 at 09 48 04

@hoangzinh
Copy link
Copy Markdown
Contributor

@blazejkustra Ah yes, it's "unclickable 'Add expense' at the start". I sent a not-so-good recording 🤦

@blazejkustra blazejkustra requested a review from a team as a code owner August 29, 2025 15:41
@blazejkustra
Copy link
Copy Markdown
Contributor

Great catch, there was an infinite loop as anchor default value was initialized with every render. Should work now @hoangzinh!

Copy link
Copy Markdown
Contributor

@trjExpensify trjExpensify left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No concerns with what this is doing in the product. For the foreseeable future while we focus on #migrate, however, I don’t think we should be prioritising help panel issues as it's behind a beta NVP flag - and don't plan to release it anytime soon. CC: @JmillsExpensify

@hoangzinh
Copy link
Copy Markdown
Contributor

hoangzinh commented Aug 31, 2025

In the leftover cases it makes more sense to use 'legacy' calculation method, but would be good to go through them as a follow up and migrate as well.

According to the PR's description, @blazejkustra, can you list some of them? I found that we already removed useThreeDotsAnchorPosition, just curious what is left.

@blazejkustra
Copy link
Copy Markdown
Contributor

@hoangzinh I think PR description is outdated and I can't edit it 😢

@hoangzinh
Copy link
Copy Markdown
Contributor

@hoangzinh I think PR description is outdated and I can't edit it 😢

No worry @blazejkustra. Can you share an updated version (just summary) of it here?

@blazejkustra
Copy link
Copy Markdown
Contributor

@hoangzinh I mean this part is outdated:

Note

Not all popovers were migrated to new calculation, but the PR was growing too much. In the leftover cases it makes more sense to use 'legacy' calculation method, but would be good to go through them as a follow up and migrate as well.

Meaning I don't think there is anything to list 😄 But we can wait for @jmusial to confirm this.

@hoangzinh
Copy link
Copy Markdown
Contributor

Thanks @blazejkustra

Copy link
Copy Markdown
Contributor

@hoangzinh hoangzinh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Sep 1, 2025

We did not find an internal engineer to review this PR, trying to assign a random engineer to #66244 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot melvin-bot bot requested a review from pecanoro September 1, 2025 22:27
@pecanoro pecanoro merged commit a28c459 into Expensify:main Sep 2, 2025
21 of 22 checks passed
@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Sep 2, 2025

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Sep 2, 2025

🚀 Deployed to staging by https://github.com/pecanoro in version: 9.2.1-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Sep 5, 2025

🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.1-20 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

const prevAnchorPosition = usePrevious(anchorPosition);
const prevWindowDimensions = usePrevious({windowWidth, windowHeight});
const {shouldHideSidePanel} = useSidePanel();
const availableWidth = windowWidth - (shouldHideSidePanel ? 0 : variables.sideBarWidth);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reference

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants