UI: two-line labels overlap the row below (Tax management, Special goods trade)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 72/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- frontend
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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).
- Lenguaje dominante
- Go
- Estrellas
- 97
- Forks
- 61
- Merge medio
- 4 h 14 min
- PR fusionados (30 d)
- 913
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de opensro-dev/opensro
-
area: client enhancement priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
opensro-dev/opensro#3681 ·
Los mantenedores suelen responder en 1 día
-
area: client bug priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
opensro-dev/opensro#3228 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Format one minified client file with dprint (ongoing: one file per PR)Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea: client enhancement good first issue priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
opensro-dev/opensro#1 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area: server bug priority: medium
Dificultad 3/5 Medio día Aptitud para principiantes 55/100
opensro-dev/opensro#3687 ·
Los mantenedores suelen responder en 1 día
-
area: ops bug priority: high
Dificultad 4/5 3-5 días Aptitud para principiantes 32/100
opensro-dev/opensro#3685 ·
Los mantenedores suelen responder en 1 día
Todos los issues de opensro-dev/opensro
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
unbound-force/gaze#353 ·
Los mantenedores suelen responder en 1 día
-
bug cross-seed ready-for-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
OneBusAway/maglev#2102 ·
Los mantenedores suelen responder en 2 días
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Waiting start: the fixed 503 body says another instance holds the lease when that may not be soAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
Los mantenedores suelen responder en 1 día