Repository navigation
sfsize= has no effect as of 2.1.2 — plugins can no longer control SF Symbol size
#543
franrich-cyber
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
#538 states that the change deliberately leaves
sfsizeand the default SF Symbol sizing unchanged, and I want to respect that decision rather than reopen it as a bug. But I think there may be a gap between the intent and the current behaviour, so I would rather raise it here than file another issue.What I observe
On 2.1.2 (build 604),
sfsize=has no observable effect at all. This is the whole plugin:All six rows render at the same size. Values from 6 to 40 are indistinguishable.
Separately, the default size changed between 2.0.1 and 2.1.2. Measuring the
magnifyingglasssymbol on two screen recordings of the same plugin on the same machine, at native resolution:The cap height of the adjacent text is identical, so both captures are at the same effective scale and the 1.6x difference is real. At a 2x backing scale that is roughly 10 pt versus 16 pt.
Why the combination is the problem
Either one alone would be fine.
A larger default with a working
sfsize=is a design choice plugins can opt out of. A frozen size with the old default would at least be visually unchanged. What makes it awkward is the two together: the appearance of every plugin usingsfimage=changed, and there is no parameter left to restore it.For scale, in my own setup that is 93 rows in one plugin and 109 in another, all using
sfimage=withoutsfsize=, since the previous default suited them.What I am asking for
Not a revert of the default. If the new sizing is intentional and matches macOS menu metrics better, that is your call and I will adapt.
What I would like is for
sfsize=to work again, so plugins that want the previous proportions can ask for them. Ifsfsizewas expected to keep working, then its current behaviour may simply be an unintended side effect of the sizing change rather than part of the decision.If reinstating the per-row parameter is not desirable, a global preference or a plugin metadata key would serve just as well from my side. The specific mechanism matters much less than having one.
Context
2.1.2 beta 2: three menu rendering regressions - multi-line title alignment next to image=, highlight and color= loss on non-actionable rows, sfsize= ignored and larger default sfimage= size#533, fix(menu): correct inline image alignment and hover redraw #538Happy to test any build on macOS 26.5.2 and report back, as the differences between 26.x and 27.x came up in #538.
All reactions