Firefox desktop · Research guidance. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Establish the failure before changing privacy controls
Write down what fails: an embedded player never appears, a sign-in handoff loops or a button does nothing. Confirm that it happens consistently on the intended trusted website. A general dislike of an error message is not a reason to grant wider permissions to an unrelated page or an unknown download prompt.
Read the site’s protection panel
Mozilla documents a shield panel for the active site. It can show and change Enhanced Tracking Protection for that website. The publisher notes that cross-site restrictions can affect some site functions. That makes a controlled site-specific test reasonable in a suitable case; it does not establish that every blocked resource is necessary or harmless.
Keep the change confined
If you choose to test an exception, record the previous state and change only that trusted site. Mozilla says turning the site protection off reloads the page and enables trackers there. Treat that as a real privacy change, not merely a cosmetic playback switch. Save unrelated work on the page before a reload.
Repeat one observable action
Try the same failing action once and compare the result. If several other settings are changed at the same time, you will not know which difference mattered. A working player after the exception suggests a compatibility relationship in that case; it does not prove that global protection should remain disabled.
Restore and report the useful result
Re-enable the protection when the diagnostic test is finished unless you deliberately choose a lasting exception. Mozilla provides broken-site reporting for persistent compatibility problems. Report the public site, browser and observed behaviour without sending private account links. The result is a narrowly described test, not a claim of universal browser or UK IPTV support.
Questions, answered
Is the site exception a privacy-neutral action?
No. Mozilla says disabling protection for the site enables trackers there; keep the test deliberate and scoped.
Does one successful test justify disabling protection globally?
No. Preserve the narrow evidence and restore the preference you want.