171–180 of 621 posts
Earlier quoted context omitted.
The article doesn't have selectable text.
Yeah that was the point. Disabling text selection also inhibits cursor movement even without selecting anything.
Earlier quoted context omitted.
by pointing your phone at it by screenshotting it and copying the text out of the screenshot by putting a screenshot itself into chatgpt I'm curious what real world scenario you've imagined yourself in with a kanji button that you don't understand within the rest of a website in kanji that you do understand, but don't know how to type kanji?
Would you say any of these are "not that onerous" compared to copying the character? The argument here isn't that it's _impossible_ to do that with copying disabled, it's that it's _more annoying_. By providing a list of _more annoying_ ways to do something, you're reinforcing the argument, not refuting it.
yes it's absolutely just as easy to point my phone's translate app at the button.
any more questions?
Earlier quoted context omitted.
Yeah, I removed the "glyphs" thing from my comment, because I realized they were SVG backgrounds, not actually text, but that is a common place to use user-select: none, on elements with font faces that are symbols. I am curious what operating system you can select text from the buttons on though. I might spin up browserstack to experiment.
macOS Safari
This is what is copied from the login page, you can see that the button text is missing:
Login
username: password:
Forgot your password?
Create Account
username: password:
I often find myself having the tiniest of complaints about using something but never get around to writing about it.
Earlier quoted context omitted.
Inside the button? Not the link? What OS/Browser?
I just tried this with every major OS and browser. I don't think it is possible. You can highlight the buttons (most times) in Safari on MacOS, but you can't select the text and copy it or translate it.
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…
Real-world example I use nearly daily: Selecting the nav header that's the ticket number in our ticketing system. I copy-paste the number elsewhere. Of course there are many other bad design decisions that go into requiring me to do this, but it's still a real example of why all text should be selectable.
This is a standard UI convention used by all internal dev tools at my current company.
- can’t select app reviews text (for translation for example)
- WhatsApp text bubbles don’t let you select text inside at all
- WeChat: exact same
Overall, it’s also very annoying when apps just don’t give you the standard OS options for a field. Like WhatsApp or WeChat does not give you access to the normal contextual menu at all, so no "translate" for your messages outside of what is or isn’t supported by the app itself, etc.
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…
It is super annoying to be clicking back and forth through tabs only to have some text erroneously highlight and then stay that way. It's more annoying when your web site won't let me copy a package tracking number to paste into my chosen package tracking program. Maybe I don't want to use your system. Maybe the program I have is better. Just because a web dev can't think of any reasons someone would want to copy tex…
Earlier quoted context omitted.
You can do better than doing personal attacks. The article is not advocating for breaking anything. And unlike me you haven't provided a single example so far, only workarounds for people who don't like your suggestions.
[flagged]
In your original post you say "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" and you explicitly mention that you leave out anchors.
So far no reply to me has talked about problems causing by having selectable "tab headers, buttons, or even text-sparse tiles".
I am still 100% open to hearing about it. But I can do away with the personal attacks and sarcasm.