Skip to content

The error banner is a faint red strip over the top bar that cannot be read or closed #708

Description

@thcp

What happens

When an import, export or playback fails, the message appears as a strip across the top of the studio: positioned 64 px from the top, a 12% red tint, pale red text. Whatever sits underneath shows through the tint, so over the busy top bar the message is barely legible. A user reported it with a screenshot: "the error message shows a red banner that is barely visible ... i cant read/close or vanish that".

The only way out is the single button inside it. For an import failure that button is "Try again", which hides the banner and moves focus to the URL field. There is no separate close control, and Escape does nothing.

It gets worse because the banner's styling lives on the bare .error class in static/css/daw.css ("Error banner"), not on the banner element. Any small status line that marks itself as an error with the same class modifier is pulled out of its panel and floated to the same spot. On main that is the stems location message in Settings (.stems-location-msg.error). With song identification, the lyrics tab's "Could not reach LRCLIB", the artist box and the AcoustID key message do the same. Those lines have no button at all, so they sit over the extraction row, overlapping the stem buttons, with no way to read or dismiss them.

Who it affects

Anyone who hits a failure. The banner is the studio's only alert surface: import failures, export failures and playback failures all go through it. A message that cannot be read is close to no message.

Constraints for a fix

  • It has to stay prominent. A failure that goes unnoticed is the problem [Bug]: A background import that fails tells the user nothing #375 was about.
  • Readable against any background, which rules out a translucent tint over whatever is below it.
  • Always dismissable, by a button and by Escape, whether or not the failure offers "Try again".
  • It must not cover the URL field, since "Try again" sends the user there.
  • Status lines that mark themselves as errors have to stay inside their own panels.

Being worked on in the feat/song-identification branch.

Activity

  1. added
    bugSomething isn't working
    on Sep 27, 2026
  2. self-assigned this
    on Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions