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.

Sign up for GitHub

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

Jump to bottom

[Bug]: New line prevented after adding a user mention #64326

Closed
annemirasol opened this issue Jun 3, 2022 · 2 comments
Closed

[Bug]: New line prevented after adding a user mention #64326

annemirasol opened this issue Jun 3, 2022 · 2 comments
Labels
[Closed] Resolved Issue is resolved. Use for issues that can be closed but did not have an explicit fix with a PR. Gutenberg RC Testing Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@annemirasol
Copy link
Contributor

Quick summary

After entering a user @-mention via autocompleter, no matter how many times ENTER is hit, new lines do not get added.

Steps to reproduce

  1. Start at any simple site with v13.4.0-rc.1 enabled (gutenberg-edge at time of writing).
  2. Type in a few things, then start adding a user mention, and use the aucompleter when it pops up.
  3. New lines are afterwards prevented.

What you expected to happen

I should be able to enter a new line after typing in a user mention.

What actually happened

No matter how many times I hit ENTER, no new lines.

Screen.Recording.2022-06-03.at.8.39.26.PM.mov

Context

Gutenberg Edge testing

Browser

Google Chrome/Chromium

Simple/Atomic

Simple

Other notes

Gutenberg: v13.4.0-rc.1
Editing Toolkit: 3.34442
WP AMP: 2.0.5
CoBlocks: 2.18.1-simple-rev.2

Reproducibility

Intermittent

Severity

Most (> 50%)

Available workarounds?

No response

Workaround details

No response
@annemirasol annemirasol added [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged Gutenberg RC Testing labels Jun 3, 2022
@chad1008
Copy link
Contributor

I've tracked the source of this down to a recent PR of mine, sorry for the inconvenience!

I've also confirmed this new bug is present in core, so an issue has been opened there as well:
WordPress/gutenberg#41724

@cuemarie
Copy link

This report was found during a recent backlog sweep.

📌 SCRUBBING : RESULT - Replicated / Could Not Replicate / Uncertain

  • Tested on Simple & SH: Could Not Replicate

📌 ACTIONS

  • Closed as Resolved

@cuemarie cuemarie added Triaged To be used when issues have been triaged. [Closed] Resolved Issue is resolved. Use for issues that can be closed but did not have an explicit fix with a PR. and removed Needs triage Ticket needs to be triaged labels May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[Closed] Resolved Issue is resolved. Use for issues that can be closed but did not have an explicit fix with a PR. Gutenberg RC Testing Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@annemirasol @chad1008 @cuemarie