Calendar next-meeting row shows unreadable clipped text
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 38/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- macos, swift
- Área
- accessibility, desktop, frontend
Línea de trabajo
Start with WidgetLabel.swift at defaultLayout, PopupView.swift at PopupBlockView.content, and BarView.swift at WidgetBlocks.body to identify which surface renders the row and whether a custom layout applies. Then trace the calendar fields in NativeMetrics.swift and compare the constrained row with the bar’s existing unit measurement and overflow handling. Done when the countdown and unit remain readable together under the reported constraint; the screenshot does not establish the exact surface or configuration.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What happens
The reporter supplied a screenshot of a calendar-style next-meeting row that is not readable. After the calendar icon, it shows a single letter, a number beginning with 7 followed by an ellipsis, and another ellipsis. Both the meeting information and the trailing value/unit are clipped.
The screenshot is the observed failure. Identifying the fragments as the native calendar title, minutes and min is a source-backed hypothesis, not a confirmed mapping of the screenshot to a particular view. The event title is not known and is not inferred here.
Steps to reproduce
- Display the next-meeting row in the reporter's existing setup.
- Observe the clipped row shown in the supplied screenshot.
The exact containing surface and width constraint are not established by the crop. It may be the bar or another surface that renders the widget. No new reproduction was run, and no calendar data or configuration was changed during triage.
Expected
Keep the countdown and its unit readable together. A long meeting title can use an ellipsis. If the available width cannot hold the row, use an appropriate compact or overflow presentation rather than independently truncating the value and unit into ambiguous fragments.
The Calendar guide describes the widget as showing the next meeting and its countdown.
Environment
- Installed StableBar: 0.17.0, build 1187.
- macOS on the reporting workstation: 27.0, build 26A428; arm64.
- Displays, notch, window manager and exact widget configuration: not established for this screenshot.
- Screenshot surface, scale and width: not established.
- Source reviewed: main
01bf12a1a67f6083342421efa090e48213fbe62e. The same default calendar row exists at stable tagv0.17.0(9ac8fb042aff9e5fa65805835dcfeaddb4777f59).
Evidence
The reporter's crop shows a calendar icon, a single-letter text fragment and two separately truncated trailing fragments. The screenshot was supplied during triage; no event name, account or private configuration is included in this report.
No app launch, rendering test, benchmark or automated test was performed for this report.
Diagnosis
Static diagnostic leads on pinned main:
- WidgetLabel.swift:99–105,
WidgetConfiguration.defaultLayout: the detailed native calendar layout is one row containing the calendar icon,textwithmaxWidth: 180,minutes, and the separate literalmin. - NativeMetrics.swift:212–218,
CalendarMetrics.read:textreceives the meeting title andfields.minutesreceives the countdown. This is why the screenshot is more consistent with a meeting row than a date-format failure, but the crop alone cannot prove it. - PopupView.swift:463–500,
PopupBlockView.content: rows use a genericHStack; ordinary field blocks uselineLimit(1). This path does not give the calendar countdown and unit a shared, protected width. - BarView.swift:947–959,
WidgetBlocks.body: custom layouts take precedence over the native default, so the exact configured layout must be identified before choosing a fix.
The main bar already measures units at intrinsic size and scrolls an unavoidably constrained unit. These safeguards mean the screenshot does not establish a defect in AdaptiveBarPlanner, or prove that the whole bar ran out of space. Investigate the actual containing surface first. Any fix should preserve those existing measurement and overflow behaviors and avoid making every text block globally fixed-size.
Related
- #741: calendar selection in Settings, not row sizing.
- #735: today-only event selection, not clipping.
- #722 and #723: agenda metadata and conditional blocks; neither protects the default row's countdown width.
- #746: the Settings window header's minimum width, not this widget row.
- #169, shipped in 0.6.0: equal-width digits reduce width changes; they do not prevent value/unit clipping under a constrained width.
No matching issue or PR was found in all-state calendar/meeting searches and focused clipping/countdown searches. The relevant default layout is unchanged in the latest stable release and pinned main.
Triaged by OMP (closerouter/openai/gpt-6.1-sol).
- Lenguaje dominante
- Swift
- Estrellas
- 184
- Forks
- 12
- Merge medio
- 3 h 50 min
- PR fusionados (30 d)
- 387
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 Seb-GRAF/StableBar
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
Los mantenedores suelen responder en 1 día
-
Menu bar items drawn as in the menu bar show the wrong part of the menu bar after a display changePosiblemente ocupada @Jonathanm10 la tomó hoy. Abiertoneeds-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
Los mantenedores suelen responder en 1 día
-
Allow the App Menu to display the frontmost app iconPosiblemente ocupada @khatami10 la tomó hoy. Abiertoenhancement needs-triage
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
Todos los issues de Seb-GRAF/StableBar
Issues similares
-
good first issue help wanted testing
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
-
area:cli documentation good first issue priority:low
Dificultad 1/5 Menos de una hora Aptitud para principiantes 94/100
isaaclins/freesnitch#430 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
MasterJ93/ATProtoKit#354 ·
-
enhancement help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
heysidhant/appvanish#4 ·
-
bug priority:low status:queued
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día