ObliviOS Developer portal Project site

Home / Decisions / ADR-146

The on-screen keyboard (LatinIME) gets a new look and a landscape fix.

Accepted, recorded 7 October 2026.

Decision
ADR-146
Date
2026-10-07
Status
AcceptedAccepted; its landscape cause and mechanism are superseded by ADR-148
Part
Keyboard
Mentions
ADR-148
Mentioned by
ADR-148, ADR-149, ADR-191

1Decision

The on-screen keyboard (LatinIME) gets a new look and a landscape fix (design, reference): every key is its own rounded cap in a tone that differs from the keyboard background, with a 1.5 dp bottom edge, a rounded keyboard top, visible suggestion dividers and the same treatment on every page (alphabet, symbols, number, phone, password number, emoji panel, popups, landscape).

The look is resources only (shape and layer-list drawables, colours, styles) in the LXX Light and Dark themes, as the patch package keyboard/restyle in sovereignos-platform (patches 0001 the restyle and 0002 the landscape fix for packages/inputmethods/LatinIME); the landscape fix is a small Java change that applies the window insets per side. Everything is centred on the visible cap and measured on a device.

Delivery is two plans: restyle with the landscape fix, then inline autofill suggestions in the keyboard. The emoji font stays unchanged.

2Why and evidence

Owner decision 2026-10-07 (chat): approved the look after seeing every surface in the reference, asked for one spec and at most two plans, and required exact centring in the real product. The keys are already separate rectangles with gaps, but the key fill equals the keyboard background, so the keys read as one surface. Apple's emoji cannot be shipped and the open sets reviewed (Noto 3D, Fluent 3D) were rejected, so the emoji look is parked.

3Consequences

Three text colours differ from the tree for contrast (functional-key text in light, hint letters, suggested words in light). The cap boundary is 1.3:1 to 1.8:1 against the background, below WCAG 1.4.11 and above today's 1.0:1; operability rests on glyph contrast. A blurred shadow is not used. Whether the rounded top shows correctly depends on the input window being transparent in the corners, and the landscape cause (keyboard narrowed but not moved) is a hypothesis until a layout dump on a device confirms it. Autofill inline suggestions need new Java at the IME and autofill boundary and get their own threat note, review and plan. Nothing is built or on a device.

4Review when

A device shows the rounded top or the centring cannot be met with resources; the landscape dump contradicts the cause; an upstream GrapheneOS change to LatinIME conflicts with the patches.

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