Repository navigation
Open
Labels
area: appThe single-page app under app/The single-page app under app/bugSomething isn't workingSomething isn't working
Description
Reported by the project lead on 2026-11-19 from the settings screen, and measured on main 6139942.
The app uses ten of Kumo's components (Button, Input, LayerDialog, DropdownMenu, Badge, the toast, Tooltip, Loader, Empty, Banner). Every other control is written by hand as a native element with its own classes, although Kumo 2.18.1, the version pinned here, exports Select, Checkbox, Radio, Switch, Field, Label, Textarea, DatePicker and Combobox.
What is there today
| Written by hand | Where |
|---|---|
<select>, 9 |
settings/GeneralSettings.tsx, rules/FilterDialog.tsx (2), SearchOptions.tsx (2), AccessKeys.tsx (2), InvitePerson.tsx, routes/members.tsx |
<input type="radio">, 35 on the general settings alone |
settings/Row.tsx and its callers |
<input type="checkbox">, 11 |
the list, its toolbar, the filter dialog, the automatic reply, search options, others |
<textarea>, 3 |
settings/AutoReplySettings.tsx, settings/AssistantSettings.tsx, AgentPanel.tsx |
<input type="date"> and datetime-local, 5 |
search options, send later, the automatic reply |
<button>, 28 |
to be read one by one: a line of the list is a real button on purpose; the others need a reason |
What a person sees
- The page-size select ("Conversations on a page"): the browser's own arrow, 12 px from the border because the control has the same padding left and right; the browser's focus colour, not the app's; 36 px high with 13 px type beside Kumo inputs of 26 px and 12 px.
- Radios and checkboxes in the browser's blue and square corners, in both themes.
- Dates in the browser's own picker, which differs by browser and ignores the app's language.
Done when
- Every control in the table is Kumo's component, or stays native for a reason written at the place.
- Where Kumo's component cannot do what is needed, one wrapper lives in one place under
app/components/and every screen uses it; no screen styles a native control itself. - The name and the role of each control stay what the browser tests find today, or the tests change in the same pull request.
- Each changed screen is looked at in a real browser at desktop and phone width, in the light and the dark theme, and the pull request shows the pictures.
- Kumo's own guidance for each component is read from its current documentation before it is used, and anything the code relies on about it is said in the pull request.
The check that keeps this from coming back is its own issue.
Metadata
Metadata
Assignees
Labels
area: appThe single-page app under app/The single-page app under app/bugSomething isn't workingSomething isn't working
Activity
fix(app): the automatic reply uses Kumo's checkbox and text area, and…
Madraka commentedon Nov 19, 2026
audit: findings on the first six screens of this issue, read at
ac6c562on the branchfix/kumo-first-screens(not pushed when I read it; this note moves to the pull request when it opens).Each screen was opened on an example instance at 1280 px and at 375 px, and measured.
pnpm staticpasses (22). The debt goes from 46 places to 26, with six kept on purpose.To put right before it merges
Buttonisw-max shrink-0, so themin-w-0on it and thetruncateinside it do nothing. At 375 px the button is 137.3 px wide in a column of 102.9 px: the name ends at x = 181.3 and the date begins at 182.9, so they touch, and a longer name runs under the date and the three buttons beside it. Onmainthe name is cut with an ellipsis. I want a browser test at phone width with a long sender, and the picture.size="xs"withshape="square"gives 14 px; the 16 px icon is drawn 14 px wide in it. Onmainthe target is 20 × 20. The box beside it takes clicks 12 px around itself, so its target (40 × 32) ends exactly where the star's begins (x = 44 at 375 px, 301 at 1280 px): on a phone a slip from the star ticks the box. The target must be no smaller than it was; Kumo'ssmis 26 px and the line is 48 px tall. The columns of the list must still line up afterwards, measured.Smaller, to decide in the same pull request
size="xs").smkeeps the size they had.mainit is underlined. Read Kumo's registry for what it gives a text action, and say which was chosen.MessageHeader.tsx): the reason says Kumo'sButtoncannot be that picture. Say whyshape="circle"at the 40 px size cannot, or move it.Holds, by measurement
sm(26 px), centred on the line of text beside it (117.0 against 117.1); at 375 px the line wraps without a sideways scroll.ON_PURPOSE(the line of the list, the folded message, the middle of a long conversation, the shade behind the rail) say what Kumo'sButtoncannot be there, and I accept them.Not opened
Madraka commentedon Nov 19, 2026
Measured before the next screens move (the writing window, the address field, the answer under a conversation, attached files), at
ac6c562, whose copies of these files are the same as onmain. So that a move that makes something smaller is seen, as with the list's star:What the move should not keep as it is:
Not opened: the answer under a conversation (the example opens answers in the window), a file that asks before it opens, a picture among the attached files, the list of scheduled messages. Their pictures are wanted in the pull request that moves them.
Madraka commentedon Nov 19, 2026
A rule for every move under this issue, after the top bar's search box (see the third finding on #98):
A move to Kumo keeps the screen. Where the skill describes a control (its size, its shape, its fill), that description is what the move has to give, and it is not edited to fit the component. Where Kumo has no such shape, the control stays on purpose with a reason that names what Kumo lacks, and the gap is written down so it can be raised with Kumo. A change of look that is wanted is said in the pull request, with a picture before and after.