On Thu 2018-04-05 09:45:57 PM - KRT wrote:
> And the solution for privacy-minded folks then would be to either
> avoid QtWebEngine entirely, or else compile your own with these
> turned off at compile time? Seems like a hassle
but that is exactly why this is being discussed here
if it can b
On 04/05/2018 03:01 PM, Luke wrote:
>
> Per QT Docs, as long as QTLocation is not compiled then Google APIs for
> Geolocation should not execute.
> https://wiki.qt.io/QtWebEngine/Features#HTML5_Geolocation
Ah, ok, that makes sense. So, I browsed to http://browserleaks.com/geo/
in Falkon, and I
On 04/04/2018 11:53 PM, KRT Listmaster wrote
>>> I might not have time right away to start rebuilding Qt5 from source
>>> with different flags (it's a huge package, takes forever on my systems).
>>> I think the point of this exercise was to evaluate a stock browser
>>> based on QtWebEngine without
