Lee Sun-woo

Aligning Signal’s timestamps with the text

My first Signal fix balanced the space below a message when the bubble ends with text. It deliberately left one case alone: a short message with the time beside it. At the default text size, that bubble was still about 4pt taller than the same message without a timestamp, and the time sat lower than the words next to it.

On November 13, 2026, I proposed a follow-up that aligns the timestamp with the last line of text. As of November 20, the pull request is open and has not been reviewed. The comparisons come from my iPhone Simulator builds, using Signal’s synthetic conversation preview rather than a registered account.

Find the rule behind the drop

When the last line leaves enough room, Signal places the time inline, beside the text. The layout code states its intent directly: align the vertical center of the footer with the baseline of the last line of body text. The time is set in smaller caption type, so centering it on the baseline pushes about half of it below the text. The bubble then grows to contain it.

On the main branch, the space below the text view measured about 8.9pt at the default size. A bubble that ends with text uses 5pt. Centering works well for an icon, but two runs of text at different sizes read as one line only when they share a baseline.

A Signal timestamp and the baseline of the message textBefore the change, the timestamp is centered on the text baseline, so it hangs below the text and the bubble grows taller. After the change, the timestamp sits on the same baseline as the text.방금 전방금 전

Measure the baseline instead of estimating it

The previous calculation reconstructed the baseline from font metrics: cap height, descender and line height. I replaced that estimate with the position TextKit reports for the last laid-out glyph, and recorded where the timestamp’s own baseline falls inside the footer. The overlap between text and footer now follows from those two measured baselines.

A second adjustment keeps the padding consistent. When the footer reaches below the text, the bottom inset now accounts for the footer’s height, so the space below the text stays at the same 5pt used by a bubble without a timestamp. I left the surrounding rules in place: when the time does not fit on the last line, it still moves to its own line, and the horizontal collision check is unchanged.

Default text size, measured on the main branch and with the change
MeasureBeforeAfter
Space below the text view8.9pt5pt
Height compared with no timestampAbout 4pt tallerThe same
Timestamp positionBelow the text baselineOn the text baseline

Test every text size, not one screenshot

A screenshot at the default size describes one case. The regression test renders incoming and outgoing bubbles at all twelve Dynamic Type sizes with six samples: Korean, English, letters with descenders, an explicit line break, Arabic in the existing left-to-right test context, and text mixed with emoji. That produces 144 bubbles. For each, the test checks the space below the text to within 0.5pt and the two baselines to within 1pt. The spacing check fails on the unmodified main branch and passes with the change.

Side-by-side previews show the same alignment for edited and disappearing messages, whose footers add a label or an icon. I have not tested the change on a physical device or in a conversation with a linked account, and I have not checked group threads or media captions.

The change adds 179 lines across four files; 135 of them are the test. Most of the work was establishing which rule produced the drop and proving that the replacement holds beyond the one size where the problem was first visible.

View the pull request on GitHub →