It’s hard to find/verify a chromium build that has auto-update and all the security features enabled. For the same reason I didn’t choose ungoogled-chromium… see ungoogled-chromium.
And Ubuntu’s snap chromium does not support keepassxc integration, which snap firefox does.
Unfortunately I’m lazy… the risk here is that some site tricks PW manager into submitting password, but should be fine if I set keepass to always popup with every request.
is it possible that this is because Chrom-(e | ium) has more aggressive unused tab unloading settings by default? Maybe manipulating these in FF’s config can improve things a bit? (no idea if it will help: just brainstorming)
Interesting I had the exact opposite result; firefox (non flatpak) running on fedora39 consumed 6w idling in the Desktop. Prorietary chrome (installed via official repo) was 8 or 9 watts doing the same.
Flatpaks changed thing a little but the trend was the same.