Broken Enhanced Tracking Protection options
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Dart
- Estrellas
- 1k
- Forks
- 41
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FaFre/WebLibre
-
bug enhancement needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
-
French app translationAbiertoenhancement needs-triage
Dificultad 3/5 1-2 días Aptitud para principiantes 60/100
-
Chromium based weblibre.Abiertoenhancement needs-triage
Dificultad 5/5 Más de una semana Aptitud para principiantes 8/100
-
bug enhancement needs-triage
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
-
needs-triage
Dificultad 4/5 1-2 días Aptitud para principiantes 48/100
Todos los issues de FaFre/WebLibre
Issues similares
-
bug from-telegram platform:windows
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
hiddify/hiddify-app#2592 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
cogwheel0/conduit#1122 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
夜間レビュー: 観点 tests の指摘 (PR #774)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
bannzai/shoppinglist#779 ·
Los mantenedores suelen responder en 1 día
-
Android bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
PostHog/posthog-flutter#731 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[BUG] JEFIT import fails because # characters are not recognisedPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertobug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día