From 8070a3a8ea8113d726edde94743cc9df1256035f Mon Sep 17 00:00:00 2001 From: lebaudantoine Date: Fri, 21 Aug 2026 15:51:49 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=90=9B(frontend)=20stop=20init=5Fvirtual?= =?UTF-8?q?=5Fbackground=20from=20firing=20on=20blur=20updates?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A regression introduced with the custom virtual background feature (16daf7b8, March 26): every blur init on Firefox, and every update call, was going through `init_virtual_background`, which raised an error because there is no virtual background to initialize in that code path. The existing guard was incorrect. Replace it with an early return, so `init_virtual_background` is only executed when there is actually a virtual background to initialize. This does not fix the other virtual background issues that currently prevent some users from activating their camera; those will be addressed separately. --- .../livekit/components/blur/BackgroundCustomProcessor.ts | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/frontend/src/features/rooms/livekit/components/blur/BackgroundCustomProcessor.ts b/src/frontend/src/features/rooms/livekit/components/blur/BackgroundCustomProcessor.ts index 9259a961..73896e7a 100644 --- a/src/frontend/src/features/rooms/livekit/components/blur/BackgroundCustomProcessor.ts +++ b/src/frontend/src/features/rooms/livekit/components/blur/BackgroundCustomProcessor.ts @@ -105,9 +105,7 @@ export class BackgroundCustomProcessor implements BackgroundProcessorInterface { _initVirtualBackgroundImage() { if (this.options.type !== 'virtual') { - throw new Error( - 'Virtual background is only supported for virtual background' - ) + return } const needsUpdate =