Skip to content

Fix Inbox filter tabs overlapping for long labels#95381

Open
Abdulloh0109 wants to merge 2 commits into
Expensify:mainfrom
Abdulloh0109:fix/93975-inbox-tab-label-overflow
Open

Fix Inbox filter tabs overlapping for long labels#95381
Abdulloh0109 wants to merge 2 commits into
Expensify:mainfrom
Abdulloh0109:fix/93975-inbox-tab-label-overflow

Conversation

@Abdulloh0109

@Abdulloh0109 Abdulloh0109 commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

In equalWidth mode each tab is constrained to a third of the row, but the TabLabel container only had a fixed maxWidth with no flexShrink/minWidth, so long-word locales (e.g. Polish) overflowed the pill into the neighbouring tab and the selection background stopped short of the label. Letting the label container shrink lets the existing numberOfLines={1} truncate within its tab.

Explanation of Change

The Inbox filter tabs (All / Unread / To-dos) were rendered with equalWidth, which forces each tab into a third of the narrow LHN width. In long-word locales (e.g. Polish — Nieprzeczytane, Zadania do wykonania) the labels overflowed their third, overlapped the neighbouring tab, and the selected-tab pill didn't cover the full label.

Per the design decision on the issue, the tab bar should be content-sized and scroll horizontally (like Spend) instead of being squeezed into equal thirds. This PR removes the equalWidth prop from InboxTabSelector, so each tab sizes to its label and the row scrolls horizontally when labels overflow — no truncation. TabSelectorBase already wraps the tabs in a horizontal ScrollView, and its content container's existing paddingHorizontal: 20 provides the 20px right margin when scrolled to the end.

Fixed Issues

$ #93975
PROPOSAL: #93975 (comment)

Tests

  1. Set the app language to Polski (Account → Preferences → Language → Polski).
  2. Open the Inbox (Skrzynka odbiorcza).
  3. Verify the three filter tabs — Wszystko / Nieprzeczytane / Zadania do wykonania — each show their full label and do not overlap each other.
  4. Verify that when the labels don't fit the width, the tab row scrolls horizontally (labels are not truncated).
  5. Scroll the tab row all the way to the right and verify there is ~20px padding after the last tab (equal margins on both sides).
  6. Switch the language back to English and verify the tabs (All / Unread / To-dos) render and scroll normally.
  7. Open another tab selector that uses TabSelectorBase (e.g. the narrow Search type menu) and verify it still renders correctly — no regression.
  • Verify that no errors appear in the JS console

Offline tests

The tab layout and filtering are entirely client-side (no API). Go offline, switch between All / Unread / To-dos in Polski, and verify the tabs still render, scroll, and don't overlap.

QA Steps

Same as tests.

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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 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 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 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 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 new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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.
  • 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

Windows: Chrome
78f6ee4f-3e87-4f63-96ac-fcf635b0286a.mp4
Android: App
REC-20260714141928.mp4
IOS: App
REC-20260714141549.mp4

@Abdulloh0109
Abdulloh0109 requested review from a team as code owners July 6, 2026 11:22
@melvin-bot
melvin-bot Bot requested review from ahmedGaber93 and joekaufmanexpensify and removed request for a team and joekaufmanexpensify July 6, 2026 11:23
@melvin-bot

melvin-bot Bot commented Jul 6, 2026

Copy link
Copy Markdown

@ahmedGaber93 Please 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]

