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

Hitting send unexpectedly triggers predictive text completion #2008

Closed
Jaffex opened this issue Nov 1, 2023 · 1 comment · Fixed by #2547
Closed

Hitting send unexpectedly triggers predictive text completion #2008

Jaffex opened this issue Nov 1, 2023 · 1 comment · Fixed by #2547
Assignees
Labels
A-Rich-Text-Editor O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Team: Element X Feature Z-Labs A defect in a feature that is behind a labs flag.

Comments

@Jaffex
Copy link

Jaffex commented Nov 1, 2023

Steps to reproduce

With predictive text turned on in iOS 17+ (Settings > General > Keyboard > Predictive Text), try writing some text that gets predicted (indicated by a grey suggestion inside the message composer)

Outcome

What did you expect?

I would expect similar behavior to iMessage and other messaging apps.
Coming to mind are:

  1. Sending a message while having begun to type a word that gets predicted, it gets completed when hitting send (This is working already)
  2. A word you didn't even begin to type, but got predicted, should not be completed upon sending
  3. When hitting backspace, predicted text should not be completed

What happened instead?

  1. Worked as expected

  2. The word "time" in the below screen capture was predicted, but the user did not show intent to actually want it in the message. iMessage would only complete the word if you at least had entered a "t"

RPReplay_Final1698771975.mp4
  1. Seen below is the most confusing interaction: When a text is predicted, but the user changes their mind and hits backspace to correct their already written text, the predicted text gets completed in the composer and gets mixed up with whatever remained after the user's correction
RPReplay_Final1698772170.mp4

Another example:

RPReplay_Final1698852721.mp4

Your phone model

iPhone 12 mini

Operating system version

iOS 17.1

Application version

1.4.0

Homeserver

Synapse

Will you send logs?

No

@Jaffex Jaffex added the T-Defect label Nov 1, 2023
@ara4n ara4n changed the title Unexpected triggers for completing predictive text Hitting send unexpectedly triggers predictive text completion Nov 1, 2023
@pixlwave pixlwave added S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Occasional Affects or can be seen by some users regularly or most users rarely A-Rich-Text-Editor labels Nov 2, 2023
@Jaffex
Copy link
Author

Jaffex commented Nov 3, 2023

The issue was renamed to imply that only hitting send would trigger unexpected completion behavior - in light of this I just wanted to chime in once more to point to the 3rd point of the report:

Seen below is the most confusing interaction: When a text is predicted, but the user changes their mind and hits backspace to correct their already written text, the predicted text gets completed in the composer and gets mixed up with whatever remained after the user's correction

Where hitting backspace also triggers completion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Rich-Text-Editor O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Team: Element X Feature Z-Labs A defect in a feature that is behind a labs flag.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants