You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The error banner is a faint red strip over the top bar that cannot be read or closed #708
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.
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
.errorclass instatic/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
Being worked on in the
feat/song-identificationbranch.