Just let me select text
111–120 of 621 posts
Re: Just let me select text
#112... alright I see...
>"(Because Tinder is a rape-friendly lure trap.)"
I just sat down. Who the hell starts a conversation off like this?
Re: Just let me select text
#113Earlier quoted context omitted.
Good UX means including translations for supported languages, not telling the user "do it yourself by highlighting content". Not translating entire articles to a language you don't support has the easy remedy of letting people select the text and use third party tools to support their specific use-cases. But not including translations for your clickable content for languages that aren't supported are the literal prac…
What about unsupported languages?
Re: Just let me select text
#114As a web dev, I fully agree with this, but with a huge exception: clickable text. Anything that is meant to be read as content should absolutely, without fail, be selectable and copyable (assuming appropriate permissions). But stuff like tab headers, buttons, or even text-sparse tiles - things meant for the user to click on - can, and usually should , prevent text selection. It is super annoying to be clicking back a…
Re: Just let me select text
#115On Android, long press home button activates Google Assistant that can OCR the current screen and translate immediately. Unironically one of the only two features keeping me on Android until now.
Re: Just let me select text
#116you're saying that you load images, even store in my cache - but simply disallow same UX you allow on other images? wtf
Re: Just let me select text
#117Earlier quoted context omitted.
Same way I do: with your OS's on-screen keyboard.
Congratulations on being fluent in Hanzi, I guess, but that does not solve a problem for the vast majority of the users.
But that's not what the topic is. The topic is HOW developers should accomodate users. And I'm simply taking the stance that preventing user selectability is a lesser evil in specific cases than universal selectability, because the former can be mitigated with less scripting overhead than the latter.
Re: Just let me select text
#118As a web dev, I fully agree with this, but with a huge exception: clickable text. Anything that is meant to be read as content should absolutely, without fail, be selectable and copyable (assuming appropriate permissions). But stuff like tab headers, buttons, or even text-sparse tiles - things meant for the user to click on - can, and usually should , prevent text selection. It is super annoying to be clicking back a…
Re: Just let me select text
#119Earlier quoted context omitted.
What's that behavior? Do you have an example of a website where selectable text makes keyboard navigation not possible? Could this be a browser problem? I can tab between links here in HN and it's perfectly also selectable.
Try to navigate inside the article, it doesn't work at all.
Re: Just let me select text
#120As a web dev, I fully agree with this, but with a huge exception: clickable text. Anything that is meant to be read as content should absolutely, without fail, be selectable and copyable (assuming appropriate permissions). But stuff like tab headers, buttons, or even text-sparse tiles - things meant for the user to click on - can, and usually should , prevent text selection. It is super annoying to be clicking back a…
How do you do this?
> can, and usually should, prevent text selection
Please don't. You're overthinking. Be a better designer by designing less.