this post was submitted on 29 Jun 2023
106 points (100.0% liked)
/kbin meta
4 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
While that wouldn't exactly be a nice way to word it, monolingual designers designing for monolingual use cases is a huge issue that crops up a lot.
For example, you used to be able to right click a text input field in Chrome and directly select the language for the spell checker. Then they changed it and said, multilingual people should just select all the languages they speak, and the spell checker will just allow every word as correct that appears in at least one language.
That's a horrible solution, because you frequently have similar words in multiple languages spelled differently, so that the word in a different language just masks a typo. For example, compare grass (English) to Gras (German). If I am typing a German sentence and accidentally type it with two s, the spell checker will not flag it.
Anyone who frequently uses multiple languages would instantly know that that's bad design, but apparently the person who designed this doesn't speak multiple languages.
As far as I can remember, there was a shitstorm and they reverted the change. It's been a long time since I used Chrome.
No disagreement here, I have a lot of gripes with the state of UX design. I don't understand why the majority of my 1440p screen is empty space when browsing the web, to give an easy example. One of my displays is vertical, which seems incredibly useful until you try to use it and realize nothing scales in any usable manner on a portrait display. I digress...