.daw-topbar sets padding-top: 10px and padding-bottom: 10px, and then a few lines later sets padding: 0 16px. A shorthand after longhands wins, so the bar has never had the vertical padding the comment above it describes.
Why nobody has seen it
The composer inside is a fixed 50px in a bar with a 77px minimum, and align-items: center distributes the missing space evenly, so the bar looks correctly padded. It only appears once that composer is taller than the bar's minimum: the box then fills the bar edge to edge and its top border sits against the top of the window.
That makes this a trap rather than a cosmetic fault. It is invisible until someone makes the top bar taller for any reason, and then it looks like their change broke the layout.
Constraints for whoever fixes it
One declaration instead of three. The comment directly above the rule already explains why the vertical padding is wanted, which is worth keeping: it was added so a wrapped translation grows the bar instead of being clipped.
.daw-topbarsetspadding-top: 10pxandpadding-bottom: 10px, and then a few lines later setspadding: 0 16px. A shorthand after longhands wins, so the bar has never had the vertical padding the comment above it describes.Why nobody has seen it
The composer inside is a fixed 50px in a bar with a 77px minimum, and
align-items: centerdistributes the missing space evenly, so the bar looks correctly padded. It only appears once that composer is taller than the bar's minimum: the box then fills the bar edge to edge and its top border sits against the top of the window.That makes this a trap rather than a cosmetic fault. It is invisible until someone makes the top bar taller for any reason, and then it looks like their change broke the layout.
Constraints for whoever fixes it
One declaration instead of three. The comment directly above the rule already explains why the vertical padding is wanted, which is worth keeping: it was added so a wrapped translation grows the bar instead of being clipped.