You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-07-03] Tags - Tag description is shown in two lines #94506
Version Number: 9.4.19-1 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#93855 Email or phone of affected tester (no customers):sdjnoisdjdosijsonssjo@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.5 / Chrome App Component: Workspace Settings
👋 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:
Identify the pull request that introduced this issue and revert it.
The Tags page header description is wrapped in styles.workspaceSection, which caps its width at workspaceSectionMaxWidth + sectionMargin * 2 = 712px, while the tags table rendered directly below it spans the full page width.
The regular tags subtitle is short and fits on one line within 712px, but the dependent-tags copy (subtitleWithDependentTags — "Tags add more detailed ways to classify costs. You are using dependent tags. You can reimport a spreadsheet to update your tags.") is longer and overflows 712px, so it wraps to two lines. This is the cap introduced when PR #93855 restyled the page header.
The same workspaceSection cap is used by the restyled Categories page header, so the cap itself is the intended new-style behavior — the wrap only shows up here because the dependent-tags copy is the longest of the header strings.
What changes do you think we should make in order to solve the problem?
Let the header description use the full available content width (matching the table beneath it) instead of the 712px workspaceSection cap — i.e. don't apply the workspaceSectionmaxWidth to the header subtitle on the Tags page, so the dependent-tags sentence renders on a single line on wide screens.
This is ultimately a small design decision between two options:
Widen the header so the description matches the full-width table (single line — matches the tester's expectation).
Shorten the dependent-tags copy so it fits within 712px.
I'd recommend option 1 since the table is already full-width and the capped description looks visually truncated next to it, but confirm the preferred width with design before implementing.
What alternative solutions did you explore? (Optional)
Accepting the two-line wrap as expected — the 712px readable-column cap is intentional and shared with other workspace pages, so a long description wrapping there is not strictly broken. Flagging in case the team considers this acceptable rather than a code change.
Next Steps for Contributor+ team: To accept:@MelvinBot implement [this](https://github.com/Expensify/App/issues/94506) to create a draft PR. To refine:@MelvinBot <your feedback> To reject: Explain why you are rejecting Melvin's proposal.
changed the title [-]Tags - Tag description is shown in two lines[/-][+][Due for payment 2026-07-03] Tags - Tag description is shown in two lines[/+]on Jun 26, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.20-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@luacmartins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
Activity
applause-bot commentedon Jun 24, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/71834afbaeb10f827fdd7e9994886897599761c7c54692ca1399d787e882c6ac
https://platform.applause.com/services/links/v1/external/7a2173ec2d82753c1bd53170e9b11286e48d221ab4c86396066ddf7f63cc19ce
melvin-bot commentedon Jun 24, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #93855
melvin-bot commentedon Jun 24, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jun 24, 2026
👋 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:
MelvinBot commentedon Jun 24, 2026
Proposal
What is the root cause of that problem?
The Tags page header description is wrapped in
styles.workspaceSection, which caps its width atworkspaceSectionMaxWidth + sectionMargin * 2= 712px, while the tags table rendered directly below it spans the full page width.The regular tags subtitle is short and fits on one line within 712px, but the dependent-tags copy (
subtitleWithDependentTags— "Tags add more detailed ways to classify costs. You are using dependent tags. You can reimport a spreadsheet to update your tags.") is longer and overflows 712px, so it wraps to two lines. This is the cap introduced when PR #93855 restyled the page header.Evidence
workspaceSection:WorkspaceTagsPage.tsx:782WorkspaceTagsPage.tsx:770-779styles/index.ts:5213-5215→maxWidth: workspaceSectionMaxWidth (680) + sectionMargin (16) * 2 = 712,variables.ts:276WorkspaceTagsPage.tsx:875-885The same
workspaceSectioncap is used by the restyled Categories page header, so the cap itself is the intended new-style behavior — the wrap only shows up here because the dependent-tags copy is the longest of the header strings.What changes do you think we should make in order to solve the problem?
Let the header description use the full available content width (matching the table beneath it) instead of the 712px
workspaceSectioncap — i.e. don't apply theworkspaceSectionmaxWidthto the header subtitle on the Tags page, so the dependent-tags sentence renders on a single line on wide screens.This is ultimately a small design decision between two options:
I'd recommend option 1 since the table is already full-width and the capped description looks visually truncated next to it, but confirm the preferred width with design before implementing.
What alternative solutions did you explore? (Optional)
Accepting the two-line wrap as expected — the 712px readable-column cap is intentional and shared with other workspace pages, so a long description wrapping there is not strictly broken. Flagging in case the team considers this acceptable rather than a code change.
Next Steps for Contributor+ team:
To accept:
@MelvinBot implement [this](https://github.com/Expensify/App/issues/94506)to create a draft PR.To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin's proposal.
luacmartins commentedon Jun 24, 2026
@Expensify/design should we just remove the 712px max width here?
luacmartins commentedon Jun 24, 2026
I'll demote this one since it's a small issue.
1 remaining item
dannymcclain commentedon Jun 24, 2026
Yeah I think that would probably be fine.
shawnborton commentedon Jun 25, 2026
Totally agree, not sure why that exists.
[-]Tags - Tag description is shown in two lines[/-][+][Due for payment 2026-07-03] Tags - Tag description is shown in two lines[/+]melvin-bot commentedon Jun 26, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jun 26, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.20-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-07-03. 🎊
melvin-bot commentedon Jun 26, 2026
@luacmartins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
luacmartins commentedon Jun 26, 2026
Done