361–370 of 621 posts
Earlier quoted context omitted.
on Mac/iOS you can just take a screenshot and then select out of the image.
Google pixel devices have had this for years. It's one of the few things that keeps me glued to this platform. Just push the button to go to the task switch view and as long as the window preview thumbnail isn't blanked out, I can just get the phone to OCR any part of the screen in real time.
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…
sure there's the accessibility zoom, but it's somewhat clunky. zoom and clipboard should be consistent, non-optional and handled by the os ui layer.
It doesnt stop any of the behaviours they think they are while making their site all the worse for actual users. All it does is give the author the illusion that its protecting their site's content while making the experience noticeably worse.
Earlier quoted context omitted.
Recently I've been considering simple click-to-copy button is a bad ux since it can destroy one's clipboard (granted, I'm not using clipboard manager). This might be mitigated with a confirmation before actually replacing the clipboard, but I haven't encountered such implementation. Maybe due to ctc more often appear in tech-related websites.
Instead of click-to-copy, you could do click-to-highlight, so that "right-click > Copy" highlights the text on right-click if it's not initially selected. There is some subtlety in the logic, because it shouldn't interfere when the user manually selects a substring. For a demo of click-to-highlight, install IPvFoo and use your mouse in the popup window. See the 'selectWholeAddress' function in https://github.com/pmar…
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…
100% disagree. Not everyone is fluent in every language, and not every website works perfectly with the browser's translator. There will be situations where people will want to translate that ONE word that is actually in a button or tab, and isn't selectable because someone thought they knew better.
It's much less frustrating when you can copy-paste the damned labels straight off the site/app, than retyping them and hoping you didn't misspell FooBar as FooBaz, leading the other person into deeper trouble rather than helping.