Here’s a concise reply you can post back in that Community thread:
You’re absolutely right to be concerned – having the recorder suddenly flip to a different window in the middle of a Loom session is both disruptive and a potential privacy risk.
Loom itself controls this behavior (not Jira, Confluence, or the browser), and today there isn’t a setting in Atlassian products to change how Loom “sticks” to one window. The only workarounds on the Atlassian side are:
Use browser‑tab recording instead of full‑desktop
When you start Loom, pick “Current Tab” (or “Browser tab”) instead of “Screen” or “Desktop”.
Then stay within that tab while you record. If Loom is only capturing that tab, flipping to other windows won’t be recorded even if they come to the front.
Use a dedicated browser window just for the recording
Open a new browser window with only the content you want to show.
Start Loom capture on that window / tab only.
Keep all private content (email, chat, other apps) in another window you don’t bring to the front while recording.
Double‑check what’s being shared before starting
In the Loom picker, confirm whether you’re sharing entire screen, window, or tab. Entire‑screen sharing is the most likely to expose private content if focus changes.
If it’s clearly misbehaving, report it to Loom
If Loom actually changes the selected window mid‑recording (not just that you switched to another window while sharing your whole screen), that’s something Loom Support should look at directly:
https://support.loom.com/
From the Atlassian side, if you’re embedding or using Loom to record walkthroughs of Jira/Confluence, the safest pattern is usually: “new window + tab‑only recording”.
If you paste the exact steps where the window flips (OS, browser, whether you use Loom Chrome extension or desktop app, and what share option you pick), I can help you phrase a precise bug/feature request for Loom as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.