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
[repo:objectui] View tab bar caps visible tabs at a fixed maxVisibleTabs = 4 — 8 queues on a 1440 px page render 4 + '还有 4 个' with ~700 px of empty bar #14883
The object list page's view tab bar shows at most 4 view tabs regardless of available width. An object with 8 list views on a 1440 px viewport renders 4 tabs, then 还有 4 个 ({{count}} more), leaving roughly 700 px of the tab bar empty. The queues a role needs most (here: 待领导审批 / 已通过 / 已归档 / 流程看板) are hidden behind the overflow menu for every user, on every screen size.
No ResizeObserver / width measurement participates; E is not set from view metadata anywhere I could find.
Expected
Overflow should be width-aware: fit as many tabs as the bar can hold (measure, or CSS container query), and only then collapse the rest into {{count}} more.
Or, at minimum, let the app author raise the cap from view metadata (e.g. a tabs.maxVisible / listViews display option), and raise the default well above 4 — most business objects have 5–8 status queues.
Keep the current behaviour (active tab promoted out of the overflow) — that part is fine.
Environment
@objectstack/console 17.2.0 via @objectstack/cli 17.2.0 · objectstack dev · Chrome. App: objectstack-ai/kpi, object kpi_entry_sheet.
Triage: lands in objectstack-ai/objectui (list-page view tab bar) ⇒ repo:objectui; type Bug; priority:p2 unchanged; pm:queue.
Rationale: a fixed maxVisibleTabs = 4 in the console's view tab bar is entirely an objectui concern — the report does not depend on objectstack in any way. It already carried repo:objectui; the missing piece was a state label, which is why it sat 6+ days outside every queue scan.
Type Bug rather than Feature: the card's own measurement shows the bar is 1152 px inside a 1184 px parent and still collapses to 4 — the component has the width it needs and does not use it. That is a defect, ⛔ not a request to widen behaviour.
priority:p2 stands as filed: it degrades a routine navigation path for any object with more than four views, and the card measures the cost in clicks rather than asserting it.
Activity
huangyiirene commentedon Sep 10, 2026
Triage: lands in
objectstack-ai/objectui(list-page view tab bar) ⇒repo:objectui; typeBug;priority:p2unchanged;pm:queue.Rationale: a fixed
maxVisibleTabs = 4in the console's view tab bar is entirely an objectui concern — the report does not depend on objectstack in any way. It already carriedrepo:objectui; the missing piece was a state label, which is why it sat 6+ days outside every queue scan.Type
Bugrather thanFeature: the card's own measurement shows the bar is 1152 px inside a 1184 px parent and still collapses to 4 — the component has the width it needs and does not use it. That is a defect, ⛔ not a request to widen behaviour.priority:p2stands as filed: it degrades a routine navigation path for any object with more than four views, and the card measures the cost in clicks rather than asserting it.Triage seat ·
session_013hshVTmHY5F7rhpNtYHa3m· R+165 · 2026-09-10T01:0xZGenerated by Claude Code