UI: two-line labels overlap the row below (Tax management, Special goods trade)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in runtime/ui/frame/frame.ts, at the wrap branch that splits an authored label wider than its box onto two centred lines — its comment names "Purchase amount" and "Large category" as targets. Reproduce by opening the UI gallery (apps/client-next/tools/ui-gallery) at surface:Fortress tax and breadth:specialty-buy, and compare with the Experimental "Fit window labels" row off. Done means both lines of every listed label sit inside their box without touching the neighbouring row, with the row on by default, checked across all the entries named in the issue.
Written by the indexing model from the issue text.
Description
Found in a full sweep of the UI gallery (apps/client-next/tools/ui-gallery). Two-line static labels wrap onto a second line that is drawn over the label in the row below.
Gallery entries:
surface:Fortress tax(alsoreach:fortress-tax-modify,reach:fortress-tax-collect): "Blacksmith's workshop" overlaps "Defending tool shop"; "Gate of Dimensions" overlaps "Specialty store".breadth:specialty-buy(Special goods trade window): "Purchase amount", "Profit amount", "Selling amount" and "Trade scale" overlap each other; in the transport inventory beside it, "Total Amount" overlaps "Trade difficulty".- Same pattern, milder: Character panel "Phy. balance" and Stall network "Large/Medium/Small category".
To do: fix the presentation so the text stays inside its box and clear of its neighbours.
Cause found: the wrap comes from the port-only Experimental row "Fit window labels" (on by default, owner's choice 2026-10-15). runtime/ui/frame/frame.ts wraps an authored label wider than its box onto two lines centred on the box, and its comment names "Purchase amount" and "Large category" as the targets. A box sized for one line has no room for two, so the lines land on the neighbouring rows. With the row off, the original runs the label past the window's left edge instead. The fix belongs in that row: give the second line room (or shift the pair) without entering a neighbour.
Owner rule (2026-11-16): retail's own overflow and misalignment are bugs, not behaviour to copy. Fix these even where retail draws them the same way, on by default under the Experimental "Fit window labels" row (off is the original).
- Dominant language
- Go
- Stars
- 97
- Forks
- 61
- Avg merge
- 4h 14m
- Merged PRs (30d)
- 913
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opensro-dev/opensro
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
area: client bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opensro-dev/opensro#3228 · 1 comment ·
Maintainers usually reply within 1 day
-
Format one minified client file with dprint (ongoing: one file per PR)Possibly taken A pull request linked to this issue is open or already merged. Openarea: client enhancement good first issue priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#1 · 1 comment ·
Maintainers usually reply within 1 day
-
area: server bug priority: medium
Difficulty 3/5 Half a day Newbie friendliness 55/100
opensro-dev/opensro#3687 ·
Maintainers usually reply within 1 day
-
area: ops bug priority: high
Difficulty 4/5 3-5 days Newbie friendliness 32/100
opensro-dev/opensro#3685 ·
Maintainers usually reply within 1 day
All issues in opensro-dev/opensro
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
unbound-force/gaze#353 ·
Maintainers usually reply within 1 day
-
bug cross-seed ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OneBusAway/maglev#2102 ·
Maintainers usually reply within 2 days
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Waiting start: the fixed 503 body says another instance holds the lease when that may not be soOpen
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
Maintainers usually reply within 1 day