Skip to content

[CFI] Attendee anchored dropdown - #105345

Merged
puneetlath merged 4 commits into
Expensify:mainfrom
DylanDylann:dylann/101573-attendees-anchored-dropdown
Oct 30, 2026
Merged

puneetlath merged 4 commits into
Expensify:mainfrom
DylanDylann:dylann/101573-attendees-anchored-dropdown

Conversation

@DylanDylann

@DylanDylann DylanDylann commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #101573
PROPOSAL:

Tests

Same QA steps

  • Verify that no errors appear in the JS console

Offline tests

Same QA steps

QA Steps

  1. Override the anchoredFieldDropdowns beta to true.
  2. Open a workspace chat on a workspace that has attendee tracking enabled.
  3. Start a manual expense and continue to the confirmation page.
  4. Click the Attendees row. Verify a pop-over opens on wide screens and a bottom sheet on narrow screens, with a "Search for someone" input and an Apply button.
  5. Add an attendee and press Apply. Verify the list closes and the row shows the new attendee.
  6. Reopen, tick another attendee, then dismiss with Esc or an outside click. Reopen and verify the attendee you dismissed is no longer ticked.
  7. Untick everyone. Verify the error shows and Apply is disabled.
  8. Submit the expense. Verify it has the applied attendees.
  • Verify that no errors appear in the JS console

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
  • 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 followed proper code patterns (see Reviewing the code)
    • 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 that was added to the app is grammatically correct in English. No new copy was added in this PR.
  • 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)
  • 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 new assets were added or existing ones were modified, I verified that: no assets were added or modified.
  • If the PR modifies code that runs when editing or sending messages: not applicable.
  • 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 — CategoryPickerModal is shared with the Search table's inline category edit and needs re-verifying there.
  • If the PR modifies a component related to any of the existing Storybook stories: not applicable.
  • 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 — the full-page category route is unchanged and still reachable directly.
  • 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow. tests/unit/components/ExpenseFieldDropdown.test.tsx covers lazy mounting, opening in place vs. navigating, the row-width/below-the-row geometry, the flip above the row, dismissing by pressing the row again, and the full-page fallback.
  • 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: HybridApp
Screen.Recording.2026-10-30.at.11.00.51.mov
Android: mWeb Chrome
Screen.Recording.2026-10-30.at.10.55.50.mov
iOS: HybridApp
Screen.Recording.2026-10-30.at.11.00.20.mov
iOS: mWeb Safari
Screen.Recording.2026-10-30.at.10.56.08.mov
MacOS: Chrome / Safari
Screen.Recording.2026-10-30.at.10.52.49.mov

@DylanDylann
DylanDylann requested review from a team as code owners October 29, 2026 07:57
@melvin-bot
melvin-bot Bot requested review from ikevin127 and thelullabyy and removed request for a team October 29, 2026 07:57
@melvin-bot

melvin-bot Bot commented Oct 29, 2026

Copy link
Copy Markdown

@ikevin127 @thelullabyy One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-29T08:20:53.440604Z 95d9be1 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@melvin-bot
melvin-bot Bot requested review from trjExpensify and removed request for a team October 29, 2026 07:57
@codecov

codecov Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 95.90% <ø> (ø)
.../components/AttendeePicker/AttendeePickerModal.tsx 100.00% <100.00%> (ø)
...RequestConfirmationList/sections/AttendeeField.tsx 75.51% <100.00%> (+4.08%) ⬆️
...onfirmationList/sections/AttendeeFieldDropdown.tsx 100.00% <100.00%> (ø)
...pages/iou/request/MoneyRequestAttendeeSelector.tsx 0.00% <0.00%> (ø)
... and 186 files with indirect coverage changes

@DylanDylann
DylanDylann removed the request for review from thelullabyy October 29, 2026 08:03
@DylanDylann

Copy link
Copy Markdown
Contributor Author

@Expensify/design I'd love to hear your thoughts on the design of the new attendee popover

Screen.Recording.2026-10-29.at.15.15.56.mov
Screen.Recording.2026-10-29.at.15.17.09.mov

@DylanDylann

DylanDylann commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor Author

@ikevin127 It’s ready for your review. I’ll add videos later, in case the design team wants to change anything

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 95d9be1229

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@dannymcclain

Copy link
Copy Markdown
Contributor

Looking pretty good to me—seems like it's following the Categories and Tags popovers which is what I would expect.

@ikevin127

ikevin127 commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • 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 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

iOS: Native
Screen.Recording.iPhone.18.Pro.10-29-2026.at.14.49.53.mp4
MacOS: Chrome / Safari
Screen.Recording.2026-10-29.at.14.36.24.mov

@trjExpensify

Copy link
Copy Markdown
Contributor

Running a build.

@github-actions

Copy link
Copy Markdown
Contributor

🚧 trjExpensify has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@ikevin127 ikevin127 left a comment

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.

I found 3 issues.

Follows the Category / Tag / Tax pattern well: the dropdown mounts lazily, compares with deepEqual before writing, and blocks Enter on an empty selection. Design (dannymcclain) is fine with the look.

⚠️ Codex already flagged 3 things on the earlier commit 95d9be1, so I skipped them: shortcuts still firing while the picker is hidden, the subscription to the whole draft (PERF-11), and the missing module header 👈 these Codex comments should be addressed as well.

trjExpensify
trjExpensify previously approved these changes Oct 30, 2026

@trjExpensify trjExpensify left a comment

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.

LGTM on the adhoc! 👍

@DylanDylann

Copy link
Copy Markdown
Contributor Author

@ikevin127 All resolved

@DylanDylann
DylanDylann requested a review from ikevin127 October 30, 2026 03:57

@ikevin127 ikevin127 left a comment

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.

🟢 LGTM - All previous comments are addressed

@DylanDylann 🟠 QA step 2 is cut off ("open a workspace chat on a workspace that"). QA runs these verbatim, and none of them cover Apply, dismissing without Apply, or the empty-selection error.

Suggested steps:

1. Override the `anchoredFieldDropdowns` beta to true.
2. Open a workspace chat on a workspace that has attendee tracking enabled.
3. Start a manual expense and continue to the confirmation page.
4. Click the Attendees row. Verify a pop-over opens on wide screens and a bottom sheet on narrow screens, with a "Search for someone" input and an Apply button.
5. Add an attendee and press Apply. Verify the list closes and the row shows the new attendee.
6. Reopen, tick another attendee, then dismiss with Esc or an outside click. Reopen and verify the attendee you dismissed is no longer ticked.
7. Untick everyone. Verify the error shows and Apply is disabled.
8. Submit the expense. Verify it has the applied attendees.

@melvin-bot
melvin-bot Bot requested a review from puneetlath October 30, 2026 04:36
@puneetlath
puneetlath merged commit a02e51e into Expensify:main Oct 30, 2026
42 of 44 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 puneetlath has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

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

@github-actions

Copy link
Copy Markdown
Contributor

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.5.27-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site update needed. The new anchored Attendees dropdown only appears when the anchoredFieldDropdowns beta is on (AttendeeField.tsx:92), and the full-page attendee selector keeps its existing Save button and search label, so no current article is inaccurate.


view run

@mitarachim

Copy link
Copy Markdown

Deploy Blocker #105562 was identified to be related to this PR.

@OSBotify

OSBotify commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.5.27-2 🚀

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

Bundle Size Analysis (Sentry):

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