- Shipped
- August 30, 2026 at 7:00 PM UTC
- Author
- Kamo
- Commit
- 732f2c6
A member filed this against the report form itself: "What happened?" — and "What would you like to see?" on the enhancement side — had the field's border running straight through the middle of the text. Both were MUI floating labels. An outlined field paints its label ON the top border and keeps it readable only by notching that border to exactly the label's width; when the notch does not open, the border crosses the question. Nothing inside the form can correct that, because the label is drawn over the border by design. The Title field above it notches correctly on the same screen, so this is not a stylesheet the window is missing — it is a mechanism that fails in one place and not the other, and I could not reproduce the failure on Chrome/Linux against this exact commit (it is the image the reporter was on). So the question moves off the border rather than being asked to survive it. Above the field there is no notch to get wrong on any browser, it reads at the window's body size instead of the floating label's 12px, and it is the shape the window's three other questions — "What are you reporting?", "Where did you see it?", "Screenshots & videos" — were already using. Five questions, one voice. Two things fall out of it: - The placeholders are visible now. A floating label with no `shrink` sits over the placeholder until the field is focused, so "What should it do, and where does it fall short today?" was only ever seen by someone already typing. - Each question is a real `<label for>`, keyed to the windowId. Dropping `label` means MUI renders no label of its own, so this is the field's whole accessible name — and two report windows can be open at once, where a fixed id would point both questions and both click targets at whichever field mounted first. Costs about 48px of the ~100px of slack the 460x690 window had, after taking 4px back off the title field's margin. Still fits without a scrollbar.