ObliviOS Developer portal Project site

Home / Decisions / ADR-123

A label inside a segmented button (labelInsideButton mode, ADR-121) may use two lines and hyphenate, and the buttons of the row share the height of the tallest one…

Accepted, recorded 2 October 2026.

Decision
ADR-123
Date
2026-10-02
Status
AcceptedAccepted (landed, built in image 2026100201 and seen on lynx, AIR-118)
Mentions
ADR-121
Mentioned by
ADR-122

1Decision

A label inside a segmented button (labelInsideButton mode, ADR-121) may use two lines and hyphenate, and the buttons of the row share the height of the tallest one (additive patch frameworks-base/0003, SegmentedButtonPreference.kt, 13 lines). The 8 dp padding of 0002 stays. Settings' stock earbud drawings are not patched: the flash they were suspected of could not be reproduced (AIR-117).

2Why and evidence

The labels were cut at font scale 1.3 (Transparen...) and 2.0 (Transp...) because a button is single-line; wrapping is the platform's answer to a large font and keeps the whole word readable, where shrinking or a smaller maximum scale would defeat the user's setting. A patch for a flash that is not reproduced would be a change to a privileged-adjacent Settings path with no measured defect behind it.

3Consequences

Stock icon-only rendering is unchanged (the code is inside labelInsideButton). MATCH_PARENT height inside the MaterialButtonToggleGroup relies on LinearLayout re-measuring match-parent children, which was checked on the device (equal heights at 1.0, 1.3 and 2.0). A single long word on 2.0 hyphenates (Transpar-ency at 1.3, Trans-parency at 2.0). The cold-start empty ring (about 0.2 s) is not fixed here: it ends with a warm foreground service (Plan 6D).

4Review when

A rebase that changes SegmentedButtonPreference; a localisation whose labels need more than two lines.

Read from docs/governance/decision-log.md, entry ADR-123.