Thanks for this – I was just assisting another user with a similar issue and because of your report I was able to notice (should have noticed right away tbh) that they were using Snap and was able to point them in the right direction. So thank you again for reporting.
According to this issue it actually appears to be an upstream issue where Chromium engine just uses default directories:
That said I cannot find an actual Chromium issue for this. Bringing this up with the team.