Firefox desktop · Research guidance. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
An embedded feature may involve another origin
A webpage can obtain a player or sign-in component from another site. Mozilla explains that cross-site cookie restrictions can affect website functionality. That is a reason to investigate a particular interaction, not proof that every external request is necessary or trustworthy. Identify the actual trusted page and failing action first.
A narrow change gives a narrow result
If a site-specific protection exception allows the feature to work, the finding concerns that page, browser and state. It suggests a compatibility relationship in the test. It does not show that all tracking protection is harmful or that every unrelated website should receive the same exception.
The change has a privacy consequence
Mozilla says disabling Enhanced Tracking Protection for a website reloads the page and allows trackers there. Treating it as a harmless picture-quality switch loses that consequence. Record the previous state, save unfinished page work and make the choice deliberately before repeating the failing action.
Restore before expanding the test
After noting the result, re-enable the preference you want to keep. Mozilla provides broken-site reporting for persistent compatibility issues. Avoid combining this test with extension removal, cookie deletion and an account reset; that would hide which change affected the embedded feature. A useful report can describe a public site and behaviour without exposing tokens.
Keep remaining questions separate
A working embedded window does not prove content entitlement, programme availability or ongoing reliability. Those remain questions for the actual service. State the browser finding separately from any later sign-in or playback error. That preserves the value of the test while avoiding a claim broader than the evidence supports.
Questions, answered
Does one successful exception justify a global change?
No. It supplies evidence about that particular case.
Is disabling site protection only cosmetic?
No. Mozilla documents its effect on trackers for that site.