Broken Enhanced Tracking Protection options
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 25/100
Direzione di ricerca
The payload names no files, so start by reproducing the Standard, Strict and Custom results on the adblock test site in the Enhanced Tracking Protection settings. Then find where the Custom mode forces ads and analytics to be blocked and how the Tracking Content option maps onto the Gecko content-blocking settings. Done needs a maintainer decision on whether that forced ad protection becomes its own toggle, which the thread has not yet settled.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Recently found out about Libre on Android and seeing the feature set instantly made me switch to it. Seeing how it was a robust and flexible yet privacy focussed browser unlike others which usually block or lock options out of users hands, I had high hopes for it. Which still remain high and I'm quite excited to continue using it. Nonetheless, in the initial testing I kinda came upon a glaring issue. Unsure if it is a bug, or that's the direction Libre team/dev went in.
Unlike firefox, where the ETP has defined exactly what each option blocks (you can see that with the little i icon). Unlike Standard, Strict also blocks something called Tracking Content. The description of which says
Tracking Content: Stops outside ads, videos, and other content from loading that contains tracking code.
And the Custom mode, which only states it blocks social media trackers and the rest is user controlled. When tested through an ad blocking site https://adblock.turtlecute.org/ it all corroborates just fine.
Coming back to Libre and its ETP, disregarding the exclusive privacy and hardening options, when I tested the ETP, all standard, strict and custom (with no options checked) all gave the same result. Consecutively, for some reason in the custom mode in libre states
Ads, analytics, social trackers, and Mozilla social trackers are always blocked in Custom mode
Which is .. exactly what the Tracking Content option is for. Which kind of makes it redundant. In fact, Libre even turns it around and somehow... Has a different description of that option. Which, does make sense. Since it's for tracking it should be for scripts and tracking resources to be blocked.
But a forced Ad protection? Why not just have it as a separate toggle like the rest? And worse, seeing how on standard and strict also gave the same result it seems that the ad blocking option seems to be constantly active in all three options, which should not really be.
If there's an option to provide logs I'd be happy to other than that I only have screenshots.
For the test on adblock test site, I made sure not to have any doh on device or in browser. It was all my ISP. No other ad blockers used. And always cleared the sites cookies before each test. I would request and suggest that the ETP work the same as firefox's ETP given how flexible and use choice driven the rest of the privacy options are.
- Lingua principale
- Dart
- Stelle
- 1k
- Fork
- 41
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di FaFre/WebLibre
-
bug enhancement needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
-
French app translationApertaenhancement needs-triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 60/100
-
Chromium based weblibre.Apertaenhancement needs-triage
Difficoltà 5/5 Più di una settimana Idoneità per principianti 8/100
-
bug enhancement needs-triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
-
needs-triage
Difficoltà 4/5 1-2 giorni Idoneità per principianti 48/100
Tutte le issue di FaFre/WebLibre
Issue simili
-
bug from-telegram platform:windows
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
hiddify/hiddify-app#2592 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
cogwheel0/conduit#1122 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
bannzai/shoppinglist#779 ·
I maintainer di solito rispondono entro 1 giorno
-
Android bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
PostHog/posthog-flutter#731 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
[BUG] JEFIT import fails because # characters are not recognisedForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno