AdguardTeam / AdguardTeam/AdguardBrowserExtension

csp rule with $domain does not work on the first page load from NTP

Offen
#3,579 0 Kommentare 1 Reaktion 1 zugewiesene Person Zugewiesen an @maximtop Auf GitHub ansehen
Bug MV3 Priority: P4 Version: AdGuard v5.6
Vorherrschende Sprache
TypeScript
Sterne
4.4k
Forks
449
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### Please answer the following questions for yourself before submitting an issue

- [x] Filters were updated before reproducing an issue
- [x] I checked the [knowledge base](https://adguard.com/kb/) and found no answer
- [x] I checked to make sure that this issue has not already been filed

### AdGuard Extension version

5.4.3.85

### Browser version

Chrome 150.0.7871.47

### OS version

Windows 11 Pro

### Ad Blocking

AdGuard Base filter

### Privacy

_No response_

### Social

_No response_

### Annoyances

_No response_

### Security

_No response_

### Other

_No response_

### Language-specific

_No response_

### What Tracking protection options do you have enabled?

_No response_

### Issue Details

See https://github.com/AdguardTeam/AdguardFilters/issues/202431#issuecomment-4829240042 and Adam's reply. No such issue for the MV2 extension.

### Expected Behavior

`$csp,domain=` should work equally as `$csp,to=`

### Actual Behavior

Only `$csp,domain=` does not work, and only on the first load from new tab page.

### Screenshots

NA

### Additional Information

_No response_

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.