Screenshot, Copy, New from Clipboard in Preview.app, Tools -> Text Selection, select your text. Hack the planet.
And yet... https://pbs.twimg.com/media/EAsh47yWwAAxU1m?format=jpg&name=...
421–430 of 621 posts
Screenshot, Copy, New from Clipboard in Preview.app, Tools -> Text Selection, select your text. Hack the planet.
And yet... https://pbs.twimg.com/media/EAsh47yWwAAxU1m?format=jpg&name=...
Not allowing text selection, disabling scrolling where there should be scrolling, disabling autocomplete/text substitutions, or corrupting the Back/Forward buttons...
Websites are guilty of this more often than apps, which usually just do whatever the device OS allows.
Even worse are the outright LIES that even Apple has been guilty of for a while now:
• Refreshing a webpage doesn't really refresh it. (it's less fresh than entering the URL in a new tab/window)
• Going back doesn't really go back. (It loads the URL again..absolutely disgusting on YouTube when you want to go back to an interesting thumbnail you noticed too late, but it's not there anymore)
• Force-quitting an app doesn't really quit it. (Now iOS still gives them a noticeable bit of time to ponder which is annoying when you open that app again right away)
Not to mention the outright privacy and security violations like textboxes that send keystrokes home.
I must admit, one of my favorite recent-ish Android[1] features is that all text is made selectable in the app switcher using on-device OCR. Regardless of the app[2], you can just swipe up and start selecting text. [1] ...at least on the Google Pixel. [2] ...unless it's a banking app and it blocks permissions for screenshots and similar things.
On iOS you can create a shortcut to push a screenshot through the built in OCR and copy to clipboard. You need to crop beforehand if you don’t want all the text on the screen. https://imgur.com/a/NctIGsK
I have a habit of selecting and highlighting text on computer screens, while reading. I have no issues tracking lines usually, but somehow I still select and highlight. Maybe it is just easier to track lines this way. When I see some web page, that prevents this, then that website gets a -50 reputation score out of 100 in my book. So if the site is perfect in every other way (almost no site is) then -50 still makes i…
> I have a habit of selecting and highlighting text on computer screens, while reading. "There are dozens of us!"
I have a habit of selecting and highlighting text on computer screens, while reading. I have no issues tracking lines usually, but somehow I still select and highlight. Maybe it is just easier to track lines this way. When I see some web page, that prevents this, then that website gets a -50 reputation score out of 100 in my book. So if the site is perfect in every other way (almost no site is) then -50 still makes i…
Earlier quoted context omitted.
isn't selectable because it breaks the UX for keyboard-only users. Has nothing to do with "thinking" anything. It's about testing with accessibility parameters and knowing* what practical problems occur. If you really need to translate ONE WORD, it's not that onerous to type it. You're bringing edge-case hypotheticals to a discussion about practical functionality.
> If you really need to translate ONE WORD, it's not that onerous to type it. I'm confident that I can type just a tiny fraction of all Latin characters all world languages use. I'm sure that pretty much any Vietnamese word is way beyond my keyboard layout. No clue about writing any non-Latin script. Can you type any Cyrillic, Kanji, Hebrew, Abjad, …, character you see?
As 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…
Dude is right, most of this non-selectable web can be served as images from a back-end. We have both the server power and network to do it, perhaps is going to be in many cases be faster than all the React/Angular slop on top of simple UIs in 2025.