Sergey M.

@kanlanc What are you going to do in the PR?

@kanlanc Ok! If you use StackBlitz or a similar service, please share the full access to the sandbox with @makma.

@kanlanc Any progress on this?

Maybe a related issue: https://github.com/karma-runner/karma-browserstack-launcher/issues/142

I haven’t searched for ways to suppress the requests in the network tab. I don’t consider it as a problem. The requests are produced by iframes used to encapsulate DOM...

Some problems that the iframes (producing the `about:blank` requests) solve: - https://github.com/fingerprintjs/fingerprintjs/issues/592 - https://github.com/fingerprintjs/fingerprintjs/issues/628 We can make a non-iframe solution specially for Safari, but it will increase the complexity of...

A potential solution is creating iframes with a fake custom URL scheme, e.g. `iframe.src = 'ieuuaskl:'`. A quick test shows that it leaves no traces.

@Valve The issue is still relevant for v3. I think we should solve it.

Hello @mmsm1381. I can't reproduce this. Provide steps to reproduce the bug please. Send us debug data for the different fingerprints also so that we can see what causes the...

Try printing the fingerprint components in addition to the visitor id on your website: ```js fpPromise .then(fp => fp.get()) .then(result => alert(result.visitorId + '\n' + JSON.stringify(result.components, null, 2))) ``` I...