@melvin-bot
melvin-bot Bot removed the request for review from a team July 6, 2026 11:23
Comment thread src/components/TabSelector/TabLabel.tsx Outdated
const styles = useThemeStyles();
return (
<View style={{maxWidth: variables.tabSelectorMaxTabLabelWidth}}>
<View style={{maxWidth: variables.tabSelectorMaxTabLabelWidth, flexShrink: 1, minWidth: 0}}>

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.

❌ UI-3 (docs)

This line passes an inline style object literal (style={{maxWidth: variables.tabSelectorMaxTabLabelWidth, flexShrink: 1, minWidth: 0}}) to a style-typed prop. Per STYLING.md, inline style objects are not allowed: they allocate a new object on every render (defeating memoization) and duplicate values that belong in the shared style system. This change compounds the issue by adding two more static values (flexShrink: 1, minWidth: 0) inline.

Move these static values into the shared styles object (e.g. a styles.tabSelectorLabelContainer entry combining maxWidth, flexShrink: 1, minWidth: 0) and reference it:

<View style={styles.tabSelectorLabelContainer}>

Define the style once in src/styles/index.ts rather than inline in JSX.


Reviewed at: dbe1d9d | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

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.

👍 Moved to shared styles

@Abdulloh0109
Abdulloh0109 requested a review from a team as a code owner July 6, 2026 11:34
@codecov

codecov Bot commented Jul 6, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/pages/inbox/sidebar/InboxTabSelector.tsx 90.47% <ø> (ø)
... and 12 files with indirect coverage changes

@shawnborton

Copy link
Copy Markdown
Contributor

Can we see a video recording for when the tabs have the counter badges? Thanks!

@Abdulloh0109

Copy link
Copy Markdown
Contributor Author

The badge counter is visible in the video recorded on macOS Safari. Have you had a chance to watch that video?

@shawnborton

Copy link
Copy Markdown
Contributor

Ah sorry I missed that, thanks! Let's get this into final review.

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@Abdulloh0109 The implemented fix isn't the approach we agreed to move forward with. Please take another look at the discussion here: #93975 (comment)

Also please update the OP with all the required data

Screenshot 2026-07-11 at 6 59 50 AM Screenshot 2026-07-11 at 6 59 33 AM

Per the design decision on Expensify#93975, the Inbox filter tabs should be
content-sized and scroll horizontally (like Spend) instead of being squeezed
into equal thirds. Dropping the equalWidth prop lets long-word locales (e.g.
Polish) show full labels without overlap, and TabSelectorBase's existing
horizontal ScrollView + 20px content padding handle the scroll and right
margin.
@Abdulloh0109
Abdulloh0109 force-pushed the fix/93975-inbox-tab-label-overflow branch from ea8df06 to 9e0aab4 Compare July 14, 2026 08:55
@Abdulloh0109

Copy link
Copy Markdown
Contributor Author

@ahmedGaber93 Could you please review the changes again?

@ahmedGaber93

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.
  • 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

Android: HybridApp
Screen.Recording.2026-07-15.at.1.25.00.PM.mov
Android: mWeb Chrome
Screen.Recording.2026-07-15.at.1.27.08.PM.mov
iOS: HybridApp
Screen.Recording.2026-07-15.at.12.54.57.PM.mov
iOS: mWeb Safari
Screen.Recording.2026-07-15.at.11.26.48.AM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-07-15.at.11.22.45.AM.mov
Screen.Recording.2026-07-15.at.11.23.45.AM.mov

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@shawnborton Here's the final result if you'd like to take a look.

Screenshots/Videos

Android: HybridApp
Screen.Recording.2026-07-15.at.1.25.00.PM.mov
Android: mWeb Chrome
Screen.Recording.2026-07-15.at.1.27.08.PM.mov
iOS: HybridApp
Screen.Recording.2026-07-15.at.12.54.57.PM.mov
iOS: mWeb Safari
Screen.Recording.2026-07-15.at.11.26.48.AM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-07-15.at.11.22.45.AM.mov
Screen.Recording.2026-07-15.at.11.23.45.AM.mov

@ahmedGaber93 ahmedGaber93 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!

@melvin-bot
melvin-bot Bot requested a review from Julesssss July 15, 2026 10:33
@Abdulloh0109

Copy link
Copy Markdown
Contributor Author

@Julesssss It's been a long time. Could we please merge this PR?

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@Abdulloh0109 could you please fix the git conflict?

…-label-overflow

# Conflicts:
#	src/pages/inbox/sidebar/InboxTabSelector.tsx
@Abdulloh0109

Copy link
Copy Markdown
Contributor Author

@ahmedGaber93 done

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.

3 participants