[Bug]: Desktop: Dialog scrim doesn't dim artwork or backdrops

Ouverte
#126 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
50/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
rust
Domaine
desktop

Piste de recherche

Start at the scrim in desktop/app/src/ui/overlay.rs:22, then find where the poster, card and title-backdrop primitives are drawn and how their draw order relates to the scrim layer. Reproduce with cargo run --locked -- --scene discover --snapshot /tmp/a.png versus --scene add, and the same for title versus releases, comparing pixels. Done means every element behind an open dialog dims while the dialog panel still covers correctly.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

bug

[!NOTE]
This issue was written by Claude (Claude Opus 5.5) from a review session of the desktop app (#80) with @PhrolovaMoe. It was found in headless renders of the debug build's fixture scenes (--snapshot), not on a live server.

Version

0.40.0 (feat/desktop, 017a837b)

Area

Other (desktop app)

What happened?

Behind a dialog, text and panels are dimmed by the scrim (desktop/app/src/ui/overlay.rs:22), but posters, cards and the title backdrop aren't: their pixels are identical with and without the dialog open. They're drawn by custom shader primitives, which end up on top of the scrim. The dialog panel itself still covers them correctly.

Steps to reproduce

From desktop/, with a debug build: compare cargo run --locked -- --scene discover --snapshot /tmp/a.png with --scene add --snapshot /tmp/b.png: the poster at the left is just as bright in both. Same for --scene title vs --scene releases (the backdrop).

Expected behavior

Everything behind a dialog dims the same way.

Suggested fix

Draw the scrim (and the dialog) in a layer above the primitives, or have the artwork/backdrop primitives take the dimming into account while an overlay is open.

Langage dominant
TypeScript
Étoiles
4
Forks
1
Merge moyen
4 h 49 min
PR mergées (30 j)
5

Préparer son environnement

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Aucun modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de tinystream-dev/tinystream

Toutes les issues de tinystream-dev/tinystream

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.