I'm not dismissing the issue you encounter: it is stupid and ugly.

I'm merely pointing out that your analysis of why it happens, is lacking.

It reminds me of customers who submit a feature-request or issue in the form of a concrete solution, rather than a good description of the problem they encounter.

"I want a dropdown with flags to switch to another language" vs "I cannot switch languages".

The latter presumes nothing, leaves the implementation to product-manager, -owner, UX designers or developers. The former is not only bad (flags for languages are stupid) it has a big chance of being dismissed entirely. Big chance the dev sees it and thinks "hmm, out of date, we already have that dropdown", but that due to a bug, setup, caching, incompatibility, browser-plugin or whatnot, it doesn't show up for the client.

I might have been a bit snarky? I skipped all the compliments and went straight to the point, but that's just me. All the information is there to reproduce the first issue, showing the wrong language in the wrong country.

My second statement wasn't a technical analysis but a principle one. One should not assume someone speaks the language of the country he or she is in. Plus, sometimes a country speaks more than 1 language.