Calendar next-meeting row shows unreadable clipped text
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- macos, swift
- Domain
- accessibility, desktop, frontend
Research direction
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.
Written by the indexing model from the issue text.
Description
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).
- Dominant language
- Swift
- Stars
- 184
- Forks
- 12
- Avg merge
- 3h 50m
- Merged PRs (30d)
- 387
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 Seb-GRAF/StableBar
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
Menu bar items drawn as in the menu bar show the wrong part of the menu bar after a display changePossibly taken @Jonathanm10 claimed this today. Openneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
Allow the App Menu to display the frontmost app iconPossibly taken @khatami10 claimed this today. Openenhancement needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in Seb-GRAF/StableBar
Similar issues
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area:cli documentation good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 94/100
isaaclins/freesnitch#430 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MasterJ93/ATProtoKit#354 ·
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
heysidhant/appvanish#4 ·
-
bug priority:low status:queued
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day