Repository navigation
Description
Background
We recently shipped a consistent bordered field treatment on the Manual create expense form (https://github.com/Expensify/Expensify/issues/598528), and recently applied the same to the Scan flow too (#93854). We applied even further improvements in #100221. Category, the tag rows, Tax rate, Attendees, and Report each render as a bordered row with a down caret, matching Amount and Merchant.
The caret is currently cosmetic. Tapping one of those rows still pushes a full-page selector, so the row promises a dropdown and delivers a page. That costs a navigation in each direction for what is usually a one-tap choice, covers the form the user is in the middle of filling out, and is especially heavy on wide layouts, where a full page opens to show a six-item list.
This issue makes the caret real, by opening each of those lists in a container anchored to the row it came from.
Change summary
- Open every list field on an expense (
Category, the tag rows,Tax rate,Attendees, andReport) in a container anchored to the row instead of a full-page selector. - Use a pop-over on wide layouts and a bottom sheet on narrow ones.
- Apply this in all three places those fields render: the
Manualcreate expense form, the expense detail view, and bulk edit from search results. - Reuse each field's existing list inside the new container, rather than building a second list.
- No change to what any list contains, how it searches, or what happens once a selection is made. This changes the container only.
Product and design details
Pop-over open on Category, wide layout
CleanShot.2026-09-21.at.11.56.26.mp4
Bottom sheet open on Category, narrow layout
CleanShot.2026-09-21.at.11.59.53.mp4
Attendees multi-select pop-over with several selected
CleanShot.2026-09-21.at.12.07.34.mp4
Fields in scope
Three of the five need a note on what the container holds:
- Every tag row gets its own container, so a workspace with three tag lists has three.
Reportkeeps itsNew reportoption at the top of the list.Tax rateis the tax field in scope.Tax amountis an amount input rather than a list, so it is unaffected.
To, Date, Merchant, and Description are also unaffected, since none of them opens a list.
Pop-over, wide layouts
The pop-over aligns to the row's left edge, matches the row's width, and opens directly below the row.
- If there is not enough room below the row, it opens above it instead. It is never clipped by the viewport.
- The list scrolls inside the pop-over once it reaches the container's max height. The form behind it does not scroll while the pop-over is open.
- The search input renders under the same conditions it renders in today's selector, so we are not introducing a new threshold for when a list becomes searchable.
- Dismiss by clicking outside the pop-over, pressing
Escape, or clicking the row again.
Bottom sheet, narrow layouts
Narrow layouts get a bottom sheet rather than a pop-over, because there is no room to anchor a pop-over to a full-width row at phone width. It holds the same list and search input as the pop-over, and is dismissed by swiping down, tapping the backdrop, or using the system back affordance. We use the existing bottom sheet pattern; no new component.
Selecting a value
Each field keeps the select mode it has today:
- Single-select (
Category, each tag list,Tax rate,Report): tapping an option saves it and closes the container. The row updates to its value-selected state. - Multi-select (
Attendees): tapping an option toggles it and saves immediately. The container stays open so the user can keep picking, and closes only when dismissed. The row's pills update as each tap lands.
What happens after a selection is unchanged in each of the three contexts. On the create form it updates the draft expense and submits nothing. On the expense detail view it saves to the expense immediately. In bulk edit it stages the change until the bulk action is confirmed. Offline, a selection applies optimistically and syncs on reconnect, exactly as it does through the full-page selector today.
Adding an attendee who isn't in the list
Today's attendees selector lets a user type an email to add someone who is not already in the list, and that path stays. Typing a non-matching email shows the same add row as today. Selecting it adds the attendee and keeps the container open, consistent with the multi-select rule above.
Bulk edit
In bulk edit, these field rows already render inside an RHP. The pop-over anchors to the row within that RHP rather than to the page, so it stays inside the panel the user is working in.
Keyboard and screen reader
On web, each row behaves like a dropdown rather than a link:
EnterorSpaceon the focused row opens the container and moves focus into it.- Up and down arrows move through the options, and
Enterselects the focused one. Escapecloses the container and returns focus to the row that opened it, so keyboard users do not lose their place in the form.- Typing filters through the search input, where the field has one.
A screen reader announces the row as a collapsed dropdown, and as expanded once the container opens.
Open: multi-level tags
Workspaces with dependent tags require the user to pick a parent tag before the next level's options are known, which today's full-page selector handles by pushing a second page.
Issue Owner
Current Issue Owner: @ikevin127Metadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsHIGH
Activity
JmillsExpensify commentedon Sep 18, 2026
@shawnborton I left mock placeholder suggestions above for you.
[-][Hold #101571] Replace the full-page selectors for Category, tag, Tax rate, Attendees, and Report with anchored pop-overs[/-][+][Hold #100221] Replace the full-page selectors for Category, tag, Tax rate, Attendees, and Report with anchored pop-overs[/+][-][Hold #100221] Replace the full-page selectors for Category, tag, Tax rate, Attendees, and Report with anchored pop-overs[/-][+][CFI] [Hold #100221] Replace the full-page selectors for Category, tag, Tax rate, Attendees, and Report with anchored pop-overs[/+]106 remaining items
melvin-bot commentedon Nov 12, 2026
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.
jponikarchuk commentedon Nov 12, 2026
Deploy Blocker #106701 was identified to be related to the PR #105939 that attempted to fix this issue.
mitarachim commentedon Nov 12, 2026
Deploy Blocker #106702 was identified to be related to the PR #106084 that attempted to fix this issue.
puneetlath commentedon Nov 12, 2026
#105939 was reverted FYI.
melvin-bot commentedon Nov 13, 2026
@ikevin127 / @DylanDylann / @thelullabyy
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.37-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
ikevin127 commentedon Nov 15, 2026
Still working on this...