Gecko cannot fake Chrome
AdsPower dual-engine contradiction, FlowerBrowser Gecko vs Chrome.
FlowerBrowser runs on Gecko, yet a profile can claim to be Chrome. That is the whole problem, and it shows up in two checks any page can run.
We tested headed and headless runs across Windows, macOS, and Linux, all OS profiles, and compared each one with genuine Chrome.
First, CSS.supports('-moz-appearance: none') returns true in FlowerBrowser and false in genuine Chrome. Second, error stacks use the SpiderMonkey @ format, while V8 frames start with 'at '. The profile also carries Chromium shims it should never have: window.chrome, navigator.userAgentData, and Chrome PDF Viewer.
We wrote this blog to show why this is not a fingerprint setting to tune. The contradiction lives in the engine itself, so every profile built on it carries the same trace.
Software Prince engineers custom Chromium builds from source, with one engine, one identity, and no shim answering for the browser, because the engine has to be clean, not patched after the fact.
Read the article here: https://programmingkings.com/blog/detecting-adspower-dual-engine-contradictions-extension-leaks?s=linkedin&m=company&post=48
Book a short call below
Our Social Media Channels
Follow this story and join the discussion across our verified networks: