Calendar next-meeting row shows unreadable clipped text

未关闭
#751 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
macos, swift

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

bug needs-info P2

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

  1. Display the next-meeting row in the reporter's existing setup.
  2. 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 tag v0.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, text with maxWidth: 180, minutes, and the separate literal min.
  • NativeMetrics.swift:212–218, CalendarMetrics.read: text receives the meeting title and fields.minutes receives 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 generic HStack; ordinary field blocks use lineLimit(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).

主要语言
Swift
星标
184
派生
12
平均合并
3 小时 50 分钟
30 天内合并 PR
387

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Seb-GRAF/StableBar 的其他 Issue

查看 Seb-GRAF/StableBar 的全部 Issue

相似的 Issue

更多 Swift Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。