Comment 2 for bug 1876906

If the other bug you linked to is set to 'confirmed', shouldn't this one be too?

Otherwise it is simply blaming the user for not understanding/knowing that chromium-browser's functionality is being broken by the use of Snap.