Chrome, Firefox and Safari on desktop · Research guidance. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Identify the scope of the sound
Keep the intended programme playing at a reasonable level and note whether another tab or window could contain media. A second source can sound like a programme fault. Do not change every system output or account setting at once; first establish which browser context is actually producing the unwanted sound.
Inspect the browser’s source controls
Google documents Chrome’s Media control, including a route back to the tab containing the media. Mozilla documents a speaker button on a sounding Firefox tab. Apple describes holding Safari’s Audio button to list sounding websites. Use the relevant current interface rather than assuming all browsers expose the same button or shortcut.
Change one source at a time
Select the identified tab and pause its own media if that is the intended result. Tab mute is available in supported browsers, but silencing a source is a different action from pausing its timeline. Avoid closing an unrelated unsaved form merely because its tab is near the one with the audio indication.
Retain the exact observation
Record which tab produced the sound and which control stopped or silenced it. If the intended programme still has an audio problem after the other source is controlled, investigate that separately. A sound indicator does not establish a service’s connection allowance or whether another account device is watching; it describes the browser context actually observed.
Questions, answered
Can Chrome media continue after switching tabs?
Yes. Google explicitly describes that behaviour.
Is muting necessarily the same as pausing?
No. Inspect the actual playback state.