Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Viewing Tiktok profiles breaks with privacy.resistFingerprinting=true

  • 5 fhreagra
  • 1 leis an bhfadhb seo
  • 1 view
  • Freagra is déanaí ó zeroknight

ranidspace
ranidspace
more options

When viewing any tiktok account profile page, for example this one , the videos do not show up, and says "Something went wrong, Sorry about that! Please try again later."

Here's what i did:

  1. Created new Firefox profile with default settings and no extensions
  2. Visited a TikTok profile, and saw it opens as expected
  3. Changed privacy.resistFingerprinting to true
  4. Refreshed the TikTok profile page, and the error message shows up

I opened the console and compared and there were new warnings:

  • Blocked https://www.tiktok.com/@tiktok from extracting canvas data because no user input was detected.
  • Get user detail failed for getting wrong response

And 3 errors, when there were 0 before, all three read

  • Uncaught TypeError: _0x5e9eb8[_0x2bd187] is null
When viewing any tiktok account profile page, for example [https://www.tiktok.com/@tiktok this one] , the videos do not show up, and says "Something went wrong, Sorry about that! Please try again later." Here's what i did: # Created new Firefox profile with default settings and no extensions # Visited a TikTok profile, and saw it opens as expected # Changed privacy.resistFingerprinting to true # Refreshed the TikTok profile page, and the error message shows up I opened the console and compared and there were new warnings: * Blocked https://www.tiktok.com/@tiktok from extracting canvas data because no user input was detected. * Get user detail failed for getting wrong response And 3 errors, when there were 0 before, all three read * Uncaught TypeError: _0x5e9eb8[_0x2bd187] is null

All Replies (5)

Terry
Terry
more options

Yes, enabling that preference causes errors.

ranidspace
ranidspace Úinéir na ceiste
more options

Terry said
Yes, enabling that preference causes errors.

im aware. hence why im posting about it

zeroknight
zeroknight
more options

Disable privacy.resistFingerprinting (RFP) and use the new fingerprinting protection (FPP) instead which allows disabling it per-site and fine-grained control of protections. The following useragent exception allows TikTok profile pages to load: 

privacy.fingerprintingProtection = true
privacy.fingerprintingProtection.overrides = +AllTargets,-NavigatorUserAgent
ranidspace
ranidspace Úinéir na ceiste
more options

zeroknight said
Disable privacy.resistFingerprinting (RFP) and use the new fingerprinting protection (FPP) instead which allows disabling it per-site and fine-grained control of protections. The following useragent exception allows TikTok profile pages to load: privacy.fingerprintingProtection = true privacy.fingerprintingProtection.overrides = +AllTargets,-NavigatorUserAgent

At the moment i really cant find much documentation at all as to what FPP does. It appears to have been added in v120 but there's nothing at all I can find as to what it actually does. I trust it's good, but I want to know what i'm losing by disabling what I have on right now

zeroknight
zeroknight
more options

FPP is provided under the "Suspected fingerprinters" setting. It only has a few protections by default but with the +AllTargets override it should match RFP. You can test it on sites like browserleaks, if you notice any difference it would be considered a bug.