Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Pasting text not always possible #1144

Open
1 task done
paulmelis opened this issue Nov 5, 2023 · 0 comments
Open
1 task done

[BUG] Pasting text not always possible #1144

paulmelis opened this issue Nov 5, 2023 · 0 comments

Comments

@paulmelis
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When creating a new post, or composing a reply, it's not always possible for me to paste text from the clipboard without selecting existing text. Pressing and holding (as in all other iOS apps) simply does not show the Cut | Copy | Paste ... menu. It's only after selecting some text in the compose area and then press-hold on that that the menu shows up and pasting becomes possible.

I haven't put my finger on the exact circumstances in which pasting isn't possible, but it happens the majority of the times for me.

Expected Behavior

Press-hold, even when no text is selected, should always show the appropriate copy-paste menu, as in all iOS apps, to allow pasting any text from the clipboard.

Steps To Reproduce

The steps below in most of the cases show the issue (step 5) for me.

  1. Open the mastodon app
  2. Select some text in an existing post and copy it to the clipboard
  3. Create a new post
  4. Press-and-hold on the cursor (or double-tap)
  5. The paste-menu does not show up
  6. Enter some text, say hello, double-click to select it, which then brings up the Cut/Copy/Pate menu
  7. Select Paste to paste the text copied in step 2

Same happens when copying (say) a URL from a browser app and then switching to Mastodon and paste it there.

Environment

- Device: iPhone 13
- OS: iOS
- Version: 16.6.1
- Build: v2023.13 (348)

Anything else?

I noticed #510 from 2022, but it ends up concluding a new feature might be a good idea, not that existing functionality is broken. Hence this bug report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant