We seem to have very different concepts of either what is "easy" or fine motor skills.
I also find it rather difficult to point my phone at itself when trying to translate a word it's currently displaying; but maybe that's also a skill issue.
One involves clicking just before the button and dragging to just after the button (or vice versa).
The other involves opening a screenshot tool, selecting a rectangle, going to a website (that I might have to pay for?), pasting the image, waiting some seconds to cause global warming, getting some text back, clicking just after that text to just before that text.
How is that a similar level of effort?
The first I could walk someone who had never used a computer through over the phone in 1995. The second I wouldn't want to walk some of my coworkers through today.
I consider this a bad faith comment given the amount of detail you described taking a screenshot vs copying the text.
Anyway, it's not a noteworthy amount of effort, no. If your text selection of the button was blocked, which is the whole point of this discussion, the other methods would be a fine alternative. Or would you give up because it's too much effort?
I just tried both on the reply button for this very comment box.
> One involves clicking just before the button and dragging to just after the button (or vice versa)
This didn't work. Text is not selectable. Do you know why it doesn't work? Because user-select: none is the default user agent style on input[type=submit].
How about the screenshot?
- keyboard shortcut for screenshot
- click and drag
- click chatgpt tab
- keyboard shortcut for paste
How about the phone app?
- open translate app
- tap camera
- point at button
Again, neither of these were a noteworthy amount of effort.
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.