From 35d4c94d54cd8b0e634b4ccc640b86ca3e2e52af Mon Sep 17 00:00:00 2001
From: Thore Cimbal <cfx@riot.8shield.net>
Date: Wed, 29 Jul 2026 07:33:41 +0200
Subject: [PATCH] revert: remove VP9/AV1 from codec dropdown (Issue #11)

Live testing confirmed selecting VP9 always falls back to VP8 - SFU's
active codec allow-list never actually included it despite the
server-side config being deployed, root cause not yet identified.
Back to the known-working VP8/H.264/H.265 options.
---
 src/settings/MediaQualitySettings.tsx | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/src/settings/MediaQualitySettings.tsx b/src/settings/MediaQualitySettings.tsx
index d47e0b10..46bd6c7c 100644
--- a/src/settings/MediaQualitySettings.tsx
+++ b/src/settings/MediaQualitySettings.tsx
@@ -122,12 +122,13 @@ export const MediaQualitySettings: FC<{
             <label htmlFor={`${id}Codec`}>
               {t("settings.codec_label", "Codec")}
             </label>
-            {/* Only list codecs the SFU actually accepts right now (confirmed
-                live via matrix-rtc-sfu negotiation logs, 2026-07-28 -
-                enabledPublishCodecs was [VP8, H264, H265]). VP9/AV1 are not
-                currently negotiated by the SFU - selecting them silently
-                falls back to VP8 via the client's backupCodec, so leaving
-                them out avoids offering a choice that has no real effect. */}
+            {/* VP9/AV1 tested live 2026-07-29 (Issue #11) after enabling them at
+                the SFU: even on a real VP9-capable browser (Firefox, fresh
+                rejoin) publishing silently fell back to VP8. SFU logs showed
+                the server-side codec allow-list never actually included
+                vp9/av1 despite the config being deployed - root cause not
+                conclusively identified (see Issue #11). Left out until
+                that's understood and fixed. */}
             <select
               id={`${id}Codec`}
               value={codec}