Agreed. Reading the clipboard should require the user to choose "paste" just like the browser does. You can't read it unless the user expressly trying to paste into your app.
It used to be true but all that was fixed like 10 years ago.
I wouldn't expect that most people would double-check to make sure a series of gibberish characters matches what they expect, especially if they don't have any reason to suspect that paste wouldn't output exactly what they copied a moment ago.
It's somewhat similar to how Firefox has disallowed auto-playing videos except on user permission or a user-triggered event.
Which has been mostly worked around by the bad actors, who use things like mouse-over or scroll to trigger the event.
Somehow I didn't even realize that's how they were getting around it! I just thought, "Dang, I thought I turned that crap off." Good callout.
“Click Reject All Cookies to exercise your GDPR rights!”
Don't know about a repo, but https://developer.mozilla.org/en-US/docs/Web/API/Clipboard_A...
Accessibility apps likely have a lot of examples like this too
It does require a user initiated event to work, but then you can access the user's clipboard with:
`await navigator.clipboard.read();`
There are some additional restrictions though (you can read them in the first link) which it might make sense for iOS as a whole to adopt.