@softyoda Welcome to the forum!
After looking into your screenshot, I’ve moved your post into this corresponding thread. It’s a known bug which seems to be resolved on extension version 2026.5.0. We only have to wait until Mozilla approves and releases that version on their extension store.