Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug] Webpages with NO DARK THEME tag are not darkened while browsing

Aperta
#15,509 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
50/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
typescript
Ambito
frontend

Direzione di ricerca

Inizia con la voce di detector-hints.config per tidal.com e riproduci la transizione da https://tidal.com/about a https://tidal.com/supported-devices senza aggiornare. Confronta la transizione con un ricaricamento tramite F5 e verifica che la navigazione applichi in modo coerente il comportamento previsto di oscuramento o esclusione, incluso il caso simile di simplywall.st.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Prerequisites
  • I searched for any existing report about this bug to avoid opening a duplicate.
  • I can reproduce this bug in a new, unmodified web browser profile with Dark Reader installed as the only extension.
  • I understand I need to use the Broken Website Report template if this bug I am reporting occurs on a single website.
Bug Description

When browsing a given website and transitioning from a page where dark theme is detected to a page that has NO DARK THEME tag and back, the new page is not processed accordingly.

Website Address

https://tidal.com/about

Steps To Reproduce

Open -> https://tidal.com/about

Image

Notice that a native dark theme is detected on this webpage.
Now click on "Support" -> "Supported Devices" near the top right corner.
A new page will open with URL -> https://tidal.com/supported-devices
Note that this URL has the NO DARK THEME tag at the detector-hints.config file.
This page should be darkened, but instead it looks like this:

Image

Now you refresh the webpage by hitting the F5 key, and it looks like this:

Image

as it should be in the first place!

Expected Behavior

Dark reader should handle these transitions and update the webpage if needed.
The new webpage should be dark as well.
The purpose is to darken all webpages.

Actual Behavior

This also happens while browsing other websites such as -> https://simplywall.st/
Which also has pages that are processed by dark reader and others that should be ignored by it.

You can put webpages under the "Invert listed only", and under "Not invert listed", and if you are transitioning from webpages that are under the same website, you may observe this undesired behavior.

When you are transitioning from webpages that are handled by dark reder to webpages that should be ignored, sometimes dark reader processes the webpage when it should not.
It happens the other way around as well!

Screenshots

No response

Operating System

Microsoft Windows 11

Web Browser name and version

Microsoft Edge Version 148.0.3967.96 (Official build) (64-bit)

Dark Reader version

4.9.125

Additional Context

No response

Lingua principale
TypeScript
Stelle
22.4k
Fork
2.8k
Merge medio
22h 56m
PR unite (30g)
61

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di darkreader/darkreader

Tutte le issue di darkreader/darkreader

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.